-
Cisco IOS Release 12.0 Debug Command Reference
-
About This Manual
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
Debug Commands (debug aaa accounting - debug appn trs)
-
Debug Commands (debug arap - debug channel packets)
-
Debug Commands (debug clns esis events - debug dialer events)
-
Debug Commands (debug dlsw - debug ip cef accounting non-recursive)
-
Debug Command (debug ip drp - debug ip packet)
-
Debug Commands (debug ip pim - debug ip wccp packets)
-
Debug Commands (debug ipx ipxwan - debug kerberos)
-
Debug Commands (debug lane client - debug local-ack state)
-
Debug Commands (debug modem - debug ppp)
-
Debug Commands (debug ppp bap - debug sdllc)
-
Debug Commands (debug serial interface - debug tacacs events)
-
Debug Commands (debug tag-switching adjacency - debug tag-switc
-
Debug Commands (debug tarp events - debug voip ccapi inout)
-
Debug Commands (debug vpdn - debug xns routing)
-
Appendix A: X.25 Cause and Diagnostic Codes
-
Appendix B: ISDN Switch Types, Codes, and Values
-
Table Of Contents
Sample Debug DLSW Peer Messages
Sample Debug DLSw Reachability Messages
debug frame-relay informationelements
debug frame-relay ip tcp header-compression
debug frame-relay networklayerinterface
debug ip cef accounting non-recursive
debug dlsw
Use the debug dlsw EXEC command to enable debugging of DLSw+. The no form of this command disables debugging output.
[no] debug dlsw [border-peers [interface interface | ip address ip-address] | core
[flow-control | messages | state | xid] [circuit-number] | local-circuit circuit-number | peers
[interface interface [fast-errors | fast-paks] | ip address ip-address [fast-errors |
fast-paks | fst-seq | udp]] | reachability [error | verbose] [sna | netbios]]Syntax Description
Usage Guidelines
When you specify no optional keywords, the debug dlsw command enables all available DLSw debugging output.
Normally you need to use only the error or verbose option of the debug dlsw reachability command to help identify problems. The error option is recommended for use by customers and provides a subset of the messages from the normal event-level debugging. The verbose option provides a very detailed view of what is going on and is typically used only by service personnel.
To reduce the amount of debug information displayed, use the sna or netbios options with the debug dlsw reachability command if you know that you have an SNA or NetBIOS problem.
The DLSw core is the engine that is responsible for the establishment and maintenance of remote circuits. If possible, specifying the index of the specific circuit you want to debug reduces the amount of output displayed. However, if you want to watch a circuit initially come up, do not use the circuit-number option with the core keyword.
The core flow-control option provides information about congestion in the WAN or at the remote end station. In these cases, DLSw sends Receiver Not Ready (RNR) frames on its local circuits, slowing data traffic on established sessions and giving the congestion an opportunity to clear.
The core state option allows you to see when the circuit changes state. This capability is especially useful for determining why a session cannot be established or why a session is being disconnected.
The core XID option allows you to track the XID-state machine. The router tracks XID commands and responses used in negotiations between end stations before establishing a session.
Sample Display
The following sections show and explain some of the typical DLSw debug messages you might see when using the debug dlsw command.
Sample Debug DLSW Peer Messages
The following example enables UDP packet debugging for a specific remote peer:
Router# debug dlsw peer ip-address 1.1.1.6 udpThe following message is sample output from the debug dlsw border-peers command:
*Mar 10 17:39:56: CSM: delete group mac cache for group 0*Mar 10 17:39:56: CSM: delete group name cache for group 0*Mar 10 17:40:19: CSM: update group cache for mac 0000.3072.1070, group 10*Mar 10 17:40:22: DLSw: send_to_group_members(): copy to peer 10.19.32.5The following message is from a router that initiated a TCP connection:
DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:ADMIN-OPEN CONNECTION state:DISCONNDLSw: dtp_action_a() attempting to connect peer 10.3.8.7(2065)DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:DISCONN->WAIT_WRDLSw: Async Open Callback 10.3.8.7(2065) -> 11002DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR DLSw: dtp_action_f() start read open timer for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_WR->WAIT_RD DLSw: passive open 10.3.8.7(11004) -> 2065 DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD DLSw: dtp_action_g() read pipe opened for peer 10.3.8.7(2065) DLSw: CapExId Msg sent to peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_RD->WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) DLSw: Recv CapExId Msg from peer 10.3.8.7(2065) DLSw: Pos CapExResp sent to peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) DLSw: Recv CapExPosRsp Msg from peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dtp_action_k() cap xchged for peer 10.3.8.7(2065) DLSw: closing read pipe tcp connection for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->PCONN_WT DLSw: Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-PEER CONNECTED state:PCONN_WT DLSw: dtp_action_m() peer connected for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:PCONN_WT->CONNECT DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:CORE-ADD CIRCUIT state:CONNECT DLSw: dtp_action_u(), peer add circuit for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:CONNECT->CONNECTThe following message is from a router that received a TCP connection:
DLSw: passive open 10.10.10.4(11002) -> 2065 DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-RD PIPE OPENED state:DISCONN DLSw: dtp_action_c() opening write pipe for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:DISCONN->WWR_RDOP DLSw: Async Open Callback 10.10.10.4(2065) -> 11004 DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-WR PIPE OPENED state:WWR_RDOP DLSw: dtp_action_i() write pipe opened for peer 10.10.10.4(2065) DLSw: CapExId Msg sent to peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WWR_RDOP->WAIT_CAP DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.10.10.4(2065) DLSw: Recv CapExId Msg from peer 10.10.10.4(2065) DLSw: Pos CapExResp sent to peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->WAIT_CAP DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.10.10.4(2065) DLSw: Recv CapExPosRsp Msg from peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dtp_action_k() cap xchged for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->PCONN_WT DLSw: dlsw_tcpd_fini() for peer 10.10.10.4(2065) DLSw: dlsw_tcpd_fini() closing write pipe for peer 10.10.10.4 DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-CLOSE WR PIPE state:PCONN_WT DLSw: dtp_action_l() close write pipe for peer 10.10.10.4(2065) DLSw: closing write pipe tcp connection for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:PCONN_WT->PCONN_WT DLSw: Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-PEER CONNECTED state:PCONN_WT DLSw: dtp_action_m() peer connected for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:PCONN_WT->CONNECT DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:CORE-ADD CIRCUIT state:CONNECT DLSw: dtp_action_u(), peer add circuit for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:CONNECT->CONNECTThe following message is from a router that initiated an FST connection:
DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:ADMIN-OPEN CONNECTION state:DISCONN DLSw: dfstp_action_a() attempting to connect peer 10.10.10.4(0) DLSw: Connection opened for peer 10.10.10.4(0) DLSw: CapExId Msg sent to peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:DISCONN->WAIT_CAP DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dfstp_action_e() cap msg rcvd for peer 10.10.10.4(0) DLSw: Recv CapExPosRsp Msg from peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->WAIT_CAP DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dfstp_action_e() cap msg rcvd for peer 10.10.10.4(0) DLSw: Recv CapExId Msg from peer 10.10.10.4(0) DLSw: Pos CapExResp sent to peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dfstp_action_f() cap xchged for peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->CONNECTThe following message is from a router that received an FST connection:
DLSw: START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP MSG RCVD state:DISCONN DLSw: dfstp_action_c() cap msg rcvd for peer 10.3.8.7(0) DLSw: Recv CapExId Msg from peer 10.3.8.7(0) DLSw: Pos CapExResp sent to peer 10.3.8.7(0) DLSw: CapExId Msg sent to peer 10.3.8.7(0) DLSw: END-FSTPFSM (peer 10.3.8.7(0)): state:DISCONN->WAIT_CAP DLSw: START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dfstp_action_e() cap msg rcvd for peer 10.3.8.7(0) DLSw: Recv CapExPosRsp Msg from peer 10.3.8.7(0) DLSw: END-FSTPFSM (peer 10.3.8.7(0)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dfstp_action_f() cap xchged for peer 10.3.8.7(0) DLSw: END-FSTPFSM (peer 10.3.8.7(0)): state:WAIT_CAP->CONNECTThe following message is from a router that initiated an LLC2 connection:
DLSw-LLC2: Sending enable port ; port no : 0PEER-DISP Sent : CLSI Msg : ENABLE.Req dlen: 20DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20DLSw-LLC2 : Sending activate sap for Serial1 - port_id = 887C3Cport_type = 7 dgra(UsapID) = 952458PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req dlen: 60DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60DLSw Got ActSapcnf back for Serial1 - port_id = 8978204, port_type = 7, psap_id = 0DLSw: START-LLC2PFSM (peer on interface Serial1): event:ADMIN-OPEN CONNECTION state:DISCONNDLSw: dllc2p_action_a() attempting to connect peer on interface Serial1PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 106DLSw: END-LLC2PFSM (peer on interface Serial1): state:DISCONN->ROS_SENTDLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-REQOPNSTN.CNF state:ROS_SENTDLSw: dllc2p_action_c()PEER-DISP Sent : CLSI Msg : CONNECT.Req dlen: 16DLSw: END-LLC2PFSM (peer on interface Serial1): state:ROS_SENT->CON_PENDDLSw: Peer Received : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 28DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-CONNECT.CNF state:CON_PENDDLSw: dllc2p_action_e() send capabilities to peer on interface Serial1PEER-DISP Sent : CLSI Msg : SIGNAL_STN.Req dlen: 8PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 418DLSw: CapExId Msg sent to peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:CON_PEND->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 418DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1DLSw: Recv CapExId Msg from peer on interface Serial1PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 96DLSw: Pos CapExResp sent to peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 96DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1DLSw: Recv CapExPosRsp Msg from peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAPDLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAPDLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP EXCHANGED state:WAIT_CAPDLSw: dllc2p_action_l() cap xchged for peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->CONNECTThe following message is from a router that received an LLC2 connection:
DLSw-LLC2: Sending enable port ; port no : 0PEER-DISP Sent : CLSI Msg : ENABLE.Req dlen: 20DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20DLSw-LLC2 : Sending activate sap for Serial0 - port_id = 887C3Cport_type = 7 dgra(UsapID) = 93AB34PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req dlen: 60DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60DLSw Got ActSapcnf back for Serial0 - port_id = 8944700, port_type = 7, psap_id = 0DLSw: Peer Received : CLSI Msg : CONECT_STN.Ind dlen: 39DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECT_STN.IND state:DISCONNDLSw: dllc2p_action_s() conn_stn for peer on interface Serial0PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 106DLSw: END-LLC2PFSM (peer on interface Serial0): state:DISCONN->CONS_PENDDLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-REQOPNSTN.CNF state:CONS_PENDDLSw: dllc2p_action_h() send capabilities to peer on interface Serial0PEER-DISP Sent : CLSI Msg : CONNECT.Rsp dlen: 20PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 418DLSw: CapExId Msg sent to peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:CONS_PEND->WAIT_CAPDLSw: Peer Received : CLSI Msg : CONNECTED.Ind dlen: 8DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECTED.IND state:WAIT_CAPDLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 418DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0DLSw: Recv CapExId Msg from peer on interface Serial0PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 96DLSw: Pos CapExResp sent to peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 96DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0DLSw: Recv CapExPosRsp Msg from peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAPDLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAPDLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP EXCHANGED state:WAIT_CAPDLSw: dllc2p_action_l() cap xchged for peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->CONNECTThe following messages occur when a CUR_ex (CANUREACH explorer) frame is received from other peers, and the peer statements or the promiscuous keyword have not been enabled so that the router is not configured correctly:
22:42:44: DLSw: Not promiscuous - Rej conn from 172.20.96.1(2065)22:42:51: DLSw: Not promiscuous - Rej conn from 172.20.99.1(2065)In the following messages, the router sends a keepalive message every 30 seconds to keep the peer connected. If three keepalive messages are missed, the peer is torn down. These messages are displayed only if keepalives are enabled (by default, keepalives are disabled):
22:44:03: DLSw: Keepalive Request sent to peer 172.20.98.1(2065) (168243148)22:44:03: DLSw: Keepalive Response from peer 172.20.98.1(2065) (168243176)22:44:34: DLSw: Keepalive Request sent to peer 172.20.98.1(2065) (168274148)22:44:34: DLSw: Keepalive Response from peer 172.20.98.1(2065) (168274172)The following peer debug messages indicate that the local peer is disconnecting from the specified remote peer because of missed peer keepalives:
0:03:24: DLSw: keepalive failure for peer on interface Serial00:03:24: DLSw: action_d(): for peer on interface Serial00:03:24: DLSW: DIRECT aborting connection for peer on interface Serial00:03:24: DLSw: peer on interface Serial0, old state CONNECT, new state DISCONNThe following peer debug messages result from an attempt to connect to an IP address that does not have DLSw enabled. The local router attempts to connect in 30-second intervals:
23:13:22: action_a() attempting to connect peer 172.20.100.1(2065)23:13:22: DLSw: CONN: peer 172.20.100.1 open failed, rejected [9]23:13:22: action_a() retries: 8 next conn time: 86123250423:13:52: action_a() attempting to connect peer 172.20.100.1(2065)23:13:52: DLSw: CONN: peer 172.20.100.1 open failed, rejected [9]23:13:52: action_a() retries: 9 next conn time: 861292536The following peer debug messages indicates a remote-peer statement is missing on the router (address 172.20.100.1) to which the connection attempt is sent:
23:14:52: action_a() attempting to connect peer 172.20.100.1(2065)23:14:52: DLSw: action_a(): Write pipe opened for peer 172.20.100.1(2065)23:14:52: DLSw: peer 172.20.100.1(2065), old state DISCONN, new state WAIT_RD23:14:52: DLSw: dlsw_tcpd_fini() closing connection for peer 172.20.100.123:14:52: DLSw: action_d(): for peer 172.20.100.1(2065)23:14:52: DLSw: aborting tcp connection for peer 172.20.100.1(2065)23:14:52: DLSw: peer 172.20.100.1(2065), old state WAIT_RD, new state DISCONNThe following messages show a peer connection opening with no errors or abnormal events:
23:16:37: action_a() attempting to connect peer 172.20.100.1(2065)23:16:37: DLSw: action_a(): Write pipe opened for peer 172.20.100.1(2065)23:16:37: DLSw: peer 172.20.100.1(2065), old state DISCONN, new state WAIT_RD23:16:37: DLSW: passive open 172.20.100.1(17762) -> 206523:16:37: DLSw: action_c(): for peer 172.20.100.1(2065)23:16:37: DLSw: peer 172.20.100.1(2065), old state WAIT_RD, new state CAP_EXG23:16:37: DLSw: peer 172.20.100.1(2065) conn_start_time set to 86139778423:16:37: DLSw: CapExId Msg sent to peer 172.20.100.1(2065)23:16:37: DLSw: Recv CapExId Msg from peer 172.20.100.1(2065)23:16:37: DLSw: Pos CapExResp sent to peer 172.20.100.1(2065)23:16:37: DLSw: action_e(): for peer 172.20.100.1(2065)23:16:37: DLSw: Recv CapExPosRsp Msg from peer 172.20.100.1(2065)23:16:37: DLSw: action_e(): for peer 172.20.100.1(2065)23:16:37: DLSw: peer 172.20.100.1(2065), old state CAP_EXG, new state CONNECT23:16:37: DLSw: dlsw_tcpd_fini() closing write pipe for peer 172.20.100.123:16:37: DLSw: action_g(): for peer 172.20.100.1(2065)23:16:37: DLSw: closing write pipe tcp connection for peer 172.20.100.1(2065)23:16:38: DLSw: peer_act_on_capabilities() for peer 172.20.100.1(2065)The following two messages show that an information frame is passing through the router:
DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:5 rs:4 i:34DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:4 rs:4 i:34Sample Debug DLSw Reachability Messages
The messages in this section are based on the following items:
•
Reachability is stored in cache. DLSw+ maintains two reachability caches: one for MAC addresses and one for NetBIOS names. Depending on how long entries have been in the cache, they are either fresh or stale.
•
•
•
•
describes the debug output indicating that the DLSW router received an SSP message that is flow controlled and should be counted against the sender's window.
Dec 6 11:26:49: CSM: Received SSP CUR csex flags = 80, mac 4000.90b1.26cf,The csex flags = 80 means that this is an CUR_ex (explorer).Dec 5 10:48:33: DLSw: 1620175180 decr r - s:27 so:0 r:27 ro:0Table 32 Debug Output Descriptions
The following message shows that DLSw is sending an I frame to a LAN:
Dec 5 10:48:33: DISP Sent : CLSI Msg : DATA.Req dlen: 1086The following message shows that DLSw received the I frame from the LAN:
Dec 5 10:48:35: DLSW Received-disp : CLSI Msg : DATA.Ind dlen: 4The following messages show that the reachability cache is cleared:
Router# clear dlsw rea23:44:11: CSM: Clearing CSM cache23:44:11: CSM: delete local mac cache for port 023:44:11: CSM: delete local name cache for port 023:44:11: CSM: delete remote mac cache for peer 023:44:11: CSM: delete remote name cash dlsw reaThe next group of messages show that the DLSw reachability cache is added, and that a name query is perform from the router Marian:
23:45:11: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:11: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:11: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:11: CSM: update local cache for name MARIAN , port 5EFBB423:45:11: CSM: Received CLS_UDATA_STN from Core23:45:11: CSM: Received netbios frame type A23:45:11: CSM: Processing Name Query23:45:11: CSM: Netbios Name Query: ws_status = 623:45:11: CSM: Write to peer 0 ok.23:45:11: CSM: Freeing clsi message23:45:11: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:11: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:11: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:11: CSM: update local cache for name MARIAN , port 658AB423:45:11: CSM: Received CLS_UDATA_STN from Core23:45:11: CSM: Received netbios frame type A23:45:11: CSM: Processing Name Query23:45:11: CSM: Netbios Name Query: ws_status = 523:45:11: CSM: DLXNR_PEND match found.... drop name query23:45:11: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:12: CSM: update local cache for name MARIAN , port 5EFBB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:12: CSM: update local cache for name MARIAN , port 658AB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:12: CSM: update local cache for name MARIAN , port 5EFBB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:12: CSM: update local cache for name MARIAN , port 658AB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:18: CSM: Deleting Reachability cache23:45:18: CSM: Deleting DLX NR pending record....23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:38: CSM: update local cache for name MARIAN , port 5EFBB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi message23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:38: CSM: update local cache for name MARIAN , port 658AB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi messageThe following messages show that Marian is added to the network:
23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:38: CSM: update local cache for name MARIAN , port 5EFBB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi message23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:38: CSM: update local cache for name MARIAN , port 658AB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi messageIn the next group of messages, an attempt is made to add the router Ginger on the Ethernet:
0:07:44: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB40:07:44: CSM: 0004.f545.24e6 passes local mac excl. filter0:07:44: CSM: update local cache for mac 0004.f545.24e6, port 658AB40:07:44: CSM: update local cache for name GINGER , port 658AB40:07:44: CSM: Received CLS_UDATA_STN from Core0:07:44: CSM: Received netbios frame type 80:07:44: CSM: Write to peer 0 ok.In the following example, the output from the show dlsw reachability command indicates that Ginger is on the Ethernet interface and Marian is on the Token Ring interface:
G41# show dlsw reachabilityDLSw MAC address reachability cache listMac Addr status Loc. peer/port rif0004.f545.24e6 FOUND LOCAL P007-S000 --no rif--0800.5a30.7a9b FOUND LOCAL P000-S000 06C0.0621.7D00P007-S000 F0F8.0006.A6FC.005F.F100.0000.0000.0000DLSw NetBIOS Name reachability cache listNetBIOS Name status Loc. peer/port rifGINGER FOUND LOCAL P007-S000 --no rif--MARIAN FOUND LOCAL P000-S000 06C0.0621.7D00P007-S000 --no rif--debug drip event
Use the debug drip event privileged EXEC command to display debug messages for DRIP events. Use the no form of this command to disable debugging output.
[no] debug drip event
Default
Debugging is disabled for DRiP events.
Usage Guidelines
When a Fast Ethernet subinterface is configured for TRISL encapsulation and a TrCRF is defined, the DRiP protocol is activated. The DRiP protocol adds the VLAN ID specified in the router command to its database and recognizes the VLAN as a locally configured, active VLAN.
Sample Display
The following is sample output from the debug drip event command:
75-2(config-subif)#encapsulation tr-isl trbrf-vlan 999 bridge-num 9DRiP is initiated when a local VLAN is added to the DRiP database:
DRIP : initThe VLAN ID is added locally when TRISL is configured:
DRIP : configure vlanNo = 100DRiP is configuring the VLAN:VLAN 100 is activated in the database:
DRIP : local status active for vlanNo = 100DRIP : resolve local - DRIP_VLAN_ACTIVEDRiP acknowledges that a VLAN is active and is now capable of printing any debug information, if necessary:
DRIP Change notification active vlan 100DRIP : State notificationDRIP Change notification active vlan 100DRiP logs the new VLAN ID:
DRIP : configure - ADD_ID 2DRIP will send an advertisement on all its trunk ports:
DRIP : configure - send_adv = TRUEDRiP provides information of the trunk port and the length of the packet:
DRIP : transmit on 0000.0c50.1900, length = 24DRiP gets a packet from the network:
612B92C0: 01000C00 00000000 0C501900 0000AAAA .........P....**612B92D0: 0300000C 00020000 00000100 0CCCCCCC .............LLL612B92E0: 00000C50 19000020 AAAA0300 000C0102 ...P... **......612B92F0: 01010114 00000002 00000002 00000C50 ...............P612B9300: 19000001 04C00064 04 .....@.d.DRiP gets a packet from the network:
Recvd. pakDRiP recognizes that the VLAN ID it is getting is a new one from the network:
6116C840: 0100 0CCCCCCC ...LLL6116C850: 00102F72 CBFB0024 AAAA0300 000C0102 ../rK{.$**......6116C860: 01FF0214 0002E254 00015003 00102F72 ......bT..P.../r6116C870: C8000010 04C00014 044003EB 14 H....@...@.k.DRIP : remote update - Never heard of this vlanDRiP attempts to resolve any conflicts when it hears of a new VLAN. The value action = 1 means to notify the local platform of change in state:
DRIP : resolve remote for vlan 20 in FastEthernet0/0/0DRIP : resolve remote - action = 1The local platform is notified of change in state:
DRIP Change notification active vlan 20Another new VLAN ID was received in the packet:
DRIP : resolve remote for vlan 1003 in FastEthernet0/0/0No action is required:
DRIP : resolve remote - action = 0Thirty seconds have expired, and DRiP sends its local database entries to all its trunk ports:
DRIP : local timer expiredDRIP : transmit on 0000.0c50.1900, length = 24612B92C0: 01000C00 00000000 0C501900 0000AAAA .........P....**612B92D0: 0300000C 00020000 00000100 0CCCCCCC .............LLL612B92E0: 00000C50 19000020 AAAA0300 000C0102 ...P... **......612B92F0: 01FF0114 00000003 00000002 00000C50 ...............P612B9300: 19000001 04C00064 04 .....@.d.debug drip packet
Use the debug drip packet privileged EXEC command to display debug messages for DRiP packets. Use the no form of this command to disable debugging output.
[no] debug drip packet
Default
Debugging is not enabled for DRIP packets.
Usage Guidelines
Before you use this command, you can optionally use the clear drip command first. As a result the DRiP counters are reset to 0. If the drip counters begin to increment, the router is receiving packets.
Sample Displays
The following is sample output from the debug drip packet command.
The following type of output is displayed when a packet is entering the router and you use the show debug command:
039E5FC0: 0100 0CCCCCCC 00E0A39B 3FFB0028 ...LLL.`#.?{.(039E5FD0: AAAA0300 000C0102 01FF0314 0000A5F6 **............%v039E5FE0: 00008805 00E0A39B 3C000000 04C00028 .....`#.<....@.(039E5FF0: 04C00032 044003EB 0F .@.2.@.k.039FBD20: 01000C00 00000010 ........The following type of output is displayed when a packet is transmitted by the router:
039FBD30: A6AEB450 0000AAAA 0300000C 00020000 &.4P..**........039FBD40: 00000100 0CCCCCCC 0010A6AE B4500020 .....LLL..&.4P.039FBD50: AAAA0300 000C0102 01FF0114 00000003 **..............039FBD60: 00000002 0010A6AE B4500001 04C00064 ......&.4P...@.d039FBD70: 04 .Related Commands
debug drip event
encapsulation tri-isl
debug dspu activation
Use the debug dspu activation EXEC command to display information on downstream physical unit (DSPU) activation. The no form of this command disables debugging output.
[no] debug dspu activation [name]
Syntax Description
Usage Guidelines
The debug dspu activation command displays all DSPU activation traffic. To restrict the output to a specific host or physical unit (PU), include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu activation command.
Sample Display
The following is sample output from the debug dspu activation command. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.
Router# debug dspu activationDSPU: LS HOST3745 connectedDSPU: PU HOST3745 activatedDSPU: LU HOST3745-2 activatedDSPU: LU HOST3745-3 activated...DSPU: LU HOST3745-253 activatedDSPU: LU HOST3745-254 activatedDSPU: LU HOST3745-2 deactivatedDSPU: LU HOST3745-3 deactivated...DSPU: LU HOST3745-253 deactivatedDSPU: LU HOST3745-254 deactivatedDSPU: LS HOST3745 disconnectedDSPU: PU HOST3745 deactivateddescribes significant fields in the output.
Related Commands
debug dspu packet
debug dspu state
debug dspu tracedebug dspu packet
Use the debug dspu packet EXEC command to display information on downstream physical unit (DSPU) packet. The no form of this command disables debugging output.
[no] debug dspu packet [name]
Syntax Description
Usage Guidelines
The debug dspu packet command displays all DSPU packet data flowing through the router. To restrict the output to a specific host or PU, include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu packet command.
Sample Display
The following is sample output from the debug dspu packet command:
Router# debug dspu packetDSPU: Rx: PU HOST3745 data length 12 data:2D0003002BE16B80 000D0201DSPU: Tx: PU HOST3745 data length 25 data:2D0000032BE1EB80 000D020100850000 000C060000010000 00DSPU: Rx: PU HOST3745 data length 12 data:2D0004002BE26B80 000D0201DSPU: Tx: PU HOST3745 data length 25 data:2D0000042BE2EB80 000D020100850000 000C060000010000 00describes significant fields in the output.
Related Commands
debug drip event
debug dspu state
debug dspu tracedebug dspu state
Use the debug dspu state EXEC command to display information on downstream physical unit (DSPU) finite state machine (FSM) state changes. The no form of this command disables debugging output.
[no] debug dspu state [name]
Syntax Description
Usage Guidelines
Use the debug dspu state command to display only the FSM state changes. To see all FSM activity, use the debug dspu trace command. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu state command.
Sample Display
The following is sample output from the debug dspu state command. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.
Router# debug dspu stateDSPU: LS HOST3745: input=StartLs, Reset -> PendConOutDSPU: LS HOST3745: input=ReqOpn.Cnf, PendConOut -> XidDSPU: LS HOST3745: input=Connect.Ind, Xid -> ConnInDSPU: LS HOST3745: input=Connected.Ind, ConnIn -> ConnectedDSPU: PU HOST3745: input=Actpu, Reset -> ActiveDSPU: LU HOST3745-2: input=uActlu, Reset -> upLuActiveDSPU: LU HOST3745-3: input=uActlu, Reset -> upLuActive...DSPU: LU HOST3745-253: input=uActlu, Reset -> upLuActiveDSPU: LU HOST3745-254: input=uActlu, Reset -> upLuActiveDSPU: LS HOST3745: input=PuStopped, Connected -> PendDiscDSPU: LS HOST3745: input=Disc.Cnf, PendDisc -> PendCloseDSPU: LS HOST3745: input=Close.Cnf, PendClose -> ResetDSPU: PU HOST3745: input=T2ResetPu, Active -> ResetDSPU: LU HOST3745-2: input=uStopLu, upLuActive -> ResetDSPU: LU HOST3745-3: input=uStopLu, upLuActive -> Reset...DSPU: LU HOST3745-253: input=uStopLu, upLuActive -> ResetDSPU: LU HOST3745-254: input=uStopLu, upLuActive -> Resetdescribes significant fields in the output.
Related Commands
debug drip event
debug dspu packet
debug dspu tracedebug dspu trace
Use the debug dspu trace EXEC command to display information on downstream physical unit (DSPU) trace activity, which includes all finite state machine (FSM) activity. The no form of this command disables debugging output.
[no] debug dspu trace [name]
Syntax Description
Usage Guidelines
Use the debug dspu trace command to display all FSM state changes. To see FSM state changes only, use the debug dspu state command. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu trace command.
Sample Display
The following is sample output from the debug dspu trace command:
Router# debug dspu traceDSPU: LS HOST3745 input = 0 ->(1,a1)DSPU: LS HOST3745 input = 5 ->(5,a6)DSPU: LS HOST3745 input = 7 ->(5,a9)DSPU: LS HOST3745 input = 9 ->(5,a28)DSPU: LU HOST3745-2 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-3 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-252 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-253 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-254 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)describes significant fields in the output.
Related Commands
debug drip event
debug dspu packet
debug dspu statedebug eigrp fsm
Use the debug eigrp fsm EXEC command to display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) feasible successor metrics (FSM). The no form of this command disables debugging output.
[no] debug eigrp fsm
Usage Guidelines
This command helps you observe EIGRP feasible successor activity and to determine whether route updates are being installed and deleted by the routing process.
Sample Display
The following is sample output from the debug eigrp fsm command:
Router# debug eigrp fsmDUAL: dual_rcvupdate(): 172.25.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0DUAL: Find FS for dest 172.25.166.0 255.255.255.0. FD is 4294967295, RD is 4294967295 foundDUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/4294967295DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0In the first line, DUAL stands for Diffusing Update ALgorithm. It is the basic mechanism within EIGRP that makes the routing decisions.The next three fields are the Internet address and mask of the destination network and the address through which the update was received. The metric field shows the metric stored in the routing table and the metric advertised by the neighbor sending the information. "Metric... inaccessible" usually means that the neighbor router no longer has a route to the destination, or the destination is in hold-down.
In the following output, EIGRP is attempting to find a feasible successor for the destination. Feasible successors are part of the DUAL loop avoidance methods. The FD field contains more loop avoidance state information. The RD field is the reported distance, which is the metric used in update, query or reply packets.
The indented line with the "not found" message means a feasible successor (FS) was not found for 192.168.4.0 and EIGRP must start a diffusing computation. This means it begins to actively probe (sends query packets about destination 192.168.4.0) the network looking for alternate paths to 192.164.4.0.
DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295The following output indicates the route DUAL successfully installed into the routing table.
DUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0The following output shows that no routes were discovered to the destination and the route information is being removed from the topology table:
DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0debug eigrp packet
Use the debug eigrp packet EXEC command to display general debugging information. The no form of this command disables debugging output.
[no] debug eigrp packet
Usage Guidelines
If a communication session is closing when it should not be, an end-to-end connection problem can be the cause. The debug eigrp packet command is useful for analyzing the messages traveling between the local and remote hosts.
Sample Display
The following is sample output from the debug eigrp packet command:
Router# debug eigrp packetEIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x1, Seq 1, Ack 0EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x0, Seq 2, Ack 0The output shows transmission and receipt of EIGRP packets. These packet types may be HELLO, UPDATE, REQUEST, QUERY, or REPLY packets. The sequence and acknowledgment numbers used by the EIGRP reliable transport algorithm are shown in the output. Where applicable, the network layer address of the neighboring router is also included.
describes significant fields in the output.