Table Of Contents
debug serial interface
Use the debug serial interface EXEC command to display information on a serial connection failure. The no form of this command disables debugging output.
[no] debug serial interface
Usage Guidelines
If the show interface serial command shows that the line and protocol are down, you can use the debug serial interface command to isolate a timing problem as the cause of a connection failure. If the keepalive values in the mineseq, yourseen, and myseen fields are not incrementing in each subsequent line of output, there is a timing or line problem at one end of the connection.
Note
While the debug serial interface command typically does not generate a lot of output, nevertheless use it cautiously during production hours. When SMDS is enabled, for example, it can generate considerable output.
The output of the debug serial interface command can vary, depending on the type of WAN configured for an interface: Frame Relay, HDLC, HSSI, SMDS, or X.25. The output also can vary depending on the type of encapsulation configured for that interface. The hardware platform also can affect debug serial interface output.
The following sections show sample debug serial interface displays for various configurations and describe the possible output the command can generate for these configurations.
Debug Serial Interface for Frame Relay Encapsulation
The following message is displayed if the encapsulation for the interface is Frame Relay (or HDLC) and the router attempts to send a packet containing an unknown packet type:
Illegal serial link type code xxxDebug Serial Interface for HDLC
shows sample debug serial interface output for an HDLC connection when keepalives are enabled.In , the debug serial interface display shows that the remote router is not receiving all the keepalives the router is sending. When the difference in the values in the myseq and mineseen fields exceeds three, the line goes down and the interface is reset.
Figure 2-234 Sample Debug Serial Interface Output for HDLC
describes significant fields shown in .
describes additional error messages that the debug serial interface command can generate for HDLC.
Debug Serial Interface for HSSI
On an HSSI interface, the debug serial interface command can generate the following additional error message:
HSSI0: Reset from 0xnnnnnnnThis message indicates that the HSSI hardware has been reset. The 0xnnnnnnn variable is the address of the routine requesting that the hardware be reset; this value is useful only to development engineers.
Debug Serial Interface for ISDN Basic Rate
describes error messages that the debug serial interface command can generate for ISDN Basic Rate.
Debug Serial Interface for an MK5025 Device
describes the additional error messages that the debug serial interface command can generate for an MK5025 device.
Debug Serial Interface for SMDS Encapsulation
When encapsulation is set to SMDS, debug serial interface displays SMDS packets that are sent and received, as well as any error messages resulting from SMDS packet transmission.
The error messages that the debug serial interface command can generate for SMDS follow.
The following message indicates that a new protocol requested SMDS to encapsulate the data for transmission. SMDS is not yet able to encapsulate the protocol.
SMDS: Error on Serial 0, encapsulation bad protocol = xThe following message indicates that SMDS was asked to encapsulate a packet, but no corresponding destination E.164 SMDS address was found in any of the static SMDS tables or in the ARP tables:
SMDS send: Error in encapsulation, no hardware address, type = xThe following message indicates that a protocol such as CLNS or IP has been enabled on an SMDS interface, but the corresponding multicast addresses have not been configured. The n variable displays the link type for which encapsulation was requested.
SMDS: Send, Error in encapsulation, type=nThe following messages can occur when a corrupted packet is received on an SMDS interface. The router expected x, but received y.
SMDS: Invalid packet, Reserved NOT ZERO, x ySMDS: Invalid packet, TAG mismatch x ySMDS: Invalid packet, Bad TRAILER length x yThe following messages can indicate an invalid length for an SMDS packet:
SMDS: Invalid packet, Bad BA length xSMDS: Invalid packet, Bad header extension length xSMDS: Invalid packet, Bad header extension type xSMDS: Invalid packet, Bad header extension value xThe following messages are displayed when the debug serial interface command is enabled:
Interface Serial 0 Sending SMDS L3 packet:SMDS: dgsize:x type:0xn src:y dst:zIf the debug serial interface command is enabled, the following message can be displayed when a packet is received on an SMDS interface, but the destination SMDS address does not match any on that interface:
SMDS: Packet n, not addressed to usdebug serial packet
Use the debug serial packet EXEC command to display more detailed serial interface debugging information than you can obtain using debug serial interface command. The no form of this command disables debugging output.
[no] debug serial packet
Usage Guidelines
The debug serial packet command generates output that is dependent on the type of serial interface and the encapsulation that is running on that interface. The hardware platform also can impact debug serial packet output.
The debug serial packet command displays output for only SMDS encapsulations.
Sample Display
shows sample output when SMDS is enabled on the interface.
Figure 2-235 Sample Debug Serial Packet Output for SMDS
Router# debug serial packetInterface Serial2 Sending SMDS L3 packet:SMDS Header: Id: 00 RSVD: 00 BEtag: EC Basize: 0044Dest:E18009999999FFFF Src:C12015804721FFFF Xh:04030000030001000000000000000000SMDS LLC: AA AA 03 00 00 00 80 38SMDS Data: E1 19 01 00 00 80 00 00 0C 00 38 1F 00 0A 00 80 00 00 0C 01 2B 71SMDS Data: 06 01 01 0F 1E 24 00 EC 00 44 00 02 00 00 83 6C 7D 00 00 00 00 00SMDS Trailer: RSVD: 00 BEtag: EC Length: 0044As shows, when encapsulation is set to SMDS, debug serial packet displays the entire SMDS header (in hex), as well as some payload data on transmit or receive. This information is useful only when you have an understanding of the SMDS protocol. The first line of the output indicates either Sending or Receiving.
debug service-module
Use the debug service-module EXEC command to display debugging information that monitors the detection and clearing of network alarms on the integrated channel service unit/data service unit (CSU/DSU) modules installed in a Cisco 2524 or Cisco 2525 router. The no form of this command disables debugging output.
[no] debug service-module
Usage Guidelines
Use this command to enable and disable debug logging for the serial 0 and serial 1 interfaces when an integrated CSU/DSU is present. This command enables debugging on all interfaces.
Network alarm status can also be viewed through the use of the show service-module command.
Note
Sample Display
shows sample debug service-module output.
Figure 2-236 Sample Debug Service-Module Output
Router# debug service-moduleSERVICE_MODULE(1): loss of signal ended after duration 00:05:36SERVICE_MODULE(1): oos/oof ended after duration 01:05:14SERVICE_MODULE(0): Unit has no clockSERVICE_MODULE(0): detects loss of signalSERVICE_MODULE(0): loss of signal ended after duration 00:00:33debug smrp all
Use the debug smrp all EXEC command to display information about Simple Multicast Routing Protocol (SMRP) activity. The no form of this command disables debugging output.
[no] debug smrp all
Usage Guidelines
Because the debug smrp all command displays all SMRP debugging output, it is processor intensive and should not be enabled when memory is scarce or in very high traffic situations.
For general debugging, use the debug smrp all command and turn off excessive transactions with the no debug smrp transaction command. This combination of commands will display various state changes and events without displaying every transaction packet. For debugging a specific feature such as a routing problem, use the debug smrp route and debug smrp transaction commands to see if packets are sent and received and which specific routes are affected. The show smrp traffic command is highly recommended as a troubleshooting method because it displays the SMRP counters.
For examples of the type of output you may see, refer to each of the commands listed in the "Related Commands" section.
Related Commands
debug smrp group
debug smrp mcache
debug smrp neighbor
debug smrp port
debug smrp route
debug smrp transactiondebug smrp group
Use the debug smrp group EXEC command to display information about SMRP group activity. The no form of this command disables debugging output.
[no] debug smrp group
Usage Guidelines
The debug smrp group command displays information when a group is created or deleted and when a forwarding entry for a group is created, changed, or deleted.
For more information, refer to the show smrp group command described in the Network Protocols Command Reference, Part 2
Sample Display
Figure 2-237 shows sample debug smrp group output of a port being created and deleted on group AT 20.34. (AT signifies that this is an AppleTalk network group.)
Figure 2-237 Sample Debug SMRP Group Output
Router# debug smrp groupSMRP: Group AT 20.34, created on port 20.1 by 20.2SMRP: Group AT 20.34, deleted on port 20.1lists the messages that may be generated with the debug smrp group command concerning the forwarding table.
Related Command
debug smrp mcache
Use the debug smrp mcache EXEC command to display information about SMRP multicast fast-switching cache entries. The no form of this command disables debugging output.
[no] debug smrp mcache
Usage Guidelines
Use the show smrp mcache command (described in the Network Protocols Command Reference, Part 2) to display the entries in the SMRP multicast cache, and use the debug smrp mcache command to see whether the cache is being populated and invalidated.
Sample Display
Figure 2-238 shows sample debug smrp mcache output. In this example, the cache is created and populated for group AT 11.124. (AT signifies that this is an AppleTalk network group.)
Figure 2-238 Sample Debug SMRP Multicast Route Cache Output
Router# debug smrp mcacheSMRP: Cache createdSMRP: Cache populated for group AT 11.124mac - 090007400b7c00000c1740d9net - 001fef7500000014ff020a0a0aSMRP: Forward cache entry created for group AT 11.124SMRP: Forward cache entry validated for group AT 11.124SMRP: Forward cache entry invalidated for group AT 11.124SMRP: Forward cache entry deleted for group AT 11.124lists all the messages that can be generated with the debug smrp mcache command concerning the multicast cache.
Related Command
debug smrp neighbor
Use the debug smrp neighbor EXEC command to display information about SMRP neighbor activity. The no form of this command disables debugging output.
[no] debug smrp neighbor
Usage Guidelines
The debug smrp neighbor command displays information when a neighbor operating state changes. A neighbor is an adjacent router. For more information, refer to the show smrp neighbor command described in the Network Protocols Command Reference, Part 2.
Sample Display
Figure 2-239 shows sample debug smrp neighbor output. In this example, the neighbor on port 30.02 has changed state from normal operation to secondary operation.
Figure 2-239 Sample Debug SMRP Neighbor Output
Router# debug smrp neighborSMRP: Neighbor 30.2, state changed from "normal op" to "secondary op"lists all the messages that can be generated with the debug smrp neighbor command concerning the neighbor table.
Related Command
debug smrp port
Use the debug smrp port EXEC command to display information about SMRP port activity. The no form of this command disables debugging output.
[no] debug smrp port
Usage Guidelines
The debug smrp port command displays information when a port operating state changes.
For more information, refer to the show smrp port command described in the Network Protocols Command Reference, Part 2.
Sample Display
Figure 2-240 shows sample debug smrp port output. In this example, port 30.1 has changed state from secondary negative to secondary operation to primary negative.
Figure 2-240 Sample Debug SMRP Port Output
Router# debug smrp portSMRP: Port 30.1, state changed from "secondary neg" to "secondary op"SMRP: Port 30.1, secondary router changed from 0.0 to 30.1SMRP: Port 30.1, state changed from "secondary op" to "primary neg"lists all the messages that can be generated with the debug smrp port command concerning the port table.
Related Command
debug smrp route
Use the debug smrp route EXEC command to display information about SMRP routing activity. The no form of this command disables debugging output.
[no] debug smrp route
Usage Guidelines
For more information, refer to the show smrp route command described in the Network Protocols Command Reference, Part 2.
Sample Display
Figure 2-241 shows sample debug smrp route output. In this example, poison notification is received from port 30.2. Poison notification is the receipt of a poisoned route on a nonparent port.
Figure 2-241 Sample Debug SMRP Route Output
Router# debug smrp routeSMRP: Route AT 20-20, poison notification from 30.2SMRP: Route AT 30-30, poison notification from 30.2lists all the messages that can be generated with the debug smrp route command concerning the routing table. In , the term route does not refer to an address but rather it is a network range.
Related Command
debug smrp transaction
Use the debug smrp transaction EXEC command to display information about SMRP transactions. The no form of this command disables debugging output.
[no] debug smrp transaction
Sample Display
Figure 2-242 shows sample debug smrp transaction output. In this example, a secondary node request is sent out to all routers on port 30.1.
Figure 2-242 Sample Debug SMRP Transaction Output
Router# debug smrp transactionSMRP: Transaction for port 30.1, secondary node request (seq 8435) sent to all routersSMRP: Transaction for port 30.1, secondary node request (seq 8435) sent to all routersSMRP: Transaction for port 30.1, secondary node request (seq 8435) sent to all routersSMRP: Transaction for port 30.1, secondary node request (seq 8435) sent to all routerslists all the messages that can be generated with the debug smrp route command.
Related Command
debug snmp packet
To display information about every SNMP packet sent or received by the router, use the debug snmp packet EXEC command. The no form of this command disables debugging output.
[no] debug snmp packet
Sample Display
shows sample output from the debug snmp packet command. In this example, the router receives a get-next request from the host at 172.16.63.17 and responds with the requested information.
Figure 2-243 Sample Debug SNMP Packet Output
Router# debug snmp packetSNMP: Packet received via UDP from 172.16.63.17 on Ethernet0SNMP: Get-next request, reqid 23584, errstat 0, erridx 0sysUpTime = NULL TYPE/VALUEsystem.1 = NULL TYPE/VALUEsystem.6 = NULL TYPE/VALUESNMP: Response, reqid 23584, errstat 0, erridx 0sysUpTime.0 = 2217027system.1.0 = Cisco Internetwork Operating System Softwaresystem.6.0 =SNMP: Packet sent via UDP to 172.16.63.17Based on the kind of packet sent or received, the output may vary. For get-bulk requests, a line similar to the following is displayed:
SNMP: Get-bulk request, reqid 23584, nonrptr 10, maxreps 20For traps, a line similar to the following is displayed:
SNMP: V1 Trap, ent 1.3.6.1.4.1.9.1.13, gentrap 3, spectrap 0describes significant fields in these displays.
debug sntp adjust
Use the debug sntp adjust EXEC command to display information about SNTP clock adjustments. The no form of this command disables debugging output.
[no] debug sntp adjust
Sample Displays
shows sample debug sntp adjust command output when an offset to the time reported by the configured NTP server is calculated. The offset indicates the difference between the router time and the actual time (as kept by the server) and is displayed in milliseconds. The clock time is then successfully changed to the accurate time by adding the offset to the current router time.
Figure 2-244 Sample Debug SNTP Adjust Output—Small Offset from Configured Server
Router# debug sntp adjustDelay calculated, offset 3.48Clock slewed.show sample debug sntp adjust command output when an offset to the time reported by a broadcast server is calculated. Since the packet is a broadcast packet, no transmission delay can be calculated. However, in this case, the offset is too large, so the clock is reset to the correct time.
Figure 2-245 Sample Debug SNTP Adjust Output—Large Offset from Broadcast Server
Router# debug sntp adjustNo delay calculated, offset 11.18Clock stepped.debug sntp packets
Use the debug sntp packets EXEC command to display information about SNTP packets sent and received. The no form of this command disables debugging output.
[no] debug sntp packets
Sample Displays
show sample debug sntp packets command output when a message is received.
Figure 2-246 Sample Debug SNTP Packets Output When a Packet Is Received
Router# debug sntp packetsReceived SNTP packet from 172.16.186.66, length 48leap 0, mode 1, version 3, stratum 4, ppoll 1024rtdel 00002B00, rtdsp 00003F18, refid AC101801 (172.16.24.1)ref B7237786.ABF9CDE5 (23:28:06.671 UTC Tue May 13 1997)org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)xmt B7237B5C.A7DE94F2 (23:44:28.655 UTC Tue May 13 1997)inp AF3BD529.810B66BC (00:19:53.504 UTC Mon Mar 1 1993)show sample debug sntp packets command output when a message is sent.
Figure 2-247 Sample Debug SNTP Packets Output When a Packet Is Sent
Router# debug sntp packetsSending SNTP packet to 172.16.25.1xmt AF3BD455.FBBE3E64 (00:16:21.983 UTC Mon Mar 1 1993)describes the significant fields shown in and .
debug sntp select
Use the debug sntp select EXEC command to display information about SNTP server selection. The no form of this command disables debugging output.
[no] debug sntp select
Sample Display
show sample debug sntp select command output. In this example, the router will synchronize its time to server at 172.16.186.66.
Figure 2-248 Sample Debug SNTP Select Output
Router# debug sntp selectSNTP: Selected 172.16.186.66debug source bridge
Use the debug source bridge EXEC command to display information about packets and frames transferred across a source-route bridge. The no form of this command disables debugging output.
[no] debug source bridge
Sample Displays
shows sample debug source bridge output for peer bridges using TCP as a transport mechanism. The remote source-route bridging (RSRB) network configuration has ring 2 and ring 1 bridged together through remote peer bridges. The remote peer bridges are connected via a serial line and use TCP as the transport mechanism.
Figure 2-249 Sample Debug Source Bridge Output—TCP Environment
Router# debug source bridgeRSRB: remote explorer to 5/131.108.250.1/1996 srn 2 [C840.0021.0050.0000]RSRB: Version/Ring XReq sent to peer 5/131.108.250.1/1996RSRB: Received version reply from 5/131.108.250.1/1996 (version 2)RSRB: DATA: 5/131.108.250.1/1996 Ring Xchg Rep, trn 2, vrn 5, off 18, len 10RSRB: added bridge 1, ring 1 for 5/131.108.240.1/1996RSRB: DATA: 5/131.108.250.1/1996 Explorer trn 2, vrn 5, off 18, len 69RSRB: DATA: 5/131.108.250.1/1996 Forward trn 2, vrn 5, off 0, len 92RSRB: DATA: forward Forward srn 2, br 1, vrn 5 to peer 5/131.108.250.1/1996Explanations for individual lines of output in follow.
The following line indicates that a remote explorer frame has been sent to IP address 131.108.250.1 and like all RSRB TCP connections, has been assigned port 1996. The bridge belongs to ring group 5. The explorer frame originated from ring number 2. The routing information field (RIF) descriptor has been generated by the local station and indicates that the frame was sent out via bridge 1 onto virtual ring 5.
RSRB: remote explorer to 5/131.108.250.1/1996 srn 2 [C840.0021.0050.0000]The following line indicates that a request for remote peer information has been sent to IP address 131.108.250.1, TCP port 1996. The bridge belongs to ring group 5.
RSRB: Version/Ring XReq sent to peer 5/131.108.250.1/1996The following line is the response to the version request previously sent. The response is sent from IP address 131.108.250.1, TCP port 1996. The bridge belongs to ring group 5.
RSRB: Received version reply from 5/131.108.250.1/1996 (version 2)The following line is the response to the ring request previously sent. The response is sent from IP address 131.108.250.1, TCP port 1996. The target ring number is 2, virtual ring number is 5, the offset is 18, and the length of the frame is 10 bytes.
RSRB: DATA: 5/131.108.250.1/1996 Ring Xchg Rep, trn 2, vrn 5, off 0, len 10The following line indicates that bridge 1 and ring 1 were added to the source-bridge table for IP address 131.108.250.1, TCP port 1996:
RSRB: added bridge 1, ring 1 for 5/131.108.250.1/1996The following line indicates that a packet containing an explorer frame came across virtual ring 5 from IP address 131.108.250.1, TCP port 1996. The packet is 69 bytes in length. This packet is received after the Ring Exchange information was received and updated on both sides.
RSRB: DATA: 5/131.108.250.1/1996 Explorer trn 2, vrn 5, off 18, len 69The following line indicates that a packet containing data came across virtual ring 5 from IP address 131.108.250.1 over TCP port 1996. The packet is being placed on the local target ring 2.The packet is 92 bytes in length.
RSRB: DATA: 5/131.108.250.1/1996 Forward trn 2, vrn 5, off 0, len 92The following line indicates that a packet containing data is being forwarded to the peer that has IP 131.108.250.1 address belonging to local ring 2 and bridge 1. The packet is forwarded via virtual ring 5. This packet is sent after the Ring Exchange information was received and updated on both sides.
RSRB: DATA: forward Forward srn 2, br 1, vrn 5 to peer 5/131.108.250.1/1996shows sample debug source bridge output for peer bridges using direct encapsulation as a transport mechanism. The RSRB network configuration has ring 1 and ring 2 bridged together through peer bridges. The peer bridges are connected via a serial line and use TCP as the transport mechanism.
Figure 2-250 Sample Debug Source Bridge Output—Direct Encapsulation Environment
Router# debug source bridgeRSRB: remote explorer to 5/Serial1 srn 1 [C840.0011.0050.0000]RSRB: Version/Ring XReq sent to peer 5/Serial1RSRB: Received version reply from 5/Serial1 (version 2)RSRB: IFin: 5/Serial1 Ring Xchg, Rep trn 0, vrn 5, off 0, len 10RSRB: added bridge 1, ring 1 for 5/Serial1Explanations for individual lines of output in follow.
The following line indicates that a remote explorer frame was sent to remote peer Serial1, which belongs to ring group 5. The explorer frame originated from ring number 1. The routing information field (RIF) descriptor 0011.0050 was generated by the local station and indicates that the frame was sent out via bridge 1 onto virtual ring 5.
RSRB: remote explorer to 5/Serial1 srn 1 [C840.0011.0050.0000]The following line indicates that a request for remote peer information was sent to Serial1. The bridge belongs to ring group 5.
RSRB: Version/Ring XReq sent to peer 5/Serial1The following line is the response to the version request previously sent. The response is sent from Serial 1. The bridge belongs to ring group 5 and the version is 2.
RSRB: Received version reply from 5/Serial1 (version 2)The following line is the response to the ring request previously sent. The response is sent from Serial1. The target ring number is 2, virtual ring number is 5, the offset is 0, and the length of the frame is 39 bytes.
RSRB: IFin: 5/Serial1 Ring Xchg Rep, trn 2, vrn 5, off 0, len 39The following line indicates that bridge 1 and ring 1 were added to the source-bridge table for Serial1:
RSRB: added bridge 1, ring 1 for 5/Serial1debug source error
Use the debug source error EXEC command to display source-route bridging errors. The no form of this command disables debugging output.
[no] debug source error
Usage Guidelines
The debug source error command displays some output also found in the debug source bridge output. Refer to the debug source bridge command for other possible output.
Sample Displays
In all of the following examples of debug source error command messages, the variable number is the Token Ring interface. For example, if the line of output starts with SRB1, the output relates to the Token Ring 1 interface. SRB indicates a source-route bridging message. RSRB indicates a remote source-route bridging message. SRTLB indicates a source-route translational bridging message.
In the following example, a packet of protocol protocol-type was dropped:
SRBnumber drop: Routed protocol protocol-typeIn the following example, an Address Resolution Protocol (ARP) packet was dropped. ARP is defined in RFC 826.
SRBnumber drop:TYPE_RFC826_ARPIn the following example, the current Cisco IOS version does not support Qualified Logical Link Control (QLLC). Reconfigure the router with an image that has the IBM feature set.
RSRB: QLLC not supported in version versionPlease reconfigure.In the following example, the packet was dropped because the outgoing interface of the router was down:
RSRB IF: outgoing interface not up, dropping packetIn the following example, the router received an out-of-sequence IP sequence number in a Fast Sequenced Transport (FST) packet. FST has no recovery for this problem like TCP encapsulation does.
RSRB FST: bad sequence number dropping.In the following example, the router was unable to locate the virtual interface:
RSRB: couldn't find virtual interfaceIn the following example, the peer router's TCP queue is full. TCPD indicates that this is a TCP debug.
RSRB TCPD: tcp queue full for peerIn the following example, the router was unable to send data to the peer router. A result of 1 indicates that the TCP queue is full. A result of -1 indicates that the RSRB peer is closed.
RSRB TCPD: tcp send failed for peer resultIn the following example, the Routing Information Identifier was not set in the explorer packet going forward. The packet will not support SRB, so it is dropped.
vrforward_explorer - RII not setIn the following example, a packet sent to a virtual bridge in the router did not include a routing information field (RIF) to tell the router which route to use:
RSRB: no RIF on packet sent to virtual bridgeThe following example indicates that the RIF did not contain any information or the length field was set to zero:
RSRB: RIF length of zero sent to virtual bridgeThe following message occurs when the local service access point (LSAP) is out of range. The variable lsap-out is the value, type is the type of RSRB peer, and state is the state of the RSRB peer.
VRP: rsrb_lsap_out = lsap-out, type = type, state = stateIn the following message, the router is unable to find another router with which to exchange bridge protocol data units (BPDU's). BPDU's are exchanged to set up the spanning tree and determine the forwarding path.
RSRB(span): BPDU's peer not foundRelated Commands
debug source bridge
debug source eventdebug source event
Use the debug source event EXEC command to display information on source-route bridging activity. The no form of this command disables debugging output.
[no] debug source event
Usage Guidelines
Some of the output from the debug source bridge and debug source error commands is identical to the output of this command.
Note
Sample Display
shows sample debug source event output.
Figure 2-251 Sample Debug Source Event Output
Router# debug source eventRSRB0: forward (srn 5 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9[0800.3201.00A1.0050]RSRB0: forward (srn 5 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9[0800.3201.00A1.0050]RSRB0: forward (srn 5 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9[0800.3201.00A1.0050]RSRB0: forward (srn 5 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9[0800.3201.00A1.0050]RSRB0: forward (srn 5 bn 1 trn 10), src: 8110.2222.33c1 dst: 1000.5a59.04f9[0800.3201.00A1.0050]describes significant fields shown in .
Examples of other debug source event messages follow.
In the following example messages, SRBnumber or RSRBnumber denotes a message associated with interface Token Ring number. A number of 99 denotes the remote side of the network.
SRBnumber: no path, s: source-MAC-addr d: dst-MAC-addr rif: rifIn the preceding example, a bridgeable packet came in on interface Token Ring number but there was nowhere to send it. This is most likely a configuration error. For example, an interface has source bridging turned on, but it is not connected to another source bridging interface or a ring group.
In the following example, a bridgeable packet has been forwarded from Token Ring number to the target ring. The two interfaces are directly linked.
SRBnumber: direct forward (srn ring bn bridge trn ring)In the following examples, a proxy explorer reply was not generated because there was no way to get to the address from this interface. The packet came from the node with the first address.
SRBnumber: br dropped proxy XID, address for address, wrong vring (rem)SRBnumber: br dropped proxy TEST, address for address, wrong vring (rem)SRBnumber: br dropped proxy XID, address for address, wrong vring (local)SRBnumber: br dropped proxy TEST, address for address, wrong vring (local)SRBnumber: br dropped proxy XID, address for address, no pathSRBnumber: br dropped proxy TEST, address for address, no pathIn the following example, an appropriate proxy explorer reply was generated on behalf of the second address. It is sent to the first address.
SRBnumber: br sent proxy XID, address for address[rif]SRBnumber: br sent proxy TEST, address for address[rif]The following example indicates that the broadcast bits were not set, or that the routing information indicator on the packet was not set:
SRBnumber: illegal explorer, s: source-MAC-addr d: dst-MAC-addr rif: rifThe following example indicates that the direction bit in the RIF field was set, or that an odd packet length was encountered. Such packets are dropped.
SRBnumber: bad explorer control, D set or oddThe following example indicates that a spanning explorer was dropped because the spanning option was not configured on the interface:
SRBnumber: span dropped, input off, s: source-MAC-addr d: dst-MAC-addr rif: rifThe following example indicates that a spanning explorer was dropped because it had traversed the ring previously:
SRBnumber: span violation, s: source-MAC-addr d: dst-MAC-addr rif: rifThe following example indicates that an explorer was dropped because the maximum hop count limit was reached on that interface:
SRBnumber: max hops reached - hop-cnt, s: source-MAC-addr d: dst-MAC-addr rif: rifThe following example indicates that the ring exchange request was sent to the indicated peer. This request tells the remote side which rings this node has and asks for a reply indicating which rings that side has.
RSRB: sent RingXreq to ring-group/ip-addrThe following example indicates that a message was sent to the remote peer. The label variable can be AHDR (active header), PHDR (passive header), HDR (normal header), or DATA (data exchange), and op can be Forward, Explorer, Ring Xchg, Req, Ring Xchg, Rep, Unknown Ring Group, Unknown Peer, or Unknown Target Ring.
RSRB: label: sent op to ring-group/ip-addrThe following example indicates that the remote bridge and ring pair were removed from or added to the local ring group table because the remote peer changed:
RSRB: removing bn bridge rn ring from ring-group/ip-addrRSRB: added bridge bridge, ring ring for ring-group/ip-addrThe following example shows miscellaneous remote peer connection establishment messages:
RSRB: peer ring-group/ip-addr closed [last state n]RSRB: passive open ip-addr(remote port) -> local portRSRB: CONN: opening peer ring-group/ip-addr, attempt nRSRB: CONN: Remote closed ring-group/ip-addr on openRSRB: CONN: peer ring-group/ip-addr open failed, reason[code]The following example shows that an explorer packet was propagated onto the local ring from the remote ring group:
RSRBn: sent local explorer, bridge bridge trn ring, [rif]The following messages indicate that the remote source-route bridging code found the packet was in error:
RSRBn: ring group ring-group not foundRSRBn: explorer rif [rif] not long enoughThe following example indicates that a buffer could not be obtained for a ring exchange packet (this is an internal error):
RSRB: couldn't get pak for ringXchgThe following example indicates that a ring exchange packet was received that had an incorrect length (this is an internal error):
RSRB: XCHG: req/reply badly formed, length pak-length, peer peer-idThe following example indicates that a ring entry was removed for the peer; the ring was possibly disconnected from the network, causing the remote router to send an update to all its peers.
RSRB: removing bridge bridge ring ring from peer-id ring-typeThe following example indicates that a ring entry was added for the specified peer; the ring was possibly added to the network, causing the other router to send an update to all its peers.
RSRB: added bridge bridge, ring ring for peer-idThe following example indicates that no memory was available to add a ring number to the ring group specified (this is an internal error):
RSRB: no memory for ring element ring-groupThe following example indicates that memory was corrupted for a connection block (this is an internal error):
RSRB: CONN: corrupt connection blockThe following example indicates that a connector process started, but that there was no packet to process (this is an internal error):
RSRB: CONN: warning, no initial packet, peer: ip-addr peer-pointerThe following example indicates that a packet was received with a version number different from the one present on the router:
RSRB: IF New version. local=local-version, remote=remote-version,pak-op-code peer-idThe following example indicates that a packet with a bad op code was received for a direct encapsulation peer (this is an internal error):
RSRB: IFin: bad op op-code (op code string) from peer-idThe following example indicates that the virtual ring header will not fit on the packet to be sent to the peer (this is an internal error):
RSRB: vrif_sender, hdr won't fitThe following example indicates that the specified peer is being opened. The retry count specifies the number of times the opening operation is attempted.
RSRB: CONN: opening peer peer-id retry-countThe following example indicates that the router, configured for FST encapsulation, received a version reply to the version request packet it had sent previously:
RSRB: FST Rcvd version reply from peer-id (version version-number)The following example indicates that the router, configured for FST encapsulation, sent a version request packet to the specified peer:
RSRB: FST Version Request. op = opcode, peer-idThe following example indicates that the router received a packet with a bad op code from the specified peer (this is an internal error):
RSRB: FSTin: bad op opcode (op code string) from peer-idThe following example indicates that the TCP connection between the router and the specified peer is being aborted:
RSRB: aborting ring-group/peer-id (vrtcpd_abort called)The following example indicates that an attempt to establish a TCP connection to a remote peer timed out:
RSRB: CONN: attempt timed outThe following example indicates that a packet was dropped because the ring group number in the packet did not correlate with the ring groups configured on the router:
RSRBnumber: ring group ring-group not founddebug span
Use the debug span EXEC command to display information on changes in the spanning-tree topology when debugging a transparent bridge. The no form of this command disables debugging output.
[no] debug span
Usage Guidelines
This command is useful for tracking and verifying that the spanning-tree protocol is operating correctly.
Sample Display—IEEE Spanning Tree
Sample debug span output for an IEEE BPDU packet follows:
Router# debug spanST: Ether4 0000000000000A080002A02D6700000000000A080002A02D6780010000140002000F00shows the preceding debug span output broken up by fields and labeled to aid documentation.
Figure 2-252 Sample Debug Span Output—IEEE BPDU Packet
describes significant fields shown in .
Sample Display—DEC Spanning Tree
Sample debug span output for a DEC BPDU packet follows:
Router# debug spanST: Ethernet4 E1190100000200000C01A2C90064008000000C0106CE0A01050F1E6Ashows the preceding debug span output broken up by fields and labeled to aid documentation.
Figure 2-253 Sample Debug Span Output
describes significant fields shown in .
debug sse
Use the debug sse EXEC command to display information for the silicon switching engine (SSE) processor. The no form of this command disables debugging output.
[no] debug sse
Usage Guidelines
By using the debug sse command, you can observe statistics and counters maintained by the SSE.
Sample Display
shows sample debug sse output.
Figure 2-254 Sample Debug SSE Output
Router# debug sseSSE: IP number of cache entries changed 273 274SSE: bridging enabledSSE: interface Ethernet0/0 icb 0x30 addr 0x29 status 0x21A040 protos 0x11SSE: interface Ethernet0/1 icb 0x33 addr 0x29 status 0x21A040 protos 0x11SSE: interface Ethernet0/2 icb 0x36 addr 0x29 status 0x21A040 protos 0x10SSE: interface Ethernet0/3 icb 0x39 addr 0x29 status 0x21A040 protos 0x11SSE: interface Ethernet0/4 icb 0x3C addr 0x29 status 0x21A040 protos 0x10SSE: interface Ethernet0/5 icb 0x3F addr 0x29 status 0x21A040 protos 0x11SSE: interface Hssi1/0 icb 0x48 addr 0x122 status 0x421E080 protos 0x11SSE: cache update took 316ms, elapsed 320msExplanations for representative lines of output in follow.
The following line indicates that the SSE cache is being updated due to a change in the IP fast switching cache:
SSE: IP number of cache entries changed 273 274The following line indicates that bridging functions were enabled on the SSE:
SSE: bridging enabledThe following lines indicate that the SSE is now loaded with information about the interfaces:
SSE: interface Ethernet0/0 icb 0x30 addr 0x29 status 0x21A040 protos 0x11SSE: interface Ethernet0/1 icb 0x33 addr 0x29 status 0x21A040 protos 0x11SSE: interface Ethernet0/2 icb 0x36 addr 0x29 status 0x21A040 protos 0x10SSE: interface Ethernet0/3 icb 0x39 addr 0x29 status 0x21A040 protos 0x11SSE: interface Ethernet0/4 icb 0x3C addr 0x29 status 0x21A040 protos 0x10SSE: interface Ethernet0/5 icb 0x3F addr 0x29 status 0x21A040 protos 0x11SSE: interface Hssi1/0 icb 0x48 addr 0x122 status 0x421E080 protos 0x11The following line indicates that the SSE took 316 ms of processor time to update the SSE cache. The value of 320 ms represents the total time elapsed while the cache updates were performed.
SSE: cache update took 316ms, elapsed 320msdebug standby
Use the debug standby EXEC command to display Hot Standby Protocol state changes. The no form of this command disables debugging output.
[no] debug standby
Usage Guidelines
The debug standby command displays Hot Standby Protocol state changes and debugging information regarding transmission and receipt of Hot Standby Protocol packets. Use this command to determine whether hot standby routers recognize one another and take the proper actions.
Sample Display
shows sample debug standby output.
Figure 2-255 Sample Debug Standby Output
Router# debug standbySB: Ethernet0 state Virgin -> ListenSB: Starting up hot standby processSB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB: Ethernet0 state Listen -> SpeakSB:Ethernet0 Hello out 192.168.72.20 Speak pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello out 192.168.72.20 Speak pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello out 192.168.72.20 Speak pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB: Ethernet0 state Speak -> StandbySB:Ethernet0 Hello out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Active pri 90 hel 3 hol 10 ip 192.168.72.29SB: Ethernet0 Coup out 192.168.72.20 Standby pri 100 hel 3 hol 10 ip 192.168.72.29SB: Ethernet0 state Standby -> ActiveSB:Ethernet0 Hello out 192.168.72.20 Active pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Speak pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello out 192.168.72.20 Active pri 100 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello in 192.168.72.21 Speak pri 90 hel 3 hol 10 ip 192.168.72.29SB:Ethernet0 Hello out 192.168.72.20 Active pri 100 hel 3 hol 10 ip 192.168.72.29describes significant fields shown in .
Explanations for representative lines of output in follow.
The following line indicates that the router is initiating the Hot Standby Protocol. The standby ip interface configuration command enables hot standby.
SB: Starting up hot standby processThe following line indicates that a state transition occurred on the interface:
SB: Ethernet0 state Listen -> Speakdebug stun packet
Use the debug stun packet EXEC command to display information on packets traveling through the serial tunnel (STUN) links. Use the no form of this command to disable debugging output.
[no] debug stun packet [group] [address]
Syntax Description
Usage Guidelines
Because using this command is processor intensive, it is best to use it after hours, rather than in a production environment. It is also best to turn this command on by itself, rather than use it in conjunction with other debug commands.
Sample Display
shows sample debug stun packet output.
Figure 2-256 Sample Debug STUN Packet Output
Explanations for individual lines of output from follow.
The following line describes an X1 type of packet:
STUN sdlc: 0:00:04 Serial3 NDI: (0C2/008) U: SNRM PF:1describes significant fields shown in this line of debug stun packet output.
The following line of output describes an X2 type of packet:
STUN sdlc: 0:00:00 Serial3 SDI: (0C2/008) S: RR PF:1 NR:000All the fields in the previous line of output match those for an X1 type of packet, except the last field, which is additional. NR:000 indicates a receive count of 0; the range for the receive count is 0 to 7.
The following line of output describes an X3 type of packet:
STUN sdlc: 0:00:00 Serial3 SDI: (0C2/008) S:I PF:1 NR:000 NS:000All fields in the previous line of output match those for an X2 type of packet, except the last field, which is additional. NS:000 indicates a send count of 0; the range for the send count is 0 to 7.
debug tacacs
Use the debug tacacs EXEC command to display information associated with the Terminal Access Controller Access Control System (TACACS). The no form of this command disables debugging output.
[no] debug tacacs
Usage Guidelines
TACACS is a distributed security system that secures networks against unauthorized access. Cisco supports TACACS under the Authentication, Authorization, and Accounting (AAA) security system.
Use the debug aaa authentication command to get a high-level view of login activity. When TACACS is used on the router, you can use the debug tacacs command for more detailed debugging information.
Sample Displays
shows part of the debug aaa authentication command output for a TACACS login attempt that was successful. The information indicates that TACACS+ is the authentication method used.
Figure 2-257 Sample Debug AAA Authentication Output—TACACS Login Attempt
Router# debug aaa authentication14:01:17: AAA/AUTHEN (567936829): Method=TACACS+14:01:17: TAC+: send AUTHEN/CONT packet14:01:17: TAC+ (567936829): received authen response status = PASS14:01:17: AAA/AUTHEN (567936829): status = PASSshows part of the debug tacacs command output for a TACACS login attempt that was successful as indicated by the status PASS.
Figure 2-258 Sample Debug TACACS Output—Successful Login Attempt
Router# debug tacacs14:00:09: TAC+: Opening TCP/IP connection to 192.168.60.15 using source 10.116.0.7914:00:09: TAC+: Sending TCP/IP packet number 383258052-1 to 192.168.60.15 (AUTHEN/START)14:00:09: TAC+: Receiving TCP/IP packet number 383258052-2 from 192.168.60.1514:00:09: TAC+ (383258052): received authen response status = GETUSER14:00:10: TAC+: send AUTHEN/CONT packet14:00:10: TAC+: Sending TCP/IP packet number 383258052-3 to 192.168.60.15 (AUTHEN/CONT)14:00:10: TAC+: Receiving TCP/IP packet number 383258052-4 from 192.168.60.1514:00:10: TAC+ (383258052): received authen response status = GETPASS14:00:14: TAC+: send AUTHEN/CONT packet14:00:14: TAC+: Sending TCP/IP packet number 383258052-5 to 192.168.60.15 (AUTHEN/CONT)14:00:14: TAC+: Receiving TCP/IP packet number 383258052-6 from 192.168.60.1514:00:14: TAC+ (383258052): received authen response status = PASS14:00:14: TAC+: Closing TCP/IP connection to 192.168.60.15shows part of the debug tacacs command output for a TACACS login attempt that was unsuccessful as indicated by the status FAIL.
Figure 2-259 Sample Debug TACACS Output—Failed Login Attempt
Router# debug tacacs13:53:35: TAC+: Opening TCP/IP connection to 192.168.60.15 using source192.48.0.7913:53:35: TAC+: Sending TCP/IP packet number 416942312-1 to 192.168.60.15(AUTHEN/START)13:53:35: TAC+: Receiving TCP/IP packet number 416942312-2 from 192.168.60.1513:53:35: TAC+ (416942312): received authen response status = GETUSER13:53:37: TAC+: send AUTHEN/CONT packet13:53:37: TAC+: Sending TCP/IP packet number 416942312-3 to 192.168.60.15(AUTHEN/CONT)13:53:37: TAC+: Receiving TCP/IP packet number 416942312-4 from 192.168.60.1513:53:37: TAC+ (416942312): received authen response status = GETPASS13:53:38: TAC+: send AUTHEN/CONT packet13:53:38: TAC+: Sending TCP/IP packet number 416942312-5 to 192.168.60.15(AUTHEN/CONT)13:53:38: TAC+: Receiving TCP/IP packet number 416942312-6 from 192.168.60.1513:53:38: TAC+ (416942312): received authen response status = FAIL13:53:40: TAC+: Closing TCP/IP connection to 192.168.60.15Related Commands
debug aaa accounting
debug aaa authenticationdebug tacacs events
Use the debug tacacs events EXEC command to display information from the TACACS+ helper process. The no form of this command disables debugging output.
[no] debug tacacs events
Usage Guidelines
Use the debug tacacs events command only in response to a request from service personnel to collect data when a problem has been reported.
CautionUse the debug tacacs events command with caution because it can generate a significant amount of output.
The TACACS protocol is used on routers to assist in managing user accounts. TACACS+ enhances the TACACS functionality by adding security features and cleanly separating out the authentication, authorization, and accounting (AAA) functionality.
Sample Display
shows sample debug tacacs events output. In this example, the opening and closing of a TCP connection to a TACACS+ server are shown, as well as the bytes read and written over the connection and the connection's TCP status.
Figure 2-260 Sample Debug TACACS Events Output
Router# debug tacacs events%LINK-3-UPDOWN: Interface Async2, changed state to up00:03:16: TAC+: Opening TCP/IP to 192.168.58.104/1049 timeout=1500:03:16: TAC+: Opened TCP/IP handle 0x48A87C to 192.168.58.104/104900:03:16: TAC+: periodic timer started00:03:16: TAC+: 192.168.58.104 req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (ESTAB)expire=14 AUTHEN/START/SENDAUTH/CHAP queued00:03:17: TAC+: 192.168.58.104 ESTAB 3BD868 wrote 46 of 46 bytes00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=12 wanted=12 alloc=12 got=1200:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=61 wanted=61 alloc=61 got=4900:03:22: TAC+: 192.168.58.104 received 61 byte reply for 3BD86800:03:22: TAC+: req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (CLOSEWAIT) expire=9AUTHEN/START/SENDAUTH/CHAP processed00:03:22: TAC+: periodic timer stopped (queue empty)00:03:22: TAC+: Closing TCP/IP 0x48A87C connection to 192.168.58.104/104900:03:22: TAC+: Opening TCP/IP to 192.168.58.104/1049 timeout=1500:03:22: TAC+: Opened TCP/IP handle 0x489F08 to 192.168.58.104/104900:03:22: TAC+: periodic timer started00:03:22: TAC+: 192.168.58.104 req=3BD868 id=299214410 ver=192 handle=0x489F08 (ESTAB)expire=14 AUTHEN/START/SENDPASS/CHAP queued00:03:23: TAC+: 192.168.58.104 ESTAB 3BD868 wrote 41 of 41 bytes00:03:23: TAC+: 192.168.58.104 CLOSEWAIT read=12 wanted=12 alloc=12 got=1200:03:23: TAC+: 192.168.58.104 CLOSEWAIT read=21 wanted=21 alloc=21 got=900:03:23: TAC+: 192.168.58.104 received 21 byte reply for 3BD86800:03:23: TAC+: req=3BD868 id=299214410 ver=192 handle=0x489F08 (CLOSEWAIT) expire=13AUTHEN/START/SENDPASS/CHAP processed00:03:23: TAC+: periodic timer stopped (queue empty)The TACACAS messages are intended to be self-explanatory or for consumption by service personnel only. However, the following messages shown in are briefly explained in the following text.
The following message indicates that a TCP open request to host 192.168.58.104 on port 1049 will time out in 15 seconds if it gets no response:
00:03:16: TAC+: Opening TCP/IP to 192.168.58.104/1049 timeout=15The following message indicates a successful open operation and provides the address of the internal TCP "handle" for this connection:
00:03:16: TAC+: Opened TCP/IP handle 0x48A87C to 192.168.58.104/1049The following message indicates that a TACACS+ request has been queued:
00:03:16: TAC+: 192.168.58.104 req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (ESTAB) expire=14 AUTHEN/START/SENDAUTH/CHAP queuedThe message identifies the following:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The following message indicates that all 46 bytes were written to address 192.168.58.104 for request 3BD868:
00:03:17: TAC+: 192.168.58.104 ESTAB 3BD868 wrote 46 of 46 bytesThe following message indicates that 12 bytes were read in reply to the request.:
00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=12 wanted=12 alloc=12 got=12The following message indicates that 49 more bytes were read, making a total of 61 bytes in all, which is all that was expected:
00:03:22: TAC+: 192.168.58.104 CLOSEWAIT read=61 wanted=61 alloc=61 got=49The following message indicates that a complete 61-byte reply has been read and processed for request 3BD868:
00:03:22: TAC+: 192.168.58.104 received 61 byte reply for 3BD868 00:03:22: TAC+: req=3BD868 id=-1242409656 ver=193 handle=0x48A87C (CLOSEWAIT) expire=9 AUTHEN/START/SENDAUTH/CHAP processedThe following message indicates that the TACACS+ server helper process switched itself off when it had no more work to do:
00:03:22: TAC+: periodic timer stopped (queue empty)Related Commands
debug aaa accounting
debug aaa authentication
debug aaa authorization
debug tacacsdebug tarp events
Use the debug tarp events EXEC command to display information on Target Identifier Address Resolution Protocol (TARP) activity. The no form of this command disables debugging output.
[no] debug tarp events
Usage Guidelines
For complete information on the TARP process, use the debug tarp packets command along with the debug tarp events command. Events are usually related to error conditions.
Sample Display
Figure 2-261 shows sample debug tarp events and debug tarp packets output after the tarp resolve command was used to determine the NSAP address for the TARP target identifier (TID) artemis.
Figure 2-261 Sample Debug TARP Events Output
Router# debug tarp eventsRouter# debug tarp packetsRouter# tarp resolve artemisType escape sequence to abort.Sending TARP type 1 PDU, timeout 15 seconds...NET corresponding to TID artemis is 49.0001.1111.1111.1111.00*Mar 1 00:43:59: TARP-PA: Propagated TARP packet, type 1, out on Ethernet0*Mar 1 00:43:59: Lft = 100, Seq = 11, Prot type = 0xFE, URC = TRUE*Mar 1 00:43:59: Ttid len = 7, Stid len = 8, Prot addr len = 10*Mar 1 00:43:59: Destination NSAP: 49.0001.1111.1111.1111.00*Mar 1 00:43:59: Originator's NSAP: 49.0001.3333.3333.3333.00*Mar 1 00:43:59: Target TID: artemis*Mar 1 00:43:59: Originator's TID: cerd*Mar 1 00:43:59: TARP-EV: Packet not propagated to 49.0001.4444.4444.4444.00 oninterface Ethernet0 (adjacency is not in UP state)*Mar 1 00:43:59: TARP-EV: No route found for TARP static adjacency55.0001.0001.1111.1111.1111.1111.1111.1111.1111.00 - packet not sent*Mar 1 00:43:59: TARP-PA: Received TARP type 3 PDU on interface Ethernet0*Mar 1 00:43:59: Lft = 100, Seq = 5, Prot type = 0xFE, URC = TRUE*Mar 1 00:43:59: Ttid len = 0, Stid len = 7, Prot addr len = 10*Mar 1 00:43:59: Packet sent/propagated by 49.0001.1111.1111.1111.af*Mar 1 00:43:59: Originator's NSAP: 49.0001.1111.1111.1111.00*Mar 1 00:43:59: Originator's TID: artemis*Mar 1 00:43:59: TARP-PA: Created new DYNAMIC cache entry for artemisdescribes the fields shown in .
Related Command
debug tarp packets
Use the debug tarp packets EXEC command to display general information on TARP packets received, generated, and propagated on the router. The no form of this command disables debugging output.
[no] debug tarp packets
Usage Guidelines
For complete information on the TARP process, use the debug tarp events command along with the debug tarp packet command. Events are usually related to error conditions.
Sample Display
shows sample debug tarp packet output after the tarp query command was used to determine the TID for the NSAP address 49.0001.3333.3333.3333.00.
Figure 2-262 Sample Debug TARP Packets Output
Router# debug tarp packetsRouter# debug tarp eventsRouter# tarp query 49.0001.3333.3333.3333.00Type escape sequence to abort.Sending TARP type 5 PDU, timeout 40 seconds...TID corresponding to NET 49.0001.3333.3333.3333.00 is cerdiwen*Mar 2 03:10:11: TARP-PA: Originated TARP packet, type 5, to destination 49.0001.3333.3333.3333.00*Mar 2 03:10:11: TARP-PA: Received TARP type 3 PDU on interface Ethernet0*Mar 2 03:10:11: Lft = 100, Seq = 2, Prot type = 0xFE, URC = TRUE*Mar 2 03:10:11: Ttid len = 0, Stid len = 8, Prot addr len = 10*Mar 2 03:10:11: Packet sent/propagated by 49.0001.3333.3333.3333.af*Mar 2 03:10:11: Originator's NSAP: 49.0001.3333.3333.3333.00*Mar 2 03:10:11: Originator's TID: cerdiwen*Mar 2 03:10:11: TARP-PA: Created new DYNAMIC cache entry for cerdiwendescribes the fields shown in the display.
Related Command
debug tdm
Use the debug tdm EXEC command to display time division multiplexer (TDM) bus connection information each time a connection is made on the Cisco AS5200 access server. Use the no form of this command to disable debug output.
[no] debug tdm
Usage Guidelines
Use the debug tdm command if you are losing channel data between the dual T1 Primary Rate Interfaces (PRI) and any termination points, such as an Ethernet or modem point.
This command displays the TDM bus connection information for each TDM device installed in the access server. One TDM device exists on the PRI card, on the motherboard, and on each modem card. Expect up to 256 TDM connections to be displayed on your terminal when this command is enabled.
Sample Display
shows sample debug tdm output.
Figure 2-263 Sample Debug TDM Output
AS5200# debug tdmdialtone connection requested.TDM(reg: 0x2138100): Close connection to STo7, channel 1TDM(reg: 0x2138100): Connect STi3, channel 1 to STo7, channel 1debug tftp
Use the debug tftp EXEC command to display Trivial File Transfer Protocol (TFTP) debugging information when encountering problems netbooting or using the copy tftp running-config or copy running-config tftp commands. The no form of this command disables debugging output.
[no] debug tftp
Sample Display
shows sample debug tftp output from the EXEC command copy running-config tftp.
Figure 2-264 Sample Debug TFTP Output
Router# debug tftpTFTP: msclock 0x292B4; Sending write request (retry 0), socket_id 0x301DA8TFTP: msclock 0x2A63C; Sending write request (retry 1), socket_id 0x301DA8TFTP: msclock 0x2A6DC; Received ACK for block 0, socket_id 0x301DA8TFTP: msclock 0x2A6DC; Received ACK for block 0, socket_id 0x301DA8TFTP: msclock 0x2A6DC; Sending block 1 (retry 0), socket_id 0x301DA8TFTP: msclock 0x2A6E4; Received ACK for block 1, socket_id 0x301DA8describes significant fields shown in the first line of output from .
debug token ring
Use the debug token ring EXEC command to display messages about Token Ring interface activity. The no form of this command disables debugging output.
[no] debug token ring
Usage Guidelines
This command reports several lines of information for each packet sent or received and is intended for low traffic, detailed debugging.
The Token Ring interface records provide information regarding the current state of the ring. These messages are only displayed when the debug token events command is enabled.
The debug token ring command invokes verbose Token Ring hardware debugging. This includes detailed displays as traffic arrives and departs the unit.
Note
Sample Display
shows sample debug token ring output.
Figure 2-265 Sample Debug Token Ring Output
Router# debug token ringTR0: Interface is alive, phys. addr 5000.1234.5678TR0: in: MAC: acfc: 0x1105 Dst: c000.ffff.ffff Src: 5000.1234.5678 bf: 0x45TR0: in: riflen 0, rd_offset 0, llc_offset 40TR0: out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00TR0: out: LLC: AAAA0300 00009000 00000100 AAC00000 00000802 50001234 ln: 28TR0: in: MAC: acfc: 0x1140 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x09TR0: in: LLC: AAAA0300 00009000 00000100 AAC0B24A 4B4A6768 74732072 ln: 28TR0: in: riflen 0, rd_offset 0, llc_offset 14TR0: out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00TR0: out: LLC: AAAA0300 00009000 00000100 D1D00000 FE11E636 96884006 ln: 28TR0: in: MAC: acfc: 0x1140 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x09TR0: in: LLC: AAAA0300 00009000 00000100 D1D0774C 4DC2078B 3D000160 ln: 28TR0: in: riflen 0, rd_offset 0, llc_offset 14TR0: out: MAC: acfc: 0x0040 Dst: 5000.1234.5678 Src: 5000.1234.5678 bf: 0x00TR0: out: LLC: AAAA0300 00009000 00000100 F8E00000 FE11E636 96884006 ln: 28describes significant fields shown in the second line of output from .
describes significant fields shown in the third line of output from .
describes significant fields shown in the fifth line of output from .
