-
Cisco IOS Debug Command Reference, Release 12.3
-
Cisco IOS Debug Command Reference Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
Debug Commands: debug aaa accounting through debug appn nof
-
Debug Commands: debug appn pc through debug bundle events
-
Debug Commands: debug cable env through debug ccfrfll session
-
Debug Commands: debug cch323 through debug channel packets
-
Debug Commands: debug clns esis events through debug crypto pki messages
-
Debug Commands: debug crypto pki transactions through debug dlsw
-
Debug Commands: debug dmsp doc-to-fax through debug events
-
Debug Commands: debug fax relay t30 through debug gprs gtp
-
Debug Commands: debug h225 through debug ip drp
-
Debug Commands: debug ip dvmrp through debug ip mrouting
-
Debug Commands: debug ip msdp through debug ip scp
-
Debug Commands: debug ip sctp api through debug ip wccp packets
-
Debug Commands: debug ipv6 cef drop through debug 12relay packets
-
Debug Commands: debug lane client through debug mmoip transfer
-
Debug Commands: debug modem through debug mpls ldp targeted-neighbors
-
Debug Commands: debug mpls ldp transport connections through debug mpls xtagatm vc
-
Debug Commands: debug mpoa client through debug oam
-
Debug Commands: debug packet through debug redundancy
-
Debug Commands: debug redundancy as5850 through debug rudpv1
-
Debug Commands: debug saa apm through debug source error
-
Debug Commands: debug source event through debug tacacs events
-
Debug Commands: debug tag-switching atm-cos through debug tag-switching xtagatm vc
-
Debug Commands: debug tarp events through debug video vicm
-
Debug Commands: debug vlan packet through debug voip settlement enter
-
Debug Commands: debug voip settlement error through debug vpm all
-
Debug Commands: debug vpm dsp through debug vxml
-
Debug Commands: debug x25 through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug saa apm
To enable debugging output for the Service Assurance Agent (SAA) Application Performance Monitor (APM), use the debug saa apm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug saa apm
no debug saa apm
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug saa apm command:
Router# debug saa apmRouter# configure terminalRouter(config)# saa apm operation 123 start ftp://apm/config/iptv.cf21:40:27: SAA-APM-123: downloading file (apm/config/iptv.cf) of size (534)21:40:29: SAA-APM-123: downloading file (apm/scheduler/master.sch) of size (2500)21:40:30: SAA-APM-123: downloading file (apm/scripts/iptv.scr) of size (1647)21:40:32: SAA-APM-123: downloading file (apm/data/iptv.dat) of size (118)21:40:32: SAA-APM-123: sending APM_CAPABILITIES_REQUEST message21:40:32: sending control msg:21:40:32: Ver: 1 ID: 29 Len: 4821:40:32: SAA-APM-123: apm_engine version: major<1>, minor<0>21:40:32: SAA-APM-123: sending APM_SCRIPT_DNLD message21:40:32: sending control msg:21:40:32: Ver: 1 ID: 30 Len: 14821:40:37: SAA-APM-123: sending APM_SCRIPT_DNLD_STATUS message21:40:37: sending control msg:21:40:37: Ver: 1 ID: 31 Len: 14821:40:38: SAA-APM-123: starting the operation21:40:38: SAA-APM-123: sending APM_SCRIPT_START message21:40:38: sending control msg:21:40:38: Ver: 1 ID: 32 Len: 14821:40:41: SAA-APM: 0,2144,0...21:49:42: SAA-APM-123: waiting for ageout timer to expire21:55:13: SAA-APM-123: sending APM_SCRIPT_DONE message21:55:13: sending control msg:21:55:13: Ver: 1 ID: 42 Len: 14821:55:13: SAA-APM-123: operation doneRouter(config)# no saa apm operation 2921:55:13: SAA-APM-123: sending APM_SCRIPT_DONE message21:55:13: sending control msg:21:55:13: Ver: 1 ID: 42 Len: 14821:55:13: SAA-APM-123: operation donedebug saa slm
To enable the output of detailed event messages for Service Assurance Agent (SAA) ATM Service Level Monitoring (SLM), use the debug saa slm command in privileged EXEC mode. To disable debugging message output, use the no form of this command.
debug saa slm
no debug saa slm
Syntax Description
This command has no arguments or keywords.
Defaults
Debug message output is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command may generate a large number of debugging messages.
Examples
In the following example, debugging is enabled for the SAA ATM SLM feature and the SAA eXtensible Markup Language (XML) feature for the purposes of debugging the XML requests and responses:
Router# debug saa slmRouter# debug saa xmlRelated Commands
debug sccp
To display debugging information for Simple Client Control Protocol (SCCP) and its related applications (transcoding and conferencing), use the debug sccp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sccp {all | errors | events | packets | parser}
no debug sccp
Syntax Description
all
All SCCP debug-trace information.
errors
SCCP errors.
events
SCCP events.
packets
SCCP packets.
parser
SCCP parser and builder.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding and conferencing digital signal processor (DSP) farms (NM-HDV-FARMs) to provide DSP resources.
Debugging is turned on for all DSP farm service sessions. You can debug multiple sessions simultaneously, with different levels of debugging for each.
Examples
The following is sample output from the debug sccp events command:
Router# debug sccp eventsSkinny Client Control Protocol events debugging is on*Mar 1 00:46:29: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:46:29: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:29: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:46:29: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:46:30: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:46:30: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:30: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:30: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:46:37: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:46:37: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:37: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:46:37: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:46:37: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:46:37: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:38: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:38: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 28, offset 36, msg_id 261*Mar 1 00:46:43: xapp_open_receive_chnl: SCCP orc_msg - 6248FC8C, appl - 6248FC10*Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2769*Mar 1 00:46:43: xapp_add_chnl_rec: chnl 631142BC*Mar 1 00:46:43: xapp_add_sess_rec: Add sess_rec (63114360) record*Mar 1 00:46:43: xapp_open_receive_chnl: stat 0, eve 0, sid 27, cid 2769, codec 1, pkt-period 20*Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142BC*Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 0, nstate 1*Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142BC, state 1, eve_id 1*Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142BC*Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 1, nstate 2, lc_ipaddr 10.10.1.1, lport 21066*Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 28, offset 36, msg_id 261*Mar 1 00:46:43: xapp_open_receive_chnl: SCCP orc_msg - 6248FC8C, appl - 6248FC10*Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2785*Mar 1 00:46:43: xapp_add_chnl_rec: chnl 631142E4*Mar 1 00:46:43: xapp_open_receive_chnl: stat 0, eve 0, sid 27, cid 2785, codec 1, pkt-period 20*Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142E4*Mar 1 00:46:43: xapp_open_chnl_request: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 0, nstate 1*Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142E4, state 1, eve_id 1*Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142E4*Mar 1 00:46:43: xapp_open_chnl_success: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 1, nstate 2, lc_ipaddr 10.10.1.1, lport 25706*Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 44, offset 52, msg_id 138*Mar 1 00:46:43: xapp_start_media_transmission: SCCP stmt_msg - 6248FC8C, appl - 6248FC10*Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2769*Mar 1 00:46:43: xapp_start_media_transmission: chnl_rec 631142BC, stat 2, sid 27, cid 2769, ripaddr 10.10.1.5, rport 32148, codec 1, pkt-period 20, pre 11, silen 16777500, mfpp 1*Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142BC*Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 2, nstate 2*Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142BC, state 2, eve_id 4*Mar 1 00:46:43: xapp_modify_chnl_success: chnl_rec 631142BC, sess_id 27, conn_id 2769, cstate 2*Mar 1 00:46:43: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:43: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 44, offset 52, msg_id 138*Mar 1 00:46:43: xapp_start_media_transmission: SCCP stmt_msg - 6248FC8C, appl - 6248FC10*Mar 1 00:46:43: xapp_search_for_chnl_rec: sess_id 27, conn_id 2785*Mar 1 00:46:43: xapp_start_media_transmission: chnl_rec 631142E4, stat 2, sid 27, cid 2785, ripaddr 10.10.1.7, rport 16422, codec 1, pkt-period 20, pre 11, silen 16777501, mfpp 1*Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142E4*Mar 1 00:46:43: xapp_modify_chnl_request: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 2, nstate 2*Mar 1 00:46:43: xapp_dequeue_and_process_dspf_events: chnl_rec 631142E4, state 2, eve_id 4*Mar 1 00:46:43: xapp_modify_chnl_success: chnl_rec 631142E4, sess_id 27, conn_id 2785, cstate 2*Mar 1 00:46:44: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:46:44: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:45: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:46:45: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:46:45: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:46:45: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:46: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:46: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:46:47: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:47: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 28, offset 36, msg_id 261*Mar 1 00:46:47: xapp_open_receive_chnl: SCCP orc_msg - 6248FC8C, appl - 6248FC10*Mar 1 00:46:47: xapp_search_for_chnl_rec: sess_id 27, conn_id 2817*Mar 1 00:46:47: xapp_add_chnl_rec: chnl 6311430C*Mar 1 00:46:47: xapp_open_receive_chnl: stat 0, eve 0, sid 27, cid 2817, codec 1, pkt-period 20*Mar 1 00:46:47: xapp_open_chnl_request: chnl_rec 6311430C*Mar 1 00:46:47: xapp_open_chnl_request: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 0, nstate 1*Mar 1 00:46:47: xapp_dequeue_and_process_dspf_events: chnl_rec 6311430C, state 1, eve_id 1*Mar 1 00:46:47: xapp_open_chnl_success: chnl_rec 6311430C*Mar 1 00:46:47: xapp_open_chnl_success: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 1, nstate 2, lc_ipaddr 10.10.1.1, lport 16730*Mar 1 00:46:47: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:47: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 44, offset 52, msg_id 138*Mar 1 00:46:47: xapp_start_media_transmission: SCCP stmt_msg - 6248FC8C, appl - 6248FC10*Mar 1 00:46:47: xapp_search_for_chnl_rec: sess_id 27, conn_id 2817*Mar 1 00:46:47: xapp_start_media_transmission: chnl_rec 6311430C, stat 2, sid 27, cid 2817, ripaddr 10.10.1.6, rport 18160, codec 1, pkt-period 20, pre 11, silen 16777502, mfpp 1*Mar 1 00:46:47: xapp_modify_chnl_request: chnl_rec 6311430C*Mar 1 00:46:47: xapp_modify_chnl_request: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 2, nstate 2*Mar 1 00:46:47: xapp_dequeue_and_process_dspf_events: chnl_rec 6311430C, state 2, eve_id 4*Mar 1 00:46:47: xapp_modify_chnl_success: chnl_rec 6311430C, sess_id 27, conn_id 2817, cstate 2*Mar 1 00:46:52: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:46:52: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:52: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:46:52: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:46:53: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:46:53: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:46:54: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:46:54: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:46:59: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:46:59: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:00: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:47:00: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:47:01: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:47:01: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:01: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:47:01: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:47:07: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:47:07: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:07: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:47:07: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:47:08: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:47:08: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:09: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:47:09: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:47:14: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:47:14: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:15: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:47:15: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:47:16: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:47:16: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:16: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:47:16: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:47:22: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:47:22: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:22: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:47:22: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:47:23: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:47:23: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:24: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:47:24: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256*Mar 1 00:47:29: sccp_create_application: send keepalive msg, appl 6248F760, appl_type 1, count 0*Mar 1 00:47:29: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:30: sccp_process_mtp_pdu: appl - 6248F760, mbuf - 6248F7D4*Mar 1 00:47:30: sccp_process_mtp_pdu: msg_ptr 6248F7DC, len 4, offset 12, msg_id 256*Mar 1 00:47:31: sccp_create_application: send keepalive msg, appl 6248FC10, appl_type 2, count 0*Mar 1 00:47:31: sccp_keepalive: send keepalive id 0, len 4*Mar 1 00:47:31: sccp_process_mtp_pdu: appl - 6248FC10, mbuf - 6248FC84*Mar 1 00:47:31: sccp_process_mtp_pdu: msg_ptr 6248FC8C, len 4, offset 12, msg_id 256Related Commands
debug sdlc
To display information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions, use the debug sdlc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sdlc
no debug sdlc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Note
Because the debug sdlc command can generate many messages and alter timing in the network node, use it only when instructed by authorized support personnel.
Examples
The following is sample output from the debug sdlc command:
Router# debug sdlcSDLC: Sending RR at location 4Serial3: SDLC O (12495952) C2 CONNECT (2) RR P/F 6Serial3: SDLC I (12495964) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0]Serial3: SDLC T [C2] 12496064 CONNECT 12496064 0SDLC: Sending RR at location 4Serial3: SDLC O (12496064) C2 CONNECT (2) RR P/F 6Serial3: SDLC I (12496076) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0]Serial3: SDLC T [C2] 12496176 CONNECT 12496176 0The following line of output indicates that the router is sending a Receiver Ready packet at location 4 in the code:
SDLC: Sending RR at location 4The following line of output describes a frame output event:
Serial1/0: SDLC O 04 CONNECT (285) IFRAME P/F 6Table 219 describes the significant fields shown in the display.
The following line of output describes a frame input event:
Serial1/0: SDLC I 02 CONNECT (16) IFRAME P 7 0,[VR: 7 VS: 0]Table 220 describes the significant fields shown in the display.
The following line of output describes a frame timer event:
Serial1/0: SDLC T 02 CONNECT 0x9CB69E8 P 0Table 221 describes the significant fields shown in the display.
Related Commands
debug list
Filters debugging information on a per-interface or per-access list basis.
debug sdlc local-ack
To display information on the local acknowledgment feature, use the debug sdlc local-ack command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sdlc local-ack [number]
no debug sdlc local-ack [number]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
You can select the frame types you want to monitor; the frame types correspond to bit flags. You can select 1, 2, 4, or 7, which is the decimal value of the bit flag settings. If you select 1, the octet is set to 00000001. If you select 2, the octet is set to 0000010. If you select 4, the octet is set to 00000100. If you want to select all frame types, select 7; the octet is 00000111. The default is 7 for all events. Table 222 defines these bit flags.
Caution
Examples
The following is sample output from the debug sdlc local-ack command:
The first line shows the input to the SDLC local acknowledgment state machine:
SLACK (Serial3): Input = Network, LinkupRequestTable 223 describes the significant fields shown in the display.
The second line shows the change in the SDLC local acknowledgment state machine. In this case the AwaitSdlcOpen state is an internal state that has not changed while this display was captured.
SLACK (Serial3): Old State = AwaitSdlcOpen New State = AwaitSdlcOpenThe third line shows the output from the SDLC local acknowledgment state machine:
SLACK (Serial3): Output = SDLC, SNRMdebug sdlc packet
To display packet information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions, use the debug sdlc packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sdlc packet [max-bytes]
no debug sdlc packet [max-bytes]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
This command requires intensive CPU processing; therefore, we recommend not using it when the router is expected to handle normal network loads, such as in a production environment. Instead, use this command when network response is noncritical. We also recommend that you use this command by itself, rather than in conjunction with other debug commands.
Examples
The following is sample output from the debug sdlc packet command with the packet display limited to 20 bytes of data:
Router# debug sdlc packet 20Serial3 SDLC Output00000 C3842C00 02010010 019000C5 C5C5C5C5 Cd.........EEEEE00010 C5C5C5C5 EEEESerial3 SDLC Output00000 C3962C00 02010011 039020F2 Co.........2Serial3 SDLC Output00000 C4962C00 0201000C 039020F2 Do.........2Serial3 SDLC Input00000 C491 Dj
debug serial interface
To display information on a serial connection failure, use the debug serial interface command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug serial interface
no debug serial interface
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
If the show interface serial EXEC command shows that the line and protocol are down, you can use the debug serial interface command to isolate a timing problem as the cause of a connection failure. If the keepalive values in the mineseq, yourseen, and myseen fields are not incrementing in each subsequent line of output, there is a timing or line problem at one end of the connection.
Caution
The output of the debug serial interface command can vary, depending on the type of WAN configured for an interface: Frame Relay, High-Level Data Link Control (HDL) , High-Speed Serial Interface (HSSI), SMDS, or X.25. The output also can vary depending on the type of encapsulation configured for that interface. The hardware platform also can affect debug serial interface output.
Examples
The following sections show and describe sample debug serial interface output for various configurations.
Debug Serial Interface for Frame Relay Encapsulation
The following message is displayed if the encapsulation for the interface is Frame Relay (or HDLC) and the router attempts to send a packet containing an unknown packet type:
Illegal serial link type code xxxDebug Serial Interface for HDLC
The following is sample output from the debug serial interface command for an HDLC connection when keepalives are enabled. This output shows that the remote router is not receiving all the keepalives the router is sending. When the difference in the values in the myseq and mineseen fields exceeds three, the line goes down and the interface is reset.
Table 224 describes shown in the significant fields.
The previous example shows that after missing three keepalives, the line goes down and the interface is reset. However, the interface is also reset when two keepalives are missed, but the line is not marked as "down." This is done in an attempt to restart traffic on the interface without bringing the line down, as shown in the following output:
*Mar 18 08:07:29.057: Serial3/2: HDLC myseq 604562, mineseen 604562, yourseen 259336, line up*Mar 18 08:07:39.053: Serial3/2: HDLC myseq 604563, mineseen 604563, yourseen 259337, line up*Mar 18 08:07:49.081: Serial3/2: HDLC myseq 604564, mineseen 604564, yourseen 259338, line up*Mar 18 08:07:59.057: Serial3/2: HDLC myseq 604565, mineseen 604565, yourseen 259339, line up*Mar 18 08:08:09.073: Serial3/2: HDLC myseq 604566, mineseen 604565, yourseen 259340, line up*Mar 18 08:08:19.057: Serial3/2: Reset from PC 0x6DEA0*Mar 18 08:08:19.061: Serial3/2: HDLC myseq 604567, mineseen 604565, yourseen 259341, line up*Mar 18 08:08:29.057: Serial3/2: HDLC myseq 604568, mineseen 604568, yourseen 259342, line up*Mar 18 08:08:39.061: Serial3/2: HDLC myseq 604569, mineseen 604569, yourseen 259343, line up*Mar 18 08:08:49.065: Serial3/2: HDLC myseq 604570, mineseen 604570, yourseen 259344, line up*Mar 18 08:08:59.053: Serial3/2: HDLC myseq 604571, mineseen 604571, yourseen 259345, line upEven though the "Reset from PC" message appears to occur when there is only a difference of 1 between myseq and mineseen, this message applies to the condition shown in the immediately following line (notice that the timestamp is only a few milliseconds later) where the difference is 2. After the reset, the line has recovered and the difference between myseq and mineseen is zero.
Table 225 describes additional error messages that the debug serial interface command can generate for HDLC.
Debug Serial Interface for HSSI
On an HSSI interface, the debug serial interface command can generate the following additional error message:
HSSI0: Reset from 0xnnnnnnnThis message indicates that the HSSI hardware has been reset. The 0xnnnnnnn variable is the address of the routine requesting that the hardware be reset; this value is useful only to development engineers.
Debug Serial Interface for ISDN Basic Rate
Table 226 describes error messages that the debug serial interface command can generate for ISDN Basic Rate.
Debug Serial Interface for an MK5025 Device
Table 227 describes the additional error messages that the debug serial interface command can generate for an MK5025 device.
Debug Serial Interface for SMDS Encapsulation
When encapsulation is set to SMDS, the debug serial interface command displays SMDS packets that are sent and received, and any error messages resulting from SMDS packet transmission.
The error messages that the debug serial interface command can generate for SMDS follow.
The following message indicates that a new protocol requested SMDS to encapsulate the data for transmission. SMDS is not yet able to encapsulate the protocol.
SMDS: Error on Serial 0, encapsulation bad protocol = xThe following message indicates that SMDS was asked to encapsulate a packet, but no corresponding destination E.164 SMDS address was found in any of the static SMDS tables or in the ARP tables:
SMDS send: Error in encapsulation, no hardware address, type = xThe following message indicates that a protocol such as Connectionless Network Service (CLNS) or IP has been enabled on an SMDS interface, but the corresponding multicast addresses have not been configured. The n variable displays the link type for which encapsulation was requested.
SMDS: Send, Error in encapsulation, type=nThe following messages can occur when a corrupted packet is received on an SMDS interface. The router expected x, but received y.
SMDS: Invalid packet, Reserved NOT ZERO, x ySMDS: Invalid packet, TAG mismatch x ySMDS: Invalid packet, Bad TRAILER length x yThe following messages can indicate an invalid length for an SMDS packet:
SMDS: Invalid packet, Bad BA length xSMDS: Invalid packet, Bad header extension length xSMDS: Invalid packet, Bad header extension type xSMDS: Invalid packet, Bad header extension value xThe following messages are displayed when the debug serial interface command is enabled:
Interface Serial 0 Sending SMDS L3 packet:SMDS: dgsize:x type:0xn src:y dst:zIf the debug serial interface command is enabled, the following message can be displayed when a packet is received on an SMDS interface, but the destination SMDS address does not match any on that interface:
SMDS: Packet n, not addressed to usdebug serial packet
To display more detailed serial interface debugging information than you can obtain using the debug serial interface command, use the debug serial packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug serial packet
no debug serial packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug serial packet command generates output that is dependent on the type of serial interface and the encapsulation running on that interface. The hardware platform also can impact debug serial packet output.
The debug serial packet command displays output for only Switched Multimegabit Data Service (SMDS) encapsulations.
Examples
The following is sample output from the debug serial packet command when SMDS is enabled on the interface:
Router# debug serial packetInterface Serial2 Sending SMDS L3 packet:SMDS Header: Id: 00 RSVD: 00 BEtag: EC Basize: 0044Dest:E18009999999FFFF Src:C12015804721FFFF Xh:04030000030001000000000000000000SMDS LLC: AA AA 03 00 00 00 80 38SMDS Data: E1 19 01 00 00 80 00 00 0C 00 38 1F 00 0A 00 80 00 00 0C 01 2B 71SMDS Data: 06 01 01 0F 1E 24 00 EC 00 44 00 02 00 00 83 6C 7D 00 00 00 00 00SMDS Trailer: RSVD: 00 BEtag: EC Length: 0044As the output shows, when encapsulation is set to SMDS, the debug serial packet command displays the entire SMDS header (in hexadecimal notation), and some payload data on transmit or receive. This information is useful only when you have an understanding of the SMDS protocol. The first line of the output indicates either Sending or Receiving.
debug service-module
To display debugging information that monitors the detection and clearing of network alarms on the integrated channel service unit/data service unit (CSU/DSU) modules, use the debug service-module command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug service-module
no debug service-module
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command to enable and disable debug logging for the serial 0 and serial 1 interfaces when an integrated CSU/DSU is present. This command enables debugging on all interfaces.
Network alarm status can also be viewed through the use of the show service-module command.
Note
Examples
The following is sample output from the debug service-module command:
Router# debug service-moduleSERVICE_MODULE(1): loss of signal ended after duration 00:05:36SERVICE_MODULE(1): oos/oof ended after duration 01:05:14SERVICE_MODULE(0): Unit has no clockSERVICE_MODULE(0): detects loss of signalSERVICE_MODULE(0): loss of signal ended after duration 00:00:33debug sgbp dial-bids
To display large-scale dial-out negotiations between the primary network access server (NAS) and alternate NASs, use the debug sgbp dial-bids command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sgbp dial-bids
no debug sgbp dial-bids
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Use this command only when the sgbp dial-bids command has been configured.
Examples
The following is sample output from the debug sgbp dial-bids command:
Router# debug sgbp dial-bids*Jan 1 00:25:03.643: SGBP-RES: New bid add request: 4B0 8 2 1 DAC0 1 1This indicates a new dialout bid has started.*Jan 1 00:25:03.643: SGBP-RES: Sent Discover message to ID 7B09B71E 49 bytesThe bid request has been sent.*Jan 1 00:25:03.647: SGBP-RES: Received Message of 49 length:*Jan 1 00:25:03.647: SGBP-RES: header 5 30 0 312 0 0 2D 0 0 0 0 0 0 0 3 0 0 0 1 1E AF 3A 41 7B 9 B7 1E 8 15 B 3 2 C 6 0 0 DA C0 D 4 0 0 E 3 1 F 3 1*Jan 1 00:25:03.647:*Jan 1 00:25:03.647: SGBP RES: Scan: Message type: Offer*Jan 1 00:25:03.647: SGBP RES: Scan: Len is 45*Jan 1 00:25:03.647: SGBP RES: Scan: Transaction ID: 3*Jan 1 00:25:03.647: SGBP RES: Scan: Message ID: 1*Jan 1 00:25:03.647: SGBP RES: Scan: Client ID: 1EAF3A41*Jan 1 00:25:03.651: SGBP RES: Scan: Server ID: 7B09B71E*Jan 1 00:25:03.651: SGBP RES: Scan: Resource type 8 length 21*Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Media type: ISDN*Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Min BW: 56000*Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Num Links: 0*Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port User class: 1*Jan 1 00:25:03.651: SGBP RES: Scan: Phy-Port Priority: 1*Jan 1 00:25:03.651: SGBP-RES: received 45 length Offer packet*Jan 1 00:25:03.651: SGBP-RES: Offer from 7B09B71E for Transaction 3 accepted*Jan 1 00:25:03.651: SGBP RES: Server is uncongested. Immediate winAn alternate network access server has responded and won the bid.*Jan 1 00:25:03.651: SGBP-RES: Bid Succeeded handle 7B09B71E Server-id 4B0*Jan 1 00:25:03.651: SGBP-RES: Sent Dial-Req message to ID 7B09B71E 66 bytesThe primary network access server has asked the alternate server to dial.*Jan 1 00:25:04.651: SGBP-RES: QScan: Purging entry*Jan 1 00:25:04.651: SGBP-RES: deleting entry 6112E204 1EAF3A41 from list...debug sgbp error
To enable the display of debug messages about routing problems between members of a stack group, use the debug sgbp error command in privileged EXEC mode. To disable debug messages about routing problems between members of a stack group, use the no form of this command.
debug sgbp error
no debug sgbp error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Enable the debug sgbp error command to enable the display of debug messages about routing problems between members of a stack group.
Note
Examples
One common configuration error is setting a source IP address for a stack member that does not match the locally defined IP address for the same stack member. The following debug output shows the error message that results from this misconfiguration:
Systema# debug sgbp error%SGBP-7-DIFFERENT - systemb's addr 10.1.1.2 is different from hello's addr 10.3.4.5This error means that the source IP address of the Stack Group Bidding Protocol (SGBP) hello message received from systemb does not match the IP address configured locally for systemb (through the sgbp member command). Correct this configuaration error by going to systemb and checking for multiple interfaces by which the SGBP hello can send the message.
Another common error message is:
Systema# debug sgbp error%SGBP-7-MISCONF, Possible misconfigured member routerk (10.1.1.6)This error message means that routerk is not defined locally, but is defined on another stack member. Correct this configuration error by defining routerk across all members of the stack group using the sgbp member command.
The following error message indicates that an SGBP peer is leaving the stack group:
Systema# debug sgbp error%SGBP-7-LEAVING:Member systemc leaving group stack1This error message indicates that the peer systemc is leaving the stack group. Systemc could be leaving the stack group intentionally, or a connectivity problem may exist.
The following error message indicates that an SGBP event was detected from an unknown peer:
Systema# debug sgbp error%SGBP-7-UNKNOWPEER:Event 0x10 from peer at 172.21.54.3An SGBP event came from a network host that was not recognizable as an SGBP peer. Check to see if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewalling of your network, SGBP packets from a nonpeer host could indicate probing and attempts to breach security.
Caution
Related Commands
debug sgbp hellos
To enable the display of debug messages for authentication between stack group members, use the debug sgbp hellos command in privileged EXEC mode. To disable debug messages about authentication between stack group members, use the no form of this command
debug sgbp hellos
no debug sgbp hellos
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Enable the debug sgbp hellos command to enable the display of debug messages for authentication between routers configured as members of a stack group.
Note
Examples
The following output from the debug sgbp hellos command shows systema sending a successful Challenge Handshake Authentication Protocol (CHAP) challenge to and receiving a response from systemb. Similarly, systemb sends out a challenge and receives a response from systema:
systema# debug sgbp hellos%SGBP-7-CHALLENGE: Send Hello Challenge to systemb group stack1%SGBP-7-CHALLENGED: Hello Challenge message from member systemb (10.1.1.2)%SGBP-7-RESPONSE: Send Hello Response to systemb group stack1%SGBP-7-CHALLENGE: Send Hello Challenge to systemb group stack1%SGBP-7-RESPONDED: Hello Response message from member systemb (10.1.1.2)%SGBP-7-AUTHOK: Send Hello Authentication OK to member systemb (10.1.1.2)%SGBP-7-INFO: Addr = 10.1.1.2 Reference = 0xC347DF7%SGBP-5-ARRIVING: New peer event for member systembThis debug output is self-explanitory.
If authentication fails, you may see one of the following messages in your debug output:
%SGBP-7-AUTHFAILED - Member systemb failed authenticationThis error message means that the remote systemb password for the stack group does not match the password defined on systema. To correct this error, make sure that both systema and systemb have the same password defined using the username command.
%SGBP-7-NORESP -Fail to respond to systemb group stack1, may not have password.This error message means that systema does not have a username or password defined. To correct this error, define a common group password across all stack members using the username command.
Related Commands
debug sgcp
To debug the Simple Gateway Control Protocol (SGCP), use the debug sgcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sgcp {errors | events | packet}
no debug sgcp {errors | events | packet}
Syntax Description
errors
Displays debug information about SGCP errors.
events
Displays debug information about SGCP events.
packet
Displays debug information about SGCP packets.
Command Modes
Privileged EXEC
Command History
12.0(5)T
This command was introduced.
12.0(7)T
Support for this command was extended to the Cisco uBR924 cable access router.
Examples
See the following examples to enable and disable debugging at the specified level:
Router# debug sgcp errorsSimple Gateway Control Protocol errors debugging is onRouter# no debug sgcp errorsSimple Gateway Control Protocol errors debugging is offRouter#Router# debug sgcp eventsSimple Gateway Control Protocol events debugging is onRouter# no debug sgcp eventsSimple Gateway Control Protocol events debugging is offRouter#Router# debug sgcp packetSimple Gateway Control Protocol packets debugging is onRouter# no debug sgcp packetSimple Gateway Control Protocol packets debugging is offRouter#Related Commands
debug sgcp errors
To debug Simple Gateway Control Protocol (SGCP) errors, use the debug sgcp errors command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sgcp errors [endpoint string]
no debug sgcp errors
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the debugging of SGCP errors being enabled:
Router# debug sgcp errorsSimple Gateway Control Protocol errors debugging is onno errors since call went through successfully.The following example shows a debug trace for SGCP errors on a specific endpoint:
Router# debug sgcp errors endpoint DS1-0/1End point name for error debug:DS1-0/1 (1)00:08:41:DS1 = 0, DS0 = 100:08:41:Call record found00:08:41:Enable error end point debug for (DS1-0/1)Related Commands
debug sgcp events
To debug Simple Gateway Control Protocol (SGCP) events, use the debug sgcp events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sgcp events [endpoint string]
no debug sgcp events
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows a debug trace for SGCP events on a specific endpoint:
Router# debug sgcp events endpoint DS1-0/1End point name for event debug:DS1-0/1 (1)00:08:54:DS1 = 0, DS0 = 100:08:54:Call record found00:08:54:Enable event end point debug for (DS1-0/1)The following example shows a debug trace for all SGCP events on a gateway:
Router# debug sgcp events*Mar 1 01:13:31.035:callp :19196BC, state :0, call ID :-1, event :23*Mar 1 01:13:31.035:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msgNTFY send to ipaddr=1092E01 port=2427*Mar 1 01:13:31.039:Push msg into SGCP wait ack queue* (1)[25]*Mar 1 01:13:31.039:Timed Out interval [1]:(2000)*Mar 1 01:13:31.039:Timed Out interval [1]:(2000)(0):E[25]*Mar 1 01:13:31.075:Removing msg :NTFY 25 ds1-1/13@mc1 SGCP 1.1X:358258758O:hd*Mar 1 01:13:31.075:Unqueue msg from SGCP wait ack q** (0)[25]DS1 = 1, DS0 = 13*Mar 1 01:13:31.091:callp :19196BC, vdbptr :1964EEC, state :1*Mar 1 01:13:31.091:Checking ack (trans ID 237740140) :*Mar 1 01:13:31.091:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:31.091:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x20000004, event2=0xC*Mar 1 01:13:31.091:Same digit map is download (ds1-1/13@mc1)*Mar 1 01:13:31.091:R:requested trans_id (237740140)*Mar 1 01:13:31.091:process_signal_ev:seizure possible=1, signal mask=0x4, mask2=0x0*Mar 1 01:13:32.405:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.489:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:32.610:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.670:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:32.766:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.810:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:32.931:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:32.967:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.087:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.132:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.240:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.280:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.389:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.433:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.537:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.581:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.702:SGCP Session Appl:ignore CCAPI event 10*Mar 1 01:13:33.742:callp :19196BC, state :1, call ID :16, event :9*Mar 1 01:13:33.742:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msgNTFY send to ipaddr=1092E01 port=2427*Mar 1 01:13:33.742:Push msg into SGCP wait ack queue* (1)[26]*Mar 1 01:13:33.742:Timed Out interval [1]:(2000)*Mar 1 01:13:33.742:Timed Out interval [1]:(2000)(0):E[26]*Mar 1 01:13:33.786:Removing msg :NTFY 26 ds1-1/13@mc1 SGCP 1.1X:440842371O:k0, 4081037, s0*Mar 1 01:13:33.786:Unqueue msg from SGCP wait ack q** (0)[26]DS1 = 1, DS0 = 13*Mar 1 01:13:33.802:callp :19196BC, vdbptr :1964EEC, state :1*Mar 1 01:13:33.802:Checking ack (trans ID 698549528) :*Mar 1 01:13:33.802:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:33.802:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x4, event2=0x0*Mar 1 01:13:33.802:R:requested trans_id (698549528)*Mar 1 01:13:33.802:set_up_voip_call_leg:peer_addr=0, peer_port=0.*Mar 1 01:13:33.806:call_setting_crcx:Enter CallProceeding state rc = 0, call_id=16*Mar 1 01:13:33.806:callp :19196BC, state :4, call ID :16, event :31*Mar 1 01:13:33.810:callp :1AF5798, state :2, call ID :17, event :8call_pre_bridge!*Mar 1 01:13:33.810:send_oc_create_ack:seizure_possiblle=1, ack-lready-sent=0, ack_send=0*Mar 1 01:13:33.814:callp :1AF5798, state :4, call ID :17, event :28*Mar 1 01:13:33.814:Call Connect:Raw Msg ptr=0x1995360, no-offhook=0; call-id=17*Mar 1 01:13:33.814:SGCP Session Appl:ignore CCAPI event 37*Mar 1 01:13:33.947:callp :19196BC, state :5, call ID :16, event :32process_nse_on_origDS1 = 1, DS0 = 13*Mar 1 01:13:34.007:callp :19196BC, vdbptr :1964EEC, state :5*Mar 1 01:13:34.007:Checking ack (trans ID 123764791) :*Mar 1 01:13:34.007:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:34.007:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x4, event2=0x0*Mar 1 01:13:34.007:R:requested trans_id (123764791)*Mar 1 01:13:34.007:process_signal_ev:seizure possible=1, signal mask=0x0, mask2=0x0*Mar 1 01:13:34.007:modify_connection:echo_cancel=1.*Mar 1 01:13:34.007:modify_connection:vad=0.*Mar 1 01:13:34.007:modify_connection:peer_addr=6000001, peer_port=0->16500.*Mar 1 01:13:34.007:modify_connection:conn_mode=2.*Mar 1 01:13:34.011:callp :19196BC, state :5, call ID :16, event :31*Mar 1 01:13:34.011:callp :1AF5798, state :5, call ID :17, event :31process_nse_event*Mar 1 01:13:34.051:callp :19196BC, state :5, call ID :16, event :39*Mar 1 01:13:34.051:call_id=16, ignore_ccapi_ev:ignore 19 for state 5DS1 = 1, DS0 = 13*Mar 1 01:13:39.497:callp :19196BC, vdbptr :1964EEC, state :5*Mar 1 01:13:39.497:Checking ack (trans ID 553892443) :*Mar 1 01:13:39.497:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:13:39.497:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x8, signal2=0x0,event=0x4, event2=0x0*Mar 1 01:13:39.497:R:requested trans_id (553892443)*Mar 1 01:13:39.497:process_signal_ev:seizure possible=1, signal mask=0x0, mask2=0x0*Mar 1 01:13:39.497:modify_connection:echo_cancel=1.*Mar 1 01:13:39.497:modify_connection:vad=0.*Mar 1 01:13:39.497:modify_connection:peer_addr=6000001, peer_port=16500->16500.*Mar 1 01:13:39.497:modify_connection:conn_mode=3.*Mar 1 01:13:39.497:callp :19196BC, state :5, call ID :16, event :31*Mar 1 01:13:39.501:callp :1AF5798, state :5, call ID :17, event :31*Mar 1 01:14:01.168:Removing ack (trans ID 237740140) :200 237740140 OK*Mar 1 01:14:03.883:Removing ack (trans ID 698549528) :200 698549528 OKI:7v=0c=IN IP4 5.0.0.1m=audio 16400 RTP/AVP 0*Mar 1 01:14:04.087:Removing ack (trans ID 123764791) :200 123764791 OKI:7v=0c=IN IP4 5.0.0.1m=audio 16400 RTP/AVP 0*Mar 1 01:14:09.573:Removing ack (trans ID 553892443) :200 553892443 OKI:7v=0c=IN IP4 5.0.0.1m=audio 16400 RTP/AVP 0*Mar 1 01:14:48.091:callp :19196BC, state :5, call ID :16, event :12*Mar 1 01:14:48.091:voice_if->call_agent_ipaddr used as Notify entityNotify entity available for Tx SGCP msgNTFY send to ipaddr=1092E01 port=2427*Mar 1 01:14:48.091:Push msg into SGCP wait ack queue* (1)[27]*Mar 1 01:14:48.091:Timed Out interval [1]:(2000)*Mar 1 01:14:48.091:Timed Out interval [1]:(2000)(0):E[27]*Mar 1 01:14:48.128:Removing msg :NTFY 27 ds1-1/13@mc1 SGCP 1.1X:97849341O:hu*Mar 1 01:14:48.128:Unqueue msg from SGCP wait ack q** (0)[27]DS1 = 1, DS0 = 13*Mar 1 01:14:48.212:callp :19196BC, vdbptr :1964EEC, state :5*Mar 1 01:14:48.212:Checking ack (trans ID 79307869) :*Mar 1 01:14:48.212:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:14:48.212:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x4, signal2=0x0,event=0x0, event2=0x0*Mar 1 01:14:48.212:delete_call:callp:19196BC, call ID:16*Mar 1 01:14:48.212:sgcp delete_call:Setting disconnect_by_dlcx to 1*Mar 1 01:14:48.216:callp :1AF5798, state :6, call ID :17, event :29*Mar 1 01:14:48.216:Call disconnect:Raw Msg ptr = 0x0, call-id=17*Mar 1 01:14:48.216:disconnect_call_leg O.K. call_id=17*Mar 1 01:14:48.216:SGCP:Call disconnect:No need to send onhook*Mar 1 01:14:48.216:Call disconnect:Raw Msg ptr = 0x19953B0, call-id=16*Mar 1 01:14:48.216:disconnect_call_leg O.K. call_id=16*Mar 1 01:14:48.220:callp :1AF5798, state :7, call ID :17, event :13*Mar 1 01:14:48.220:Processing DLCX signal request :4, 0, 0*Mar 1 01:14:48.220:call_disconnected:call_id=17, peer 16 is not idle yet.DS1 = 1, DS0 = 13*Mar 1 01:14:48.272:callp :19196BC, vdbptr :1964EEC, state :7*Mar 1 01:14:48.272:Checking ack (trans ID 75540355) :*Mar 1 01:14:48.272:is_capability_ok:caps.codec=5, caps.pkt=10, caps.nt=8*Mar 1 01:14:48.272:is_capability_ok:supported signal=0x426C079C, signal2=0x80003,event=0x6003421F, event2=0x3FDrequested signal=0x0, signal2=0x0,event=0x8, event2=0x0*Mar 1 01:14:48.272:R:requested trans_id (75540355)*Mar 1 01:14:48.272:process_signal_ev:seizure possible=1, signal mask=0x4, mask2=0x0*Mar 1 01:14:49.043:callp :19196BC, state :7, call ID :16, event :27*Mar 1 01:14:49.043:process_call_feature:Onhook event*Mar 1 01:14:49.043:callp :19196BC, state :7, call ID :16, event :13*Mar 1 01:15:18.288:Removing ack (trans ID 79307869) :250 79307869 OK*Mar 1 01:15:18.344:Removing ack (trans ID 75540355) :200 75540355 OKRelated Commands
debug sgcp packet
To debug the Simple Gateway Control Protocol (SGCP), use the debug sgcp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sgcp packet [endpoint string]
no debug sgcp packet
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows a debug trace for SGCP packets on a specific endpoint:
Router# debug sgcp packet endpoint DS1-0/1End point name for packet debug:DS1-0/1 (1)00:08:14:DS1 = 0, DS0 = 100:08:14:Enable packet end point debug for (DS1-0/1)The following example shows a debug trace for all SGCP packets on a gateway:
Router# debug sgcp packet*Mar 1 01:07:45.204:SUCCESS:Request ID string building is OK*Mar 1 01:07:45.204:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:45.204:SUCCESS:SGCP message building OK*Mar 1 01:07:45.204:SUCCESS:END of building*Mar 1 01:07:45.204:SGCP Packet sent --->NTFY 22 ds1-1/13@mc1 SGCP 1.1X:550092018O:hd<---*Mar 1 01:07:45.204:NTFY Packet sent successfully.*Mar 1 01:07:45.240:Packet received -200 22*Mar 1 01:07:45.244:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:45.244:SUCCESS:END of Parsing*Mar 1 01:07:45.256:Packet received -RQNT 180932866 ds1-1/13@mc1 SGCP 1.1X:362716780R:hu,k0(A),s0(N),[0-9T](A) (D)D:(9xx|xxxxxxx)*Mar 1 01:07:45.256:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:45.256:SUCCESS:Request ID string(362716780) parsing is OK*Mar 1 01:07:45.260:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:45.260:SUCCESS:Digit Map parsing is OK*Mar 1 01:07:45.260:SUCCESS:END of Parsing*Mar 1 01:07:45.260:SUCCESS:SGCP message building OK*Mar 1 01:07:45.260:SUCCESS:END of building*Mar 1 01:07:45.260:SGCP Packet sent --->200 180932866 OK<---*Mar 1 01:07:47.915:SUCCESS:Request ID string building is OK*Mar 1 01:07:47.915:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:47.919:SUCCESS:SGCP message building OK*Mar 1 01:07:47.919:SUCCESS:END of building*Mar 1 01:07:47.919:SGCP Packet sent --->NTFY 23 ds1-1/13@mc1 SGCP 1.1X:362716780O:k0, 4081037, s0<---*Mar 1 01:07:47.919:NTFY Packet sent successfully.*Mar 1 01:07:47.955:Packet received -200 23*Mar 1 01:07:47.955:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:47.955:SUCCESS:END of Parsing*Mar 1 01:07:47.971:Packet received -CRCX 938694984 ds1-1/13@mc1 SGCP 1.1M:recvonlyL:p:10,e:on,s:off, a:G.711uR:huC:6*Mar 1 01:07:47.971:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:47.971:SUCCESS:Connection Mode parsing is OK*Mar 1 01:07:47.971:SUCCESS:Packet period parsing is OK*Mar 1 01:07:47.971:SUCCESS:Echo Cancellation parsing is OK*Mar 1 01:07:47.971:SUCCESS:Silence Supression parsing is OK*Mar 1 01:07:47.971:SUCCESS:CODEC strings parsing is OK*Mar 1 01:07:47.971:SUCCESS:Local Connection option parsing is OK*Mar 1 01:07:47.971:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:47.975:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:07:47.975:SUCCESS:END of Parsing*Mar 1 01:07:47.979:SUCCESS:Conn ID string building is OK*Mar 1 01:07:47.979:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:47.979:SUCCESS:SGCP message building OK*Mar 1 01:07:47.979:SUCCESS:END of building*Mar 1 01:07:47.979:SGCP Packet sent --->200 938694984 OKI:6v=0c=IN IP4 5.0.0.1m=audio 16538 RTP/AVP 0<---*Mar 1 01:07:48.188:Packet received -MDCX 779665338 ds1-1/13@mc1 SGCP 1.1I:6M:recvonlyL:p:10,e:on,s:off,a:G.711uR:huC:6v=0c=IN IP4 6.0.0.1m=audio 16392 RTP/AVP 0*Mar 1 01:07:48.188:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:48.188:SUCCESS:Conn ID string(6) parsing is OK*Mar 1 01:07:48.192:SUCCESS:Connection Mode parsing is OK*Mar 1 01:07:48.192:SUCCESS:Packet period parsing is OK*Mar 1 01:07:48.192:SUCCESS:Echo Cancellation parsing is OK*Mar 1 01:07:48.192:SUCCESS:Silence Supression parsing is OK*Mar 1 01:07:48.192:SUCCESS:CODEC strings parsing is OK*Mar 1 01:07:48.192:SUCCESS:Local Connection option parsing is OK*Mar 1 01:07:48.192:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:48.192:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:07:48.192:SUCCESS:SDP Protocol version parsing OK*Mar 1 01:07:48.192:SUCCESS:SDP Conn Data OK*Mar 1 01:07:48.192:SUCCESS:END of Parsing*Mar 1 01:07:48.200:SUCCESS:Conn ID string building is OK*Mar 1 01:07:48.200:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:48.200:SUCCESS:SGCP message building OK*Mar 1 01:07:48.200:SUCCESS:END of building*Mar 1 01:07:48.200:SGCP Packet sent --->200 779665338 OKI:6v=0c=IN IP4 5.0.0.1m=audio 16538 RTP/AVP 0<---*Mar 1 01:07:53.674:Packet received -MDCX 177780432 ds1-1/13@mc1 SGCP 1.1I:6M:sendrecvX:519556004L:p:10,e:on, s:off,a:G.711uC:6R:huS:hdv=0c=IN IP4 6.0.0.1m=audio 16392 RTP/AVP 0*Mar 1 01:07:53.674:SUCCESS:SGCP Header parsing was OK*Mar 1 01:07:53.674:SUCCESS:Conn ID string(6) parsing is OK*Mar 1 01:07:53.674:SUCCESS:Connection Mode parsing is OK*Mar 1 01:07:53.674:SUCCESS:Request ID string(519556004) parsing is OK*Mar 1 01:07:53.678:SUCCESS:Packet period parsing is OK*Mar 1 01:07:53.678:SUCCESS:Echo Cancellation parsing is OK*Mar 1 01:07:53.678:SUCCESS:Silence Supression parsing is OK*Mar 1 01:07:53.678:SUCCESS:CODEC strings parsing is OK*Mar 1 01:07:53.678:SUCCESS:Local Connection option parsing is OK*Mar 1 01:07:53.678:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:07:53.678:SUCCESS:Requested Event parsing is OK*Mar 1 01:07:53.678:SUCCESS:Signal Requests parsing is OK*Mar 1 01:07:53.678:SUCCESS:SDP Protocol version parsing OK*Mar 1 01:07:53.678:SUCCESS:SDP Conn Data OK*Mar 1 01:07:53.678:SUCCESS:END of Parsing*Mar 1 01:07:53.682:SUCCESS:Conn ID string building is OK*Mar 1 01:07:53.682:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:07:53.682:SUCCESS:SGCP message building OK*Mar 1 01:07:53.682:SUCCESS:END of building*Mar 1 01:07:53.682:SGCP Packet sent --->200 177780432 OKI:6v=0c=IN IP4 5.0.0.1m=audio 16538 RTP/AVP 0<---*Mar 1 01:09:02.401:SUCCESS:Request ID string building is OK*Mar 1 01:09:02.401:SUCCESS:Building SGCP Parameter lines is OK*Mar 1 01:09:02.401:SUCCESS:SGCP message building OK*Mar 1 01:09:02.401:SUCCESS:END of building*Mar 1 01:09:02.401:SGCP Packet sent --->NTFY 24 ds1-1/13@mc1 SGCP 1.1X:519556004O:hu<---*Mar 1 01:09:02.401:NTFY Packet sent successfully.*Mar 1 01:09:02.437:Packet received -200 24*Mar 1 01:09:02.441:SUCCESS:SGCP Header parsing was OK*Mar 1 01:09:02.441:SUCCESS:END of Parsing*Mar 1 01:09:02.541:Packet received -DLCX 865375036 ds1-1/13@mc1 SGCP 1.1C:6S:hu*Mar 1 01:09:02.541:SUCCESS:SGCP Header parsing was OK*Mar 1 01:09:02.541:SUCCESS:Call ID string(6) parsing is OK*Mar 1 01:09:02.541:SUCCESS:Signal Requests parsing is OK*Mar 1 01:09:02.541:SUCCESS:END of Parsing*Mar 1 01:09:02.545:SUCCESS:SGCP message building OK*Mar 1 01:09:02.545:SUCCESS:END of building*Mar 1 01:09:02.545:SGCP Packet sent --->250 865375036 OK<---*Mar 1 01:09:02.577:Packet received -RQNT 254959796 ds1-1/13@mc1 SGCP 1.1X:358258758R:hd*Mar 1 01:09:02.577:SUCCESS:SGCP Header parsing was OK*Mar 1 01:09:02.577:SUCCESS:Request ID string(358258758) parsing is OK*Mar 1 01:09:02.577:SUCCESS:Requested Event parsing is OK*Mar 1 01:09:02.581:SUCCESS:END of Parsing*Mar 1 01:09:02.581:SUCCESS:SGCP message building OK*Mar 1 01:09:02.581:SUCCESS:END of building*Mar 1 01:09:02.581:SGCP Packet sent --->200 254959796 OKRelated Commands
debug snasw dlc
To display frame information entering and leaving the Systems Network Architecture (SNA) switch in real time to the console, use the debug snasw dlc command in privileged EXEC mode.
debug snasw dlc detail
Syntax Description
detail
Indicates that in addition to a one-line description of the frame being displayed, an entire hexadecimal dump of the frame will follow.
Defaults
By default, a one-line description of the frame is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
Examples
The following is an example of the debug snasw dlc command output:
Router# debug snasw dlcSequenceNumber Size of ISR/Link SNA BTU HPR Description of frame343 MVSD In sz:134 ISR fmh5 DLUR Rq ActPU NETA.APPNRA29344 MVSD Out sz:12 ISR +Rsp IPM slctd nws:0008345 @I000002 Out sz:18 ISR Rq ActPU346 MVSD Out sz:273 ISR fmh5 TOPOLOGY UPDATE347 @I000002 In sz:9 ISR +Rsp Data348 @I000002 In sz:12 ISR +Rsp IPM slctd nws:0002349 @I000002 In sz:29 ISR +Rsp ActPU350 MVSD Out sz:115 ISR fmh5 DLUR +Rsp ActPU351 MVSD In sz:12 ISR +Rsp IPM slctd nws:0007352 MVSD In sz:88 ISR fmh5 DLUR Rq ActLU NETA.MARTLU1353 MVSD Out sz:108 ISR fmh5 REGISTER354 @I000002 Out sz:27 ISR Rq ActLU NETA.MARTLU1Related Commands
debug snasw ips
To display internal signal information between the Systems Network Architecture (SNA) switch and the console in real time, use the debug snasw ips command in privileged EXEC mode.
debug snasw dlc
Syntax Description
This command has no arguments or keywords.
Defaults
By default, a one-line description of the interprocess signal is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
Examples
The following is an example of the debug snasw ips command output:
Router# debug snasw ipsSequenceNumber Sending ReceivingSignal Name Process Process Queue11257 : DEALLOCATE_RCB : --(0) -> RM(2130000) Q 411258 : RCB_DEALLOCATED : RM(2130000) -> PS(22E0000) Q 211259 : RCB_DEALLOCATED : --(0) -> PS(22E0000) Q 211260 : VERB_SIGNAL : PS(22E0000) -> DR(20F0000) Q 211261 : FREE_SESSION : --(0) -> RM(2130000) Q 211262 : BRACKET_FREED : RM(2130000) -> HS(22FB0001) Q 211263 : BRACKET_FREED : --(0) -> HS(22FB0001) Q 211264 : VERB_SIGNAL : --(0) -> DR(20F0000) Q 211265 : DLC_MU : DLC(2340000) -> PC(22DD0001) Q 211266 : DLC_MU : --(0) -> PC(22DD0001) Q 2Related Commands
snasw ipstrace
Captures interprocess signal information between Switching Services components.
debug snmp packet
To display information about every Simple Network Management Protocol (SNMP) packet sent or received by the router, use the debug snmp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug snmp packet
no debug snmp packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug snmp packet command. In this example, the router receives a get-next request from the host at 172.16.63.17 and responds with the requested information.
Router# debug snmp packetSNMP: Packet received via UDP from 172.16.63.17 on Ethernet0SNMP: Get-next request, reqid 23584, errstat 0, erridx 0sysUpTime = NULL TYPE/VALUEsystem.1 = NULL TYPE/VALUEsystem.6 = NULL TYPE/VALUESNMP: Response, reqid 23584, errstat 0, erridx 0sysUpTime.0 = 2217027system.1.0 = Cisco Internetwork Operating System Softwaresystem.6.0 =SNMP: Packet sent via UDP to 172.16.63.17Based on the kind of packet sent or received, the output may vary. For get-bulk requests, a line similar to the following is displayed:
SNMP: Get-bulk request, reqid 23584, nonrptr 10, maxreps 20For traps, a line similar to the following is displayed:
SNMP: V1 Trap, ent 1.3.6.1.4.1.9.1.13, gentrap 3, spectrap 0Table 228 describes the significant fields shown in the display.
debug snmp requests
To display information about every Simple Network Management Protocol (SNMP) request made by the SNMP manager, use the debug snmp requests command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug snmp requests
no debug snmp requests
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug snmp requests command:
Router# debug snmp requestsSNMP Manager API: requestdest: 171.69.58.33.161, community: publicretries: 3, timeout: 30, mult: 2, use session rttuserdata: 0x0Table 229 describes the significant fields shown in the display.
debug sntp adjust
To display information about Simple Network Time Protocol (SNTP) clock adjustments, use the debug sntp adjust command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sntp adjust
no debug sntp adjust
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug sntp adjust command output when an offset to the time reported by the configured NTP server is calculated. The offset indicates the difference between the router time and the actual time (as kept by the server) and is displayed in milliseconds. The clock time is then successfully changed to the accurate time by adding the offset to the current router time.
Router# debug sntp adjustDelay calculated, offset 3.48Clock slewed.The following is sample output from the debug sntp adjust command when an offset to the time reported by a broadcast server is calculated. Because the packet is a broadcast packet, no transmission delay can be calculated. However, in this case, the offset is too large, so the clock is reset to the correct time.
Router# debug sntp adjustNo delay calculated, offset 11.18Clock stepped.debug sntp packets
To display information about Simple Network Time Protocol (SNTP) packets sent and received, use the debug sntp packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sntp packets
no debug sntp packets
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug sntp packets command when a message is received:
Router# debug sntp packetsReceived SNTP packet from 172.16.186.66, length 48leap 0, mode 1, version 3, stratum 4, ppoll 1024rtdel 00002B00, rtdsp 00003F18, refid AC101801 (172.16.24.1)ref B7237786.ABF9CDE5 (23:28:06.671 UTC Tue May 13 1997)org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)xmt B7237B5C.A7DE94F2 (23:44:28.655 UTC Tue May 13 1997)inp AF3BD529.810B66BC (00:19:53.504 UTC Mon Mar 1 1993)The following is sample output from the debug sntp packets command when a message is sent:
Router# debug sntp packetsSending SNTP packet to 172.16.25.1xmt AF3BD455.FBBE3E64 (00:16:21.983 UTC Mon Mar 1 1993)Table 230 describes the significant fields shown in the display.
debug sntp select
To display information about Simple Network Time Protocol (SNTP) server selection, use the debug sntp select command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug sntp select
no debug sntp select
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug sntp select command. In this example, the router will synchronize its time to the server at 172.16.186.66.
Router# debug sntp selectSNTP: Selected 172.16.186.66debug source bridge
To display information about packets and frames transferred across a source-route bridge, use the debug source bridge command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug source bridge
no debug source bridge
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug source bridge output for peer bridges using TCP as a transport mechanism. The remote source-route bridging (RSRB) network configuration has ring 2 and ring 1 bridged together through remote peer bridges. The remote peer bridges are connected via a serial line and use TCP as the transport mechanism.
Router# debug source bridgeRSRB: remote explorer to 5/192.108.250.1/1996 srn 2 [C840.0021.0050.0000]RSRB: Version/Ring XReq sent to peer 5/192.108.250.1/1996RSRB: Received version reply from 5/192.108.250.1/1996 (version 2)RSRB: DATA: 5/192.108.250.1/1996 Ring Xchg Rep, trn 2, vrn 5, off 18, len 10RSRB: added bridge 1, ring 1 for 5/192.108.240.1/1996RSRB: DATA: 5/192.108.250.1/1996 Explorer trn 2, vrn 5, off 18, len 69RSRB: DATA: 5/192.108.250.1/1996 Forward trn 2, vrn 5, off 0, len 92RSRB: DATA: forward Forward srn 2, br 1, vrn 5 to peer 5/192.108.250.1/1996The following line indicates that a remote explorer frame has been sent to IP address 192.108.250.1 and, like all RSRB TCP connections, has been assigned port 1996. The bridge belongs to ring group 5. The explorer frame originated from ring 2. The routing information field (RIF) descriptor has been generated by the local station and indicates that the frame was sent out via bridge 1 onto virtual ring 5.
RSRB: remote explorer to 5/192.108.250.1/1996 srn 2 [C840.0021.0050.0000]The following line indicates that a request for remote peer information has been sent to IP address 192.108.250.1, TCP port 1996. The bridge belongs to ring group 5.
RSRB: Version/Ring XReq sent to peer 5/192.108.250.1/1996The following line is the response to the version request previously sent. The response is sent from IP address 192.108.250.1, TCP port 1996. The bridge belongs to ring group 5.
RSRB: Received version reply from 5/192.108.250.1/1996 (version 2)The following line is the response to the ring request previously sent. The response is sent from IP address 192.108.250.1, TCP port 1996. The target ring number is 2, virtual ring number is 5, the offset is 18, and the length of the frame is 10 bytes.
RSRB: DATA: 5/192.108.250.1/1996 Ring Xchg Rep, trn 2, vrn 5, off 0, len 10The following line indicates that bridge 1 and ring 1 were added to the source-bridge table for IP address 192.108.250.1, TCP port 1996:
RSRB: added bridge 1, ring 1 for 5/192.108.250.1/1996The following line indicates that a packet containing an explorer frame came across virtual ring 5 from IP address 192.108.250.1, TCP port 1996. The packet is 69 bytes in length. This packet is received after the Ring Exchange information was received and updated on both sides.
RSRB: DATA: 5/192.108.250.1/1996 Explorer trn 2, vrn 5, off 18, len 69The following line indicates that a packet containing data came across virtual ring 5 from IP address 192.108.250.1 over TCP port 1996. The packet is being placed on the local target ring 2. The packet is 92 bytes in length.
RSRB: DATA: 5/192.108.250.1/1996 Forward trn 2, vrn 5, off 0, len 92The following line indicates that a packet containing data is being forwarded to the peer that has IP address 192.108.250.1 address belonging to local ring 2 and bridge 1. The packet is forwarded via virtual ring 5. This packet is sent after the Ring Exchange information was received and updated on both sides.
RSRB: DATA: forward Forward srn 2, br 1, vrn 5 to peer 5/192.108.250.1/1996The following is sample output from the debug source bridge command for peer bridges using direct encapsulation as a transport mechanism. The RSRB network configuration has ring 1 and ring 2 bridged together through peer bridges. The peer bridges are connected via a serial line and use TCP as the transport mechanism.
Router# debug source bridgeRSRB: remote explorer to 5/Serial1 srn 1 [C840.0011.0050.0000]RSRB: Version/Ring XReq sent to peer 5/Serial1RSRB: Received version reply from 5/Serial1 (version 2)RSRB: IFin: 5/Serial1 Ring Xchg, Rep trn 0, vrn 5, off 0, len 10RSRB: added bridge 1, ring 1 for 5/Serial1The following line indicates that a remote explorer frame was sent to remote peer Serial1, which belongs to ring group 5. The explorer frame originated from ring 1. The RIF descriptor 0011.0050 was generated by the local station and indicates that the frame was sent out via bridge 1 onto virtual ring 5.
RSRB: remote explorer to 5/Serial1 srn 1 [C840.0011.0050.0000]The following line indicates that a request for remote peer information was sent to Serial1. The bridge belongs to ring group 5.
RSRB: Version/Ring XReq sent to peer 5/Serial1The following line is the response to the version request previously sent. The response is sent from Serial 1. The bridge belongs to ring group 5 and the version is 2.
RSRB: Received version reply from 5/Serial1 (version 2)The following line is the response to the ring request previously sent. The response is sent from Serial1. The target ring number is 2, virtual ring number is 5, the offset is 0, and the length of the frame is 39 bytes.
RSRB: IFin: 5/Serial1 Ring Xchg Rep, trn 2, vrn 5, off 0, len 39The following line indicates that bridge 1 and ring 1 were added to the source-bridge table for Serial1:
RSRB: added bridge 1, ring 1 for 5/Serial1debug source error
To display source-route bridging (SRB) errors, use the debug source error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug source error
no debug source error
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
The debug source error command displays some output also found in the debug source bridge output. See the debug source bridge command for other possible output.
Examples
In all of the following examples of debug source error command messages, the variable number is the Token Ring interface. For example, if the line of output starts with SRB1, the output relates to the Token Ring 1 interface. SRB indicates a source-route bridging message. RSRB indicates a remote source-route bridging message. SRTLB indicates a source-route translational bridging (SR/TLB) message.
In the following example, a packet of protocol protocol-type was dropped:
SRBnumber drop: Routed protocol protocol-typeIn the following example, an Address Resolution Protocol (ARP) packet was dropped. ARP is defined in RFC 826.
SRBnumber drop:TYPE_RFC826_ARPIn the following example, the current Cisco IOS version does not support Qualified Logical Link Control (QLLC). Reconfigure the router with an image that has the IBM feature set.
RSRB: QLLC not supported in version versionPlease reconfigure.In the following example, the packet was dropped because the outgoing interface of the router was down:
RSRB IF: outgoing interface not up, dropping packetIn the following example, the router received an out-of-sequence IP sequence number in a Fast Sequenced Transport (FST) packet. FST has no recovery for this problem like TCP encapsulation does.
RSRB FST: bad sequence number dropping.In the following example, the router was unable to locate the virtual interface:
RSRB: couldn't find virtual interfaceIn the following example, the TCP queue of the peer router is full. TCPD indicates that this is a TCP debug.
RSRB TCPD: tcp queue full for peerIn the following example, the router was unable to send data to the peer router. A result of 1 indicates that the TCP queue is full. A result of —1 indicates that the RSRB peer is closed.
RSRB TCPD: tcp send failed for peer resultIn the following example, the routing information identifier (RII) was not set in the explorer packet going forward. The packet will not support SRB, so it is dropped.
vrforward_explorer - RII not setIn the following example, a packet sent to a virtual bridge in the router did not include a routing information field (RIF) to tell the router which route to use:
RSRB: no RIF on packet sent to virtual bridgeThe following example indicates that the RIF did not contain any information or the length field was set to zero:
RSRB: RIF length of zero sent to virtual bridgeThe following message occurs when the local service access point (LSAP) is out of range. The variable lsap-out is the value, type is the type of RSRB peer, and state is the state of the RSRB peer.
VRP: rsrb_lsap_out = lsap-out, type = type, state = stateIn the following message, the router is unable to find another router with which to exchange bridge protocol data units (BPDUs). BPDUs are exchanged to set up the spanning tree and determine the forwarding path.
RSRB(span): BPDU's peer not foundRelated Commands
debug source bridge
Displays information about packets and frames transferred across a source-route bridge.
debug source event
Displays information on SRB activity.
