Cisco Cisco ASR 5000
GMM-SM Event Logging
▀ Feature Description
▄ SGSN Administration Guide, StarOS Release 18
for authentication, only sync and mac failures will be logged if they are present - otherwise, the value
will be left blank.
C5:
cause is present only for activate-reject or modify-reject
deactivation will always have a cause
activate-accept might have a cause sent (e.g., single address bearers only allowed)
EDR Storage
The EDRs are stored in CSV format on an external server. The external server relieves the SGSN of the storage
overhead and the post-processing overhead while the SGSN continues to perform call processing.
overhead and the post-processing overhead while the SGSN continues to perform call processing.
Architecture
The primary components of the feature architecture include:
Session Manager (SessMgr) - reports events to the CDRMOD
CDRMOD - stores EDR file in RAMDisk
HardDisk Controller - transfers EDR files from RAMDisk to hard disk
Limitations
The reliability of event generation is limited by the CDRMOD framework, specifically:
Any SessMgr death will result in the loss of event records that are not yet released to the CDRMOD.
Any death of the CDRMOD proclet will result in the loss of records that are not yet written to the RAMDisk.
Any reboot of the chassis will result in the loss of records that are not yet flushed to the hard disk or to an
external server.
In the case of overload of the CDRMOD, the SessMgr will ignore event records when its queue is full.
The IMSI of the subscriber should be available while generating the EDR. Procedures which couldn't be
associated with any particular IMSI will not generate EDRs, for example, the inter-SGSN-RAU being rejected
because of its inability to contact the old-SGSN.
because of its inability to contact the old-SGSN.