EPCTrainingASR5500v1

Cisco ASR 5500 TrainingPresented by: Amit DeshmukhVersion 1.0 Delivered: 12/20/2013

ASR5500 Chassis and Hardware

• Designed to provide subscriber management services for High-Capacity 4G wireless networks.

• The ASR5500 is a 21RU (36.75 in. x 17.5 in x 28.65 in. ), 19" rack-mount midplane-based chassis with input/output (I/O) and processing cards in the rear, and fabric cards in the front.

• The rear cards are larger and used for chassis management, I/O and session processing

• The smaller front cards are used for fabric crossbars and persistent storage.

• There are 10 slots at the front and rear of the chassis.



• The rear slots have a common midplane connector that is shared between the supported cards to allow different mixes of I/O and processing capacity depending on the customer's intended use.

• Power capacity include up to eight 80-amp, -48 VDC power feeds across redundant power filter units (PFUs).

• The connections are made at the top-rear of the chassis.• The ASR 5500 uses two types of fan tray units and a total of

four fan trays per chassis – two front fan trays and two rear fan trays.


MIO – Mgmt. I/ODPC – Data Processing CardFSC – Fabric and Storage CardSSC – System and Status CardPFU – Power Filter Unit


• The rear slots are numbered 1 through 10 with slots 5 and 6 used for the chassis management cards.

• The front slots are numbered 11 through 20.• Lower slot numbers begin at the left side.• There are no direct relationships between front and rear

cards.• There is a midplane within the ASR 5500 chassis interconnects

rear input/output ports and processing cards with front fabric cards.


Three BusesData control Management and HATTiming Distribution


• The larger rear cards support chassis management, input/output, and session processing.

• The smaller front cards provide fabric crossbars, persistent storage and system status monitoring.

• The two MIO slots (5 and 6) have additional midplane connections to perform chassis control operations, including support for a serial Console port and dual remote management ports.


• (1) MIO• (2) DPC• (3) FSC• (4) SSC


Management I/O Card (MIO)• The ASR5500 chassis supports two MIO Cards.• The MIO Cards automatically implement 1:1 port redundancy across slots 5 and 6.• Each MIO has: • •One CPU subsystem with 96 GB of RAM • •Four NPU subsystems• The two 1000Base-T (1GbE) ports on MIO cards can only be used for local context

(OAM). MIO in includes support for: • •Midplane connections for chassis control operations • •SAS storage controller for FSC solid state drives (SSDs) • •RS-232 serial console for CLI management • •USB port for an external flash device • •32 GB SDHC internal flash device


Data Processing Card (DPC)• The ASR 5500 chassis supports multiple DPCs in the rear

facing slots of the chassis. The DPC contains a common subset of the midplane connectors on the MIO allowing it to plug into the same slots as the MIO cards.

• The DPC has two identical CPU subsystems each containing: • •96 GB of RAM • •NPU for session data flow offload • •Crypto offload engines located on a daughter card• DPCs manage subscriber sessions and control traffic.


Fabric and Storage Card (FSC)• The ASR 5500 chassis supports multiple FSCs in front facing slots of the chassis. The FSC uses

dedicated slots in the middle of the front side of the chassis.• The FSC features: • •Fabric cross-bars providing in aggregate: • –120 Gbps full-duplex fabric connection to each MIO • –60 Gbps full-duplex fabric connection to each DPC • •Two 2.5" serial attached SCSI (SAS) solid state drives (SSDs) with a 6 Gbps SAS connection to each

chassis management MIO.• Every FSC adds to the available fabric bandwidth to each card. Each FSC connects to all MIOs or

DPCs, with a varying number of links depending on the MIO or DPC slot. Three FSCs provide sufficient bandwidth with the fourth FSC supports redundancy.

• The SSDs are not field replaceable units (FRUs). If an SSD fails the FSC must be replaced.• Each FSC provides the storage for one quarter of the RAID 5 array. Data is striped across all four

FSCs with each FSC providing parity data for the other three FSCs. The array is managed by the Master MIO.


System Status Card (SSC)• The ASR 5500 chassis supports two SSCs in front facing slots

of the chassis. SSCs use dedicated slots in the left most slots of the front side of the chassis.

• The SSC card features: • •Three alarm relays (Form C contacts) • •Audible alarm • •System status LEDs


ASR5500 Software Architecture Overview

• *OS******** show version verbose *******Wednesday December 11 15:31:07 PST 2013Active Software:Image Version: 15.0 (52633)Image Branch Version: 015.000(016)Image Description: Production_BuildImage Date: Thu Nov 28 06:56:27 EST 2013Boot Image: /flash/production.52633.asr5500.binKernel Version: 2.6.38-staros-v3-hw-64Kernel Machine Type: x86_64

