Cisco IOS Debug Command Reference, Release 12.1 - Debug Commands (debug dlsw - debug ip dhcp server) [Cisco IOS Software Releases 12.1 Mainline]

Table Of Contents

debug dlsw

debug drip event

debug drip packet

debug dsc clock

debug dsip

debug dspu activation

debug dspu packet

debug dspu state

debug dspu trace

debug dss ipx event

debug eigrp fsm

debug eigrp neighbor

debug eigrp packet

debug eigrp transmit

debug fddi smt-packets

debug frame-relay

debug frame-relay callcontrol

debug frame-relay end-to-end keepalive

debug frame-relay events

debug frame-relay fragment

debug frame-relay foresight

debug frame-relay informationelements

debug frame-relay ip tcp header-compression

debug frame-relay lapf

debug frame-relay lmi

debug frame-relay networklayerinterface

debug frame-relay packet

debug frame-relay ppp

debug fras error

debug fras-host activation

debug fras-host error

debug fras-host packet

debug fras-host snmp

debug fras message

debug fras state

debug ftpserver

debug h225

debug h225 asn1

debug h225 events

debug h245 asn1

debug h245 events

debug ima

debug ip auth-proxy

debug ip bgp

debug ip casa affinities

debug ip casa packets

debug ip casa wildcards

debug ip cef

debug ip cef accounting non-recursive

debug ip dhcp server

debug dlsw

Use the debug dlsw privileged EXEC command to enable debugging of DLSw+. The no form of this command disables debugging output.

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]
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

border-peers

(Optional) Enables debugging output for border peer events.

interface interface

(Optional) Specifies a remote peer to debug by a direct interface.

ip address ip-address

(Optional) Specifies a remote peer to debug by its IP address.

core

(Optional) Enables debugging output for DLSw core events.

flow-control

(Optional) Enables debugging output for congestion in the WAN or at the remote end station.

messages

(Optional) Enables debugging output of core messages—specific packets received by DLSw either from one of its peers or from a local medium via the Cisco link services interface.

state

(Optional) Enables debugging output for state changes on the circuit.

xid

(Optional) Enables debugging output for the exchange identification-state machine.

circuit-number

(Optional) Specifies the circuit for which you want core debugging output to reduce the of output.

local-circuit circuit-number

(Optional) Enables debugging output for circuits performing local conversion. Local conversion occurs when both the input and output data-link connections are on the same local peer and no remote peer exists.

peers

(Optional) Enables debugging output for peer events.

fast-errors

(Optional) Debugs errors for fast-switched packets.

fast-paks

(Optional) Debugs fast-switched packets.

fst-seq

(Optional) Debugs FST sequence numbers on fast switched packets.

udp

(Optional) Debugs UDP packets.

reachability

(Optional) Enables debugging output for reachability events (explorer traffic). If no options are specified, event-level information is displayed for all protocols.

error | verbose

(Optional) Specifies how much reachability information you want displayed. The verbose keyword displays everything, including errors and events. The error keyword displays error information only. If no option is specified, event-level information is displayed.

sna | netbios

(Optional) Specifies that reachability information be displayed for only SNA or NetBIOS protocols. If no option is specified, information for all protocols is displayed.

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.

Examples

The following sections show and explain some of the typical DLSw debug messages you might see when using the debug dlsw command.

The following example enables UDP packet debugging for a specific remote peer:
Router# debug dlsw peer ip-address 1.1.1.6 udp
The 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.5
The 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:DISCONN
DLSw: dtp_action_a() attempting to connect peer 10.3.8.7(2065)
DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:DISCONN->WAIT_WR
DLSw: Async Open Callback 10.3.8.7(2065) -> 11002
DLSw: 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->CONNECT
The 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->CONNECT
The 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->CONNECT
The 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->CONNECT
The following message is from a router that initiated an LLC2 connection:
DLSw-LLC2: Sending enable port ; port no : 0
           PEER-DISP Sent : CLSI Msg : ENABLE.Req   dlen: 20 
DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20 
DLSw-LLC2 : Sending activate sap for Serial1 - port_id = 887C3C
            port_type = 7 dgra(UsapID) = 952458
            PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req   dlen: 60 
DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60 
DLSw Got ActSapcnf back for Serial1 - port_id = 8978204, port_type = 7, psap_id = 0
DLSw: START-LLC2PFSM (peer on interface Serial1): event:ADMIN-OPEN CONNECTION 
state:DISCONN
DLSw: dllc2p_action_a() attempting to connect peer on interface Serial1
 PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req   dlen: 106 
DLSw: END-LLC2PFSM (peer on interface Serial1): state:DISCONN->ROS_SENT
DLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106 
DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-REQOPNSTN.CNF state:ROS_SENT
DLSw: dllc2p_action_c()
 PEER-DISP Sent : CLSI Msg : CONNECT.Req   dlen: 16 
DLSw: END-LLC2PFSM (peer on interface Serial1): state:ROS_SENT->CON_PEND
DLSw: Peer Received : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 28 
DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-CONNECT.CNF state:CON_PEND
DLSw: dllc2p_action_e() send capabilities to peer on interface Serial1
 PEER-DISP Sent : CLSI Msg : SIGNAL_STN.Req   dlen: 8 
 PEER-DISP Sent : CLSI Msg : DATA.Req   dlen: 418 
DLSw: CapExId Msg sent to peer on interface Serial1
DLSw: END-LLC2PFSM (peer on interface Serial1): state:CON_PEND->WAIT_CAP
DLSw: Peer Received : CLSI Msg : DATA.Ind   dlen: 418 
DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAP
DLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1
DLSw: Recv CapExId Msg from peer on interface Serial1
 PEER-DISP Sent : CLSI Msg : DATA.Req   dlen: 96 
DLSw: Pos CapExResp sent to peer on interface Serial1
DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAP
DLSw: Peer Received : CLSI Msg : DATA.Ind   dlen: 96 
DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAP
DLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1
DLSw: Recv CapExPosRsp Msg from peer on interface Serial1
DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAP
DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP
DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP EXCHANGED state:WAIT_CAP
DLSw: dllc2p_action_l() cap xchged for peer on interface Serial1
DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->CONNECT
The following message is from a router that received an LLC2 connection:
DLSw-LLC2: Sending enable port ; port no : 0
 PEER-DISP Sent : CLSI Msg : ENABLE.Req   dlen: 20 
DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20 
DLSw-LLC2 : Sending activate sap for Serial0 - port_id = 887C3C
 port_type = 7 dgra(UsapID) = 93AB34
 PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req   dlen: 60 
DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60 
DLSw Got ActSapcnf back for Serial0 - port_id = 8944700, port_type = 7, psap_id = 0
DLSw: Peer Received : CLSI Msg : CONECT_STN.Ind   dlen: 39 
DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECT_STN.IND state:DISCONN
DLSw: dllc2p_action_s() conn_stn for peer on interface Serial0
 PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req   dlen: 106 
DLSw: END-LLC2PFSM (peer on interface Serial0): state:DISCONN->CONS_PEND
DLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106 
DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-REQOPNSTN.CNF state:CONS_PEND
DLSw: dllc2p_action_h() send capabilities to peer on interface Serial0
 PEER-DISP Sent : CLSI Msg : CONNECT.Rsp   dlen: 20 
 PEER-DISP Sent : CLSI Msg : DATA.Req   dlen: 418 
DLSw: CapExId Msg sent to peer on interface Serial0
DLSw: END-LLC2PFSM (peer on interface Serial0): state:CONS_PEND->WAIT_CAP
DLSw: Peer Received : CLSI Msg : CONNECTED.Ind   dlen: 8 
DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECTED.IND state:WAIT_CAP
DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAP
DLSw: Peer Received : CLSI Msg : DATA.Ind   dlen: 418 
DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAP
DLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0
DLSw: Recv CapExId Msg from peer on interface Serial0
 PEER-DISP Sent : CLSI Msg : DATA.Req   dlen: 96 
