Table Of Contents
debug modem
Use the debug modem EXEC command to observe modem line activity on an access server. The no form of this command disables debugging output.
[no] debug modem
Usage Guidelines
This output of this command is self-explanatory.
Sample Display
shows sample debug modem output.
Figure 2-181 Sample Debug Modem Output
Router# debug modem15:25:51: TTY4: DSR came up15:25:51: tty4: Modem: IDLE->READY15:25:51: TTY4: Autoselect started15:27:51: TTY4: Autoselect failed15:27:51: TTY4: Line reset15:27:51: TTY4: Modem: READY->HANGUP15:27:52: TTY4: dropping DTR, hanging up15:27:52: tty4: Modem: HANGUP->IDLE15:27:57: TTY4: restoring DTR15:27:58: TTY4: DSR came upThe output in shows when the modem line changes state.
debug modem csm
Use the debug modem csm EXEC command to debug the call state machine used to connect calls on the modem. Use the no form of this command to disable debug output.
[no] debug modem csm [slot/modem-port | group group-number]
Syntax Description
Usage Guidelines
Use the debug modem csm command to troubleshoot call switching problems. With this command, you can trace the complete sequence of switching incoming and outgoing calls.
Sample Displays
shows sample debug modem csm output. In this example, a call enters the modem (incoming) on slot 1 port 0.
Figure 2-182 Sample Debug Modem CSM Output—Incoming Call
router(config)# service timestamps debug uptimerouter(config)# endRouter# debug modem csm00:04:09: ccpri_ratetoteup bear rate is 1000:04:09: CSM_MODEM_ALLOCATE: slot 1 and port 0 is allocated.00:04:09: MODEM_REPORT(0001): DEV_INCALL at slot 1 and port 000:04:09: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 000:04:11: CSM_RING_INDICATION_PROC: RI is on00:04:13: CSM_RING_INDICATION_PROC: RI is off00:04:15: CSM_PROC_IC1_RING: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 000:04:15: MODEM_REPORT(0001): DEV_CONNECTED at slot 1 and port 000:04:15: CSM_PROC_IC2_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 0shows sample debug modem csm output when call is dialed from the modem into the network (outgoing) from slot 1 port 2.
Figure 2-183 Sample Debug Modem CSM Output—Outgoing Call
Router# debug modem csmatdt1666520200:11:21: CSM_PROC_IDLE: CSM_EVENT_MODEM_OFFHOOK at slot 1, port 200:11:21: T1_MAIL_FROM_NEAT: DC_READY_RSP: mid = 1, slot = 0, unit = 000:11:21: CSM_PROC_OC1_REQUEST_DIGIT: CSM_EVENT_DIGIT_COLLECT_READY at slot 1, port 200:11:24: T1_MAIL_FROM_NEAT: DC_FIRST_DIGIT_RSP: mid = 1, slot = 0, unit = 000:11:24: CSM_PROC_OC2_COLLECT_1ST_DIGIT: CSM_EVENT_GET_1ST_DIGIT at slot 1, port 200:11:27: T1_MAIL_FROM_NEAT: DC_ALL_DIGIT_RSP: mid = 1, slot = 0, unit = 000:11:27: CSM_PROC_OC3_COLLECT_ALL_DIGIT: CSM_EVENT_GET_ALL_DIGITS (16665202) at slot 1, port 200:11:27: ccpri_ratetoteup bear rate is 1000:11:27: MODEM_REPORT(A000): DEV_CALL_PROC at slot 1 and port 200:11:27: CSM_PROC_OC4_DIALING: CSM_EVENT_ISDN_BCHAN_ASSIGNED at slot 1, port 200:11:31: MODEM_REPORT(A000): DEV_CONNECTED at slot 1 and port 200:11:31: CSM_PROC_OC5_WAIT_FOR_CARRIER: CSM_EVENT_ISDN_CONNECTED at slot 1, port 2CONNECT 19200/REL - MNPRelated Commands
debug modem oob
debug modem tracedebug modem oob
Use the debug modem oob EXEC command to debug the out-of-band port used to poll modem events on the modem. Use the no form of this command to disable debug output.
[no] debug modem oob [slot/modem-port | group group-number]
Syntax Description
Usage Guidelines
CautionEntering the debug modem oob command without specifying a slot and modem number debugs all out-of-band ports, which generates a significant amount of information.
The message types and sequence numbers that appear in the debug output are initiated by the Modem Out-of-Band (OOB) Protocol and used by service personnel for debugging purposes.
Sample Display
shows sample debug modem oob output. This example debugs the out-of-band port on modem 2/0, which creates modem startup messages between the network management software and the modem.
Figure 2-184 Sample Debug Modem OOB Output
Router# debug modem oob 2/0MODEM(2/0): One message sent --Message type:3, Sequence number:0MODEM(2/0): Modem DC session data replyMODEM(2/0): One message sent --Message type:83, Sequence number:1MODEM(2/0): DC session event =MODEM(2/0): One message sent --Message type:82, Sequence number:2MODEM(2/0): No status changes since last polledMODEM(2/0): One message sent --Message type:3, Sequence number:3MODEM(2/0): Modem DC session data replyMODEM(2/0): One message sent --Message type:83, Sequence number:4Related Commands
debug modem csm
debug modem tracedebug modem trace
Use the debug modem trace EXEC command to debug a call trace on the modem to determine why calls are terminated. Use the no form of this command to disable debug output.
[no] debug modem trace [normal | abnormal | all] [slot/modem-port | group group-number]
Syntax Description
Usage Guidelines
The debug modem trace command applies only to manageable modems.
For additional information, use the show modem command.
Sample Display
shows sample debug modem trace abnormal output.
Figure 2-185 Sample Debug Modem Trace Command
Router# debug modem trace abnormal 1/14Modem 1/14 Abnormal End of Connection Trace. Caller 123-4567Start-up Response: AS5200 Modem, Firmware 1.0Control Reply: 0x7C01DC session response: brasil firmware 1.0RS232 event:DSR=On, DCD=On, RI=Off, TST=Offchanges: RTS=No change, DTR=No change, CTS=No changechanges: DSR=No change, DCD=No change, RI=No change, TST=No changeModem State event: ConnectedConnection event: Speed = 19200, Modulation = VFCDirection = Originate, Protocol = reliable/LAPM, Compression = V42bisDTR event: DTR OnModem Activity event: Data ActiveModem Analog signal event: TX = -10, RX = -24, Signal to noise = -32End connection event: Duration = 10:34-11:43,Number of xmit char = 67, Number of rcvd char = 88, Reason: Watchdog Time-out.Related Commands
debug modem csm
debug modem oobdebug ncia circuit
Use the debug ncia circuit EXEC command to display circuit-related information between the native client interface architecture (NCIA) server and client. The no form of this command disables debugging output.
[no] debug ncia circuit [error | event | flow-control | state]
Syntax Description
Usage Guidelines
NCIA is an architecture developed by Cisco for accessing SNA applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones.
You cannot enable debugging output for a particular client or particular circuit.
CautionDo not enable the debug ncia circuit command during normal operation because this command generates a large amount of output messages and could slow down the router.
Sample Displays
shows sample debug ncia circuit error output. In this example, the possible errors are displayed. The first error message indicates that the router is out of memory. The second message indicates that the router has an invalid circuit control block. The third message indicates that the router is out of memory. The remaining messages identify errors related to the finite state machine.
Figure 2-186 Sample Debug NCIA Circuit Error Output
Router# debug ncia circuit errorNCIA: ncia_circuit_create memory allocation failNCIA: ncia_send_ndlc: invalid circuit control blockNCIA: send_ndlc: fail to get buffer for ndlc primitive xxxNCIA: ncia circuit fsm: Invalid inputNCIA: ncia circuit fsm: Illegal stateNCIA: ncia circuit fsm: Illegal inputNCIA: ncia circuit fsm: Unexpected inputNCIA: ncia circuit fsm: Unknown error rtn codeshows sample debug ncia circuit event output. In this example, a session start-up sequence is displayed.
Figure 2-187 Sample Debug NCIA Circuit Event Output
Router# debug ncia circuit eventNCIA(IN): Ver_Id: 0x81, MsgType: NDLC_START_DL, Len: 24, tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 0, lfs 16, ws 1NCIA: create circuit: saddr 4000.1060.1000, ssap 4, daddr 4000.3000.0003, dsap 8 sid:8B09A8NCIA: send NDLC_DL_STARTED to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_DL_STARTED, Len: 2,4 tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 8B09A8, lfs 16, ws 1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8B09A8, FC 0x81NCIA: send NDLC_XID_FRAME to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8A91E8, FC 0xC1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 18, sid: 8B09A8, FC 0xC1NCIA: send NDLC_CONTACT_STN to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_CONTACT_STN, Len: 12, sid: 8A91E8, FC 0xC1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_STN_CONTACTED, Len: 12, sid: 8B09A8, FC 0xC1NCIA: send NDLC_INFO_FRAME to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_INFO_FRAME, Len: 30, sid: 8A91E8, FC 0xC1describes the fields and messages shown in .
In the following messages, an NDLC_START_DL messages is received from a client. to start a data link session:
NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_START_DL, Len: 24, tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 0, lfs 16, ws 1NCIA: create circuit: saddr 4000.1060.1000, ssap 4, daddr 4000.3000.0003, dsap 8 sid:8B09A8The next two messages indicate that an NDLC_DL_STARTED message is sent to a client. The server informs the client that a data link session is started.
NCIA: send NDLC_DL_STARTED to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_DL_STARTED, Len: 2,4 tmac: 4000.1060.1000,tsap: 4, csap 8, oid: 8A91E8, tid 8B09A8, lfs 16, ws 1In the following two messages, an NDLC_XID_FRAME message is received from a client, and the client starts an XID exchange:
NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8B09A8, FC 0x81NCIA: send NDLC_XID_FRAME to client 10.2.20.3 for ckt: 8B09A8In the following two messages, an NDLC_XID_FRAME message is sent from a client, and an DLC_XID_FRAME message is received from a client:
NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 12, sid: 8A91E8, FC 0xC1NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_XID_FRAME, Len: 18, sid: 8B09A8, FC 0xC1The next two messages show that an NDLC_CONTACT_STN message is sent to a client:
NCIA: send NDLC_CONTACT_STN to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_CONTACT_STN, Len: 12, sid: 8A91E8, FC 0xC1In the following message, an NDLC_STN_CONTACTED message is received from a client. The client informs server that the station has been contacted.
NCIA(IN): Ver_Id: 0x81, MsgType: NDLC_STN_CONTACTED, Len: 12, sid: 8B09A8, FC 0xC1In the last two messages, an NDLC_INFO_FRAME is sent to a client, and the server sends data to the client:
NCIA: send NDLC_INFO_FRAME to client 10.2.20.3 for ckt: 8B09A8NCIA(OUT): Ver_Id: 0x81, MsgType: NDLC_INFO_FRAME, Len: 30, sid: 8A91E8, FC 0xC1shows sample debug ncia circuit flow-control output. In this example, the flow control in a session start-up sequence is displayed.
Figure 2-188 Sample Debug NCIA Circuit Flow-Control Output
Router# debug ncia circuit flow-controlNCIA: no flow control in NDLC_DL_STARTED frameNCIA: receive Increment Window Op for circuit 8ADE00NCIA: ncia_flow_control_in FC 0x81, IW 1 GP 2 CW 2, Client IW 1 GP 0 CW 1NCIA: grant client more packet by sending Repeat Window OpNCIA: ncia_flow_control_out FC: 0xC1, IW 1 GP 2 CW 2, Client IW 1 GP 2 CW 2NCIA: receive FCA for circuit 8ADE00NCIA: receive Increment Window Op for circuit 8ADE00NCIA: ncia_flow_control_in FC 0xC1, IW 1 GP 5 CW 3, Client IW 1 GP 2 CW 2NCIA: grant client more packet by sending Repeat Window OpNCIA: ncia_flow_control_out FC: 0xC1, IW 1 GP 5 CW 3, Client IW 1 GP 5 CW 3NCIA: receive FCA for circuit 8ADE00NCIA: receive Increment Window Op for circuit 8ADE00NCIA: ncia_flow_control_in FC 0xC1, IW 1 GP 9 CW 4, Client IW 1 GP 5 CW 3NCIA: grant client more packet by sending Repeat Window OpNCIA: ncia_flow_control_out FC: 0xC1, IW 1 GP 8 CW 4, Client IW 1 GP 9 CW 4NCIA: reduce ClientGrantPacket by 1 (Granted: 8)NCIA: receive FCA for circuit 8ADE00NCIA: receive Increment Window Op for circuit 8ADE00describes the important fields shown in .
Table 2-90 Debug NCIA Circuit Flow-Control Field Descriptions
IW
Initial window size.
GP
Granted packet number.
CW
Current window size.
shows sample debug ncia circuit state output. In this example, a session start-up sequence is displayed.
Figure 2-189 Sample Debug NCIA Circuit State Output
Router# debug ncia circuit stateNCIA: pre-server fsm: event CONN_OPENEDNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - STDL state: CLSOEDNCIA: ncia server fsm action 32NCIA: circuit state: CLOSED -> START_DL_RCVDNCIA: server event: DLU - TestStn.Rsp state: START_DL_RCVDNCIA: ncia server fsm action 17NCIA: circuit state: START_DL_RCVD -> DL_STARTED_SNDNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - XID state: DL_STARTED_SNDNCIA: ncia server fsm action 33NCIA: circuit state: DL_STARTED_SND -> DL_STARTED_SNDNCIA: server event: DLU - ReqOpnStn.Req state: DL_STARTED_SNDNCIA: ncia server fsm action 33NCIA: circuit state: DL_STARTED_SND -> OPENEDNCIA: server event: DLU - Id.Rsp state: OPENEDNCIA: ncia server fsm action 11NCIA: circuit state: OPENED -> OPENEDNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - XID state: OPENEDNCIA: ncia server fsm action 33NCIA: circuit state: OPENED -> OPENEDNCIA: server event: DLU - Connect.Req state: OPENEDNCIA: ncia server fsm action 6NCIA: circuit state: OPENED -> CONNECT_PENDINGNCIA: pre-server fsm: event NDLC_PRIMITIVESNCIA: server event: WAN - CONR state: CONNECT_PENDINGNCIA: ncia server fsm action 33 --> CLS_CONNECT_CNF sets NciaClsBusyNCIA: circuit state: CONNECT_PENDING -> CONNECTEDNCIA: server event: DLU - Flow.Req (START) state: CONNECTEDNCIA: ncia server fsm action 25 --> unset NciaClsBusyNCIA: circuit state: CONNECTED -> CONNECTEDNCIA: server event: DLU - Data.Rsp state: CONNECTEDNCIA: ncia server fsm action 8NCIA: circuit state: CONNECTED -> CONNECTEDdescribes the important fields shown in .
Related Commands
debug dlsw
debug ncia client
debug ncia serverdebug ncia client
Use the debug ncia client EXEC command to display debug information for all native client interface architecture (NCIA) client processing that occurs in the router. The no form of this command disables debugging output.
[no] debug ncia client [ip-address | error [ip-address] | event [ip-address] | message [ip-address]]
Syntax Description
Usage Guidelines
NCIA is an architecture developed by Cisco for accessing SNA applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones.
Use the debug ncia client event command to determine the sequences of activities that occur while a NCIA client is in different processing states.
Use the debug ncia client error command to see only certain error conditions that occur.
Use the debug ncia client message command to see only the first 32 bytes of data in a TCP packet sent to or received from an NCIA client.
The debug ncia client command can be used in conjunction with the debug ncia server and debug ncia circuit commands to get a complete picture of NCIA activity.
Sample Display
shows sample debug ncia circuit output. Following the example is a description of each sample output message.
Figure 2-190 Sample Debug NCIA Circuit Output
Router# debug ncia clientNCIA: Passive open 10.2.20.123(1088) -> 1973NCIA: index for client hash queue is 27NCIA: number of element in client hash queue 27 is 1NCIA: event PASSIVE_OPEN, state NCIA_CLOSED for client 10.2.20.123NCIA: Rcvd msg type NDLC_CAP_XCHG in tcp packet for client 10.2.20.123NCIA: First 17 byte of data rcvd: 811200110000000000000400050104080CNCIA: Sent msg type NDLC_CAP_XCHG in tcp packet to client 10.2.20.123NCIA: First 17 byte of data sent: 811200111000000010000400050104080CNCIA: event CAP_CMD_RCVD, state NCIA_CAP_WAIT, for client 10.2.20.123, cap xchg cmd sentNCIA: Rcvd msg type NDLC_CAP_XCHG in tcp packet for client 10.2.20.123NCIA: First 17 byte of data rcvd: 811200111000000010000000050104080CNCIA: event CAP_RSP_RCVD, state NCIA_CAP_NEG for client 10.2.20.123NCIA: Rcvd msg type NDLC_PEER_TEST_REQ in tcp packet for client 10.2.20.123NCIA: First 4 byte of data rcvd: 811D0004NCIA: event KEEPALIVE_RCVD, state NCIA_OPENED for client 10.2.20.123NCIA: Sent msg type NDLC_PEER_TEST_RSP in tcp packet to client 10.2.20.123NCIA: First 4 byte of data sent: 811E0004IANCIA: event TIME_OUT, state NCIA_OPENED, for client 10.2.20.123, keepalive_count = 0NCIA: Sent msg type NDLC_PEER_TEST_REQ, in tcp packet to client 10.2.20.123NCIA: First 4 byte of data sent: 811D0004NCIA: Rcvd msg type NDLC_PEER_TEST_RSP in tcp packet for client 10.2.20.123NCIA: First 4 byte of data rcvd: 811E0004NCIA: event KEEPALIVE_RSP_RCVD, state NCIA_OPENED for client 10.2.20.123NCIA: Error, event PASIVE_OPEN, state NCIA_OPENED, for client 10.2.20.123, should not have occured.NCIA: Error, active_open for pre_client_fsm while client 10.2.20.123 is active or not configured, registered.Messages in lines 1 through 12 show the events that occur when a client connects to the router (the NCIA server). These messages show a passive_open process.
Messages in lines 13 to 17 show the events that occur when a TIME_OUT event is detected by a client PC workstation. The workstation sends an NDLC_PEER_TEST_REQ message to the NCIA server, and the router responds with an NDLC_PEER_TEST_RSP message.
Messages in lines 18 to 23 show the events that occur when a TIME_OUT event is detected by the router (the NCIA server). The router sends an NDLC_PEER_TEST_REQ message to the client PC workstation, and the PC responds with an NDLC_PEER_TEST_RSP message.
When you use the debug ncia client message command, the messages shown on lines 6, 8, 11, 14, 17, 20, and 22 are output in addition to other messages not shown in this example.
When you use the debug ncia client error command, the messages shown on lines 24 and 25 are output in addition to other messages not shown in this example.
Related Commands
debug ncia circuit
debug ncia serverdebug ncia server
Use the debug ncia server EXEC command to display debug information for the native client interface architecture (NCIA) server and its upstream software modules. The no form of this command disables debugging output.
[no] debug ncia server
Usage Guidelines
NCIA is an architecture developed by Cisco for accessing SNA applications. This architecture allows native SNA interfaces on hosts and clients to access TCP/IP backbones.
The debug ncia server command displays all Cisco Link Services (CLS) messages between the NCIA server and its upstream modules, such as data-link switching (DLSw) and downstream physical units (DSPUs). Use this command when a problem exists between the NCIA server and other software modules within the router.
You cannot enable debugging output for a particular client or particular circuit.
Sample Display
shows sample debug ncia server output. In this example, a session start-up sequence is displayed. Following the example is a description of each group of sample output messages.
Figure 2-191 Sample Debug NCIA Server Output
Router# debug ncia serverNCIA: send CLS_TEST_STN_IND to DLUNCIA: Receive TestStn.RspNCIA: send CLS_ID_STN_IND to DLUNCIA: Receive ReqOpnStn.ReqNCIA: send CLS_REQ_OPNSTN_CNF to DLUNCIA: Receive Id.RspNCIA: send CLS_ID_IND to DLUNCIA: Receive Connect.ReqNCIA: send CLS_CONNECT_CNF to DLUNCIA: Receive Flow.ReqNCIA: Receive Data.ReqNCIA: send CLS_DATA_IND to DLUNCIA: send CLS_DISC_IND to DLUNCIA: Receive Disconnect.RspIn the following messages, the client is sending a test message to the host and the test message is received by the host:
NCIA: send CLS_TEST_STN_IND to DLUNCIA: Receive TestStn.RspIn the next message, the server is sending an XID message to the host.
NCIA: send CLS_ID_STN_IND to DLUIn the next two messages, the host opens the station and the server responds.
NCIA: Receive ReqOpnStn.ReqNCIA: send CLS_REQ_OPNSTN_CNF to DLUIn the following two messages, the client is performing an XID exchange with the host:
NCIA: Receive Id.RspNCIA: send CLS_ID_IND to DLUIn the next group of messages, the host attempts to establish a session with the client.
NCIA: Receive Connect.ReqNCIA: send CLS_CONNECT_CNF to DLUNCIA: Receive Flow.ReqIn the next two messages, the host sends data to the client.
NCIA: Receive Data.ReqNCIA: send CLS_DATA_IND to DLUIn the last two messages, the client closes the session.
NCIA: send CLS_DISC_IND to DLUNCIA: Receive Disconnect.RspRelated Commands
debug dlsw
debug ncia circuit
debug ncia clientdebug netbios error
Use the debug netbios error EXEC command to display information about Network Basic Input/Output System (NetBIOS) protocol errors. The no form of this command disables debugging output.
[no] debug netbios error
Usage Guidelines
For complete information on the NetBIOS process, use the debug netbios packet command along with the debug netbios error command.
Sample Display
Figure 2-192 shows sample debug netbios error output. This example shows that an illegal packet has been received on the async interface.
Figure 2-192 Sample Debug NetBIOS Error Output
Router# debug netbios errorAsync1 nbf Bad packetRelated Commands
debug netbios-name-cache
debug netbios packetdebug netbios-name-cache
Use the debug netbios-name-cache EXEC command to display name caching activities on a router. The no form of this command disables debugging output.
[no] debug netbios-name-cache
Usage Guidelines
Examine the display to diagnose problems in NetBIOS name caching.
Sample Display
illustrates a collection of sample debug netbios-name-cache output listings.
Figure 2-193 Sample Debug NetBIOS-Name-Cache Output
Router# debug netbios-name-cacheNETBIOS: L checking name ORINDA, vrn=0NetBIOS name cache table corrupted at offset 13NetBIOS name cache table corrupted at later offset, at location 13NETBIOS: U chk name=ORINDA, addr=1000.4444.5555, idb=TR1, vrn=0, type=1NETBIOS: U upd name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1NETBIOS: U add name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1NETBIOS: U no memory to add cache entry. name=ORINDA,addr=1000.4444.5555NETBIOS: Invalid structure detected in netbios_name_cache_agerNETBIOS: flushed name=ORINDA, addr=1000.4444.5555NETBIOS: expired name=ORINDA, addr=1000.4444.5555NETBIOS: removing entry. name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0NETBIOS: Tossing ADD_NAME/STATUS/NAME/ADD_GROUP frameNETBIOS: Lookup Failed -- not in cacheNETBIOS: Lookup Worked, but split horizon failedNETBIOS: Could not find RIF entryNETBIOS: Cannot duplicate packet in netbios_name_cache_proxy
Note
The sample display in is a composite output. Debugging output that you actually see would not necessarily occur in this sequence.
describes selected output fields shown in .
The following discussion briefly outlines each line shown in the example provided in .
With the first line of output, the router declares that it has examined the NetBIOS name cache table for the machine name ORINDA and that the packet that prompted the lookup came from virtual ring 0. In this case, this packet comes from a real interface—virtual ring number 0 is not valid.
NETBIOS: L checking name ORINDA, vrn=0The following two lines indicate that an invalid NetBIOS entry exists and that the corrupted memory was detected. The invalid memory will be removed from the table; no action is needed.
NetBIOS name cache table corrupted at offset 13NetBIOS name cache table corrupted at later offset, at location 13The following line indicates that the router attempted to check the NetBIOS cache table for the name ORINDA with MAC address 1000.4444.5555. This name was obtained from Token Ring interface 1. The type field indicates that the name was learned from traffic.
NETBIOS: U chk name=ORINDA, addr=1000.4444.5555, idb=TR1, vrn=0, type=1The following line indicates that the NetBIOS name ORINDA is in the name cache table and was updated to the current value:
NETBIOS: U upd name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1The following line indicates that the NetBIOS name ORINDA is not in the table and must be added to the table:
NETBIOS: U add name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0,type=1The following line indicates that there was insufficient cache buffer space when the router tried to add this name:
NETBIOS: U no memory to add cache entry. name=ORINDA,addr=1000.4444.5555The following line indicates that the NetBIOS ager detects an invalid memory in the cache. The router clears the entry; no action is needed.
NETBIOS: Invalid structure detected in netbios_name_cache_agerThe following line indicates that the entry for ORINDA was flushed from the cache table:
NETBIOS: flushed name=ORINDA, addr=1000.4444.5555The following line indicates that the entry for ORINDA timed out and was flushed from the cache table:
NETBIOS: expired name=ORINDA, addr=1000.4444.5555The following line indicates that the router removed the ORINDA entry from its cache table:
NETBIOS: removing entry. name=ORINDA,addr=1000.4444.5555,idb=TR1,vrn=0The following line indicates that the router discarded a NetBIOS packet of type ADD_NAME, STATUS, NAME_QUERY, or ADD_GROUP. These packets are discarded when multiple copies of one of these packet types are detected during a certain period of time.
NETBIOS: Tossing ADD_NAME/STATUS/NAME/ADD_GROUP frameThe following line indicates that the system could not find a NetBIOS name in the cache:
NETBIOS: Lookup Failed -- not in cacheThe following line indicates that the system found the destination NetBIOS name in the cache, but located on the same ring from which the packet came. The router will drop this packet because the packet should not leave this ring.
NETBIOS: Lookup Worked, but split horizon failedThe following line indicates that the system found the NetBIOS name in the cache, but the router could not find the corresponding RIF. The packet will be sent as a broadcast frame.
NETBIOS: Could not find RIF entryThe following line indicates that no buffer was available to create a NetBIOS name-cache proxy. A proxy will not be created for the packet, which will be forwarded as a broadcast frame.
NETBIOS: Cannot duplicate packet in netbios_name_cache_proxyRelated Commands
debug netbios error
debug netbios packetdebug netbios packet
Use the debug netbios packet EXEC command to display general information about NetBIOS packets. The no form of this command disables debugging output.
[no] debug netbios packet
Usage Guidelines
For complete information on the NetBIOS process, use the debug netbios error command along with the debug netbios packet command.
Sample Display
Figure 2-194 shows sample debug netbios packet and debug netbios error output. This example shows the LLC header for an asynchronous interface followed by the NetBIOS information. For additional information on the NetBIOS fields, refer to IBM LAN Technical Reference IEEE 802.2.
Figure 2-194 Sample Debug NetBIOS Packet Output
Router# debug netbios packetAsync1 (i) U-format UI C_R=0x0(i) NETBIOS_ADD_NAME_QUERYResp_correlator= 0x6F 0x0Src name=CS-NT-1Async1 (i) U-format UI C_R=0x0(i) NETBIOS_ADD_GROUP_QUERYResp_correlator= 0x6F 0x0Src name=COMMSERVER-WGAsync1 (i) U-format UI C_R=0x0(i) NETBIOS_ADD_NAME_QUERYResp_correlator= 0x6F 0x0Src name=CS-NT-1Ethernet0 (i) U-format UI C_R=0x0(i) NETBIOS_DATAGRAMLength= 0x2C 0x0Dest name=COMMSERVER-WGSrc name=CS-NT-3Related Commands
debug netbios error
debug netbios-name-cachedebug nhrp
Use the debug nhrp EXEC command to display information about Next Hop Resolution Protocol (NHRP) activity. The no form of this command disables debugging output.
[no] debug nhrp
Usage Guidelines
Use this command when some nodes on a TCP/IP or IPX network are not responding. It shows whether the router is sending or receiving NHRP packets.
Sample Display
Figure 2-195 shows sample debug nhrp output.
Figure 2-195 Sample Debug NHRP Output
Router# debug nhrpNHRP: Cache update 172.19.145.57 NoneNHRP: Sent request src 172.19.145.56 dst 255.255.255.255NHRP M: id 0 src 172.19.145.56 dst 172.19.145.57NHRP: Encapsulation succeeded. MAC addr ffff.ffff.ffff.NHRP: O 86 bytes out Ethernet1 dest 255.255.255.255NHRP: Recv reply Size 64NHRP M: id 0 src 172.19.145.56 dst 172.19.145.57NHRP: Cache update 172.19.145.57 0000.0c14.59d3.describes the fields shown in the display.
Related Commands
debug nhrp options
debug nhrp ratedebug nhrp options
Use the debug nhrp options EXEC command to display information about NHRP option processing. The no form of this command disables debugging output.
[no] debug nhrp options
Usage Guidelines
Use this command to show you whether there are problems or error situations with NHRP option processing (for example, unknown options).
Sample Display
Figure 2-196 shows sample debug nhrp options output.
Figure 2-196 Sample Debug NHRP Options Output
Router# debug nhrp optionsNHRP-OPT: MASK 4NHRP-OPT-MASK: FFFFFFFFNHRP-OPT: NETID 4NHRP-OPT: RESPONDER 4NHRP-OPT: RECORD 0NHRP-OPT: RRECORD 0describes the fields shown in .
Related Commands
debug nhrp rate
Use the debug nhrp rate EXEC command to display information about NHRP traffic rate limits. The no form of this command disables debugging output.
[no] debug nhrp rate
Usage Guidelines
Use this command to verify that the traffic is consistent with the setting of the NHRP commands (such as ip nhrp use and ip max-send commands).
Sample Display
Figure 2-197 shows sample debug nhrp rate output.
Figure 2-197 Sample Debug NHRP Rate Output
Router# debug nhrp rateNHRP-RATE: Sending initial requestNHRP-RATE: Retransmitting request (retrans ivl 2)NHRP-RATE: Retransmitting request (retrans ivl 4)NHRP-RATE: Ethernet1: Used 3describes the fields shown in .
Related Commands
debug packet
Use the debug packet EXEC command to display information on packets that the network can not classify. The no form of this command disables debugging output.
[no] debug packet
Sample Display
shows sample debug packet output.
Figure 2-198 Sample Debug Packet Output
Router# debug packetEthernet0: Unknown ARPA, src 0000.0c00.6fa4, dst ffff.ffff.ffff, type 0x0a0data 00000c00f23a00000c00ab45, len 60Serial3: Unknown HDLC, size 64, type 0xaaaa, flags 0x0F00Serial2: Unknown PPP, size 128Serial7: Unknown FRAME-RELAY, size 174, type 0x5865, DLCI 7aSerial0: compressed TCP/IP packet droppeddescribes significant fields shown in .
debug ppp
Use the debug ppp EXEC command to display information on traffic and exchanges in an internetwork implementing the Point-to-Point Protocol (PPP). The no form of this command disables debugging output.
[no] debug ppp {packet | negotiation | error | authentication}
Syntax Description
Usage Guidelines
Use the debug ppp commands when trying to find the following:
•
•
•
•
•
•
Refer to Internet RFCs 1331, 1332, and 1333 for details concerning PPP-related nomenclature and protocol information.
Sample Displays
shows sample debug ppp packet output as seen from the Link Quality Monitor (LQM) side of the connection. This display example depicts packet exchanges under normal PPP operation.
Figure 2-199 Sample Debug PPP Packet Output
Router# debug ppp packetPPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 3 len = 12PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 4 (C) magic D3454PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 4 len = 12PPP Serial4: O LCP ECHOREP(A) id 4 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 5 (C) magic D3454PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 5 len = 12PPP Serial4: O LCP ECHOREP(A) id 5 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 6 (C) magic D3454PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 6 len = 12PPP Serial4: O LCP ECHOREP(A) id 6 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 7 (C) magic D3454PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 7 len = 12PPP Serial4: O LCP ECHOREP(A) id 7 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48describes significant fields shown in .
To elaborate on the displayed output, consider the partial exchange in . This sequence shows that one side is using ECHO for its keepalives and the other side is using LQRs.
Figure 2-200 Sample Debug PPP Packet Output—Keepalive Messages
Router# debug ppp packetPPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454PPP Serial4: input(C021) state = OPEN code = ECHOREQ(9) id = 3 len = 12PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48Explanations for each line of follow.
The first line states that the router with debugging enabled has sent an LQR to the other side of the PPP connection:
PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48The next two lines indicate that the router has received a packet of type C025 (LQM) and provides details about the packet:
PPP Serial4(i): pkt type 0xC025, datagramsize 52PPP Serial4(i): lcp_rlqr() state = OPEN magic = D3454, len = 48The next two lines indicate that the router received an ECHOREQ of type C021 (LCP). The other side is sending ECHOs. The router on which debugging is configured for LQM but also responds to ECHOs.
PPP Serial4(i): pkt type 0xC021, datagramsize 16PPP Serial4: I LCP ECHOREQ(9) id 3 (C) magic D3454Next, the router is detected to have responded to the ECHOREQ with an ECHOREP and is preparing to send out an LQR:
PPP Serial4: O LCP ECHOREP(A) id 3 (C) magic D21B4PPP Serial4(o): lcp_slqr() state = OPEN magic = D21B4, len = 48shows sample debug ppp negotiation output. This is a normal negotiation, where both sides agree on network control program (NCP) parameters. In this case, protocol type IP is proposed and acknowledged.
Figure 2-201 Sample Debug PPP Negotiation Output
Router# debug ppp negotiationppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 3D56CACppp: received config for type = 4 (QUALITYTYPE) ackedppp: received config for type = 5 (MAGICNUMBER) value = 3D567F8 acked (ok)PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 3D56CACppp: ipcp_reqci: returning CONFACK.(ok)PPP Serial4: state = ACKSENT fsm_rconfack(8021): rcvd id 4describes significant fields shown in .
Explanations for each line in follow.
The first two lines in indicate that the router is trying to bring up LCP and will use the indicated negotiation options (Quality Protocol and Magic Number). The value fields are the values of the options themselves. C025/3E8 translates to Quality Protocol LQM. 3E8 is the reporting period (in hundredths of a second). 3D56CAC is the value of the Magic Number for the router.
ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 3D56CACThe next two lines indicate that the other side negotiated for options 4 and 5 as requested and acknowledged both. If the responding end does not support the options, a CONFREJ is sent by the responding node. If the responding end does not accept the value of the option, a CONFNAK is sent with the value field modified.
ppp: received config for type = 4 (QUALITYTYPE) ackedppp: received config for type = 5 (MAGICNUMBER) value = 3D567F8 acked (ok)The next three lines indicate that the router received a CONFACK from the responding side and displays accepted option values. Use the rcvd id field to verify that the CONFREQ and CONFACK have the same id field.
PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5ppp: config ACK received, type = 4 (CI_QUALITYTYPE), value = C025ppp: config ACK received, type = 5 (CI_MAGICNUMBER), value = 3D56CACThe next line indicates that the router has IP routing enabled on this interface and that the IPCP NCP negotiated successfully:
ppp: ipcp_reqci: returning CONFACK.In the last line, the router's state is listed as ACKSENT.
PPP Serial4: state = ACKSENT fsm_rconfack(C021): rcvd id 5\shows sample output when debug ppp packet and debug ppp negotiation output are enabled at the same time.
Figure 2-202 Sample Debug PPP Output—Packet and Negotiation Options Enabled
shows sample debug ppp negotiation output when the remote side of the connection is unable to respond to LQM requests.
Figure 2-203 Sample Debug PPP Negotiation Output—No Response Detected
Router# debug ppp negotiationppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44B7010ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44C1488shows sample output when no response is detected for configuration requests (with both debug ppp negotiation and debug ppp packet enabled).
Figure 2-204 Sample Debug PPP Negotiation and Packet Output—No Response Detected
Router# debug ppp negotiationRouter# debug ppp packetppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8PPP Serial4: O LCP CONFREQ(1) id 14 (12) QUALITYTYPE (8) 192 37 0 0 3 232MAGICNUMBER (6) 4 77 253 200ppp: TIMEout: Time= 44E0980 State= 3ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8PPP Serial4: O LCP CONFREQ(1) id 15 (12) QUALITYTYPE (8) 192 37 0 0 3 232MAGICNUMBER (6) 4 77 253 200ppp: TIMEout: Time= 44E1828 State= 3ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8PPP Serial4: O LCP CONFREQ(1) id 16 (12) QUALITYTYPE (8) 192 37 0 0 3 232MAGICNUMBER (6) 4 77 253 200ppp: TIMEout: Time= 44E27C8 State= 3ppp: sending CONFREQ, type = 4 (CI_QUALITYTYPE), value = C025/3E8ppp: sending CONFREQ, type = 5 (CI_MAGICNUMBER), value = 44DFDC8PPP Serial4: O LCP CONFREQ(1) id 17 (12) QUALITYTYPE (8) 192 37 0 0 3 232MAGICNUMBER (6) 4 77 253 200ppp: TIMEout: Time= 44E3768 State= 3shows sample debug ppp error output. These messages might appear when the Quality Protocol option is enabled on an interface that is already running PPP.
Figure 2-205 Sample Debug PPP Error Output
Router# debug ppp errorPPP Serial3(i): rlqr receive failure. successes = 15PPP: myrcvdiffp = 159 peerxmitdiffp = 41091PPP: myrcvdiffo = 2183 peerxmitdiffo = 1714439PPP: threshold = 25PPP Serial4(i): rlqr transmit failure. successes = 15PPP: myxmitdiffp = 41091 peerrcvdiffp = 159PPP: myxmitdiffo = 1714439 peerrcvdiffo = 2183PPP: l->OutLQRs = 1 LastOutLQRs = 1PPP: threshold = 25PPP Serial3(i): lqr_protrej() Stop sending LQRs.PPP Serial3(i): The link appears to be looped back.describes significant fields shown in .
shows sample debug ppp authentication output. Use this debug command to determine why an authentication fails.
Figure 2-206 Sample Debug PPP Authentication Output
Router# debug ppp authenticationSerial0: Unable to authenticate. No name received from peerSerial0: Unable to validate CHAP response. USERNAME pioneer not found.Serial0: Unable to validate CHAP response. No password defined for USERNAME pioneerSerial0: Failed CHAP authentication with remote.Remote message is Unknown nameSerial0: remote passed CHAP authentication.Serial0: Passed CHAP authentication with remote.Serial0: CHAP input code = 4 id = 3 len = 48In general, these messages are self-explanatory. Fields that appear in that can show optional output are outlined in .
debug ppp bap
To display general BACP transactions, use the debug ppp bap EXEC command. To disable debugging output, use the no form of this command.
[no] debug ppp bap [error | event | negotiation]
Syntax Description
Usage Guidelines
Do not use this command when memory is scarce or in very high traffic situations.
Sample Displays
The following types of events generate the debug messages displayed in the figures in this section:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
shows the basic sample output when the debug ppp bap command is used.
Figure 2-207 Sample Debug PPP BAP Output
Router# debug ppp bapBAP Virtual-Access1: group "laudrup" (2) (multilink) without precedence createdBAP laudrup: sending CallReq, id 2, len 38 on BRI3:1 to remoteBAP Virtual-Access1: received CallRsp, id 2, len 13BAP laudrup: CallRsp, id 2, ACKBAP laudrup: attempt1 to dial 19995776677 on BRI3---> reason BAP - Multilink bundle overloadedBAP laudrup: sending StatusInd, id 2, len 44 on Virtual-Access1 to remoteBAP Virtual-Access1: received StatusRsp, id 2, len 1BAP laudrup: StatusRsp, id 2, ACKdescribes some basic information about the group, the events, and the sent-message details.
Table 2-101 Debug PPP BAP Field Descriptions
The debug ppp bap event command output might show state transitions and protocol actions, in addition to the basic debug ppp bap output as displayed in .
shows state transition output that might be displayed for the command when the event keyword is used.
Figure 2-208 Debug PPP BAP Event State Transition Messages
Router# debug ppp bap eventBAP laudrup: Idle --> AddWaitBAP laudrup: AddWait --> AddPendingBAP laudrup: AddPending --> Idleshows protocol action output that might be displayed for the command when the event keyword is used.
Figure 2-209 Debug PPP BAP Event Protocol Action Messages
Router# debug ppp bap eventPeer does not support a message typeNo response to a particular requestNo response to all request retransmissionsNot configured to initiate link additionExpected action by peer has not occurredExceeded number of retriesNo links available to call outUnable to provide phone numbers for callbackMaximum number of links in the groupMinimum number of links in the groupUnable to process link addition at presentUnable to process link removal at presentNot configured/unable to initiate link removalLink addition completed notificationLink addition failed notificationDetermination of location of the group configLink with specified discriminator not in groupLink removal failedCall failure with statusFailed to dial specified numberDiscarding retransmissionUnable to find received identifierReceived StatusInd when no call pendingDiscarding message with no phone deltaUnable to send message in particular stateReceived a zero identifierRequest has precedenceThe error messages displayed in might be added to the basic output when the debug ppp bap error command is used. Because the errors are very rare, you might never see these messages.
Figure 2-210 PPP BAP Error Messages
Router# debug ppp bap errorUnable to find appropriate request for received responseInvalid message type of queueReceived request is not part of the groupAdd link attempt failed to locate groupRemove link attempt failed to locate groupUnable to inform peer of link additionChanging of precedence cannot locate groupReceived short header/illegal length/short packetInvalid configuration information lengthUnable to NAK incomplete optionsUnable to determine current number of linksNo interface list to dial onAttempt to send invalid dataLocal link discriminator is not in groupReceived response type is incorrect for identifierThe messages displayed in might be added to the basic output when the debug ppp bap negotiation command is used:
Figure 2-211 Debug PPP BAP Negotiation Messages
Router# debug ppp bap negotiationBAP laudrup: adding link speed 64 kbps for type 0x1 len 5BAP laudrup: adding reason "User initiated addition", len 25BAP laudrup: CallRsp, id 4, ACKBAP laudrup: link speed 64 kbps for types 0x1, len 5 (ACK)BAP laudrup: phone number "1: 0 2: ", len 7 (ACK)BAP laudrup: adding call status 0, action 0 len 4BAP laudrup: adding 1 phone numbers "1: 0 2: " len 7BAP laudrup: adding reason "Successfully added link", len 25BAP laudrup: StatusRsp, id 4, ACKAdditional negotiation messages might also be displayed for the following:
Received BAP messageSending messageDecode individual options for send/receiveNotification of invalid optionsshows additional reasons for a particular BAP action that might be displayed in an "adding reason" line of the debug ppp bap negotiation command output.
Figure 2-212 Additional Reasons for a BACP Negotiation Action
"Outgoing add request has precedence""Outgoing remove request has precedence""Unable to change request precedence""Unable to determine valid phone delta""Attempting to add link""Link addition is pending""Attempting to remove link""Link removal is pending""Precedence of peer marked CallReq for no action""Callback request rejected due to configuration""Call request rejected due to configuration""No links of specified type(s) available""Drop request disallowed due to configuration""Discriminator is invalid""No response to call requests""Successfully added link""Attempt to dial destination failed""No interfaces present to dial out""No dial string present to dial out""Mandatory options incomplete""Load has not exceeded threshold""Load is above threshold""Currently attempting to dial destination""No response to CallReq from race condition"describes the reasons for a BACP Negotiation Action provided in .
debug ppp multilink
Use the debug ppp multilink EXEC command to display information about individual multilink fragments and important multilink events. The no form of this command disables debugging output.
[no] debug ppp multilink
Usage Guidelines
The debug ppp multilink command has some memory overhead and should not be used when memory is scarce or in very high traffic situations.
Sample Display
Figure 2-213 shows sample debug ppp multilink output when this command is used with the ping command. The debug output indicates that a multilink PPP packet on interface BRI 0 (on the B channel) is an input (I) or output (O) packet. The output also identifies the sequence number of the packet and the size of the fragment.
Figure 2-213 Sample Debug PPP Multilink Output
Router# debug ppp multilinkRouter# ping 7.1.1.7Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 7.1.1.7, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 32/34/36 msRouter#2:00:28: MLP BRI0: B-Channel 1: O seq 80000000: size 582:00:28: MLP BRI0: B-Channel 2: O seq 40000001: size 592:00:28: MLP BRI0: B-Channel 2: I seq 40000001: size 592:00:28: MLP BRI0: B-Channel 1: I seq 80000000: size 582:00:28: MLP BRI0: B-Channel 1: O seq 80000002: size 582:00:28: MLP BRI0: B-Channel 2: O seq 40000003: size 592:00:28: MLP BRI0: B-Channel 2: I seq 40000003: size 592:00:28: MLP BRI0: B-Channel 1: I seq 80000002: size 582:00:28: MLP BRI0: B-Channel 1: O seq 80000004: size 582:00:28: MLP BRI0: B-Channel 2: O seq 40000005: size 592:00:28: MLP BRI0: B-Channel 2: I seq 40000005: size 592:00:28: MLP BRI0: B-Channel 1: I seq 80000004: size 582:00:28: MLP BRI0: B-Channel 1: O seq 80000006: size 582:00:28: MLP BRI0: B-Channel 2: O seq 40000007: size 592:00:28: MLP BRI0: B-Channel 2: I seq 40000007: size 592:00:28: MLP BRI0: B-Channel 1: I seq 80000006: size 582:00:28: MLP BRI0: B-Channel 1: O seq 80000008: size 582:00:28: MLP BRI0: B-Channel 2: O seq 40000009: size 592:00:28: MLP BRI0: B-Channel 2: I seq 40000009: size 592:00:28: MLP BRI0: B-Channel 1: I seq 80000008: size 58debug ppp multilink events
To display information about events affecting multilink groups established for BACP, use the debug ppp multilink events EXEC command. The no form of this command disables debugging output.
[no] debug ppp multilink events
Usage Guidelines
Do not use this command when memory is scarce or in very high traffic situations.
Sample Display
shows sample debug ppp multilink events command output.
Figure 2-214 Sample Debug PPP Multilink Events Output
Router# debug ppp multilink eventsMLP laudrup: established BAP group 4 on Virtual-Access1, physical BRI3:1MLP laudrup: removed BAP group 4Other event messages include the following:
Unable to find bundle for BAP group identifierUnable to find physical interface to start BAPUnable to create BAP groupAttempt to start BACP when inactive or runningAttempt to start BACP on non-MLP interfaceLink protocol has gone down, removing BAP groupLink protocol has gone down, BAP not running or presentdescribes the significant fields in .
Table 2-103 Debug PPP Multilink Events Field Descriptions
debug qllc error
Use the debug qllc error EXEC command to display quality link line control (QLLC) errors. The no form of this command disables debugging output.
[no] debug qllc error
Usage Guidelines
This command helps you track down errors in the QLLC interactions with X.25 networks. Use debug qllc error in conjunction with debug x25 all to see the connection. The data shown by this command only flows through the router on the X.25 connection. Some forms of this command can generate lots of output and network traffic.
Sample Display
shows sample debug qllc error output.
Figure 2-215 Sample Debug QLLC Error Output
Router# debug qllc error%QLLC-3-GENERRMSG: qllc_close - bad qllc pointer Caller 00407116 Caller 00400BD2QLLC 4000.1111.0002: NO X.25 connection. Dicarding XID and calling outExplanations for individual lines of output from follow.
The following line indicates that the QLLC connection was closed:
%QLLC-3-GENERRMSG: qllc_close - bad qllc pointer Caller 00407116 Caller 00400BD2The following line shows the virtual MAC address of the failed connection:
QLLC 4000.1111.0002: NO X.25 connection. Dicarding XID and calling outdebug qllc event
Use the debug qllc event EXEC command to enable debugging of QLLC events. The no form of this command disables debugging output.
[no] debug qllc event
Usage Guidelines
Use the debug qllc event command to display primitives that might affect the state of a QLLC connection. An example of these events is the allocation of a QLLC structure for a logical channel indicator when an X.25 call has been accepted with the QLLC call user data. Other examples are the receipt and transmission of LAN explorer and XID frames.
Sample Display
shows sample debug qllc event output.
Figure 2-216 Sample Debug QLLC Event Output
Router# debug qllc eventQLLC: allocating new qllc lci 9QLLC: tx POLLING TEST, da 4001.3745.1088, sa 4000.1111.0001QLLC: rx explorer response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040QLLC: gen NULL XID, da c001.3745.1088, sa 4000.1111.0001, rif 0830.1A91.1901.A040, dsap 4, ssap 4QLLC: rx XID response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040Explanations for representative lines of output in follow.
The following line indicates a new QLLC data structure has been allocated:
QLLC: allocating new qllc lci 9The following lines show transmission and receipt of LAN explorer or test frames:
QLLC: tx POLLING TEST, da 4001.3745.1088, sa 4000.1111.0001QLLC: rx explorer response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040The following lines show XID events:
QLLC: gen NULL XID, da c001.3745.1088, sa 4000.1111.0001, rif 0830.1A91.1901.A040, dsap 4, ssap 4QLLC: rx XID response, da 4000.1111.0001, sa c001.3745.1088, rif 08B0.1A91.1901.A040debug qllc packet
Use the debug qllc packet EXEC command to display QLLC events and QLLC data packets. The no form of this command disables debugging output.
[no] debug qllc packet
Usage Guidelines
This command helps you to track down errors in the QLLC interactions with X.25 networks. The data shown by this command only flows through the router on the X25 connection. Use debug qllc packet in conjunction with debug x25 all to see the connection and the data that flows through the router.
Sample Display
shows sample debug qllc packet output.
Figure 2-217 Sample Debug QLLC Packet Output
Router# debug qllc packet14:38:05: Serial2/5 QLLC I: Data Packet.-RSP 9 bytes.14:38:07: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes.14:38:07: Serial2/6 QLLC O: Data Packet. 128 bytes.14:38:08: Serial2/6 QLLC I: Data Packet.-RSP 9 bytes.14:38:08: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes.14:38:08: Serial2/6 QLLC O: Data Packet. 128 bytes.14:38:08: Serial2/6 QLLC I: Data Packet.-RSP 9 bytes.14:38:12: Serial2/5 QLLC I: Data Packet.-RSP 112 bytes.14:38:12: Serial2/5 QLLC O: Data Packet. 128 bytes.Explanations for individual lines of output from follow.
The following lines indicate a packet was received on the interfaces:
14:38:05: Serial2/5 QLLC I: Data Packet.-RSP 9 bytes.14:38:07: Serial2/6 QLLC I: Data Packet.-RSP 112 bytes.The following lines show that a packet was transmitted on the interfaces:
14:38:07: Serial2/6 QLLC O: Data Packet. 128 bytes.14:38:12: Serial2/5 QLLC O: Data Packet. 128 bytes.debug qllc state
Use the debug qllc state EXEC command to enable debugging of the QLLC events. The no form of this command disables debugging output.
[no] debug qllc state
Usage Guidelines
Use the debug qllc state command to show when the state of a QLLC connection has changed. The typical QLLC connection goes from states ADM to SETUP to NORMAL. The NORMAL state indicates that a QLLC connection exists and is ready for data transfer.
Sample Display
shows sample debug qllc state output.
Figure 2-218 Sample Debug QLLC State Output
Router# debug qllc stateSerial2 QLLC O: QSM-CMDSerial2: X25 O D1 DATA (5) Q 8 lci 9 PS 4 PR 3QLLC: state ADM -> SETUPSerial2: X25 I D1 RR (3) 8 lci 9 PR 5Serial2: X25 I D1 DATA (5) Q 8 lci 9 PS 3 PR 5Serial2 QLLC I: QUA-RSPQLLC: addr 00, ctl 73QLLC: qsetupstate: recvd qua rspQLLC: state SETUP -> NORMALExplanations for representative lines of output in follow.
The following line indicates a QLLC connection attempt is changing state from ADM to SETUP:
QLLC: state ADM -> SETUPThe following line indicates a QLLC connection attempt is changing state from SETUP to NORMAL:
QLLC: state SETUP -> NORMALdebug qllc timer
Use the debug qllc timer EXEC command to display QLLC timer events. The no form of this command disables debugging output.
[no] debug qllc timer
Usage Guidelines
The QLLC process periodically cycles and checks status of itself and its partner. If the partner is not found in the desired state, a LAPB primitive command is resent until the partner is in the desired state or the timer expires.
Sample Display
shows sample debug qllc timer output.
Figure 2-219 Sample Debug QLLC Timer Output
Router# debug qllc timer14:27:24: Qllc timer lci 257, state ADM retry count 0 Caller 00407116 Caller 00400BD214:27:34: Qllc timer lci 257, state NORMAL retry count 014:27:44: Qllc timer lci 257, state NORMAL retry count 114:27:54: Qllc timer lci 257, state NORMAL retry count 1Explanations for individual lines of output from follow.
The following line of output shows the state of a QLLC partner on a given X.25 logical channel identifier:
14:27:24: Qllc timer lci 257, state ADM retry count 0 Caller 00407116 Caller 00400BD2Other messages are informational and appear every ten seconds.
debug qllc x25
Use the debug qllc x25 EXEC command to display X.25 packets that affect a QLLC connection. The no form of this command disables debugging output.
[no] debug qllc x25
Usage Guidelines
This command is helpful to track down errors in the QLLC interactions with X.25 networks. Use debug qllc x25 in conjunction with debug x25 events or debug x25 all to see the X.25 events between the router and its partner.
Sample Display
shows sample debug qllc x25 output.
Figure 2-220 Sample Debug QLLC X25 Output
Router# debug qllc x2515:07:23: QLLC X25 notify lci 257 event 115:07:23: QLLC X25 notify lci 257 event 515:07:34: QLLC X25 notify lci 257 event 3 Caller 00407116 Caller 00400BD215:07:35: QLLC X25 notify lci 257 event 4describes fields of output that appear in .
debug radius
Use the debug radius EXEC command to display information associated with the Remote Authentication Dial-In User Server (RADIUS). The no form of this command disables debugging output.
[no] debug radius
Usage Guidelines
RADIUS is a distributed security system that secures networks against unauthorized access. Cisco supports RADIUS under the Authentication, Authorization, and Accounting (AAA) security system.
Use the debug aaa authentication command to get a high-level view of login activity. When RADIUS is used on the router, you can use the debug radius command for more detailed debugging information.
Sample Displays
shows part of the debug aaa authentication command output for a RADIUS login attempt that failed. The information indicates that RADIUS is the authentication method used.
Figure 2-221 Sample Debug AAA Authentication Output—RADIUS Login Attempt
Router# debug aaa authentication14:02:55: AAA/AUTHEN (164826761): Method=RADIUS14:02:55: AAA/AUTHEN (164826761): status = GETPASS14:03:01: AAA/AUTHEN/CONT (164826761): continue_login14:03:01: AAA/AUTHEN (164826761): status = GETPASS14:03:01: AAA/AUTHEN (164826761): Method=RADIUS14:03:04: AAA/AUTHEN (164826761): status = FAILshows part of the debug radius command output that shows a login attempt that failed because of a key mismatch (that is, a configuration problem).
Figure 2-222 Sample Debug RADIUS Output—Failed Login (Key Mismatch)
Router# debug radius13:55:19: Radius: IPC Send 0.0.0.0:1645, Access-Request, id 0x7, len 5713:55:19: Attribute 4 6 AC150E5A13:55:19: Attribute 5 6 0000000A13:55:19: Attribute 1 7 62696C6C13:55:19: Attribute 2 18 19D6648313:55:22: Radius: Received from 171.69.1.152:1645, Access-Reject, id 0x7, len 2013:55:22: Radius: Reply for 7 fails decryptshows part of the debug radius command output that shows a successful login attempt as indicated by an Access-Accept message.
Figure 2-223 Sample Debug RADIUS Output—Successful Login
Router# debug radius13:59:02: Radius: IPC Send 0.0.0.0:1645, Access-Request, id 0xB, len 5613:59:02: Attribute 4 6 AC150E5A13:59:02: Attribute 5 6 0000000A13:59:02: Attribute 1 6 62696C6C13:59:02: Attribute 2 18 0531FEA313:59:04: Radius: Received from 171.69.1.152:1645, Access-Accept, id 0xB, len 2613:59:04: Attribute 6 6 00000001shows part of the debug radius command output that shows an unsuccessful login attempt as indicated by the Access-Reject message.
Figure 2-224 Sample Debug RADIUS Output—Failed Login
Router# debug radius13:57:56: Radius: IPC Send 0.0.0.0:1645, Access-Request, id 0xA, len 5713:57:56: Attribute 4 6 AC150E5A13:57:56: Attribute 5 6 0000000A13:57:56: Attribute 1 7 62696C6C13:57:56: Attribute 2 18 49C28F6C13:57:59: Radius: Received from 171.69.1.152:1645, Access-Reject, id 0xA, len 20Related Commands
debug aaa accounting
debug aaa authenticationdebug rif
Use the debug rif EXEC command to display information on entries entering and leaving the routing information field (RIF) cache. The no form of this command disables debugging output.
[no] debug rif
Usage Guidelines
In order to use the debug rif command to display traffic source-routed through an interface, fast switching of source route bridging (SRB) frames must first be disabled with the no source-bridge route-cache interface configuration command.
Sample Display
shows sample debug rif output.
Figure 2-225 Sample Debug RIF Output
Explanations for representative lines of debug rif output in follow.
The first line of output is an example of a RIF entry for an interface configured for SDLLC or Local-Ack. describes significant fields shown in this line of debug rif output.
The following line of output is an example of a RIF entry for an interface that is not configured for SDLLC or Local-Ack:
RIF: U chk da=0000.3080.4aed,sa=0000.0000.0000 [] type 8 on TokenRing0/0Notice that the source address contains only zero values (0000.0000.0000), and that the RIF string is null ([ ]). The last element in the entry indicates that this route was learned from a virtual ring, rather than a real Token Ring port.
The following line shows that a new entry has been added to the RIF cache:
RIF: U add 1000.5a59.04f9 [4880.3201.00A1.0050] type 8The following line shows that a RIF cache lookup operation has taken place:
RIF: L checking da=0000.3080.4aed, sa=0000.0000.0000The following line shows that a TEST response from address 9000.5a59.04f9 was inserted into the RIF cache:
RIF: rcvd TEST response from 9000.5a59.04f9The following line shows that the RIF entry for this route has been found and updated:
RIF: U upd da=1000.5a59.04f9,sa=0110.2222.33c1 [4880.3201.00A1.0050]The following line shows that an XID response from this address was inserted into the RIF cache:
RIF: rcvd XID response from 9000.5a59.04f9The following line shows that the router sent an XID response to this address:
SR1: sent XID response to 9000.5a59.04f9explains the other possible lines of debug rif output.
Related Command
debug rtr error
Use the debug rtr error EXEC command to enable logging of response time reporter runtime errors. The no form of this command disables debugging output—including the debug rtr trace command.
[no] debug rtr error [probe]
Syntax Description:
Usage Guidelines
The response time reporter feature allows you to monitor network performance and network resources by measuring response times and availability. With this feature you can perform troubleshooting, problem notifications, and preproblem analysis based on response time reporter statistics.
The debug rtr error command displays runtime errors. When a probe number other than 0 is specified, all runtime errors for that probe are displayed when the probe is active. When the probe number is 0, all runtime errors relating to the response time reporter scheduler process are displayed. When no probe number is specified, all runtime errors for all active probes configured on the router and probe control are displayed. The response time reporter scheduler process is responsible for starting and stopping probes and managing the database.
Note
Because the trace output generated by the debug rtr trace command uses the same control mechanism as debug rtr error, the no debug rtr error command disables both logging and tracing.
Sample Display
shows sample debug rtr error output. All debug output for the response time reporter (including debug rtr trace) has the format shown in .
Figure 2-226 Sample Debug RTR Error Output
Router# debug rtr error 1RTR 1: Error Return Code - LU0 RTR Probe 1in echoTarget on call luReceiveLuApiReturnCode of InvalidHandle - invalid host name or API handleshows describes the fields and messages shown in .
Related Command
debug rtr trace
Use the debug rtr trace EXEC command to trace the execution of a response time reporter probe. The no form of this command disables trace debugging output (but not debug rtr error output).
[no] debug rtr trace [probe]
Syntax Description:
Usage Guidelines
Note
When a probe number other than 0 is specified, execution for that probe is traced. When the probe number is 0, the response time reporter scheduler process is traced. When no probe number is specified, all active probes and every probe control is traced. The response time reporter scheduler process is responsible for starting and stopping probes and managing the database.
The debug rtr trace command also enables debug rtr error for the specified probe. However, the no debug rtr trace command does not disable the debug rtr error command. You must manually disable the command by using the no debug rtr error command.
All debug output (including debug rtr error) has the format shown in the debug rtr error output example in .
Sample Display
shows a partial sample of debug rtr trace output. In this example, a probe is traced through a single operation attempt: the setup of a connection to the target (LU0), the attempt at an echo, and the closing of the connection on the echo attempt.
Figure 2-227 Sample Debug RTR Trace Output
Router# debug rtr traceRTR 1: Calling getRttMonOperState (check pending) - LU0 RTR Probe 1RTR 1: Calling getRttMonOperState (check death) - LU0 RTR Probe 1RTR 1: Starting An Echo Operation - LU0 RTR Probe 1RTR 1: setting receiveFinished to FALSE - LU0 RTR Probe 1in dependLuEchoApplicationRTR 1: openConnection called - LU0 RTR Probe 1Calling rttMonHopConnectedRTR 1: calling luT0orT2Open - LU0 RTR Probe 1RTR 1: Dumping luT0orT2Open Result - LU0 RTR Probe 1applicationHandle: inRttMonCtrlAdminQItem = 13920808receiveFinished = FALSE currentLUHandle = 14199576maxRespBufferLen = 52 receivedBufferLen = 0aHostName = CWBC02 locAddr = 1 eApplNameLen = 7ApplName = D5E2D7C5C3C8D60 eModeName = 4040404040404040 userDataLen = 14userData = D5E2D7C5C3C8D61 sysSense = 0 userSense = 0 bindDataLen = 64bindData = D5E2D7C5C3C8D61 bindDataCount = 14RTR 1: Calling rttMonSetConnectionHandle - LU0 RTR Probe 1RTR 1: Calling rttMonSetHopConnectedState to TRUE - LU0 RTR Probe 1RTR 1: Calling rttMonSetDiagText - LU0 RTR Probe 1RTR 1: setupPathInfo called - LU0 RTR Probe 1Calling rttMonStartUpdatePathRTR 1: Calling rttMonUpdatePath - LU0 RTR Probe 1for Target CWBC02 NSPECHORTR 1: Calling rttMonEndUpdatePath - LU0 RTR Probe 1RTR 1: Calling rttMonUpdateNumberOfEchosAttempted - LU0 RTR Probe 1RTR 1: performEcho called - LU0 RTR Probe 1applicationHandle: inRttMonCtrlAdminQItem = 13920808receiveFinished = FALSE currentLUHandle = 14199576maxRespBufferLen = 52 receivedBufferLen = 0echoTimeout (milliseconds) = 5000 sequenceNum = 886rttMonEchoAdminTargetAddress is CWBC02 NSPECHOverifyDataFlag = FalseRTR 1: Calling rttMonGetFirstStoredHopAddress - LU0 RTR Probe 1RTR 1: echoTarget called - LU0 RTR Probe 1applicationHandle: inRttMonCtrlAdminQItem = 13920808receiveFinished = FALSE currentLUHandle = 14199576maxRespBufferLen = 52 receivedBufferLen = 0echoTimeout (milliseconds) = 5000Data:E6 A7 E8 A9 01 02 03 77 00 00 00 00 C1calling luReceive...RTR 1: calling luSend - LU0 RTR Probe 1RTR 1: receiveFinished is FALSE - LU0 RTR Probe 1in echoTarget callingprocess_wait_for_event_timed(5000 milliseconds)RTR 1: rtt_closeIndication called - DSPU Msg ProcapplicationHandle: inRttMonCtrlAdminQItem = 13920808receiveFinished = FALSE currentLUHandle = 14199576maxRespBufferLen = 52 receivedBufferLen = 0RTR 1: setting receiveFinished to TRUE - DSPU Msg Procin rtt_closeIndicationRTR 1: Woke on receive event - LU0 RTR Probe 1RTR 1: returned from echoTarget - LU0 RTR Probe 1with D_echoTarget_connectionLost return_codeand responseTime (milliseconds) = 196...RTR 1: Calling getRttMonOperState (check active) - LU0 RTR Probe 1RTR 1: Going to Sleep - LU0 RTR Probe 1until next frequency time (delta milliseconds 60000)Related Command
debug sdlc
Use the debug sdlc EXEC command to display information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions. The no form of this command disables debugging output.
[no] debug sdlc
Usage Guidelines
Note
Sample Display
shows sample debug sdlc output.
Figure 2-228 Sample Debug SDLC Output
Router# debug sdlcSDLC: Sending RR at location 4Serial3: SDLC O (12495952) C2 CONNECT (2) RR P/F 6Serial3: SDLC I (12495964) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0]Serial3: SDLC T [C2] 12496064 CONNECT 12496064 0SDLC: Sending RR at location 4Serial3: SDLC O (12496064) C2 CONNECT (2) RR P/F 6Serial3: SDLC I (12496076) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0]Serial3: SDLC T [C2] 12496176 CONNECT 12496176 0Explanations for individual lines of output from follow.
The following line of output indicates that the router is sending a Receiver Ready packet at location 4 in the code:
SDLC: Sending RR at location 4The following line of output describes a frame input event:
Serial3: SDLC O (12495952) C2 CONNECT (2) RR P/F 6describes the fields in this line of output.
The following line of output describes a frame input event:
Serial3: SDLC I (12495964) [C2] CONNECT (2) RR P/F 0 (R) [VR: 6 VS: 0] rfp: PIn addition to the fields described in , output for a frame input event also includes the additional fields described in .
The following line of output describes a frame timer event:
Serial3: SDLC T [C2] 12496064 CONNECT 12496064 0describes the fields in this line of output.
Related Command
debug sdlc local-ack
Use the debug sdlc local-ack EXEC command to display information on the local acknowledgment feature. The no form of this command disables debugging output.
[no] debug sdlc local-ack [number]
Syntax Description
Usage Guidelines
You can select the frame types you want to monitor; the frame types correspond to bit flags. You can select 1, 2, 4, or 7, which is the decimal value of the bit flag settings. If you select 1, the octet is set to 00000001. If you select 2, the octet is set to 0000010. If you select 4, the octet is set to 00000100. If you want to select all frame types, select 7; the octet is 00000111. The default is 7 for all events. defines these bit flags.
CautionBecause using this command is processor intensive, it is best to use it after hours, rather than in a production environment. It is also best to use this command by itself, rather than in conjunction with other debugging commands.
Sample Display
shows sample debug sdlc local-ack output.
Figure 2-229 Sample Debug SDLC Local-Ack Output
Explanations for individual lines of output from follow.
The first line shows the input to the SDLC local acknowledgment state machine:
SLACK (Serial3): Input = Network, LinkupRequestdescribes the fields in this line of output.
The second line shows the change in the SDLC local acknowledgment state machine. In this case the AwaitSdlcOpen state is an internal state that has not changed while this display was captured.
SLACK (Serial3): Old State = AwaitSdlcOpen New State = AwaitSdlcOpenThe third line shows the output from the SDLC local acknowledgment state machine:
SLACK (Serial3): Output = SDLC, SNRMdebug sdlc packet
Use the debug sdlc packet EXEC command to display packet information on Synchronous Data Link Control (SDLC) frames received and sent by any router serial interface involved in supporting SDLC end station functions. The no form of this command disables debugging output.
[no] debug sdlc packet [max-bytes]
Syntax Description
Usage Guidelines
This command requires intensive CPU processing; therefore, we recommend not using it when the router is expected to handle normal network loads, such as in a production environment. Instead, use this command when network response is non-critical. We also recommend that you use this command by itself, rather than in conjunction with other debug commands.
Sample Display
shows sample debug sdlc packet output with the packet display limited to 20 bytes of data.
Figure 2-230 Sample Debug SDLC Packet Output
Router# debug sdlc packet 20Serial3 SDLC Output00000 C3842C00 02010010 019000C5 C5C5C5C5 Cd.........EEEEE00010 C5C5C5C5 EEEESerial3 SDLC Output00000 C3962C00 02010011 039020F2 Co.........2Serial3 SDLC Output00000 C4962C00 0201000C 039020F2 Do.........2Serial3 SDLC Input00000 C491 Djdebug sdllc
Use the debug sdllc EXEC command to display information about data link layer frames transferred between a device on a Token Ring and a device on a serial line via a router configured with the SDLLC feature. The no form of this command disables debugging output.
[no] debug sdllc
Usage Guidelines
The SDLLC feature translates between the SDLC link layer protocol used to communicate with devices on a serial line and the LLC2 link layer protocol used to communicate with devices on a Token Ring.
The router configured with the SDLLC feature must be attached to the serial line. The router sends and receives frames on behalf of the serial device on the attached serial line but acts as an SDLC station.
The topology between the router configured with the SDLLC feature and the Token Ring is network dependent and is not limited by the SDLLC feature.
Sample Display
shows sample debug sdllc output between link layer peers from the perspective of the SDLLC-configured router.
Figure 2-231 Sample Debug SDLLC Output
Router# debug sdllcSDLLC: rx explorer rsp, da 4000.2000.1001, sa C000.1020.1000, rif8840.0011.00A1.0050SDLLC: tx short xid, sa 4000.2000.1001, da C000.1020.1000, rif88C0.0011.00A1.0050, dsap 4 ssap 4SDLLC: tx long xid, sa 4000.2000.1001, da C000.1020.1000, rif88C0.0011.00A1.0050, dsap 4 ssap 4Rcvd SABME/LINKUP_REQ pak from TR hostSDLLCERR: not from our partner, pak dropped, da 4000.2000.1001,sa C000.1020.1000, rif 8840.0011.00A1.0050, partner = 5000.1040.1003describes significant fields shown in .
The following line indicates that an explorer frame response was received by the router at address 4000.2000.1001 from the FEP at address C000.1020.1000 with the specified RIF. The original explorer sent to the FEP from the router is not monitored as part of the debug sdllc command.
SDLLC: rx explorer rsp, da 4000.2000.1001, sa C000.1020.1000, rif8840.0011.00A1.0050The following line indicates that the router sent the null XID (Type 0) to the FEP. The debugging information does not include the response to the XID message sent by the FEP to the router.
SDLLC: tx short xid, sa 4000.2000.1001, da C000.1020.1000, rif88C0.0011.00A1.0050, dsap 4 ssap 4The following line indicates that the router sent the XID command (Format 0 Type 2) to the FEP:
SDLLC: tx long xid, sa 4000.2000.1001, da C000.1020.1000, rif88C0.0011.00A1.0050, dsap 4 ssap 4The following line is the SABME response to the XID command previously sent by the router to the FEP:
Rcvd SABME/LINKUP_REQ pak from TR host