******** show system uptime *******Wednesday December 11 15:31:13 PST 2013System uptime: 8D 4H 24M

16


******** show boot *******Wednesday December 11 15:31:13 PST 2013

boot system priority 89 \ image /flash/production.52633.asr5500.bin \ config /flash/consumer-temp.cfg

boot system priority 90 \ image /flash/production.52586.asr5500.bin \ config /flash/config-111813-14-config-backup-brawal.cfg




17


Upgrade Procedure• Check if the latest configuration is added properly, by running the below mentioned command:• [local]ASR5500# show config • Save the updated configuration file by running the below mentioned command• [local]ASR5500# save config /flash/<15.0-new-config-filename-1>.cfg –redundant –no confirm• Update the boot record by running the below mentioned command• [local]ASR5500# show boot• [local]ASR5500# config • [local]ASR5500(config)# boot system priority n-1 image /flash/<production.xxxxx.asr5500.bin> config

/flash/<15.0-new-config-filename-1>.cfg • [local]ASR5500# end• <production.xxxxx.asr5500.bin> is the image file which is currently in use and can be found from the lowest boot

entry recorded in the output of show boot command above.• Synchronize both the MIOs by running the below mentioned command to update the latest configuration and

boot priority on the standby MIO• [local]ASR5500# file system synchronize all• Reload the standby gateway as Demux Card type change only takes effect on boot.• [local]ASR5500# reload • Are you sure? [Yes|No]: Yes

18


******** show hardware inventory *******Wednesday December 11 15:31:13 PST 2013Slot Type Part Number Product ID / Version ID Serial Num CLEI code---- ---- ----------------- ----------------------- ----------- ---------- 1: DPC 73-14872-03 C0 ASR55-DPC-K9 V05 SAD1630010W -- CCK 73-15573-01 B0 -- -- SAD173200F6 -- 2: DPC 73-14872-03 C0 ASR55-DPC-K9 V05 SAD1606019E -- CCK 73-15573-01 B0 -- -- SAD172700R0 -- 3: DPC 73-14872-03 C0 ASR55-DPC-K9 V05 SAD1606018V -- CCK 73-15573-01 B0 -- -- SAD1735001L -- 4: DPC 73-14872-03 C0 ASR55-DPC-K9 V05 SAD152902ZY -- CCK 73-15573-01 B0 -- -- SAD173400P7 -- 5: MIO 73-14234-03 A0 ASR55-MIO-BASE-K9 V03 SAD1603019T -- XDC 73-14547-01 A0 -- -- SAD160300WC -- XDC 73-14547-01 A0 -- -- SAD160300X9 -- CCK 73-14548-01 A0 -- -- SAD1550018T -- MEC 73-14501-01 A0 ASR55-MEC V01 SAD151602R0 -- MIDP 73-14232-01 A0 -- -- TBM15384182 -- CHAS 73-14344-01 A0 ASR55-CHS-SYS V01 FLM154601EY -- 6: MIO 73-14234-03 A0 ASR55-MIO-BASE-K9 V03 SAD1603019N -- XDC 73-14547-01 A0 -- -- SAD16010289 -- XDC 73-14547-01 A0 -- -- SAD16010285 -- CCK 73-14548-01 A0 -- -- SAD1601029J -- MEC 73-14501-01 A0 ASR55-MEC V01 SAD151602R0 -- MIDP 73-14232-01 A0 -- -- TBM15384182 -- CHAS 73-14344-01 A0 ASR55-CHS-SYS V01 FLM154601EY -- 7: DPC 73-14872-03 C0 ASR55-DPC-K9 V05 SAD163700JL -- CCK 73-15573-01 B0 -- -- SAD1725012W -- 8: DPC 73-14872-03 C0 ASR55-DPC-K9 V05 SAD15360163 --


• show task resources



• sitmain – System Initialization Task• sitparent – • hatcpu – High Availability Task• rmmgr – Resource Manager• dhmgr – • rctmgr – Recovery Control Task• egtpinmgr – Evolved GTP Manager Ingress• egtpemgr – Evolved GTP Manager Egress• vpnmgr – VPN Manager• sessmgr – Session Manager• aaamgr – Accounting Task


Command Line Interface• Console• ssh or Telnet

Security Administrator

Administrator

Configuration ModeOperator

Inspector


MGMT Virtual Router # Security Administrator (context Local – Default)

# configure(config)# (Global or Root) context <context name>

