Cisco ASR 5500 System Administration Manual page 350

Session Subsystem
Task Description
acsctrl Active Charging System (ACS)
Controller
acsmgr Active Charging System (ACS)
Controller
cdrmod Charging Detail Record
Module
dgmbmgr Diameter Gmb interface
Application Manager
diamproxy Diameter Proxy
ASR 5500 System Administration Guide, StarOS Release 21.5
324
Function
Active Charging service is defined at the global level and can be utilized
through CSS commands from any VPN context. Enable via the Global
Configuration mode active-charging service CLI command.
The ACS controller runs on the primary packet processing card and is
responsible for managing the ACS service.
Reads and writes ACS configuration information into SCT.
The ACS Controller monitors the ACS Manager's recovery process and
performs cleanup when redundancy is enabled.
Created by ACS Controller to perform IP session processing for a specific
number of flows.
Sends and receives data through Session Managers.
Active/Standby acsmgr tasks are created when session recovery (SR) is
enabled.
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.
Provides Multimedia Broadcast/Multicast Service (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.
Handles the Gmb interface over a Diameter connection to a BMSC Server
for MBMS bearer sessions. dgmbmgr recovers by polling all sessmgrs for
MBMS session states and recreating the MBMS UE and MBMS bearer
context information.
Created by diactrl (which runs as part of vpnctrl) 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
packet processing cards. When multiple proxies are configured, one
diamproxy task is run per packet processing card.
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 (does not maintain any queues).
A single Diameter proxy is used to service multiple Diameter applications.
StarOS Tasks