-
Cisco IOS Debug Command Reference, Release 12.2 T
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug appn trs
-
debug arap through debug cable env
-
debug cable err through debug ccfrf11 session
-
debug cch323 through debug clns events
-
debug clns packet through debug crypto pki messages
-
debug crypto pki transactions through debug dmsp doc-to-fax
-
debug dmsp fax-to-doc through debug fddi smt-packets
-
debug fmsp receive through debug gprs gtp
-
debug h225 through debug ip drp
-
debug ip dvmrp through debug ip mrouting
-
debug ip msdp through debug ip scp
-
debug ip sctp api through debug ip wccp packets
-
debug ipv6 cef drop through debug l2relay packets
-
debug lane client through debug mmoip transfer
-
debug modem through debug mpls ldp targeted-neighbors
-
debug mpls ldp transport connections through debug mpls xmplsatm vc
-
debug mpoa client through debug packet
-
debug piafs events through debug redundancy
-
debug redundancy as5850 through debug sdllc
-
debug serial interface through debug source error
-
debug source event through debug tacacs events
-
debug tag-switching adjacency through debug tag-switching xtagatm vc
-
debug tarp events through debug video vicm
-
debug vlan packet through debug voip settlement enter
-
debug voip settlement error through debug vpm all
-
debug vpm dsp through debug vxml
-
debug x25 through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Index
-
Table Of Contents
debug frame-relay informationelements
debug frame-relay ip tcp header-compression
debug frame-relay networklayerinterface
debug fmsp receive
To display debug messages for Fax Media Services Provider (FMSP) receive, use the debug fmsp receive command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fmsp receive [t30 | t38]
no debug fmsp receive [t30 | t38]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays output from the debug fmsp receive command:
Router# debug fmsp receive*Oct 16 08:31:33.243: faxmsp_call_setup_request: call id=28*Oct 16 08:31:33.243: faxmsp_call_setup_request: ramp data dir=ONRAMP, conf dir=DEST*Oct 16 08:31:33.243: faxmsp_bridge(): cfid=19, srccid=28, dstcid=27*Oct 16 08:31:33.243: faxmsp_bridge(): ramp data dir=ONRAMP, conf dir=DEST*Oct 16 08:31:33.243: faxmsp_bridge(): Explicit caps ind. done; will wait for registry caps ind*Oct 16 08:31:33.243: faxmsp_caps_ind: call id=28, src=27*Oct 16 08:31:33.243: faxmsp_caps_ack: call id src=27*Oct 16 08:31:33.279: faxmsp_call_setup_request: call id=29*Oct 16 08:31:33.279: faxmsp_call_setup_request: ramp data dir=OFFRAMP, conf dir=SRC*Oct 16 08:31:33.283: faxmsp_bridge(): cfid=20, srccid=29, dstcid=26*Oct 16 08:31:33.283: faxmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC*Oct 16 08:31:33.283: faxmsp_bridge(): Explicit caps ind. done; will wait for registry caps ind*Oct 16 08:31:33.283: faxmsp_caps_ind: call id=29, src=26*Oct 16 08:31:33.283: faxmsp_caps_ack: call id src=26*Oct 16 08:31:33.635: faxmsp_codec_download_done: call id=29*Oct 16 08:31:33.635: faxmsp_codec_download_done: call id=28*Oct 16 08:31:33.643: faxmsp_xmit: callid src=26, dst=29*Oct 16 08:31:33.643: faxmsp_xmit: callid src=27, dst=28*Oct 16 08:31:33.643: faxmsp_process_rcv_data: call id src=26, dst=29Related Commands
debug fmsp send
To display debug messages for FMSP send, use the debug fmsp send command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fmsp send [t30 | t38]
no debug fmsp send [t30 | t38]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays output from the debug fmsp send command:
Router# debug fmsp sendJan 1 05:02:56.782: faxmsp_call_setup_request: call id=21Jan 1 05:02:56.782: faxmsp_call_setup_request: ramp data dir=OFFRAMP, conf dir=SRCJan 1 05:02:56.782: faxmsp_bridge(): cfid=7, srccid=21, dstcid=20Jan 1 05:02:56.782: faxmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRCJan 1 05:02:56.782: faxmsp_bridge(): Explicit caps ind. done; will wait for registry caps indJan 1 05:02:56.782: faxmsp_caps_ind: call id=21, src=20Jan 1 05:02:56.782: faxmsp_caps_ack: call id src=20Jan 1 05:02:57.174: faxmsp_codec_download_done: call id=21Jan 1 05:02:57.174: faxMsp_tx_buffer callID=21Jan 1 05:02:57.178: faxMsp_tx_buffer callID=21Jan 1 05:02:57.178: faxMsp_tx_buffer callID=21Jan 1 05:02:57.178: faxMsp_tx_buffer callID=21Jan 1 05:02:57.182: faxmsp_xmit: callid src=20, dst=21Jan 1 05:02:57.182: faxmsp_process_rcv_data: call id src=20, dst=21Jan 1 05:03:01.814: faxmsp_xmit: callid src=20, dst=21Jan 1 05:03:01.814: faxmsp_process_rcv_data: call id src=20, dst=21Jan 1 05:03:01.814: faxMsp_tx_buffer callID=21Jan 1 05:03:02.802: faxmsp_xmit: callid src=20, dst=21Jan 1 05:03:02.802: faxmsp_process_rcv_data: call id src=20, dst=21Jan 1 05:03:02.822: faxmsp_xmit: callid src=20, dst=21Jan 1 05:03:02.822: faxmsp_process_rcv_data: call id src=20, dst=21Jan 1 05:03:02.854: faxmsp_xmit: callid src=20, dst=21Jan 1 05:03:02.854: faxmsp_process_rcv_data: call id src=20, dst=21Related Commands
debug foip off-ramp
To display debug messages for off-ramp fax mail, use the debug foip off-ramp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug foip off-ramp
no debug foip off-ramp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays output from the debug foip off-ramp command:
Router# debug foip off-rampJan 1 02:31:17.539: lapp off: CC_EV_CALL_HANDOFF, cid(0xB)Jan 1 02:31:17.539: loffHandoff: called number=5271714, callid=0xBJan 1 02:31:17.543: loffSetupPeer: cid1(0xB)Jan 1 02:31:17.543: destPat(5271714),matched(1),pref(5),tag(20),encap(1)Jan 1 02:31:22.867: lapp off: CC_EV_CALL_CONNECTED, cid(0xC)Jan 1 02:31:22.867: st=CALL_SETTING cid(0xB,0x0,0x0,0xC),cfid(0x0,0x0,0x0)Jan 1 02:31:22.867: loffConnectedJan 1 02:31:22.867: loffFlushPeerTagQueue cid(11) peer list: (empty)Jan 1 02:31:22.867: lapp off: CC_EV_CONF_CREATE_DONE, cid(0xC), cid2(0xD), cfid(0x1)Jan 1 02:31:22.867: st=CONFERENCING3 cid(0xB,0x0,0xD,0xC),cfid(0x0,0x0,0x1)Jan 1 02:31:22.867: loffConfDone3Jan 1 02:31:30.931: lapp off: CC_EV_FROM_FMSP_ON_CALL_DETAIL, cid(0xD)Jan 1 02:31:30.931: st=WAIT_SESS_INFO cid(0xB,0x0,0xD,0xC),cfid(0x0,0x0,0x1)Jan 1 02:31:30.931: loffSessionInfoJan 1 02:31:30.931: encd=2, resl=2, spd=26, min_scan_len=0, csid= 4085271714Jan 1 02:31:30.931: lapp off: CC_EV_CONF_CREATE_DONE, cid(0xD), cid2(0xE), cfid(0x2)Jan 1 02:31:30.931: st=CONFERENCING2 cid(0xB,0xE,0xD,0xC),cfid(0x0,0x2,0x1)Jan 1 02:31:30.931: loffConfDone2Related Commands
debug foip on-ramp
To display debug messages for on-ramp fax mail, use the debug foip on-ramp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug foip on-ramp
no debug foip on-ramp
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays output from the debug foip on-ramp command:
Router# debug foip on-ramp*Oct 16 08:07:01.947: lapp_on_application: Incoming Event: (15 = CC_EV_CALL_HANDOFF), CID(11), DISP(0)*Oct 16 08:07:01.947: lapp_on_call_handoff: Authentication enabled = FALSE*Oct 16 08:07:01.947: lapp_on_call_handoff: Authentication ID = 0*Oct 16 08:07:01.947: lapp_on_call_handoff: Authentication ID source = IVR or unknown*Oct 16 08:07:01.947: lapp_on_call_handoff: Authentication status = SUCCESS*Oct 16 08:07:01.947: lapp_on_call_handoff: Accounting enabled = FALSE*Oct 16 08:07:01.947: lapp_on_call_handoff: Accounting method list = fax*Oct 16 08:07:01.947: lapp_on_conference_vtsp_fmsp: Begin conferencing VTSP and FMSP...*Oct 16 08:07:01.951: lapp_on_change_state: old state(0) new state(1)*Oct 16 08:07:01.951: lapp_on_application: Incoming Event: (29 = CC_EV_CONF_CREATE_DONE), CID(11), DISP(0)*Oct 16 08:07:01.951: lapp_on_application: Current call state = 1*Oct 16 08:07:01.951: lapp_on_conference_created: The VTSP and the FMSP are conferenced*Oct 16 08:07:01.951: lapp_on_conference_created: Wait for FMSP call detail eventRelated Commands
debug frame-relay
To display debugging information about the packets received on a Frame Relay interface, use the debug frame-relay command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay
no debug frame-relay
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
9.00
This command was introduced.
12.2(13)T
Support for Banyan VINES was removed.
Usage Guidelines
This command helps you analyze the packets that have been received. However, because the debug frame-relay command generates a substantial amount of output, only use it when traffic on the Frame Relay network is fewer than 25 packets per second.
To analyze the packets that have been sent on a Frame Relay interface, use the debug frame-relay packet command.
Examples
The following is sample output from the debug frame-relay command:
Router# debug frame-relaySerial0(i): dlci 500(0x7C41), pkt type 0x809B, datagramsize 24Serial1(i): dlci 1023(0xFCF1), pkt type 0x309, datagramsize 13Serial0(i): dlci 500(0x7C41), pkt type 0x809B, datagramsize 24Serial1(i): dlci 1023(0xFCF1), pkt type 0x309, datagramsize 13Serial0(i): dlci 500(0x7C41), pkt type 0x809B, datagramsize 24Table 63 describes the significant fields shown in the display.
debug frame-relay adjacency
To display information pertaining to an adjacent node that has one or more Frame Relay permanent virtual circuit (PVC) bundles, use the debug frame-relay adjacency command in privileged EXEC mode. To stop displaying the adjacent node information, use the no form of this command.
debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]}
no debug frame-relay adjacency {pvc [dlci] | vc-bundle [vc-bundle-name]}
Syntax Description
Defaults
No default behaviors or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor adjacency activity and status for an adjacent node.
Note
Debug messages that are prefixed with "FR_ADJ" (instead of "FR-ADJ") indicate serious failures in the Frame Relay PVC bundle performance. Contact the Cisco Technical Assistance Center (TAC) if you see debugging messages with this prefix.
Examples
The following sample output from the debug frame-relay adjacency vc-bundle command shows PVC bundle "MP-4-dynamic" going down. Each bundle member PVC is marked for removal from CEF's adjacency table, and then the adjacency for the PVC bundle itself is marked for removal. The adjacencies are actually removed from the table later when a background clean-up process runs.
Router# debug frame-relay adjacency vc-bundle MP-4-dynamic00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 400: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 401: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 402: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 403: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 404: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 405: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 406: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: member 407: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 14.2.2.2: removing primary adjRelated Commands
debug frame-relay vc-bundle
Displays information pertaining to all the PVC bundles configured on the router.
debug frame-relay callcontrol
To display Frame Relay Layer 3 (network layer) call control information, use the debug frame-relay callcontrol command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay callcontrol
no debug frame-relay callcontrol
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug frame-relay callcontrol command is used specifically for observing FRF.4/Q.933 signalling messages and related state changes. The FRF.4/Q.933 specification describes a state machine for call control. The signalling code implements the state machine. The debug statements display the actual event and state combinations.
The Frame Relay switched virtual circuit (SVC) signalling subsystem is an independent software module. When used with the debug frame-relay networklayerinterface command, the debug frame-relay callcontrol command provides a better understanding of the call setup and teardown sequence. The debug frame-relay networklayerinterface command provides the details of the interactions between the signalling subsystem on the router and the Frame Relay subsystem.
Examples
State changes can be observed during a call setup on the calling party side. The debug frame-relay networklayerinterface command shows the following state changes or transitions:
STATE_NULL -> STATE_CALL_INITIATED -> STATE_CALL_PROCEEDING->STATE_ACTIVEThe following messages are samples of output generated during a call setup on the calling side:
6d20h: U0_SetupRequest: Serial06d20h: L3SDL: Ref: 1, Init: STATE_NULL, Rcvd: SETUP_REQUEST, Next: STATE_CALL_INITIATED 6d20h: U1_CallProceeding: Serial06d20h: L3SDL: Ref: 1, Init: STATE_CALL_INITIATED, Rcvd: MSG_CALL_PROCEEDING, Next:STATE_CALL_PROCEEDING6d20h: U3_Connect: Serial06d20h: L3SDL: Ref: 1, Init: STATE_CALL_PROCEEDING, Rcvd: MSG_CONNECT, Next: STATE_ACTIVE 6d20h:The following messages are samples of output generated during a call setup on the called party side. Note the state transitions as the call goes to the active state:
STATE_NULL -> STATE_CALL_PRESENT-> STATE_INCOMING_CALL_PROCEEDING->STATE_ACTIVE1w4d: U0_Setup: Serial2/31w4d: L3SDL: Ref: 32769, Init: STATE_NULL, Rcvd: MSG_SETUP, Next: STATE_CALL_PRESENT 1w4d: L3SDL: Ref: 32769, Init: STATE_CALL_PRESENT, Rcvd: MSG_SETUP, Next:STATE_INCOMING_CALL_PROC 1w4d: L3SDL: Ref: 32769, Init: STATE_INCOMING_CALL_PROC,Rcvd: MSG_SETUP, Next: STATE_ACTIVETable 64 explains the possible call states.
Related Commands
Displays debugging information about the packets that are received on a Frame Relay interface.
debug frame-relay networklayerinterface
Displays NLI information.
debug frame-relay events
To display debugging information about Frame Relay Address Resolution Protocol (ARP) replies on networks that support a multicast channel and use dynamic addressing, use the debug frame-relay events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug frame-relay events
no debug frame-relay events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is useful for identifying the cause of end-to-end connection problems during the installation of a Frame Relay network or node.
Note
Examples
The following is sample output from the debug frame-relay events command:
Router# debug frame-relay eventsSerial2(i): reply rcvd 172.16.170.26 126Serial2(i): reply rcvd 172.16.170.28 128Serial2(i): reply rcvd 172.16.170.34 134Serial2(i): reply rcvd 172.16.170.38 144Serial2(i): reply rcvd 172.16.170.41 228Serial2(i): reply rcvd 172.16.170.65 325As the output shows, the debug frame-relay events command returns one specific message type. The first line, for example, indicates that IP address 172.16.170.26 sent a Frame Relay ARP reply; this packet was received as input on serial interface 2. The last field (126) is the data-link connection identifier (DLCI) to use when communicating with the responding router.
For Frame Relay over MPLS, the following is sample output for the debug frame-relay events command. The command output shows the status of the VCs.
Router# debug frame-relay eventsFrame Relay events debugging is onThis example shows the messages that are displayed when you shut the core-facing interface on a provider edge (PE) router:
04:40:38:%SYS-5-CONFIG_I: Configured from console by consolenf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface hssi2/0Router(config-if)# shut04:40:43:%OSPF-5-ADJCHG: Process 10, Nbr 12.12.12.12 on Hssi2/0 from FULL to DOWN, Neighbor Down: Interface down or detached04:40:43: FRoMPLS [12.12.12.12, 100]: PW pvc_status set INACTIVE04:40:43: FRoMPLS [12.12.12.12, 100]: Setting pw segment DOWN04:40:43: FRoMPLS [12.12.12.12, 100]: Setting connection DOWN04:40:43: FRoMPLS [12.12.12.12, 101]: PW pvc_status set INACTIVE04:40:43: FRoMPLS [12.12.12.12, 101]: Setting pw segment DOWN04:40:43: FRoMPLS [12.12.12.12, 101]: Setting connection DOWN04:40:45:%LINK-5-CHANGED: Interface Hssi2/0, changed state to administratively down04:40:46:%LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi2/0, changed state to downThis example shows the messages that are displayed when you enable the core-facing interface on a PE router:
Router(config-if)# no shut04:40:56:%LINK-3-UPDOWN: Interface Hssi2/0, changed state to up04:40:57:%LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi2/0, changed state to up04:41:06:%OSPF-5-ADJCHG: Process 10, Nbr 12.12.12.12 on Hssi2/0 from LOADING to FULL, Loading Done04:41:19: FRoMPLS [12.12.12.12, 100]: PW pvc_status set ACTIVE04:41:19: FRoMPLS [12.12.12.12, 100]: Setting pw segment UP04:41:19: FRoMPLS [12.12.12.12, 101]: PW pvc_status set ACTIVE04:41:19: FRoMPLS [12.12.12.12, 101]: Setting pw segment UPThis example shows the messages that are displayed when you shut the edge-facing interface on a PE router:
Router(config)# interface pos4/0Router(config-if)# shut04:42:50: FRoMPLS [12.12.12.12, 100]: acmgr_circuit_down04:42:50: FRoMPLS [12.12.12.12, 100]: Setting connection DOWN04:42:50: FRoMPLS [12.12.12.12, 100]: PW pvc_status set INACTIVE04:42:52:%LINK-5-CHANGED: Interface POS4/0, changed state to administratively down04:42:53:%LINEPROTO-5-UPDOWN: Line protocol on Interface POS4/0, changed state to downThis example shows the messages that are displayed when you enable the edge-facing interface on a PE router:
Router(config)# interface pos4/0Router(config-if)# no shut04:43:20:%LINK-3-UPDOWN: Interface POS4/0, changed state to upc72-33-2(config-if)#04:43:20: FRoMPLS [12.12.12.12, 100]: Local up, sending acmgr_circuit_up04:43:20: FRoMPLS [12.12.12.12, 100]: PW nni_pvc_status set ACTIVE04:43:20: FRoMPLS [12.12.12.12, 100]: PW pvc_status set ACTIVE04:43:20: FRoMPLS [12.12.12.12, 100]: Setting pw segment UPdebug frame-relay foresight
To observe Frame Relay traces relating to traffic shaping with router ForeSight enabled, use the debug frame-relay foresight command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay foresight
no debug frame-relay foresight
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output that shows the display message returned in response to the debug frame-relay foresight command:
Router# debug frame-relay foresightFR rate control for DLCI 17 due to ForeSight msgThis message indicates the router learned from the ForeSight message that DLCI 17 is now experiencing congestion. The output rate for this circuit should be slowed down, and in the router this DLCI is configured to adapt traffic shaping in response to foresight messages.
Related Commands
debug frame-relay fragment
To display information related to Frame Relay fragmentation on a PVC, use the debug frame-relay fragment command in privileged EXEC mode. Use the no form of this command to turn off the debug function.
debug frame-relay fragment [event | interface type number dlci]
no debug frame-relay fragment [event | interface type number dlci]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command will display event or error messages related to Frame Relay fragmentation; it is only enabled at the PVC level on the selected interface.
This command is not supported on the Cisco MC3810 networking device for fragments received by a PVC configured via the voice-encap command.
Examples
The following example shows sample output from the debug frame-relay fragment command:
Router# debug frame-relay fragment interface serial 0/0 109This may severely impact network performance.You are advised to enable 'no logging console debug'. Continue?[confirm]Frame Relay fragment/packet debugging is onDisplaying fragments/packets on interface Serial0/0 dlci 109 onlySerial0/0(i): dlci 109, rx-seq-num 126, exp_seq-num 126, BE bits set, frag_hdr 04 C0 7ESerial0/0(o): dlci 109, tx-seq-num 82, BE bits set, frag_hdr 04 C0 52The following example shows sample output from the debug frame-relay fragment event command:
Router# debug frame-relay fragment eventThis may severely impact network performance.You are advised to enable 'no logging console debug'. Continue?[confirm]Frame Relay fragment event/errors debugging is onFrame-relay reassembled packet is greater than MTU size, packet dropped on serial 0/0dlci 109Unexpected B bit frame rx on serial0/0 dlci 109, dropping pending segmentsRx an out-of-sequence packet on serial 0/0 dlci 109, seq_num_received 17seq_num_expected 19Related Commands
debug frame-relay informationelements
To display information about Frame Relay Layer 3 (network layer) information element parsing and construction, use the debug frame-relay informationelements command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay informationelements
no debug frame-relay informationelements
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Within the FRF.4/Q.933 signalling specification, messages are divided into subunits called information elements. Each information element defines parameters specific to the call. These parameters can be values configured on the router, or values requested from the network.
The debug frame-relay informationelements command shows the signalling message in hexadecimal format. Use this command to determine parameters being requested and granted for a call.
Note
Caution
Examples
The following is sample output from the debug frame-relay informationelements command. In this example, each information element has a length associated with it. For those with odd-numbered lengths, only the specified bytes are valid, and the extra byte is invalid. For example, in the message "Call Ref, length: 3, 0x0200 0x0100," only "02 00 01" is valid; the last "00" is invalid.
lw0d# debug frame-relay informationelementsRouter: Outgoing MSG_SETUPRouter: Dir: U --> N, Type: Prot Disc, length: 1, 0x0800Router: Dir: U --> N, Type: Call Ref, length: 3, 0x0200 0x0100Router: Dir: U --> N, Type: Message type, length: 1, 0x0500Router: Dir: U --> N, Type: Bearer Capability, length: 5, 0x0403 0x88A0 0xCF00Router: Dir: U --> N, Type: DLCI, length: 4, 0x1902 0x46A0Router: Dir: U --> N, Type: Link Lyr Core, length: 27, 0x4819 0x090B 0x5C0B 0xDC0ARouter: 0x3140 0x31C0 0x0B21 0x4021Router: 0xC00D 0x7518 0x7598 0x0E09Router: 0x307D 0x8000Router: Dir: U --> N, Type: Calling Party, length: 12, 0x6C0A 0x1380 0x3837 0x3635Router: 0x3433 0x3231Router: Dir: U --> N, Type: Calling Party Subaddr, length: 4, 0x6D02 0xA000Router: Dir: U --> N, Type: Called Party, length: 11, 0x7009 0x9331 0x3233 0x3435Router: 0x3637 0x386ERouter: Dir: U --> N, Type: Called Party Subaddr, length: 4, 0x7102 0xA000Router: Dir: U --> N, Type: Low Lyr Comp, length: 5, 0x7C03 0x88A0 0xCE65Router: Dir: U --> N, Type: User to User, length: 4, 0x7E02 0x0000Table 65 explains the information elements in the example shown.
Related Commands
debug frame-relay ip tcp header-compression
To display debugging information about TCP/IP header compression on Frame Relay interfaces, use the debug frame-relay ip tcp header-compression command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug frame-relay ip tcp header-compression
no debug frame-relay ip tcp header-compression
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug frame-relay ip tcp header-compression command shows the control packets that are passed to initialize IP header compression (IPHC) on a permanent virtual circuit (PVC). For Cisco IPHC, typically two packets are passed: one sent and one received per PVC. (Inverse Address Resolution Protocol (InARP) packets are sent on PVCs that do not have a mapping defined between a destination protocol address and the data-link connection identifier (DLCI) or Frame Relay PVC bundle that connects to the destination address.)
Debug messages are displayed only if the IPHC control protocol is renegotiated (for an interface or PVC state change or for a configuration change).
Examples
The following is sample output from the debug frame-relay ip tcp header-compression command when Cisco IPHC is configured in the IPHC profile:
Router# debug frame-relay ip tcp header-compression*Nov 14 09:22:07.991: InARP REQ: Tx compr_flags 43 *Nov 14 09:22:08.103: InARP RSP: Rx compr_flags: 43Table 66 describes the significant fields shown in the display.
debug frame-relay lapf
To display Frame Relay switched virtual circuit (SVC) Layer 2 information, use the debug frame-relay lapf command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay lapf
no debug frame-relay lapf
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug frame-relay lapf command to troubleshoot the data-link control portion of Layer 2 that runs over data-link connection identifier (DLCI) 0. Use this command only if you have a problem bringing up Layer 2. You can use the show interface serial command to determine the status of Layer 2. If it shows a Link Access Procedure, Frame Relay (LAPF) state of down, Layer 2 has a problem.
Examples
The following is sample output from the debug frame-relay lapf command. In this example, a line being brought up indicates an exchange of set asynchronous balanced mode extended (SABME) and unnumbered acknowledgment (UA) commands. A SABME is initiated by both sides, and a UA is the response. Until the SABME gets a UA response, the line is not declared to be up. The p/f value indicates the poll/final bit setting. TX means send, and RX means receive.
Router# debug frame-relay lapfRouter: *LAPF Serial0 TX -> SABME Cmd p/f=1Router: *LAPF Serial0 Enter state 5Router: *LAPF Serial0 RX <- UA Rsp p/f=1Router: *LAPF Serial0 lapf_ua_5Router: *LAPF Serial0 Link up!Router: *LAPF Serial0 RX <- SABME Cmd p/f=1Router: *LAPF Serial0 lapf_sabme_78Router: *LAPF Serial0 TX -> UA Rsp p/f=1In the following example, a line in an up LAPF state should see a steady exchange of RR (receiver ready) messages. TX means send, RX means receive, and N(R) indicates the receive sequence number.
Router# debug frame-relay lapfRouter: *LAPF Serial0 T203 expired, state = 7Router: *LAPF Serial0 lapf_rr_7Router: *LAPF Serial0 TX -> RR Rsp p/f=1, N(R)= 3Router: *LAPF Serial0 RX <- RR Cmd p/f=1, N(R)= 3Router: *LAPF Serial0 lapf_rr_7Router: *LAPF Serial0 TX -> RR Rsp p/f=1, N(R)= 3Router: *LAPF Serial0 RX <- RR Cmd p/f=1, N(R)= 3Router: *LAPF Serial0 lapf_rr_7debug frame-relay lmi
To display information on the local management interface (LMI) packets exchanged by the router and the Frame Relay service provider, use the debug frame-relay lmi command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay lmi [interface name]
no debug frame-relay lmi [interface name]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
You can use this command to determine whether the router and the Frame Relay switch are sending and receiving LMI packets properly.
Note
Examples
The following is sample output from the debug frame-relay lmi command:
The first four lines describe an LMI exchange. The first line describes the LMI request the router has sent to the switch. The second line describes the LMI reply the router has received from the switch. The third and fourth lines describe the response to this request from the switch. This LMI exchange is followed by two similar LMI exchanges. The last six lines consist of a full LMI status message that includes a description of the two permanent virtual circuits (PVCs) of the router.
Table 67 describes significant fields shown in the first line of the display.
Table 68 describes the significant fields shown in the third and fourth lines of the display.
Table 69 describes the significant fields shown in the last line of the display.
debug frame-relay multilink
To display debug messages for multilink Frame Relay bundles and bundle links, use the debug frame-relay multilink command in privileged EXEC mode. To disable the display of debug messages for multilink Frame Relay bundles and bundle links, use the no form of this command.
debug frame-relay multilink [control [mfr number | serial number]]
no debug frame-relay multilink
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
12.0(17)S
This command was introduced.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Usage Guidelines
Caution
Using the debug frame-relay multilink command without the mfr or serial keywords will display error conditions occurring at the bundle layer.
Examples
The following example shows output from the debug frame-relay multilink command for bundle "MFR0", which has 3 bundle links:
Router# debug frame-relay multilink control MFR000:42:54:Serial5/3(o):msg=Add_link, Link=Serial5/3, Bundle=MFR0, Link id=Serial5/3, BL state=IdleE1 00 01 01 07 4D 46 52 30 0000:42:54:Serial5/2(o):msg=Add_link, Link=Serial5/2, Bundle=MFR0, Link id=Serial5/2, BL state=IdleE1 00 01 01 07 4D 46 52 30 0000:42:54:Serial5/1(o):msg=Add_link, Link=Serial5/1, Bundle=MFR0, Link id=Serial5/1, BL state=IdleE1 00 01 01 07 4D 46 52 30 0000:42:54:%LINK-3-UPDOWN:Interface MFR0, changed state to down00:42:54:Serial5/3(i):msg=Add_link_ack, Link=Serial5/3, Bundle=MFR0, Link id=Serial5/3, BL state=Add_sentE1 00 02 01 07 4D 46 52 30 0000:42:54:Serial5/2(i):msg=Add_link_ack, Link=Serial5/2, Bundle=MFR0, Link id=Serial5/2, BL state=Add_sentE1 00 02 01 07 4D 46 52 30 0000:42:54:Serial5/1(i):msg=Add_link_ack, Link=Serial5/1, Bundle=MFR0, Link id=Serial5/1, BL state=Add_sentE1 00 02 01 07 4D 46 52 30 0000:42:54:%SYS-5-CONFIG_I:Configured from console by console00:43:00:Serial5/1(i):msg=Add_link, Link=Serial5/1, Bundle=MFR0, Link id=Serial5/1, BL state=Ack_rxE1 00 01 01 07 4D 46 52 30 0000:43:00:Serial5/1(o):msg=Add_link_ack, Link=Serial5/1, Bundle=MFR0, Link id=Serial5/1, BL state=Ack_rxE1 00 02 01 07 4D 46 52 30 0000:43:00:%LINK-3-UPDOWN:Interface MFR0, changed state to up00:43:00:Serial5/1(i):msg=Hello, Link=Serial5/1, Bundle=MFR0, Linkid=Serial5/1, BL state=UpE1 00 04 03 06 30 A7 E0 54 0000:43:00:Serial5/1(o):msg=Hello_ack, Link=Serial5/1, Bundle=MFR0, Link id=Serial5/1, BL state=UpE1 00 05 03 06 90 E7 0F C2 0600:43:01:Serial5/2(i):msg=Add_link, Link=Serial5/2, Bundle=MFR0, Link id=Serial5/2, BL state=Ack_rxE1 00 01 01 07 4D 46 52 30 0000:43:01:Serial5/2(o):msg=Add_link_ack, Link=Serial5/2, Bundle=MFR0, Link id=Serial5/2, BL state=Ack_rxE1 00 02 01 07 4D 46 52 30 0000:43:01:Serial5/2(i):msg=Hello, Link=Serial5/2, Bundle=MFR0, Linkid=Serial5/2, BL state=UpE1 00 04 03 06 30 A7 E0 54 0000:43:01:Serial5/2(o):msg=Hello_ack, Link=Serial5/2, Bundle=MFR0, Link id=Serial5/2, BL state=UpE1 00 05 03 06 90 E7 0F C2 0600:43:01:%LINEPROTO-5-UPDOWN:Line protocol on Interface Serial5/1, changed state to up00:43:01:Serial5/3(i):msg=Add_link, Link=Serial5/3, Bundle=MFR0, Link id=Serial5/3, BL state=Ack_rxE1 00 01 01 07 4D 46 52 30 0000:43:01:Serial5/3(o):msg=Add_link_ack, Link=Serial5/3, Bundle=MFR0, Link id=Serial5/3, BL state=Ack_rxE1 00 02 01 07 4D 46 52 30 0000:43:01:Serial5/3(i):msg=Hello, Link=Serial5/3, Bundle=MFR0, Linkid=Serial5/3, BL state=UpE1 00 04 03 06 30 A7 E0 54 0000:43:01:Serial5/3(o):msg=Hello_ack, Link=Serial5/3, Bundle=MFR0, Link id=Serial5/3, BL state=UpE1 00 05 03 06 90 E7 0F C2 0600:43:02:%LINEPROTO-5-UPDOWN:Line protocol on Interface Serial5/2 , changed state to up00:43:02:%LINEPROTO-5-UPDOWN:Line protocol on Interface Serial5/3 , changed state to upTable 70 describes the significant fields shown in the display.
Related Commands
show frame-relay multilink
Displays configuration information and statistics about multilink Frame Relay bundles and bundle links.
debug frame-relay networklayerinterface
To display Network Layer Interface (NLI) information, use the debug frame-relay networklayerinterface command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay networklayerinterface
no debug frame-relay networklayerinterface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The Frame Relay SVC signalling subsystem is decoupled from the rest of the router code by means of the NLI intermediate software layer.
The debug frame-relay networklayerinterface command shows activity within the network-layer interface when a call is set up or torn down. All output that contains an NL relates to the interaction between the Q.933 signalling subsystem and the NLI.
Note
Examples
The following is sample output from the debug frame-relay networklayerinterface command. This example displays the output generated when a call is set up. The second example shows the output generated when a call is torn down.
Router# debug frame-relay networklayerinterfaceRouter: NLI STATE: L3_CALL_REQ, Call ID 1 state 0Router: NLI: Walking the event table 1Router: NLI: Walking the event table 2Router: NLI: Walking the event table 3Router: NLI: Walking the event table 4Router: NLI: Walking the event table 5Router: NLI: Walking the event table 6Router: NLI: Walking the event table 7Router: NLI: Walking the event table 8Router: NLI: Walking the event table 9Router: NLI: NL0_L3CallReqRouter: NLI: State: STATE_NL_NULL, Event: L3_CALL_REQ, Next: STATE_L3_CALL_REQRouter: NLI: Enqueued outgoing packet on holdqRouter: NLI: Map-list search: Found maplist bermudaRouter: daddr.subaddr 0, saddr.subaddr 0, saddr.subaddr 0Router: saddr.subaddr 0, daddr.subaddr 0, daddr.subaddr 0Router: nli_parameter_negotiationRouter: NLI STATE: NL_CALL_CNF, Call ID 1 state 10Router: NLI: Walking the event table 1Router: NLI: Walking the event table 2Router: NLI: Walking the event table 3Router: NLI: NLx_CallCnfRouter: NLI: State: STATE_L3_CALL_REQ, Event: NL_CALL_CNF, Next: STATE_NL_CALL_CNFRouter: Checking maplist "junk"Router: working with maplist "bermuda"Router: Checking maplist "bermuda"Router: working with maplist "bermuda"Router: NLI: Emptying holdQ, link 7, dlci 100, size 104Router# debug frame-relay networklayerinterfaceRouter: NLI: L3 Call Release Req for Call ID 1Router: NLI STATE: L3_CALL_REL_REQ, Call ID 1 state 3Router: NLI: Walking the event table 1Router: NLI: Walking the event table 2Router: NLI: Walking the event table 3Router: NLI: Walking the event table 4Router: NLI: Walking the event table 5Router: NLI: Walking the event table 6Router: NLI: Walking the event table 7Router: NLI: Walking the event table 8Router: NLI: Walking the event table 9Router: NLI: Walking the event table 10Router: NLI: NLx_L3CallRejRouter: NLI: State: STATE_NL_CALL_CNF, Event: L3_CALL_REL_REQ, Next: STATE_L3_CALL_REL_REQRouter: NLI: junk: State: STATE_NL_NULL, Event: L3_CALL_REL_REQ, Next: STATE_NL_NULLRouter: NLI: Map-list search: Found maplist junkRouter: daddr.subaddr 0, saddr.subaddr 0, saddr.subaddr 0Router: saddr.subaddr 0, daddr.subaddr 0, daddr.subaddr 0Router: nli_parameter_negotiationRouter: NLI STATE: NL_REL_CNF, Call ID 1 state 0Router: NLI: Walking the event table 1Router: NLI: Walking the event table 2Router: NLI: Walking the event table 3Router: NLI: Walking the event table 4Router: NLI: Walking the event table 5Router: NLI: Walking the event table 6Router: NLI: Walking the event table 7Router: NLI: NLx_RelCnfRouter: NLI: State: STATE_NL_NULL, Event: NL_REL_CNF, Next: STATE_NL_NULLTable 71 describes the significant states and events shown in the display.
Related Commands
debug frame-relay callcontrol
Displays Frame Relay Layer 3 (network layer) call control information.
debug frame-relay packet
To display information on packets that have been sent on a Frame Relay interface, use the debug frame-relay packet command in privileged EXEC mode. The no form of this command disables debugging output.
debug frame-relay packet [interface name [dlci value]]
no debug frame-relay packet [interface name [dlci value]]
Syntax Description
interface name
(Optional) Name of interface or subinterface.
dlci value
(Optional) Data-link connection indentifier (DLCI) decimal value.
Command Modes
Privileged EXEC
Usage Guidelines
This command helps you analyze the packets that are sent on a Frame Relay interface. Because the debug frame-relay packet command generates a substantial amount of output, only use it when traffic on the Frame Relay network is fewer than 25 packets per second. Use the options to limit the debugging output to a specific DLCI or interface.
To analyze the packets received on a Frame Relay interface, use the debug frame-relay command.
Examples
The following is sample output from the debug frame-relay packet command:
The debug frame-relay packet output consists of groups of output lines; each group describes a Frame Relay packet that has been sent. The number of lines in the group can vary, depending on the number of DLCIs on which the packet was sent. For example, the first two pairs of output lines describe two different packets, both of which were sent out on a single DLCI. The last three lines describe a single Frame Relay packet that was sent out on two DLCIs.
Table 72 describes the significant fields shown in the display.
The following lines describe a Frame Relay packet sent to a particular address; in this case AppleTalk address 10.2:
Serial0: broadcast - 0, link 809B, addr 10.2Serial0(o):DLCI 100 type 809B size 104The following lines describe a Frame Relay packet that went out on two different DLCIs, because two Frame Relay map entries were found:
Serial0: broadcast searchSerial0(o):DLCI 300 type 809B size 24Serial0(o):DLCI 400 type 809B size 24The following lines do not appear. They describe a Frame Relay packet sent to a true broadcast address.
Serial1: broadcast searchSerial1(o):DLCI 400 type 800 size 288debug frame-relay ppp
To display debugging information, use the debug frame-relay ppp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug frame-relay ppp
no debug frame-relay ppp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
This command displays error messages for link states and LMI status changes for PPP over Frame Relay sessions.
To debug process-switched packets, use the debug frame-relay packet or debug ppp packet commands. To analyze the packets that have been sent on a Frame Relay interface, use the debug frame-relay packet command.
The debug frame-relay ppp command is generated from process-level switching only and is not CPU intensive.
Examples
The following shows output from the debug frame-relay ppp command where the encapsulation failed for VC 100.
Router# debug frame-relay pppFR-PPP: encaps failed for FR VC 100 on Serial0 downFR-PPP: input- Serial0 vc or va down, pak droppedThe following shows the output from the debug frame relay ppp and debug frame-relay packet commands. This example shows a virtual interface (virtual interface 1) establishing a PPP connection over PPP.
Router# debug frame-relay pppRouter# debug frame-relay packetVi1 LCP: O CONFREQ [Closed] id 1 len 10Vi1 LCP: MagicNumber 0xE0638565 (0x0506E0638565)Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 16Vi1 PPP: I pkt type 0xC021, datagramsize 14Vi1 LCP: I CONFACK [REQsent] id 1 len 10Vi1 LCP: MagicNumber 0xE0638565 (0x0506E0638565)Vi1 PPP: I pkt type 0xC021, datagramsize 14Vi1 LCP: I CONFREQ [ACKrcvd] id 6 len 10Vi1 LCP: MagicNumber 0x000EAD99 (0x0506000EAD99)Vi1 LCP: O CONFACK [ACKrcvd] id 6 len 10Vi1 LCP: MagicNumber 0x000EAD99 (0x0506000EAD99)Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 16Vi1 IPCP: O CONFREQ [Closed] id 1 len 10Vi1 IPCP: Address 170.100.9.10 (0x0306AA64090A)Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 16Vi1 PPP: I pkt type 0x8021, datagramsize 14Vi1 IPCP: I CONFREQ [REQsent] id 1 len 10Vi1 IPCP: Address 170.100.9.20 (0x0306AA640914)Vi1 IPCP: O CONFACK [REQsent] id 1 len 10Vi1 IPCP: Address 170.100.9.20 (0x0306AA640914)Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 16Vi1 PPP: I pkt type 0x8021, datagramsize 14Vi1 IPCP: I CONFACK [ACKsent] id 1 len 10Vi1 IPCP: Address 170.100.9.10 (0x0306AA64090A)Vi1 PPP: I pkt type 0xC021, datagramsize 16Vi1 LCP: I ECHOREQ [Open] id 1 len 12 magic 0x000EAD99Vi1 LCP: O ECHOREP [Open] id 1 len 12 magic 0xE0638565Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 18Vi1 LCP: O ECHOREQ [Open] id 1 len 12 magic 0xE0638565Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 18Vi1 LCP: echo_cnt 4, sent id 1, line upThe following shows the output for the debug frame-relay ppp and debug frame-relay packet commands that report a failed PPP over Frame Relay session. The problem is due to a challenge handshake authentication protocol (CHAP) failure.
Router# debug frame-relay pppRouter# debug frame-relay packetVi1 LCP: O CONFREQ [Listen] id 24 len 10Vi1 LCP: MagicNumber 0xE068EC78 (0x0506E068EC78)Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 16Vi1 PPP: I pkt type 0xC021, datagramsize 19Vi1 LCP: I CONFREQ [REQsent] id 18 len 15Vi1 LCP: AuthProto CHAP (0x0305C22305)Vi1 LCP: MagicNumber 0x0014387E (0x05060014387E)Vi1 LCP: O CONFACK [REQsent] id 18 len 15Vi1 LCP: AuthProto CHAP (0x0305C22305)Vi1 LCP: MagicNumber 0x0014387E (0x05060014387E)Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 21Vi1 PPP: I pkt type 0xC021, datagramsize 14Vi1 LCP: I CONFACK [ACKsent] id 24 len 10Vi1 LCP: MagicNumber 0xE068EC78 (0x0506E068EC78)Vi1 PPP: I pkt type 0xC223, datagramsize 32Vi1 CHAP: I CHALLENGE id 12 len 28 from "krishna"Vi1 LCP: O TERMREQ [Open] id 25 len 4Serial2/1(o): dlci 201(0x3091), NLPID 0x3CF(PPP), datagramsize 10Vi1 PPP: I pkt type 0xC021, datagramsize 8Vi1 LCP: I TERMACK [TERMsent] id 25 len 4Serial2/1(i): dlci 201(0x3091), pkt type 0x2000, datagramsize 303%SYS-5-CONFIG_I: Configured from console by consoleVi1 LCP: TIMEout: Time 0x199580 State Listendebug frame-relay switching
To display debug messages for switched Frame Relay PVCs, use the debug frame-relay switching EXEC command. To disable Frame Relay switching debugging, use the no form of this command.
debug frame-relay switching interface interface dlci [interval interval]
no debug frame-relay switching
Syntax Description
Defaults
The default interval is 1 second.
Command Modes
EXEC
Command History
12.0(12)S
This command was introduced.
12.1(5)T
This command was implemented in Cisco IOS Release 12.1(5)T.
Usage Guidelines
The debug frame-relay switching command can be used only on switched Frame Relay PVCs, not terminated PVCs.
Debug statistics are displayed only if they have changed.
Note
Examples
The following example shows sample output for the debug frame-relay switching command:
Router# debug frame-relay switching interface s2/1 1000 interval 2Frame Relay switching debugging is onDisplay frame switching debug on interface Serial2/1 dlci 10001d02h: Serial2/1 dlci 1000: 32 packets switched to Serial2/0 dlci 10021d02h: Serial2/1 dlci 1000: 1800 packets output1d02h: Serial2/1 dlci 1000: 4 packets dropped - outgoing PVC inactive1d02h: Serial2/1 dlci 1000: Incoming PVC status changed to ACTIVE1d02h: Serial2/1 dlci 1000: Outgoing PVC status changed to ACTIVE1d02h: Serial2/1 dlci 1000: Incoming interface hardware module state changed to UP1d02h: Serial2/1 dlci 1000: Outgoing interface hardware module state changed to UPdebug frame-relay vc-bundle
To display information about the Frame Relay permanent virtual circuit (PVC) bundles that are configured on a router, use the debug frame-relay vc-bundle command in privileged EXEC mode. To stop the display, use the no form of this command.
debug frame-relay vc-bundle {detail | state-change} [vc-bundle-name]
no debug frame-relay vc-bundle {detail | state-change} [vc-bundle-name]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to monitor state changes and Inverse ARP activity for one or all of the PVC bundles and bundle members configured on a router.
Note
Examples
The following is sample output from the debug frame-relay vc-bundle command that shows Inverse ARP information for the PVC bundle. PVC bundle member 406 is the only PVC in the bundle to handle Inverse ARP packets. The Inverse ARP packets coming in on other bundle member PVCs are dropped.
00:23:48:FR-VCB:MP-4-dynamic:inarp received on elected member 40600:23:48:FR-VCB:MP-4-dynamic:installing dynamic map00:23:48:FR-VCB:MP-4-dynamic:dropping inarp received on member 40700:23:52:FR-VCB:MP-4-dynamic:sending inarp pkt on member 406In the following example the PVC bundle goes down because the protected group goes down. All information about active transmission on each PVC is removed.
00:58:27:FR-VCB:MP-4-dynamic:member 402 state changed to DOWN00:58:27:FR-VCB:MP-4-dynamic:protected group is DOWN00:58:27:FR-VCB:MP-4-dynamic:state changed to DOWN00:58:27:FR-VCB:MP-4-dynamic:active table resetThe following is sample output from the debug frame-relay vc-bundle detail command. State change and Inverse ARP activity is displayed for all PVC bundles and bundle members on the router.
Router# debug frame-relay adjacency vc-bundle detail00:33:40: FR-VCB: MP-4-dynamic: member 404 state changed to UP00:33:40: FR-VCB: MP-4-dynamic: active table update00:33:40: FR-VCB: MP-3-static: sending inarp pkt on member 30000:33:41: FR-VCB: MP-3-static: inarp received on elected member 30000:33:48: FR-VCB: MP-3-static: inarp received on elected member 30000:33:48: FR-VCB: MAIN-1-static: dropping inarp received on member 10000:33:48: FR-VCB: MP-4-dynamic: dropping inarp received on member 40400:33:48: FR-VCB: MP-4-dynamic: dropping inarp received on member 40500:33:48: FR-VCB: P2P-5: dropping inarp received on member 50700:33:48: FR-VCB: MP-3-static: dropping inarp received on member 30300:33:48: FR-VCB: MAIN-2-dynamic: dropping inarp received on member 20200:33:48: FR-VCB: MAIN-1-static: dropping inarp received on member 10700:33:48: FR-VCB: MP-3-static: dropping inarp received on member 30500:33:48: FR-VCB: MAIN-1-static: dropping inarp received on member 10500:33:49: FR-VCB: P2P-5: dropping inarp received on member 50500:33:49: FR-VCB: P2P-5: dropping inarp received on member 50400:33:49: FR-VCB: P2P-5: dropping inarp received on member 50300:33:49: FR-VCB: P2P-5: dropping inarp received on member 50200:33:49: FR-VCB: P2P-5: dropping inarp received on member 501Related Commands
debug frame-relay adjacency
Displays information pertaining to an adjacent node that has one or more Frame Relay PVC bundles.
debug frame-relay virtual
To display debug messages for the virtual Frame Relay interface, use the debug frame-relay virtual command in privileged EXEC mode.
debug frame-relay virtual destination interface
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug frame-relay virtual command to display debug messages for the virtual Frame Relay interface. The debug frame-relay virtual command produces output only when problems occur.
Examples
The following example shows the output if one of the routers has not been configured. This output occurs when the other end is trying to send the receiving box Frame Relay packets.
VFR: Radio1/0 has no VFR for 00:00:C068:6F:AARelated Commands
debug fras error
To display information about Frame Relay access support (FRAS) protocol errors, use the debug fras error command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras error
no debug fras error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
For complete information on the FRAS process, use the debug fras message along with the debug fras error command.
Examples
The following is sample output from the debug fras error command. This example shows that no logical connection exists between the local station and remote station in the current setup:
Router# debug fras errorFRAS: No route, lmac 1000.5acc.7fb1 rmac 4fff.0000.0000, lSap=0x4, rSap=0x4FRAS: Can not find the SetupRelated Commands
debug fras-host activation
To display the LLC2 session activation and deactivation frames (such as XID, SABME, DISC, UA) that are being handled by the FRAS host, use the debug fras-host activation command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras-host activation
no debug fras-host activation
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
If many LLC2 sessions are being activated or deactivated at any time, this command may generate a substantial amount of output to the console.
Examples
The following is sample output from the debug fras-host activation command:
Router# debug fras-host activationFRHOST: Snd TST C to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x00 SSAP = 0x04FRHOST: Fwd BNN XID to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x04FRHOST: Fwd HOST XID to BNN, DA = 400f.dddd.001e SA = 4001.3745.1088 DSAP = 0x04 SSAP = 0x05FRHOST: Fwd BNN XID to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x04FRHOST: Fwd HOST SABME to BNN, DA = 400f.dddd.001e SA = 4001.3745.1088 DSAP = 0x04 SSAP = 0x04FRHOST: Fwd BNN UA to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x05The first line indicates that the FRAS Host sent a TEST Command to the host. In the second line, the FRAS Host forwards an XID frame from a BNN device to the host. In the third line, the FRAS Host forwards an XID from the host to the BNN device.
Table 73 describes the significant fields shown in the display.
debug fras-host error
To enable the FRAS Host to send error messages to the console, use the debug fras-host error command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras-host error
no debug fras-host error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug fras-host error command when the I-field in a TEST Response frame from a host does not match the I-field of the TEST Command sent by the FRAS Host:
Router# debug fras-host errorFRHOST: SRB TST R Protocol Violation - LLC I-field not maintained.debug fras-host packet
To see which LLC2 session frames are being handled by the FRAS Host, use the debug fras-host packet command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras-host packet
no debug fras-host packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command with great care. If many LLC2 sessions are active and passing data, this command may generate a substantial amount of output to the console and impact device performance.
Examples
The following is sample output from the debug fras-host packet command:
Router# debug fras-host packetFRHOST: Snd TST C to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x00 SSAP = 0x04FRHOST: Fwd BNN XID to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x04FRHOST: Fwd HOST XID to BNN, DA = 400f.dddd.001e SA = 4001.3745.1088 DSAP = 0x04 SSAP = 0x05FRHOST: Fwd BNN XID to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x04FRHOST: Fwd HOST SABME to BNN, DA = 400f.dddd.001e SA = 4001.3745.1088 DSAP = 0x04 SSAP = 0x04FRHOST: Fwd BNN UA to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x05FRHOST: Fwd HOST LLC-2 to BNN, DA = 400f.dddd.001e SA = 4001.3745.1088 DSAP = 0x04 SSAP = 0x04FRHOST: Fwd BNN LLC-2 to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x05FRHOST: Fwd HOST LLC-2 to BNN, DA = 400f.dddd.001e SA = 4001.3745.1088 DSAP = 0x04 SSAP = 0x04FRHOST: Fwd BNN LLC-2 to HOST, DA = 4001.3745.1088 SA = 400f.dddd.001e DSAP = 0x04 SSAP = 0x04The debug fras-host packet output contains all of the output from the debug fras-host activation command and additional information. The first six lines of this sample display are the same as the output from the debug fras-host activation command. The last lines show LLC-2 frames being sent between the BNN device and the host.
Table 74 describes the significant fields shown in the display.
debug fras-host snmp
To display messages to the console describing SNMP requests to the FRAS Host MIB, use the debug fras-host snmp command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras-host snmp
no debug fras-host snmp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use of this command may result in a substantial amount of output to the screen. Only use this command for problem determination.
Examples
The following is sample output from the debug fras-host snmp command. In this example, the MIB variable k_frasHostConnEntry_get() is providing SNMP information for the FRAS host.
Router# debug fras-host snmpk_frasHostConnEntry_get(): serNum = -1, vRingIfIdx = 31, frIfIdx = 12Hmac = 4001.3745.1088, frLocSap = 4, Rmac = 400f.dddd.001e, frRemSap = 4Table 75 describes the significant fields shown in the display.
debug fras message
To display general information about Frame Relay access support (FRAS) messages, use the debug fras message command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras message
no debug fras message
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
For complete information on the FRAS process, use the debug fras error command along with the debug fras message command.
Examples
The following is sample output from the debug fras message command. This example shows incoming Cisco Link Services (CLS) primitives:
Router# debug fras messageFRAS: receive 4C23FRAS: receive CC09Related Commands
debug fras state
To display information about Frame Relay access support (FRAS) data-link control link-state changes, use the debug fras state command in privileged EXEC mode. The no form of this command disables debugging output.
debug fras state
no debug fras state
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug fras state command. This example shows the state changing from a request open station is sent state to an exchange XID state.
Possible states are the following: reset, request open station is sent, exchange xid, connection request is sent, signal station wait, connection response wait, connection response sent, connection established, disconnect wait, and number of link states.
Router# debug fras stateFRAS: TR0 (04/04) oldstate=LS_RQOPNSTNSENT, input=RQ_OPNSTN_CNFFRAS: newstate=LS_EXCHGXIDRelated Commands
debug ftpserver
To display information about the FTP server process, use the debug ftpserver command in privileged EXEC mode. The no form of this command disables debugging output.
debug ftpserver
no debug ftpserver
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug ftpserver command:
Router# debug ftpserverMar 3 10:21:10: %FTPSERVER-6-NEWCONN: FTP Server - new connection made.-Process= "TCP/FTP Server", ipl= 0, pid= 53Mar 3 10:21:10: FTPSRV_DEBUG:FTP Server file path: 'disk0:'Mar 3 10:21:10: FTPSRV_DEBUG:(REPLY) 220Mar 3 10:21:10: FTPSRV_DEBUG:FTProuter IOS-FTP server (version 1.00) ready.Mar 3 10:21:10: FTPSRV_DEBUG:FTP Server Command received: 'USER aa'Mar 3 10:21:20: FTPSRV_DEBUG:(REPLY) 331Mar 3 10:21:20: FTPSRV_DEBUG:Password required for 'aa'.Mar 3 10:21:20: FTPSRV_DEBUG:FTP Server Command received: 'PASS aa'Mar 3 10:21:21: FTPSRV_DEBUG:(REPLY) 230Mar 3 10:21:21: FTPSRV_DEBUG:Logged in.Mar 3 10:21:21: FTPSRV_DEBUG:FTP Server Command received: 'SYST'Mar 3 10:21:21: FTPSRV_DEBUG:(REPLY) 215Mar 3 10:21:21: FTPSRV_DEBUG:Cisco IOS Type: L8 Version: IOS/FTP 1.00Mar 3 10:21:21: FTPSRV_DEBUG:FTP Server Command received: 'PWD'Mar 3 10:21:35: FTPSRV_DEBUG:(REPLY) 257Mar 3 10:21:39: FTPSRV_DEBUG:FTP Server Command received: 'CWD disk0:/syslogd.d'r/'Mar 3 10:21:45: FTPSRV_DEBUG:FTP Server file path: 'disk0:/syslogd.dir'Mar 3 10:21:45: FTPSRV_DEBUG:(REPLY) 250Mar 3 10:21:45: FTPSRV_DEBUG:CWD command successful.Mar 3 10:21:45: FTPSRV_DEBUG:FTP Server Command received: 'PORT 171,69,30,20,22',32Mar 3 10:21:46: FTPSRV_DEBUG:(REPLY) 200Mar 3 10:21:46: FTPSRV_DEBUG:PORT command successful.Mar 3 10:21:46: FTPSRV_DEBUG:FTP Server Command received: 'LIST'Mar 3 10:21:47: FTPSRV_DEBUG:FTP Server file path: 'disk0:/syslogd.dir/.'Mar 3 10:21:47: FTPSRV_DEBUG:(REPLY) 220Mar 3 10:23:11: FTPSRV_DEBUG:Opening ASCII mode data connection for file list.Mar 3 10:23:11: FTPSRV_DEBUG:(REPLY) 226Mar 3 10:23:12: FTPSRV_DEBUG:Transfer complete.Mar 3 10:23:12: FTPSRV_DEBUG:FTP Server Command received: 'TYPE I'Mar 3 10:23:14: FTPSRV_DEBUG:(REPLY) 200Mar 3 10:23:14: FTPSRV_DEBUG:Type set to I.Mar 3 10:23:14: FTPSRV_DEBUG:FTP Server Command received: 'PORT 171,69,30,20,22',51Mar 3 10:23:20: FTPSRV_DEBUG:(REPLY) 200Mar 3 10:23:20: FTPSRV_DEBUG:PORT command successful.Mar 3 10:23:20: FTPSRV_DEBUG:FTP Server Command received: 'RETR syslogd.1'Mar 3 10:23:21: FTPSRV_DEBUG:FTP Server file path: 'disk0:/syslogd.dir/syslogd.1'Mar 3 10:23:21: FTPSRV_DEBUG:FTPSERVER: Input path passed Top-dir(disk0:/syslogd.dir/) test.Mar 3 10:23:21: FTPSRV_DEBUG:(REPLY) 150Mar 3 10:23:21: FTPSRV_DEBUG:Opening BINARY mode data connection for syslogd.1 (607317 bytes).Mar 3 10:23:21: FTPSRV_DEBUG:(REPLY) 226Mar 3 10:23:29: FTPSRV_DEBUG:Transfer complete.The sample output corresponds to the following FTP client session. In this example, the user connects to the FTP server, views the contents of the top-level directory, and gets a file.
FTPclient% ftp FTProuterConnected to FTProuter.cisco.com.220 FTProuter IOS-FTP server (version 1.00) ready.Name (FTProuter:me): aa331 Password required for 'aa'.Password:230 Logged in.Remote system type is Cisco.ftp> pwd257 "disk0:/syslogd.dir/" is current directory.ftp> dir200 PORT command successful.150 Opening ASCII mode data connection for file list.syslogd.1syslogd.2syslogd.3syslogd.4syslogd.5syslogd.6syslogd.7syslogd.8syslogd.9syslogd.cur226 Transfer complete.ftp> bin200 Type set to I.ftp> get syslogd.1200 PORT command successful.150 Opening BINARY mode data connection for syslogd.1 (607317 bytes).226 Transfer complete.607317 bytes received in 7.7 seconds (77 Kbytes/s)ftp>The following debug ftpserver command output indicates that no top-level directory is specified. Therefore, the client cannot access any location on the FTP server. Use the ftp-server topdir command to specify the top-level directory.
Mar 3 10:29:14: FTPSRV_DEBUG:(REPLY) 550Mar 3 10:29:14: FTPSRV_DEBUG:Access denied to 'disk0:'debug gatekeeper gup
To display the Gatekeeper Update Protocol (GUP) events or Abstract Syntax Notation 1 (ASN.1) details, use the debug gatekeeper gup command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug gatekeeper gup {events | asn1}
no debug gatekeeper gup {events | asn1}
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to enable a packet dump of all GUP announcement messages:
Router# debug gatekeeper gup asn100:10:21:ENCODE BUFFER::= 00 0A2A8648 86F70C0A 00000120 001E800186A08001 86A00547 656E6576 614E0000 00000142 80004700 65006E00 6500760061080050 00610072 00690073 00000000 000000:10:21:00:10:21:PDU ::=value GUP_Information ::=protocolIdentifier { 1 2 840 113548 10 0 0 1 }message announcementIndication :announcementInterval 30endpointCapacity 100000callCapacity 100000hostName '47656E657661'HpercentMemory 39percentCPU 0currentCalls 0currentEndpoints 0zoneInformationgatekeeperIdentifier {"Geneva"}altGKIdentifier {"Paris"}totalBandwidth 0interzoneBandwidth 0remoteBandwidth 0RAW_BUFFER::=00 0A2A8648 86F70C0A 00000120 001E800B 858A8001 86A00144 80007400 6F007200 6E006100 64006F00 2D006700 6B120063 00790063 006C006F 006E0065 002D0067 006B0000 00000000*Mar 3 15:40:31:*Mar 3 15:40:31:Sending GUP ANNOUNCEMENT INDICATION to 172.18.195.140RAW_BUFFER::=00 0A2A8648 86F70C0A 00000120 001E800A EF8A8001 86A00144 80006300 79006300 6C006F00 6E006500 2D006700 6B120074 006F0072 006E0061 0064006F 002D0067 006B0000 00000000*Mar 3 15:40:31:PDU DATA = 60EAB248value GUP_Information ::=protocolIdentifier { 1 2 840 113548 10 0 0 1 }message announcementIndication :{announcementInterval 30endpointCapacity 716682callCapacity 100000zoneInformationgatekeeperIdentifier {"cyclone-gk"}altGKIdentifier {"tornado-gk"}totalBandwidth 0interzoneBandwidth 0remoteBandwidth 0Mar 3 15:40:31:Received GUP ANNOUNCEMENT INDICATION from 172.18.195.140u allAll possible debugging has been turned offRelated Commands
debug gatekeeper load
To display gatekeeper load-balancing debug events, use the debug gatekeeper load command in privileged EXEC mode. To disable debugging output, use the no form of the command.
debug gatekeeper load {events}
no debug gatekeeper load {events}
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows output for the debug gatekeeper load command.
Note
Router# debug gatekeeper loadRouter#Router#Router# show debugginggk load-balancing debug level = EventsRouterk#Router#gk_load_overloaded:Overloaded, 5-second CPU utilization too highgk_load_overloaded:Overloaded due to excessive calls/endpointsgk_load_balance_endpt_request:load balance occurred. New load_balance_count=2Related Commands
debug gatekeeper server
To trace all the message exchanges between the Cisco IOS Gatekeeper and the external applications, use the debug gatekeeper server command from EXEC mode. Enter the no form of this command to disable debugging output.
debug gatekeeper server
no debug gatekeeper server
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to see information about a Gatekeeper server. This command shows any errors that occur in sending messages to the external applications or in parsing messages from the external applications.
Examples
The following example shows debugging information about a Gatekeeper server
Router# debug gatekeeper serversRouter# show debugGatekeeper:Gatekeeper Server Messages debugging is onTo turn the Gatekeeper server debugging message off, see the following examples:
Router# no debug allRouter# no debug Gatekeeper serversRelated Commands
show gatekeeper server
Displays information about the Gatekeeper servers configured on your network by ID.
debug glbp errors
To display debugging messages about Gateway Load Balancing Protocol (GLBP) error conditions, use the debug glbp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp errors
no debug glbp errors
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Examples
The following is sample output from the debug glbp errors command:
Router# debug glbp errorsGLBP Errors debugging is on1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not found1d19h: GLBP: Fa0/0 API active virtual address 10.21.8.32 not foundRelated Commands
debug condition glbp
Displays debugging messages about GLBP that match specific conditions.
debug glbp events
To display debugging messages about Gateway Load Balancing Protocol (GLBP) events that are occurring, use the debug glbp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp events [all | detail | terse]
no debug glbp events [all | detail | terse]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Examples
The following is sample output from the debug glbp events command when the terse keyword is specified:
Router# debug glbp events terseGLBP Events debugging is on(protocol, redundancy, track)Related Commands
debug condition glbp
Displays debugging messages about GLBP that match specific conditions.
debug glbp packets
To display summary information about Gateway Load Balancing Protocol (GLBP) packets being sent or received, use the debug glbp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp packets [all | detail | hello | reply | request | terse]
no debug glbp packets [all | detail | hello | reply | request | terse]
Syntax Description
Command Modes
Privileged EXEC
Command History
12.2(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Examples
The following sample output from the debug glbp packets command shows debugging output about GLBP hello packets:
Router# debug glbp packets helloGLBP Packets debugging is on(Hello)1d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 11d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 11d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 11d19h: GLBP: Fa0/0 Grp 10 Hello out 10.21.8.32 VG Active pri 254 vIP 10.21.8.10 1Related Commands
debug condition glbp
Displays debugging messages about GLBP that match specific conditions.
debug glbp terse
To display a limited range of debugging messages about Gateway Load Balancing Protocol (GLBP) errors, events, and packets, use the debug glbp terse command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug glbp terse
no debug glbp terse
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
12.2(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Examples
The following is sample output from the debug glbp terse command:
Router# debug glbp terseGLBP:GLBP Errors debugging is onGLBP Events debugging is on(protocol, redundancy, track)GLBP Packets debugging is on(Request, Reply)Related Commands
debug gprs charging
To display information about GPRS charging functions on the GGSN, use the debug gprs charging events command. To disable debugging output, use the no form of the command.
debug gprs charging {events | packets}
no debug gprs charging {events | packets}
Syntax Description
events
Displays events related to GPRS charging processing on the GGSN.
packets
Displays GPRS charging packets that are sent between the GGSN and the charging gateway.
Defaults
No default behavior or values.
Command History
12.1(1)GA
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
Usage Guidelines
This command is useful for system operators if problems are encountered with GPRS charging functions.
Caution
Examples
The following example enables the display of events related to GPRS charging events on the GGSN:
Router# debug gprs charging eventsThe following example enables the display of GPRS charging packets sent between the GGSN and the charging gateway:
Router# debug gprs charging eventsdebug gprs gtp
To display information about the GPRS Tunneling Protocol (GTP), use the debug gprs gtp command. To disable debugging output, use the no form of the command.
debug gprs gtp {events | messages | packets}
no debug gprs gtp {events | messages | packets}
Syntax Description
Defaults
No default behavior or values.
Command History
12.1(1)GA
This command was introduced.
12.1(3)T
This command was integrated in Cisco IOS Release 12.1(3)T.
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 signalling messages:
Router# debug gprs gtp messagesThe following example enables the display of GTP packets sent between the SGSN and GGSN:
Router# debug gprs gtp packets
