|
|
Use the debug lane client EXEC command to display information about a LAN Emulation Client (LEC). The no form of this command disables debugging output.
[no] debug lane client {all | le-arp | packet | signaling | state | topology} [interface interface]
all | Displays all debug information related to the LEC. |
le-arp | Displays debug information related to the LANE ARP table. |
packet | Displays debug information about each packet. |
signaling | Displays debug information related to client SVCs. |
state | Displays debug information when the state changes. |
topology | Displays debug information related to the topology of the emulated LAN. |
interface interface | (Optional) Limits the debugging output to messages that relate to a particular interface or subinterface. If you enter this command multiple times with different interfaces, the last interface entered will be the one used to filter the messages. |
The debug lane client all command can generate a large amount of output. Use a limiting keyword or specify a subinterface to decrease the amount of output and focus on the information you need.
The following is sample output from the debug lane client packet and debug lane client state commands for an LEC joining an emulated LAN (ELAN) called elan1:
Router# debug lane client packet
Router# debug lane client state
The LEC listens for signaling calls to its ATM address (Initial State):
LEC ATM2/0.1: sending LISTEN LEC ATM2/0.1: listen on 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: received LISTEN
The LEC calls the LAN Emulation Configuration Server (LECS) and attempts to set up the Configure Direct VC (LECS Connect Phase):
LEC ATM2/0.1: sending SETUP LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B43.00 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the LECS. The Configure Direct VC is established:
LEC ATM2/0.1: received CONNECT LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: vcd 148
The LEC sends a CONFIG REQUEST to the LECS on the Configure Direct VC (Configuration Phase):
LEC ATM2/0.1: sending LANE_CONFIG_REQ on VCD 148 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC receives a CONFIG RESPONSE from the LECS on the Configure Direct VC:
LEC ATM2/0.1: received LANE_CONFIG_RSP on VCD 148 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC releases the Configure Direct VC:
LEC ATM2/0.1: sending RELEASE LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: cause code 31
The LEC receives a RELEASE_COMPLETE from the LECS:
LEC ATM2/0.1: received RELEASE_COMPLETE LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: cause code 16
The LEC calls the LAN Emulation Server (LES) and attempts to set up the Control Direct VC (Join/Registration Phase):
LEC ATM2/0.1: sending SETUP LEC ATM2/0.1: callid 0x61167110 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B41.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the LES. The Control Direct VC is established:
LEC ATM2/0.1: received CONNECT LEC ATM2/0.1: callid 0x61167110 LEC ATM2/0.1: vcd 150
The LEC sends a JOIN REQUEST to the LES on the Control Direct VC:
LEC ATM2/0.1: sending LANE_JOIN_REQ on VCD 150 LEC ATM2/0.1: Status 0 LEC ATM2/0.1: LECID 0 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC receives a SETUP request from the LES to set up the Control Distribute VC:
LEC ATM2/0.1: received SETUP LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B41.01
The LEC responds to the LES call setup with a CONNECT:
LEC ATM2/0.1: sending CONNECT LEC ATM2/0.1: callid 0x6114D174 LEC ATM2/0.1: vcd 151
A CONNECT_ACK is received from the ATM switch. The Control Distribute VC is established:
LEC ATM2/0.1: received CONNECT_ACK
The LEC receives a JOIN response from the LES on the Control Direct VC:
LEC ATM2/0.1: received LANE_JOIN_RSP on VCD 150 LEC ATM2/0.1: Status 0 LEC ATM2/0.1: LECID 1 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: LAN Type 2 LEC ATM2/0.1: Frame size 2 LEC ATM2/0.1: LAN Name elan1 LEC ATM2/0.1: LAN Name size 5
The LEC sends an LE_ARP request to the LES to obtain the broadcast-and-unknown (BUS) ATM NSAP address (BUS Connect):
LEC ATM2/0.1: sending LANE_ARP_REQ on VCD 150 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: TARGET MAC address ffff.ffff.ffff LEC ATM2/0.1: TARGET ATM address 00.000000000000000000000000.000000000000.00
The LEC receives its own LE_ARP request via the LES over the Control Distribute VC:
LEC ATM2/0.1: received LANE_ARP_RSP on VCD 151 LEC ATM2/0.1: SRC MAC address 0000.0ca0.5b40 LEC ATM2/0.1: SRC ATM address 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: TARGET MAC address ffff.ffff.ffff LEC ATM2/0.1: TARGET ATM address 39.020304050607080910111213.00000CA05B42.01
The LEC calls the BUS and attempts to set up the Multicast Send VC:
LEC ATM2/0.1: sending SETUP LEC ATM2/0.1: callid 0x6114D354 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B42.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B40.01
The LEC receives a CONNECT response from the BUS. The Multicast Send VC is established:
LEC ATM2/0.1: received CONNECT LEC ATM2/0.1: callid 0x6114D354 LEC ATM2/0.1: vcd 153
The LEC receives a SETUP request from the BUS to set up the Multicast Forward VC:
LEC ATM2/0.1: received SETUP LEC ATM2/0.1: callid 0x610D4230 LEC ATM2/0.1: called party 39.020304050607080910111213.00000CA05B40.01 LEC ATM2/0.1: calling_party 39.020304050607080910111213.00000CA05B42.01
The LEC responds to the BUS call setup with a CONNECT:
LEC ATM2/0.1: sending CONNECT LEC ATM2/0.1: callid 0x610D4230 LEC ATM2/0.1: vcd 154
A CONNECT_ACK is received from the ATM switch. The Multicast Forward VC is established:
LEC ATM2/0.1: received CONNECT_ACK
The LEC moves into the OPERATIONAL state:
%LANE-5-UPDOWN: ATM2/0.1 elan elan1: LE Client changed state to up
The following output is the from show lane client command after the LEC joins the emulated LAN as shown in the debug lane client output:
Router# show lane client
LE Client ATM2/0.1 ELAN name: elan1 Admin: up State: operational Client ID: 1 LEC up for 1 minute 2 seconds Join Attempt: 1 HW Address: 0000.0ca0.5b40 Type: token ring Max Frame Size: 4544 Ring:1 Bridge:1 ELAN Segment ID: 2048 ATM Address: 39.020304050607080910111213.00000CA05B40.01 VCD rxFrames txFrames Type ATM Address 0 0 0 configure 39.020304050607080910111213.00000CA05B43.00 142 1 2 direct 39.020304050607080910111213.00000CA05B41.01 143 1 0 distribute 39.020304050607080910111213.00000CA05B41.01 145 0 0 send 39.020304050607080910111213.00000CA05B42.01 146 1 0 forward 39.020304050607080910111213.00000CA05B42.01
The following is sample output from the debug lane client all command when an interface with an LECS, an LES/BUS, and an LEC is shut down:
Router# debug lane client all
LEC ATM1/0.2: received RELEASE_COMPLETE LEC ATM1/0.2: callid 0x60E8B474 LEC ATM1/0.2: cause code 0 LEC ATM1/0.2: action A_PROCESS_REL_COMP LEC ATM1/0.2: action A_TEARDOWN_LEC LEC ATM1/0.2: sending RELEASE LEC ATM1/0.2: callid 0x60EB6160 LEC ATM1/0.2: cause code 31 LEC ATM1/0.2: sending RELEASE LEC ATM1/0.2: callid 0x60EB7548 LEC ATM1/0.2: cause code 31 LEC ATM1/0.2: sending RELEASE LEC ATM1/0.2: callid 0x60EB9E48 LEC ATM1/0.2: cause code 31 LEC ATM1/0.2: sending CANCEL LEC ATM1/0.2: ATM address 47.00918100000000613E5A2F01.006070174820.02 LEC ATM1/0.2: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.3: received RELEASE_COMPLETE LEC ATM1/0.3: callid 0x60E8D108 LEC ATM1/0.3: cause code 0 LEC ATM1/0.3: action A_PROCESS_REL_COMP LEC ATM1/0.3: action A_TEARDOWN_LEC LEC ATM1/0.3: sending RELEASE LEC ATM1/0.3: callid 0x60EB66D4 LEC ATM1/0.3: cause code 31 LEC ATM1/0.3: sending RELEASE LEC ATM1/0.3: callid 0x60EB7B8C LEC ATM1/0.3: cause code 31 LEC ATM1/0.3: sending RELEASE LEC ATM1/0.3: callid 0x60EBA3BC LEC ATM1/0.3: cause code 31 LEC ATM1/0.3: sending CANCEL LEC ATM1/0.3: ATM address 47.00918100000000613E5A2F01.006070174820.03 LEC ATM1/0.3: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.2: received RELEASE_COMPLETE LEC ATM1/0.2: callid 0x60EB7548 LEC ATM1/0.2: cause code 0 LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.3: received RELEASE_COMPLETE LEC ATM1/0.3: callid 0x60EB7B8C LEC ATM1/0.3: cause code 0 LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.1: received RELEASE_COMPLETE LEC ATM1/0.1: callid 0x60EBC458 LEC ATM1/0.1: cause code 0 LEC ATM1/0.1: action A_PROCESS_REL_COMP LEC ATM1/0.1: action A_TEARDOWN_LEC LEC ATM1/0.1: sending RELEASE LEC ATM1/0.1: callid 0x60EBD30C LEC ATM1/0.1: cause code 31 LEC ATM1/0.1: sending RELEASE LEC ATM1/0.1: callid 0x60EBDD28 LEC ATM1/0.1: cause code 31 LEC ATM1/0.1: sending RELEASE LEC ATM1/0.1: callid 0x60EBF174 LEC ATM1/0.1: cause code 31 LEC ATM1/0.1: sending CANCEL LEC ATM1/0.1: ATM address 47.00918100000000613E5A2F01.006070174820.01 LEC ATM1/0.1: state ACTIVE event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.1: received RELEASE_COMPLETE LEC ATM1/0.1: callid 0x60EBDD28 LEC ATM1/0.1: cause code 0 LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.2: received RELEASE_COMPLETE LEC ATM1/0.2: callid 0x60EB6160 LEC ATM1/0.2: cause code 0 LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.3: received RELEASE_COMPLETE LEC ATM1/0.3: callid 0x60EB66D4 LEC ATM1/0.3: cause code 0 LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.2: received RELEASE_COMPLETE LEC ATM1/0.2: callid 0x60EB9E48 LEC ATM1/0.2: cause code 0 LEC ATM1/0.2: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.2: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE LEC ATM1/0.3: received RELEASE_COMPLETE LEC ATM1/0.3: callid 0x60EBA3BC LEC ATM1/0.3: cause code 0 LEC ATM1/0.3: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.3: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE LEC ATM1/0.1: received RELEASE_COMPLETE LEC ATM1/0.1: callid 0x60EBD30C LEC ATM1/0.1: cause code 0 LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => TERMINATING LEC ATM1/0.1: received RELEASE_COMPLETE LEC ATM1/0.1: callid 0x60EBF174 LEC ATM1/0.1: cause code 0 LEC ATM1/0.1: action A_PROCESS_TERM_REL_COMP LEC ATM1/0.1: state TERMINATING event LEC_SIG_RELEASE_COMP => IDLE LEC ATM1/0.2: received CANCEL LEC ATM1/0.2: state IDLE event LEC_SIG_CANCEL => IDLE LEC ATM1/0.3: received CANCEL LEC ATM1/0.3: state IDLE event LEC_SIG_CANCEL => IDLE LEC ATM1/0.1: received CANCEL LEC ATM1/0.1: state IDLE event LEC_SIG_CANCEL => IDLE LEC ATM1/0.1: action A_SHUTDOWN_LEC LEC ATM1/0.1: sending CANCEL LEC ATM1/0.1: ATM address 47.00918100000000613E5A2F01.006070174820.01 LEC ATM1/0.1: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE LEC ATM1/0.2: action A_SHUTDOWN_LEC LEC ATM1/0.2: sending CANCEL LEC ATM1/0.2: ATM address 47.00918100000000613E5A2F01.006070174820.02 LEC ATM1/0.2: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE LEC ATM1/0.3: action A_SHUTDOWN_LEC LEC ATM1/0.3: sending CANCEL LEC ATM1/0.3: ATM address 47.00918100000000613E5A2F01.006070174820.03 LEC ATM1/0.3: state IDLE event LEC_LOCAL_DEACTIVATE => IDLE
Use the debug lane config EXEC command to display information about a LANE configuration server. The no form of this command disables debugging output.
[no] debug lane config {all | events | packets}
all | Display all debug messages related to the LANE configuration server. The output includes both the events and packets types of output. |
events | Display only messages related to significant LANE configuration server events. |
packets | Display information on each packet sent or received by the LANE configuration server. |
The debug lane config output is intended to be used primarily by a Cisco technical support representative.
The following is sample output from the debug lane config all command when an interface with an LECS, an LES/BUS, and an LEC is shut down:
Router# debug lane config all
LECS EVENT ATM1/0: processing interface down transition LECS EVENT ATM1/0: placed de-register address 0x60E8A824 (47.00918100000000613E5A2F01.006070174823.00) request with signalling LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ? LECS EVENT ATM1/0: placed de-register address 0x60EC4F28 (47.007900000000000000000000.00A03E000001.00) request with signalling LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ? LECS EVENT ATM1/0: placed de-register address 0x60EC5C08 (47.00918100000000613E5A2F01.006070174823.99) request with signalling LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ? LECS EVENT ATM1/0: tearing down all connexions LECS EVENT ATM1/0: elan 'xxx' LES 47.00918100000000613E5A2F01.006070174821.01 callId 0x60CE0F58 deliberately being disconnected LECS EVENT ATM1/0: sending RELEASE for call 0x60CE0F58 cause 31 LECS EVENT ATM1/0: elan 'yyy' LES 47.00918100000000613E5A2F01.006070174821.02 callId 0x60CE2104 deliberately being disconnected LECS EVENT ATM1/0: sending RELEASE for call 0x60CE2104 cause 31 LECS EVENT ATM1/0: elan 'zzz' LES 47.00918100000000613E5A2F01.006070174821.03 callId 0x60CE2DC8 deliberately being disconnected LECS EVENT ATM1/0: sending RELEASE for call 0x60CE2DC8 cause 31 LECS EVENT ATM1/0: All calls to/from LECSs are being released LECS EVENT ATM1/0: placed de-register address 0x60EC4F28 (47.007900000000000000000000.00A03E000001.00) request with signalling LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ? LECS EVENT ATM1/0: ATM_RELEASE_COMPLETE received: callId 0x60CE0F58 cause 0 LECS EVENT ATM1/0: call 0x60CE0F58 cleaned up LECS EVENT ATM1/0: ATM_RELEASE_COMPLETE received: callId 0x60CE2104 cause 0 LECS EVENT ATM1/0: call 0x60CE2104 cleaned up LECS EVENT ATM1/0: ATM_RELEASE_COMPLETE received: callId 0x60CE2DC8 cause 0 LECS EVENT ATM1/0: call 0x60CE2DC8 cleaned up LECS EVENT ATM1/0: UNKNOWN/UNSET: signalling DE-registered LECS EVENT: UNKNOWN/UNSET: signalling DE-registered LECS EVENT ATM1/0: UNKNOWN/UNSET: signalling DE-registered LECS EVENT ATM1/0: placed de-register address 0x60E8A824 (47.00918100000000613E5A2F01.006070174823.00) request with signalling LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ? LECS EVENT ATM1/0: placed de-register address 0x60EC5C08 (47.00918100000000613E5A2F01.006070174823.99) request with signalling LECS EVENT ATM1/0: ilmiDeRegisterAddress: sendSetRequestToILMI failure; interface down ? LECS EVENT ATM1/0: tearing down all connexions LECS EVENT ATM1/0: All calls to/from LECSs are being released LECS EVENT: config server 56 killed
Use the debug lane finder EXEC command to display information about the finder internal state machine. The no form of this command disables debugging output.
[no] debug lane finderThe debug lane finder output is intended to be used primarily by a Cisco technical support representative.
The following is sample output from the debug lane finder command when an interface with an LECS, an LES/BUS, and an LEC is shut down:
Router# debug lane finder
LECS FINDER ATM1/0.3: user request 1819 of type GET_MASTER_LECS_ADDRESS queued up LECS FINDER ATM1/0: finder state machine started LECS FINDER ATM1/0: time to perform a getNext on the ILMI LECS FINDER ATM1/0: LECS 47.00918100000000613E5A2F01.006070174823.00 deleted LECS FINDER ATM1/0: ilmi_client_request failed, answering all users LECS FINDER ATM1/0: answering all requests now LECS FINDER ATM1/0: responded to user request 1819 LECS FINDER ATM1/0: number of remaining requests still to be processed: 0 LECS FINDER ATM1/0.2: user request 1820 of type GET_MASTER_LECS_ADDRESS queued up LECS FINDER ATM1/0: finder state machine started LECS FINDER ATM1/0: time to perform a getNext on the ILMI LECS FINDER ATM1/0: ilmi_client_request failed, answering all users LECS FINDER ATM1/0: answering all requests now LECS FINDER ATM1/0: responded to user request 1820 LECS FINDER ATM1/0: number of remaining requests still to be processed: 0 LECS FINDER ATM1/0.1: user request 1821 of type GET_MASTER_LECS_ADDRESS queued up LECS FINDER ATM1/0: finder state machine started LECS FINDER ATM1/0: time to perform a getNext on the ILMI LECS FINDER ATM1/0: ilmi_client_request failed, answering all users LECS FINDER ATM1/0: answering all requests now LECS FINDER ATM1/0: responded to user request 1821 LECS FINDER ATM1/0: number of remaining requests still to be processed: 0
Use the debug lane server EXEC command to display information about a LANE server. The no form of this command disables debugging output.
[no] debug lane server [interface interface]
interface interface | (Optional) Limits the debugging output to messages relating to a specific interface or subinterface. If you use this command multiple times with different interfaces, the last interface entered is the one used to filter debug messages. |
The debug lane server output is intended to be used primarily by a Cisco technical support representative. The debug lane server command can generate a large amount of output. Specify a subinterface to decrease the amount of output and focus on the information you need.
The following is sample output from the debug lane server command when an interface with an LECS, an LES/BUS, and an LEC is shut down:
Router# debug lane server
LES ATM1/0.1: lsv_lecsAccessSigCB called with callId 0x60CE124C, opcode ATM_RELEASE_COMPLETE
LES ATM1/0.1: disconnected from the master LECS
LES ATM1/0.1: should have been connected, will reconnect in 3 seconds
LES ATM1/0.2: lsv_lecsAccessSigCB called with callId 0x60CE29E0, opcode ATM_RELEASE_COMPLETE
LES ATM1/0.2: disconnected from the master LECS
LES ATM1/0.2: should have been connected, will reconnect in 3 seconds
LES ATM1/0.3: lsv_lecsAccessSigCB called with callId 0x60EB1940, opcode ATM_RELEASE_COMPLETE
LES ATM1/0.3: disconnected from the master LECS
LES ATM1/0.3: should have been connected, will reconnect in 3 seconds
LES ATM1/0.2: elan yyy client 1 lost control distribute
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1 state change Oper -> Term
LES ATM1/0.3: elan zzz client 1 lost control distribute
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1 state change Oper -> Term
LES ATM1/0.2: elan yyy client 1 lost MC forward
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1 lost MC forward
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1 lost control distribute
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1 state change Oper -> Term
LES ATM1/0.1: elan xxx client 1 lost MC forward
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1 released control direct
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1 released control direct
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1 MC forward released
LES ATM1/0.2: elan yyy client 1: lsv_kill_client called
LES ATM1/0.2: elan yyy client 1: freeing client structures
LES ATM1/0.2: elan yyy client 1 unregistered 0060.7017.4820
LES ATM1/0.2: elan yyy client 1 destroyed
LES ATM1/0.3: elan zzz client 1 MC forward released
LES ATM1/0.3: elan zzz client 1: lsv_kill_client called
LES ATM1/0.3: elan zzz client 1: freeing client structures
LES ATM1/0.3: elan zzz client 1 unregistered 0060.7017.4820
LES ATM1/0.3: elan zzz client 1 destroyed
LES ATM1/0.1: elan xxx client 1 released control direct
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1 MC forward released
LES ATM1/0.1: elan xxx client 1: lsv_kill_client called
LES ATM1/0.1: elan xxx client 1: freeing client structures
LES ATM1/0.1: elan xxx client 1 unregistered 0060.7017.4820
LES ATM1/0.1: elan xxx client 1 destroyed
LES ATM1/0.1: elan xxx major interface state change
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: shutting down
LES ATM1/0.1: elan xxx: lsv_kill_lesbus called
LES ATM1/0.1: elan xxx: LES/BUS state change operational -> terminating
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: elan yyy major interface state change
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: shutting down
LES ATM1/0.2: elan yyy: lsv_kill_lesbus called
LES ATM1/0.2: elan yyy: LES/BUS state change operational -> terminating
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: elan zzz major interface state change
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: shutting down
LES ATM1/0.3: elan zzz: lsv_kill_lesbus called
LES ATM1/0.3: elan zzz: LES/BUS state change operational -> terminating
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: elan xxx: lsv_kill_lesbus called
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: elan xxx: lsv_kill_lesbus called
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: elan xxx: stopped listening on addresses
LES ATM1/0.1: elan xxx: all clients killed
LES ATM1/0.1: elan xxx: multicast groups killed
LES ATM1/0.1: elan xxx: addresses de-registered from ilmi
LES ATM1/0.1: elan xxx: LES/BUS state change terminating -> down
LES ATM1/0.1: elan xxx: administratively down
LES ATM1/0.2: elan yyy: lsv_kill_lesbus called
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: elan yyy: lsv_kill_lesbus called
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: elan yyy: stopped listening on addresses
LES ATM1/0.2: elan yyy: all clients killed
LES ATM1/0.2: elan yyy: multicast groups killed
LES ATM1/0.2: elan yyy: addresses de-registered from ilmi
LES ATM1/0.2: elan yyy: LES/BUS state change terminating -> down
LES ATM1/0.2: elan yyy: administratively down
LES ATM1/0.3: elan zzz: lsv_kill_lesbus called
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: elan zzz: lsv_kill_lesbus called
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.3: elan zzz: stopped listening on addresses
LES ATM1/0.3: elan zzz: all clients killed
LES ATM1/0.3: elan zzz: multicast groups killed
LES ATM1/0.3: elan zzz: addresses de-registered from ilmi
LES ATM1/0.3: elan zzz: LES/BUS state change terminating -> down
LES ATM1/0.3: elan zzz: administratively down
LES ATM1/0.3: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.2: cleanupLecsAccess: discarding all validation requests
LES ATM1/0.1: cleanupLecsAccess: discarding all validation requests
Use the debug lane signaling EXEC command to display information about LANE Server and BUS switched virtual circuits (SVCs). The no form of this command disables debugging output.
[no] debug lane signaling [interface interface]
interface interface | (Optional) Limits the debugging output to messages that relate to a particular interface or subinterface. If you enter this command multiple times with different interfaces, the last interface entered will be the one used to filter debug messages. |
The debug lane signaling output is intended to be used primarily by a Cisco technical support representative.
The debug lane signaling command can generate a large amount of output. Specify a subinterface to decrease the amount of output and focus on the information you need.
The following is sample output from the debug lane signaling command when an interface with an LECS, an LES/BUS, and an LEC is shut down:
Router# debug lane signaling
LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60EB565C cause 0 lv 0x60E8D348 lvstate LANE_VCC_CONNECTED LANE SIG ATM1/0.2: lane_sig_mc_release: breaking lv 0x60E8D348 from mcg 0x60E97E84 LANE SIG ATM1/0.2: timer for lv 0x60E8D348 stopped LANE SIG ATM1/0.2: sent ATM_RELEASE request for lv 0x60E8D468 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.2: sent ATM_RELEASE request for lv 0x60E8D3D8 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.2: sent ATM_RELEASE request for lv 0x60E8D2B8 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60EB5CA0 cause 0 lv 0x60E8BEF4 lvstate LANE_VCC_CONNECTED LANE SIG ATM1/0.3: lane_sig_mc_release: breaking lv 0x60E8BEF4 from mcg 0x60E9A37C LANE SIG ATM1/0.3: timer for lv 0x60E8BEF4 stopped LANE SIG ATM1/0.3: sent ATM_RELEASE request for lv 0x60E8C014 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.3: sent ATM_RELEASE request for lv 0x60E8BF84 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.3: sent ATM_RELEASE request for lv 0x60E8BE64 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60EB9040 cause 0 lv 0x60E8D468 lvstate LANE_VCC_DROP_SENT LANE SIG ATM1/0.2: lane_sig_mc_release: breaking lv 0x60E8D468 from mcg 0x60E97EC8 LANE SIG ATM1/0.2: timer for lv 0x60E8D468 stopped LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60EB97D4 cause 0 lv 0x60E8C014 lvstate LANE_VCC_DROP_SENT LANE SIG ATM1/0.3: lane_sig_mc_release: breaking lv 0x60E8C014 from mcg 0x60E9A3C0 LANE SIG ATM1/0.3: timer for lv 0x60E8C014 stopped LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBCEB8 cause 0 lv 0x60EBBAF0 lvstate LANE_VCC_CONNECTED LANE SIG ATM1/0.1: lane_sig_mc_release: breaking lv 0x60EBBAF0 from mcg 0x60E8F51C LANE SIG ATM1/0.1: timer for lv 0x60EBBAF0 stopped LANE SIG ATM1/0.1: sent ATM_RELEASE request for lv 0x60EBBC10 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.1: sent ATM_RELEASE request for lv 0x60EBBB80 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.1: sent ATM_RELEASE request for lv 0x60EBBA60 in state LANE_VCC_CONNECTED LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBEB00 cause 0 lv 0x60EBBC10 lvstate LANE_VCC_DROP_SENT LANE SIG ATM1/0.1: lane_sig_mc_release: breaking lv 0x60EBBC10 from mcg 0x60E8F560 LANE SIG ATM1/0.1: timer for lv 0x60EBBC10 stopped LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60E8B174 cause 0 lv 0x60E8D2B8 lvstate LANE_VCC_RELEASE_SENT LANE SIG ATM1/0.2: timer for lv 0x60E8D2B8 stopped LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60E8B990 cause 0 lv 0x60E8BE64 lvstate LANE_VCC_RELEASE_SENT LANE SIG ATM1/0.3: timer for lv 0x60E8BE64 stopped LANE SIG ATM1/0.2: received ATM_RELEASE_COMPLETE callid 0x60EB7FE0 cause 0 lv 0x60E8D3D8 lvstate LANE_VCC_RELEASE_SENT LANE SIG ATM1/0.2: timer for lv 0x60E8D3D8 stopped LANE SIG ATM1/0.3: received ATM_RELEASE_COMPLETE callid 0x60EB8554 cause 0 lv 0x60E8BF84 lvstate LANE_VCC_RELEASE_SENT LANE SIG ATM1/0.3: timer for lv 0x60E8BF84 stopped LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBB6D4 cause 0 lv 0x60EBBA60 lvstate LANE_VCC_RELEASE_SENT LANE SIG ATM1/0.1: timer for lv 0x60EBBA60 stopped LANE SIG ATM1/0.1: received ATM_RELEASE_COMPLETE callid 0x60EBE24C cause 0 lv 0x60EBBB80 lvstate LANE_VCC_RELEASE_SENT LANE SIG ATM1/0.1: timer for lv 0x60EBBB80 stopped LANE SIG ATM1/0.1: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER LANE SIG ATM1/0.1: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER LANE SIG ATM1/0.2: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER LANE SIG ATM1/0.2: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER LANE SIG ATM1/0.3: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER LANE SIG ATM1/0.3: sent ATM_CANCEL_NSAP request for lv 0x0 in state NULL_VCC_POINTER LANE SIG ATM1/0.1: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00 LANE SIG ATM1/0.1: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00 LANE SIG ATM1/0.2: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00 LANE SIG ATM1/0.2: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00 LANE SIG ATM1/0.3: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00 LANE SIG ATM1/0.3: received ATM_CANCEL_NSAP for nsap 00.000000000000050000000000.000000000000.00
Use the debug lapb EXEC command to display all traffic for interfaces using Link Access Procedure, Balanced (LAPB) encapsulation. The no form of this command disables debugging output.
[no] debug lapbThis command displays information on the X.25 Layer 2 protocol. It is useful to users who are familiar with the LAPB protocol.
You can use the debug lapb command to determine why X.25 interfaces or LAPB connections are going up and down. It is also useful for identifying link problems, as evidenced when show interfaces command displays a high number of rejects or frame errors over the X.25 link.
 | Caution Because the debug lapb command generates a lot of output, use it when the aggregate of all LAPB traffic on X.25 and LAPB interfaces is fewer than five frames per second. |