DLSw: Pos CapExResp sent to peer on interface Serial0
DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAP
DLSw: Peer Received : CLSI Msg : DATA.Ind   dlen: 96 
DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAP
DLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0
DLSw: Recv CapExPosRsp Msg from peer on interface Serial0
DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAP
DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP
DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP EXCHANGED state:WAIT_CAP
DLSw: dllc2p_action_l() cap xchged for peer on interface Serial0
DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->CONNECT
The 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 Serial0
0:03:24: DLSw: action_d(): for peer on interface Serial0
0:03:24: DLSW: DIRECT aborting connection for peer on interface Serial0
0:03:24: DLSw: peer on interface Serial0, old state CONNECT, new state DISCONN
The 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: 861232504
23: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: 861292536
The 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_RD
23:14:52: DLSw: dlsw_tcpd_fini() closing connection for peer 172.20.100.1
23: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 DISCONN
The 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_RD
23:16:37: DLSW: passive open 172.20.100.1(17762) -> 2065
23: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_EXG
23:16:37: DLSw: peer 172.20.100.1(2065) conn_start_time set to 861397784
23: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 CONNECT
23:16:37: DLSw: dlsw_tcpd_fini() closing write pipe for peer 172.20.100.1
23: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:34
DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:4 rs:4 i:34
Sample 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.

•If a router has a fresh entry in the cache for a certain resource, it answers a locate request for that resource without verifying that it is still available. A locate request is typically a TEST frame for MAC addresses or a FIND_NAME_QUERY for NetBIOS.

•If a router has a stale entry in the cache for a certain resource, it verifies that the entry is still valid before answering a locate request for the resource by sending a frame to the resource's last known location and waits for a resource. If the entry is a REMOTE entry, the router sends a CUR_ex frame to the remote peer to verify. If the entry is a LOCAL entry, it sends either a TEST frame or a NetBIOS FIND_NAME_QUERY on the appropriate local port.

•By default, all reachability cache entries remain fresh for 4 minutes after they are learned. For MAC addresses, you can change this time with the dlsw timer sna-verify-interval command. For NetBIOS names, you can change this with the dlsw timer netbios-verify-interval command.

•By default, all reachability cache entries age out of the cache 16 minutes after they are learned. For MAC addresses, you can change this time with the dlsw timer sna-cache-timeout command. For NetBIOS names, you can change the time with the dlsw timer netbios-cache-timeout command.

Table 40 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:0
Table 40 Debug Output Command Descriptions

Field

Description

decr r

Decrement received count.

s

This DLSW router's granted units for the circuit.

so

0=This DLSW router does not owe a flow control acknowledgment.

1=This router owes a flow control acknowledgment.

r

Partner's number of granted units for the circuit.

ro

