Cisco Cisco ASR 5700 Fehlerbehebungsanleitung

This document describes specific scenario where Gateway-Gprs Support Node (GGSN) Call Data
records(G-CDRs) are stuck due to wrong configuration in Access Point Name(APN) results in
wrong billing for subscribers and Charging Gateway Function(CGF) receives backdated CDRs
which are stuck in GGSN. This issue is reported in Cisco Aggregrated Service routers (ASR) 5x00
series.

Because of various reasons(Most probably misconfigurations) for some APNs , CDRs go to
 default group. In default group, we do not have CGF servers configured and hence the requests
get stuck.

 for example :

In Show support details output, check for the command output

Current aaa acct archived shows 6 million CDRs are stuck in all aaamgrs and due to which no
new CDRs get processed and transferred to CGF in streaming mode.

Once the Limit is reached per aaamgr, CDRs are purged and results in loss of CDRs and revenue
loss to customer.

out of 6 million CDRs archived , you see some CDRs being purged

Here is the check lists of CLI commands commonly used to debug CDR related issues.

Method of Procedure(MOP) to clean up the CDRs that belong to Default group in aaaproxy
process.

Step 1. Note down the archived CDRs. Show gtpp counters all

Step 2. Configure the mode to local in gaggsnctx config context gaggsnctx gtpp group default