The following is sample output from the debug lapb command. (The numbers 1 through 7 at the top of the display have been added in order to aid documentation.)
1 2 3 4 5 6 7 Serial0: LAPB I CONNECT (5) IFRAME P 2 1 Serial0: LAPB O REJSENT (2) REJ F 3 Serial0: LAPB O REJSENT (5) IFRAME 0 3 Serial0: LAPB I REJSENT (2) REJ (C) 7 Serial0: LAPB I DISCONNECT (2) SABM P Serial0: LAPB O CONNECT (2) UA F Serial0: LAPB O CONNECT (5) IFRAME 0 0 Serial0: LAPB T1 CONNECT 357964 0
Each line of output describes a LAPB event. There are two types of LAPB events: frame events (when a frame enters or exits the LAPB) and timer events. In the sample output, the last line describes a timer event; all of the other lines describe frame events. Table 85 describes the first seven fields.
| Field | Description |
|---|---|
First field (1) | Interface type and unit number reporting the frame event. |
Second field (2) | Protocol providing the information. |
Third field (3) | Frame event type. Possible values follow:
|
Fourth field (4) | State of the protocol when the frame event occurred. Possible values follow:
|
Fifth field (5) | In a frame event, this value is the size of the frame (in bytes). In a timer event, this value is the current timer value (in milliseconds). |
Sixth field (6) | In a frame event, this value is the frame type name. Possible values for frame type names follow:
In a T1 timer event, this value is the number of retransmissions already attempted. |
Seventh field (7) (This field will not print if the frame control field is required to appear as either a command or a response, and that frame type is correct.) | This field is only present in frame events. It describes the frame type identified by the LAPB address and Poll/Final bit. Possible values are as follows:
|
A timer event only displays the first six fields of debug lapb output. For frame events, however, the fields that follow the sixth field document the LAPB control information present in the frame. Depending on the value of the frame type name shown in the sixth field, these fields may or may not appear. Descriptions of the fields following the first six fields follow.
After the Poll/Final indicator, depending on the frame type, three different types of LAPB control information can be printed.
For information frames, the value of the N(S) field and the N(R) field will be printed. The N(S) field of an information frame is the sequence number of that frame, so this field will rotate between 0 and 7 for (modulo 8 operation) or 0 and 127 (for modulo 128 operation) for successive outgoing information frames and (under normal circumstances) also will rotate for incoming information frame streams. The N(R) field is a "piggybacked" acknowledgment for the incoming information frame stream; it informs the other end of the link what sequence number is expected next.
RR, RNR, and REJ frames have an N(R) field, so the value of that field is printed. This field has exactly the same significance that it does in an information frame.
For the FRMR frame, the error information is decoded to display the rejected control field, V(R) and V(S) values, the Response/Command flag, and the error flags WXYZ.
In the following example, the output shows an idle link timer action (T4) where the timer expires twice on an idle link, with the value of T4 set to five seconds:
Serial2: LAPB T4 CONNECT 255748 Serial2: LAPB O CONNECT (2) RR P 5 Serial2: LAPB I CONNECT (2) RR F 5 Serial2: LAPB T4 CONNECT 260748 Serial2: LAPB O CONNECT (2) RR P 5 Serial2: LAPB I CONNECT (2) RR F 5
The next example shows an interface outage timer expiration (T3):
Serial2: LAPB T3 DISCONNECT 273284
The following example output shows an error condition when no DCE to DTE connection exists. Note that if a frame has only one valid type (for example, a SABM can only be a command frame), a received frame that has the wrong frame type will be flagged as a receive error (R/ERR in the following output). This feature makes misconfigured links (DTE-DTE or DCE-DCE) easy to spot. Other, less common errors will be highlighed too, such as a too-short or too-long frame, or an invalid address (neither command nor response).
Serial2: LAPB T1 SABMSENT 1026508 1 Serial2: LAPB O SABMSENT (2) SABM P Serial2: LAPB I SABMSENT (2) SABM (R/ERR) Serial2: LAPB T1 SABMSENT 1029508 2 Serial2: LAPB O SABMSENT (2) SABM P Serial2: LAPB I SABMSENT (2) SABM (R/ERR)
The output in the next example shows the router is misconfigured and has a standard (modulo 8) interface connected to an extended (modulo 128) interface. This condition is indicated by the SABM balanced mode and SABME balanced mode extended messages appearing on the same interface.
Serial2: LAPB T1 SABMSENT 1428720 0 Serial2: LAPB O SABMSENT (2) SABME P Serial2: LAPB I SABMSENT (2) SABM P Serial2: LAPB T1 SABMSENT 1431720 1 Serial2: LAPB O SABMSENT (2) SABME P Serial2: LAPB I SABMSENT (2) SABM P
Use the debug lat packet EXEC command to display information on all LAT events. The no form of this command disables debugging output.
[no] debug lat packetFor each datagram (packet) received or transmitted, a message is logged to the console.
The following is sample output from the debug lat packet command:
Router# debug lat packet
LAT: I int=Ethernet0, src=0000.0c01.0509, dst=0900.2b00.000f, type=0, M=0, R=0 LAT: I int=Ethernet0, src=0800.2b11.2d13, dst=0000.0c01.7876, type=A, M=0, R=0 LAT: O dst=0800.2b11.2d13, int=Ethernet0, type= A, M=0, R=0, len= 20, next 0 ref 1
The second line of output describes a packet that is input to the router. Table 86 describes the fields in this line.
| Field | Description |
|---|---|
LAT: | Indicates that this display shows LAT debugging output. |
I | Indicates that this line of output describes a packet that is input to the router (I) or output from the router (O). |
int = Ethernet0 | Indicates the interface on which the packet event took place. |
src = 0800.2b11.2d13 | Indicates the source address of the packet. |
dst = 0000.0c01.7876 | Indicates the destination address of the packet. |
type = A | Indicates the message type (in hexadecimal). Possible values are as follows:
|
The third line of output describes a packet that is output from the router. Table 87 describes the last three fields in this line.
| Field | Description |
|---|---|
len= 20 | Indicates the length (hexadecimal) of the packet in bytes. |
next 0 | Indicates the link on transmit queue. |
ref 1 | Indicates the count of packet users. |
Use the debug lex rcmd EXEC command to debug LAN Extender remote commands. The no form of this command disables debugging output.
[no] debug lex rcmdThe following is sample output from the debug lex rcmd command:
Router# debug lex rcmd
LEX-RCMD: "shutdown" command received on unbound serial interface- Serial0 LEX-RCMD: Lex0: "inventory" command received Rcvd rcmd: FF 03 80 41 41 13 00 1A 8A 00 00 16 01 FF 00 00 Rcvd rcmd: 00 02 00 00 07 5B CD 15 00 00 0C 01 15 26 LEX-RCMD: ACK or response received on Serial0 without a corresponding ID LEX-RCMD: REJ received LEX-RCMD: illegal CODE field received in header: <number> LEX-RCMD: illegal length for Lex0: "lex input-type-list" LEX-RCMD: Lex0 is not bound to a serial interface LEX-RCMD: encapsulation failure LEX-RCMD: timeout for Lex0: "lex priority-group" command LEX-RCMD: re-transmitting Lex0: "lex priority-group" command LEX-RCMD: lex_setup_and_send called with invalid parameter LEX-RCMD: bind occurred on shutdown LEX interface LEX-RCMD: Serial0- No free Lex interface found with negotiated MAC address 0000.0c00.d8db LEX-RCMD: No active Lex interface found for unbind
The following output indicates that a LAN Extender remote command packet was received on a serial interface that is not bound to a LAN Extender interface:
LEX-RCMD: "shutdown" command received on unbound serial interface- Serial0
This message can occur for any of the LAN Extender remote commands. Possible causes of this message are as follows:
The following output indicates that a LAN Extender remote command response has been received. The hexadecimal values are for internal use only.
LEX-RCMD: Lex0: "inventory" command received Rcvd rcmd: FF 03 80 41 41 13 00 1A 8A 00 00 16 01 FF 00 00 Rcvd rcmd: 00 02 00 00 07 5B CD 15 00 00 0C 01 15 26
The following output indicates that when the host router originates a LAN Extender remote command to FLEX, it generates an 8-bit identifier which is used to associate a command with its corresponding response:
LEX-RCMD: ACK or response received on Serial0 without a corresponding ID
This message could be displayed for any of the following reasons:
Possible responses to Config-Request are Config-ACK, Config-NAK, and Config-Rej. The following output shows that some of the options in the Config-Request are not recognizable or are not acceptable to FLEX due to transmission errors or software errors:
LEX-RCMD: REJ received
The following output shows that a LAN Extender remote command response was received but that the CODE field in the header was incorrect:
LEX-RCMD: illegal CODE field received in header: <number>
The following output indicates that a LAN Extender remote command response was received but that it had an incorrect length field. This message can occur for any of the LAN Extender remote commands.
LEX-RCMD: illegal length for Lex0: "lex input-type-list"
The following output shows that a host router was about to send a remote command when the serial link went down:
LEX-RCMD: Lex0 is not bound to a serial interface
The following output shows that the serial interface's encapsulation routine failed to encapsulate the remote command datagram because the LEX-NCP was not in the OPEN state. Due to the way the PPP state machine is implemented, it is normal to see a single encapsulation failure for each remote command that gets sent at bind time.
LEX-RCMD: encapsulation failure
The following output shows that the timer expired for the given remote command without having received a response from the FLEX device. This message can occur for any of the LAN Extender remote commands.
LEX-RCMD: timeout for Lex0: "lex priority-group" command
This message could be displayed for any of the following reasons:
The following output indicates that the host is retransmitting the remote command after a timeout:
LEX-RCMD: re-transmitting Lex0: "lex priority-group" command
The following output indicates that an illegal parameter was passed to the lex_setup_and_send routine. This message could be displayed for due to a host software error.
LEX-RCMD: lex_setup_and_send called with invalid parameter
The following output is informational and shows when a bind occurs on a shutdown interface:
LEX-RCMD: bind occurred on shutdown LEX interface
The following output shows that LEX-NCP reached the open state and a bind operation was attempted with the FLEX's MAC address, but no free LAN Extender interfaces were found that were configured with that MAC address. This output can occur when the network administrator does not configure a LAN Extender interface with the correct MAC address.
LEX-RCMD: Serial0- No free Lex interface found with negotiated MAC address 0000.0c00.d8db
The following output shows that the serial line that was bound to the LAN Extender interface went down and the unbind routine was called, but when the list of active LAN Extender interfaces was searched, the LAN Extender interface corresponding to the serial interface was not found. This output usually occurs because of a host software error.
LEX-RCMD: No active Lex interface found for unbind
Use the debug list EXEC command to filter debugging information on a per-interface or per-access list basis. The no form of this command turns off the list filter.
debug list [list] [interface]
list | (Optional) An access list number in the range of 1100-1199. |
interface | (Optional) Interface type. Allowed values include · channel---IBM Channel interface · ethernet---IEEE 802.3 · fddi---ANSI X3T9.5 · null---Null interface · serial---Serial · tokenring---IEEE 802.5 · tunnel---Tunnel interface |
The debug list command is used with other debug commands for specific protocols and interfaces to filter the amount of debug information that is displayed. In particular, this command is designed to filter specific physical unit (PU) output from bridging protocols. The debug list command is supported with the following commands:
To use debug list on only the first of several LLC2 connections, use the show llc2 command to display the active connections:
Router# show llc2
SdllcVirtualRing2008 DTE: 4000.2222.22c7 4000.1111.111c 04 04 state NORMAL SdllcVirtualRing2008 DTE: 4000.2222.22c8 4000.1111.1120 04 04 state NORMAL SdllcVirtualRing2008 DTE: 4000.2222.22c1 4000.1111.1104 04 04 state NORMAL
Next, configure an extended bridging access list, numbered 1103, for the connection you want to filter:
access-list 1103 permit 4000.1111.111c 0000.0000.0000 4000.2222.22c7 0000.0000.0000 0xC 2 eq 0x404
The convention for LLC debug list filtering is to use dmac=6 bytes, smac=6 bytes, dsap_offset = 12, and ssap_offset = 13.
Finally, you invoke the following debug commands:
Router# debug list 1103
Router# debug llc2 packet
LLC2 Packets debugging is on for access list: 1103
To use debug list for SDLC connections, with the exception of address 04, create access list 1102 to deny the specific address and permit all others:
access-list 1102 deny 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000 0xC 1 eq 0x4
access-list 1102 permit 0000.0000.0000 0000.0000.0000 0000.0000.0000 0000.0000.0000
The convention is to use dmac = 0.0.0, smac = 0.0.0, and sdlc_frame_offset = 12.
Invoke the following debug commands:
Router# debug list 1102
Router# debug sdlc
SDLC link debugging is on for access list: 1102
To enable SDLC debugging (or debugging for any of the other supported protocols) for a specific interface rather than for all interfaces on a router, use the following commands:
Router# debug list serial 0
Router# debug sdlc
SDLC link debugging is on for interface: Serial0
To enable Token Ring debugging between two MAC address, 0000.3018.4acd and 0000.30e0.8250, configure an extended bridging access list 1106:
access-list 1106 permit 0000.3018.4acd 8000.0000.0000 0000.30e0.8250 8000.0000.0000
access-list 1106 permit 0000.30e0.8250 8000.0000.0000 0000.3018.4acd 8000.0000.0000
Invoke the following debug commands:
Router# debug list 1106
Router# debug token ring
Token Ring Interface debugging is on for access list: 1106
To enable RIF debugging for a single MAC address, configure an access list 1109:
access-list 1109 permit permit 0000.0000.0000 ffff.ffff.ffff 4000.2222.22c6 0000.0000.0000
Invoke the following debug commands:
Router# debug list 1109
Router# debug rif
RIF update debugging is on for access list: 1109
debug llc2 errors
debug llc2 packet
debug llc2 state
debug rif
debug sdlc
debug token ring
Use the debug llc2 dynwind EXEC command to display changes to the dynamic window over Frame Relay. The no form of this command disables debugging output.
[no] debug llc2 dynwindThe following is sample output from the debug llc2 dynwind command:
Router# debug llc2 dynwind
LLC2/DW: BECN received! event REC_I_CMD, Window size reduced to 4 LLC2/DW: 1 consecutive I-frame(s) received without BECN LLC2/DW: 2 consecutive I-frame(s) received without BECN LLC2/DW: 3 consecutive I-frame(s) received without BECN LLC2/DW: 4 consecutive I-frame(s) received without BECN LLC2/DW: 5 consecutive I-frame(s) received without BECN LLC2/DW: Current working window size is 5
In this example, the router receives a backward explicit congestion notification (BECN) and reduces the window size to four. After receiving five consecutive I-frames without a BECN, the router increases the window size to five.
debug llc2 errors
debug llc2 packet
debug llc2 state
Use the debug llc2 errors EXEC command to display Logical Link Control, type 2 (LLC2) protocol error conditions or unexpected input. The no form of this command disables debugging output.
[no] debug llc2 errorsThe following is sample output from the debug llc2 errors command from a router ignoring an incorrectly configured device:
Router# debug llc2 errors
LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP LLC: admstate: 4000.1014.0001 0000.0000.0000 04 04 REC_RR_RSP
Each line of output contains the remote MAC address, the local MAC address, the remote service access point (SAP), and the local SAP. In this example, the router receives unsolicited RR frames marked as responses.
debug list
debug llc2 dynwind
debug llc2 packet
debug llc2 state
The following is sample output from the debug llc2 packet command from the router sending ping data back and forth to another router:
Router# debug llc2 packet
LLC: llc2_input 401E54F0: 10400000 .@.. 401E5500: 303A90CF 0006F4E1 2A200404 012B5E 0:.O..ta* ...+ LLC: i REC_RR_CMD N(R)=21 p/f=1 LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 NORMAL REC_RR_CMD (3) LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_RR_CMD N(R)=42 LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 txmt RR_RSP N(R)=20 p/f=1 LLC: llc_sendframe 401E5610: 0040 0006F4E1 2A200000 .@..ta* .. 401E5620: 303A90CF 04050129 00 N 0:.O...). 2012 LLC: llc_sendframe 4022E3A0: 0040 0006F4E1 .@..ta 4022E3B0: 2A200000 303A90CF 04042A28 2C000202 * ..0:.O..*(,... 4022E3C0: 00050B90 A02E0502 FF0003D1 004006C1 .... ......Q.@.A 4022E3D0: D7C9D5C 0.128 C400130A C1D7D7D5 4BD5F2F0 WIUGD...AWWUKUrp 4022E3E0: F1F30000 011A6071 00010860 D7027000 qs....\Qq...\QW.p. 4022E3F0: 00003B00 1112FF01 03000243 6973636F ..;........Cisco 4022E400: 20494F53 69 IOSi LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 txmt I N(S)=21 N(R)=20 p/f=0 size=90 LLC: llc2_input 401E5620: 10400000 303A90CF .@..0:.O 401E5630: 0006F4E1 2A200404 282C2C00 02020004 ..ta* ..(,,..... 401E5640: 03902000 1112FF01 03000243 6973636F .. ........Cisco 401E5650: 20494F53 A0 IOS LLC: i REC_I_CMD N(R)=22 N(S)=20 V(R)=20 p/f=0 LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 NORMAL REC_I_CMD (1) LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_I_CMD N(S)=20 V(R)=20 LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_I_CMD N(R)=44 LLC: INFO: 0006.f4e1.2a20 0000.303a.90cf 04 04 v(r) 20
The first three lines indicate that the router has received some input from the link:
LLC: llc2_input 401E54F0: 10400000 .@.. 401E5500: 303A90CF 0006F4E1 2A200404 012B5E 0:.O..ta* ...+
The next line indicates that this input was an RR command with the poll bit set. The other router has received sequence number 21 and is waiting for the final bit.
LLC: i REC_RR_CMD N(R)=21 p/f=1
The next two lines contain the MAC addresses of the sender and receiver as well as the state of the router when it received this frame.
LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 NORMAL REC_RR_CMD (3) LLC (rs): 0006.f4e1.2a20 0000.303a.90cf 04 04 REC_RR_CMD N(R)=42
The next four lines indicate that the router is transmitting a response with the final bit set.
LLC: 0006.f4e1.2a20 0000.303a.90cf 04 04 txmt RR_RSP N(R)=20 p/f=1 LLC: llc_sendframe 401E5610: 0040 0006F4E1 2A200000 .@..ta* .. 401E5620: 303A90CF 04050129 00 N 0:.O...). 2012
debug list
debug llc2 dynwind
debug llc2 errors
debug llc2 state
Use the debug llc2 state EXEC command to display state transitions of the Logical Link Control, type 2 (LLC2) protocol. The no form of this command disables debugging output.
[no] debug llc2 stateRefer to the ISO/IEC standard 8802-2 for definitions and explanations of debug llc2 state output.
The following is sample output from the debug llc2 state command when a router disables and enables an interface:
Router# debug llc2 state
LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, NORMAL -> AWAIT (P_TIMER_EXP) LLC(rs): 0006.f4e1.2a20 0000.303a.90cf 04 04, AWAIT -> D_CONN (P_TIMER_EXP) LLC: cleanup 0006.f4e1.2a20 0000.303a.90cf 04 04, UNKNOWN (17) LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, ADM -> SETUP (CONN_REQ) LLC: normalstate: set_local_busy 0006.f4e1.2a20 0000.303a.90cf 04 04 LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, NORMAL -> BUSY (SET_LOCAL_BUSY) LLC: Connection established: 0006.f4e1.2a20 0000.303a.90cf 04 04, success LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, SETUP -> BUSY (SET_LOCAL_BUSY) LLC: busystate: 0006.f4e1.2a20 0000.303a.90cf 04 04 local busy cleared LLC (stsw): 0006.f4e1.2a20 0000.303a.90cf 04 04, BUSY -> NORMAL (CLEAR_LOCAL_BUSY)
debug list
debug llc2 dynwind
debug llc2 errors
debug llc2 packet
Use the debug lnm events EXEC command to display any unusual events that occur on a Token Ring network. These events include stations reporting errors or error thresholds being exceeded. The no form of this command disables debugging output.
[no] debug lnm eventsThe following is sample output from the debug lnm events command:
Router# debug lnm events
IBMNM3: Adding 0000.3001.1166 to error list IBMNM3: Station 0000.3001.1166 going into preweight condition IBMNM3: Station 0000.3001.1166 going into weight condition IBMNM3: Removing 0000.3001.1166 from error list LANMGR0: Beaconing is present on the ring LANMGR0: Ring is no longer beaconing IBMNM3: Beaconing, Postmortem Started IBMNM3: Beaconing, heard from 0000.3000.1234 IBMNM3: Beaconing, Postmortem Next Stage IBMNM3: Beaconing, Postmortem Finished
The following message indicates that station 0000.3001.1166 reported errors and has been added to the list of stations reporting errors. This station is located on Ring 3.
IBMNM3: Adding 0000.3001.1166 to error list
The following message indicates that station 0000.3001.1166 has passed the "early warning" threshold for error counts:
IBMNM3: Station 0000.3001.1166 going into preweight condition
The following message indicates that station 0000.3001.1166 is experiencing a severe number of errors:
IBMNM3: Station 0000.3001.1166 going into weight condition
The following message indicates that the error counts for station 0000.3001.1166 have all decayed to zero, so this station is being removed from the list of stations that have reported errors:
IBMNM3: Removing 0000.3001.1166 from error list
The following message indicates that Ring 0 has entered failure mode. This ring number is assigned internally.
LANMGR0: Beaconing is present on the ring
The following message indicates that Ring 0 is no longer in failure mode. This ring number is assigned internally.
LANMGR0: Ring is no longer beaconing
The following message indicates that the router is beginning its attempt to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. The router attempts to contact stations that were part of the fault domain to detect whether they are still operating on the ring.
IBMNM3: Beaconing, Postmortem Started
The following message indicates that the router is attempting to determine whether or not any stations left the ring during the automatic recovery process for the last beaconing failure. It received a response from station 0000.3000.1234, one of the two stations in the fault domain.
IBMNM3: Beaconing, heard from 0000.3000.1234
The following message indicates that the router is attempting to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. It is initiating another attempt to contact the two stations in the fault domain.
IBMNM3: Beaconing, Postmortem Next Stage
The following message indicates that the router has attempted to determine whether any stations left the ring during the automatic recovery process for the last beaconing failure. It has successfully heard back from both stations that were part of the fault domain.
IBMNM3: Beaconing, Postmortem Finished
Explanations follow for other messages that the debug lnm events command can generate.
The following message indicates that the router is out of memory:
LANMGR: memory request failed, find_or_build_station()
The following message indicates that Ring 3 is experiencing a large number of errors that cannot be attributed to any individual station:
IBMNM3: Non-isolating error threshold exceeded
The following message indicates that a station (or stations) on Ring 3 are receiving frames faster than they can be processed:
IBMNM3: Adapters experiencing congestion
The following message indicates that the beaconing has lasted for over 1 minute and is considered a "permanent" error:
IBMNM3: Beaconing, permanent
The following message indicates that the beaconing lasted for less than 1 minute. The router is attempting to determine whether either station in the fault domain left the ring.
IBMNM: Beaconing, Destination Started
In the preceding line of output, the following can replace "Started": "Next State", "Finished", "Timed out", and "Cannot find station n".
Use the debug lnm llc EXEC command to display all communication between the router/bridge and the LAN Network Managers (LNMs) that have connections to it. The no form of this command disables debugging output.
[no] debug lnm llcOne line is displayed for each message sent or received.
The following is sample output from the debug lnm llc command:
Router# debug lnm llc
IBMNM: Received LRM Set Reporting Point frame from 1000.5ade.0d8a. IBMNM: found bridge: 001-2-00A, addresses: 0000.3040.a630 4000.3040.a630 IBMNM: Opening connection to 1000.5ade.0d8a on TokenRing0 IBMNM: Sending LRM LAN Manager Accepted to 1000.5ade.0d8a on link 0. IBMNM: sending LRM New Reporting Link Established to 1000.5a79.dbf8 on link 1. IBMNM: Determining new controlling LNM IBMNM: Sending Report LAN Manager Control Shift to 1000.5ade.0d8a on link 0. IBMNM: Sending Report LAN Manager Control Shift to 1000.5a79.dbf8 on link 1. IBMNM: Bridge 001-2-00A received Request Bridge Status from 1000.5ade.0d8a. IBMNM: Sending Report Bridge Status to 1000.5ade.0d8a on link 0. IBMNM: Bridge 001-2-00A received Request REM Status from 1000.5ade.0d8a. IBMNM: Sending Report REM Status to 1000.5ade.0d8a on link 0. IBMNM: Bridge 001-2-00A received Set Bridge Parameters from 1000.5ade.0d8a. IBMNM: Sending Bridge Parameters Set to 1000.5ade.0d8a on link 0. IBMNM: sending Bridge Params Changed Notification to 1000.5a79.dbf8 on link 1. IBMNM: Bridge 001-2-00A received Set REM Parameters from 1000.5ade.0d8a. IBMNM: Sending REM Parameters Set to 1000.5ade.0d8a on link 0. IBMNM: sending REM Parameters Changed Notification to 1000.5a79.dbf8 on link 1. IBMNM: Bridge 001-2-00A received Set REM Parameters from 1000.5ade.0d8a. IBMNM: Sending REM Parameters Set to 1000.5ade.0d8a on link 0. IBMNM: sending REM Parameters Changed Notification to 1000.5a79.dbf8 on link 1. IBMNM: Received LRM Set Reporting Point frame from 1000.5ade.0d8a. IBMNM: found bridge: 001-1-00A, addresses: 0000.3080.2d79 4000.3080.2d7
As the above indicates, debug lnm llc output can vary somewhat in format. Table 88 describes significant fields shown in the first line of output.
| Field | Description |
|---|---|
IBMNM: | This line of output displays LLC-level debugging information. |
Received | The router received a frame. The other possible value is Sending, to indicate that the router is sending a frame. |
LRM | The function of the LLC-level software that is communicating:
|
Set Reporting Point | Name of the specific frame that the router sent or received. Possible values include the following:
|
from 1000.5ade.0d8a | If the router has received the frame, this address is the source address of the frame. If the router is sending the frame, this address is the destination address of the frame. |
The following message indicates that the lookup for the bridge with which the LAN Manager was requesting to communicate was successful:
IBMNM: found bridge: 001-2-00A, addresses: 0000.3040.a630 4000.3040.a630
The following message indicates the connection is being opened:
IBMNM: Opening connection to 1000.5ade.0d8a on TokenRing0
The following message indicates that a LAN Manager has connected or disconnected from an internal bridge and that the router computes which LAN Manager is allowed to change parameters:
IBMNM: Determining new controlling LNM
The following line of output indicates which bridge in the router is the destination for the frame:
IBMNM: Bridge 001-2-00A received Request Bridge Status from 1000.5ade.0d8a.
Use the debug lnm mac EXEC command to display all management communication between the router/bridge and all stations on the local Token Rings. The no form of this command disables debugging output.
[no] debug lnm macOne line is displayed for each message sent or received.
The following is sample output from the debug lnm mac command:
Router# debug lnm mac
LANMGR0: RS received request address from 4000.3040.a670. LANMGR0: RS sending report address to 4000.3040.a670. LANMGR0: RS received request state from 4000.3040.a670. LANMGR0: RS sending report state to 4000.3040.a670. LANMGR0: RS received request attachments from 4000.3040.a670. LANMGR0: RS sending report attachments to 4000.3040.a670. LANMGR2: RS received ring purge from 0000.3040.a630. LANMGR2: CRS received report NAUN change from 0000.3040.a630. LANMGR2: RS start watching ring poll. LANMGR0: CRS received report NAUN change from 0000.3040.a630. LANMGR0: RS start watching ring poll. LANMGR2: REM received report soft error from 0000.3040.a630. LANMGR0: REM received report soft error from 0000.3040.a630. LANMGR2: RS received ring purge from 0000.3040.a630. LANMGR2: RS received AMP from 0000.3040.a630. LANMGR2: RS received SMP from 0000.3080.2d79. LANMGR2: CRS received report NAUN change from 1000.5ade.0d8a. LANMGR2: RS start watching ring poll. LANMGR0: RS received ring purge from 0000.3040.a630. LANMGR0: RS received AMP from 0000.3040.a630. LANMGR0: RS received SMP from 0000.3080.2d79. LANMGR0: CRS received report NAUN change from 1000.5ade.0d8a. LANMGR0: RS start watching ring poll. LANMGR2: RS received SMP from 1000.5ade.0d8a. LANMGR2: RPS received request initialization from 1000.5ade.0d8a. LANMGR2: RPS sending initialize station to 1000.5ade.0d8a.
Table 89 describes significant fields shown in the first line of output.
| Field | Description |
|---|---|
LANMGR0: | LANMGR indicates that this line of output displays MAC-level debugging information. 0 indicates the number of the Token Ring interface associated with this line of debugging output. |
RS | Indicates which function of the MAC-level software is communicating:
|
received | Indicates that the router received a frame. The other possible value is "sending", to indicate that the router is sending a frame. |
request address | Indicates the name of the specific frame that the router sent or received. Possible values include the following:
|
from 4000.3040.a670 | Indicates the source address of the frame, if the router has received the frame. If the router is sending the frame, this address is the destination address of the frame. |
As the above indicates, all debug lnm mac messages follow the format described in Table 89 except the following:
LANMGR2: RS start watching ring poll LANMGR2: RS stop watching ring poll
These messages indicate that the router starts and stops receiving AMP and SMP frames. These frames are used to build a current picture of which stations are on the ring.
Use the debug local-ack state EXEC command to display the new and the old state conditions whenever there is a state change in the local acknowledgment state machine. The no form of this command disables debugging output.
[no] debug local-ack stateThe following is sample output from the debug local-ack state command:
Router# debug local-ack state
LACK_STATE: 2370300, hashp 2AE628, old state = disconn, new state = awaiting LLC2 open to finish LACK_STATE: 2370304, hashp 2AE628, old state = awaiting LLC2 open to finish, new state = connected LACK_STATE: 2373816, hashp 2AE628, old state = connected, new state = disconnected LACK_STATE: 2489548, hashp 2AE628, old state = disconn, new state = awaiting LLC2 open to finish LACK_STATE: 2489548, hashp 2AE628, old state = awaiting LLC2 open to finish, new state = connected LACK_STATE: 2490132, hashp 2AE628, old state = connected, new state = awaiting linkdown response LACK_STATE: 2490140, hashp 2AE628, old state = awaiting linkdown response, new state = disconnected LACK_STATE: 2497640, hashp 2AE628, old state = disconn, new state = awaiting LLC2 open to finish LACK_STATE: 2497644, hashp 2AE628, old state = awaiting LLC2 open to finish, new state = connected
Table 90 describes significant fields.
| Field | Description |
|---|---|
LACK_STATE: | Indication that this packet describes a state change in the local acknowledgment state machine. |
2370300 | System clock. |
hashp 2AE628 | Internal control block pointer used by technical support staff for debugging purposes. |
old state = disconn | The old state condition in the local acknowledgment state machine. Possible values include the following:
|
new state = awaiting LLC2 open to finish | The new state condition in the local acknowledgment state machine. Possible values include the following:
|
|
|