Indicates whether the partner owes flow control acknowledgment.

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: 1086
The 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: 4
The following messages show that the reachability cache is cleared:
Router# clear dlsw rea
23:44:11: CSM: Clearing CSM cache
23:44:11: CSM: delete local mac cache for port 0
23:44:11: CSM: delete local name cache for port 0
23:44:11: CSM: delete remote mac cache for peer 0
23:44:11: CSM: delete remote name cash dlsw rea
The 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 5EFBB4
23:45:11: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:11: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB4
23:45:11: CSM: update local cache for name MARIAN         , port 5EFBB4
23:45:11: CSM: Received CLS_UDATA_STN from Core
23:45:11: CSM: Received netbios frame type A
23:45:11: CSM: Processing Name Query
23:45:11: CSM: Netbios Name Query: ws_status = 6
23:45:11: CSM: Write to peer 0 ok.
23:45:11: CSM: Freeing clsi message
23:45:11: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB4
23:45:11: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:11: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB4
23:45:11: CSM: update local cache for name MARIAN         , port 658AB4
23:45:11: CSM: Received CLS_UDATA_STN from Core
23:45:11: CSM: Received netbios frame type A
23:45:11: CSM: Processing Name Query
23:45:11: CSM: Netbios Name Query: ws_status = 5
23:45:11: CSM: DLXNR_PEND match found.... drop name query
23:45:11: CSM: Freeing clsi message
23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB4
23:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB4
23:45:12: CSM: update local cache for name MARIAN         , port 5EFBB4
23:45:12: CSM: Received CLS_UDATA_STN from Core
23:45:12: CSM: Received netbios frame type A
23:45:12: CSM: Processing Name Query
23:45:12: CSM: Netbios Name Query: ws_status = 5
23:45:12: CSM: DLXNR_PEND match found.... drop name query
23:45:12: CSM: Freeing clsi message
23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB4
23:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB4
23:45:12: CSM: update local cache for name MARIAN         , port 658AB4
23:45:12: CSM: Received CLS_UDATA_STN from Core
23:45:12: CSM: Received netbios frame type A
23:45:12: CSM: Processing Name Query
23:45:12: CSM: Netbios Name Query: ws_status = 5
23:45:12: CSM: DLXNR_PEND match found.... drop name query
23:45:12: CSM: Freeing clsi message
23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB4
23:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB4
23:45:12: CSM: update local cache for name MARIAN         , port 5EFBB4
23:45:12: CSM: Received CLS_UDATA_STN from Core
23:45:12: CSM: Received netbios frame type A
23:45:12: CSM: Processing Name Query
23:45:12: CSM: Netbios Name Query: ws_status = 5
23:45:12: CSM: DLXNR_PEND match found.... drop name query
23:45:12: CSM: Freeing clsi message
23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB4
23:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB4
23:45:12: CSM: update local cache for name MARIAN         , port 658AB4
23:45:12: CSM: Received CLS_UDATA_STN from Core
23:45:12: CSM: Received netbios frame type A
23:45:12: CSM: Processing Name Query
23:45:12: CSM: Netbios Name Query: ws_status = 5
23:45:12: CSM: DLXNR_PEND match found.... drop name query
23:45:12: CSM: Freeing clsi message
23:45:18: CSM: Deleting Reachability cache
23:45:18: CSM: Deleting DLX NR pending record....
23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB4
23:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB4
23:45:38: CSM: update local cache for name MARIAN         , port 5EFBB4
23:45:38: CSM: Received CLS_UDATA_STN from Core
23:45:38: CSM: Received netbios frame type 8
23:45:38: CSM: Write to peer 0 ok.
23:45:38: CSM: Freeing clsi message
23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB4
23:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB4
23:45:38: CSM: update local cache for name MARIAN         , port 658AB4
23:45:38: CSM: Received CLS_UDATA_STN from Core
23:45:38: CSM: Received netbios frame type 8
23:45:38: CSM: Write to peer 0 ok.
23:45:38: CSM: Freeing clsi message
The following messages show that Marian is added to the network:
23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB4
23:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB4
23:45:38: CSM: update local cache for name MARIAN         , port 5EFBB4
23:45:38: CSM: Received CLS_UDATA_STN from Core
23:45:38: CSM: Received netbios frame type 8
23:45:38: CSM: Write to peer 0 ok.
23:45:38: CSM: Freeing clsi message
23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB4
23:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter
23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB4
23:45:38: CSM: update local cache for name MARIAN         , port 658AB4
23:45:38: CSM: Received CLS_UDATA_STN from Core
23:45:38: CSM: Received netbios frame type 8
23:45:38: CSM: Write to peer 0 ok.
23:45:38: CSM: Freeing clsi message
In 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 658AB4
0:07:44: CSM: 0004.f545.24e6 passes local mac excl. filter
0:07:44: CSM: update local cache for mac 0004.f545.24e6, port 658AB4
0:07:44: CSM: update local cache for name GINGER         , port 658AB4
0:07:44: CSM: Received CLS_UDATA_STN from Core
0:07:44: CSM: Received netbios frame type 8
0: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 reachability
DLSw MAC address reachability cache list
Mac Addr        status     Loc.    peer/port            rif
0004.f545.24e6  FOUND      LOCAL   P007-S000    --no rif--
0800.5a30.7a9b  FOUND      LOCAL   P000-S000    06C0.0621.7D00
                                   P007-S000    F0F8.0006.A6FC.005F.F100.0000.0000.0000
