- TID/IMSI/MSISDN-Based Conditionally Triggered Debugging
- debug condition calling
- debug data-store
- debug data-store detail
- debug diameter
- debug ggsn quota-server
- debug gprs category fsm event
- debug gprs dcca
- debug gprs dfp
- debug gprs dhcp
- debug gprs gtp
- debug gprs gtp parsing
- debug gprs gtp ppp
- debug gprs gtp ppp-regeneration
- debug gprs radius
- debug gprs redundancy
Debug Commands
The commands in this section are for troubleshooting the GGSN. For information about other debug commands, see the Cisco IOS Debug Command Reference.
Because debugging output is assigned high priority in the CPU process, it can diminish the performance of the router or even render it unusable. For this reason, use
debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use
debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased
debug command processing overhead will affect system use.
This chapter contains the following section and commands:
•TID/IMSI/MSISDN-Based Conditionally Triggered Debugging
•debug gprs category fsm event
•debug gprs gtp ppp-regeneration
TID/IMSI/MSISDN-Based Conditionally Triggered Debugging
When the TID/IMSI/MSISDN-based conditionally triggered debugging feature is enabled, the GGSN generates debugging messages for PDP contexts that match a particular tunnel ID (TID), International Mobile Subscriber Identity (IMSI) value, or Mobile Station ISDN number (MSISDN) entering or leaving the GGSN. The GGSN will not generate debugging output for PDP contexts containing a different TID, IMSI, or MSISDN value.
Normally, the GGSN will generate debugging messages for every PDP context, resulting in a large number of messages that consume system resources and can make it difficult to find the specific information you need. By limiting the number of debugging messages, you can receive messages related to only to PDP contexts you want to troubleshoot.
Usage Guidelines for TID/IMSI/MSISDN-Based Conditional Debugging
Use the following guidelines when configuring TID/IMSI/MSISDN-based conditional debugging on a GGSN.
1. Before enabling a debug gprs command, first enable TID/IMSI/MSISDN-based debugging using the debug condition calling command. Ensure that the TID/IMSI or MSISDN string match the ones from the Create Request.
For examples:
For a create request with TID 12345678090000B0, you would enter:
GGSN# debug condition calling 12345678090000B0
Condition 1 set
GGSN#
For a create request with IMSI 21436579000000, you would enter:
GGSN# debug condition calling 21436579000000
Condition 2 set
GGSN#
For a create request with MSISDN 1112223344, you would enter:
GGSN# debug condition calling msisdn-1112223344
Condition 3 set
GGSN#
To verify the set conditions, enter:
GGSN# show debug condition all
Condition 1: calling 12345678090000B0 (0 flags triggered)
Condition 2: calling 21436579000000 (0 flags triggered)
Condition 3: calling 1112223344 (0 flags triggered)
GGSN#
2. After turning on TID, IMSI, or MSISDN-based debugging, turn on GPRS debugging by entering the debug gprs gtp and/or debug gprs charging commands.
Once this step is completed, when PDP Context Create Requests are received, the GGSN will display debug messages for those create requests with either a matching TID, IMSI, or MSISDN.
3. Because the no debug all command does not disable conditional debug flags, to ensure that you do not receive a flood of debugging messages when disabling debugging, turn off GPRS debug flags first using the no debug all command as follows:
GGSN# no debug all
All possible debugging has been turned off
GGSN#
GGSN# show debug condition all
Condition 1: calling 12345678090000B0 (1 flags triggered)
Condition 2: calling 21436579000000 (1 flags triggered)
Condition 3: calling 1112223344 (1 flags triggered)
GGSN#
4. Disable the conditional debug flags using the no debug condition all command:
GGSN# no debug condition all
Removing all conditions may cause a flood of debugging messages to result, unless specified debugging flags are first removed.
Proceed with the removal of all conditions [yes/no] y
2 conditions have been removed
5. Verify that the conditional debug flags have been removed using the show debug condition all command:
GGSN# show debug condition all
% No conditions found
debug condition calling
To limit output for some debug commands based on specified conditions, use the debug condition command in privileged EXEC mode. To remove the specified condition, use the no form of this command.
debug condition {username username | called dial-string | caller dial-string | vcid vc-id | ip ip-address | calling [tid | imsi | msisdn-msisdn]}
no debug condition {condition-id | all}
Syntax Description
Defaults
No default behavior or values.
Command History
Usage Guidelines
Ensure that you enable TID/IMSI/MSISDN-based conditional debugging using the debug condition calling command before configuring the debug gprs gtp and debug gprs charging. In addition, ensure that you disable the debug gprs gtp and debug gprs charging commands using the no debug all command before disabling conditional debugging using the no debug condition command. This will prevent a flood of debug messages when you disable conditional debugging.
Note Conditional debugging does not apply to debug gprs gtp events, debug gprs gtp messages, or debug gprs gtp packets. For debug gprs gtp parsing, the conditional debugging starts to limit its output only after the PDP context is created (the TID value is not empty).
For more information on using the GGSN TID/IMSI/MSISDN-based conditional debugging, see "TID/IMSI/MSISDN-Based Conditionally Triggered Debugging" section.
Examples
Example 1
The following examples configure a conditional debug session based on a TID 12345678090000B0, IMSI 21436579000000, and MSISDN 408525823010:
GGSN# debug condition calling 12345678090000B0
Condition 1 set
GGSN#
GGSN# debug condition calling 21436579000000
Condition 2 set
GGSN#
GGSN# debug condition calling msisdn 408525823010
Condition 3 set
GGSN#
Example 2
The following example stops all conditional debugging:
Router# no debug conditional all
All possible debugging has been turned off
Router#
debug data-store
To display PSD related debugging messages for the gateway GPRS support node (GGSN), use the debug data-store command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug data-store
no debug data-store
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays PSD-related debugging messages for the GGSN.
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use
debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use
debug commands during periods of lower network flows and fewer users. Debugging during these periods reduces the effect these commands have on other users on the system.
Examples
The following example configures a debugging session to check PSD-related parameters:
Router# debug data-store
debug data-store detail
To display extended details for PSD related debugging information, use the debug data-store detail command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug data-store detail
no debug data-store detail
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays PSD-related debugging messages for the GGSN.
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use
debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use
debug commands during periods of lower network flows and fewer users. Debugging during these periods reduces the effect these commands have on other users on the system.
Examples
The following example configures a detailed PSD-related debugging session:
Router# debug data-store details
debug diameter
To display information about Diameter processing on the gateway GPRS support node (GGSN), use the debug diameter command in privileged EXEC mode.
debug diameter {dcca | connection | error | packet | event | fsm | failover | all}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with Diameter processing.
Examples
The following configuration example displays Diameter-related events:
debug diameter event
debug ggsn quota-server
To display debug information related to quota server processing on the GGSN, use the debug ggsn quota-server privileged EXEC command.
debug ggsn quota-server [detail | packets [dump] | events | parsing | errors]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with communication between the GGSN quota server process and the CSG.
Examples
The following example enables the display of detailed quota server processing debug output—pre-allocated quota and quota push:
Router#debug ggsn quota-server detail
ggsn quota-server details debugging is on
Router#
Jun 2 02:40:39.391: GGSN-QS:Encoding QUOTA PUSH REQUEST
Jun 2 02:40:39.391: GGSN-QS:Adding TLV USER_INDEX
Jun 2 02:40:39.391: GGSN-QS: IP Address: 3.3.3.1 User ID: 12345
Jun 2 02:40:39.391: GGSN-QS:Adding TLV SERVICE_ID: 1
Jun 2 02:40:39.391: GGSN-QS:Adding TLV QUADRANS_GRANTED
Jun 2 02:40:39.391: GGSN-QS: Quadrans: 1250 Threshold: 1000 Units: SECONDS
Jun 2 02:40:39.391: GGSN-QS:Adding TLV QUADRANS_GRANTED
Jun 2 02:40:39.391: GGSN-QS: Quadrans: 5000 Threshold: 5000 Units: BYTES_IP
Jun 2 02:40:39.391: GGSN-QS:Adding TLV TIMEOUT: 50000
Jun 2 02:40:39.391: GGSN-QS:Adding TLV TARIFF_TIME: 1147698000
Jun 2 02:40:39.391: GGSN-QS:Sending QUOTA_PUSH_REQ from QS (4.4.4.4:3386) to CSG (30.1.1.1:3386)
Jun 2 02:40:39.395: pak=0x6523B5B0, datagramstart=0x200143D8, network_start=0x200143BC datagramsize 91
Jun 2 02:40:39.395: GGSN-QS msgtype 0xF0, seq 1, len 85, from 4.4.4.4:3386 to 30.1.1.1:3386
200143D0: 0FF00055 00017E01 .p.U..~.
200debug ggsn quota-server detail143E0: FC005001 31000000 4A002E00 46001400 |.P.1...J...F...
200143F0: 09030303 01313233 34350015 00013100 .....12345....1.
20014400: 2D000E00 00000000 0004E201 03000003 -.........b.....
20014410: E8002D00 0E000000 00000013 88020300 h.-.............
20014420: 00138800 17000400 00C35000 4D000444 .........CP.M..D
20014430: 687B50 h{P
Jun 2 02:40:39.395: GGSN-QS:Received Data Record Transfer Response from (30.1.1.1:3386) Sequence number 1
Jun 2 02:40:39.395: GGSN-QS:Cause = 128
Jun 2 02:40:39.395: GGSN-QS:Request Responded Sequence Number = 1
Jun 2 02:40:39.395: GGSN-QS:Private Ext IE length 32 QM Rsp length 29
Jun 2 02:40:39.395: GGSN-QS:Received message QUOTA_PUSH_RESP from CSG
Jun 2 02:40:39.395: GGSN-QS:UserIndex TLV: IP Address 3.3.3.1 UserName/MSISDN 12345
Jun 2 02:40:39.395: GGSN-QS:Session ID TLV: 1736898353
Jun 2 02:40:39.395: GGSN-QS:Service ID TLV: 1
Jun 2 02:40:39.399: GGSN-QS:Detected real CSG 30.1.1.1 for virtual CSG 30.1.1.1
Jun 2 02:40:39.399: GGSN-QS:real CSG newly detected
ggsn quota-server details debugging is on
Router#
debug gprs category fsm event
To display debug information related to service-aware GGSN category events, and state transactions, use the debug gprs category fsm event privileged EXEC command.
debug gprs category fsm event
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with eGGSN processing.
Examples
Example 1—PDPs with Pre-Allocated Quota
The following example enables the display of eGGSN events and state transactions—pre-allocated quota. This is PDP context create, prepaid user data transfer, and then context teardown.
PDP Context Create:
Router#debug gprs category fsm event
eGGSN category fsm event debugging is on
Router#
Jun 2 02:55:08.491: GPRS:1234050000000010:created service-aware subblock
Jun 2 02:55:11.383: GPRS:1234050000000010:it is the only one PDP of the user, need CCR msg
Jun 2 02:55:11.383: GPRS:1234050000000010:sent ccr_init
Jun 2 02:55:11.823: GPRS:1234050000000010:create new category 1
Jun 2 02:55:11.823: GPRS:1234050000000010:shdb 0xFB00001C created for category 1 (handle 0x8C000007)
Jun 2 02:55:11.823: GPRS:1234050000000010:successfully create a category
Jun 2 02:55:14.623: GPRS:1234050000000010:created sync_object for CREATE_PDP
Jun 2 02:55:14.623: GPRS:1234050000000010:get 1 impacted categories into sync_object for CREATE_PDP
Jun 2 02:55:14.623: GPRS:1234050000000010:insert category 1 from sync_object for CREATE_PDP
Jun 2 02:55:14.623: GPRS:1234050000000010:number of really impacted by CREATE_PDP = 1
Jun 2 02:55:14.623: GPRS:1234050000000010:FSM_ggsn_rcvd_quota
Jun 2 02:55:14.623: GPRS:1234050000000010:category 1 trans from INIT to PENDING QP on event CCA_QUOTA
Jun 2 02:55:14.627: GPRS:1234050000000010:FSM_ggsn_rcvd_qp_ack_in_qp
Jun 2 02:55:14.627: GPRS:1234050000000010:remove category 1 from sync_object for CREATE_PDP 0 still pending in the sync_object
Jun 2 02:55:14.627: GPRS:1234050000000010:send Create PDP Context Res to SGSN
Jun 2 02:55:14.627: GPRS:1234050000000010:delete sync object for CREATE_PDP, it has 0 categories
Jun 2 02:55:14.627: GPRS:1234050000000010:category 1 trans from PENDING QP to AUTHORIZED on event CSG_QP_ACK
Router#
Router#
PDP Context Delete:
Router#
Jun 2 02:55:31.455: GPRS:1234050000000010:look up category by 1 found 65EEB128
Jun 2 02:55:31.455: GPRS:1234050000000010:FSM_ggsn_rcvd_stop
Jun 2 02:55:31.455: GPRS:category 1 report usage queue size = 2
Jun 2 02:55:31.455: GPRS:1234050000000010:usage unit has total_octets 0
Jun 2 02:55:31.455: GPRS:1234050000000010:usage unit has total_octets 300
Jun 2 02:55:31.455: GPRS:1234050000000010:category 1 , usage 6615E470
Jun 2 02:55:31.455: GPRS:1234050000000010:no sync_object for service stop
Jun 2 02:55:31.455: %GPRSFLTMG-4-CHARGING: GSN: 0.0.0.0, TID: 0000000000000000, APN: NULL, Reason: 1, unexpected CSG usage report cause
Jun 2 02:55:31.455: GPRS:1234050000000010:send CCR_UPDATE to DCCA server return ok
Jun 2 02:55:31.455: GPRS:releasing 2 usages in category
Jun 2 02:55:31.455: GPRS:release_usage_parameter
Jun 2 02:55:31.455: GPRS:1234050000000010:category 1 trans from AUTHORIZED to IDLE on event CSG_SERVICE_STOP
Jun 2 02:55:34.939: GPRS:1234050000000010:eggsn_get_final_usage_report
Jun 2 02:55:34.939: GPRS:1234050000000010:freeing all categories
Jun 2 02:55:34.939: GPRS:1234050000000010:delete_category 1
Jun 2 02:55:34.939: GPRS:1234050000000010:freeing service-aware subblock
Router#
Example 2—PDPs without Pre-Allocated Quota
The following example enables the display of eGGSN events and state transactions—for PDPs without pre-allocated quota.
PDP Context Create:
Router#debug gprs category fsm event
eGGSN category fsm event debugging is on
Router#
Jun 2 02:58:45.727: GPRS:1234050000000010:created service-aware subblock
Jun 2 02:58:48.623: GPRS:1234050000000010:it is the only one PDP of the user, need CCR msg
Jun 2 02:58:48.623: GPRS:1234050000000010:sent ccr_init
Router#
PDP Context Delete:
Router#
Jun 2 02:59:06.975: GPRS:1234050000000010:eggsn_get_final_usage_report
Jun 2 02:59:06.975: GPRS:1234050000000010:freeing all categories
Jun 2 02:59:06.975: GPRS:1234050000000010:freeing service-aware subblock
Router
debug gprs dcca
To display troubleshooting information about Diameter Credit Control Application (DCCA) processing on the gateway GPRS support node (GGSN), use the debug gprs dcca privileged EXEC command.
debug gprs dcca
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful for system operators and development engineers if Diameter protocol problems are encountered on the GGSN.
Examples
Example 1
The following is a sample of DCCA debug information with pre-allocated quota.
Router#debug gprs dcca
Router#
Jun 2 03:13:45.827: GPRS:1234050000000010:GPRS:DCCA: 3GPP-IMSI : 214350000000000
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-Charging-Id : 613053186
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-PDP-Type : 0
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-CG-Address : 20.1.1.1
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-QoS-Profile : 99-0911012964FFFF1100FFFF
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-SGSN-Address : 11.20.1.1
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-GGSN-Address : 10.20.61.1
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-IMSI-MCC-MNC : 21435
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-GGSN-MCC-MNC : 001002
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-NSAPI : 1
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS:DCCA: 3GPP-Selection-Mode : 0
Jun 2 03:13:45.831: GPRS:1234050000000010:3GPP-Charging-Char : 0100
Jun 2 03:13:45.831: GPRS:1234050000000010:GPRS DCCA: Starting Tx timer , value = 100000
Jun 2 03:13:45.831: GPRS:1234050000000010:DCCA FSM:Event = CCR_INITIAL, Old State = IDLE, New State = PENDING_I
Jun 2 03:13:46.287: GPRS:1234050000000010:GPRS DCCA: Result-Code = 2001
Jun 2 03:13:46.287: GPRS:1234050000000010:GPRS DCCA: Stopping Tx timer
Jun 2 03:13:46.287: GPRS:1234050000000010:GPRS DCCA: Result-Code for Category : 1 = 2001
Jun 2 03:13:46.287: GPRS:1234050000000010:DCCA FSM:Event = CCA_SUCCESS, Old State = PENDING_I, New State = OPEN
Router#
Router#show gprs gtp pdp tid 1234050000000010 ser all
Diameter Credit Control: Enabled
Current Billing status: Prepaid
Reason to convert to postpaid: N/A
Charging Profile Index: 1
DCCA profile name: dcca-profile1, Source: charging profile
Rule base id: 1, Source: DCCA server
ServiceID State Quota(octets)
1 AUTHORIZED 5000
Router#
PDP being deleted
Example 2
The following is a sample of DCCA debug information without pre-allocated quota.
Router#show debug
GPRS:
GPRS DCCA Events debugging is on
Router#
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-IMSI : 214350000000000
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-Charging-Id : 613053181
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-PDP-Type : 0
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-CG-Address : 20.1.1.1
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-QoS-Profile : 99-0911012964FFFF1100FFFF
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-SGSN-Address : 11.20.1.1
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-GGSN-Address : 10.20.61.1
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-IMSI-MCC-MNC : 21435
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-GGSN-MCC-MNC : 001002
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-NSAPI : 1
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS:DCCA: 3GPP-Selection-Mode : 0
Jun 2 03:05:07.743: GPRS:1234050000000010:3GPP-Charging-Char : 0100
Jun 2 03:05:07.743: GPRS:1234050000000010:GPRS DCCA: Starting Tx timer , value = 100000
Jun 2 03:05:07.743: GPRS:1234050000000010:DCCA FSM:Event = CCR_INITIAL, Old State = IDLE, New State = PENDING_I
Jun 2 03:05:08.167: GPRS:1234050000000010:GPRS DCCA: Result-Code = 2001
Jun 2 03:05:08.167: GPRS:1234050000000010:GPRS DCCA: Stopping Tx timer
Jun 2 03:05:08.167: GPRS:1234050000000010:DCCA FSM:Event = CCA_SUCCESS, Old State = PENDING_I, New State = OPEN
Router#
gprs5-72b#sgpt 1234050000000010 ser all
Diameter Credit Control: Enabled
Current Billing status: Prepaid
Reason to convert to postpaid: N/A
Charging Profile Index: 1
DCCA profile name: dcca-profile1, Source: charging profile
Rule base id: 1, Source: DCCA server
ServiceID State Quota(octets)
gprs5-72b#clear gprs gtp pdp all
PDP deleted
Router#
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-IMSI : 214350000000000
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-Charging-Id : 613053181
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-PDP-Type : 0
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-CG-Address : 20.1.1.1
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-QoS-Profile : 99-0911012964FFFF1100FFFF
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-SGSN-Address : 11.20.1.1
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-GGSN-Address : 10.20.61.1
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-IMSI-MCC-MNC : 21435
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-GGSN-MCC-MNC : 001002
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-NSAPI : 1
Jun 2 03:05:28.459: GPRS:1234050000000010:GPRS:DCCA: 3GPP-Selection-Mode : 0
Jun 2 03:05:28.459: GPRS:1234050000000010:3GPP-Charging-Char : 0100
Jun 2 03:05:28.463: GPRS:1234050000000010:GPRS DCCA: Stopping Tx timer
Jun 2 03:05:28.463: GPRS:1234050000000010:DCCA FSM:Event = CCR_FINAL, Old State = OPEN, New State = PENDING_T
Jun 2 03:05:28.463: GPRS:1234050000000010:GPRS DCCA: Stopping Tx timer
Jun 2 03:05:28.871: GPRS:GPRS DCCA: DCCA request was cancelled, Droping AAA reply
Router#
Router#sgpt 1234050000000010 ser all
%ERROR: Cannot find the PDP
Router#
debug gprs dfp
To display debug messages for GPRS DFP weight calculation, use the debug gprs dfp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug gprs dfp
no debug gprs dfp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Usage Guidelines
See the following caution before using debug commands:
Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use
debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use
debug commands during periods of lower network flows and fewer users. Debugging during these periods reduces the effect these commands have on other users on the system.
This command displays debug messages for GPRS DFP weight calculation. To display debug messages for the DFP agent subsystem, use the debug ip dfp agent command.
Examples
The following example configures a debug session to check all GPRS DFP weight calculation:
Router# debug gprs dfp
GPRS DFP debugging is on
Router#
The following example stops all debugging:
Router# no debug all
All possible debugging has been turned off
Router#
debug gprs dhcp
To display information about Dynamic Host Configuration Protocol (DHCP) processing on the gateway GPRS support node (GGSN), use the debug gprs dhcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug gprs dhcp
no debug gprs dhcp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with DHCP processing on the GGSN. To display standard debug messages between the DHCP client on the router and a DHCP server, you can also use the debug dhcp or debug dhcp detail commands with the debug gprs dhcp command.
Because the
debug gprs dhcp command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.
Examples
The following example shows sample output for DHCP processing on the GGSN:
Router# debug gprs dhcp
2d13h: GPRS:DHCP req:TID 1111111100000099, Req 1
2d13h: GPRS:Requesting IP address for pdp 1111111100000099 from server 172.16.0.8 tableid 0
2d13h: GPRS:DHCP ip allocation pass (10.88.17.43) for pdp 1111111100000099
2d13h: GPRS:Using DHCP ip address 10.88.17.43 for pdp 1111111100000099
The following example shows sample output for standard debug messaging for DHCP processing on the router between the DHCP client and a DHCP server:
2d13h: DHCP: proxy allocate request
2d13h: DHCP: new entry. add to queue
2d13h: DHCP: SDiscover attempt # 1 for entry:
2d13h: DHCP: SDiscover: sending 283 byte length DHCP packet
2d13h: DHCP: SDiscover with directed serv 172.16.0.8, 283 bytes
2d13h: DHCP: XID MATCH in dhcpc_for_us()
2d13h: DHCP: Received a BOOTREP pkt
2d13h: DHCP: offer received from 172.16.0.8
2d13h: DHCP: SRequest attempt # 1 for entry:
2d13h: DHCP: SRequest- Server ID option: 172.16.0.8
2d13h: DHCP: SRequest- Requested IP addr option: 10.88.17.43
2d13h: DHCP: SRequest placed lease len option: 604800
2d13h: DHCP: SRequest: 301 bytes
2d13h: DHCP: SRequest: 301 bytes
2d13h: DHCP: XID MATCH in dhcpc_for_us()
2d13h: DHCP: Received a BOOTREP pkt
2d13h: DHCP Proxy Client Pooling: ***Allocated IP address: 10.88.17.43
Related Commands
|
|
|
|---|---|
debug dhcp |
Displays debug messages between the DHCP client on the router and a DHCP server. |
debug gprs gtp
To display information about the GPRS Tunneling Protocol (GTP), use the debug gprs gtp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug gprs gtp {events | messages | packets}
no debug gprs gtp {events | messages | packets}
Syntax Description
Defaults
No default behavior or values.
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with communication between the GGSN and the SGSN using GTP.
Because the
debug gprs gtp command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.
Examples
The following example enables the display of events related to GTP processing on the GGSN:
Router# debug gprs gtp events
The following example enables the display of GTP signaling messages:
Router# debug gprs gtp messages
The following example enables the display of GTP packets sent between the SGSN and GGSN:
Router# debug gprs gtp packets
The following example enables the display of GTP PPP events between the SGSN and GGSN:
Router# debug gprs gtp ppp events
The following example enables the display of detailed GTP PPP debug output along with GTP PPP events between the SGSN and GGSN:
Router# debug gprs gtp ppp details
Router# debug gprs gtp ppp events
debug gprs gtp parsing
To display information about the parsing of GPRS Tunneling Protocol (GTP) information elements (IEs) in signaling requests, use the debug gprs gtp parsing command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug gprs gtp parsing
no debug gprs gtp parsing
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Usage Guidelines
This command is useful for system operators and development engineers to verify parsing of GTP IEs in signaling requests that are received by GDM or by the GGSN. If the packet is parsed successfully, you will receive a message along with the TID for the packet as shown in the following example:
GPRS:TID:7300000000000000:Packet Parsed successfully
The debug gprs gtp parsing command can be used to verify GDM or GGSN processing of IEs.
Because the
debug gprs gtp parsing command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.
Examples
The following example enables the display of debug messages that occur while GDM or the GGSN parses GTP IEs:
Router# debug gprs gtp parsing
debug gprs gtp ppp
To display information about PPP PDP type processing on the gateway GPRS support node (GGSN), use the debug gprs gtp ppp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug gprs gtp ppp {events | details}
no debug gprs gtp ppp {events | details}
Syntax Description
events |
Displays messages specific to certain conditions that are occurring during PPP PDP type processing. |
details |
Displays more extensive and lower-level messages related to PPP PDP type processing. |
Defaults
No default behavior or values.
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with PPP PDP type processing on the GGSN.
You can enable both forms of the debug gprs gtp ppp command at the same time, as separate command line entries. The events keyword generates output specific to certain conditions that are occurring, which helps qualify the output being received using the details option.
Because the
debug gprs gtp ppp command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.
Examples
The following debug examples provide sample output for a Create PDP Context request and clear PDP context using PPP PDP type on the GGSN. The examples show output while both debug events and details are enabled on the GGSN.
Example 1
The following example displays details and events output related to PPP PDP context processing for a Create PDP Context requested received by the GGSN:
Router# debug gprs gtp ppp events
GTP PPP events display debugging is on
Router# debug gprs gtp ppp details
GTP PPP details display debugging is on
7200b#
3d23h: GPRS:
3d23h: GTP-PPP Fa1/0: Create new gtp_ppp_info
3d23h: GPRS:
3d23h: GTP-PPP: domain gprs.cisco.com not in any VPDN group
3d23h: GPRS:
3d23h: GTP-PPP: aaa-group accounting not configured under APN gprs.cisco.com
3d23h: GPRS:GTP-PPP: Don't cache internally generated pak's header
3d23h: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
3d23h: GPRS:
3d23h: GTP-PPP Vi2: gtp_ppp_cstate_react changing states
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:
3d23h: GTP-PPP: Vi2: Concat names user00 & gprs.cisco.com
3d23h: GPRS:
3d23h: GTP-PPP: New username after concat: user00@gprs.cisco.com
3d23h: GPRS:
3d23h: GTP-PPP: Vi2: Concat names user00@gprs.cisco.com & gprs.cisco.com
3d23h: GPRS:
3d23h: GTP-PPP: New username after concat: user00@gprs.cisco.com
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:
3d23h: GTP-PPP Vi2: gtp_ppp_protocol_up is notified about intf UP
3d23h: GPRS:
3d23h: GTP-PPP Vi2: PDP w/ MS addr 98.102.0.1 inserted into IP radix tree
Example 2
The following example displays both details and events related to PPP PDP type processing after clearing PDP contexts on the GGSN:
Router# clear gprs gtp pdp-context all
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak
3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 30
3d23h: GPRS:
3d23h: GTP-PPP Vi2: gtp_ppp_pdp_terminate shutting down the vaccess
3d23h: GPRS:
3d23h: GTP-PPP Vi2: gtp_ppp_pdp_shut_va shutting down intf
3d23h: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
3d23h: GPRS:
3d23h: GTP-PPP Vi2: gtp_ppp_cstate_react changing states
3d23h: GPRS:
3d23h: GTP-PPP Vi2: gtp_ppp_free_va resetting intf vectors
3d23h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
debug gprs gtp ppp-regeneration
To display information about PPP regeneration processing on the GGSN, use the debug gprs gtp ppp-regeneration privileged EXEC command. To disable debugging output, use the no form of this command.
debug gprs gtp ppp-regeneration {events | details}
no debug gprs gtp ppp-regeneration {events | details}
Syntax Description
Defaults
No default behavior or values.
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with communication between GDM and a GGSN.
You can enable both forms of the debug gprs gtp ppp-regeneration command at the same time, as separate command line entries. The events keyword generates output specific to certain conditions that are occurring, which helps qualify the output being received using the details option.
Because the
debug gprs gtp ppp-regeneration command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.
Examples
The following debug examples provide sample output for a create PDP context request and clear PDP context using PPP regeneration on the GGSN. The examples show output while both debug events and details are enabled on the GGSN.
Example 1
The following example displays details and events output related to PPP regeneration processing for a create PDP context requested received by the GGSN:
Router# debug gprs gtp ppp-regeneration details
GTP PPP regeneration details display debugging is on
Router# debug gprs gtp ppp-regeneration events
GTP PPP regeneration events display debugging is on
06:24:02: PPP-REGEN state counters: pending counter is 0
06:24:02: State[IDLE] counter is 0
06:24:02: State[AUTHORIZING] counter is 0
06:24:02: State[VPDN CONNECTING] counter is 0
06:24:02: State[PPP NEGOTIATING] counter is 0
06:24:02: State[PPP CONNECTED] counter is 0
06:24:02: State[PPP TERMINATING] counter is 0
06:24:02: PPP-REGEN state counters: pending counter is 1
06:24:02: State[IDLE] counter is 1
06:24:02: State[AUTHORIZING] counter is 0
06:24:02: State[VPDN CONNECTING] counter is 0
06:24:02: State[PPP NEGOTIATING] counter is 0
06:24:02: State[PPP CONNECTED] counter is 0
06:24:02: State[PPP TERMINATING] counter is 0
06:24:02: GPRS:1011111111500001:Authen: PAP username: tomy1@corporate_1.com
06:24:02: GPRS:1011111111500001:Session timer started
06:24:02: GPRS:Processing PPP regen reqQ
06:24:02: GPRS:1011111111500001:Processing Initiate PPP regen from reqQ
06:24:02: GPRS:1011111111500001:got event [REQUEST PPP REGEN] in state [IDLE]
06:24:02: PPP-REGEN state counters: pending counter is 1
06:24:02: State[IDLE] counter is 0
06:24:02: State[AUTHORIZING] counter is 1
06:24:02: State[VPDN CONNECTING] counter is 0
06:24:02: State[PPP NEGOTIATING] counter is 0
06:24:02: State[PPP CONNECTED] counter is 0
06:24:02: State[PPP TERMINATING] counter is 0
06:24:02: GPRS:1011111111500001:state [IDLE->AUTHORIZING] on event [REQUEST PPP REGEN]
06:24:02: GPRS:1011111111500001:Got VPN authorization info
06:24:02: GPRS:1011111111500001:got event [AUTHOR SUCCESS] in state [AUTHORIZING]
06:24:02: PPP-REGEN state counters: pending counter is 1
06:24:02: State[IDLE] counter is 0
06:24:02: State[AUTHORIZING] counter is 0
06:24:02: State[VPDN CONNECTING] counter is 1
06:24:02: State[PPP NEGOTIATING] counter is 0
06:24:02: State[PPP CONNECTED] counter is 0
06:24:02: State[PPP TERMINATING] counter is 0
06:24:02: GPRS:1011111111500001:state [AUTHORIZING->VPDN CONNECTING] on event [AUTHOR SUCCESS]
06:24:02: GPRS:1011111111500001:Author succeeded, establishing the tunnel
06:24:02: GPRS:1011111111500001:Create/Clone vaccess to negotiate PPP
06:24:02: GPRS:1011111111500001:no need to set NS ppp_config
06:24:02: GPRS:1011111111500001:MS no static IP addr. Get one via IPCP
06:24:02: GPRS:1011111111500001:VPDN to inform PPP regen: CONNECTED
06:24:02: GPRS:1011111111500001:got event [VPDN CONNECTED] in state [VPDN CONNECTING]
06:24:02: PPP-REGEN state counters: pending counter is 1
06:24:02: State[IDLE] counter is 0
06:24:02: State[AUTHORIZING] counter is 0
06:24:02: State[VPDN CONNECTING] counter is 0
06:24:02: State[PPP NEGOTIATING] counter is 1
06:24:02: State[PPP CONNECTED] counter is 0
06:24:02: State[PPP TERMINATING] counter is 0
06:24:02: GPRS:1011111111500001:state [VPDN CONNECTING->PPP NEGOTIATING] on event [VPDN CONNECTED]
06:24:02: GPRS:1011111111500001:Start PPP negotiations on vaccess
06:24:02: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
06:24:02: GPRS:1011111111500001:IPCP is up
06:24:02: GPRS:1011111111500001:LNS allocates 10.100.1.1 for MS
06:24:02: GPRS:1011111111500001:IP addr 10.100.1.1 is negotiated for MS
06:24:02: GPRS:1011111111500001:PPP connected
06:24:02: GPRS:1011111111500001:got event [PPP NEGOTIATED] in state [PPP NEGOTIATING]
06:24:02: PPP-REGEN state counters: pending counter is 0
06:24:02: State[IDLE] counter is 0
06:24:02: State[AUTHORIZING] counter is 0
06:24:02: State[VPDN CONNECTING] counter is 0
06:24:02: State[PPP NEGOTIATING] counter is 0
06:24:02: State[PPP CONNECTED] counter is 1
06:24:02: State[PPP TERMINATING] counter is 0
06:24:02: GPRS:1011111111500001:state [PPP NEGOTIATING->PPP CONNECTED] on event [PPP NEGOTIATED]
06:24:02: GPRS:1011111111500001:PPP succeeded negotiation, session established
06:24:02: GPRS:1011111111500001:Session timer stopped
06:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
Example 2
The following example displays both details and events related to PPP regeneration processing after clearing PDP contexts on the GGSN:
Router# clear gprs gtp pdp-context all
06:28:05: PPP-REGEN state counters: pending counter is 0
06:28:05: State[IDLE] counter is 0
06:28:05: State[AUTHORIZING] counter is 0
06:28:05: State[VPDN CONNECTING] counter is 0
06:28:05: State[PPP NEGOTIATING] counter is 0
06:28:05: State[PPP CONNECTED] counter is 1
06:28:05: State[PPP TERMINATING] counter is 0
06:28:05: GPRS:1011111111500001:PPP regen current state PPP CONNECTED
06:28:05: GPRS:1011111111500001:GTP disconnecting the PPP regen session
06:28:05: GPRS:Processing PPP regen reqQ
06:28:05: GPRS:1011111111500001:Processing Disconnect PPP regen from reqQ
06:28:05: GPRS:1011111111500001:got event [CANCEL REGEN'ED PPP] in state [PPP CONNECTED]
06:28:05: PPP-REGEN state counters: pending counter is 1
06:28:05: State[IDLE] counter is 0
06:28:05: State[AUTHORIZING] counter is 0
06:28:05: State[VPDN CONNECTING] counter is 0
06:28:05: State[PPP NEGOTIATING] counter is 0
06:28:05: State[PPP CONNECTED] counter is 0
06:28:05: State[PPP TERMINATING] counter is 1
06:28:05: GPRS:1011111111500001:state [PPP CONNECTED->PPP TERMINATING] on event [CANCEL REGEN'ED PPP]
06:28:05: GPRS:1011111111500001:Cancel request after VPND tunnel is up
06:28:05: PPP-REGEN state counters: pending counter is 1
06:28:05: State[IDLE] counter is 0
06:28:05: State[AUTHORIZING] counter is 0
06:28:05: State[VPDN CONNECTING] counter is 0
06:28:05: State[PPP NEGOTIATING] counter is 0
06:28:05: State[PPP CONNECTED] counter is 0
06:28:05: State[PPP TERMINATING] counter is 1
06:28:05: GPRS:1011111111500001:PPP down
06:28:05: GPRS:1011111111500001:got event [PPP FAILED] in state [PPP TERMINATING]
06:28:05: PPP-REGEN state counters: pending counter is 1
06:28:05: State[IDLE] counter is 1
06:28:05: State[AUTHORIZING] counter is 0
06:28:05: State[VPDN CONNECTING] counter is 0
06:28:05: State[PPP NEGOTIATING] counter is 0
06:28:05: State[PPP CONNECTED] counter is 0
06:28:05: State[PPP TERMINATING] counter is 0
06:28:05: GPRS:1011111111500001:state [PPP TERMINATING->IDLE] on event [PPP FAILED]
06:28:05: GPRS:1011111111500001:LCP went down
06:28:05: GPRS:1011111111500001:VPDN disconnect
06:28:05: GPRS:1011111111500001:got event [CLEANUP CONTEXT] in state [IDLE]
06:28:05: GPRS:1011111111500001:state [IDLE->IDLE] on event [CLEANUP CONTEXT]
06:28:05: GPRS:1011111111500001:Freeing context structure
06:28:05: GPRS:1011111111500001:VPDN handle invalid, no need to free it
06:28:05: GPRS:1011111111500001:remove PPP regen context from Vi2
06:28:05: GPRS:1011111111500001:Session timer stopped
06:28:05: PPP-REGEN state counters: pending counter is 0
06:28:05: State[IDLE] counter is 0
06:28:05: State[AUTHORIZING] counter is 0
06:28:05: State[VPDN CONNECTING] counter is 0
06:28:05: State[PPP NEGOTIATING] counter is 0
06:28:05: State[PPP CONNECTED] counter is 0
06:28:05: State[PPP TERMINATING] counter is 0
06:28:05: GPRS:1011111111500001:PPP regen context 0x633F196C released
06:28:05: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
06:28:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
debug gprs radius
To display information about Remote Access Dial-In User Service (RADIUS) processing on the gateway GPRS support node (GGSN), use the debug gprs radius command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug gprs radius
no debug gprs radius
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command History
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with communication between a RADIUS server and the GGSN.
Because the
debug gprs radius command generates a significant amount of output, use it only when traffic on the GPRS network is low, so other activity on the system is not adversely affected.
Examples
The following example enables the display of debug messages related to RADIUS processing on the GGSN:
Router# debug gprs radius
debug gprs redundancy
To display debug messages, errors, events, or packets related to GTP session redundancy (GTP-SR), use the debug gprs redundancy privileged EXEC command. To disable debugging output, use the no form of this command.
debug gprs redundancy [debug | errors | events | packets]
no debug gprs redundancy [debug | errors | events | packets]
Syntax Description
debug |
Displays debug messages related to GTP-SR. |
errors |
Displays errors related to GTP-SR. |
events |
Displays events related to GTP-SR. |
packets |
Displays packets related to GTP-SR packets. |
Defaults
Disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
This command displays debug level messages, errors, events, or packets for GTP-SR. It is useful for system operators and development engineers if problems are encountered with communication between the two GGSNs configured as an redundant pair and on which GTP-SR is enabled.
Examples
Example 1.
The following sample outputs is for a GGSN failover and switchover of Standby to Active. There is no PDP context involved in this debug collection.
Active GGSN:
Router-a#show gprs redundancy
GPRS redundancy is enabled and Unit-Status is Standby
Redundancy Transport Infrastructure status
Redundancy Infrastructure state: STANDBY HOT
Peer Redundancy Infrastructure state: ACTIVE
GGSN Redundancy system up since: 21:29:21 EDT Aug 19 2000
Time of last switchover: never
Total Number of Switchovers: 2
GPRS Redundancy Statistics
Last cleared: never
CheckPointed-From-Active Statistics
Total Number of Messages: 129
Number of Context Setup messages: 19
Number of Context Modify messages: 3
Number of Context Remove messages: 19
Number of Path Setup messages: 34
Number of Path Modify messages: 5
Number of Path Remove messages: 34
Number of CGF Ready messages: 1
Number of CGF Modify messages: 0
Number of CGF Remove messages: 0
Number of Internal State messages: 7
Router-a#debug gprs redundancy
GPRS CF packets debugging is on
GPRS CF events debugging is on
GPRS CF errors debugging is on
GPRS CF debug debugging is on
Router-a#
Router-a#
Router-a#
MWAM 10/2: 000064: Jun 1 2006 18:19:00.975 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1100 Grp 51 state Standby -> Active
MWAM 10/2: 000065: Jun 1 2006 18:19:00.975 EDT: GTP-SR: RF_Status=403-RF_STATUS_MAINTENANCE_ENABLE RFState=9-ACTIVE-FAST operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000066: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=200-RF_PROG_ACTIVE_FAST RFState=9-ACTIVE-FAST operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000067: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active Fast
MWAM 10/2: 000068: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=201-RF_PROG_ACTIVE_DRAIN RFState=10-ACTIVE-DRAIN operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000069: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active Drain
MWAM 10/2: 000070: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=202-RF_PROG_ACTIVE_PRECONFIG RFState=11-ACTIVE_PRECONFIG operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000071: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active PreConfig
MWAM 10/2: 000072: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=203-RF_PROG_ACTIVE_POSTCONFIG RFState=12-ACTIVE_POSTCONFIG operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000073: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active PostConfig
MWAM 10/2: 000074: Jun 1 2006 18:19:00.979 EDT: GTP-SR: RF_Event=204-RF_PROG_ACTIVE RFState=13-ACTIVE operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000075: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Received RF Progression Active
MWAM 10/2: 000076: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Start of the Standby-to-Active transition
MWAM 10/2: 000077: Jun 1 2006 18:19:00.979 EDT: GTP_SR: Old State Standby,Event Active Fast Received, New State Active
MWAM 10/2: 000078: Jun 1 2006 18:19:00.979 EDT: GTP-SR:Context Type OWN, Handler Sync, Context Event OWN Ready, Context Sub Event No Sub Event
MWAM 10/2: 000079: Jun 1 2006 18:19:00.979 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000080: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Event OWN Ready, Sub Event No Sub Event
MWAM 10/2: 000081: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Removing element from state-list Initialized, final count 2
MWAM 10/2: 000082: Jun 1 2006 18:19:00.979 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 2
MWAM 10/2: 000083: Jun 1 2006 18:19:00.979 EDT: GTP-SR:Context Type CGF, Handler Sync, Context Event CGF Ready, Context Sub Event No Sub Event
MWAM 10/2: 000084: Jun 1 2006 18:19:00.979 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000085: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Event CGF Ready, Sub Event No Sub Event
MWAM 10/2: 000086: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Removing element from state-list Initialized, final count 1
MWAM 10/2: 000087: Jun 1 2006 18:19:00.979 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 3
MWAM 10/2: 000088: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Invalid shdb 0x0
MWAM 10/2: 000089: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Transition CG 10.0.250.114 to (state 0)
MWAM 10/2: 000090: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Invalid shdb 0x0
MWAM 10/2: 000091: Jun 1 2006 18:19:00.979 EDT: GTP-SR: Transition CG 10.0.250.115 to (state 0)
MWAM 10/2: 000092: Jun 1 2006 18:19:00.983 EDT: GTP-SR: SHDB AVL tree cleanup to start in 10 sec
MWAM 10/2: 000093: Jun 1 2006 18:19:00.983 EDT: GTP-SR: Completion of Standby-to-Active transition
MWAM 10/2: 000094: Jun 1 2006 18:19:00.983 EDT: GTP-SR: Chkpt Status Flow Off Indication
MWAM 10/2: 000095: Jun 1 2006 18:19:00.987 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.301 Grp 51 state Standby -> Active
MWAM 10/2: 000096: Jun 1 2006 18:19:00.987 EDT: GTP-SR: RF_Status=400-RF_STATUS_PEER_PRESENCE RFState=13-ACTIVE operand=0 RFPeerState=13-ACTIVE
MWAM 10/2: 000097: Jun 1 2006 18:19:00.987 EDT: GTP-SR: zero elements to move to other list
MWAM 10/2: 000098: Jun 1 2006 18:19:00.987 EDT: GTP-SR: zero elements to move to other list
MWAM 10/2: 000099: Jun 1 2006 18:19:00.987 EDT: GTP-SR: RF_Status=401-RF_STATUS_PEER_COMM RFState=13-ACTIVE operand=0 RFPeerState=1-DISABLED
MWAM 10/2: 000100: Jun 1 2006 18:19:01.107 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1151 Grp 51 state Standby -> Active
MWAM 10/2: 000101: Jun 1 2006 18:19:01.155 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.250 Grp 51 state Standby -> Active
MWAM 10/2: 000102: Jun 1 2006 18:19:01.295 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1101 Grp 51 state Standby -> Active
MWAM 10/2: 000103: Jun 1 2006 18:19:01.355 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1251 Grp 51 state Standby -> Active
MWAM 10/2: 000104: Jun 1 2006 18:19:01.451 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.1201 Grp 51 state Standby -> Active
MWAM 10/2: 000105: Jun 1 2006 18:19:01.459 EDT: %HSRP-6-STATECHANGE: GigabitEthernet0/0.220 Grp 51 state Standby -> Active
Router-2#
MWAM 10/2: 000106: Jun 1 2006 18:19:10.983 EDT: GTP-SR: SHDB AVL tree cleanup has 3 nodes removed, 0 leftover
Router-a#
Router-a#
Router-a#
MWAM 10/2: 000107: Jun 1 2006 18:20:25.947 EDT: GTP-SR: Chkpt Status Flow Off Indication
MWAM 10/2: 000108: Jun 1 2006 18:20:25.947 EDT: GTP-SR: RF_Status=400-RF_STATUS_PEER_PRESENCE RFState=13-ACTIVE operand=1 RFPeerState=1-DISABLED
MWAM 10/2: 000109: Jun 1 2006 18:20:25.947 EDT: GTP-SR: RF_Status=401-RF_STATUS_PEER_COMM RFState=13-ACTIVE operand=1 RFPeerState=1-DISABLED
MWAM 10/2: 000110: Jun 1 2006 18:20:25.947 EDT: GTP-SR: RF_Event=300-RF_PROG_PLATFORM_SYNC RFState=13-ACTIVE operand=0 RFPeerState=0-UNKNOWN
MWAM 10/2: 000111: Jun 1 2006 18:20:25.947 EDT: GTP-SR: Received RF Progression Platform Sync
MWAM 10/2: 000112: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=102-RF_PROG_STANDBY_CONFIG RFState=13-ACTIVE operand=0 RFPeerState=5-STANDBY COLD-CONFIG
MWAM 10/2: 000113: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Standby Config
MWAM 10/2: 000114: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=103-RF_PROG_STANDBY_FILESYS RFState=13-ACTIVE operand=0 RFPeerState=6-STANDBY COLD-FILESYS
MWAM 10/2: 000115: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Stadnby Filesys
MWAM 10/2: 000116: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=104-RF_PROG_STANDBY_BULK RFState=13-ACTIVE operand=0 RFPeerState=7-STANDBY COLD-BULK
MWAM 10/2: 000117: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Standby Bulk
MWAM 10/2: 000118: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Active GGSN sending Bulk Sync finished Msg
MWAM 10/2: 000119: Jun 1 2006 18:20:53.899 EDT: GTP-SR: packing csg_path vaddr: 10.0.250.91
MWAM 10/2: 000120: Jun 1 2006 18:20:53.899 EDT: GTP-SR: packing csg_path port: 4386
MWAM 10/2: 000121: Jun 1 2006 18:20:53.899 EDT: GTP-SR: packing csg_path state: 1
MWAM 10/2: 000122: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000123: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 2
MWAM 10/2: 000124: Jun 1 2006 18:20:53.899 EDT: GTP-SR: adding element in state-list Synched, final count 1
MWAM 10/2: 000125: Jun 1 2006 18:20:53.899 EDT: GTP-SR: sync next charging id 0x1C0AA436, local rsn 0x6B76EBDE
MWAM 10/2: 000126: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Packing Pair Boot time 21:29:21 EDT Aug 19 2000
MWAM 10/2: 000127: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Packing Switcover Count 3
MWAM 10/2: 000128: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Packing local restart_count 21
MWAM 10/2: 000129: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000130: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 1
MWAM 10/2: 000131: Jun 1 2006 18:20:53.899 EDT: GTP-SR: adding element in state-list Synched, final count 2
MWAM 10/2: 000132: Jun 1 2006 18:20:53.899 EDT: GTP-SR: sync cgf gw 10.0.250.114, operatemode NOT ACTIVE, nextseq 0x7530
MWAM 10/2: 000133: Jun 1 2006 18:20:53.899 EDT: GTP-SR: sync cgf gw 10.0.250.115, operatemode NOT ACTIVE, nextseq 0x7530
MWAM 10/2: 000134: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000135: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 0
MWAM 10/2: 000136: Jun 1 2006 18:20:53.899 EDT: GTP-SR: adding element in state-list Synched, final count 3
MWAM 10/2: 000137: Jun 1 2006 18:20:53.899 EDT: GTP-SR:Active took time of 0 msec to transfer data for bulk sync
MWAM 10/2: 000138: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Empty list to sync
MWAM 10/2: 000139: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Redundancy RF Event Received is Standby Bulk Sync End
MWAM 10/2: 000140: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Redundancy Event is Invalid
MWAM 10/2: 000141: Jun 1 2006 18:20:53.899 EDT: GTP-SR: RF_Event=105-RF_PROG_STANDBY_HOT RFState=13-ACTIVE operand=0 RFPeerState=8-STANDBY HOT
MWAM 10/2: 000142: Jun 1 2006 18:20:53.899 EDT: GTP-SR: Received RF Progression Standby Hot
Router-b
Router-b#show gprs redundancy
GPRS redundancy is enabled and Unit-Status is Active
Redundancy Transport Infrastructure status
Redundancy Infrastructure state: ACTIVE
Peer Redundancy Infrastructure state: STANDBY HOT
GGSN Redundancy system up since: 21:29:21 EDT Aug 19 2000
Time of last switchover:
Total Number of Switchovers: 3
GPRS Redundancy Statistics
Last cleared: never
CheckPointed-To-Standby Statistics
Total Number of Messages: 3
Number of Context Setup messages: 0
Number of Context Modify messages: 0
Number of Context Remove messages: 0
Number of Path Setup messages: 0
Number of Path Modify messages: 0
Number of Path Remove messages: 0
Number of CGF Ready messages: 1
Number of CGF Modify messages: 0
Number of CGF Remove messages: 0
Number of Internal State messages: 1
Example 2
The following sample outputs is for PDP context setup, prepaid user traffic, and then PDP context teardown. The debug is given for both Active and Standby GGSN. There is no GGSN switchover.
Active GGSN:
Router-a#debug gprs redundancy
GPRS CF packets debugging is on
GPRS CF events debugging is on
GPRS CF errors debugging is on
GPRS CF debug debugging is on
Router-a#show gprs redundancy
GPRS redundancy is enabled and Unit-Status is Active
Redundancy Transport Infrastructure status
Redundancy Infrastructure state: ACTIVE
Peer Redundancy Infrastructure state: STANDBY HOT
GGSN Redundancy system up since: 21:29:21 EDT Aug 19 2000
Time of last switchover:
Total Number of Switchovers: 4
GPRS Redundancy Statistics
Last cleared: never
CheckPointed-To-Standby Statistics
Total Number of Messages: 3
Number of Context Setup messages: 0
Number of Context Modify messages: 0
Number of Context Remove messages: 0
Number of Path Setup messages: 0
Number of Path Modify messages: 0
Number of Path Remove messages: 0
Number of CGF Ready messages: 1
Number of CGF Modify messages: 0
Number of CGF Remove messages: 0
Number of Internal State messages: 1
Router-a#
MWAM 10/2: 000073: Aug 24 2000 23:18:55.947 EDT: GTP-SR:pdpmcb handle for pdpmcb (0x24D2FC3C) is (0x3A000001)
MWAM 10/2: 000074: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000075: Aug 24 2000 23:18:55.963 EDT: GTP-SR: adding element in state-list Initialized, final count 2
MWAM 10/2: 000076: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000077: Aug 24 2000 23:18:55.963 EDT: GTP-SR: adding element in state-list Initialized, final count 3
MWAM 10/2: 000078: Aug 24 2000 23:18:55.963 EDT: GTP-SR:Context Type Path, Handler Sync, Context Event Path Setup, Context Sub Event No Sub Event
MWAM 10/2: 000079: Aug 24 2000 23:18:55.963 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000080: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Event Path Setup, Sub Event No Sub Event
MWAM 10/2: 000081: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Removing element from state-list Initialized, final count 2
MWAM 10/2: 000082: Aug 24 2000 23:18:55.963 EDT: GTP-SR: adding element in state-list Dynamic Sync Ready, final count 1
MWAM 10/2: 000083: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000084: Aug 24 2000 23:18:55.963 EDT: GTP-SR: adding element in state-list Initialized, final count 3
MWAM 10/2: 000085: Aug 24 2000 23:18:55.963 EDT: GTP-SR:Context Type Path, Handler Sync, Context Event Path Setup, Context Sub Event No Sub Event
MWAM 10/2: 000086: Aug 24 2000 23:18:55.963 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000087: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Event Path Setup, Sub Event No Sub Event
MWAM 10/2: 000088: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Removing element from state-list Initialized, final count 2
MWAM 10/2: 000089: Aug 24 2000 23:18:55.963 EDT: GTP-SR: adding element in state-list Dynamic Sync Ready, final count 2
MWAM 10/2: 000090: Aug 24 2000 23:18:55.963 EDT: GTP-SR:packing pathcb->gtpv 1
MWAM 10/2: 000091: Aug 24 2000 23:18:55.963 EDT: GTP-SR:Local IP address 166.11.0.11, and port 2123
MWAM 10/2: 000092: Aug 24 2000 23:18:55.963 EDT: GTP-SR:Remote IP address 10.10.50.3, and port 2123
MWAM 10/2: 000093: Aug 24 2000 23:18:55.963 EDT: GTP-SR:packing pathcb->num_data_socks 0
MWAM 10/2: 000094: Aug 24 2000 23:18:55.963 EDT: GTP-SR:packing pathcb->flags 9
MWAM 10/2: 000095: Aug 24 2000 23:18:55.963 EDT: GTP-SR:packing pathcb->restart_count_remote 1
MWAM 10/2: 000096: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Different lengths during path create: allowed: 63, packed: 23
MWAM 10/2: 000097: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000098: Aug 24 2000 23:18:55.963 EDT: GTP-SR: Removing element from state-list Dynamic Sync Ready, final count 1
MWAM 10/2: 000099: Aug 24 2000 23:18:55.963 EDT: GTP-SR: adding element in state-list Synched, final count 4
MWAM 10/2: 000100: Aug 24 2000 23:18:55.963 EDT: GTP-SR:packing pathcb->gtpv 1
MWAM 10/2: 000101: Aug 24 2000 23:18:55.963 EDT: GTP-SR:Local IP address 166.11.0.11, and port 2152
MWAM 10/2: 000102: Aug 24 2000 23:18:55.963 EDT: GTP-SR:Remote IP address 10.10.50.3, and port 2152
MWAM 10/2: 000103: Aug 24 2000 23:18:55.967 EDT: GTP-SR:packing pathcb->num_data_socks 0
MWAM 10/2: 000104: Aug 24 2000 23:18:55.967 EDT: GTP-SR:packing pathcb->flags 8
MWAM 10/2: 000105: Aug 24 2000 23:18:55.967 EDT: GTP-SR:packing pathcb->restart_count_remote 0
MWAM 10/2: 000106: Aug 24 2000 23:18:55.967 EDT: GTP-SR: Different lengths during path create: allowed: 63, packed: 23
MWAM 10/2: 000107: Aug 24 2000 23:18:55.967 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000108: Aug 24 2000 23:18:55.967 EDT: GTP-SR: Removing element from state-list Dynamic Sync Ready, final count 0
MWAM 10/2: 000109: Aug 24 2000 23:18:55.967 EDT: GTP-SR: adding element in state-list Synched, final count 5
MWAM 10/2: 000110: Aug 24 2000 23:18:55.967 EDT: GTP-SR: Empty list to sync
MWAM 10/2: 000111: Aug 24 2000 23:18:55.967 EDT: GTP-SR: Empty list to sync
MWAM 10/2: 000112: Aug 24 2000 23:19:01.583 EDT: GTP-SR: Creating red context for category ID 4 username 100000000000000 on APN ms-apn
MWAM 10/2: 000113: Aug 24 2000 23:19:01.583 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000114: Aug 24 2000 23:19:01.583 EDT: GTP-SR: adding element in state-list Initialized, final count 3
MWAM 10/2: 000115: Aug 24 2000 23:19:01.583 EDT: GTP-SR: Removing element from state-list Initialized, final count 2
MWAM 10/2: 000116: Aug 24 2000 23:19:01.583 EDT: GTP-SR: adding element in state-list Synched, final count 6
MWAM 10/2: 000117: Aug 24 2000 23:19:01.583 EDT: GPRS:0100000000000050:shdb 0x95000008 created for category 4 (handle 0xD0000001)
MWAM 10/2: 000118: Aug 24 2000 23:19:01.591 EDT: GTP-SR: Don't checkpoint QP4QR Clear for Create/Update after a Quota Push Resp
MWAM 10/2: 000119: Aug 24 2000 23:19:01.591 EDT: GTP-SR:Context Type PDP, Handler Sync, Context Event Context Setup, Context Sub Event No Sub Event
MWAM 10/2: 000120: Aug 24 2000 23:19:01.591 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000121: Aug 24 2000 23:19:01.591 EDT: GTP-SR: Event Context Setup, Sub Event No Sub Event
MWAM 10/2: 000122: Aug 24 2000 23:19:01.591 EDT: GTP-SR: Removing element from state-list Initialized, final count 1
MWAM 10/2: 000123: Aug 24 2000 23:19:01.591 EDT: GTP-SR: adding element in state-list Dynamic Sync Ready, final count 1
MWAM 10/2: 000124: Aug 24 2000 23:19:01.591 EDT: GTP-SR: for pdpmcb: 221 bytes to be packed
MWAM 10/2: 000125: Aug 24 2000 23:19:01.591 EDT: GTP-SR: pdpmcb bitmap = 14346
MWAM 10/2: 000126: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->user-name 91100000000000000
MWAM 10/2: 000127: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->msisdn 9101000000000000F000
MWAM 10/2: 000128: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->selection_mode 0
MWAM 10/2: 000129: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->remove_staticIP 0
MWAM 10/2: 000130: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->llcframenum 0
MWAM 10/2: 000131: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->idle_timeout 3600
MWAM 10/2: 000132: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->session_timeout 0
MWAM 10/2: 000133: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpmcb_handle 973078529
MWAM 10/2: 000134: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->shdb 2080374789
MWAM 10/2: 000135: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing apn_name ms-apn
MWAM 10/2: 000136: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing apnvalue ms-apn
MWAM 10/2: 000137: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->teid 4194305
MWAM 10/2: 000138: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->imsi 01000000000000F0
MWAM 10/2: 000139: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.static_addr_allocated 0
MWAM 10/2: 000140: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.dynamic_addr_allocated 1
MWAM 10/2: 000141: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.dynamic_addr_requested 1
MWAM 10/2: 000142: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.addr_source 3
MWAM 10/2: 000143: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.allocated_prefix_len 16
MWAM 10/2: 000144: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.aggregate_prefix_len 16
MWAM 10/2: 000145: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.pdp_type_org 1
MWAM 10/2: 000146: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.pdp_type_num 33
MWAM 10/2: 000147: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->pdpaddr.addrlen 6
MWAM 10/2: 000148: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb-ggsn_addr_si 166.11.0.11
MWAM 10/2: 000149: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb-ggsn_addr_data 166.11.0.11
MWAM 10/2: 000150: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpmcb->msisdn_len 9nGTP-SR:packing aaa charging profile index -1,
MWAM 10/2: 000151: Aug 24 2000 23:19:01.591 EDT: GTP-SR:pdpmcb encoded len_t 0
MWAM 10/2: 000152: Aug 24 2000 23:19:01.591 EDT: GTP-SR: pdpcb bitmap = 0
MWAM 10/2: 000153: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_cntl_remote 1
MWAM 10/2: 000154: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_local 4194306
MWAM 10/2: 000155: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_remote 1000
MWAM 10/2: 000156: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->tid 0100000000000050
MWAM 10/2: 000157: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing naspi = 5
MWAM 10/2: 000158: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->internal_flags 9175041
MWAM 10/2: 000159: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->mnrgflag 0
MWAM 10/2: 000160: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->open_cdr_sent 0
MWAM 10/2: 000161: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->charging_reserved 0
MWAM 10/2: 000162: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->pri 1
MWAM 10/2: 000163: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fastswitchable 0
MWAM 10/2: 000164: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb-sgsn_addr_sig 10.10.50.3
MWAM 10/2: 000165: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb-sgsn_addr_data 10.10.50.3
MWAM 10/2: 000166: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->sequence_sig 1
MWAM 10/2: 000167: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_sig_up 0
MWAM 10/2: 000168: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_data1_up 0
MWAM 10/2: 000169: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_sig_down 0
MWAM 10/2: 000170: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_data1_down 0
MWAM 10/2: 000171: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->fl_data2 0
MWAM 10/2: 000172: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->cause 128
MWAM 10/2: 000173: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->restart_count 0
MWAM 10/2: 000174: Aug 24 2000 23:19:01.591 EDT: GTP-SR: packing pdpcb->create_time Aug 24 2000 23:18:56
MWAM 10/2: 000175: Aug 24 2000 23:19:01.591 EDT: GTP-SR: packing pdpcb->last_access_time Aug 24 2000 23:18:56
MWAM 10/2: 000176: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->gtpv1_qos_req.qos_profile 152109353l
MWAM 10/2: 000177: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->gtpv1_qos_neg.qos_profile 152109353l
MWAM 10/2: 000178: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_cntl_remote 1
MWAM 10/2: 000179: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_local 4194306
MWAM 10/2: 000180: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->teid_data_remote 1000
MWAM 10/2: 000181: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->charging_id 471179447
MWAM 10/2: 000182: Aug 24 2000 23:19:01.591 EDT: GTP-SR:packing pdpcb->cdr_recseqnum 0
MWAM 10/2: 000183: Aug 24 2000 23:19:01.591 EDT: GTP-SR: packing of pdpcb->reorder_required FF
MWAM 10/2: 000184: Aug 24 2000 23:19:01.591 EDT: GPRS:0100000000000050:
GTP-SR: Successfully pack PDP
MWAM 10/2: 000185: Aug 24 2000 23:19:01.591 EDT: GTP-SR: rulebase ID MS packed
MWAM 10/2: 000186: Aug 24 2000 23:19:01.591 EDT: GTP-SR: cc_session ccfh 0 failover_supported 1 reqnum 1 packed
MWAM 10/2: 000187: Aug 24 2000 23:19:01.591 EDT: GTP-SR: cc_session dest_host ips-clcis1.cisco.com dest_realm cisco.com packed
MWAM 10/2: 000188: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category ID 4 packed:
MWAM 10/2: 000189: Aug 24 2000 23:19:01.591 EDT: GTP-SR: sync data len 164
MWAM 10/2: 000190: Aug 24 2000 23:19:01.591 EDT: GTP-SR: active shdb 0x95000008
MWAM 10/2: 000191: Aug 24 2000 23:19:01.591 EDT: GTP-SR: CSG session ID 27599459844129
MWAM 10/2: 000192: Aug 24 2000 23:19:01.591 EDT: GTP-SR: chrg last svc rec seqnum 0
MWAM 10/2: 000193: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category state AUTHORIZED
MWAM 10/2: 000194: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category state trigger flags 0x3
MWAM 10/2: 000195: Aug 24 2000 23:19:01.591 EDT: GTP-SR: category sub flags 0x0
MWAM 10/2: 000196: Aug 24 2000 23:19:01.591 EDT: GTP-SR: sync flag 0x0
MWAM 10/2: 000197: Aug 24 2000 23:19:01.591 EDT: GTP-SR: quotas included
MWAM 10/2: 000198: Aug 24 2000 23:19:01.591 EDT: GTP-SR: last req timestamp 0
MWAM 10/2: 000199: Aug 24 2000 23:19:01.591 EDT: GTP-SR: last req seqnum 0
MWAM 10/2: 000200: Aug 24 2000 23:19:01.595 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000201: Aug 24 2000 23:19:01.595 EDT: GTP-SR: Removing element from state-list Dynamic Sync Ready, final count 0
MWAM 10/2: 000202: Aug 24 2000 23:19:01.595 EDT: GTP-SR: adding element in state-list Synched, final count 7
MWAM 10/2: 000203: Aug 24 2000 23:19:01.595 EDT: GTP-SR: Empty list to sync
MWAM 10/2: 000204: Aug 24 2000 23:19:03.939 EDT: GTP-SR:Context Type PDP, Handler Sync, Context Event Context Setup, Context Sub Event No Sub Event
MWAM 10/2: 000205: Aug 24 2000 23:19:03.939 EDT: GTP-SR:State of Redundancy Context is Synched
MWAM 10/2: 000206: Aug 24 2000 23:19:03.939 EDT: GTP-SR: Event Context Setup, Sub Event No Sub Event
MWAM 10/2: 000207: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Checkpoint SGSN init deletion via a category before final MCB deletion
MWAM 10/2: 000208: Aug 24 2000 23:19:04.463 EDT: GTP-SR:Context Type Category, Handler Update, Context Event Category update, Context Sub Event No Sub Event
MWAM 10/2: 000209: Aug 24 2000 23:19:04.463 EDT: GTP-SR:State of Redundancy Context is Synched
MWAM 10/2: 000210: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Event Category update, Sub Event No Sub Event
MWAM 10/2: 000211: Aug 24 2000 23:19:04.463 EDT: GTP-SR: MCB internal flags 0x5802 packed
MWAM 10/2: 000212: Aug 24 2000 23:19:04.463 EDT: GTP-SR: cc_session reqnum 1 packed
MWAM 10/2: 000213: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category ID 4 packed:
MWAM 10/2: 000214: Aug 24 2000 23:19:04.463 EDT: GTP-SR: sync data len 52
MWAM 10/2: 000215: Aug 24 2000 23:19:04.463 EDT: GTP-SR: active shdb 0x95000008
MWAM 10/2: 000216: Aug 24 2000 23:19:04.463 EDT: GTP-SR: CSG session ID 27599459844129
MWAM 10/2: 000217: Aug 24 2000 23:19:04.463 EDT: GTP-SR: chrg last svc rec seqnum 0
MWAM 10/2: 000218: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category state PENDING_SERVICE_STOP
MWAM 10/2: 000219: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category state trigger flags 0x3
MWAM 10/2: 000220: Aug 24 2000 23:19:04.463 EDT: GTP-SR: category sub flags 0x0
MWAM 10/2: 000221: Aug 24 2000 23:19:04.463 EDT: GTP-SR: sync flag 0xA
MWAM 10/2: 000222: Aug 24 2000 23:19:04.463 EDT: GTP-SR: quotas not included
MWAM 10/2: 000223: Aug 24 2000 23:19:04.463 EDT: GTP-SR: last req timestamp 0
MWAM 10/2: 000224: Aug 24 2000 23:19:04.463 EDT: GTP-SR: last req seqnum 0
MWAM 10/2: 000225: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Different lengths during category sync: allowed 188, packed 56
MWAM 10/2: 000226: Aug 24 2000 23:19:04.463 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000227: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Checkpoint final MCB deletion after sending a CCR Final
MWAM 10/2: 000228: Aug 24 2000 23:19:04.467 EDT: GTP-SR:Context Type PDP, Handler Delete, Context Event Context Remove, Context Sub Event No Sub Event
MWAM 10/2: 000229: Aug 24 2000 23:19:04.467 EDT: GTP-SR:State of Redundancy Context is Synched
MWAM 10/2: 000230: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Event Context Remove, Sub Event No Sub Event
MWAM 10/2: 000231: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Checkpoint final MCB deletion
MWAM 10/2: 000232: Aug 24 2000 23:19:04.467 EDT: GTP-SR:Context Type PDP, Handler Delete, Context Event Context Remove, Context Sub Event No Sub Event
MWAM 10/2: 000233: Aug 24 2000 23:19:04.467 EDT: GTP-SR:State of Redundancy Context is Synched
MWAM 10/2: 000234: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Event Context Remove, Sub Event No Sub Event
MWAM 10/2: 000235: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Different lengths during PDP delete: allowed: 40, packed: 0
MWAM 10/2: 000236: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Ckpt Message was sucessfully sent
MWAM 10/2: 000237: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Removing element from state-list Synched, final count 6
MWAM 10/2: 000238: Aug 24 2000 23:19:04.467 EDT: GTP-SR: adding element in state-list Delete, final count 1
MWAM 10/2: 000239: Aug 24 2000 23:19:04.467 EDT: GTP-SR: Removing element from state-list Delete, final count 0
MWAM 10/2: 000240: Aug 24 2000 23:19:04.467 EDT: GTP-SR: No redundancy context for sending a down event to standby
MWAM 10/2: 000241: Aug 24 2000 23:19:04.471 EDT: GTP-SR: Removing element from state-list Synched, final count 5
Router-a#
Router-a#
Standby GGSN:
Router-b#debug gprs redundancy
GPRS CF packets debugging is on
GPRS CF events debugging is on
GPRS CF errors debugging is on
GPRS CF debug debugging is on
Router-b#sh gprs redun
GPRS redundancy is enabled and Unit-Status is Standby
Redundancy Transport Infrastructure status
Redundancy Infrastructure state: STANDBY HOT
Peer Redundancy Infrastructure state: ACTIVE
GGSN Redundancy system up since: 21:29:21 EDT Aug 19 2000
Time of last switchover: never
Total Number of Switchovers: 4
GPRS Redundancy Statistics
Last cleared: never
CheckPointed-From-Active Statistics
Total Number of Messages: 3
Number of Context Setup messages: 0
Number of Context Modify messages: 0
Number of Context Remove messages: 0
Number of Path Setup messages: 0
Number of Path Modify messages: 0
Number of Path Remove messages: 0
Number of CGF Ready messages: 1
Number of CGF Modify messages: 0
Number of CGF Remove messages: 0
Number of Internal State messages: 1
Router-b#
MWAM 10/2: 000065: Jun 1 2006 18:28:06.591 EDT: GTP-SR: Redundancy RF Event Received is Create Redundancy Context
MWAM 10/2: 000066: Jun 1 2006 18:28:06.591 EDT: GTP-SR: Redundancy Event is Path Setup
MWAM 10/2: 000067: Jun 1 2006 18:28:06.591 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000068: Jun 1 2006 18:28:06.591 EDT: GTP-SR: adding element in state-list Initialized, final count 4
MWAM 10/2: 000069: Jun 1 2006 18:28:06.591 EDT: GTP-SR Packet Dump: Len for dump: org_len=63, len=63
MWAM 10/2: 000070: Jun 1 2006 18:28:06.591 EDT: 1 0 0 0 0 0 0 0 9 1 A6 B 0 B 8 4B
MWAM 10/2: 000071: Jun 1 2006 18:28:06.591 EDT: A A 32 3 8 4B 1 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000072: Jun 1 2006 18:28:06.591 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000073: Jun 1 2006 18:28:06.595 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000074: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->gtpv 1
MWAM 10/2: 000075: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Local IP address 166.11.0.11, and port 2123
MWAM 10/2: 000076: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Remote IP address 10.10.50.3, and port 2123
MWAM 10/2: 000077: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->num_data_socks 0
MWAM 10/2: 000078: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->flags 9
MWAM 10/2: 000079: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing restart_count_remote 1
MWAM 10/2: 000080: Jun 1 2006 18:28:06.595 EDT: GTP-SR:Context Type Path, Handler Sync, Context Event Path Setup, Context Sub Event No Sub Event
MWAM 10/2: 000081: Jun 1 2006 18:28:06.595 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000082: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Event Path Setup, Sub Event No Sub Event
MWAM 10/2: 000083: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Removing element from state-list Initialized, final count 3
MWAM 10/2: 000084: Jun 1 2006 18:28:06.595 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 2
MWAM 10/2: 000085: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Redundancy RF Event Received is Create Redundancy Context
MWAM 10/2: 000086: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Redundancy Event is Path Setup
MWAM 10/2: 000087: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000088: Jun 1 2006 18:28:06.595 EDT: GTP-SR: adding element in state-list Initialized, final count 4
MWAM 10/2: 000089: Jun 1 2006 18:28:06.595 EDT: GTP-SR Packet Dump: Len for dump: org_len=63, len=63
MWAM 10/2: 000090: Jun 1 2006 18:28:06.595 EDT: 1 0 0 0 0 0 0 0 8 1 A6 B 0 B 8 68
MWAM 10/2: 000091: Jun 1 2006 18:28:06.595 EDT: A A 32 3 8 68 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000092: Jun 1 2006 18:28:06.595 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000093: Jun 1 2006 18:28:06.595 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000094: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->gtpv 1
MWAM 10/2: 000095: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Local IP address 166.11.0.11, and port 2152
MWAM 10/2: 000096: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Remote IP address 10.10.50.3, and port 2152
MWAM 10/2: 000097: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->num_data_socks 0
MWAM 10/2: 000098: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing u_path->flags 8
MWAM 10/2: 000099: Jun 1 2006 18:28:06.595 EDT: GTP-SR: un-packing restart_count_remote 0
MWAM 10/2: 000100: Jun 1 2006 18:28:06.595 EDT: GTP-SR:Context Type Path, Handler Sync, Context Event Path Setup, Context Sub Event No Sub Event
MWAM 10/2: 000101: Jun 1 2006 18:28:06.595 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000102: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Event Path Setup, Sub Event No Sub Event
MWAM 10/2: 000103: Jun 1 2006 18:28:06.595 EDT: GTP-SR: Removing element from state-list Initialized, final count 3
MWAM 10/2: 000104: Jun 1 2006 18:28:06.595 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 3
MWAM 10/2: 000105: Jun 1 2006 18:28:12.223 EDT: GTP-SR: Redundancy RF Event Received is Create Redundancy Context
MWAM 10/2: 000106: Jun 1 2006 18:28:12.223 EDT: GTP-SR: Redundancy Event is Context Setup
MWAM 10/2: 000107: Jun 1 2006 18:28:12.223 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000108: Jun 1 2006 18:28:12.223 EDT: GTP-SR: adding element in state-list Initialized, final count 4
MWAM 10/2: 000109: Jun 1 2006 18:28:12.223 EDT: GTP-SR Packet Dump: Len for dump: org_len=755, len=128
MWAM 10/2: 000110: Jun 1 2006 18:28:12.223 EDT: 1 1 39 31 31 30 30 30 30 30 30 30 30 30 30 30
MWAM 10/2: 000111: Jun 1 2006 18:28:12.223 EDT: 30 30 30 0 0 0 0 91 1 0 0 0 0 0 0 F0
MWAM 10/2: 000112: Jun 1 2006 18:28:12.223 EDT: 0 0 0 0 0 0 E 10 0 0 0 0 0 0 0 0
MWAM 10/2: 000113: Jun 1 2006 18:28:12.223 EDT: C0 23 1 8 5 63 69 73 63 6F 31 31 31 63 69 73
MWAM 10/2: 000114: Jun 1 2006 18:28:12.227 EDT: 63 6F 0 7C 0 0 5 0 0 8 0 0 0 0 0 0
MWAM 10/2: 000115: Jun 1 2006 18:28:12.227 EDT: 0 0 0 40 0 1 1 0 0 0 0 0 0 F0 B 1
MWAM 10/2: 000116: Jun 1 2006 18:28:12.227 EDT: 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000117: Jun 1 2006 18:28:12.227 EDT: 0 0 0 1 1 0 0 0 3 10 10 1 21 0 6 0
MWAM 10/2: 000118: Jun 1 2006 18:28:12.227 EDT: ...
MWAM 10/2: 000119: Jun 1 2006 18:28:12.231 EDT: GTP-SR:pdpmcb handle for pdpmcb (0x24AA0CCC) is (0x41000001)
MWAM 10/2: 000120: Jun 1 2006 18:28:12.231 EDT: GTP-SR: un-packing # of PDPs packed = 1
MWAM 10/2: 000121: Jun 1 2006 18:28:12.231 EDT: GTP-SR: un-packing pdpmcb->user-name 91100000000000000
MWAM 10/2: 000122: Jun 1 2006 18:28:12.231 EDT: GTP-SR: un-packing pdpmcb->msisdn 9101000000000000F000
MWAM 10/2: 000123: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->selection_mode 0
MWAM 10/2: 000124: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->remove_staticIP 0
MWAM 10/2: 000125: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->llcframenum 0
MWAM 10/2: 000126: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->idle_timeout 3600
MWAM 10/2: 000127: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->session_timeout 0
MWAM 10/2: 000128: Jun 1 2006 18:28:12.235 EDT: GTP-SR: pdpmcb bitmap = 30730
MWAM 10/2: 000129: Jun 1 2006 18:28:12.235 EDT: GTP-SR: apn name is ms-apn
MWAM 10/2: 000130: Jun 1 2006 18:28:12.235 EDT: GTP-SR: packing pdpmcb->teid 4194305
MWAM 10/2: 000131: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->imsi 01000000000000F0
MWAM 10/2: 000132: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.pdp_addr 11.1.0.1
MWAM 10/2: 000133: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.static_addr_allocated 0
MWAM 10/2: 000134: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.dynamic_addr_allocated 1
MWAM 10/2: 000135: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.dynamic_addr_requested 1
MWAM 10/2: 000136: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.addr_source 3
MWAM 10/2: 000137: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.allocated_prefix_len 16
MWAM 10/2: 000138: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.aggregate_prefix_len 16
MWAM 10/2: 000139: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.pdp_type_org 1
MWAM 10/2: 000140: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.pdp_type_num 33
MWAM 10/2: 000141: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.addrlen 6
MWAM 10/2: 000142: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->pdpaddr.dhcp_addr 0.0.0.0
MWAM 10/2: 000143: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb-ggsn_addr_si 166.11.0.11
MWAM 10/2: 000144: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb-ggsn_addr_data 166.11.0.11
MWAM 10/2: 000145: Jun 1 2006 18:28:12.235 EDT: GTP-SR: un-packing pdpmcb->msisdn_len 9
MWAM 10/2: 000146: Jun 1 2006 18:28:12.247 EDT: GTP-SR: Got teid=4194305, as requested
MWAM 10/2: 000147: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb->gtpv1_qos_req.qos_profile 152109353l
MWAM 10/2: 000148: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb->gtpv1_qos_neg.qos_profile 152109353l
MWAM 10/2: 000149: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb bitmap = 0
MWAM 10/2: 000150: Jun 1 2006 18:28:12.247 EDT: GTP-SR: un-packing pdpcb->tid0100000000000050
MWAM 10/2: 000151: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing nsapi = 5
MWAM 10/2: 000152: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->internal_flags 9175041
MWAM 10/2: 000153: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->mnrgflag 0
MWAM 10/2: 000154: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->open_cdr_sent 0
MWAM 10/2: 000155: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->charging_reserved 0
MWAM 10/2: 000156: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->pri 1
MWAM 10/2: 000157: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb->fastswitchable 0
MWAM 10/2: 000158: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb-sgsn_addr_sig 10.10.50.3
MWAM 10/2: 000159: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing pdpcb-sgsn_addr_data 10.10.50.3
MWAM 10/2: 000160: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->sequence_sig 1
MWAM 10/2: 000161: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_sig_up 0
MWAM 10/2: 000162: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_data1_up 0
MWAM 10/2: 000163: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_sig_down 0
MWAM 10/2: 000164: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_data1_down 0
MWAM 10/2: 000165: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->fl_data2 0
MWAM 10/2: 000166: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->cause 128
MWAM 10/2: 000167: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->restart_count 0
MWAM 10/2: 000168: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->create_time Apr 13 2006 01:25:25
MWAM 10/2: 000169: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->last_access_time Apr 13 2006 01:25:25
MWAM 10/2: 000170: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->teid_cntl_remote 1
MWAM 10/2: 000171: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->teid_data_local 4194306
MWAM 10/2: 000172: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->teid_data_remote 1000
MWAM 10/2: 000173: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->charging_id 471179447
MWAM 10/2: 000174: Jun 1 2006 18:28:12.251 EDT: GTP-SR: unpacking pdpcb->cdr_recseqnum 0
MWAM 10/2: 000175: Jun 1 2006 18:28:12.251 EDT: GTP-SR: un-packing of pdpcb->reorder_required FF
MWAM 10/2: 000176: Jun 1 2006 18:28:12.251 EDT: GTP-SR: We wanted teid 4194306, and got 4194306
MWAM 10/2: 000177: Jun 1 2006 18:28:12.251 EDT: GTP-SR: Got teid 4194306 as requested
MWAM 10/2: 000178: Jun 1 2006 18:28:12.251 EDT: pdp_create_by_tid on standby:tid 100000050, pdp 24A90B24
MWAM 10/2: 000179: Jun 1 2006 18:28:12.251 EDT: GPRS:0100000000000050:
GTP-SR: Successfully unpack PDP
MWAM 10/2: 000180: Jun 1 2006 18:28:12.251 EDT: GTP-SR: rulebase ID MS unpacked
MWAM 10/2: 000181: Jun 1 2006 18:28:12.251 EDT: GTP-SR: cc_session ccfh 0 failover_supported 1 reqnum 1 packed
MWAM 10/2: 000182: Jun 1 2006 18:28:12.251 EDT: GTP-SR: new cc_session dest_host ips-clcis1.cisco.com unpacked
MWAM 10/2: 000183: Jun 1 2006 18:28:12.251 EDT: GTP-SR: new cc_session dest_realm cisco.com unpacked
MWAM 10/2: 000184: Jun 1 2006 18:28:12.251 EDT: GTP-SR: Unpacking 1 categories
MWAM 10/2: 000185: Jun 1 2006 18:28:12.251 EDT: GTP-SR: Unpacking category of ID 4
MWAM 10/2: 000186: Jun 1 2006 18:28:12.255 EDT: GTP-SR: Creating red context for category ID 4 username 100000000000000 on APN ms-apn
MWAM 10/2: 000187: Jun 1 2006 18:28:12.255 EDT: GTP-SR: Need to allocate redundancy context
MWAM 10/2: 000188: Jun 1 2006 18:28:12.255 EDT: GTP-SR: adding element in state-list Initialized, final count 5
MWAM 10/2: 000189: Jun 1 2006 18:28:12.255 EDT: GTP-SR: Removing element from state-list Initialized, final count 4
MWAM 10/2: 000190: Jun 1 2006 18:28:12.255 EDT: GTP-SR: adding element in state-list Synched, final count 1
MWAM 10/2: 000191: Jun 1 2006 18:28:12.255 EDT: GPRS:0100000000000050:shdb 0xC6000008 created for category 4 (handle 0xDE000001)
MWAM 10/2: 000192: Jun 1 2006 18:28:12.255 EDT: GTP-SR: red context installed for the new category (shdb: active 0x95000008, standby 0xC6000008)
MWAM 10/2: 000193: Jun 1 2006 18:28:12.255 EDT: GTP-SR: new category ID 4 unpacked:
MWAM 10/2: 000194: Jun 1 2006 18:28:12.255 EDT: GTP-SR: sync data len 164
MWAM 10/2: 000195: Jun 1 2006 18:28:12.255 EDT: GTP-SR: active shdb 0x95000008
MWAM 10/2: 000196: Jun 1 2006 18:28:12.255 EDT: GTP-SR: CSG session ID 27599459844129
MWAM 10/2: 000197: Jun 1 2006 18:28:12.255 EDT: GTP-SR: chrg last svc rec seqnum 0
MWAM 10/2: 000198: Jun 1 2006 18:28:12.255 EDT: GTP-SR: category state AUTHORIZED
MWAM 10/2: 000199: Jun 1 2006 18:28:12.255 EDT: GTP-SR: category state trigger flags 0x3
MWAM 10/2: 000200: Jun 1 2006 18:28:12.255 EDT: GTP-SR: category sub flags 0x0
MWAM 10/2: 000201: Jun 1 2006 18:28:12.255 EDT: GTP-SR: sync flag 0x0
MWAM 10/2: 000202: Jun 1 2006 18:28:12.255 EDT: GTP-SR: quotas included
MWAM 10/2: 000203: Jun 1 2006 18:28:12.255 EDT: GTP-SR: last req timestamp 0
MWAM 10/2: 000204: Jun 1 2006 18:28:12.255 EDT: GTP-SR: last req seqnum 0
MWAM 10/2: 000205: Jun 1 2006 18:28:12.255 EDT: GTP-SR: address received from active with radius source is
MWAM 10/2: 000206: Jun 1 2006 18:28:12.259 EDT: GTP-SR:Context Type PDP, Handler Sync, Context Event Context Setup, Context Sub Event No Sub Event
MWAM 10/2: 000207: Jun 1 2006 18:28:12.259 EDT: GTP-SR:State of Redundancy Context is Initialized
MWAM 10/2: 000208: Jun 1 2006 18:28:12.259 EDT: GTP-SR: Event Context Setup, Sub Event No Sub Event
MWAM 10/2: 000209: Jun 1 2006 18:28:12.259 EDT: GTP-SR: Removing element from state-list Initialized, final count 3
MWAM 10/2: 000210: Jun 1 2006 18:28:12.259 EDT: GTP-SR: adding element in state-list Bulk Synch Ready, final count 4
MWAM 10/2: 000211: Jun 1 2006 18:28:15.091 EDT: GTP-SR: Redundancy RF Event Received is Update Redundancy Context
MWAM 10/2: 000212: Jun 1 2006 18:28:15.091 EDT: GTP-SR: Redundancy Event is Category update
MWAM 10/2: 000213: Jun 1 2006 18:28:15.091 EDT: GTP-SR: red context found (active shdb 0x95000008, standby shdb 0xC6000008)
MWAM 10/2: 000214: Jun 1 2006 18:28:15.091 EDT: GTP-SR Packet Dump: Len for dump: org_len=188, len=128
MWAM 10/2: 000215: Jun 1 2006 18:28:15.091 EDT: 7C 0 0 5 0 0 58 2 0 0 0 1 0 34 34 0
MWAM 10/2: 000216: Jun 1 2006 18:28:15.091 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 95
MWAM 10/2: 000217: Jun 1 2006 18:28:15.091 EDT: 0 0 8 0 0 19 1A 0 0 0 21 0 0 0 0 0
MWAM 10/2: 000218: Jun 1 2006 18:28:15.091 EDT: 0 0 9 0 0 0 3 0 0 A 0 0 0 0 0 0
MWAM 10/2: 000219: Jun 1 2006 18:28:15.091 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000220: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000221: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000222: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000223: Jun 1 2006 18:28:15.095 EDT: ...
MWAM 10/2: 000224: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category found with handle 0xDE000001 shdbs: active 0x95000008 standby 0xC6000008 (MCB shdbs: active 0x7C000005, standby 0xC6000008)
MWAM 10/2: 000225: Jun 1 2006 18:28:15.095 EDT: GTP-SR: MCB internal flags 0x5802 unpacked
MWAM 10/2: 000226: Jun 1 2006 18:28:15.095 EDT: GTP-SR: cc_session reqnum 1 unpacked and installed
MWAM 10/2: 000227: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Unpacking category of ID 4
MWAM 10/2: 000228: Jun 1 2006 18:28:15.095 EDT: GTP-SR: sync obj created in prep for MCB deletion
MWAM 10/2: 000229: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category ID 4 unpacked:
MWAM 10/2: 000230: Jun 1 2006 18:28:15.095 EDT: GTP-SR: sync data len 52
MWAM 10/2: 000231: Jun 1 2006 18:28:15.095 EDT: GTP-SR: active shdb 0x95000008
MWAM 10/2: 000232: Jun 1 2006 18:28:15.095 EDT: GTP-SR: CSG session ID 27599459844129
MWAM 10/2: 000233: Jun 1 2006 18:28:15.095 EDT: GTP-SR: chrg last svc rec seqnum 0
MWAM 10/2: 000234: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category state PENDING_SERVICE_STOP
MWAM 10/2: 000235: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category state trigger flags 0x3
MWAM 10/2: 000236: Jun 1 2006 18:28:15.095 EDT: GTP-SR: category sub flags 0x0
MWAM 10/2: 000237: Jun 1 2006 18:28:15.095 EDT: GTP-SR: sync flag 0xA
MWAM 10/2: 000238: Jun 1 2006 18:28:15.095 EDT: GTP-SR: quotas not included
MWAM 10/2: 000239: Jun 1 2006 18:28:15.095 EDT: GTP-SR: last req timestamp 0
MWAM 10/2: 000240: Jun 1 2006 18:28:15.095 EDT: GTP-SR: last req seqnum 0
MWAM 10/2: 000241: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Redundancy RF Event Received is Redundancy Context Delete
MWAM 10/2: 000242: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Redundancy Event is Context Remove
MWAM 10/2: 000243: Jun 1 2006 18:28:15.095 EDT: GTP-SR Packet Dump: Len for dump: org_len=40, len=40
MWAM 10/2: 000244: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000245: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
MWAM 10/2: 000246: Jun 1 2006 18:28:15.095 EDT: 0 0 0 0 0 0 0 0
MWAM 10/2: 000247: Jun 1 2006 18:28:15.095 EDT: GPRS:GTP-SR: Deleting v1 MCB on the standby
MWAM 10/2: 000248: Jun 1 2006 18:28:15.095 EDT: GPRS:0100000000000050:GTP-SR: Deleting v1 PDP on the standby
MWAM 10/2: 000249: Jun 1 2006 18:28:15.095 EDT: GTP-SR: MCB deletion sync obj deleted
MWAM 10/2: 000250: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Removing element from state-list Synched, final count 0
MWAM 10/2: 000251: Jun 1 2006 18:28:15.095 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 3
MWAM 10/2: 000252: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy RF Event Received is Redundancy Context Delete
MWAM 10/2: 000253: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy Event is Path Remove
MWAM 10/2: 000254: Jun 1 2006 18:29:15.103 EDT: GTP-SR:Context Type Path, Handler Delete, Context Event Path Remove, Context Sub Event No Sub Event
MWAM 10/2: 000255: Jun 1 2006 18:29:15.103 EDT: GTP-SR:State of Redundancy Context is Bulk Synch Ready
MWAM 10/2: 000256: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Event Path Remove, Sub Event No Sub Event
MWAM 10/2: 000257: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 2
MWAM 10/2: 000258: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy RF Event Received is Redundancy Context Delete
MWAM 10/2: 000259: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Redundancy Event is Path Remove
MWAM 10/2: 000260: Jun 1 2006 18:29:15.103 EDT: GTP-SR:Context Type Path, Handler Delete, Context Event Path Remove, Context Sub Event No Sub Event
MWAM 10/2: 000261: Jun 1 2006 18:29:15.103 EDT: GTP-SR:State of Redundancy Context is Bulk Synch Ready
MWAM 10/2: 000262: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Event Path Remove, Sub Event No Sub Event
MWAM 10/2: 000263: Jun 1 2006 18:29:15.103 EDT: GTP-SR: Removing element from state-list Bulk Synch Ready, final count 1
Feedback