-
Cisco IOS Debug Command Reference
-
Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug auto-config
-
debug backhaul-session-manager session through debug channel packets
-
debug clns esis events through debug dbconn tcp
-
debug decnet adj through debug events
-
debug fax dmsp through debug gvrp
-
debug h225 asn1 through debug ip ftp
-
debug ip http all through debug ip rsvp
-
debug ip rtp header-compression through debug ipv6 icmp
-
debug ipv6 inspect through debug local-ack state
-
debug management event through debug mpls ldp bindings
-
debug mpls ldp checkpoint through debug mwi relay events
-
debug ncia circuit through debug pxf tbridge
-
debug qllc error through debug snmp sync
-
debug sntp adjust through debug tag-switching xtagatm vc
-
debug tag-template event through debug voip application vxml
-
debug voip avlist through debug vpm signaling
-
debug vpm spi through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug frame-relay end-to-end keepalive
debug frame-relay informationelements
debug frame-relay ip tcp header-compression
debug frame-relay networklayerinterface
debug gprs gtp ppp-regeneration
debug fax dmsp
To troubleshoot the fax Document Media Service Provider (DMSP), use the debug fax dmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax dmsp [all | default | detail | error [call [informational] | software [informational]] | event | function | inout]
no debug fax dmsp
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug fax dmsp all command:
Router# debug fax dmsp all2d07h: //70/67D6061D8012/DMSP/docmsp_call_setup_request:ramp data dir=ONRAMP, conf dir=DEST2d07h: //70/67D6061D8012/DMSP/docmsp_caps_ind:cid(0x46), srcCallID(0x44)2d07h: //70/67D6061D8012/DMSP/docmsp_bridge:conf id(0x33), srcCallID(0x46), dstCallID(0x44),ramp data dir=ONRAMP, conf dir=DEST, encode out=12d07h: //70/67D6061D8012/DMSP/docmsp_bridge:Bridge done2d07h: //70/67D6061D8012/DMSP/docmsp_bridge:conf id(0x34), srcCallID(0x46), dstCallID(0x45),ramp data dir=ONRAMP, conf dir=SRC, encode out=12d07h: //70/67D6061D8012/DMSP/docmsp_bridge:Bridge done2d07h: //70/67D6061D8012/DMSP/docmsp_xmit:srcCallID(0x44), dstCallID(0x46), direction=02d07h: //68/67D6061D8012/DMSP/docmsp_process_rcv_data:evID=0, proto_flag=3, srcCallID(0x44), dstCallID(0x46)2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_data_process:START_OF_CONNECTION2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_data_process:START_OF_FAX_PAGE2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_get_buffer_callback:tiff_segment=0x63A88ECC2d07h: //70/67D6061D8012/DMSP_ON/docmsp_tiff_writer_get_buffer_callback:tiff_segment=0x63D589442d07h: //70/67D6061D8012/DMSP/docmsp_process_rcv_data:DoneTable 88 describes the significant fields shown in the display.
debug fax fmsp
To troubleshoot the Fax Media Service Provider (FMSP), use the debug fax fmsp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax fmsp [all | default | detail | error [call [informational] | software [informational]] | event | function | inout | receive | send]
no debug fax fmsp
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug fax fmsp all command:
Router# debug fax fmsp all2d08h: //76/90A52CB88014/FMSP/faxmsp_call_setup_request:session(0x63A8A474), vdbPtr(0x62CA45A8),data dir=ONRAMP, conf dir=DEST2d08h: //76/90A52CB88014/FMSP/faxmsp_bridge:confID(0x38), srcCID(0x4C), dstCID(0x4B)2d08h: //76/90A52CB88014/FMSP/faxmsp_bridge:ramp data dir=ONRAMP, conf dir=DEST2d08h: //76/90A52CB88014/FMSP/faxmsp_bridge:Explicit caps ind. done; Wait for registry cap ind2d08h: //76/90A52CB88014/FMSP/faxmsp_caps_ind:per_bridge_info(0x63D52FD8), cap_ind_state(0x6)2d08h: //76/90A52CB88014/FMSP/faxmsp_caps_ind[1617]:2d08h: //76/90A52CB88014/FMSP/faxmsp_caps_ack:direction=0, srcCID(0x4B), dstCID(0x0)2d08h: //76/90A52CB88014/FMSP/faxmsp_codec_download_done:per_bridge_info(0x63D52FD8), application_data(0x63C54698), state(0x2), direction=22d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer:event(0x402897C0), bufferBegin(0x63A86B5C), dataBegin(0x402897EC)2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer:event(0x40289B50), bufferBegin(0x63C55794), dataBegin(0x40289B7C)2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer:event(0x40851E58), bufferBegin(0x63D4EAE4), dataBegin(0x40851E84)2d08h: //76/90A52CB88014/FMSP/faxmsp_xmit:srcCallID(0x4B), dstCallID(0x4C)2d08h: //76/90A52CB88014/FMSP/faxmsp_xmit[1813]:2d08h: //76/90A52CB88014/FMSP/faxmsp_process_rcv_data:state(0x1), evID=918065, evProtoFlag=22d08h: //76/90A52CB88014/FMSP/t38_rx_buffer:t38 rx msg dump (size=6):00 00 01 00 00 002d08h: //76/90A52CB88014/FMSP/faxmsp_process_rcv_data[1994]:2d08h: //76/90A52CB88014/FMSP/fax2_phaseB_receive:CSI_PACKET(8881111)DIS_PACKET(speed=5, resolution=1, encoding=1)2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer:event(0x40289690), bufferBegin(0x63A7E798), dataBegin(0x402896BC)2d08h: //76/90A52CB88014/FMSP/faxMsp_get_tx_buffer:event(0x4028858C), bufferBegin(0x63B89AC0), dataBegin(0x402885B8)2d08h: //76/90A52CB88014/FMSP/t38_tx_command:t38 tx msg dump (size=47):00 04 2A C0 04 80 00 16 FF C0 02 8C 8C 8C 8C 1C 1C 1C 04 0404 04 04 04 04 04 04 04 04 04 04 28 00 09 FF C8 01 00 77 1F01 01 19 80 40 00 002d08h: //76/90A52CB88014/FMSP/fax2_phaseB_receive:fax2_response_receive, PROCESSINGTable 89 describes the significant fields shown in the display.
debug fax foip
To troubleshoot fax mail, use the debug fax foip command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax foip [all | default | detail | error [call [informational] | software [informational]] | event | function | inout]
no debug fax foip
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug fax foip all command:
Router# debug fax foip all2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_call_handoff:Authentication:Id: 0Method: IVR or unknownStatus: SUCCESSEnabled: FALSETemplate:List: faxMailtoAddress: Calling Oct3A=0x02d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_vtsp_fmsp:Begin Conferencing VTSP and FMSP2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_vtsp_fmsp[887]:2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_change_state:Old State=0, New State=12d07h: //35/67E715B7800A/FOIP_ON/lapp_on_call_handoff[2953]:2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_validate_context[930]:2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_created:VTSP and FMSP Are Conferenced;Waiting for FMSP Call Detail Event2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_change_state:Old State=1, New State=22d07h: %ISDN-6-CONNECT: Interface Serial2:30 is now connected to unknown2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_validate_context[930]:2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_msp_event:2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Prepare MSPI Call Setup Request2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Envelope From=FAX=7771111@cisco.com2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Envelope To=jdoe@server.cisco.com2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:RFC822 To Comment=dileung2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Faxmail Subject=hagar-c5300-bw12 subject line here2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Disposition Notification=2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Originator TSI=RFC822 From Comment=2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Auth/Account ID: `0'2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_setup_mspi:Call Setup Request To MSPI2d07h: //37/67E715B7800A/FOIP_ON/lapp_on_setup_mspi[748]:2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_fmsp_dmsp:Starting Conference with FMSP and DMSP2d07h: //35/67E715B7800A/FOIP_ON/lapp_on_conference_fmsp_dmsp:Tiff File Created; Time=2003:06:05 22:46:48Table 90 describes the significant fields shown in the display.
debug fax mmoip aaa
To display output relating to authentication, authorization, and accounting (AAA) services using multimedia mail over IP (MMoIP) for the Store and Forward Fax feature, use the debug fax mmoip aaa command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax mmoip aaa [all | default | error [call [informational] | software [informational]] | inout]
no debug fax mmoip aaa
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows output from the debug fax mmoip aaa all command for an onramp fax connection:
Router# debug fax mmoip aaa all16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:UID=316:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:fax_account_id_origin=NONE_ID16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:fax_msg_id=00012003151904623@Router.cisco.com, Length=3916:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:fax_pages=016:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:fax_connect_speed=disable bps16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:fax_mdn_flag=FALSE16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:fax_auth_status=USER NOT AUTHENTICATED16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:email_server_address=172.19.140.11216:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:email_server_ack_flag=TRUE16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:gateway_id=Router.cisco.com16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:call_type=Fax Receive16:22:04: //3/D9242FD08002/MMOIP_AAA_ON/mmoip_aaa_accounting_onramp:abort_cause=10Table 91 describes the significant fields shown in the display.
debug fax mspi
To troubleshoot the fax Mail Service Provider Interface (MSPI), use the debug fax mspi command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax mspi [all | default | detail | error [call [informational] | software [informational]] | event | function | inout]
no debug fax mspi
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug fax mspi all command:
Router# debug fax mspi allRouter#2d07h: %ISDN-6-CONNECT: Interface Serial2:30 is now connected to unknown2d07h: //41/ACF704FA800B/MSPI_ON/mspi_call_setup_request:Outgoing Peer Tag=22Envelope From=FAX=5550121@cisco.comEnvelope To=jdoe@server.cisco.comMime Outer Type=22d07h: //41/ACF704FA800B/MSPI_ON/mspi_check_connect:MMccb(Count=0)2d07h: //41/ACF704FA800B/MSPI_ON/mspi_check_connect:SMTP Connected To The Server !2d07h: //41/ACF704FA800B/MSPI/mspi_bridge:MMccb(State=CONNECTED, Type=Onramp), Destination Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=0), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=1), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=2), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=3), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback:MMccb(Call State=CONFERENCED, Buffer Count=9)2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback:MMccb(Call State=CONFERENCED, Buffer Count=8)2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback:MMccb(Call State=CONFERENCED, Buffer Count=7)2d07h: //41/ACF704FA800B/MSPI_ON/mspi_onramp_buff_finished_callback:2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=0), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=1), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=2), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=3), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=4), Source Call Id=0x2A2d07h: //41/ACF704FA800B/MSPI_ON/mspi_xmit:MMccb(State=CONFERENCED, Type=Onramp, Buffer Count=5), Source Call Id=0x2ARouter#Table 92 describes the significant fields shown in the display.
debug fax mta
To troubleshoot the fax Mail Transfer Agent (MTA), use the debug fax mta command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax mta [all | default | detail | error [call [informational] | software [informational]] | event | function | inout]
no debug fax mta
Syntax Description
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug fax mta all command:
Router# debug fax mta all2d07h: %ISDN-6-CONNECT: Interface Serial2:30 is now connected to unknown2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_new_context_guid[2177]:2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_open:from=FAX=7771111@cisco.com, to=jdoe@server.cisco.com2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_open[1868]:2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_add_headers:from_comment=2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_work_routine:socket 0 readable for first time2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 220 vip2-das.cisco.com ESMTP Sendmail 8.9.3/8.9.3; Thu, 5 Jun 2003 23:24:54 -07002d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: EHLO Router.cisco.com2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-vip2-das.cisco.com Hello [172.19.140.108], pleased to meet you2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-EXPN2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-VERB2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-8BITMIME2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-SIZE2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-DSN2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-ONEX2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-ETRN2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250-XUSR2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250 HELP2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: MAIL FROM:<FAX=7771111@cisco.com>2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250 <FAX=7771111@cisco.com>... Sender ok2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: RCPT TO:<jdoe@server.cisco.com>2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 250 <jdoe@server.cisco.com>... Recipient ok2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_getln:(C)R: 354 Enter mail, end with "." on a line by itself2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: Received: by Router.cisco.com for <jdoe@server.cisco.com> (with Cisco NetWorks); Thu, 05 Jun 2003 23:11:09 +00002d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: To: "jdoe" <jdoe@server.cisco.com>2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: Message-ID: <00222003231109198@Router.cisco.com>2d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=02d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_writeln:(C)S: Date: Thu, 05 Jun 2003 23:11:09 +00002d07h: //-1/CEB9FA0B800E/SMTPC/esmtp_client_engine_write:return code=0Table 93 describes the significant fields shown in the display.
debug fax relay t30
To display debugging messages for T.30 real-time fax, use the debug fax relay t30 command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fax relay t30 {all | calling-number string | called-number string}
no debug fax relay t30
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The incoming or outgoing numbers must be a valid E.164 destination. The period symbol (.) as a wildcard should not be used. Instead of a wildcard, leave the space blank to indicate that any numbers can be valid.
There are no limits to the number of debug entries. The number entered generates a match if the calling or called number matches up to the final number of the debug entry. For example, the 408555 entry would match 408555, 4085551, 4085551212, or any other number starting with 408555.
Examples
The following command enables debugging for any incoming calls that start with 408555:
Router# debug fax relay t30 calling-number 408555Debugging fax relay t30 from 408555The following command enables debugging for any calls received to a number starting with 555-1212:
Router# debug fax relay t30 called-number 4155551212Debugging fax relay t30 to 4155551212The following command displays all debug entries:
Router# debug fax relay t30 allDebugging fax relay t30 from 408555Debugging fax relay t30 to 4155551212debug fddi smt-packets
To display information about Station Management (SMT) frames received by the router, use the debug fddi smt-packets command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fddi smt-packets
no debug fddi smt-packets
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug fddi smt-packets command. In this example, an SMT frame has been output by FDDI 1/0. The SMT frame is a next station addressing (NSA) neighbor information frame (NIF) request frame with the parameters as shown.
Router# debug fddi smt-packetsSMT O: Fddi1/0, FC=NSA, DA=ffff.ffff.ffff, SA=00c0.eeee.be04,class=NIF, type=Request, vers=1, station_id=00c0.eeee.be04, len=40- code 1, len 8 -- 000000016850043F- code 2, len 4 -- 00010200- code 3, len 4 -- 00003100- code 200B, len 8 -- 0000000100000000Table 94 describes the significant fields shown in the display.
debug filesystem
To enable ATA ROM monitor library (monlib) debugging messages, use the debug filesystem command in privileged EXEC mode. To disable ATA monlib debugging messages, use the no form of this command.
debug filesystem {disk0 | disk1}
no debug filesystem {disk0 | disk1}
Syntax Description
disk0
Selects disk 0 as the disk on which to enable or disable debugging.
disk1
Selects disk 1 as the disk on which to enable or disable debugging.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug filesystem command enables the display of ATA monlib debugging messages during boot operations.
To display the debugging messages when ROMMON accesses the PCMCIA disk, the ROMMON must have disk support. In other words, if a dev command is entered in ROMMON mode, the output should display the supported disks as shown in the following example:
rommon 1> devDevices in device table:id namebootflash: boot flashslot0: PCMCIA slot 0slot1: PCMCIA slot 1disk0: PCMCIA slot 0disk1: PCMCIA slot 1eprom: epromExamples
The following example shows how to enable ATA monlib debugging messages on disk 0, reboot the router to view ATA monlib debugging messages, and then disable ATA monlib debugging messages:
Router# debug filesystem disk0rommon 1> boot disk0:c7200-is-mz.123-5.7.PI3aInitializing ATA monitor library.......ATA_read_sector:dev = 0ATA_data_xfer:1:dev = 0, command = 32, nsecs = 8, sector = 3, cyl_low = 0,cyl_high = 0, head = 171ATA_read_sector:dev = 0, retval = 0dfs_openfile:Using monlib version 2dfs_openfile:Using version info 1dfs_openfile:finding file.. /c7200-is-mz.123-5.7.PI3aATA_read_sector:dev = 0ATA_data_xfer:1:dev = 0, command = 32, nsecs = 1, sector = 15, cyl_low = 0,cyl_high = 0, head = 163ATA_read_sector:dev = 0, retval = 0ATA_read_sector:dev = 0ATA_data_xfer:1:dev = 0, command = 32, nsecs = 128, sector = 35, cyl_low = 0,cyl_high = 0, head = 171ATA_read_sector:dev = 0, retval = 0dfs_openfile:opened file.. /c7200-is-mz.123-5.7.PI3a with fd = 0DFSLIB_read:reading file.. fd = 0, byte_count = 4DFSLIB_read:read from.. fd = 0, byte_count = 4, retval = 4DFSLIB_read:reading file.. fd = 0, byte_count = 52DFSLIB_read:read from.. fd = 0, byte_count = 52, retval = 52DFSLIB_read:reading file.. fd = 0, byte_count = 40DFSLIB_read:read from.. fd = 0, byte_count = 40, retval = 40...DFSLIB_read:reading file.. fd = 0, byte_count = 40DFSLIB_read:read from.. fd = 0, byte_count = 40, retval = 40DFSLIB_read:reading file.. fd = 0, byte_count = 19539160ATA_read_sector:dev = 0ATA_data_xfer:1:dev = 0, command = 32, nsecs = 1, sector = 15, cyl_low = 0,cyl_high = 0, head = 163ATA_read_sector:dev = 0, retval = 0ATA_read_sector:dev = 0...ATA_read_sector:dev = 0ATA_data_xfer:1:dev = 0, command = 32, nsecs = 19, sector = 1, cyl_low = 38,cyl_high = 0, head = 169ATA_read_sector:dev = 0, retval = 0DFSLIB_read:read from.. fd = 0, byte_count = 19539160, retval = 19539160Self decompressing the image :############################################################################################################################################################### ######################################################################### [OK]Router# no debug filesystem disk0Table 95 describes the significant fields shown in the display.
debug flow exporter
To enable debugging output for Flexible NetFlow flow exporters, use the debug flow exporter command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug flow exporter [[name] exporter-name] [error] [event] [packets number]
no debug flow exporter [[name] exporter-name] [error] [event] [packets number]
Syntax Description
Command Default
Debugging output for Flexible NetFlow flow exporters is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You must have already enabled traffic monitoring with Flexible NetFlow using an exporter before you can use the debug flow exporter command.
Examples
The following example indicates that a flow exporter packet has been queued for process send:
Router# debug flow exporterMay 21 21:29:12.603: FLOW EXP: Packet queued for process sendRelated Commands
debug flow monitor
To enable debugging output for Flexible NetFlow flow monitors, use the debug flow monitor command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug flow monitor [error] [{[name] monitor-name [cache] [error] [packets packets]}]
no debug flow monitor [error] [{[name] monitor-name [cache] [error] [packets packets]}]
Syntax Description
Command Default
Debugging output for Flexible NetFlow flow monitors is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You must have already enabled traffic monitoring with Flexible NetFlow before you can use the debug flow monitor command.
Examples
The following example shows that the cache for FLOW-MONITOR-1 was deleted:
Router# debug flow monitor FLOW-MONITOR-1 cacheMay 21 21:53:02.839: FLOW MON: 'FLOW-MONITOR-1' deleted cacheRelated Commands
debug flow record
To enable debugging output for Flexible NetFlow flow records, use the debug flow record command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug flow record [[name] record-name | netflow-original] | netflow ipv4 record [peer] | options {{exporter-statistics | interface-table | sampler-table} [detailed | error]}]
no debug flow record [[name] record-name | netflow-original] | netflow ipv4 record [peer] | options {{exporter-statistics | interface-table | sampler-table} [detailed | error]}]
Syntax Description
name record-name
(Optional) The name of a flow record that you previously configured.
netflow-original
(Optional) Traditional IPv4 input NetFlow with origin autonomous systems.
netflow ipv4 record
(Optional) The name of the NetFlow predefined record that you want to run debugging on. See Table 96.
peer
(Optional) Includes peer information for the NetFlow predefined records that support the peer keyword.
Note
The peer keyword is not supported for every type of NetFlow predefined record. See Table 96.
options
(Optional) Includes information on other flow record options.
exporter-statistics
(Optional) Information on the flow exporter statistics.
interface-table
(Optional) Information on the interface tables.
sampler-table
(Optional) Information on the sampler tables.
detailed
(Optional) Show detailed information.
error
(Optional) Only show errors.
Command Default
Debugging output for Flexible NetFlow flow records is disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You must have already enabled traffic monitoring with Flexible NetFlow before you can use the debug flow record command.
Keywords and Descriptions for the record Argument
Table 96 describes the keywords and descriptions for the record argument.
Examples
There are no examples available for this command.
Related Commands
debug flow-sampler
To enable debugging output for NetFlow sampler activity, use the debug flow-sampler command in privileged EXEC mode. To disable debugging output for NetFlow sampler activity, use the no form of this command.
debug flow-sampler {class-based | events | ipc | match}
no debug flow-sampler {class-based | events | ipc | match}
Syntax Description
Command Default
Debugging output for NetFlow sampler activity is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Because debugging output is assigned high priority in the CPU process, you should use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, you should use debug commands during periods of lower network traffic and fewer users. Debugging during these periods reducess the likelihood that increased debug command processing overhead will affect system use.
Examples
The following is sample output from the debug flow-sampler events command:
Router# debug flow-sampler eventsFlow sampler events debugging is onRouter# configure terminalRouter(config# no flow-sampler mysampler2Router(config)#5d00h: Flow: Sampler mysampler2 detached from FastEthernet0/15d00h: Flow: Sampler mysampler2 deletedThe following is sample output from the debug flow-sampler match command:
Router# debug flow-sampler matchFlow sampler match debugging is onRouter#4d23h: Flow: Packet matched sampler mysampler1 on interface FastEthernet0/0Router#4d23h: Flow: Packet matched sampler mysampler1 on interface FastEthernet0/0Router#4d23h: Flow: Packet matched sampler mysampler1 on interface FastEthernet0/0Router#4d23h: Flow: Packet matched sampler mysampler1 on interface FastEthernet0/0Table 97 describes the significant fields shown in the display.
Related Commands
debug fm private-hosts
To enable debug messages for the Private Hosts feature manager, use the debug fm private-hosts command in privileged EXEC mode.
debug fm private-hosts {all | vmr | unusual | events}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows sample command output:
Router# debug fm private-hosts allfm private-hosts vmr debugging is onfm private-hosts unusual debugging is onfm private-hosts events debugging is onRouter#Related Commands
debug fmsp receive
Note
To display debugging 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 is sample 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
Note
To display debugging messages for Fax Media Services Provider (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 is sample 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
Note
To display debugging 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 is sample 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
Note
To display debugging 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 is sample 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 format
To verify syntax of eXtensible Markup Language Programmatic Interface (XML-PI) spec files, use the debug format command in privileged EXEC mode. To disable debugging of the XML-PI spec files, use the no form of this command.
debug format {all | error}
no debug format {all | error}
Syntax Description
all
Verbose mode that displays selected debug data first with comments followed by full debug output.
error
Displays minimal format error statements.
Command Default
Debugging of the XML-PI spec files does not occur.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug format all command to troubleshoot errors in XML-PI spec files. The command displays XML output, the XML Schema Definition (XSD), and parsing locations. For less verbose output, use the debug format error command.
Examples
The following examples show how to use the verbose output from the debug format all command to troubleshoot spec file entries based on information collected from the show interfaces command.
Begin by displaying the show interfaces command output.
Router# show interfacesFastEthernet0/0 is up, line protocol is upHardware is i82543 (Livengood), address is 000b.60dc.9408 (bia 000b.60dc.9408)Internet address is 2.4.0.5/8MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Full-duplex, 100Mb/s, 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:07, output 00:00:03, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec769 packets input, 121369 bytesReceived 696 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog0 input packets with dribble condition detected959 packets output, 94185 bytes, 0 underruns2 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred2 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outFastEthernet0/1 is down, line protocol is downHardware is i82543 (Livengood), address is 000b.60dc.9406 (bia 000b.60dc.9406)MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Unknown duplex, Unknown Speed, 100BaseTX/FXARP type: ARPA, ARP Timeout 04:00:00Last input never, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytesReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog0 input packets with dribble condition detected0 packets output, 0 bytes, 0 underruns2 output errors, 0 collisions, 1 interface resets0 babbles, 0 late collision, 0 deferred2 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outLoopback0 is up, line protocol is upHardware is LoopbackMTU 1514 bytes, BW 8000000 Kbit, DLY 5000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation LOOPBACK, loopback not setLast input never, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/0 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outThe next step is to generate XML output for the show interfaces command:
Router# show interfaces | format slot0:spec3.3.odm<?xml version="1.0" encoding="UTF-8"?><ShowInterfaces><Interface><Name>FastEthernet0/0</Name><State>UP</State><lineprotocol>up</lineprotocol><Hardware>i82543</Hardware><address>000b.60dc.9408</address><bia>000b.60dc.9408</bia><Internetaddress>2.4.0.5/8</Internetaddress><MTU>1500</MTU><BW>100000</BW><DLY>100</DLY><reliability>255/255,</reliability><txload>1/255,</txload><rxload>1/255</rxload><Encapsulation>ARPA,</Encapsulation><loopback>Notset</loopback><Keepalive>Set</Keepalive><KeepAliveInterval>10</KeepAliveInterval><TunnelInfo></TunnelInfo><DuplexInfo><Duplextype>duplex,</Duplextype><DuplexSpeed>100Mb/s,</DuplexSpeed></DuplexInfo><ARPtype>ARPA,</ARPtype><ARPTimeout>04:00:00</ARPTimeout><LMIInfo></LMIInfo><BroadcastInfo></BroadcastInfo><Lastinput>00:00:26,</Lastinput><output>00:00:08,</output><outputhang>never</outputhang><LastclearingOfCounters>never</LastclearingOfCounters><Inputqueue><Size>0/75/0/0</Size><Max>0/75/0/0</Max><Drops>0/75/0/0</Drops><flushes>0/75/0/0</flushes></Inputqueue><Totaloutputdrops>0</Totaloutputdrops><Queueingstrategy>fifo</Queueingstrategy><Outputqueue><Size>0/40</Size><Max>0/40</Max></Outputqueue><Conversations></Conversations><ReservedConversations></ReservedConversations><Fiveminuteinputrateinbits>0</Fiveminuteinputrateinbits><Fiveminuteinputrateinpkts>0</Fiveminuteinputrateinpkts><Fiveminuteoutputrateinbits>0</Fiveminuteoutputrateinbits><Fiveminuteoutputrateinpkts>0</Fiveminuteoutputrateinpkts><L2Switched></L2Switched><L3in></L3in><L3out></L3out><packetsinput>771</packetsinput><nobuffer>0</nobuffer><broadcasts>0</broadcasts><runts>0</runts><giants>0</giants><throttles>0</throttles><inputerrors>0</inputerrors><CRC>0</CRC><frame>0</frame><overrun>0</overrun><ignored>0</ignored><packetsoutput>0</packetsoutput><underruns>0</underruns><outputerrors>0</outputerrors><collisions>0</collisions><interfaceresets>0</interfaceresets><outputbufferfailures>0</outputbufferfailures><outputbuffersswappedout>0</outputbuffersswappedout></Interface></ShowInterfaces>Analyze the two outputs: In this case, output about only one interface is listed in the show interfaces | format slot0:spec3.3.odm command, but based on the original show interfaces command output, it was expected that there would be output about three interfaces.
Enter the following commands to enable the verbose debugging mode that displays all Operational Data Model (ODM) errors:
Router# debug format allRouter# show interfaces | format slot0:spec3.3.odmThe debug format statements are read in groups of two lines. As the following example shows, the first line describes what the attempted match was; the second line provides the offset and the byte count from the beginning of the show interfaces command output that the cursor of the screen scraper is currently up to.
*May 4 01:20:35.279: ODM: Could not match Property mcast*May 4 01:20:35.279: offset 703: 5 minute output rate 0 bits/sec, 0 packets/secThe following example shows where the spec file entry (SFE) caused the ODM algorithm to return a truncated XML. Notice how the offset jumps from 703 to 3001. This is a large jump that implies a search between multicast and IP multicast probably caused the screen scraper to jump too far into the text. Because the cursor is not at a buffer, this condition is the likely candidate for the error. Looking at the spec file entry and doing a manual search through the show command output will confirm this suspicion.
*May 4 01:20:35.279: offset 703: 5 minute output rate 0 bits/sec, 0 packets/sec786 pa*May 4 01:20:35.279: ODM: Could not match Property mcast*May 4 01:20:35.279: offset 703: 5 minute output rate 0 bits/sec, 0 packets/sec786 pa*May 4 01:20:35.279: ODM: Could not match Property IP multicasts*May 4 01:20:35.279: offset 3001: no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0*May 4 01:20:35.279: ODM: Could not match Property watchdog*May 4 01:20:35.279: offset 3122: ignored, 0 abort0 packets output, 0 bytes, 0 underru*May 4 01:20:35.279: ODM: Could not match Property input packets with dribble condition detectedBe sure to disable the debug command.
debug fpm event
To display protocol information from the designated protocol header description field (PHDF), use the debug fpm event command in privileged EXEC mode. To disable debugging messages, use the no form of this command.
debug fpm event
no debug fpm event
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following sample output is from the debug fpm event command:
Router# debug fpm event*Jun 21 09:22:21.607: policy-classification-inline(): matches class: class-default *Jun 21 09:22:21.607: packet-access-control(): policy-map: fpm-policy, dir: input, match. retval: 0x0, ip-flags: 0x80000000debug 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. To disable debugging output, use the no form of this command.
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
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, use it only when the rate of traffic on the Frame Relay network is less 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 98 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
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 the CEF 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 10.2.2.2: member 400: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 401: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 402: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 403: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 404: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 405: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 406: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.2.2.2: member 407: removing adj00:46:35: FR-ADJ: vcb MP-4-dynamic: ip 10.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. To disable debugging output, use the no form of this command.
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 99 explains the possible call states.
Related Commands
debug frame-relay end-to-end keepalive
To display debug messages for the Frame Relay End-to-End Keepalive feature, use the debug frame-relay end-to-end keepalive command. Use the no form of this command to disable the display of debug messages.
debug frame-relay end-to-end keepalive {events | packet}
no debug frame-relay end-to-end keepalive {events | packet}
Syntax Description
Command History
Usage Guidelines
We recommend that both commands be enabled.
Examples
The following examples show typical output from the debug frame-relay end-to-end keepalive packet command. The following example shows output for an outgoing request packet:
EEK (o, Serial0.1 DLCI 200): 1 1 1 3 2 4 3The seven number fields that follow the colon signify the following:
The following example shows output for an incoming reply packet:
EEK (i, Serial0.1 DLCI 200): 1 1 2 3 2 4 4The seven number fields that follow the colon signify the following:
The following example shows typical output from the debug frame-relay end-to-end keepalive events command:
EEK SUCCESS (request, Serial0.2 DLCI 400)EEK SUCCESS (reply, Serial0.1 DLCI 200)EEK sender timeout (Serial0.1 DLCI 200)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. To disable debugging output, use the no form of this command.
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 data-link connection identifier (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 permanent virtual circuit (PVC), use the debug frame-relay fragment command in privileged EXEC mode. To disable debugging output, use the no form of this command.
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 is 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 is 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 hqf
To display debug messages for Frame Relay (FR) hierarchical queueing framework (HQF) events, use the debug frame-relay hqf command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug frame-relay hqf
no debug frame-relay hqf
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug frame-relay hqf command to track which quality of service (QoS) features are being used on an interface. QoS for a given FR interface changes depending on the commands being used.
Note
To use HQF on an interface, you must complete the following tasks:
•
•
This task is accomplished by adding a service policy to a frame map class. A valid MQC service policy shapes all traffic via the class default and has a child policy to support any further traffic classification, as shown in the following example:
policy-map llqclass voicepriority 32policy-map shape1class class-defaultshape average 96000service-policy llqpolicy-map shape2class class-defaultshape average 128000service-policy llqmap-class frame-relay mqc-class1service-policy output shape1map-class frame-relay mqc-class2service-policy output shape2interface serial4/0encapsulation frame-relayframe-relay class mqc-class1 <----- Map-class installedframe-relay interface-dlci 16 <----- Inherits map-class1frame-relay interface-dlci 17class mqc-class2 <----- Map-class installed for DLCI 17Examples
The following is sample output from the debug frame-relay hqf command:
Router# debug frame-relay hqfdebug frame-relay hqf is enabledRouter# show running-configuration...00:25:54: %SYS-5-CONFIG_I: Configured from console by console serial4/1Building configuration...Current configuration : 167 bytes!interface Serial4/1serial restart-delay 0service-policy output shapeendThe following commands and subsequent output show events that occur when HQF is enabled or disabled as a result of queueing changes at the interface level while debugging is on:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface serial4/1Router(config-if)# policy-map shapeRouter(config-pmap)# class class-defaultRouter(config-pmap-c)# shape average 128000 1000Router(config-pmap-c)# interface serial4/1Router(config-if)# encapsulation frame-relayRouter(config-if)# frame-relay fragment 80 end-to-endRouter(config-if)# service-policy output shapeRouter(config-if)# frame-relay map ip 10.0.0.1 16 payload frf9 stac00:26:52: Serial4/1- Setting up interface for legacy QOS. <---Indicates legacy QoS is being installed on an interface.00:26:52: Legacy fair-queueing installed on interface. <---Indicates that legacy QoS is being installed and HQF is being removed. You see this only with interface fragmentation and service policies since these policies must be able to support both QoS mechanisms. This usually means that either payload compression has been enabled on an interface or legacy queueing has been set up on the main interface.Router(config-if)# no frame-relay map ip 10.0.0.1 16 payload frf9 stac00:27:08: Serial4/1- Setting up HQF/MQC QOS. <---Indicates that the last legacy restriction has been removed and HQF is being installed on the interface.00:27:08: Serial4/1- Setting up interface for legacy QOS. <--- Indicates that legacy QoS is being installed on the interface.Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface serial4/1Router(config-if)# frame-relay map ip 10.0.0.1 16Router(config-if)# no service-policy output shapeRouter(config-if)# no frame-relay fragment 80 end-to-endThe following commands and subsequent output show events that occur when HQF is enabled or disabled as a result of queueing changes at the PVC level while debugging is on:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface serial4/1Router(config-if)# map-class frame-relay frts-shapeRouter(config-map-class)# frame-relay fragment 80Router(config-map-class)# service-policy output shapeRouter(config-map-class)# interface serial4/1Router(config-if)# frame-relay interface-dlci 16Router(config-fr-dlci)# class frts-shape00:28:54: Serial4/1- Setting up HQF/MQC QOS. <---Indicates that the last legacy restriction has been removed and that HQF is being installed on the interface.Router(config-fr-dlci)# no class frts-shape00:29:02: Serial4/1- Setting up interface for legacy QOS. <--- Indicates that legacy QoS has been installed on the interface.Related 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. To disable debugging output, use the no form of this command.
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 100 explains the information elements shown in the example.
Related Commands
debug frame-relay callcontrol
Displays Frame Relay Layer 3 (network layer) call control information.
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.) For FRF .20 IPHC, typically four packets are passed per PVC.
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 (not FRF .20 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: 43The following is sample output from the debug frame-relay ip tcp header-compression command when FRF .20 IPHC (without either Real-time Transport Protocol (RTP) or ECRTP) is configured in the IPHC profile:
Router# debug frame-relay ip tcp header-compressionFRF20(DLCI 16): Rxed Request, state 0: ident 0, tot len 19, conf_opts FE, len 15negotiation codes 1, version 1Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0,F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 FRF20(DLCI 16): Txed Ack, state 0: ident 0, tot len 19, conf_opts FE, len 15negotiation codes 1, version 1Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0,F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 FRF20(DLCI 16): Txed Request, state 0: ident 3, tot len 19, conf_opts FE, len 15negotiation codes 0, version 1Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0,F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 FRF20(DLCI 16): Rxed Ack, state 2: ident 3, tot len 19, conf_opts FE, len 15negotiation codes 0, version 1Par: IPV4, len 12, TCP_SPACE 16, NON_TCP_SPACE 0,F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 168 *Nov 14 09:18:37.019:FRF20(DLCI 16): STARTING IPHCThe following is sample output from the debug frame-relay ip tcp header-compression command when FRF .20 IPHC and RTP are configured in the IPHC profile:
Router# debug frame-relay ip tcp header-compressionFRF20(DLCI 16): Txed Request, state 1: ident 0, tot len 21, conf_opts FE, len 17negotiation codes 1, version 1Par: IPV4, len 14, TCP_SPACE 16, NON_TCP_SPACE 16,F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 16801:33:06: Subopt: rtp enabledThe following is sample output from the debug frame-relay ip tcp header-compression command when FRF .20 IPHC and ECRTP are configured in the IPHC profile:
Router# debug frame-relay ip tcp header-compressionFRF20(DLCI 16): Txed Request, state 1: ident 0, tot len 21, conf_opts FE, len 17negotiation codes 1, version 1Par: IPV4, len 14, TCP_SPACE 16, NON_TCP_SPACE 16,F_MAX_PERIOD 256, F_MAX_TIME 5, MAX_HEADER 16801:33:06: Subopt: ecrtp enabledTable 101 describes the significant fields shown in the displays.
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. To disable debugging output, use the no form of this command.
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. To disable debugging output, use the no form of this command.
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 102 describes the significant fields shown in the first line of the display.
Table 103 describes the significant fields shown in the third and fourth lines of the display.
Table 104 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 debugging output, use the no form of this command.
debug frame-relay multilink [control [mfr number | serial number]]
no debug frame-relay multilink
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Caution
Using the debug frame-relay multilink command without the mfr or serial keywords displays error conditions that occur at the bundle layer.
Examples
The following example shows output from the debug frame-relay multilink command for bundle "MFR0," which has three 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 105 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. To disable debugging output, use the no form of this command.
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 switched virtual circuit (SVC) signaling 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 signaling 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 106 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. To disable debugging output, use the no form of this command.
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 107 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 Local Management Interface (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 pseudowire
To display events and error conditions that occur when binding a Frame Relay data-link connection identifier (DLCI) to a pseudowire, use the debug frame-relay pseudowire command in privileged EXEC mode. To disable the display of these events and error conditions, use the no form of this command.
debug frame-relay pseudowire
no debug frame-relay pseudowire
Syntax Description
This command contains no arguments or keywords.
Defaults
DLCI events and errors are not displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The following are examples of Frame Relay pseudowire events:
•
•
•
Examples
The following example enables the display of Frame Relay pseudowire events. In this example, the interface has been shut down and then enabled.
Router# debug frame-relay pseudowireRouter(config)# interface hssi1/0/0Router(config-if)# shutdown09:18:33.303: FRoPW [10.15.15.15, 100]: acmgr_circuit_down09:18:33.303: FRoPW [10.15.15.15, 100]: SW AC update circuit state to down09:18:33.303: FRoPW [10.15.15.15, 100]: Setting connection DOWN09:18:35.299: %LINK-5-CHANGED: Interface Hssi1/0/0, changed state to administratively down09:18:36.299: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi1/0/0, changed state to downRouter(config-if)# no shutdown09:18:41.919: %LINK-3-UPDOWN: Interface Hssi1/0/0, changed state to up09:18:41.919: FRoPW [10.15.15.15, 100]: Local up, sending acmgr_circuit_up09:18:41.919: FRoPW [10.15.15.15, 100]: Setting pw segment UP09:18:41.919: FRoPW [10.15.15.15, 100]: PW nni_pvc_status set ACTIVE09:18:41.919: label_oce_get_label_bundle: flags 14 label 2809:18:42.919: %LINEPROTO-5-UPDOWN: Line protocol on Interface Hssi1/0/0, changed state to upTable 108 describes the significant fields shown in the display.
debug frame-relay redundancy
To debug Frame Relay and Multilink Frame Relay redundancy on the networking device, use the debug frame-relay redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug frame-relay redundancy
no debug frame-relay redundancy
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to debug Frame Relay synchronization problems. The debug frame-relay redundancy command logs synchronization events and errors.
Examples
The following example displays debug messages regarding Frame Relay redundancy on the networking device:
Router# debug frame-relay redundancyRelated Commands
frame-relay redundancy auto-sync lmi-sequence-numbers
Configures LMI synchronization parameters.
debug frame-relay switching
To display debugging messages for switched Frame Relay permanent virtual circuits (PVCs), use the debug frame-relay switching command in privileged EXEC mode. To disable debugging output, 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
Privileged EXEC
Command History
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 is sample output from 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.
Router# debug frame-relay vc-bundle00: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 debugging 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 debugging 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. To disable debugging output, use the no form of this command.
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 Logical Link Control, Type 2 (LLC2) session activation and deactivation frames (such as XID, SABME, DISC, UA) that are being handled by the Frame Relay access support (FRAS) host, use the debug fras-host activation command in privileged EXEC mode. To disable debugging output, use the no form of this command.
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 109 describes the significant fields shown in the display.
debug fras-host error
To enable the Frame Relay access support (FRAS) Host to send error messages to the console, use the debug fras-host error command in privileged EXEC mode. To disable debugging output, use the no form of this command.
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 Logical Link Control, type 2 (LLC2) session frames are being handled by the Frame Relay access support (FRAS) Host, use the debug fras-host packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug fras-host packet
no debug fras-host packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
Caution
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 Frame Relay Boundary Network Node (BNN) device and the host.
Table 110 describes the significant fields shown in the display.
debug fras-host snmp
To display messages to the console describing Simple Network Management Protocol (SNMP) requests to the Frame Relay access support (FRAS) Host MIB, use the debug fras-host snmp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
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 111 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. To disable debugging output, use the no form of this command.
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. To disable debugging output, use the no form of this command.
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. To disable debugging output, use the no form of this command.
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 this 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 this command.
debug gatekeeper load {events}
no debug gatekeeper load {events}
Syntax Description
