Table Of Contents
debug frame-relay informationelements
debug frame-relay networklayerinterface
debug clns esis events
Use the debug clns esis events EXEC command to display uncommon End System-to-Intermediate System (ES-IS) events, including previously unknown neighbors, neighbors that have aged out, and neighbors that have changed roles (ES to IS, for example). The no form of this command disables debugging output.
[no] debug clns esis events
Sample Display
shows sample debug clns esis events output.
Figure 2-47 Sample Debug CLNS ESIS Events Output
Router# debug clns esis eventsES-IS: ISH from aa00.0400.2c05 (Ethernet1), HT 30ES-IS: ESH from aa00.0400.9105 (Ethernet1), HT 150ES-IS: ISH sent to All ESs (Ethernet1): NET 49.0001.AA00.0400.6904.00, HT 299, HLEN 20Explanations for individual lines of output from follow.
The following line indicates that the router received a hello packet (ISH) from the IS at MAC address aa00.0400.2c05 on the Ethernet1 interface. The hold time (or number of seconds to consider this packet valid before deleting it) for this packet is 30 seconds.
ES-IS: ISH from aa00.0400.2c05 (Ethernet1), HT 30The following line indicates that the router received a hello packet (ESH) from the ES at MAC address aa00.0400.9105 on the Ethernet1 interface. The hold time is 150 seconds.
ES-IS: ESH from aa00.0400.9105 (Ethernet1), HT 150The following line indicates that the router sent an IS hello packet on the Ethernet0 interface to all ESs on the network. The network entity title (NET) address of the router is 49.0001.0400.AA00.6904.00; the hold time for this packet is 299 seconds; and the header length of this packet is 20 bytes.
ES-IS: ISH sent to All ESs (Ethernet1): NET 49.0001.AA00.0400.6904.00, HT 299, HLEN 20debug clns esis packets
Use the debug clns esis packets EXEC command to enable display information on End System-to-Intermediate System (ES-IS) packets that the router has received and sent. The no form of this command disables debugging output.
[no] debug clns esis packets
Sample Display
shows sample debug clns esis packets output.
Figure 2-48 Sample Debug CLNS ESIS Packets Output
Router# debug clns esis packetsES-IS: ISH sent to All ESs (Ethernet0): NET47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 33ES-IS: ISH sent to All ESs (Ethernet1): NET47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34ES-IS: ISH from aa00.0400.6408 (Ethernet0), HT 299ES-IS: ISH sent to All ESs (Tunnel0): NET47.0005.80ff.ef00.0000.0001.5940.1600.O906.4023.00, HT 299, HLEN 34IS-IS: ESH from 0000.0c00.bda8 (Ethernet0), HT 300Explanations for individual lines of output from follow.
The following line indicates that the router has sent an IS hello packet on Ethernet0 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length.
ES-IS: ISH sent to All ESs (Ethernet0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 33The following line indicates that the router has sent an IS hello packet on Ethernet1 to all ESs on the network. This hello packet indicates that the network entity title (NET) of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length.
ES-IS: ISH sent to All ESs (Ethernet1): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34The following line indicates that the router received a hello packet on Ethernet0 from an intermediate system, aa00.0400.6408. The hold time for this packet is 299 seconds.
ES-IS: ISH from aa00.0400.6408 (Ethernet0), HT 299The following line indicates that the router has sent an IS hello packet on Tunnel0 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length.
ES-IS: ISH sent to All ESs (Tunnel0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34The following line indicates that on Ethernet0, the router received a hello packet from an end system with an SNPA of 0000.0c00.bda8. The hold time for this packet is 300 seconds.
IS-IS: ESH from 0000.0c00.bda8 (Ethernet0), HT 300debug clns events
Use the debug clns events EXEC command to display CLNS events that are occurring at the router. The no form of this command disables debugging output.
[no] debug clns events
Sample Display
shows sample debug clns events output.
Figure 2-49 Sample Debug CLNS Events Output
Router# debug clns eventsCLNS: Echo PDU received on Ethernet3 from 39.0001.2222.2222.2222.00!CLNS: Sending from 39.0001.3333.3333.3333.00 to 39.0001.2222.2222.2222.00via 2222.2222.2222 (Ethernet3 0000.0c00.3a18)CLNS: Forwarding packet size 117from 39.0001.2222.2222.2222.00to 49.0002.0001.AAAA.AAAA.AAAA.00via 49.0002 (Ethernet3 0000.0c00.b5a3)CLNS: RD Sent on Ethernet3 to 39.0001.2222.2222.2222.00 @ 0000.0c00.3a18,redirecting 49.0002.0001.AAAA.AAAA.AAAA.00 to 0000.0c00.b5a3Explanations for individual lines of output from follow.
The following line indicates that the router received an echo PDU on Ethernet3 from source network service access point (NSAP) 39.0001.2222.2222.2222.00. The exclamation point at the end of the line has no significance.
CLNS: Echo PDU received on Ethernet3 from 39.0001.2222.2222.2222.00!The following lines indicate that the router at source NSAP 39.0001.3333.3333.3333.00 is sending a CLNS echo packet to destination NSAP 39.0001.2222.2222.2222.00 via an IS with system ID 2222.2222.2222. The packet is being sent on the Ethernet3 interface, with a MAC address of 0000.0c00.3a18.
CLNS: Sending from 39.0001.3333.3333.3333.00 to 39.0001.2222.2222.2222.00via 2222.2222.2222 (Ethernet3 0000.0c00.3a18)The following lines indicate that a CLNS echo packet 117 bytes in size is being sent from source NSAP 39.0001.2222.2222.2222.00 to destination NSAP 49.0002.0001.AAAA.AAAA.AAAA.00 via the router at NSAP 49.0002. The packet is being forwarded on the Ethernet3 interface, with a MAC address of 0000.0c00.b5a3.
CLNS: Forwarding packet size 117from 39.0001.2222.2222.2222.00to 49.0002.0001.AAAA.AAAA.AAAA.00via 49.0002 (Ethernet3 0000.0c00.b5a3)The following lines indicate that the router sent a redirect packet on the Ethernet3 interface to the NSAP 39.0001.2222.2222.2222.00 at MAC address 0000.0c00.3a18 to indicate that NSAP 49.0002.0001.AAAA.AAAA.AAAA.00 can be reached at MAC address 0000.0c00.b5a3.
CLNS: RD Sent on Ethernet3 to 39.0001.2222.2222.2222.00 @ 0000.0c00.3a18,redirecting 49.0002.0001.AAAA.AAAA.AAAA.00 to 0000.0c00.b5a3debug clns igrp packets
Use the debug clns igrp packets EXEC command to display debugging information on all ISO-IGRP routing activity. The no form of this command disables debugging output.
[no] debug clns igrp packets
Sample Display
shows sample debug clns igrp packets output.
Figure 2-50 Sample Debug CLNS IGRP Packets Output
Router# debug clns igrp packetsISO-IGRP: Hello sent on Ethernet3 for DOMAIN_green1ISO-IGRP: Received hello from 39.0001.3333.3333.3333.00, (Ethernet3), ht 51ISO-IGRP: Originating level 1 periodic updateISO-IGRP: Advertise dest: 2222.2222.2222ISO-IGRP: Sending update on interface: Ethernet3ISO-IGRP: Originating level 2 periodic updateISO-IGRP: Advertise dest: 0001ISO-IGRP: Sending update on interface: Ethernet3ISO-IGRP: Received update from 3333.3333.3333 (Ethernet3)ISO-IGRP: Opcode: areaISO-IGRP: Received level 2 adv for 0001 metric 1100ISO-IGRP: Opcode: stationISO-IGRP: Received level 1 adv for 3333.3333.3333 metric 1100Explanations for individual lines of output from follow.
The following line indicates that the router is sending a hello packet to advertise its existence in the DOMAIN_green1 domain:
ISO-IGRP: Hello sent on Ethernet3 for DOMAIN_green1The following line indicates that the router received a hello packet from a certain network service access point (NSAP) on the Ethernet3 interface. The hold time for this information is 51 seconds.
ISO-IGRP: Received hello from 39.0001.3333.3333.3333.00, (Ethernet3), ht 51The following lines indicate that the router is generating a Level 1 update to advertise reachability to destination NSAP 2222.2222.2222 and that it is sending that update to all systems that can be reached through the Ethernet3 interface:
ISO-IGRP: Originating level 1 periodic updateISO-IGRP: Advertise dest: 2222.2222.2222ISO-IGRP: Sending update on interface: Ethernet3The following lines indicate that the router is generating a Level 2 update to advertise reachability to destination area 1 and that it is sending that update to all systems that can be reached through the Ethernet3 interface:
ISO-IGRP: Originating level 2 periodic updateISO-IGRP: Advertise dest: 0001ISO-IGRP: Sending update on interface: Ethernet3The following lines indicate that the router received an update from NSAP 3333.3333.3333 on Ethernet3. This update indicated the area the router at this NSAP could reach.
ISO-IGRP: Received update from 3333.3333.3333 (Ethernet3)ISO-IGRP: Opcode: areaThe following lines indicate that the router received an update advertising that the source of that update can reach area 1 with a metric of 1100. A station opcode indicates that the update included system addresses.
ISO-IGRP: Received level 2 adv for 0001 metric 1100ISO-IGRP: Opcode: stationdebug clns packet
Use the debug clns packet EXEC command to display information about packet receipt and forwarding to the next interface. The no form of this command disables debugging output.
[no] debug clns packet
Sample Display
shows sample debug clns packet output.
Figure 2-51 Sample Debug CLNS Packet Output
Router# debug clns packetCLNS: Forwarding packet size 157from 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.00 STUPI-RBSto 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)CLNS: Echo PDU received on Ethernet0 from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00!CLNS: Sending from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00 to47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)Explanations for individual lines of output from follow.
In the following lines, the first line indicates that a Connectionless Network Service (CLNS) packet of size 157 bytes is being forwarded. The second line indicates the network service access point (NSAP) and system name of the source of the packet. The third line indicates the destination NSAP for this packet. The fourth line indicates the next-hop system ID, interface, and SNPA of the router interface used to forward this packet.
CLNS: Forwarding packet size 157from 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.00 STUPI-RBSto 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)In the following lines, the first line indicates that the router received an Echo PDU on the specified interface from the source NSAP. The second line indicates which source NSAP is used to send a CLNS packet to the destination NSAP, as shown on the third line. The fourth line indicates the next-hop system ID, interface, and SNPA of the router interface used to forward this packet.
CLNS: Echo PDU received on Ethernet0 from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00!CLNS: Sending from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00 to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)debug clns routing
Use the debug clns routing EXEC command to display debugging information for all Connectionless Network Service (CLNS) routing cache updates and activities involving the CLNS routing table. The no form of this command disables debugging output.
[no] debug clns routing
Sample Display
shows sample debug clns routing output.
Figure 2-52 Sample Debug CLNS Routing Output
Router# debug clns routingCLNS-RT: cache increment:17CLNS-RT: Add 47.0023.0001.0000.0000.0003.0001 to prefix table, next hop 1920.3614.3002CLNS-RT: Aging cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06CLNS-RT: Deleting cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06Explanations for individual lines of output from follow.
The following line indicates that a change to the routing table has resulted in an addition to the fast-switching cache:
CLNS-RT: cache increment:17The following line indicates that a specific prefix route was added to the routing table, and indicates the next-hop system ID to that prefix route. In other words, when the router receives a packet with the prefix 47.0023.0001.0000.0000.0003.0001 in that packet's destination address, it forwards that packet to the router with the MAC address 1920.3614.3002.
CLNS-RT: Add 47.0023.0001.0000.0000.0003.0001 to prefix table, next hop 1920.3614.3002The following lines indicate that the fast-switching cache entry for a certain network service access point (NSAP) has been invalidated and then deleted:
CLNS-RT: Aging cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06CLNS-RT: Deleting cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06debug cls message
Use the debug cls message EXEC command to display information about Cisco Link Services (CLS) messages. The no form of this command disables debugging output.
[no] debug cls message
Usage Guidelines
The debug cls message command displays the primitives (state), selector, header length, and data size.
Sample Display
shows sample debug cls message output. For example, CLS-->DLU indicates the direction of the flow that is described by the status. From CLS to DLU, a request was established to the connection end point. The header length is 48 bytes, and the data size is 104 bytes.
Figure 2-53 Sample Debug CLS Message Output
Router# debug cls message(FRAS Daemon:CLS-->DLU):ID_STN.Ind to uSAP: 0x607044C4 sel: LLC hlen: 40, dlen: 54(FRAS Daemon:CLS-->DLU):ID_STN.Ind to uSAP: 0x6071B054 sel: LLC hlen: 40, dlen: 46(FRAS Daemon:DLU-->SAP):REQ_OPNSTN.Req to pSAP: 0x608021F4 sel: LLC hlen: 48, dlen: 104(FRAS Daemon:CLS-->DLU):REQ_OPNSTN.Cfm(NO_REMOTE_STN) to uCEP: 0x607FFE84 sel: LLC hlen: 48, dlen: 104The status possibilities include the following: enabled, disabled, request open station, open station, close station, activate SA, deactivate SAP, XID, XID station, connect station, signal station, connect, disconnect, connected, data, flow, unnumbered data, modify SAP, test, activate ring, deactivate ring, test station, and unnumbered data station.
Related Commands
debug fras error
debug fras message
debug fras statedebug cls vdlc
Use the debug cls vdlc EXEC command to display information about Cisco Link Services (CLS) Virtual Data Link Control (VDLC). The no form of this command disables debugging output.
[no] debug cls vdlc
Usage Guidelines
CautionUse the debug cls vdlc command with caution because it can generate a significant amount of output.
The debug cls message command displays primitive state transitions, selector, and source and destination media access control (MAC) and service access points (SAPs).
Also use the show cls command to display additional information on CLS VDLC.
Sample Displays
The following messages are sample debug cls vdlc output. In the following scenario, the SNA service point—also called native service point (NSP)—is setting up two connections through VDLC and data link switching (DLSw): one from NSP to VDLC and one from DLSw to VDLC. VDLC's task is to join the two.
The NSP initiates a connection from 4000.05d2.0001 as follows:
VDLC: Req Open Stn Req PSap 0x7ACE00, port 0x79DF98 4000.05d2.0001(0C)->4000.1060.1000(04)In the next message, VDLC sends a test station request to DLSw for destination address 4000.1060.1000.
VDLC: Send UFrame E3: 4000.05d2.0001(0C)->4000.1060.1000(00)In the next two messages, DLSw replies with test station response, and NSP goes to a half-open state. NSP is waiting for the DLSw connection to VDLC.
VDLC: Sap to Sap TEST_STN_RSP VSap 0x7B68C0 4000.1060.1000(00)->4000.05d2.0001(0C)VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPENING->VDLC_HALF_OPENThe NSP sends an exchange identification (XID) and changes state as follows:
VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_HALF_OPEN->VDLC_XID_RSP_PENDINGVDLC: CEP to SAP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04) via bridging SAP (DLSw)In the next several messages, DLSw initiates its connection, which matches the half-open connection with NSP.
VDLC: Req Open Stn Req PSap 0x7B68C0, port 0x7992A0 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: two-way connection establishedVDLC: 4000.1060.1000(04)->4000.05d2.0001(0C): VDLC_IDLE->VDLC_OPENIn the following messages, DLSw sends an XID response, and NSP's connection goes from the state XID Response Pending to Open. The XID exchange follows:
VDLC: CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPENVDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDINGVDLC: CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04)VDLC: CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPENVDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDINGVDLC: CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04)VDLC: CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPENVDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDINGVDLC: CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04)VDLC: CEP to CEP ID_RSP 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPENVDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_OPEN->VDLC_XID_RSP_PENDINGVDLC: CEP to CEP ID_REQ 4000.05d2.0001(0C)->4000.1060.1000(04)When DLSw is ready to connect, the front-end processor (FEP) sends a set asynchronous balanced mode extended (SABME) command as follows:
VDLC: CEP to CEP CONNECT_REQ 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: 4000.05d2.0001(0C)->4000.1060.1000(04): VDLC_XID_RSP_PENDING->VDLC_OPENIn the following messages, NSP accepts the connection and sends an unnumbered acknowledgment (UA) to the FEP:
VDLC: CEP to CEP CONNECT_RSP 4000.05d2.0001(0C)->4000.1060.1000(04)VDLC: FlowReq QUENCH OFF 4000.1060.1000(04)->4000.05d2.0001(0C)The following messages show the data flow:
VDLC: DATA 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: DATA 4000.05d2.0001(0C)->4000.1060.1000(04)...VDLC: DATA 4000.1060.1000(04)->4000.05d2.0001(0C)VDLC: DATA 4000.05d2.0001(0C)->4000.1060.1000(04)Related Commands
debug cls message
debug dlsw core messagedebug compress
Use the debug compress EXEC command to display compression information. The no form of this command disables debugging output.
[no] debug compress
Sample Display
shows sample debug compress output.
Figure 2-54 Sample Debug Compress Output
Router# debug compressDECOMPRESS xmt_paks 5 rcv_sync 5COMPRESS xmt_paks 10 version 1COMPRESS xmt_paks 11 version 1DECOMPRESS xmt_paks 6 rcv_sync 6COMPRESS xmt_paks 12 version 1COMPRESS xmt_paks 13 version 1DECOMPRESS xmt_paks 7 rcv_sync 7COMPRESS xmt_paks 14 version 1COMPRESS xmt_paks 15 version 1describes significant debug compress output fields.
debug confmodem
Use the debug confmodem EXEC command to display information associated with the discovery and configuration of the modem attached to the router. The no form of this command disables debugging output.
[no] debug confmodem
Usage Guidelines
The debug confmodem command is used in debugging configurations that use the modem autoconfig command.
Sample Display
shows sample debug confmodem output. In the first three lines, the router is searching for a speed at which it can communicate with the modem. The remaining lines show the actual sending of the modem command.
Figure 2-55 Sample Debug Configuration Modem Output
Router# debug confmodemTTY4:detection speed(115200) response ------TTY4:detection speed(57600) response ------TTY4:detection speed(38400) response ---OK---TTY4:Modem command: --AT&F&C1&D2S180=3S190=1S0=1--TTY4: Modem configuration suceeededTTY4: Done with modem configurationdebug cpp event
Use the debug cpp event EXEC command to display general Combinet Proprietary Protocol (CPP) events. The no form of this command disables debugging output.
[no] debug cpp event
Usage Guidelines
The CPP protocol allows a router to engage in negotiation over an ISDN B channel to establish connections with a Combinet bridge.
The debug cpp event command displays events such as CPP sequencing, group creation, and keepalives.
Sample Displays
One or more of the messages shown in appear when you use the debug cpp event command. Each message begins with the short name of the interface the event occurred on (for example, SERIAL0:1 or BRI0:1) and might contain one or more packet sequence numbers or remote site names.
Related Commands
debug cpp negotiation
debug cpp packetdebug cpp negotiation
Use the debug cpp negotiation EXEC command to display Combinet Proprietary Protocol (CPP) negotiation events. The no form of this command disables debugging output.
[no] debug cpp negotiation
Usage Guidelines
The CPP protocol allows a router to engage in negotiation over an ISDN B channel to establish connections with a Combinet bridge.
The debug cpp negotiation command displays events such as the type of packet and packet size being sent.
Sample Display
shows sample debug cpp negotiation output. In this example, a sample connection is shown.
Figure 2-56 Sample Debug CPP Negotiation Output
Router# debug cpp negotiation%LINK-3-UPDOWN: Interface BRI0: B-Channel 2, changed state to down%LINK-3-UPDOWN: Interface BRI0, changed state to up%SYS-5-CONFIG_I: Configured from console by console%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to upBR0:1:(I) NEG packet - len 77attempting proto:2ether id:0040.f902.c7b4port 1 number:5559876port 2 number:5559876origination port:1remote name:berl9password is correctshows describes the fields and messages shown in .
Related Commands
debug cpp event
debug cpp packetdebug cpp packet
Use the debug cpp packet EXEC command to display Combinet Proprietary Protocol (CPP) packets. The no form of this command disables debugging output.
[no] debug cpp packet
Usage Guidelines
The CPP protocol allows a router to engage in negotiation over an ISDN B channel to establish connections with a Combinet bridge.
The debug cpp packet command displays the hexadecimal values of the packets.
Sample Display
shows sample debug cpp packet output. This example shows the interface name, packet type, packet size, and the hexadecimal values of the packet.
Figure 2-57 Sample Debug CPP Packet Output
Router# debug cpp packetBR0:1:input packet - len 6000 00 00 00 00 00 00 40 F9 02 C7 B4 08 0.!6 00 0108 00 06 04 00 02 00 40 F9 02 C7 B4 83 6C A1 02!!!Success rate is 80 percent (4/5), round-trip min/avg/max = 64/66/68 msBR0:1 output packet - len 11606 00 00 40 F9 02 C7 B4 00 00 0C 3E 12 3A 08 0045 00 00 64 00 01 00 00 FF 01 72 BB 83 6C A1 01Related Commands
debug cpp event
debug cpp negotiationdebug crypto key-exchange
Use the debug crypto key-exchange EXEC command to show Digital Signature Standard (DSS) public key exchange messages.The no form of this command disables debugging output.
[no] debug crypto key-exchange
Usage Guidelines
Encryption and authentication are provided by a software service on the router called a crypto engine. The crypto engine performs authentication through DSS public and private keys when a connection is set up. DSS is a means of sending a "signature" at the end of a message that positively identifies the author of the message. The signature cannot be forged or duplicated by others, so whoever received a message with a DSS signature knows exactly who sent the message.
If the process of exchanging DSS public keys with a peer router by means of the config crypto key-exchange command is not successful, try to exchange DSS public keys again after enabling the debug crypto key-exchange command to help you diagnose the problem.
Sample Displays
and show sample debug crypto key-exchange output. shows output from the initiating router in a key exchange. shows output from the passive router in a key exchange. The number of bytes received should match the number of bytes sent from the initiating side, although the number of messages can be different.
Figure 2-58 Sample Debug Crypto Key-Exchange Output—Initiating Router
Router# debug crypto key-exchangeCRYPTO-KE: Sent 4 bytes.CRYPTO-KE: Sent 2 bytes.CRYPTO-KE: Sent 2 bytes.CRYPTO-KE: Sent 2 bytes.CRYPTO-KE: Sent 64 bytes.Figure 2-59 Sample Debug Crypto Key-Exchange Output—Passive Router
Router# debug crypto key-exchangeCRYPTO-KE: Received 4 bytes.CRYPTO-KE: Received 2 bytes.CRYPTO-KE: Received 2 bytes.CRYPTO-KE: Received 2 bytes.CRYPTO-KE: Received 49 bytes.CRYPTO-KE: Received 15 bytes.Related Command
debug crypto sesmgmt
Use the debug crypto sesmgmt EXEC command to show connection setup messages and their flow through the router. The no form of this command disables debugging output.
[no] debug crypto sesmgmt
Usage Guidelines
Encryption and authentication are provided by a software service on the router called a crypto engine. The crypto engine performs authentication through DSS public and private keys when a connection is set up. DSS is a means of sending a "signature" at the end of a message that positively identifies the author of the message. The signature cannot be forged or duplicated by others, so whoever received a message with a DSS signature knows exactly who sent the message.
When connections are not completing, use the debug crypto sesmgmt command to follow the progress of connection messages as a first step in diagnosing the problem. You see a record of each connection message as the router discovers it, and can track its progress through the necessary signing, verifying, and encryption session setup operations. Other significant connection setup events, such as the pregeneration of Diffie-Hellman public numbers, are also shown. For information on Diffie-Hellman public numbers, refer to the Security Configuration Guide.
Also use the show crypto connections command to display additional information on connections.
Sample Displays
and show sample debug crypto sesmgmt output. shows messages from a router that initiates a successful connection. shows the messages from a router that receives a connection.
Figure 2-60 Sample Debug Crypto Sesmgmt Output—Initiating Router
Router# debug crypto sesmgmtCRYPTO: Dequeued a message: Inititate_ConnectionCRYPTO: DH gen phase 1 status for conn_id 2 slot 0:OKCRYPTO: Signing done. Status:OKCRYPTO: ICMP message sent: s=172.21.114.163, d=172.21.114.162CRYPTO-SDU: send_nnc_req: NNC Echo Request sentCRYPTO: Dequeued a message: CRMCRYPTO: DH gen phase 2 status for conn_id 2 slot 0:OKCRYPTO: Verify done. Status=OKCRYPTO: Signing done. Status:OKCRYPTO: ICMP message sent: s=172.21.114.163, d=172.21.114.162CRYPTO-SDU: recv_nnc_rpy: NNC Echo Confirm sentCRYPTO: Create encryption key for conn_id 2 slot 0:OKCRYPTO: Replacing -2 in crypto maps with 2 (slot 0)Figure 2-61 Sample Debug Crypto Sesmgmt Output—Receiving Router
Router# debug crypto sesmgmtCRYPTO: Dequeued a message: CIMCRYPTO: Verify done. Status=OKCRYPTO: DH gen phase 1 status for conn_id 1 slot 0:OKCRYPTO: DH gen phase 2 status for conn_id 1 slot 0:OKCRYPTO: Signing done. Status:OKCRYPTO: ICMP message sent: s=172.21.114.162, d=172.21.114.163CRYPTO-SDU: act_on_nnc_req: NNC Echo Reply sentCRYPTO: Create encryption key for conn_id 1 slot 0:OKCRYPTO: Replacing -2 in crypto maps with 1 (slot 0)CRYPTO: Dequeued a message: CCMCRYPTO: Verify done. Status=OKRelated Command
debug decnet adj
Use the debug decnet adj EXEC command to display debugging information on DECnet adjacencies. The no form of this command disables debugging output.
[no] debug decnet adj
Sample Display
shows sample debug decnet adj output.
Figure 2-62 Sample Debug DECnet Adj Output
Router# debug decnet adjDNET-ADJ: Level 1 hello from 1.3DNET-ADJ: sending hellosDNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498DNET-ADJ: Level 1 hello from 1.3DNET-ADJ: 1.5 adjacency initializingDNET-ADJ: sending triggered hellosDNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498DNET-ADJ: Level 1 hello from 1.3DNET-ADJ: 1.5 adjacency upDNET-ADJ: Level 1 hello from 1.5DNET-ADJ: 1.5 adjacency down, listener timeoutExplanations for representative lines of output in follow.
The following line indicates that the router is sending hellos to all routers on this segment, which in this case is Ethernet 0:
DNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498The following line indicates that the router has heard a hello from address 1.5 and is creating an adjacency entry in its table. The initial state of this adjacency will be initializing.
DNET-ADJ: 1.5 adjacency initializingThe following line indicates that the router is sending an unscheduled (triggered) hello as a result of some event, such as new adjacency being heard:
DNET-ADJ: sending triggered hellosThe following line indicates that the adjacency with 1.5 is now up, or active:
DNET-ADJ: 1.5 adjacency upThe following line indicates that the adjacency with 1.5 has timed out, because no hello has been heard from adjacency 1.5 in the time interval originally specified in the hello from 1.5:
DNET-ADJ: 1.5 adjacency down, listener timeoutThe following line indicates that the router is sending an unscheduled hello, as a result of some event, such as the adjacency state changing:
DNET-ADJ: hello update triggered by state changed in dn_add_adjacencydebug decnet connects
Use the debug decnet connects EXEC command to display debugging information of all connect packets that are filtered (permitted or denied) by DECnet access lists. The no form of this command disables debugging output.
[no] debug decnet connects
Usage Guidelines
When you use connect packet filtering, it may be helpful to use the decnet access-group configuration command to apply the following basic access list:
access-list 300 permit 0.0 63.1023 eq anyYou can then log all connect packets transmitted on interfaces to which you applied this list, in order to determine those elements on which your connect packets must be filtered.
Note
Packet password and account information is not logged in the debug decnet connects message, nor is it displayed by the show access EXEC command. If you specify password or account information in your access list, they can be viewed by anyone with access to the configuration of the router.
Sample Display
shows sample debug decnet connects output.
Figure 2-63 Sample Debug DECnet Connects Output
Router# debug decnet connectsDNET-CON: list 300 item #2 matched src=19.403 dst=19.309 on Ethernet0: permittedsrcname="RICK" srcuic=[0,017]dstobj=42 id="USER"describes significant fields shown in .
debug decnet events
Use the debug decnet events EXEC command to display debugging information on DECnet events. The no form of this command disables debugging output.
[no] debug decnet events
Sample Display
shows sample debug decnet events output.
Figure 2-64 Sample Debug DECnet Events Output
Router# debug decnet eventsDNET: Hello from area 50 rejected - exceeded `max area' parameter (45)DNET: Hello from area 50 rejected - exceeded `max area' parameter (45)Explanations for representative lines of output in follow.
The following line indicates that the router received a hello from a router whose area was greater than the max-area parameter with which this router was configured:
DNET: Hello from area 50 rejected - exceeded'max area' parameter (45)The following line indicates that the router received a hello from a router whose node ID was greater than the max-node parameter with which this router was configured:
DNET: Hello from node 1002 rejected - exceeded'max node' parameter (1000)debug decnet packet
Use the debug decnet packet EXEC command to display debugging information on DECnet packet events. The no form of this command disables debugging output.
[no] debug decnet packet
Sample Display
shows sample debug decnet packet output.
Figure 2-65 Sample Debug DECnet Packet Output
Router# debug decnet packetDNET-PKT: src 1.4 dst 1.5 sending to PHASEVDNET-PKT: Packet fwded from 1.4 to 1.5, via 1.5, snpa 0000.3080.cf90, TokenRing0Explanations for individual lines of output from follow.
The following line indicates that the router is sending a converted packet addressed to node 1.5 to Phase V:
DNET-PKT: src 1.4 dst 1.5 sending to PHASEVThe following line indicates that the router forwarded a packet from node 1.4 to node 1.5. The packet is being sent to the next hop of 1.5 whose subnetwork point of attachment (MAC address) on that interface is 0000.3080.cf90.
DNET-PKT: Packet fwded from 1.4 to 1.5, via 1.5, snpa 0000.3080.cf90, TokenRing0debug decnet routing
Use the debug decnet routing EXEC command to display all DECnet routing-related events occurring at the router. The no form of this command disables debugging output.
[no] debug decnet routing
Sample Display
shows sample debug decnet routing output.
Figure 2-66 Sample Debug DECnet Routing Output
Router# debug decnet routingDNET-RT: Received level 1 routing from 1.3 on Ethernet0 at 1:16:34DNET-RT: Sending routesDNET-RT: Sending normal routing updates on Ethernet0DNET-RT: Sending level 1 routing updates on interface Ethernet0DNET-RT: Level1 routes from 1.5 on Ethernet0: entry for node 5 createdDNET-RT: route update triggered by after split route pointers in dn_rt_inputDNET-RT: Received level 1 routing from 1.5 on Ethernet 0 at 1:18:35DNET-RT: Sending L1 triggered routesDNET-RT: Sending L1 triggered routing updates on Ethernet0DNET-RT: removing route to node 5Explanations for individual lines of output from follow.
The following line indicates that the router has received a level 1 update on interface Ethernet 0:
DNET-RT: Received level 1 routing from 1.3 on Ethernet0 at 1:16:34The following line indicates that the router is sending its scheduled updates on interface Ethernet 0:
DNET-RT: Sending normal routing updates on Ethernet0The following line indicates that the route will send an unscheduled update on this interface as a result of some event. In this case, the unscheduled update is a result of a new entry created in the interface's routing table.
DNET-RT: route update triggered by after split route pointers in dn_rt_inputThe following line indicates that the router sent the unscheduled update on Ethernet 0:
DNET-RT: Sending L1 triggered routesDNET-RT: Sending L1 triggered routing updates on Ethernet0The following line indicates that the router removed the entry for node 5 because the adjacency with node 5 timed out, or the route to node 5 through a next-hop router went away:
DNET-RT: removing route to node 5debug dialer events
Use the debug dialer events EXEC command to display debugging information about the packets received on a dialer interface. The no form of this command disables debugging output.
[no] debug dialer events
Sample Displays
When DDR is enabled on the interface, information concerning the cause of any call (called the Dialing cause) is displayed. The following line of output for an IP packet lists the name of the DDR interface and the source and destination addresses of the packet:
Dialing cause: Serial0: ip (s=172.16.1.111 d=172.16.2.22)The following line of output for a bridged packet lists the DDR interface and the type of packet (in hexadecimal). For information on these packet types, see the "Ethernet Type Codes" appendix of the Bridging and IBM Networking Command Reference publication.
Dialing cause: Serial1: Bridge (0x6005)Most messages are self-explanatory; however, messages that may need some explanation are described in .
describes the messages that the debug dialer events command can generate for a serial interface used as a V.25bis dialer for dial-on-demand routing (DDR).
Related Command
debug dialer packets
Use the debug dialer packets EXEC command to display debugging information about the packets received on a dialer interface. The no form of this command disables debugging output.
[no] debug dialer packets
Usage Guidelines
Most debug dialer packet messages are self-explanatory.
Sample Display
shows sample debug dialer packets output. The following message shows the interface type, the type of packet (protocol) being sent, the source and destination addresses, the size of the packet, and the default action for the packet (in this example, permit).
Figure 2-67 Sample Debug Dialer Packets Output
Router# debug dialer packetsBRI0: ip (s=10.1.1.8, d=10.1.1.1), 100 bytes, interesting (ip PERMIT)Related Command
debug dlsw
Use the debug dlsw EXEC command to enable debugging of DLSw+. The no form of this command disables debugging output.
[no] debug dlsw [border-peers [interface interface | ip address ip address] | core
[flow-control | messages | state | xid] [circuit number] | local-circuit circuit number | peers
[interface interface [fast-errors | fast-paks] | ip address ip address [fast-errors |
fast-paks | fst-seq | udp]] | reachability [error | verbose] [sna | netbios]]
Syntax Description
Usage Guidelines
When you specify no optional keywords, the debug dlsw command enables all available DLSw debugging output.
Normally you need to use only the error or verbose option of the debug dlsw reachability command to help identify problems. The error option is recommended for use by customers and provides a subset of the messages from the normal event-level debugging. The verbose option provides a very detailed view of what is going on and is typically used only by service personnel.
To reduce the amount of debug information displayed, use the sna or netbios options with the debug dlsw reachability command if you know that you have an SNA or NetBIOS problem.
The DLSw core is the engine that is responsible for the establishment and maintenance of remote circuits. If possible, specifying the index of the specific circuit you want to debug reduces the amount of output displayed. However, if you want to watch a circuit initially come up, do not use the circuit-number option with the core keyword.
The core flow-control option provides information about congestion in the WAN or at the remote end station. In these cases, DLSw sends Receiver Not Ready (RNR) frames on its local circuits, slowing data traffic on established sessions and giving the congestion an opportunity to clear.
The core state option allows you to see when the circuit changes state. This capability is especially useful for determining why a session cannot be established or why a session is being disconnected.
The core XID option allows you to track the XID-state machine. The router tracks XID commands and responses used in negotiations between end stations before establishing a session.
Sample Displays
The following sections show and explain some of the typical DLSw debug messages you might see when using the debug dlsw command.
Sample Debug DLSW Peer Messages
The following example enables UDP packet debugging for a specific remote peer:
Router# debug dlsw peer ip-address 1.1.1.6 udpThe following message is sample output from the debug dlsw border-peers command:
*Mar 10 17:39:56: CSM: delete group mac cache for group 0*Mar 10 17:39:56: CSM: delete group name cache for group 0*Mar 10 17:40:19: CSM: update group cache for mac 0000.3072.1070, group 10*Mar 10 17:40:22: DLSw: send_to_group_members(): copy to peer 10.19.32.5The following message is from a router that initiated a TCP connection:
DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:ADMIN-OPEN CONNECTION state:DISCONNDLSw: dtp_action_a() attempting to connect peer 10.3.8.7(2065)DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:DISCONN->WAIT_WRDLSw: Async Open Callback 10.3.8.7(2065) -> 11002DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR DLSw: dtp_action_f() start read open timer for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_WR->WAIT_RD DLSw: passive open 10.3.8.7(11004) -> 2065 DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD DLSw: dtp_action_g() read pipe opened for peer 10.3.8.7(2065) DLSw: CapExId Msg sent to peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_RD->WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) DLSw: Recv CapExId Msg from peer 10.3.8.7(2065) DLSw: Pos CapExResp sent to peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) DLSw: Recv CapExPosRsp Msg from peer 10.3.8.7(2065) DLSw:
