> System Software Task and Subsystem Descriptions
> For redundancy, scalability and robust call processing, the system’s software is divided into a series of tasks that perform specific functions. These tasks communicate with each other as needed to share control and data signals. As a result, system processes can be distributed across multiple tasks thus reducing the overall work-load on any given task and improving system performance. In addition, this distributed design provides fault containment that greatly minimizes the impact to the number of processes or sessions due to a failure.
> All tasks run in a Common Firmware Environment (CFE) that resides on specialized Central Processing Units (CPUs) on each of the application cards. The Packet Services Card (PSC) contains two CPUs (CPU 0 and 1, CPU 0 is the lead CPU). The CPUs on the PSC are responsible for session processing, and for running the various tasks and processes required to handle the mobile data call. In addition to the CPUs, PSCs each have a Network Processor Unit (NPU) for IP forwarding.
> The following sections describe the primary tasks that are implemented by the system:
> Primary Task Subsystems
> The individual tasks that run on the CPUs are divided into subsystems. Following is a list of the primary subsystems responsible for call session processing:

> • | System Initiation Task (SIT): This subsystem starts tasks and initializes the system. This includes starting a set of initial tasks at system startup time (static tasks), and starting individual tasks on demand at arbitrary times (dynamic tasks).

> • | High Availability Task (HAT): With the Recovery Control Task (RCT) subsystem, the HAT subsystem maintains the operational state of the system. HAT monitors the various software and hardware components of the system. If there are unusual activities, such as the unexpected termination of another task, the HAT subsystem takes a suitable course of action, such as triggering an event to the RCT subsystem to take corrective action or to report the status. The end result is that there is minimal or no impact to the service.

> • | Recovery Control Task (RCT): This subsystem executes a recovery action for any failure that occurs in the system. The RCT subsystem receives signals from the HAT subsystem (and in some cases from the NPU subsystem) and determines what recovery actions are needed.

> The RCT subsystem runs on the active SMC and synchronizes the information it contains with the RCT subsystem on the standby SMC.

> • | Shared Configuration Task (SCT): This subsystem provides a facility to set, retrieve, and receive notification of system configuration parameters. The SCT is mainly responsible for storing configuration data for the applications that run on the system.

> The SCT subsystem runs only on the active SMC and synchronizes the information it contains with the SCT subsystem on the standby SMC.

> • | Resource Management (RM): This subsystem assigns resources, such as CPU loading and memory, for every system task upon start-up. The RM subsystem monitors resource use to verify that allocations are as specified. RM also monitors all sessions and communicates with the Session Controller to enforce capacity licensing limits.

> • | Virtual Private Network (VPN): This subsystem manages the administrative and operational aspects of all VPN-related entities in the system. The functions performed by the VPN subsystem include:

> • | Creating separate VPN contexts

> • | Starting the IP services within a VPN context

> • | Managing IP pools and subscriber IP addresses, and distributing the IP flow information within a VPN context.

> All IP operations within the system are done within specific VPN contexts. In general, packets are not forwarded across different VPN contexts. The only exception currently is the Session subsystem.

> • | Network Processing Unit (NPU): This subsystem is responsible for the following:

> • | Using the database to match address and port numbers to destination tasks for fast-path forwarding of dataframes

> • | Receiving and transmitting user data frames to/from various physical interfaces

> • | IPv4 forwarding decisions (both unicast and multicast)

> • | Per-interface packet filtering

> • | Traffic management and traffic engineering

> • | Passing user data frames to/from PAC/PSC CPUs

> • | Modifying, adding, or stripping datalink/network layer headers

> • | Recalculating checksums

> • | Maintaining statistics

> • | Managing external Ethernet interfaces

> • | Card/Slot/Port (CSP): Coordinates the events that occur when any card (application or line) is inserted, locked, unlocked, removed, shutdown, or migrated. SCP also performs auto-discovery and configures ports on a newly-inserted line card. It determines how line cards map to PSC/PSC2 cards (through a Redundancy Crossbar Card (RCC), if necessary).

> The CSP subsystem runs only on the active SMC and synchronizes the information it contains with the SCT subsystem on the standby SMC. It is started by the SIT subsystem and monitored by the HAT subsystem.

> • | Session: Performs high-touch processing of mobile subscribers’ packet-oriented data session flows. High-touch user data processing consists of the following:

> • | Payload transformation

> • | Filtering and scheduling

> • | Statistics collection

> • | Policing

> Primary Subsystem Composition
> Many of the primary subsystems are composed of critical tasks—controller tasks called Controllers, and subordinated tasks called Managers. Critical tasks are essential to the system’s ability to process calls, such as those in the SIT subsystem.
> Controllers serve several purposes:

> • | They monitor the state of their Managers and allow communication between Managers within the same subsystem.

> • | They enable inter-subsystem communication since they can communicate with the controllers of other subsystems.

> • | They masks the distributed nature of the software from the user allowing for ease of management.

> Managers manage resources and mappings between resources. In addition, some managers are directly responsible for call processing.
> The following sections provide information about the composition of the primary subsystems that are composed of critical, controller, and /or manager tasks:
> ASR 5000 Subsystems
> The following tables describe managers and tasks performing within the specified subsystems on an ASR 5000.
> Important: Variations regarding how the managers and tasks are distributed based on session recovery are included in the Card and CPU columns in some tables. Tables without these indicators are applicable to ASR 5000s with and without session recovery. The ASR 5000 dynamically distributes processes, tasks, and managers on startup. The following tables list the typical locations but variations can occur depending on available resources.
> ASR 5000 System Initiation Subsystem

> Task | Description | Card | CPU
> SITMAIN | Initiated at system start-up, the SITMAIN task performs the following functions:
> • | Reads and provides startup configuration to other SIT components
> • | Starts SITREAP sub-function
> • | Maintains CPU state information
> | All | All
> SITPARENT sub-function |
> • | Starts SMCs in either active or standby mode
> • | Registers tasks with HAT task
> • | Notifies CSP task of CPU startup completion
> Important: SITPARENT replaces the sub-functions SITPAC, SITSPC and SITTAC. | All | All
> SITREAP sub-function | Shuts down tasks as required | All | All

> ‌
> ASR 5000 High Availability Subsystem

> Task | Description | Card | CPU
> HAT System Controller (HATSYSTEM) | This is the main HAT task that will control all the HAT sub-function tasks in the system. It is initiated on system start-up and performs the following functions:
> • | Initializes system components (such as the Gigabit Ethernet switches and switch fabric)
> • | Monitors system components such as fans for state changes
> • | Triggers actions for redundancy in the event of fault detection
> The HAT subsystem on the redundant SMC mirrors the HAT subsystem on the active SMC. | SMCs | 0
> HATCPU |
> • | Performs device initialization and control functions because of the CPUs hardware capabilities
> • | Reports the loss of any task on its CPU to HATSYSTEM sub-function
> • | Initializes and monitors the dedicated hardware on PACs
> | All PSCs | 0
> • | Collects CPU monitoring information periodically and reports to the master HATCPU sub-function
> • | Reports the loss of any task on its CPU to the master HATCPU sub-function
> | All PSCs | ALL
> • | Performs device initialization and control functions because of the CPU’s hardware capabilities
> • | Reports the loss of any task on its CPU to HATSYSTEM sub-function
> • | Controls the LEDs on the SMC
> • | Initializes and monitors the dedicated hardware on the SMCs
> | SMCs | 0

> ‌
> ASR 5000 Resource Manager (RM) Subsystem

> Task | Description | Card | CPU
> Resource Manager Controller (RMCTRL) | Started by the SITPARENT task on system startup, and monitored by the HAT task for a failure, the RMCTRL performs the following functions at startup:
> • | Initializes resources such as CPUs and memory
> • | Requests updated card status from the CSP subsystem and updates the system card table
> • | Communicates with all RMMGRs to request their most recent set of resource data
> | Active SMC | 0
> Resource Manager Managers (RMMGRs) | Started by the SITPARENT task, and monitored by the HAT tasks for failures, each RMMGR performs the following functions at startup:
> • | Initializes the local resource data and local resource scratch space
> • | Communicates with the SIT task on the local CPU to get its entire task table and the resources associated with each task
> • | Gathers current resource utilization for each task
> • | Sends the resource data to the RMCTRL task
> | All | All

> ‌
> ASR 5000 Virtual Private Networking (VPN) Subsystem

> |  | Card | CPU
> Task | Description | w/o SR | w/ SR | w/o SR | w/ SR
> VPN Controller (VPNCTRL) | Created at system start-up, the VPN Controller:
> • | initiates the VPN Manager for each context
> • | informs the Session Controller task when there are additions or changes to contexts
> • | routes context specific operation information to the appropriate VPN Manager
> • | performs VPN Manager recovery and saves all VPN related configuration information in the SCT task
> Only one Session Controller operates at any time | Active SMC | Active SMC | 0 | 0
> VPN Manager (VPNMGR) | One VPN manager is started by the VPN Controller for each configured context (one is always present for the local context) and performs the following functions:
> • | Performs IP address pool and subscriber IP address management
> • | Performs all the context specific operations including but not limited to: UCM services, IP interfaces, the Address Resolution Protocol (ARP), IP address pool management, slow path forwarding, NPU flows, port Access Control Lists (ACLs), and logging
> • | Provides IP interface address information for each context to the Session Controller
> | Active SMC (local context)Active PSCs (cfg contexts) | Active SMC (local context)1st PSC (cfg contexts) | 0 (all contexts) | 0 (local context)All on 1st PSC (cfg contexts)
> Border Gateway Protocol (BGP) | The BGP task is created by the VPN Manager for each context that has enabled the BGP routing protocol (“router bgp” config-context CLI command). The BGP task is responsible for learning and redistributing routing information via the BGP protocol. This includes:
> • | maintaining the BGP peering connections
> • | applying any defined BGP routing policy
> | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr.
> Open Shortest Path First (OSPF) | The OSPF task is created by VPN Manager for each context that has enabled the OSPF routing protocol (“router ospf” config-context CLI command). The OSPF task is responsible for learning and redistributing routing information via the OSPF protocol. This includes:
> • | maintaining the OSPF neighboring relationship
> • | LSA database maintenance
> • | SPF calculations
> • | applying any defined OSPF routing policy
> | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr.
> Open Shortest Path First (OSPFv3) | The OSPFv3 task is created by VPN Manager for each context that has enabled the OSPF routing protocol (“router ospfv3” config-context CLI command) The OSPFv3 task is responsible for learning and redistributing routing information via the OSPFv3 protocol. This includes:
> • | maintaining the OSPFv3 neighboring relationship
> • | LSA database maintenance
> • | OSPFv3 SPF calculations
> • | applying any defined OSPFv3 routing policy
> | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr.
> Routing Information Protocol (RIP) | The RIP task is created by VPN Manager for each context that has enabled the RIP routing protocol (“router rip” config-context CLI command) The RIP task is responsible for learning and redistributing routing information via the RIP protocol. This includes:
> • | maintaining the RIP database
> • | sending periodic RIP update messages
> • | applying any defined RIP routing policy
> | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr.
> ZEBOSTM OSPF Message | The Zebos task is created by VPN Manager for each context. The Zebos task is responsible for maintaining the routing table for the context. This includes:
> • | maintaining the routing table (RIB and FIB)
> • | static routing
> • | interfacing to the kernel for routing & interface updates
> • | redistributing routing information to dynamic routing protocols
> • | calculating nexthop reachability
> | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr. | Same as VPN Mgr.

> ‌
> ASR 5000 Network Processing Unit (NPU) Subsystem

> Task | Description | Card | CPU
> NPU Controller (NPUCTRL) | Created at system start-up, the NPU Controller performs the following functions:
> • | Monitors the state of NPU Managers in the system
> • | Registers to receive notifications when NPU Manager crashes
> • | Controls recovery operation
> • | Provides a centralized location for CLI commands related to NPU Manager state
> Only one NPU Controller operates in the system at any time. | Active SMC | 0
> NPU Manager (NPUMGR) | The NPU Manager task is created for every PSC installed and started and it performs the following functions:
> • | Provides port configuration services to the CSP task
> • | Provides interface binding and forwarding services to the VPN Manager
> • | Provides flow insertion and removal services to Session Manager and AAA Manager tasks
> • | Provides recovery services to the NPU Controller
> | SMCs/PSCs | 0

> ‌
> ASR 5000 Session Subsystem

> Task | Description | Card | CPU
> |  | w/o SR | w/ SR | w/o SR | w/ SR
> Session Controller (SESSCTRL) | Created at system start-up, the Session Controller task performs the following functions:
> • | Acts as the primary point of contact for the Session Subsystem. Since it is aware of the other subsystems running within the system, the Session Controller acts as a proxy for the other components, or tasks, that make up the subsystem
> • | Starting, configuring, and coordinating the efforts of the Session Processing Subsystem sub-managers
> • | Works with Resource Manager to start new Session Managers when all existing Session Managers exceed their capacity
> • | Receives context information from VPN Managers
> • | Distributes IP interface address information to other Session Processing Subsystem sub-managers
> • | Manages Enhanced Charging Service, Content Filtering and URL Blacklisting services
> Only one Session Controller operating in the system at any time. | Active SMC | Active SMC | 0 | 0
> Session Manager (SESSMGR) | Created by the Session Controller, the Session Manager performs the following functions:
> • | Provides a subscriber processing system that supports multiple session types
> • | Multiple Session Managers can run on a single CPU and/or can be distributed throughout any CPU present in the system
> • | A single Session Manager can service sessions from multiple A11 Managers, ASNGW Manager, ASN PC Manager, GTPC Message Managers, and from multiple contexts
> • | Protocol processing for A10/A11, GRE, R3, R4, R6, GTPU/GTPC, PPP, and Mobile IP
> • | Manages Enhanced Charging Service, Content Filtering and URL Blacklisting services
> Session Managers are paired with AAA Managers. | All PSCs | All PSCs except 1st | 0 | 0 on all PSCs except 1st
> A11 Manager (A11MGR) | Created by the Session Controller for each context in which a PDSN service is configured, the A11 Manager task performs the following functions:
> • | Receives the R-P sessions from the PCF and distributes them to different Session Manager tasks for load balancing
> • | Maintains a list of current Session Manager tasks to aid in system recovery
> The A11 Manager task is also known as the Signaling De-multiplexing task (SDT). Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | Active PSCs | 1st PSC | 0 | Any (see NOTE)
> Access Link Control Application Part Manager (ALCAPMgr) | The ALCAP Mgr tasks starts when an ALCAP service configuration is detected. There can be multiple instances of this task for load sharing. All ALCAP Managers will have all the Active ALCAP Services configured in HNB-GW service and will be identical in configuration and capabilities.
> • | It runs the ALCAP protocol stack and handles the IuCS-over-ATM associations
> • | Maintains AAL2 node entity databases
> • | Provides nodal functions for IuCS-over-ATM interface on ALCAP protocol
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. The HNBMGRs should not be started on a PSC which has the HNB DEMUX MGR started. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> ASN Gateway Manager (ASNGWMGR) | Created by the Session Controller, the ASN Gateway Manager performs the following functions:
> • | Provides a subscriber processing system that supports multiple session types
> • | Multiple ASNGW Managers can run on a single CPU and/or can be distributed throughout any CPU present in the system
> • | A single ASN GW Manager can service sessions from multiple ASN PC Managers and multiple contexts
> • | Protocol processing for R3, R4, R6, GRE tunneling, and Mobile IP
> | Active PSCs |  | 0 |
> ASN PC Manager (ASNPCMGR) | Created by the Session Controller, the ASN Paging Controller and Location Registry Manager performs the following functions:
> • | Provides a subscriber processing system that supports multiple paging controller and location update session types
> • | Multiple ASNPC Managers can run on a single CPU and/or can be distributed throughout any CPU present in the system
> • | A single ASN GW Manager can service sessions from multiple contexts
> • | Protocol processing for R3, R4, R6, GRE tunneling, and Mobile IP
> | Active PSCs |  | 0 |
> Authorization, Authentication, and Accounting (AAA) Manager (AAAMGR) | AAA Managers are paired with Session Managers (except the one running on the SMC) and perform the following functions:
> • | Performs all AAA protocol operations and functions for subscribers and administrative users within the system
> • | Acts as a AAA client to AAA servers
> • | Manages GTP Prime (GTPP) messaging with charging gateway functions (CGFs).
> • | Multiple AAA Managers can run on a single CPU and/or can be distributed throughout any CPU present in the system.
> • | AAA operations for the CLI are done through a AAA Manager running on the active SMC
> | Active PSCs | All PSCs except 1st | All except 0 | All
> Active SMC (CLI only) | Active SMC (CLI only) | 0 | 0
> Charging Detail Record Module (CDRMOD) | CDRMOD is created by VPNCTRL proclet in v90+ releases and by the VPNMGR proclet in pre-v90 releases. Responsible for receiving EDR/UDR records from different ACSMGR instances in the system. Responsible for writing the received EDR/UDR records in files using the configured file naming conventions. | 1st PSC | 1st PSC | 0 | 0
> Diameter GMB Application Manager (DGMBMGR) | DGMBMGR is created specifically for providing MBMS feature support for GGSN. It is instantiated when an MBMS policy CLI is configured in the GGSN Service configuration mode. DGMBMGR maintains the MBMS UE and bearer contexts. It handles the GMB interface over a Diameter connection to a BMSC Server for MBMS bearer sessions. DGMBMGR recovers by polling all SMGRs for MBMS session states and recreating the MBMS UE and MBMS bearer context information. | Active PSCs |  | 0 |
> Diameter Proxy (DIAMPROXY) | Diameter proxy is created by DIACTRL (which runs as part of VPNCTRIL) and the number of DIAMPROXY tasks spawned is based on the configuration to use “multiple” or “single” proxies. In instances that a single proxy is configured, only one DIAMPROXY task is spawned for the entire chassis and runs on demux PACs. When multiple proxies are configured, one DIAMPROXY task is run per PAC. It performs the following functions:
> • | Maintains diameter base connections to all peers configured in the system
> • | Informs applications about any change in the connection status
> • | Acts as a pass-through to the messages from application to the diameter server
> • | Just acts as a forwarding agent (doesn't maintain any queues)
> A single diameter proxy is used to service multiple diameter applications | Active PSCs (see description) | Active PSCs (see description) | All (see description) | All (see description)
> eGTP Egress Manager | Created by Session Controller for each context in which an egtp-service of interface type sgw-egress or MME is configured. The egtpinmgr performs the following functions:
> • | Handles certain EGTP messages from SGW, PGW
> • | Maintains list of current EGTP sessions
> • | Maintains list of current Session Manager tasks which aids in session recovery
> • | Handles GTP Echo messaging
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | PSC | 1st PSC | All | Any (see NOTE)
> eGTP Ingress Manager | Created by Session Controller for each context in which an egtp-service of interface type sgw-ingress or pgw-ingress is configured. The egtpinmgr performs the following functions:
> • | Receives EGTP sessions from MME/S4 SGSN/SGW and distributes them to different Session Manager tasks for load balancing
> • | Maintains list of current EGTP sessions
> • | Maintains list of current Session Manager tasks which aids in session recovery
> • | Handles GTP Echo messaging
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | PSC | 1st PSC | All | Any (see NOTE)
> Foreign Agent (FA) Manager (FAMGR) | Created by the Session Controller for each context in which an FA service is configured, the FA Manager performs the following functions:
> • | Maintains a list of the FA-services available within the context and performs load-balancing for them
> • | Performs load-balancing by routing incoming MIP calls between the FA Managers
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | Active PSCs | 1st PSC | 0 | Any (see NOTE)
> GPRS Tunneling Protocol Control (GTPC) Message Manager (GTPCMGR) | Created by the Session Controller for each context in which a GGSN service is configured, the GTPC Manager task performs the following functions:
> • | Receives the GTP sessions from the SGSN and distributes them to different Session Manager tasks for load balancing
> • | Maintains a list of current Session Manager tasks to aid in system recovery
> • | Verifies validity of GTPC messages
> • | Maintains a list of current GTPC sessions
> • | Handles GTPC Echo messaging to/from SGSN'
> | Active PSCs |  | 0 |
> GTP-U Manager (GTPUMGR) | Created by the Session Controller for each context in which a GTPU service is configured, the GTPU Manager performs the following functions:
> • | Maintains a list of the GTPU-services available within the context and performs load-balancing (of only Error-Ind) for them
> • | Support for GTPU Echo handling
> • | Path Failure detection on no response for GTPU echo
> • | Error-Ind reception and demuxing it to a particular SMGR
> • | Default GTPU listener. GTPUMGR will process GTPU packets with invalid TEID
> Above features are supported for both GTPUv0 and GTPUv1. Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | Active PSCs | 1st PSC | 0 | Any (see NOTE)
> HNB Demux Manager (HNBDemux) | The HNB Demux Manager is started as part of HNB-GW service creation procedure. There will be only one HNBDEMUX MGR in the chassis.
> • | Distributes incoming Iuh connections to HNB Mgrs in the system
> • | Aware of all the active HNB-GW services in the system
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC but should not be created on the same PSC that has HNB Manager. | PSC | PSC (see NOTE) | 0 | Any (see NOTE)
> HNB Manager (HNBMgr) | The HNB Mgr tasks starts when an HNB-GW service configuration is detected. There can be multiple instances of this task for load sharing. All HNB Managers will have all the Active HNB-GW Services configured and will be identical in configuration and capabilities.
> • | It runs the SCTP protocol stack
> • | handles the SCTP associations
> • | Maintains Home-NodeB databases
> • | Provides nodal functions for Iuh interface on SCTP protocol
> Important: For ASR 5000s with session recovery enabled, this manager is usually established on one of the CPUs on the 1st active PSC. The HNBMGRs should not be started on a PSC which has the HNB DEMUX MGR started. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> Home Agent (HA) Manager (HAMGR) | Created by the Session Controller for each context in which an HA service is configured, the HA Manager performs the following functions:
> • | Receives Mobile IP sessions from the Foreign Agents (FAs) and distributes them to different Session Manager tasks
> • | Maintains a list of current Session Manager tasks that aids in system recovery
> • | Functions as the DemuxMgr – handles all the PMIP signaling packets.
> • | HAMgr also functions as the Demuxmgr for MIPv6/MIPv4 HA.
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | Active PSCs | 1st PSC | 0 | Any (see NOTE)
> IMSI Manager for MME (IMSIMgr) | The IMSI Mgr tasks starts when an MME service configuration is detected. There will be only one instance of this taks.IMSI Manager has the following functions:Signaling De-multiplexer: Selects which SessMgr to use for new subscriber sessions.IMSI-to-SessMgr resolutionMaintains and reports MME related Demux statistics on events like Attach by IMSI, Attach by GUTI etc. IMSIMgr can interact with following different tasks in the system:
> • | Session Controller
> • | MME Manager
> • | Session Manager
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. The IMSIMgr will not start on a PSC in which SessMgrs are started. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> International Mobile Subscriber Identity Manager for SGSN (IMSIMgr) | Started by the Session Controller, the IMSIMgr performs the following functions
> • | Selects SessMgr, when not done by LinkMgr or SGTPCMgr, for calls sessions based on IMSI/P-TMSI.
> • | Load-balances across SessMgrs to select one for assigning subscriber sessions to.
> • | Maintains records for all subscribers on the system.
> • | Maintains mapping between the IMSI/P-TMSI and SessMgrs.
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active deumux PSC. The IMSIMgr will not start on a PSC in which SessMgrs are already started. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> IP Services Gateway Manager (IPSGMGR) | Created by the Session Controller, the IPSG Manager performs the following functions:
> • | In Server mode, acts as a RADIUS server, and supports Proxy functionality
> • | In Snoop mode supports snooping RADIUS Accounting messages
> • | Load balances requests among different SessMgrs
> • | Activates and deactivates sessions
> | Active PSCs |  | 0 |
> Layer 2 Tunneling Protocol Manager (L2TPMGR) | Created by the Session Controller for each context in which a LAC or LNS service is configured, (additional Managers created as needed depending on loading) the L2TP Manager task performs the following functions:
> • | Responsible for all aspects of L2TP processing
> • | Maintain protocol state machines for all L2TP sessions and tunnels
> • | Trigger IPSec encryption for new L2TP tunnels as needed
> • | Work with Session Managers to gracefully bring down tunnels
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | Active PSCs | 1st PSC | 0 | Any (see NOTE)
> L2TP Demultiplexor Task (L2TPDEMUX) | Created by the Session Controller when a LNS service is created, only one L2TPDemux task is invoked for the entire system. This task performs the following functions:
> • | De-multiplexes and forwards new incoming tunnel create requests to L2TPMgrs
> • | Maintains information about current active tunnels in all L2TPMgrs
> • | Load balances requests among L2TPMgrs
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. | Active PSCs | 1st PSC | 0 | Any (see NOTE)
> Mobile Access Gateway Manager | Created by the Session Controller when the first MAG service is created in a context. This task performs the following functions:
> • | Sends and receives PMIP control messages (PBU/PBA)
> • | Adds an NPU flow to receive MIPv6 PBA packets. This flow is identical to the flow used in the HAMgr
> • | Maintains the Binding Update List used to keep track of the mobile node’s bindings:
> • | MN-ID
> • | APN
> • | Home Network Prefix and prefix length
> • | IPv6 LMA address
> • | IPv4 Home Address
> • | Originates PBU based on trigger received from the Session Manager during error conditions
> • | Receives PBA and forwards it to Session Manager
> • | Debugging facility – “magmgr” and “mobile-ipv6”
> | PSC |  | Same as VPN Mgr. |
> Mobility Management Entity Demux Manager (MMEDemux) | The MME Demux Manager is started as part of MME service creation procedure. There will be only one MME DEMUX MGR in the chassis.
> • | Distributes incoming S1-MME SCTP connections to MME Mgrs in the system
> • | Aware of all the active MME services in the system
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC but should not be created on the same PSC that has MME Manager. | PSC | PSC (see NOTE) | 0 | Any (see NOTE)
> Mobility Management Entity Manager (MMEMgr) | The MME Mgr tasks starts when an MME service configuration is detected. There can be multiple instances of this task for load sharing. All MME Managers will have all the Active MME Services configured and will be identical in configuration and capabilities.
> • | It runs the SCTP protocol stack
> • | Handles the SCTP associations
> • | Maintains TA List
> • | Manage eNodeB databases
> • | Provides nodal functions for S1-MME protocol
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC. The MMEMGRs should not be started on a PSC which has the MME DEMUX MGR started. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> PCC Bindmux Manager (PCC Demux) | The Bindmux Manager is started as part of PCC service creation procedure. There will be only one BindMux MGR in the chassis. The BindMux function handles multiplexing of the sessions across the available PCCMgrs along with the session binding functions. The capabilities includes:
> • | "Monitors load on PCCMgrs
> • | Distributes incoming IP-CAN connections across PCC Mgrs in the system
> • | "Perform session binding; i.e. binding of IP-CAN/Gateway session with the AF-Session
> • | "Ensure all messaging for an IMSI across various interfaces is directed towards the selected PCCMgr
> • | Aware of all the active PCC services in the system.
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active PSC but should not be created on the same PSC that has PCC Manager. | PSC | PSC (see NOTE) | 0 | Any (see NOTE)
> PCC Manager (PCCMgr) | The PCC Manager is part of the SessMgr process. All PCC Managers will have all the Active PCC Policy Services configured and will be identical in configuration and capabilities. The PCC Manager function manages all the sessions and forms the main block of IPCF functionality which is making authorization decisions. At its core is the rules engine that acts on the user defined policy profiles; i.e. rules to generate the policy and charging decision applicable to a subscriber's usage towards an application service. Along with the PCC processing logic, the PCC-Mgr co-hosts the Gx-API and Rx-API modules. It includes the following capabilities:
> • | It runs the Gx/Gxa protocol stack
> • | handles the IP-CAN associations
> • | Provides nodal functions for Gx/Gxa/Rx interface with PCEF/BBERF/AF.
> Important: For ASR 5000s with session recovery enabled, this manager is usually established on one of the CPUs on the 1st active PSC. The PCCMGRs should not be started on a PSC which has the PCC BINDMUX MGR started. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> SPR Manager (SPRMgr) | The SPR Manager is part of AAAMgr process and manages the transactions towards an external SSC/SPR node over Sp interface. The Sp interface is based on Sh protocol interface. The SPRMgr abstracts the Sp interactions required for the PCC functions. Important: For more information, refer AAAMgr section of this table. | Active PSC | Active PSC (see NOTE) | 0 | Any (see NOTE)
> SGSN GPRS Tunneling Protocol Control message Manager (SGTPCMgr) | Created by the Session Controller for each VPN context in which an SGSN service is configured, the SGTPC Manager task performs the following functions:
> • | Terminates Gn/Gp and GTP-U interfaces from peer GGSNs and SGSNs for SGSN Services.
> • | Terminates GTP-U interfaces from RNCs for IuPS Services.
> • | Controls standard ports for GTP-C and GTP-U.
> • | Processes and distributes GTP-traffic received from peers on these ports.
> • | Performs all node level procedures associated with Gn/Gp interface.
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active demux PSC. The IMSIMgr will not start on a PSC in which SessMgrs are already started. | Active PSC | Active Demux PSC (see NOTE) | 0 | Any (see NOTE)
> SGSN Master Manager (MMgr) | MMgr is created upon provisioning of SS7RDs/SCCP-NWs/etc., The Session Controller provides the initial system configuration which includes a detailed description of each distributed protocol layer, its resources sets, and a list of its service user protocol layers and service provider protocol layers. The MMgr task runs in duplex mode (active/standby) to perform the following functions:
> • | Single instanced
> • | Handles nodal SS7, Iu, and Gb functionality.
> • | Implements master LinkMgr functionality for SS7 route status aggregation.
> • | Implements master LinkMgr functionality for RNC and BSC status aggregation.
> Important: For ASR 5000s with session recovery enabled, this demux manager is usually established on one of the CPUs on the 1st active demux PSC. The IMSIMgr will not start on a PSC in which SessMgrs are already started. | Active PSC | Active Demux PSC (see NOTE) | 0 | Any (see NOTE)
> SS7 Link Manager (LinkMgr) | Created by the Session Controller when the first SS7RD (routing domain) is activated, the LinkMgr performs the following functions:
> • | Multi-instanced for redundancy and scaling purposes.
> • | Provides SS7 and Gb connectivity to the platform.
> • | Routes per subscriber signalling across the SS7 (including Iu) and Gb interfaces to the SessMgr.
> | Any Active PSC Not Running an MMgr | Any Active non- demux PSC |  |
> Standard Routing Database (SRDB) | Eight SRDBs are created by the Session Controller when Content Filtering in the Enhanced Charging Service is enabled. A minimum of two PSCs or PSC2s are required to initiate these eight tasks. SRDB performs the following functions:
> • | The SRDB task receives the static database from the session controller. Each SRDB task loads two database volumes (one primary and one secondary). The SRDB task also stores the static DB.
> • | The SRDB task rates the URL. It returns the proper category of the URL depending on the DB volumes and CSI (category set Index) stored on it.
> • | The SRDB tasks perform peer loading in case its peer fails. If both the SRDB task and its peer fail, the session controller performs the loading.
> | Peer SRDBs evenly distributed across PSCs |  |  |

> ‌
> ASR 5000 Platform Processes

> Task | Description | Card | CPU
> |  | w/o SR | w/ SR | w/o SR | w/ SR
> Card-Slot-Port Controller (CSPCTRL) | Manages physical chassis components. | SMC | SMC | 0 | 0
> Messenger Daemon (MSGD) | Implements the Name Service and related functions for the internal message passing system. | All | All | All | All
> Name Service Controller (NSCONTROL) | As part of the Messenger process, NSControl provides a reliable channel for tasks to send control messages to the Messenger Daemon. | All | All | All | All
> Daughter Card Controller (DCARDCTRL) | The daughter card controller spawns daughter card managers during system initialization and monitors daughter card managers during system steady state execution. The daughter card controller spawns daughter card managers in case a daughter card manager task fails. | Active SMC | Active SMC | 0 | 0
> Daughter Card Manager (DCARDMGR) | The daughter card manager is responsible for managing IPsec Security Associations for AH and ESP based sessions. The daughter card manager is also responsible for interfacing to the on-board hardware accelerated cryptographic chip which executes cryptographic algorithms associated with the given IPsec Security Associations. | All PSCs | All PSCs | 0 | 0
> Distributed Host Manager (DHMGR) | Started automatically on each CPU by SITPARENT. Coordinates establishment of locally terminated TCP, SCTP, and UDP connections on behalf of multi-instanced tasks such as Diameter endpoints among SESSMGR tasks. | All | All | All | All
> Driver Controller (DRVCTRL) | The driver controller centralizes accesses to many of the system device drivers. It also performs temperature and voltage monitoring. | SMCs | SMCs | 0 | 0
> Hard Drive Controller (HDCTRL) | The hard drive controller controls/manages the RAID 1 array spanning the SMCs. | SMCs | SMCs | 0 | 0
> IPSec Controller (IPSECCTRL) | The IPSec controller is started by SIT on system startup regardless of configuration and performs the following functions:
> • | Starts IPSECMGR tasks based on configuration and maintains its list for task recovery.
> • | Receives and maintains user configuration for IPSec.
> • | Manages the configured IPSec crypto maps and its assignment to IPSECMGRs.
> • | Interfaces with the VPNMGR task for required IPSec configuration parameters such as IP Access-lists, IP pools, interface addresses, and interface state notifications.
> | Active SMC | Active SMC | 0 | 0
> IPSec Manager (IPSECMGR) | Created by the Session Controller, the IPSECMGR establishes and manages secure IKEv1, IKEv2 and IPSec data tunnels. | PSC | PSC | All | All
> Recovery Control Task (RCT) | Monitors tasks/managers/facilities across the system and performs recovery in the event of a failure. | SMCs | SMCs | 0 | 0
> Shared Configuration Task (SCT) | Performs the redundant storage of configuration information and other state information in an in-memory database. | SMCs | SMCs | 0 | 0
> Switch Fabric Task (SFT) | The switch fabric task monitors the switch fabric and the gigabit Ethernet control plane. | PSCs | PSCs | 0 | 0
> Utilities Configuration Manager (UCM) | DHCPD, DNS, FTPD, INETD, NTPD, PING, RLOGIN, SFTPD, SFTP-SERVER, SNMPD, SSH, SSHD, TELNET, TELNETD, TFTPD, TRACEROUTE | Active SMC | Active SMC | 0 | 0

> ‌
> ASR 5000 Management Processes

> Task | Description | Card | CPU
> |  | w/o SR | w/ SR | w/o SR | w/ SR
> Bulk Statistic Manager (BULKSTAT) | Performs a periodic statistic polling/gathering function (bulk statistics) and handles the transfer of this data to external management systems. | Active SMC | Active SMC | 0 | 0
> Event Log Daemon (EVLOGD) | Handles event logging functions including the interface to external syslogd servers and the internal event logs. | Active SMC | Active SMC | 0 | 0
> ORB Service (ORBS) | The ORBS task is also known as the ORB Element Manager (ORBEM). Application Servers (EMS) request ORBS to perform Element Management Functions on the system using secure IIOP. ORBS then interacts with concerned Controller Tasks to execute the function. The response/errors from the execution is interpreted, formulated into EMF response, and handed over to Application Server (EMS). | Active SMC | Active SMC | 0 | 0
> ORB Notification Service (ORBNS) | The ORBNS task performs the following functions:
> • | There are different types of event that can continually occur within Boxer.
> • | The Application Servers (EMS) may be notified of occurrences of these events.
> • | Such Application Servers (EMS) may register with ORBS (ORBEM) subscribing to the types of events they are interested in.
> • | As the events occur, the concerned Controller Task notifies ORBS (ORBEM), which then notifies the subscribing Application Servers (EMS).
> | Active SMC | Active SMC | 0 | 0
> Session Trace Collection Task (SESSTRC) | The session trace task implements the standards-based session trace functionality. The session trace task manages both CLI and signaling-based subscriber traces. It collects messages to be traced and generates trace files as needed. It uploads trace files to the Trace Collection Entity as needed. | Active SMC | Active SMC | 0 | 0
> Simple Network Management Protocol (SNMP) | Handles inboard SNMP operations if configured, and sends SNMP notifications (traps) if enabled. | Active SMC | Active SMC | 0 | 0
> Threshold Server (THRESHOLD) | Handles monitoring of threshold crossing alerts, if configured. Polls the needed statistics/variables, maintains state, and generates log messages/SNMP notification of threshold crossings. | Active SMC | Active SMC | 0 | 0

> ‌

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883