Table Of Contents
TID/IMSI/MSISDN-Based Conditionally Triggered Debugging
Usage Guidelines for TID/IMSI/MSISDN-Based Conditional Debugging
debug gprs gtp ppp-regeneration
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.
CautionBecause 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
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.
For examples:
For a create request with TID 12345678090000B0, you would enter:
GGSN# debug condition calling 12345678090000B0Condition 1 setGGSN#For a create request with IMSI 21436579000000, you would enter:GGSN# debug condition calling 21436579000000Condition 2 setGGSN#For a create request with MSISDN 1112223344, you would enter:
GGSN# debug condition calling msisdn-1112223344Condition 3 setGGSN#To verify the set conditions, enter:
GGSN# show debug condition allCondition 1: calling 12345678090000B0 (0 flags triggered)Condition 2: calling 21436579000000 (0 flags triggered)Condition 3: calling 1112223344 (0 flags triggered)GGSN#2.
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.
GGSN# no debug allAll possible debugging has been turned offGGSN#GGSN# show debug condition allCondition 1: calling 12345678090000B0 (1 flags triggered)Condition 2: calling 21436579000000 (1 flags triggered)Condition 3: calling 1112223344 (1 flags triggered)GGSN#4.
GGSN# no debug condition allRemoving 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] y2 conditions have been removed5.
GGSN# show debug condition all% No conditions founddebug 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.
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 12345678090000B0Condition 1 setGGSN#GGSN# debug condition calling 21436579000000Condition 2 setGGSN#GGSN# debug condition calling msisdn 408525823010Condition 3 setGGSN#Example 2
The following example stops all conditional debugging:
Router# no debug conditional allAll possible debugging has been turned offRouter#debug data-store
To display PSD related debugging messages for the 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.
Caution
Examples
The following example configures a debugging session to check PSD-related parameters:
Router# debug data-storedebug 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.
Caution
Examples
The following example configures a detailed PSD-related debugging session:
Router# debug data-store detailsdebug diameter
To display information about Diameter processing on the GGSN, use the debug diameter privilege EXEC command.
debug diameter {dcca | connection | error | packet | event | fsm | failover | all}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privilege 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 eventdebug ggsn quota-server
To display debug information related to quota server processing on the GGSN, use the debug ggsn quota-server privilege EXEC command.
debug ggsn quota-server [details | packets [dump] | events | parsing | errors]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privilege EXEC
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
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 events related to quota server processing on the GGSN:
Router# debug ggsn quota-server eventsThe following example enables the display of packets sent between the quota server process on the GGSN and the CSG:
Router# debug ggsn quota-server packetsThe following example enables the display of detailed quota server processing debug output:
Router# debug ggsn quota-server detailsdebug 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 privilege EXEC command.
debug gprs category fsm event
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privilege EXEC
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
This command is useful for system operators and development engineers if problems are encountered with eGGSN processing.
Examples
The following example enables the display of eGGSN events and state transactions:
Router# debug ggsn eggsn category fsm eventdebug gprs dcca
To display troubleshooting information about DCCA processing on the GGSN, use the debug gprs dcca privilege EXEC command.
debug gprs dcca
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privilege EXEC
Command History
12.3(14)YQ
This command was introduced.
12.3(14)YU
This command was integrated into Cisco IOS Release 12.3(14)YU.
Usage Guidelines
This command is useful for system operators and development engineers if Diameter protocol problems are encountered on the GGSN.
Examples
The following configuration example displays information specific to DCCA processing:
debug gprs dccadebug gprs dfp
To display debug messages for GPRS DFP weight calculation, use the debug gprs dfp privileged EXEC command. 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:
Caution
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 dfpGPRS DFP debugging is onRouter#The following example stops all debugging:
Router# no debug allAll possible debugging has been turned offRouter#debug gprs dhcp
To display information about Dynamic Host Configuration Protocol (DHCP) processing on the GGSN, use the debug gprs dhcp privileged EXEC command. 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.
Caution
Examples
The following example shows sample output for DHCP processing on the GGSN:
Router# debug gprs dhcp2d13h: GPRS:DHCP req:TID 1111111100000099, Req 12d13h: GPRS:Requesting IP address for pdp 1111111100000099 from server 172.16.0.8 tableid 02d13h: GPRS:DHCP ip allocation pass (10.88.17.43) for pdp 11111111000000992d13h: GPRS:Using DHCP ip address 10.88.17.43 for pdp 1111111100000099The 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 request2d13h: DHCP: new entry. add to queue2d13h: DHCP: SDiscover attempt # 1 for entry:2d13h: DHCP: SDiscover: sending 283 byte length DHCP packet2d13h: DHCP: SDiscover with directed serv 172.16.0.8, 283 bytes2d13h: DHCP: XID MATCH in dhcpc_for_us()2d13h: DHCP: Received a BOOTREP pkt2d13h: DHCP: offer received from 172.16.0.82d13h: DHCP: SRequest attempt # 1 for entry:2d13h: DHCP: SRequest- Server ID option: 172.16.0.82d13h: DHCP: SRequest- Requested IP addr option: 10.88.17.432d13h: DHCP: SRequest placed lease len option: 6048002d13h: DHCP: SRequest: 301 bytes2d13h: DHCP: SRequest: 301 bytes2d13h: DHCP: XID MATCH in dhcpc_for_us()2d13h: DHCP: Received a BOOTREP pkt2d13h: DHCP Proxy Client Pooling: ***Allocated IP address: 10.88.17.43Related 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 privileged EXEC command. 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.
Caution
Examples
The following example enables the display of events related to GTP processing on the GGSN:
Router# debug gprs gtp eventsThe following example enables the display of GTP signaling messages:
Router# debug gprs gtp messagesThe following example enables the display of GTP packets sent between the SGSN and GGSN:
Router# debug gprs gtp packetsThe following example enables the display of GTP PPP events between the SGSN and GGSN:
Router# debug gprs gtp ppp eventsThe 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 detailsRouter# debug gprs gtp ppp eventsdebug 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 privileged EXEC command. 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 successfullyThe debug gprs gtp parsing command can be used to verify GDM or GGSN processing of IEs.
Caution
Examples
The following example enables the display of debug messages that occur while GDM or the GGSN parses GTP IEs:
Router# debug gprs gtp parsingdebug gprs gtp ppp
To display information about PPP PDP type processing on the GGSN, use the debug gprs gtp ppp privileged EXEC command. 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.
Caution
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 eventsGTP PPP events display debugging is onRouter# debug gprs gtp ppp detailsGTP PPP details display debugging is on7200b#3d23h: GPRS:3d23h: GTP-PPP Fa1/0: Create new gtp_ppp_info3d23h: GPRS:3d23h: GTP-PPP: domain gprs.cisco.com not in any VPDN group3d23h: GPRS:3d23h: GTP-PPP: aaa-group accounting not configured under APN gprs.cisco.com3d23h: GPRS:GTP-PPP: Don't cache internally generated pak's header3d23h: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up3d23h: GPRS:3d23h: GTP-PPP Vi2: gtp_ppp_cstate_react changing states3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:3d23h: GTP-PPP: Vi2: Concat names user00 & gprs.cisco.com3d23h: GPRS:3d23h: GTP-PPP: New username after concat: user00@gprs.cisco.com3d23h: GPRS:3d23h: GTP-PPP: Vi2: Concat names user00@gprs.cisco.com & gprs.cisco.com3d23h: GPRS:3d23h: GTP-PPP: New username after concat: user00@gprs.cisco.com3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:3d23h: GTP-PPP Vi2: gtp_ppp_protocol_up is notified about intf UP3d23h: 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 all3d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:GTP-PPP: pdp_entry 0x62F442A4, recv ppp data pak3d23h: GPRS:GTP-PPP Vi2: proc_udp_input pak's linktype = 303d23h: GPRS:3d23h: GTP-PPP Vi2: gtp_ppp_pdp_terminate shutting down the vaccess3d23h: GPRS:3d23h: GTP-PPP Vi2: gtp_ppp_pdp_shut_va shutting down intf3d23h: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down3d23h: GPRS:3d23h: GTP-PPP Vi2: gtp_ppp_cstate_react changing states3d23h: GPRS:3d23h: GTP-PPP Vi2: gtp_ppp_free_va resetting intf vectors3d23h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to downdebug 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.
Caution
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 detailsGTP PPP regeneration details display debugging is onRouter# debug gprs gtp ppp-regeneration eventsGTP PPP regeneration events display debugging is on06:24:02: PPP-REGEN state counters: pending counter is 006:24:02: State[IDLE] counter is 006:24:02: State[AUTHORIZING] counter is 006:24:02: State[VPDN CONNECTING] counter is 006:24:02: State[PPP NEGOTIATING] counter is 006:24:02: State[PPP CONNECTED] counter is 006:24:02: State[PPP TERMINATING] counter is 006:24:02: PPP-REGEN state counters: pending counter is 106:24:02: State[IDLE] counter is 106:24:02: State[AUTHORIZING] counter is 006:24:02: State[VPDN CONNECTING] counter is 006:24:02: State[PPP NEGOTIATING] counter is 006:24:02: State[PPP CONNECTED] counter is 006:24:02: State[PPP TERMINATING] counter is 006:24:02: GPRS:1011111111500001:Authen: PAP username: tomy1@corporate_1.com06:24:02: GPRS:1011111111500001:Session timer started06:24:02: GPRS:Processing PPP regen reqQ06:24:02: GPRS:1011111111500001:Processing Initiate PPP regen from reqQ06:24:02: GPRS:1011111111500001:got event [REQUEST PPP REGEN] in state [IDLE]06:24:02: PPP-REGEN state counters: pending counter is 106:24:02: State[IDLE] counter is 006:24:02: State[AUTHORIZING] counter is 106:24:02: State[VPDN CONNECTING] counter is 006:24:02: State[PPP NEGOTIATING] counter is 006:24:02: State[PPP CONNECTED] counter is 006:24:02: State[PPP TERMINATING] counter is 006:24:02: GPRS:1011111111500001:state [IDLE->AUTHORIZING] on event [REQUEST PPP REGEN]06:24:02: GPRS:1011111111500001:Got VPN authorization info06:24:02: GPRS:1011111111500001:got event [AUTHOR SUCCESS] in state [AUTHORIZING]06:24:02: PPP-REGEN state counters: pending counter is 106:24:02: State[IDLE] counter is 006:24:02: State[AUTHORIZING] counter is 006:24:02: State[VPDN CONNECTING] counter is 106:24:02: State[PPP NEGOTIATING] counter is 006:24:02: State[PPP CONNECTED] counter is 006:24:02: State[PPP TERMINATING] counter is 006:24:02: GPRS:1011111111500001:state [AUTHORIZING->VPDN CONNECTING] on event [AUTHOR SUCCESS]06:24:02: GPRS:1011111111500001:Author succeeded, establishing the tunnel06:24:02: GPRS:1011111111500001:Create/Clone vaccess to negotiate PPP06:24:02: GPRS:1011111111500001:no need to set NS ppp_config06:24:02: GPRS:1011111111500001:MS no static IP addr. Get one via IPCP06:24:02: GPRS:1011111111500001:VPDN to inform PPP regen: CONNECTED06:24:02: GPRS:1011111111500001:got event [VPDN CONNECTED] in state [VPDN CONNECTING]06:24:02: PPP-REGEN state counters: pending counter is 106:24:02: State[IDLE] counter is 006:24:02: State[AUTHORIZING] counter is 006:24:02: State[VPDN CONNECTING] counter is 006:24:02: State[PPP NEGOTIATING] counter is 106:24:02: State[PPP CONNECTED] counter is 006:24:02: State[PPP TERMINATING] counter is 006:24:02: GPRS:1011111111500001:state [VPDN CONNECTING->PPP NEGOTIATING] on event [VPDN CONNECTED]06:24:02: GPRS:1011111111500001:Start PPP negotiations on vaccess06:24:02: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up06:24:02: GPRS:1011111111500001:IPCP is up06:24:02: GPRS:1011111111500001:LNS allocates 10.100.1.1 for MS06:24:02: GPRS:1011111111500001:IP addr 10.100.1.1 is negotiated for MS06:24:02: GPRS:1011111111500001:PPP connected06:24:02: GPRS:1011111111500001:got event [PPP NEGOTIATED] in state [PPP NEGOTIATING]06:24:02: PPP-REGEN state counters: pending counter is 006:24:02: State[IDLE] counter is 006:24:02: State[AUTHORIZING] counter is 006:24:02: State[VPDN CONNECTING] counter is 006:24:02: State[PPP NEGOTIATING] counter is 006:24:02: State[PPP CONNECTED] counter is 106:24:02: State[PPP TERMINATING] counter is 006:24:02: GPRS:1011111111500001:state [PPP NEGOTIATING->PPP CONNECTED] on event [PPP NEGOTIATED]06:24:02: GPRS:1011111111500001:PPP succeeded negotiation, session established06:24:02: GPRS:1011111111500001:Session timer stopped06:24:03: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to upExample 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 all06:28:05: PPP-REGEN state counters: pending counter is 006:28:05: State[IDLE] counter is 006:28:05: State[AUTHORIZING] counter is 006:28:05: State[VPDN CONNECTING] counter is 006:28:05: State[PPP NEGOTIATING] counter is 006:28:05: State[PPP CONNECTED] counter is 106:28:05: State[PPP TERMINATING] counter is 006:28:05: GPRS:1011111111500001:PPP regen current state PPP CONNECTED06:28:05: GPRS:1011111111500001:GTP disconnecting the PPP regen session06:28:05: GPRS:Processing PPP regen reqQ06:28:05: GPRS:1011111111500001:Processing Disconnect PPP regen from reqQ06:28:05: GPRS:1011111111500001:got event [CANCEL REGEN'ED PPP] in state [PPP CONNECTED]06:28:05: PPP-REGEN state counters: pending counter is 106:28:05: State[IDLE] counter is 006:28:05: State[AUTHORIZING] counter is 006:28:05: State[VPDN CONNECTING] counter is 006:28:05: State[PPP NEGOTIATING] counter is 006:28:05: State[PPP CONNECTED] counter is 006:28:05: State[PPP TERMINATING] counter is 106: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 up06:28:05: PPP-REGEN state counters: pending counter is 106:28:05: State[IDLE] counter is 006:28:05: State[AUTHORIZING] counter is 006:28:05: State[VPDN CONNECTING] counter is 006:28:05: State[PPP NEGOTIATING] counter is 006:28:05: State[PPP CONNECTED] counter is 006:28:05: State[PPP TERMINATING] counter is 106:28:05: GPRS:1011111111500001:PPP down06:28:05: GPRS:1011111111500001:got event [PPP FAILED] in state [PPP TERMINATING]06:28:05: PPP-REGEN state counters: pending counter is 106:28:05: State[IDLE] counter is 106:28:05: State[AUTHORIZING] counter is 006:28:05: State[VPDN CONNECTING] counter is 006:28:05: State[PPP NEGOTIATING] counter is 006:28:05: State[PPP CONNECTED] counter is 006:28:05: State[PPP TERMINATING] counter is 006:28:05: GPRS:1011111111500001:state [PPP TERMINATING->IDLE] on event [PPP FAILED]06:28:05: GPRS:1011111111500001:LCP went down06:28:05: GPRS:1011111111500001:VPDN disconnect06: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 structure06:28:05: GPRS:1011111111500001:VPDN handle invalid, no need to free it06:28:05: GPRS:1011111111500001:remove PPP regen context from Vi206:28:05: GPRS:1011111111500001:Session timer stopped06:28:05: PPP-REGEN state counters: pending counter is 006:28:05: State[IDLE] counter is 006:28:05: State[AUTHORIZING] counter is 006:28:05: State[VPDN CONNECTING] counter is 006:28:05: State[PPP NEGOTIATING] counter is 006:28:05: State[PPP CONNECTED] counter is 006:28:05: State[PPP TERMINATING] counter is 006:28:05: GPRS:1011111111500001:PPP regen context 0x633F196C released06:28:05: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down06:28:06: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to downdebug gprs radius
To display information about Remote Access Dial-In User Service (RADIUS) processing on the GGSN, use the debug gprs radius privileged EXEC command. 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.
Caution
Examples
The following example enables the display of debug messages related to RADIUS processing on the GGSN:
Router# debug gprs radiusdebug 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
The following example enables the display of events related to GTP-SR processing on the GGSN:
Router# debug gprs redundancyRelated CommandsRouter# debug gprs gtp events