DLSw NetBIOS Name reachability cache list
NetBIOS Name    status     Loc.    peer/port            rif
GINGER          FOUND      LOCAL   P007-S000     --no rif--
MARIAN          FOUND      LOCAL   P000-S000     06C0.0621.7D00
                                   P007-S000     --no rif--
debug drip event

Use the debug drip event privileged EXEC command to display debug messages for Duplicate Ring Protocol (DRiP) events. Use the no form of this command to disable debugging output.

debug drip event
no debug drip event
Syntax Description

This command has no arguments or keywords.

Defaults

Debugging is disabled for DRiP events.

Command History

Release

Modification

11.3(4)T

This command was introduced.

Usage Guidelines

When a TrBRF interface is configured on the RSM, 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.

Examples

Following examples show output for the debug drip event command.

DRiP gets a packet from the network:
612B92C0: 01000C00 00000000 0C501900 0000AAAA  .........P....**
612B92D0: 0300000C 00020000 00000100 0CCCCCCC  .............LLL
612B92E0: 00000C50 19000020 AAAA0300 000C0102  ...P... **......
612B92F0: 01010114 00000002 00000002 00000C50  ...............P
612B9300: 19000001 04C00064 04                 .....@.d.       
DRiP gets a packet from the network:
Recvd. pak
DRiP recognizes that the VLAN ID it is getting is a new one from the network:
6116C840:                       0100 0CCCCCCC            ...LLL
6116C850: 00102F72 CBFB0024 AAAA0300 000C0102  ../rK{.$**......
6116C860: 01FF0214 0002E254 00015003 00102F72  ......bT..P.../r
6116C870: C8000010 04C00014 044003EB 14        H....@...@.k. 
DRIP : remote update - Never heard of this vlan
DRiP 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 VLAN0
DRIP : resolve remote - action = 1
The local platform is notified of change in state:
DRIP Change notification active vlan 20
Another new VLAN ID was received in the packet:
DRIP : resolve remote for vlan 1003 in Vlan0
No action is required:
DRIP : resolve remote - action = 0
Thirty seconds have expired, and DRiP sends its local database entries to all its trunk ports:
DRIP : local timer expired
DRIP : transmit on 0000.0c50.1900, length = 24
612B92C0: 01000C00 00000000 0C501900 0000AAAA  .........P....**
612B92D0: 0300000C 00020000 00000100 0CCCCCCC  .............LLL
612B92E0: 00000C50 19000020 AAAA0300 000C0102  ...P... **......
612B92F0: 01FF0114 00000003 00000002 00000C50  ...............P
612B9300: 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.

debug drip packet
no debug drip packet
Syntax Description

This command has no arguments or keywords.

Defaults

Debugging is not enabled for DRiP packets.

Command History

Release

Modification

11.3(4)T

This command was introduced.

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.

Examples

Following is sample output for 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  **............%v
039E5FE0: 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...@.d
039FBD70: 04                                   . 
Related Commands

Command

Description

debug drip event

Displays debug messages for DRIP events.

debug dsc clock

Use the debug dsc clock privileged EXEC command to display output for the time-division multiplexing (TDM) clock switching events on the dial shelf controller. To turn off output, use the no form of this command.

debug dsc clock
no debug dsc clock
Syntax Description

This command was no arguments or keywords.

Command History

Release

Modification

11.3(2)AA

This command was introduced.

Usage Guidelines

The debug dsc clock command displays TDM clock switching events on the dial shelf controller. The information displayed includes the following:

•Clock configuration messages received from trunks via the bus

•Dial shelf controller clock configuration messages from the router shelf over the dial shelf interface link

•Clock switchover algorithm events

Examples

The following example shows that the debug dsc clock command has been enabled, that trunk messages are received, and that the configuration message has been received:
AS5800# debug dsc clock
Dial Shelf Controller Clock debugging is on
AS5800#
00:02:55: Clock Addition msg of len 12 priority 8 from slot 1 port 1 on line 0
00:02:55: Trunk 1 has reloaded
Related Commands

Command

Description

show dsc clock

Displays information about the dial shelf controller clock.

debug dsip

Use the debug dsip privileged EXEC command to display output for distributed system interconnect protocol (DSIP) used between the router shelf and the dial shelf. To disable the output, use the no form of this command.

debug dsip {all | api | boot | console | trace | transport}
no debug dsip {all | api | boot | console | trace | transport}
Syntax Description

all

View all DSIP messages.

api

View DSIP client interface (API) messages.

boot

View DSIP booting messages that are generated when a download of the feature board image is occurring properly.

console

View DSIP console operation.

trace

Enable logging of header information concerning DSIP packets entering the system in a trace buffer.

transport

Debug the DSIP transport layer, the module that interacts with the underlying physical media driver.

Command History

Release

Modification

11.3(2)AA

This command was introduced.

Usage Guidelines

The debug dsip command is used to display messages for DSIP between the router shelf and the dial shelf. Using this command, you can display booting messages generated when the download of an image occurs, view console operation, trace logging of MAC header information, and view DSIP transport layer information as modules interact with the underlying physical media driver. This command can be applied to a single modem or a group of modems.

Once the debug dsip trace command is enabled, you can read the information captured in the trace buffer using the show dsip tracing command.

Examples

The following example shows the available debug dsip command options:
AS5800# debug dsip ?
  all        All DSIP debugging messages
  api        DSIP API debugging
  boot       DSIP booting
  console    DSIP console
  trace      DSIP tracing
  transport  DSIP transport
The following example indicates the debug dsip trace command logs MAC headers of the various classes of DSIP packets. View the logged information using the show dsip tracing command.
AS5800# debug dsip trace
NIP tracing debugging is on
AS5800# show dsip tracing
NIP Control Packet Trace
------------------------------------------------------------
Dest:00e0.b093.2238 Src:0007.4c72.0058 Type:200B SrcShelf:1 SrcSlot:11
MsgType:0 MsgLen:82 Timestamp: 00:49:14
------------------------------------------------------------
Dest:00e0.b093.2238 Src:0007.4c72.0028 Type:200B SrcShelf:1 SrcSlot:5
MsgType:0 MsgLen:82 Timestamp: 00:49:14
------------------------------------------------------------
Related Commands

Command

Description

debug modem dsip

Displays output for modem control messages that are received or sent to the router.

debug dspu activation

Use the debug dspu activation privileged EXEC command to display information on downstream physical unit (DSPU) activation. The no form of this command disables debugging output.

debug dspu activation [name]
no debug dspu activation [name]
Syntax Description

name

(Optional) Host or PU name designation.

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.

Examples

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 activation 
DSPU: LS HOST3745 connected
DSPU: PU HOST3745 activated
DSPU: LU HOST3745-2 activated
DSPU: LU HOST3745-3 activated
...
DSPU: LU HOST3745-253 activated
DSPU: LU HOST3745-254 activated
DSPU: LU HOST3745-2 deactivated
DSPU: LU HOST3745-3 deactivated
...
DSPU: LU HOST3745-253 deactivated
DSPU: LU HOST3745-254 deactivated
DSPU: LS HOST3745 disconnected
DSPU: PU HOST3745 deactivated
Table 41 describes significant fields in the output.

Table 41 debug dspu activation Command Field Descriptions

Field

Description

DSPU

Downstream PU debug message.

LS

Link station (LS) event triggered the message.

PU

PU event triggered the message.

LU

LU event triggered the message.

HOST3745

Host name or PU name.

HOST3745-253

Host name or PU name and the LU address, separated by a dash.

connected

activated

disconnected

deactivated

Event that occurred to trigger the message.

Related Commands

Command

Description

debug dspu packet

Displays information on DSPU packet.

debug dspu state

Displays information on DSPU FSM state changes.

debug dspu trace

Displays information on DSPU trace activity.

debug dspu packet

Use the debug dspu packet privileged EXEC command to display information on downstream physical unit (DSPU) packet. The no form of this command disables debugging output.

debug dspu packet [name]
no debug dspu packet [name]
Syntax Description

name

(Optional) Host or PU name designation.

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.

Examples

The following is sample output from the debug dspu packet command:
Router# debug dspu packet 
DSPU: Rx: PU HOST3745 data length 12 data:
    2D0003002BE16B80 000D0201
DSPU: Tx: PU HOST3745 data length 25 data:
    2D0000032BE1EB80 000D020100850000 000C060000010000 00
DSPU: Rx: PU HOST3745 data length 12 data:
    2D0004002BE26B80 000D0201
DSPU: Tx: PU HOST3745 data length 25 data:
    2D0000042BE2EB80 000D020100850000 000C060000010000 00
Table 42 describes significant fields in the output.

Table 42 debug dspu packet Command Field Descriptions

Field

Description

DSPU: Rx:

Received frame (packet) from the remote PU to the router PU.

DSPU: Tx:

Transmitted frame (packet) from the router PU to the remote PU.

PU HOST3745

Host name or PU associated with the transmit or receive.

data length 12 data:

Number of bytes of data, followed by up to 128 bytes of displayed data.

Related Commands

Command

Description

debug drip event

Displays debug messages for DRiP packets.

debug dspu state

Displays information on DSPU FSM state changes.

debug dspu trace

Displays information on DSPU trace activity.

debug dspu state

Use the debug dspu state privileged 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.

debug dspu state [name]
no debug dspu state [name]
Syntax Description

name

(Optional) Host or PU name designation.

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.

Examples

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 state 
DSPU: LS HOST3745: input=StartLs, Reset -> PendConOut
DSPU: LS HOST3745: input=ReqOpn.Cnf, PendConOut -> Xid
DSPU: LS HOST3745: input=Connect.Ind, Xid -> ConnIn
DSPU: LS HOST3745: input=Connected.Ind, ConnIn -> Connected
DSPU: PU HOST3745: input=Actpu, Reset -> Active
DSPU: LU HOST3745-2: input=uActlu, Reset -> upLuActive
DSPU: LU HOST3745-3: input=uActlu, Reset -> upLuActive
... 
DSPU: LU HOST3745-253: input=uActlu, Reset -> upLuActive
DSPU: LU HOST3745-254: input=uActlu, Reset -> upLuActive
DSPU: LS HOST3745: input=PuStopped, Connected -> PendDisc
DSPU: LS HOST3745: input=Disc.Cnf, PendDisc -> PendClose
DSPU: LS HOST3745: input=Close.Cnf, PendClose -> Reset
DSPU: PU HOST3745: input=T2ResetPu, Active -> Reset
DSPU: LU HOST3745-2: input=uStopLu, upLuActive -> Reset
DSPU: LU HOST3745-3: input=uStopLu, upLuActive -> Reset
... 
DSPU: LU HOST3745-253: input=uStopLu, upLuActive -> Reset
DSPU: LU HOST3745-254: input=uStopLu, upLuActive -> Reset
Table 43 describes significant fields in the output.

Table 43 debug dspu state Coomand Field Descriptions

Field

Description

DSPU

Downstream PU debug message.

LS

Link station (LS) event triggered the message.

PU

PU event triggered the message.

LU

LU event triggered the message.

HOST3745-253

Host name or PU name and LU address.

input=input,

Input received by the FSM.

previous-state, -> current-state

Previous state and current new state as seen by the FSM.

Related Commands

Command

Description

debug drip event

Displays debug messages for DRiP packets.

debug drip packet

Displays information on DSPU packet.

debug dspu trace

Displays information on DSPU trace activity.

debug dspu trace

Use the debug dspu trace privileged 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.

debug dspu trace [name]
no debug dspu trace [name]
Syntax Description

<