# exit

# end

IP Access List Name

sgw-service (service Name)


The CLI interface format is based on ANSI T1276# configure

# context SAEGW # bfd protocol enables bidirectional forwarding detection

# exitrouter bgp 64675 (Autonomous System Number)

: :

exit # interface mme-sgw-s5::

exit


Configuration Terminology• Contexts- Virtual routers also called work spaces or folders

isolated from one to another context.• Logical Interfaces – It is an IP address that is defined within a

context.• Logical interface is independent of any physical port• A context is a virtual router similarly a logical interface can be

visualized as an interface in that virtual router.• A logical interface can have up to 17 secondary IP addresses

assigned to it without VLAN Tagging and 1017 with VLAN Tags.• In ASR5K up to 512 logical interfaces can be configured


Context A

Local Context

Context B

Context C

Added Via Configuration

Default Context for Management

27


Examples of logical interface are S11 Interface, sGi Interface, Diameter Interface

Context A

Logical Interface A IP Address 192.168.1.150

Context B

Logical Interface A IP Address 192.168.2.150

Logical Interface within a context

28


29


30

31


Bindings and associations• Binding is defined as assigning a physical Ethernet port to a

logical interface.• There can be multiple interface bindings to the same physical

ports separated by VLANS• A binding can also be configured between a service and a

logical interface IP Address.• An association is instantiating one service into another • One service can be associated with multiple services.• A service provides call processing capability

32


Bindings CLI Binding

CLI Binding CLI Binding

Logical Interface A(10.1.8.150/32)

Service

Logical Interface B(10.1.8.17/28)

Logical Interface C(10.1.8.33/28)

Active MIO 10G 5/10 STDBY Active MIO

10G 5/20STDBY

33


sgw-service Associations gtpu-service SGW_S1u_DATA_SVC Association S11 Ingress egtp-service SGW_S11_CTRL_SVC Association

Association egress egtp-service SGW_S5_CTRL_SVC S5

Association gtpu-service SGW_S5_DATA_SVC

sgw-service SGW_SVC

34


pgw-service Associations gtpu-service PGW_S5_DATA_SVC

Associationegtp-service PGW_S5_CTRL_SVC

Association

pgw-service PGW_SVC

35


Software Tasks• Software tasks can be correlated to call-processing configurations• For every context there is a vpnmgr instance• For every service there is a corresponding signaling manager• For sgw-service there are two signaling managers (egtpimgr &

egtpemgr)• Subscriber sessions are contained within sessmgr and aaamgr.• There is a one to one correspondence between the sessmgr instance

and the aaamgr instance however they cannot reside on the same DPC for session recovery purpose.

36


SAEGW

sessmgr

aaamgr

sgw-servicepgw-service

egtpimgregtpemgr

vpnmgr vpnmgr

SGi ConfigS11/s1u

SGi

37


Software Tasks• Many tasks have a parent child relationship referred to as controllers and

managers• A controller tasks runs on the active MIO and are responsible for creating

manager tasks• Session controller (sessctrl) creates multiple instances of sessmgr and

aaamgr• VPN controller (vpnctrl) creates a vpnmgr for each context• The vpnmgr facilitates IP routing across and within contexts• Signalling managers (egtpimgr/egtpemgr) and all instances of vpnmgr also

reside on the active MIO and hence acts as Demux card• The sessmgr and aaamgr tasks run on the control processors (CPs) located

on the DPC cards. There are no sessmgr and aaamgr tasks running on MIO

38


39


Tasks Related to startup• Active MIO is the first to boot by loading the binary image

found on the flash card• The first task to start is the system initialization task (SIT)• SIT is responsible for the startup of the Linux kernel and

starOS on each processer of each module• SIT starts a set of initial static tasks at system startup time• The SIT on the MIO creates SIT manager instances on each

DPC cards. Resource manager audits the HW capabilities.SIT –invokes RM –invokes CSP Module (card slot port)

40


41


Tasks Related to RedundancyThe following tasks work together to provide SW/HW recovery and failover.• High Availability Task (HAT) – Maintains the operation state of

the system by monitoring the SW and HW on each board• Recovery Control TASK (RCT) – Depending on the triggers fed

by the HAT and the CSP module, the RCT executes recovery for any failure that occurs in the system

• Shared Configuration Task (SCT) – The SCT is notified of system configuration parameters. It sets, retrieves and stores configuration data for the applications that run in the system

Thank You

Date post:	25-Jul-2015
Category:	Documents
Upload:	amit-deshmukh
View:	84 times
Download:	0 times

EPCTrainingASR5500v1

Documents