-
Cisco IOS Debug Command Reference
-
Introduction
-
Using Debug Commands
-
Conditionally Triggered Debugging
-
debug aaa accounting through debug auto-config
-
debug backhaul-session-manager session through debug channel packets
-
debug clns esis events through debug dbconn tcp
-
debug decnet adj through debug events
-
debug fax dmsp through debug gvrp
-
debug h225 asn1 through debug ip ftp
-
debug ip http all through debug ip rsvp
-
debug ip rtp header-compression through debug ipv6 icmp
-
debug ipv6 inspect through debug local-ack state
-
debug management event through debug mpls ldp bindings
-
debug mpls ldp checkpoint through debug mwi relay events
-
debug ncia circuit through debug pxf tbridge
-
debug qllc error through debug snmp sync
-
debug sntp adjust through debug tag-switching xtagatm vc
-
debug tag-template event through debug voip application vxml
-
debug voip avlist through debug vpm signaling
-
debug vpm spi through voice call debug
-
X.25 Cause and Diagnostic Codes
-
ISDN Switch Types, Codes, and Values
-
Table Of Contents
debug eigrp address-family neighbor
debug eigrp address-family notifications
debug ephone extension-assigner
debug decnet adj
To display debugging information on DECnet adjacencies, use the debug decnet adj command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug decnet adj
no debug decnet adj
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug decnet adj command:
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 timeoutThe following line indicates that the router is sending hello messages 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 message 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 message 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 message has been heard from adjacency 1.5 in the time interval originally specified in the hello message from 1.5:
DNET-ADJ: 1.5 adjacency down, listener timeoutThe following line indicates that the router is sending an unscheduled hello message, 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
To display debugging information of all connect packets that are filtered (permitted or denied) by DECnet access lists, use the debug decnet connects command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug decnet connects
no debug decnet connects
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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 sent 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.
Examples
The following is sample output from the debug decnet connects command:
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"Table 71 describes significant fields shown in the output.
debug decnet events
To display debugging information on DECnet events, use the debug decnet events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug decnet events
no debug decnet events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug decnet events command:
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)The following line indicates that the router received a hello message 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 message 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
To display debugging information on DECnet packet events, use the debug decnet packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug decnet packet
no debug decnet packet
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug decnet packet command:
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, TokenRing0The 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
To display all DECnet routing-related events occurring at the router, use the debug decnet routing command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug decnet routing
no debug decnet routing
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Examples
The following is sample output from the debug decnet routing command:
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 5The following line indicates that the router has received a level 1 update on Ethernet interface 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 Ethernet interface 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 routing table of the interface.
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 was disconnected:
DNET-RT: removing route to node 5debug dhcp
To display debugging information about the Dynamic Host Configuration Protocol (DHCP) client activities and to monitor the status of DHCP packets, use the debug dhcp command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dhcp [detail]
no debug dhcp [detail]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
You can also use the debug dhcp command to monitor the subnet allocation and releasing for on-demand address pools.
For debugging purposes, the debug dhcp detail command provides the most useful information such as the lease entry structure of the client and the state transitions of the lease entry. The debug output shows the scanned option values from received DHCP messages that are replies to a router request. The values of the op, htype, hlen, hops, server identifier option, xid, secs, flags, ciaddr, yiaddr, siaddr, and giaddr fields of the DHCP packet are shown in addition to the length of the options field.
Examples
The following examples show and explain some of the typical debugging messages you may see when using the debug dhcp detail command.
The following sample output shows when a DHCP client sends a DHCPDISCOVER broadcast message to find its local DHCP server:
Router# debug dhcp detail00:07:16:DHCP:DHCP client process started:1000:07:16:RAC:Starting DHCP discover on Ethernet200:07:16:DHCP:Try 1 to acquire address for Ethernet200:07:16:%SYS-5-CONFIG_I:Configured from console by console00:07:19:DHCP:Shutting down from get_netinfo()00:07:19:DHCP:Attempting to shutdown DHCP Client00:07:21:DHCP:allocate request00:07:21:DHCP:new entry. add to queue00:07:21:DHCP:SDiscover attempt # 1 for entry:The first seven lines of the following output show the current values stored in the lease entry structure for the client:
00:07:21:Temp IP addr:0.0.0.0 for peer on Interface:Ethernet200:07:21:Temp sub net mask:0.0.0.000:07:21: DHCP Lease server:0.0.0.0, state:1 Selecting00:07:21: DHCP transaction id:58200:07:21: Lease:0 secs, Renewal:0 secs, Rebind:0 secs00:07:21: Next timer fires after:00:00:0300:07:21: Retry count:1 Client-ID:cisco-0010.7b6e.afd8-Et200:07:21:DHCP:SDiscover:sending 308 byte length DHCP packet00:07:21:DHCP:SDiscover 308 bytes00:07:21: B'cast on Ethernet2 interface from 0.0.0.0The following output shows the offered addresses and parameters sent to the DHCP client by the DHCP server via a DHCPOFFER message. The messages containing the Scan field indicate the options that were scanned from the received BOOTP packet and the corresponding values:
00:07:23:DHCP:Received a BOOTREP pkt00:07:23:DHCP:Scan:Message type:DHCP Offer00:07:23:DHCP:Scan:Server ID Option:10.1.1.1 = A01010100:07:23:DHCP:Scan:Lease Time:18000:07:23:DHCP:Scan:Renewal time:9000:07:23:DHCP:Scan:Rebind time:15700:07:23:DHCP:Scan:Subnet Address Option:255.255.255.0The following output shows selected fields in the received BOOTP packet:
00:07:23:DHCP:rcvd pkt source:10.1.1.1, destination: 255.255.255.25500:07:23: UDP sport:43, dport:44, length:30800:07:23: DHCP op:2, htype:1, hlen:6, hops:000:07:23: DHCP server identifier:10.1.1.100:07:23: xid:582, secs:0, flags:800000:07:23: client:0.0.0.0, your:10.1.1.200:07:23: srvr: 0.0.0.0, gw:0.0.0.000:07:23: options block length:6000:07:23:DHCP Offer Message Offered Address:10.1.1.200:07:23:DHCP:Lease Seconds:180 Renewal secs: 90 Rebind secs:15700:07:23:DHCP:Server ID Option:10.1.1.100:07:23:DHCP:offer received from 10.1.1.1The following output shows when the DHCP client sends a DHCPREQUEST broadcast message to the DHCP server to accept the offered parameters:
00:07:23:DHCP:SRequest attempt # 1 for entry:00:07:23:Temp IP addr:10.1.1.2 for peer on Interface:Ethernet200:07:23:Temp sub net mask:255.255.255.000:07:23: DHCP Lease server:10.1.1.1, state:2 Requesting00:07:23: DHCP transaction id:58200:07:23: Lease:180 secs, Renewal:0 secs, Rebind:0 secs00:07:23: Next timer fires after:00:00:0200:07:23: Retry count:1 Client-ID:cisco-0010.7b6e.afd8-Et200:07:23:DHCP:SRequest- Server ID option:10.1.1.100:07:23:DHCP:SRequest- Requested IP addr option:10.1.1.200:07:23:DHCP:SRequest placed lease len option:18000:07:23:DHCP:SRequest:326 bytes00:07:23:DHCP:SRequest:326 bytes00:07:23: B'cast on Ethernet2 interface from 0.0.0.0The following output shows when the DHCP server sends a DHCPACK message to the client with the full set of configuration parameters:
00:07:23:DHCP:Received a BOOTREP pkt00:07:23:DHCP:Scan:Message type:DHCP Ack00:07:23:DHCP:Scan:Server ID Option:10.1.1.1 = A01010100:07:23:DHCP:Scan:Lease Time:18000:07:23:DHCP:Scan:Renewal time:9000:07:23:DHCP:Scan:Rebind time:15700:07:23:DHCP:Scan:Subnet Address Option:255.255.255.000:07:23:DHCP:rcvd pkt source:10.1.1.1, destination: 255.255.255.25500:07:23: UDP sport:43, dport:44, length:30800:07:23: DHCP op:2, htype:1, hlen:6, hops:000:07:23: DHCP server identifier:10.1.1.100:07:23: xid:582, secs:0, flags:800000:07:23: client:0.0.0.0, your:10.1.1.200:07:23: srvr: 0.0.0.0, gw:0.0.0.000:07:23: options block length:6000:07:23:DHCP Ack Message00:07:23:DHCP:Lease Seconds:180 Renewal secs: 90 Rebind secs:15700:07:23:DHCP:Server ID Option:10.1.1.1Interface Ethernet2 assigned DHCP address 10.1.1.2, mask 255.255.255.000:07:26:DHCP Client Pooling:***Allocated IP address:10.1.1.200:07:26:Allocated IP address = 10.1.1.2 255.255.255.0The following output shows when a default gateway (option 3) is assigned a static IP address that is the default route and that static routes were added from the DHCP server:
*Oct 2 06:22:24: Setting default_gateway to 68.8.8.1 ! This is the option 3 default gateway.*Oct 2 06:22:24: Adding default route 68.8.8.1*Oct 2 06:22:24: DHCP: Adding static route to 4.3.2.1 255.255.255.255 via 68.8.8.1*Oct 2 06:22:24: DHCP: Adding static route to 1.1.1.1 255.255.255.255 via 68.8.8.1*Oct 2 06:22:24: DHCP: Adding static route to 67.2.2.2 255.255.255.255 via 68.8.8.1Most fields are self-explanatory; however, fields that may need further explanation are described in Table 72.
Related Commands
debug dhcp redundancy
To display debugging information about DHCP proxy client redundancy events, use the debug dhcp redundancy command in privileged EXEC mode. To disable the display of debugging output, use the no form of this command.
debug dhcp redundancy
no debug dhcp redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
Debugging output is disabled for DHCP redundancy events.
Command Modes
Privileged EXEC
Command History
Examples
The following example displays debug messages regarding DHCP redundancy events. The last line is output when the debug dhcp redundancy command is enabled. The line indicates that the active Route Processor has sent a dynamic lease synchronization message for IP address 10.1.1.1:
Router# debug dhcp redundancy*Mar 15 10:32:21: DHCPD: assigned IP address 10.1.1.1 to client*Mar 15 10:32:21: DHCPD: dynamic sync sent for 10.1.1.1Related Commands
debug ip dhcp server redundancy
Displays debugging information about DHCP server and relay agent redundancy events.
debug dialer events
To display debugging information about the packets received on a dialer interface, use the debug dialer events command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dialer events
no debug dialer events
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Usage Guidelines
When dial-on-demand routing (DDR) is enabled on the interface, information concerning the cause of any call (called the Dialing cause) is displayed.
Examples
In the following example, the line of output for an IP packet lists the name of the DDR interface and the source and destination addresses of the packet:
Router# debug dialer eventsDialing 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 Cisco IOS 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 Table 73.
Table 74 describes the messages that the debug dialer events command can generate for a serial interface used as a V.25bis dialer for DDR.
Related Commands
debug decnet packet
Displays debugging information about the packets received on a dialer interface.
debug dialer forwarding
To display debugging information about the control plane at the home gateway (HGW) for Layer 2 Tunneling Protocol (L2TP) dialout, use the debug dialer forwarding command in privileged EXEC mode. The no form of this command disables debugging output.
debug dialer forwarding
no debug dialer forwarding
Syntax Description
This command has no keywords or arguments.
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug dialer forwarding command to configure a virtual private dialout network (VPDN) on the HGW and a network access server (NAS) to dial from the HGW to the client.
An L2TP tunnel is created between the HGW and the NAS and the packets are forwarded transparently at the NAS.
Examples
The following is sample output from the debug dialer forwarding command for dialing from the HGW to the client.
Note
Router# debug dialer forwardingDialer forwarding events debugging is onRouter# pingProtocol [ip]:Target IP address:1.1.1.3Repeat count [5]:1Datagram size [100]:Timeout in seconds [2]:Extended commands [n]:Sweep range of sizes [n]:Type escape sequence to abort.Sending 1, 100-byte ICMP Echos to 1.1.1.3, timeout is 2 seconds:1d00h:Vi3 DDR-FWD 83093A60:event [REQUEST] state before [IDLE]1d00h:Vi3 DDR-FWD 83093A60:VPN Authorization started1d00h:Vi3 DDR-FWD 83093A60:VPN author result 11d00h:Vi3 DDR-FWD 83093A60:event [AUTHOR FOUND] state before [AUTHORIZING]1d00h:Vi3 DDR-FWD 83093A60:event [FORWARDED] state before [FORWARDING]1d00h:Vi3 DDR-FWD 83093A60:Connection is up, start LCP now*Mar 2 00:31:33:%LINK-3-UPDOWN:Interface Virtual-Access3, changed state to up.Success rate is 0 percent (0/1)R2604#*Mar 2 00:31:35:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access3, changedstate to upRouter#Outgoing call disconnected:
Router#1d00h:Vi3 DDR-FWD 83093A60:event [VPDN DISC] state before [FORWARDED]*Mar 2 00:33:33:%LINK-3-UPDOWN:Interface Virtual-Access3, changed state to down*Mar 2 00:33:34:%LINEPROTO-5-UPDOWN:Line protocol on Interface Virtual-Access3, changedstate to downRelated Commands
debug dialer map
To display debugging information about the creation and deletion of dynamic dialer maps, use the debug dialer map command in privileged EXEC mode. The no form of this command disables debugging output.
debug dialer map
no debug dialer map
Syntax Description
This command has no keywords or arguments.
Defaults
This command is disabled by default.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the debug dialer map command to track large-scale dialout (LSDO) and incoming calls that use dynamic dialer maps. This command shows the whole trace including when the map is created and removed.
If an interface is configured for dial-on-demand routing (DDR), and a map to a specified address does not exist, then a dynamic dialer map is created and when the call disconnects, the dialer map is removed.
Note
Examples
In the following sample output from the debug dialer map command, a dialer map is created when an incoming call is connected and removed when that call is disconnected:
Router# debug dialer mapDial on demand dynamic dialer maps debugging is onIncoming call connected:
Router#*Mar 22 12:19:15.597:%LINK-3-UPDOWN:Interface BRI0/0:1, changed state to up*Mar 22 12:19:17.748:BR0/0:1 DDR:dialer_create_dynamic_map map created for 11.0.0.1*Mar 22 12:19:18.734:%LINEPROTO-5-UPDOWN:Line protocol on Interface BRI0/0:1, changed state to up*Mar 22 12:19:21.598:%ISDN-6-CONNECT:Interface BRI0/0:1 is now connected to unknown R2604Incoming call disconnected:
Router#*Mar 22 12:21:15.597:%ISDN-6-DISCONNECT:Interface BRI0/0:1 disconnected from R2604, call lasted 120 seconds*Mar 22 12:21:15.645:%LINK-3-UPDOWN:Interface BRI0/0:1, changed state to down*Mar 22 12:21:15.649:BR0/0:1 DDR:dialer_remove_dynamic_map map 11.0.0.1 removed*Mar 22 12:21:16.647:%LINEPROTO-5-UPDOWN:Line protocol on Interface BRI0/0:1, changed state to downRelated Commands
debug dialpeer
Note
To view dial peer information, use the debug dialpeer command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dialpeer
no debug dialpeer
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Disable console logging and use buffered logging before using the debug dialpeer command. Using the debug dialpeer command generates a large volume of debugging messages, which can affect router performance.
Examples
The following is sample output for the debug dialpeer command. The output shows the destination pattern configured on the matched dial-peer. Expanded string is the string after applying number translation to the original number. It shows that dial-peer 1311 was an incoming dial-peer match. It also shows that routing label was att1. It shows that dial-peer 5108888 and 111399 are an outgoing dial-peer match.
Router# debug dialpeerRouter#00:22:28: Inside dpMatchCore:00:22:28: destination pattn:5108880101 expanded string:510888010100:22:28:MatchNextPeer:Peer 1311 matched00:22:28: Inside dpMatchCore:00:22:28: destination pattn:5108880101 expanded string:510888010100:22:28: Inside dpMatchCore:00:22:28: destination pattn:4088880101 expanded string:408888010100:22:28: Inside dpMatchCore:00:22:28: destination pattn:4088880101 expanded string:408888010100:22:28: dpAssociateIncomingPeer_T:Matching route label att100:22:28: Inside dpMatchCore:00:22:28: destination pattn:5108880101 expanded string:510888010100:22:28: dpAssociateIncomingPeer_T:Matching peer with src route label att1 failed00:22:28: Inside dpMatchCore:00:22:28: destination pattn:5108880101 expanded string:510888010100:22:28:MatchNextPeer:Peer 1311 matched00:22:28: Inside dpMatchPeersMoreArg00:22:28:dpMatchPeersMoreArg:Match Dest. pattern; called (5108880101)00:22:28: Inside dpMatchCore:00:22:28: destination paRouter#ttn:5108880101 expanded string:510888010100:22:28:MatchNextPeer:Peer 5108888 matched00:22:28:MatchNextPeer:Peer 111399 matched00:22:28:dpMatchPeersMoreArg:Result=0 after MATCH_ORIGINATETable 75 describes the significant fields shown in the display.
Related Commands
debug diameter
To display information about the Diameter Protocol, use the debug diameter command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug diameter [dcca | connection | error | packet | event | fsm | failover]
no debug diameter [dcca | connection | error | packet | event | fsm | failover]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display information about any of the listed classes of information about the Diameter Protocol.
Examples
The following examples show output from the debug diameter command:
Peer configuration and peer connection after a peer is configured
Router# debug diameter all*May 9 17:58:14.832: Dia Base: Diameter Peer configured. Allocate connection context.*May 9 17:58:14.832: Dia Base: Allocate the peer connection context 50F63888, handle C000000C *May 9 17:58:14.832: Dia Base: (C000000C): Received peer configuration event *May 9 17:58:14.832: Dia Peer FSM (50F63888): input event START in state CLOSED *May 9 17:58:14.832: Dia Peer FSM (50F63888): Starting Connection timer *May 9 17:58:14.832: Dia Peer FSM (50F63888): event START, stateCLOSED-->WAIT_CONN_ACK*May 9 17:58:14.836: Dia Transport: socket 0 - connecting to 9.113.33.6(3868)*May 9 17:58:14.836: Dia Transport: socket 0 - connection in progress *May 9 17:58:14.836: Dia Transport: socket 0 - local address 9.113.33.5(49214)*May 9 17:58:14.836: Dia Transport: socket 0 - resume socket write - nothing to write *May 9 17:58:14.836: Dia Base: (C000000C): Received peer connection event from transport *May 9 17:58:14.836: Dia Peer FSM (50F63888): input event RCV_CONN_ACK in state WAIT_CONN_ACK *May 9 17:58:14.836: Dia Base: Sending diameter message to peer "Unknown"*May 9 17:58:14.836: DIAMETER: CER message, ver=1, len=120, app=0, [2328318322/2328318322]*May 9 17:58:14.836: DIAMETER: Origin-host-name [264]"host" (M)*May 9 17:58:14.836: DIAMETER: Origin-Realm [296]"cisco" (M)*May 9 17:58:14.836: DIAMETER: Host-IP-address [257]9.113.33.5 (M)*May 9 17:58:14.836: DIAMETER: Vendor-ID [266] 9(M)*May 9 17:58:14.836: DIAMETER: Product-name [269]"C7200-G8IS-M"*May 9 17:58:14.836: DIAMETER: Auth-Application-ID [258] 4(M)*May 9 17:58:14.836: DIAMETER: Firmware-Revision [267] 150D0B710: 01000078 80000101 00000000 ...x........50D0B720: 8AC75172 8AC75172 00000108 4000000C .GQr.GQr....@...50D0B730: 686F7374 00000128 4000000D 63697363 host...(@...cisc50D0B740: 6F000000 00000101 4000000E 00010971 o.......@......q50D0B750: 21050000 0000010A 4000000C 00000009 !.......@.......50D0B760: 0000010D 00000014 43373230 302D4738 ........C7200-G850D0B770: 49532D4D 00000102 4000000C 00000004 IS-M....@.......50D0B780: 0000010B 0000000C 00000001 00 .............*May 9 17:58:14.836: Dia Base: Request message hash ctx created for [2328318322/2328318322] *May 9 17:58:14.836: Dia Peer FSM (50F63888): Starting CER timer *May 9 17:58:14.836: Dia Peer FSM (50F63888): event RCV_CONN_ACK, state WAIT_CONN_ACK-->WAIT_CEA *May 9 17:58:14.836: Dia Transport: Dia Transport write message event *May 9 17:58:14.836: Dia Transport: socket 0 - complete msg sent *May 9 17:58:14.840: Dia Transport: socket 0 - complete read of 20 bytes *May 9 17:58:14.840: Dia Transport: complete header read from socket 0 *May 9 17:58:14.840: Dia Transport: read msg (172) bytes from socket 0 *May 9 17:58:14.840: Dia Transport: socket 0 - complete read of 172 bytes *May 9 17:58:14.840: Dia Base: Diameter message received from the peer "Unknown"*May 9 17:58:14.840: DIAMETER: CEA message, ver=1, len=192, app=0, [2328318322/2328318322]*May 9 17:58:14.840: DIAMETER: Result-code [268]2001 (M)*May 9 17:58:14.840: DIAMETER: Origin-host-name [264]"diameter2.cisco.com" (M)*May 9 17:58:14.840: DIAMETER: Origin-Realm [296]"cisco.com" (M)*May 9 17:58:14.840: DIAMETER: Host-IP-address [257]10.77.154.80 (M)*May 9 17:58:14.840: DIAMETER: Vendor-ID [266] 9(M)*May 9 17:58:14.840: DIAMETER: Product-name [269]"Diameter-Server"*May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265]10415 (M)*May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265]12645 (M)*May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265] 9(M)*May 9 17:58:14.840: DIAMETER: Supported-Vendor-ID [265] 9(M)*May 9 17:58:14.840: DIAMETER: Auth-Application-ID [258] 4(M)65940780: 010000C0 00000101 00000000 ...@........65940790: 8AC75172 8AC75172 0000010C 4000000C .GQr.GQr....@...659407A0: 000007D1 00000108 4000001B 6469616D ...Q....@...diam659407B0: 65746572 322E6369 73636F2E 636F6D00 eter2.cisco.com.659407C0: 00000128 40000011 63697363 6F2E636F ...(@...cisco.co659407D0: 6D000000 00000101 4000000E 00010A4D m.......@......M659407E0: 9A500000 0000010A 4000000C 00000009 .P......@.......659407F0: 0000010D 00000017 4469616D 65746572 ........Diameter65940800: 2D536572 76657200 00000109 4000000C -Server.....@...65940810: 000028AF 00000109 4000000C 00003165 ..(/....@.....1e65940820: 00000109 4000000C 00000009 00000109 ....@...........65940830: 4000000C 00000009 00000102 4000000C @...........@...65940840: 00000004 00 .....*May 9 17:58:14.840: Dia Base: Request message hash ctx removed for [2328318322/2328318322] *May 9 17:58:14.840: Dia Base: (C000000C): Received msg event from message i/o *May 9 17:58:14.840: Dia Peer FSM (50F63888): input event RCV_CEA in state WAIT_CEA *May 9 17:58:14.840: Dia Peer FSM (50F63888): Starting Watchdog timer *May 9 17:58:14.840: %DIABASE-4-DIA_PEER_UP: Diameter peer 9.113.33.6 port 3868 TCP UP *May 9 17:58:14.840: Dia Peer FSM (50F63888): event RCV_CEA, state WAIT_CEA-->OPENPeriodic watch-dog message exchanges
*May 9 17:59:14.840: Dia Peer FSM (50F63888): input event TIMEOUT instate OPEN*May 9 17:59:14.840: Dia Base: Sending diameter message to peer"diameter2.cisco.com"*May 9 17:59:14.840: DIAMETER: DWR message, ver=1, len=48, app=0,[2328318323/2328318323]*May 9 17:59:14.840: DIAMETER: Origin-host-name [264]"host" (M)*May 9 17:59:14.840: DIAMETER: Origin-Realm [296]"cisco" (M)50D0B710: 01000030 80000118 00000000 ...0........50D0B720: 8AC75173 8AC75173 00000108 4000000C .GQs.GQs....@...50D0B730: 686F7374 00000128 4000000D 63697363 host...(@...cisc50D0B740: 6F000000 FD o...}*May 9 17:59:14.840: Dia Base: Request message hash ctx created for[2328318323/2328318323]*May 9 17:59:14.840: Dia Peer FSM (50F63888): Starting Watchdog timer,[60] left for next timeout*May 9 17:59:14.840: Dia Peer FSM (50F63888):event TIMEOUT, state OPEN-->OPEN*May 9 17:59:14.840: Dia Transport: Dia Transport write message event*May 9 17:59:14.840: Dia Transport: socket 0 - complete msg sent*May 9 17:59:14.840: Dia Transport: socket 0 - complete read of 20bytes*May 9 17:59:14.840: Dia Transport: complete header read from socket 0*May 9 17:59:14.840: Dia Transport: read msg (60) bytes from socket 0*May 9 17:59:14.840: Dia Transport: socket 0 - complete read of 60bytes*May 9 17:59:14.840: Dia Base: Diameter message received from the peer"diameter2.cisco.com"*May 9 17:59:14.840: DIAMETER: DWA message, ver=1, len=80, app=0,[2328318323/2328318323]*May 9 17:59:14.840: DIAMETER: Result-code [268]2001 (M)*May 9 17:59:14.840: DIAMETER: Origin-host-name [264]"diameter2.cisco.com" (M)*May 9 17:59:14.840: DIAMETER: Origin-Realm [296]"cisco.com" (M)65940780: 01000050 00000118 00000000 ...P........65940790: 8AC75173 8AC75173 0000010C 4000000C .GQs.GQs....@...659407A0: 000007D1 00000108 4000001B 6469616D ...Q....@...diam659407B0: 65746572 322E6369 73636F2E 636F6D00 eter2.cisco.com.659407C0: 00000128 40000011 63697363 6F2E636F ...(@...cisco.co659407D0: 6D000000 00 m....*May 9 17:59:14.840: Dia Base: Request message hash ctx removed for[2328318323/2328318323]*May 9 17:59:14.840: Dia Base: (C000000C): Received msg event frommessage i/o*May 9 17:59:14.840: Dia Peer FSM (50F63888): input event RCV_DWA instate OPEN*May 9 17:59:14.840: Dia Peer FSM (50F63888): Starting Watchdog timer*May 9 17:59:14.840: Dia Peer FSM (50F63888): event RCV_DWA, stateOPEN-->OPENPeriodic connection attempt when the peer connection is broken
*May 9 18:07:18.472: Dia Transport: socket 0 READ event: UP->CLOSE dueto bytes read = 0*May 9 18:07:18.472: Dia Base: (8600000E): Received peer disconnectionevent from transport*May 9 18:07:18.472: %DIABASE-4-DIA_PEER_DOWN: Diameter peer 9.113.33.6port 3868 TCP DOWN*May 9 18:07:18.472: Dia Peer FSM (2068FF44): input event PEER_DISC instate OPEN*May 9 18:07:18.472: Dia Peer FSM (2068FF44): Starting Reconnect timer*May 9 18:07:18.472: Dia Peer FSM (2068FF44): event PEER_DISC, stateOPEN-->CLOSED*May 9 18:07:48.472: Dia Peer FSM (2068FF44): input event START instate CLOSED*May 9 18:07:48.472: Dia Peer FSM (2068FF44): Starting Connection timer*May 9 18:07:48.472: Dia Peer FSM (2068FF44): event START, stateCLOSED-->WAIT_CONN_ACK*May 9 18:07:48.472: Dia Transport: socket 0 - connecting to 9.113.33.6(3868)*May 9 18:07:48.472: Dia Transport: socket 0 - connection in progress*May 9 18:07:48.472: Dia Transport: socket 0 - local address 9.113.33.5(61122)*May 9 18:07:48.472: Dia Transport: socket 0 - CONN_WAIT->CLOSE*May 9 18:07:48.472: Dia Base: (8600000E): Received peer disconnectionevent from transport*May 9 18:07:48.472: Dia Peer FSM (2068FF44): input event PEER_DISC instate WAIT_CONN_ACK*May 9 18:07:48.472: Dia Peer FSM (2068FF44): Starting Reconnect timer*May 9 18:07:48.472: Dia Peer FSM (2068FF44): event PEER_DISC, stateWAIT_CONN_ACK-->CLOSEDPeer disconnection when a peer configuration is removed
Ginger(config)#no diameter peer watchGinger(config)#*May 9 18:05:02.812: Dia Base: Peer unconfigured, start peerdisconnection*May 9 18:05:02.812: Dia Base: (C000000C): Received peerunconfiguration event*May 9 18:05:02.812: Dia Peer FSM (50F63888): input event STOP in stateOPEN*May 9 18:05:02.812: Dia Base: Sending diameter message to peer"diameter2.cisco.com"*May 9 18:05:02.812: DIAMETER: DPR message, ver=1, len=60, app=0,[2328318329/2328318329]*May 9 18:05:02.812: DIAMETER: Origin-host-name [264]"host" (M)*May 9 18:05:02.816: DIAMETER: Origin-Realm [296]"cisco" (M)*May 9 18:05:02.816: DIAMETER: Peer-disconnect-reason [273]Server-do-not-want-to-talk (M)653D1810: 0100003C 8000011A ...<....653D1820: 00000000 8AC75179 8AC75179 00000108 .....GQy.GQy....653D1830: 4000000C 686F7374 00000128 4000000D @...host...(@...653D1840: 63697363 6F000000 00000111 4000000C cisco.......@...653D1850: 00000002 00 .....*May 9 18:05:02.816: Dia Base: Request message hash ctx created for[2328318329/2328318329]*May 9 18:05:02.816: Dia Peer FSM (50F63888): Starting DPR timer*May 9 18:05:02.816: Dia Peer FSM (50F63888): event STOP, stateOPEN-->CLOSING*May 9 18:05:02.816: Dia Transport: Dia Transport write message event*May 9 18:05:02.816: Dia Transport: socket 0 - complete msg sent*May 9 18:05:02.816: Dia Transport: socket 0 - complete read of 20bytes*May 9 18:05:02.816: Dia Transport: complete header read from socket 0*May 9 18:05:02.816: Dia Transport: read msg (60) bytes from socket 0*May 9 18:05:02.816: Dia Transport: socket 0 - complete read of 60bytes*May 9 18:05:02.816: Dia Base: Diameter message received from the peer"diameter2.cisco.com"*May 9 18:05:02.816: DIAMETER: DPA message, ver=1, len=80, app=0,[2328318329/2328318329]*May 9 18:05:02.816: DIAMETER: Result-code [268]2001 (M)*May 9 18:05:02.816: DIAMETER: Origin-host-name [264]"diameter2.cisco.com" (M)*May 9 18:05:02.816: DIAMETER: Origin-Realm [296]"cisco.com" (M)65913A20: 01000050 ...P65913A30: 0000011A 00000000 8AC75179 8AC75179 .........GQy.GQy65913A40: 0000010C 4000000C 000007D1 00000108 ....@......Q....65913A50: 4000001B 6469616D 65746572 322E6369 @...diameter2.ci65913A60: 73636F2E 636F6D00 00000128 40000011 sco.com....(@...65913A70: 63697363 6F2E636F 6D000000 00 cisco.com....*May 9 18:05:02.816: Dia Base: Request message hash ctx removed for[2328318329/2328318329]*May 9 18:05:02.816: Dia Base: (C000000C): Received msg event frommessage i/o*May 9 18:05:02.816: Dia Peer FSM (50F63888): input event RCV_DPA instate CLOSING*May 9 18:05:02.816: Dia Base: (C000000C): Free the peer connectioncontext 50F63888Related Commands
debug dlsw
To enable debugging of data-link switching plus (DLSw+), use the debug dlsw command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dlsw [border-peers [interface interface | ip address ip-address] | core [flow-control messages | state | xid] [circuit-number] | local-circuit circuit-number | peers [interface interface [fast-errors | fast-paks] | ip address ip-address [fast-errors | fast-paks | fst-seq | udp]] | reachability [error | verbose] [sna | netbios]
no debug dlsw [border-peers [interface interface | ip address ip-address] | core [flow-control messages | state | xid] [circuit-number] | local-circuit circuit-number | peers [interface interface [fast-errors | fast-paks] | ip address ip-address [fast-errors | fast-paks | fst-seq | udp]] | reachability [error | verbose] [sna | netbios]
Syntax Description
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 events, and is typically used only by service personnel.
To reduce the amount of debug information displayed, use the sna or netbios option 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 exchange identification (XID)-state machine. The router tracks XID commands and responses used in negotiations between end stations before establishing a session.
Examples
The following examples show and explain some of the typical DLSw debugging messages you might see when using the debug dlsw command.
The following example enables UDP packet debugging for a specific remote peer:
Router# debug dlsw peers ip-address 1.1.1.6 udpThe following message is sample output from the debug dlsw border-peers command:
*Mar 10 17:39:56: CSM: delete group mac cache for group 0*Mar 10 17:39:56: CSM: delete group name cache for group 0*Mar 10 17:40:19: CSM: update group cache for mac 0000.3072.1070, group 10*Mar 10 17:40:22: DLSw: send_to_group_members(): copy to peer 10.19.32.5The following message is from a router that initiated a TCP connection:
DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:ADMIN-OPEN CONNECTION state:DISCONNDLSw: dtp_action_a() attempting to connect peer 10.3.8.7(2065)DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:DISCONN->WAIT_WRDLSw: Async Open Callback 10.3.8.7(2065) -> 11002DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR DLSw: dtp_action_f() start read open timer for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_WR->WAIT_RD DLSw: passive open 10.3.8.7(11004) -> 2065 DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD DLSw: dtp_action_g() read pipe opened for peer 10.3.8.7(2065) DLSw: CapExId Msg sent to peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_RD->WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) DLSw: Recv CapExId Msg from peer 10.3.8.7(2065) DLSw: Pos CapExResp sent to peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.3.8.7(2065) DLSw: Recv CapExPosRsp Msg from peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dtp_action_k() cap xchged for peer 10.3.8.7(2065) DLSw: closing read pipe tcp connection for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:WAIT_CAP->PCONN_WT DLSw: Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:TCP-PEER CONNECTED state:PCONN_WT DLSw: dtp_action_m() peer connected for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:PCONN_WT->CONNECT DLSw: START-TPFSM (peer 10.3.8.7(2065)): event:CORE-ADD CIRCUIT state:CONNECT DLSw: dtp_action_u(), peer add circuit for peer 10.3.8.7(2065) DLSw: END-TPFSM (peer 10.3.8.7(2065)): state:CONNECT->CONNECTThe following message is from a router that received a TCP connection:
DLSw: passive open 10.10.10.4(11002) -> 2065 DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-RD PIPE OPENED state:DISCONN DLSw: dtp_action_c() opening write pipe for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:DISCONN->WWR_RDOP DLSw: Async Open Callback 10.10.10.4(2065) -> 11004 DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-WR PIPE OPENED state:WWR_RDOP DLSw: dtp_action_i() write pipe opened for peer 10.10.10.4(2065) DLSw: CapExId Msg sent to peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WWR_RDOP->WAIT_CAP DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.10.10.4(2065) DLSw: Recv CapExId Msg from peer 10.10.10.4(2065) DLSw: Pos CapExResp sent to peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->WAIT_CAP DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dtp_action_j() cap msg rcvd from peer 10.10.10.4(2065) DLSw: Recv CapExPosRsp Msg from peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dtp_action_k() cap xchged for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:WAIT_CAP->PCONN_WT DLSw: dlsw_tcpd_fini() for peer 10.10.10.4(2065) DLSw: dlsw_tcpd_fini() closing write pipe for peer 10.10.10.4 DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-CLOSE WR PIPE state:PCONN_WT DLSw: dtp_action_l() close write pipe for peer 10.10.10.4(2065) DLSw: closing write pipe tcp connection for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:PCONN_WT->PCONN_WT DLSw: Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:TCP-PEER CONNECTED state:PCONN_WT DLSw: dtp_action_m() peer connected for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:PCONN_WT->CONNECT DLSw: START-TPFSM (peer 10.10.10.4(2065)): event:CORE-ADD CIRCUIT state:CONNECT DLSw: dtp_action_u(), peer add circuit for peer 10.10.10.4(2065) DLSw: END-TPFSM (peer 10.10.10.4(2065)): state:CONNECT->CONNECTThe following message is from a router that initiated an FST connection:
DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:ADMIN-OPEN CONNECTION state:DISCONN DLSw: dfstp_action_a() attempting to connect peer 10.10.10.4(0) DLSw: Connection opened for peer 10.10.10.4(0) DLSw: CapExId Msg sent to peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:DISCONN->WAIT_CAP DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dfstp_action_e() cap msg rcvd for peer 10.10.10.4(0) DLSw: Recv CapExPosRsp Msg from peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->WAIT_CAP DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dfstp_action_e() cap msg rcvd for peer 10.10.10.4(0) DLSw: Recv CapExId Msg from peer 10.10.10.4(0) DLSw: Pos CapExResp sent to peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-FSTPFSM (peer 10.10.10.4(0)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dfstp_action_f() cap xchged for peer 10.10.10.4(0) DLSw: END-FSTPFSM (peer 10.10.10.4(0)): state:WAIT_CAP->CONNECTThe following message is from a router that received an FST connection:
DLSw: START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP MSG RCVD state:DISCONN DLSw: dfstp_action_c() cap msg rcvd for peer 10.3.8.7(0) DLSw: Recv CapExId Msg from peer 10.3.8.7(0) DLSw: Pos CapExResp sent to peer 10.3.8.7(0) DLSw: CapExId Msg sent to peer 10.3.8.7(0) DLSw: END-FSTPFSM (peer 10.3.8.7(0)): state:DISCONN->WAIT_CAP DLSw: START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP MSG RCVD state:WAIT_CAP DLSw: dfstp_action_e() cap msg rcvd for peer 10.3.8.7(0) DLSw: Recv CapExPosRsp Msg from peer 10.3.8.7(0) DLSw: END-FSTPFSM (peer 10.3.8.7(0)): state:WAIT_CAP->WAIT_CAP DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP DLSw: START-FSTPFSM (peer 10.3.8.7(0)): event:SSP-CAP EXCHANGED state:WAIT_CAP DLSw: dfstp_action_f() cap xchged for peer 10.3.8.7(0) DLSw: END-FSTPFSM (peer 10.3.8.7(0)): state:WAIT_CAP->CONNECTThe following message is from a router that initiated an LLC2 connection:
DLSw-LLC2: Sending enable port ; port no : 0PEER-DISP Sent : CLSI Msg : ENABLE.Req dlen: 20DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20DLSw-LLC2 : Sending activate sap for Serial1 - port_id = 887C3Cport_type = 7 dgra(UsapID) = 952458PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req dlen: 60DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60DLSw Got ActSapcnf back for Serial1 - port_id = 8978204, port_type = 7, psap_id = 0DLSw: START-LLC2PFSM (peer on interface Serial1): event:ADMIN-OPEN CONNECTION state:DISCONNDLSw: dllc2p_action_a() attempting to connect peer on interface Serial1PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 106DLSw: END-LLC2PFSM (peer on interface Serial1): state:DISCONN->ROS_SENTDLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-REQOPNSTN.CNF state:ROS_SENTDLSw: dllc2p_action_c()PEER-DISP Sent : CLSI Msg : CONNECT.Req dlen: 16DLSw: END-LLC2PFSM (peer on interface Serial1): state:ROS_SENT->CON_PENDDLSw: Peer Received : CLSI Msg : CONNECT.Cfm CLS_OK dlen: 28DLSw: START-LLC2PFSM (peer on interface Serial1): event:CLS-CONNECT.CNF state:CON_PENDDLSw: dllc2p_action_e() send capabilities to peer on interface Serial1PEER-DISP Sent : CLSI Msg : SIGNAL_STN.Req dlen: 8PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 418DLSw: CapExId Msg sent to peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:CON_PEND->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 418DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1DLSw: Recv CapExId Msg from peer on interface Serial1PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 96DLSw: Pos CapExResp sent to peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 96DLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial1DLSw: Recv CapExPosRsp Msg from peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->WAIT_CAPDLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAPDLSw: START-LLC2PFSM (peer on interface Serial1): event:SSP-CAP EXCHANGED state:WAIT_CAPDLSw: dllc2p_action_l() cap xchged for peer on interface Serial1DLSw: END-LLC2PFSM (peer on interface Serial1): state:WAIT_CAP->CONNECTThe following message is from a router that received a Logical Link Control, type 2 (LLC2) connection:
DLSw-LLC2: Sending enable port ; port no : 0PEER-DISP Sent : CLSI Msg : ENABLE.Req dlen: 20DLSw: Peer Received : CLSI Msg : ENABLE.Cfm CLS_OK dlen: 20DLSw-LLC2 : Sending activate sap for Serial0 - port_id = 887C3Cport_type = 7 dgra(UsapID) = 93AB34PEER-DISP Sent : CLSI Msg : ACTIVATE_SAP.Req dlen: 60DLSw: Peer Received : CLSI Msg : ACTIVATE_SAP.Cfm CLS_OK dlen: 60DLSw Got ActSapcnf back for Serial0 - port_id = 8944700, port_type = 7, psap_id = 0DLSw: Peer Received : CLSI Msg : CONECT_STN.Ind dlen: 39DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECT_STN.IND state:DISCONNDLSw: dllc2p_action_s() conn_stn for peer on interface Serial0PEER-DISP Sent : CLSI Msg : REQ_OPNSTN.Req dlen: 106DLSw: END-LLC2PFSM (peer on interface Serial0): state:DISCONN->CONS_PENDDLSw: Peer Received : CLSI Msg : REQ_OPNSTN.Cfm CLS_OK dlen: 106DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-REQOPNSTN.CNF state:CONS_PENDDLSw: dllc2p_action_h() send capabilities to peer on interface Serial0PEER-DISP Sent : CLSI Msg : CONNECT.Rsp dlen: 20PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 418DLSw: CapExId Msg sent to peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:CONS_PEND->WAIT_CAPDLSw: Peer Received : CLSI Msg : CONNECTED.Ind dlen: 8DLSw: START-LLC2PFSM (peer on interface Serial0): event:CLS-CONNECTED.IND state:WAIT_CAPDLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 418DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0DLSw: Recv CapExId Msg from peer on interface Serial0PEER-DISP Sent : CLSI Msg : DATA.Req dlen: 96DLSw: Pos CapExResp sent to peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAPDLSw: Peer Received : CLSI Msg : DATA.Ind dlen: 96DLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP MSG RCVD state:WAIT_CAPDLSw: dllc2p_action_k() cap msg rcvd for peer on interface Serial0DLSw: Recv CapExPosRsp Msg from peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->WAIT_CAPDLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAPDLSw: START-LLC2PFSM (peer on interface Serial0): event:SSP-CAP EXCHANGED state:WAIT_CAPDLSw: dllc2p_action_l() cap xchged for peer on interface Serial0DLSw: END-LLC2PFSM (peer on interface Serial0): state:WAIT_CAP->CONNECTThe following messages occur when a CUR_ex (CANUREACH explorer) frame is received from other peers, and the peer statements or the promiscuous keyword have not been enabled so that the router is not configured correctly:
22:42:44: DLSw: Not promiscuous - Rej conn from 172.20.96.1(2065)22:42:51: DLSw: Not promiscuous - Rej conn from 172.20.99.1(2065)In the following messages, the router sends a keepalive message every 30 seconds to keep the peer connected. If three keepalive messages are missed, the peer is torn down. These messages are displayed only if keepalives are enabled (by default, keepalives are disabled):
22:44:03: DLSw: Keepalive Request sent to peer 172.20.98.1(2065) (168243148)22:44:03: DLSw: Keepalive Response from peer 172.20.98.1(2065) (168243176)22:44:34: DLSw: Keepalive Request sent to peer 172.20.98.1(2065) (168274148)22:44:34: DLSw: Keepalive Response from peer 172.20.98.1(2065) (168274172)The following peer debugging messages indicate that the local peer is disconnecting from the specified remote peer because of missed peer keepalives:
0:03:24: DLSw: keepalive failure for peer on interface Serial00:03:24: DLSw: action_d(): for peer on interface Serial00:03:24: DLSW: DIRECT aborting connection for peer on interface Serial00:03:24: DLSw: peer on interface Serial0, old state CONNECT, new state DISCONNThe following peer debugging messages result from an attempt to connect to an IP address that does not have DLSw enabled. The local router attempts to connect in 30-second intervals:
23:13:22: action_a() attempting to connect peer 172.20.100.1(2065)23:13:22: DLSw: CONN: peer 172.20.100.1 open failed, rejected [9]23:13:22: action_a() retries: 8 next conn time: 86123250423:13:52: action_a() attempting to connect peer 172.20.100.1(2065)23:13:52: DLSw: CONN: peer 172.20.100.1 open failed, rejected [9]23:13:52: action_a() retries: 9 next conn time: 861292536The following peer debugging messages that indicates a remote peer statement is missing on the router (address 172.20.100.1) to which the connection attempt is sent:
23:14:52: action_a() attempting to connect peer 172.20.100.1(2065)23:14:52: DLSw: action_a(): Write pipe opened for peer 172.20.100.1(2065)23:14:52: DLSw: peer 172.20.100.1(2065), old state DISCONN, new state WAIT_RD23:14:52: DLSw: dlsw_tcpd_fini() closing connection for peer 172.20.100.123:14:52: DLSw: action_d(): for peer 172.20.100.1(2065)23:14:52: DLSw: aborting tcp connection for peer 172.20.100.1(2065)23:14:52: DLSw: peer 172.20.100.1(2065), old state WAIT_RD, new state DISCONNThe following messages show a peer connection opening with no errors or abnormal events:
23:16:37: action_a() attempting to connect peer 172.20.100.1(2065)23:16:37: DLSw: action_a(): Write pipe opened for peer 172.20.100.1(2065)23:16:37: DLSw: peer 172.20.100.1(2065), old state DISCONN, new state WAIT_RD23:16:37: DLSW: passive open 172.20.100.1(17762) -> 206523:16:37: DLSw: action_c(): for peer 172.20.100.1(2065)23:16:37: DLSw: peer 172.20.100.1(2065), old state WAIT_RD, new state CAP_EXG23:16:37: DLSw: peer 172.20.100.1(2065) conn_start_time set to 86139778423:16:37: DLSw: CapExId Msg sent to peer 172.20.100.1(2065)23:16:37: DLSw: Recv CapExId Msg from peer 172.20.100.1(2065)23:16:37: DLSw: Pos CapExResp sent to peer 172.20.100.1(2065)23:16:37: DLSw: action_e(): for peer 172.20.100.1(2065)23:16:37: DLSw: Recv CapExPosRsp Msg from peer 172.20.100.1(2065)23:16:37: DLSw: action_e(): for peer 172.20.100.1(2065)23:16:37: DLSw: peer 172.20.100.1(2065), old state CAP_EXG, new state CONNECT23:16:37: DLSw: dlsw_tcpd_fini() closing write pipe for peer 172.20.100.123:16:37: DLSw: action_g(): for peer 172.20.100.1(2065)23:16:37: DLSw: closing write pipe tcp connection for peer 172.20.100.1(2065)23:16:38: DLSw: peer_act_on_capabilities() for peer 172.20.100.1(2065)The following two messages show that an information frame is passing through the router:
DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:5 rs:4 i:34DLSw: dlsw_tr2fct() lmac:c000.a400.0000 rmac:0800.5a29.75fe ls:4 rs:4 i:34Sample debug DLSw Reachability Messages
The messages in this section are based on the following criteria:
•
•
•
•
•
Table 76 describes the debug output indicating that the DLSW router received an SSP message that is flow controlled and should be counted against the window of the sender.
Dec 6 11:26:49: CSM: Received SSP CUR csex flags = 80, mac 4000.90b1.26cf,The csex flags = 80 means that this is an CUR_ex (explorer).Dec 5 10:48:33: DLSw: 1620175180 decr r - s:27 so:0 r:27 ro:0
The following message shows that DLSW is sending an I frame to a LAN:
Dec 5 10:48:33: DISP Sent : CLSI Msg : DATA.Req dlen: 1086The following message shows that DLSW received the I frame from the LAN:
Dec 5 10:48:35: DLSW Received-disp : CLSI Msg : DATA.Ind dlen: 4The following messages show that the reachability cache is cleared:
Router# clear dlsw rea23:44:11: CSM: Clearing CSM cache23:44:11: CSM: delete local mac cache for port 023:44:11: CSM: delete local name cache for port 023:44:11: CSM: delete remote mac cache for peer 023:44:11: CSM: delete remote name cash dlsw reaThe next group of messages show that the DLSW reachability cache is added, and that a name query is perform from the router MARIAN:
23:45:11: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:11: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:11: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:11: CSM: update local cache for name MARIAN , port 5EFBB423:45:11: CSM: Received CLS_UDATA_STN from Core23:45:11: CSM: Received netbios frame type A23:45:11: CSM: Processing Name Query23:45:11: CSM: Netbios Name Query: ws_status = 623:45:11: CSM: Write to peer 0 ok.23:45:11: CSM: Freeing clsi message23:45:11: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:11: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:11: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:11: CSM: update local cache for name MARIAN , port 658AB423:45:11: CSM: Received CLS_UDATA_STN from Core23:45:11: CSM: Received netbios frame type A23:45:11: CSM: Processing Name Query23:45:11: CSM: Netbios Name Query: ws_status = 523:45:11: CSM: DLXNR_PEND match found.... drop name query23:45:11: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:12: CSM: update local cache for name MARIAN , port 5EFBB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:12: CSM: update local cache for name MARIAN , port 658AB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:12: CSM: update local cache for name MARIAN , port 5EFBB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:12: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:12: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:12: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:12: CSM: update local cache for name MARIAN , port 658AB423:45:12: CSM: Received CLS_UDATA_STN from Core23:45:12: CSM: Received netbios frame type A23:45:12: CSM: Processing Name Query23:45:12: CSM: Netbios Name Query: ws_status = 523:45:12: CSM: DLXNR_PEND match found.... drop name query23:45:12: CSM: Freeing clsi message23:45:18: CSM: Deleting Reachability cache23:45:18: CSM: Deleting DLX NR pending record....23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:38: CSM: update local cache for name MARIAN , port 5EFBB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi message23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:38: CSM: update local cache for name MARIAN , port 658AB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi messageThe following messages show that the router named MARIAN is added to the network:
23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 5EFBB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 5EFBB423:45:38: CSM: update local cache for name MARIAN , port 5EFBB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi message23:45:38: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB423:45:38: CSM: 0800.5a30.7a9b passes local mac excl. filter23:45:38: CSM: update local cache for mac 0800.5a30.7a9b, port 658AB423:45:38: CSM: update local cache for name MARIAN , port 658AB423:45:38: CSM: Received CLS_UDATA_STN from Core23:45:38: CSM: Received netbios frame type 823:45:38: CSM: Write to peer 0 ok.23:45:38: CSM: Freeing clsi messageIn the next group of messages, an attempt is made to add the router named GINGER on the Ethernet interface:
0:07:44: CSM: core_to_csm CLSI_MSG_PROC - port_id 658AB40:07:44: CSM: 0004.f545.24e6 passes local mac excl. filter0:07:44: CSM: update local cache for mac 0004.f545.24e6, port 658AB40:07:44: CSM: update local cache for name GINGER , port 658AB40:07:44: CSM: Received CLS_UDATA_STN from Core0:07:44: CSM: Received netbios frame type 80:07:44: CSM: Write to peer 0 ok.In the following example, the output from the show dlsw reachability command indicates that GINGER is on the Ethernet interface and MARIAN is on the Token Ring interface:
Router# show dlsw reachabilityDLSw MAC address reachability cache listMac Addr status Loc. peer/port rif0004.f545.24e6 FOUND LOCAL P007-S000 --no rif--0800.5a30.7a9b FOUND LOCAL P000-S000 06C0.0621.7D00P007-S000 F0F8.0006.A6FC.005F.F100.0000.0000.0000DLSw NetBIOS Name reachability cache listNetBIOS Name status Loc. peer/port rifGINGER FOUND LOCAL P007-S000 --no rif--MARIAN FOUND LOCAL P000-S000 06C0.0621.7D00P007-S000 --no rif--debug dmsp doc-to-fax
Note
To display debugging messages for the doc Media Service Provider (docMSP) TIFF or text2Fax engine, use the debug dmsp doc-to-fax command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dmsp doc-to-fax [text-to-fax | tiff-reader]
no debug dmsp doc-to-fax [text-to-fax | tiff-reader]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug dmsp doc-to-fax command:
Router# debug dmsp doc-to-faxJan 1 04:58:39.898: docmsp_call_setup_request: callid=18Jan 1 04:58:39.902: docmsp_call_setup_request(): ramp data dir=OFFRAMP, conf dir=SRCJan 1 04:58:39.902: docmsp_caps_ind: call id=18, src=17Jan 1 04:58:39.902: docmsp_bridge cfid=5, srccid=18, dstcid=17Jan 1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC, encode out=2Jan 1 04:58:39.902: docmsp_rcv_msp_ev: call id =18, evID = 42Jan 1 04:58:39.902: docmsp_bridge cfid=6, srccid=18, dstcid=15Jan 1 04:58:39.902: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2Jan 1 04:58:39.902: docmsp_process_rcv_data: call id src=0, dst=18Jan 1 04:58:39.902: docmsp_generate_page:Jan 1 04:58:39.902: docmsp_generate_page: new context for Call 18Jan 1 04:58:39.922: docmsp_get_msp_event_buffer:Jan 1 04:58:42.082: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.082: docmsp_process_rcv_data: call id src=15, dst=18Jan 1 04:58:42.082: offramp_data_process:Jan 1 04:58:42.102: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.106: docmsp_process_rcv_data: call id src=15, dst=18Jan 1 04:58:42.106: offramp_data_process:Jan 1 04:58:42.122: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.126: docmsp_process_rcv_data: call id src=15, dst=18Jan 1 04:58:42.126: offramp_data_process:Jan 1 04:58:42.142: docmsp_xmit: call id src=15, dst=18Jan 1 04:58:42.146: docmsp_xmit: call id src=15, dst=18Related Commands
debug dmsp fax-to-doc
Note
To display debugging messages for doc MSP (docMSP) fax-to-doc, use the debug dmsp fax-to-doc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dmsp fax-to-doc [tiff-writer]
no debug dmsp fax-to-doc [tiff-writer]
Syntax Description
tiff-writer
(Optional) Displays debug messages that occur while the DocMSP Component is receiving T4 fax data and producing TIFF packets.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug dmsp fax-to-doc command:
Router# debug dmsp fax-to-doc*Oct 16 08:29:54.487: docmsp_call_setup_request: callid=22*Oct 16 08:29:54.487: docmsp_call_setup_request(): ramp data dir=OFFRAMP, conf dir=SRC*Oct 16 08:29:54.487: docmsp_caps_ind: call id=22, src=21*Oct 16 08:29:54.487: docmsp_bridge cfid=15, srccid=22, dstcid=21*Oct 16 08:29:54.487: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=SRC, encode out=2*Oct 16 08:29:54.487: docmsp_bridge cfid=16, srccid=22, dstcid=17*Oct 16 08:29:54.487: docmsp_bridge(): ramp data dir=OFFRAMP, conf dir=DEST, encode out=2*Oct 16 08:29:54.487: docmsp_xmit: call id src=17, dst=22*Oct 16 08:29:54.487: docmsp_process_rcv_data: call id src=17, dst=22*Oct 16 08:29:54.487: offramp_data_process:*Oct 16 08:29:54.515: docmsp_get_msp_event_buffer:*Oct 16 08:29:56.115: docmsp_call_setup_request: callid=24*Oct 16 08:29:56.115: docmsp_call_setup_request(): ramp data dir=ONRAMP, conf dir=DEST*Oct 16 08:29:56.115: docmsp_caps_ind: call id=24, src=20*Oct 16 08:29:56.115: docmsp_bridge cfid=17, srccid=24, dstcid=20Related Commands
debug dmsp doc-to-fax
Displays debugging messages for the doc Media Service Provider TIFF or text2Fax engine.
debug dmvpn
To display debug Dynamic Multipoint VPN (DMVPN) session information, use the debug dmvpn command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dmvpn {all | error | detail | packet} {all | debug-type}
no debug dmvpn {all | error | detail | packet} {all | debug-type}
Syntax Description
Command Default
DMVPN debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
You must specify both the level and the type of debugging that you want to enable. The debugging levels are all, error, detail, or packet. You can enable NHRP, crypto Internet Key Exchange (IKE) and IPsec, tunnel protection, and crypto secure socket debugging at any of the four debugging levels.
To enable conditional DMVPN debugging, you must first specify the level and type of debugging that you want to enable, and then use the debug dmvpn condition command to specify the conditions that you want to enable.
Error-Level Debugging
When error-level debugging is enabled with the debug dmvpn error command, the following debugging commands are enabled by default:
•
•
•
Detail-Level Debugging
When detail-level debugging is enabled with the debug dmvpn detail command, the following debugging commands are enabled by default:
•
•
•
•
•
•
•
Packet-Level Debugging
When packet-level debugging is enabled with the debug dmvpn packet command, the following debugging commands are enabled by default:
•
•
Note
Examples
The following example shows how to enable all debugging levels for DMVPN tunnel debugging:
Router# debug dmvpn all tunnelRelated Commands
debug dmvpn condition
To display conditional debug Dynamic Multipoint VPN (DMVPN) session information, use the debug dmvpn condition command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dmvpn condition {unmatched | peer {nbma | tunnel {ipv4-address | ipv6-address}} | vrf vrf-name | interface tunnel tunnel-interface}
no debug dmvpn condition [unmatched | peer {nbma | tunnel {ipv4-address | ipv6-address}} | vrf vrf-name | interface tunnel tunnel-interface]
Syntax Description
Command Default
DMVPN conditional debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Conditional debugging is enabled only after the DMVPN debugging type and level have been specified using the debug dmvpn command.
Console Output
The following debug dmvpn commands do not have any console output on the Cisco 3845 and Cisco 7200 series routers:
•
•
•
•
Note
Examples
The following example shows how to enable conditional DMVPN debugging for a specific peer NBMA address:
Router# debug dmvpn condition peer nbma 192.0.2.1The following example shows how to enable conditional DMVPN debugging when context is not available to check against debugging conditions:
Router# debug dmvpn condition unmatchedThe following example shows how to disable conditional debugging for a specific tunnel interface:
Router# no debug dmvpn condition interface tunnel 1The following example shows how to disable all conditional debugging:
Router# no debug dmvpn conditionRelated Commands
debug dot11
To enable debugging of radio functions, use the debug dot11 command in privileged EXEC mode. To stop or disable the debug operation, use the no form of this command.
debug dot11 {events | forwarding | mgmt | packets | syslog | virtual-interface}
no debug dot11 {events | forwarding | mgmt | packets | syslog | virtual-interface}
Syntax Descriptionno debug dot11
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display debugging information about radio functions.
Examples
The following example shows how to enable debugging of all radio-related events:
Router# debug dot11 eventsRelated Commands
debug dot11 aaa
Enables debugging of dot11 AAA operations.
debug dot11 dot11radio
Enables radio debug options.
debug dot11 aaa
To enable debugging of dot11 authentication, authorization, and accounting (AAA) operations, use the debug dot11 aaa command in privileged EXEC mode. To disable or stop the debug operation, use the no form of this command.
debug dot11 aaa {accounting | authenticator {all | dispatcher | mac-authen | process | rxdata | state-machine | txdata} | dispatcher | manager {all | dispatcher | keys | rxdata | state-machine | supplicant | txdata}}
no debug dot11 aaa {accounting | authenticator {all | dispatcher | mac-authen | process | rxdata | state-machine | txdata} | dispatcher | manager {all | dispatcher | keys | rxdata | state-machine | supplicant | txdata}}
Syntax Descriptionno debug dot11
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display debugging information about dot11 AAA operations.
Examples
The following example shows how to activate debugging for 802.11 AAA accounting packets:
Router# debug dot11 aaa accountingRelated Commands
debug dot11
Enables debugging of radio functions.
debug dot11 dot11radio
Enables radio debug options.
debug dot11 cac
Use the debug dot11 cac privileged EXEC command to begin debugging of admission control radio functions. Use the no form of this command to stop the debug operation.
[no] debug dot11 cac
{events | unit}
Note
Syntax Description
events
Activates debugging of radio admission control events.
unit
Activates verbose debugging of radio admission control events.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Examples
This example shows how to begin debugging of all admission control radio-related events:
SOAP-AP# debug dot11 cac eventsThis example shows how to begin verbose debugging of all admission control radio-related events:
SOAP-AP# debug dot11 cac unitThis example shows how to stop debugging of all admission control radio-related events:
SOAP-AP# debug dot11 cac eventsThis example shows how to stop verbose debugging of all admission control radio-related events:
SOAP-AP# no debug dot11 cac unitRelated Commands
debug dot11 dot11radio
To enable radio debug options, use the debug dot11 dot11radio command in privileged EXEC mode. To disable debug options, use the no form of this command.
debug dot11 dot11radio interface {accept-radio-firmware | dfs simulate [channel] | monitor {ack | address | beacon | crc | lines | plcp | print | probe | store} | print {hex | if | iv | lines | mic | plcp | printf | raw | shortadr} | stop-on-failure | trace {off | print | store}}
no debug dot11 dot11radio interface {accept-radio-firmware | dfs simulate [channel] | monitor {ack | address | beacon | crc | lines | plcp | print | probe | store} | print {hex | if | iv | lines | mic | plcp | printf | raw | shortadr} | stop-on-failure | trace {off | print | store}}
Syntax Description
Command Default
Debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display debugging information about radio options.
Examples
This example shows how to begin monitoring of all packets with CRC errors:
Router# debug dot11 dot11radio 0 monitor crcRelated Commands
debug dot11
Enables debugging of radio functions.
debug dot11 aaa
Enables debugging of dot11 AAA operations.
debug dot11 ids
Use the debug dot11 ids eap privileged EXEC command to enable debugging for wireless IDS monitoring. Use the no form of the command to disable IDS debugging.
[no] debug dot11 ids {eap | cipher-errors}
Note
Syntax Description
eap
Activates debugging of IDS authentication events
cipher-errors
Activates debugging of cipher errors detected by IDS
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Examples
This example shows how to activate wireless IDS debugging for authentication events:
SOAP-AP# debug dot11 ids eapRelated Commands
debug dot11 ids mfp
Use the debug dot11 ids mfp privileged EXEC command to debug Management Frame Protection (MFP) operations on the access point.
[no] debug dot11 ids mfp
ap [all] [detectors] [events] [generators] [io] [reporting] |
wds [all] [detectors] [events] [generators] [reporting] [statistics] |
wlccpSyntax Description
Defaults
There are no defaults for this command.
Command Modes
Privileged EXEC (#)
Command History
Examples
This example shows how to debug the MFP detectors on the access point:
ap(config)# debug dot11 ids mfp ap detectorsRelated Commands
dot11 ids mfp
Configures MFP parameters on the access point.
show dot11 ids mfp
Displays MFP parameters on the access point.
debug dot1x
To display 802.1X debugging information, use the debug dot1x command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dot1x [all | errors | events | feature | packets | redundancy | registry | state-machine]
no debug dot1x [all | errors | events | feature | packets | redundancy | registry | state-machine]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output for the debug dot1x command:
Router# debug dot1xRouter-871#debug dot1x all*Nov 7 13:07:56.872: dot1x-ev:dot1x_mgr_pre_process_eapol_pak: Role determination not required on FastEthernet1.*Nov 7 13:07:56.876: dot1x-packet:dot1x_mgr_process_eapol_pak: queuing an EAPOL pkt on Authenticator Q*Nov 7 13:07:56.876: dot1x-ev:Enqueued the eapol packet to the global authenticator queue*Nov 7 13:07:56.876: dot1x-packet:Received an EAPOL frame on interface FastEthernet1*Nov 7 13:07:56.876: dot1x-ev:Received pkt saddr =000f.23c4.a401 , daddr = 0180.c200.0003,pae-ether-type = 888e.0202.0000*Nov 7 13:07:56.876: dot1x-packet:Received an EAPOL-Logoff packet on interface FastEthernet1*Nov 7 13:07:56.876: EAPOL pak dump rx*Nov 7 13:07:56.876: EAPOL Version: 0x2 type: 0x2 length: 0x0000*Nov 7 13:07:56.876: dot1x-sm:Posting EAPOL_LOGOFF on Client=82AC85CC*Nov 7 13:07:56.876: dot1x_auth Fa1: during state auth_authenticating, got event 7(eapolLogoff)The fields in the output are self-explanatory.
Related Commands
debug dot1x (EtherSwitch)
To enable debugging of the 802.1x protocol when an Ethernet switch network module is installed, use the debug dot1x command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dot1x {all | authsm | backend | besm | core | reauthsm}
no debug dot1x {all | authsm | backend | besm | core | reauthsm}
Syntax Description
Defaults
Debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug dot1x command is the same as the no debug dot1x command.
Related Commands
debug drip event
To display debugging messages for Duplicate Ring Protocol (DRiP) events, use the debug drip event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug drip event
no debug drip event
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is disabled for DRiP events.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
When a TrBRF interface is configured on the Remote Switch Module (RSM), the DRiP protocol is activated. The DRiP protocol adds the VLAN ID specified in the router command to its database and recognizes the VLAN as a locally configured, active VLAN.
Examples
The following is sample output from the debug drip event command:
Router# debug drip eventDRiP gets a packet from the network:
612B92C0: 01000C00 00000000 0C501900 0000AAAA .........P....**612B92D0: 0300000C 00020000 00000100 0CCCCCCC .............LLL612B92E0: 00000C50 19000020 AAAA0300 000C0102 ...P... **......612B92F0: 01010114 00000002 00000002 00000C50 ...............P612B9300: 19000001 04C00064 04 .....@.d.DRiP gets a packet from the network:
Recvd. pakDRiP recognizes that the VLAN ID it is getting is a new one from the network:
6116C840: 0100 0CCCCCCC ...LLL6116C850: 00102F72 CBFB0024 AAAA0300 000C0102 ../rK{.$**......6116C860: 01FF0214 0002E254 00015003 00102F72 ......bT..P.../r6116C870: C8000010 04C00014 044003EB 14 H....@...@.k.DRIP : remote update - Never heard of this vlanDRiP attempts to resolve any conflicts when it discovers a new VLAN. The value action = 1 means to notify the local platform of change in state.
DRIP : resolve remote for vlan 20 in VLAN0DRIP : resolve remote - action = 1The local platform is notified of change in state:
DRIP Change notification active vlan 20Another new VLAN ID was received in the packet:
DRIP : resolve remote for vlan 1003 in Vlan0No action is required:
DRIP : resolve remote - action = 0Thirty seconds have expired, and DRiP sends its local database entries to all its trunk ports:
DRIP : local timer expiredDRIP : transmit on 0000.0c50.1900, length = 24612B92C0: 01000C00 00000000 0C501900 0000AAAA .........P....**612B92D0: 0300000C 00020000 00000100 0CCCCCCC .............LLL612B92E0: 00000C50 19000020 AAAA0300 000C0102 ...P... **......612B92F0: 01FF0114 00000003 00000002 00000C50 ...............P612B9300: 19000001 04C00064 04 .....@.d.debug drip packet
To display debugging messages for Duplicate Ring Protocol (DRiP) packets, use the debug drip packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug drip packet
no debug drip packet
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is not enabled for DRiP packets.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Before you use this command, you can optionally use the clear drip command first. As a result the DRiP counters are reset to 0. If the DRiP counters begin to increment, the router is receiving packets.
Examples
The following is sample output from the debug drip packet command:
Router# debug drip packetThe following type of output is displayed when a packet is entering the router and you use the show debug command:
039E5FC0: 0100 0CCCCCCC 00E0A39B 3FFB0028 ...LLL.`#.?{.(039E5FD0: AAAA0300 000C0102 01FF0314 0000A5F6 **............%v039E5FE0: 00008805 00E0A39B 3C000000 04C00028 .....`#.<....@.(039E5FF0: 04C00032 044003EB 0F .@.2.@.k.039FBD20: 01000C00 00000010 ........The following type of output is displayed when a packet is sent by the router:
039FBD30: A6AEB450 0000AAAA 0300000C 00020000 &.4P..**........039FBD40: 00000100 0CCCCCCC 0010A6AE B4500020 .....LLL..&.4P.039FBD50: AAAA0300 000C0102 01FF0114 00000003 **..............039FBD60: 00000002 0010A6AE B4500001 04C00064 ......&.4P...@.d039FBD70: 04 .Related Commands
debug dsc clock
To display debugging output for the time-division multiplexing (TDM) clock-switching events on the dial shelf controller (DSC), use the debug dsc clock command in privileged EXEC mode. To disable debugging output, use the no form of this command.
[execute-on] debug dsc clock
[execute-on] no debug dsc clock
Syntax Description
This command has no arguments or keywords; however, it can be used with the execute-on command.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To perform this command from the router shelf on the Cisco AS5800 series platform, use the execute-on slot slot-number debug dsc clock form of this command.
The debug dsc clock command displays TDM clock-switching events on the dial shelf controller. The information displayed includes the following:
•
•
•
Examples
The following example shows that the debug dsc clock command has been enabled, and that trunk messages are received, and that the configuration message has been received:
AS5800# debug dsc clockDial Shelf Controller Clock debugging is onAS5800#00:02:55: Clock Addition msg of len 12 priority 8 from slot 1 port 1 on line 000:02:55: Trunk 1 has reloadedRelated Commands
execute-on
Executes commands remotely on a line card.
show dsc clock
Displays information about the dial shelf controller clock.
debug dsip
To display debugging output for Distributed System Interconnect Protocol (DSIP) used between a router shelf and a dial shelf, use the debug dsip command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dsip {all | api | boot | console | trace | transport}
no debug dsip {all | api | boot | console | trace | transport}
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug dsip command is used to enable the display of debugging messages for DSIP between the router shelf and the dial shelf. Using this command, you can display booting messages generated when the download of an image occurs, view console operation, and trace logging of MAC header information and DSIP transport layer information as modules interact with the underlying physical media driver. This command can be applied to a single modem or a group of modems.
Once the debug dsip trace command has been enabled, you can read the information captured in the trace buffer using the show dsip tracing command.
Examples
The following example indicates the debug dsip trace command logs MAC headers of the various classes of DSIP packets. To view the logged information, use the show dsip tracing command:
AS5800# debug dsip traceNIP tracing debugging is onAS5800# show dsip tracingNIP Control Packet Trace------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.4c72.0058 Type:200B SrcShelf:1 SrcSlot:11MsgType:0 MsgLen:82 Timestamp: 00:49:14------------------------------------------------------------Dest:00e0.b093.2238 Src:0007.4c72.0028 Type:200B SrcShelf:1 SrcSlot:5MsgType:0 MsgLen:82 Timestamp: 00:49:14------------------------------------------------------------Related Commands
debug dspapi
Note
To enable debugging for Digital Signal Processor (DSP) application programming interface (API) message events, use the debug dspapi command in privileged EXEC mode. To reset the default value for this feature, use the no form of this command.
debug dspapi {all | command | detail | error | notification | response}
no debug dspapi {all | command | detail | error | notification | response}
Syntax Description
Defaults
This command is not enabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
DSP API message events used to communicate with DSPs are intended for use with Connexant (Nextport) and Texas Instrument (54x) DSPs. This command severely impacts performance and should be used only for single-call debug capture.
Examples
The following example shows how to enable debugging for all DSP API message events:
Router# debug dspapi allRelated Commands
debug dspfarm
To display digital signal processor (DSP) farm service debugging information, use the debug dspfarm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dspfarm {all | errors | events | packets}
no debug dspfarm
Syntax Description
all
All DSP-farm debug-trace information.
errors
DSP-farm errors.
events
DSP-farm events.
packets
DSP-farm packets.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The router on which this command is used must be equipped with one or more digital T1/E1 packet voice trunk network modules (NM-HDVs) or high-density voice (HDV) transcoding/conferencing DSP farms (NM-HDV-FARMs) to provide DSP resources.
Debugging is turned on for all DSP-farm-service sessions. You can debug multiple sessions simultaneously, with different levels of debugging for each.
Examples
The following is sample output from the debug dspfarm events command:
Router# debug dspfarm eventsDSP Farm service events debugging is on*Mar 1 00:45:51: Sent 180 bytes to DSP 4 channel 2*Mar 1 00:45:53: Sent 180 bytes to DSP 4 channel 3*Mar 1 00:45:55: Sent 180 bytes to DSP 4 channel 1*Mar 1 00:45:56: Sent 180 bytes to DSP 4 channel 2*Mar 1 00:45:58: Sent 180 bytes to DSP 4 channel 3*Mar 1 00:46:00: Sent 180 bytes to DSP 4 channel 1*Mar 1 00:46:01: xapi_dspfarm_modify_connection: sess_id 26, conn_id 2705, conn_mode 3, ripaddr 10.10.1.7, rport 20170*Mar 1 00:46:01: dspfarm_process_appl_event_queue: XAPP eve 6311C4B0 rcvd*Mar 1 00:46:01: dspfarm_find_stream: stream 63121F1C, found in sess 631143CC, cid 2705*Mar 1 00:46:01: dspfarm_modify_connection: old_mode 4, new_mode 3*Mar 1 00:46:01: dspfarm_close_local_rtp: stream 63121F1C, local_rtp_port 22656*Mar 1 00:46:01: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C4C8, eve_id 5, context 6311426C, result 0*Mar 1 00:46:01: xapi_dspfarm_delete_connection: sess_id 26, conn_id 2705*Mar 1 00:46:01: dspfarm_process_appl_event_queue: XAPP eve 6311C4E0 rcvd*Mar 1 00:46:01: dspfarm_find_stream: stream 63121F1C, found in sess 631143CC, cid 2705*Mar 1 00:46:01: dspfarm_close_local_rtp: stream 63121F1C, local_rtp_port 0*Mar 1 00:46:01: dspfarm_release_dsp_resource: sess 631143CC, stream 63121F1C, num_stream 3, sess_type 2, sess_dsp_id 2040000, stream_dsp_id 2040002*Mar 1 00:46:01: dspfarm_drop_conference:slot 2 dsp 4 ch 2*Mar 1 00:46:01: dspfarm_send_drop_conf: Sent drop_conference to DSP 4 ch 2*Mar 1 00:46:01: dspfarm_xapp_enq: Sent msg 8 to DSPFARM*Mar 1 00:46:01: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C4F8, eve_id 9, context 6311426C, result 0*Mar 1 00:46:01: dspfarm_process_dsp_event_queue: DSP eve 6312078C rcvd*Mar 1 00:46:01: dspfarm_delete_stream: sess_id 26, conn_id 2705, stream 63121F1C, in sess 631143CC is freed*Mar 1 00:46:01: Sent 180 bytes to DSP 4 channel 3*Mar 1 00:46:04: Sent 180 bytes to DSP 4 channel 3*Mar 1 00:46:05: xapi_dspfarm_modify_connection: sess_id 26, conn_id 2689, conn_mode 3, ripaddr 10.10.1.5, rport 19514*Mar 1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C510 rcvd*Mar 1 00:46:05: dspfarm_find_stream: stream 63121E34, found in sess 631143CC, cid 2689*Mar 1 00:46:05: dspfarm_modify_connection: old_mode 4, new_mode 3*Mar 1 00:46:05: dspfarm_close_local_rtp: stream 63121E34, local_rtp_port 25834*Mar 1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C528, eve_id 5, context 63114244, result 0*Mar 1 00:46:05: xapi_dspfarm_delete_connection: sess_id 26, conn_id 2689*Mar 1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C540 rcvd*Mar 1 00:46:05: dspfarm_find_stream: stream 63121E34, found in sess 631143CC, cid 2689*Mar 1 00:46:05: dspfarm_close_local_rtp: stream 63121E34, local_rtp_port 0*Mar 1 00:46:05: dspfarm_release_dsp_resource: sess 631143CC, stream 63121E34, num_stream 2, sess_type 2, sess_dsp_id 2040000, stream_dsp_id 2040001*Mar 1 00:46:05: dspfarm_drop_conference:slot 2 dsp 4 ch 1*Mar 1 00:46:05: dspfarm_send_drop_conf: Sent drop_conference to DSP 4 ch 1*Mar 1 00:46:05: dspfarm_xapp_enq: Sent msg 8 to DSPFARM*Mar 1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C558, eve_id 9, context 63114244, result 0*Mar 1 00:46:05: dspfarm_process_dsp_event_queue: DSP eve 6311586C rcvd*Mar 1 00:46:05: dspfarm_delete_stream: sess_id 26, conn_id 2689, stream 63121E34, in sess 631143CC is freed*Mar 1 00:46:05: xapi_dspfarm_modify_connection: sess_id 26, conn_id 2721, conn_mode 3, ripaddr 10.10.1.6, rport 21506*Mar 1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C570 rcvd*Mar 1 00:46:05: dspfarm_find_stream: stream 63122004, found in sess 631143CC, cid 2721*Mar 1 00:46:05: dspfarm_modify_connection: old_mode 4, new_mode 3*Mar 1 00:46:05: dspfarm_close_local_rtp: stream 63122004, local_rtp_port 19912*Mar 1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C588, eve_id 5, context 63114294, result 0*Mar 1 00:46:05: xapi_dspfarm_delete_connection: sess_id 26, conn_id 2721*Mar 1 00:46:05: dspfarm_process_appl_event_queue: XAPP eve 6311C5A0 rcvd*Mar 1 00:46:05: dspfarm_find_stream: stream 63122004, found in sess 631143CC, cid 2721*Mar 1 00:46:05: dspfarm_close_local_rtp: stream 63122004, local_rtp_port 0*Mar 1 00:46:05: dspfarm_release_dsp_resource: sess 631143CC, stream 63122004, num_stream 1, sess_type 2, sess_dsp_id 2040000, stream_dsp_id 2040003*Mar 1 00:46:05: dspfarm_drop_conference:slot 2 dsp 4 ch 3*Mar 1 00:46:05: dspfarm_drop_conference: Last conferee - closing the conf session*Mar 1 00:46:05: dspfarm_send_close_conf: Sent close_conference to DSP 4*Mar 1 00:46:05: dspfarm_drop_conference: Removed the conf in dsp 4*Mar 1 00:46:05: dspfarm_xapp_enq: Sent msg 8 to DSPFARM*Mar 1 00:46:05: xapi_dspfarm_enqueue_event_to_appl: handle 63120634, event 6311C5B8, eve_id 9, context 63114294, result 0*Mar 1 00:46:05: dspfarm_process_dsp_event_queue: DSP eve 6311586C rcvd*Mar 1 00:46:05: dspfarm_delete_stream: sess_id 26, conn_id 2721, stream 63122004, in sess 631143CC is freedRelated Commands
debug dspu activation
To display information on downstream physical unit (DSPU) activation, use the debug dspu activation command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dspu activation [name]
no debug dspu activation [name]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
The debug dspu activation command displays all DSPU activation traffic. To restrict the output to a specific host or PU, include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu activation command.
Examples
The following is sample output from the debug dspu activation command. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.
Router# debug dspu activationDSPU: LS HOST3745 connectedDSPU: PU HOST3745 activatedDSPU: LU HOST3745-2 activatedDSPU: LU HOST3745-3 activated...DSPU: LU HOST3745-253 activatedDSPU: LU HOST3745-254 activatedDSPU: LU HOST3745-2 deactivatedDSPU: LU HOST3745-3 deactivated...DSPU: LU HOST3745-253 deactivatedDSPU: LU HOST3745-254 deactivatedDSPU: LS HOST3745 disconnectedDSPU: PU HOST3745 deactivatedTable 77 describes the significant fields shown in the display.
Related Commands
debug dspu packet
To display information on a downstream physical unit (DSPU) packet, use the debug dspu packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dspu packet [name]
no debug dspu packet [name]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
The debug dspu packet command displays all DSPU packet data flowing through the router. To restrict the output to a specific host or physical unit (PU), include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu packet command.
Examples
The following is sample output from the debug dspu packet command:
Router# debug dspu packetDSPU: Rx: PU HOST3745 data length 12 data:2D0003002BE16B80 000D0201DSPU: Tx: PU HOST3745 data length 25 data:2D0000032BE1EB80 000D020100850000 000C060000010000 00DSPU: Rx: PU HOST3745 data length 12 data:2D0004002BE26B80 000D0201DSPU: Tx: PU HOST3745 data length 25 data:2D0000042BE2EB80 000D020100850000 000C060000010000 00Table 78 describes the significant fields shown in the display.
Related Commands
debug dspu state
To display information on downstream physical unit (DSPU) finite state machine (FSM) state changes, use the debug dspu state command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dspu state [name]
no debug dspu state [name]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug dspu state command to display only the FSM state changes. To see all FSM activity, use the debug dspu trace command. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu state command.
Examples
The following is sample output from the debug dspu state command. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.
Router# debug dspu stateDSPU: LS HOST3745: input=StartLs, Reset -> PendConOutDSPU: LS HOST3745: input=ReqOpn.Cnf, PendConOut -> XidDSPU: LS HOST3745: input=Connect.Ind, Xid -> ConnInDSPU: LS HOST3745: input=Connected.Ind, ConnIn -> ConnectedDSPU: PU HOST3745: input=Actpu, Reset -> ActiveDSPU: LU HOST3745-2: input=uActlu, Reset -> upLuActiveDSPU: LU HOST3745-3: input=uActlu, Reset -> upLuActive...DSPU: LU HOST3745-253: input=uActlu, Reset -> upLuActiveDSPU: LU HOST3745-254: input=uActlu, Reset -> upLuActiveDSPU: LS HOST3745: input=PuStopped, Connected -> PendDiscDSPU: LS HOST3745: input=Disc.Cnf, PendDisc -> PendCloseDSPU: LS HOST3745: input=Close.Cnf, PendClose -> ResetDSPU: PU HOST3745: input=T2ResetPu, Active -> ResetDSPU: LU HOST3745-2: input=uStopLu, upLuActive -> ResetDSPU: LU HOST3745-3: input=uStopLu, upLuActive -> Reset...DSPU: LU HOST3745-253: input=uStopLu, upLuActive -> ResetDSPU: LU HOST3745-254: input=uStopLu, upLuActive -> ResetTable 79 describes the significant fields shown in the display.
Related Commands
debug drip event
Displays debugging messages for DRiP packets.
debug drip packet
Displays information on DSPU packet.
debug dspu trace
Displays information on DSPU trace activity.
debug dspu trace
To display information on downstream physical unit (DSPU) trace activity, which includes all finite state machine (FSM) activity, use the debug dspu trace command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dspu trace [name]
no debug dspu trace [name]
Syntax Description
Command Modes
Privileged EXEC
Usage Guidelines
Use the debug dspu trace command to display all FSM state changes. To see FSM state changes only, use the debug dspu state command. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu trace command.
Examples
The following is sample output from the debug dspu trace command:
Router# debug dspu traceDSPU: LS HOST3745 input = 0 ->(1,a1)DSPU: LS HOST3745 input = 5 ->(5,a6)DSPU: LS HOST3745 input = 7 ->(5,a9)DSPU: LS HOST3745 input = 9 ->(5,a28)DSPU: LU HOST3745-2 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-3 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-252 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-253 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)DSPU: LS HOST3745 input = 18 ->(8,a17)DSPU: LU HOST3745-254 in:0 s:0->(2,a1)DSPU: LS HOST3745 input = 19 ->(8,a20)Table 80 describes significant fields shown in the output.
Related Commands
debug dss ipx event
To display debugging messages for route change events that affect Internetwork Packet Exchange (IPX) Multilayer Switching (MLS), use the debug dss ipx event command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug dss ipx event
no debug dss ipx event
Syntax Description
This command has no arguments or keywords.
Defaults
Debugging is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug dss ipx event command:
Router# debug dss ipx eventDSS IPX events debugging is onRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# interface vlan 22Router(config-if)# ipx access-group 800 out05:51:36:DSS-feature:dss_ipxcache_version():idb:NULL, reason:42,prefix:0, mask:FFFFFFFF05:51:36:DSS-feature:dss_ipx_access_group():idb:Vlan2205:51:36:DSS-feature:dss_ipx_access_list()05:51:36:DSS-base 05:51:33.834 dss_ipx_invalidate_interface Vl2205:51:36:DSS-base 05:51:33.834 dss_set_ipx_flowmask_reg 205:51:36:%IPX mls flowmask transition from 1 to 2 due to new status ofsimple IPX access list on interfacesRelated Commands
debug eap
To display information about Extensible Authentication Protocol (EAP), use the debug eap command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eap [all | method] [authenticator | peer ] {all | errors | events | packets | sm}
no debug eap [all | method] [authenticator | peer ] {all | errors | events | packets | sm}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following sample output from the debug eap all command shows all EAP information:
Router# debug eap all*Nov 7 13:05:58.512: EAP-EVENT: Received get canned status from lower layer (0x00000000)*Nov 7 13:05:59.460: EAP-EVENT: Received context create from lower layer (0x00000009)*Nov 7 13:05:59.460: eap_authen : initial state eap_auth_initialize has enter*Nov 7 13:05:59.460: EAP-EVENT: Started 'Authenticator Start' timer (1s) for EAP sesion handle 0xD6000008*Nov 7 13:05:59.460: EAP-EVENT: Allocated new EAP context (handle = 0xD6000008)*Nov 7 13:05:59.464: EAP-EVENT: Started EAP tick timer*Nov 7 13:06:00.488: EAP-EVENT: 'Authenticator Start' timer expired for EAP sesion handle 0xD6000008*Nov 7 13:06:00.488: eap_authen : during state eap_auth_initialize, got event 21(eapStartTmo)*Nov 7 13:06:00.488: @@@ eap_authen : eap_auth_initialize -> eap_auth_select_action*Nov 7 13:06:00.488: eap_authen : during state eap_auth_select_action, got event 17(eapDecisionPropose)*Nov 7 13:06:00.488: @@@ eap_authen : eap_auth_select_action -> eap_auth_propose_methodRelated Commands
debug eigrp address-family neighbor
To display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) address family neighbors, use the debug eigrp address-family neighbor command in privileged EXEC mode. To disable debugging of EIGRP service-family neighbors, use the no form of this command.
debug eigrp address-family [ipv4 | ipv6] neighbor [ip-address]
no debug eigrp address-family [ipv4 | ipv6] neighbor [ip-address]
Syntax Description
Command Default
Debugging of EIGRP service-family neighbors is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Consult Cisco technical support before using this command.
Caution
Examples
The following example shows how to enable debugging of an EIGRP address-family neighbor at 10.0.0.0:
Router# debug eigrp address-family ipv4 neighbor 10.0.0.0Neighbor target enabled on AS 3 for 10.0.0.0*Mar 17 15:50:53.244: EIGRP: 10.0.0.0/24 - do advertise out Serial1/2*Mar 17 15:50:53.244: EIGRP: Int 10.0.0.0/24 metric 20512000 -20000000 512000*Mar 17 15:50:53.244: EIGRP: 10.0.0.0/24 - do advertise out Serial1/2*Mar 17 15:50:53.244: EIGRP: Int 10.0.0.0/24 metric 28160 - 256002560*Mar 17 15:50:53.244: EIGRP: 10.0.0.0/24 - do advertise out Serial1/2*Mar 17 15:50:53.244: EIGRP: 10.0.0.0/24 - do advertise out Serial1/2*Mar 17 15:50:53.244: EIGRP: Int 10.0.0.0/24 metric 28160 - 25600256*Mar 17 15:50:53.668: EIGRP: Processing incoming UPDATE packet*Mar 17 15:50:54.544: EIGRP: 10.0.0.0/24 - do advertise out Serial1/1Related Commands
debug eigrp address-family notifications
Displays debugging information about EIGRP event notifications.
debug eigrp address-family notifications
To display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) address family event notifications, use the debug eigrp address-family notifications command in privileged EXEC mode. To disable EIGRP event notification debugging, use the no form of this command.
debug eigrp address-family {ipv4 [autonomous-system-number | vrf [vrf-name] | ip-address] | ipv6 [autonomous-system-number | ip-address]} notifications
no debug eigrp address-family {ipv4 [autonomous-system-number | vrf [vrf-name] | ip-address] | ipv6 [autonomous-system-number | ip-address]} notifications
Syntax Description
Command Default
EIGRP event notification debugging is disabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Consult Cisco technical support before using this command.
Caution
Examples
The following example shows how to enable EIGRP event notification debugging:
Router# debug eigrp address-family ipv4 notifications*Mar 17 15:58:07.144: IP-EIGRP: Callback: reload_iptable*Mar 17 15:58:08.148: IP-EIGRP: iptable_redistribute into eigrp AS 1*Mar 17 15:58:12.144: IP-EIGRP: Callback: redist frm static AS 0 10.0.0.0/24*Mar 17 15:58:12.144: into: eigrp AS 1 event: 1 *Mar 17 15:58:12.144: IP-EIGRP: Callback: redist frm static AS 0 172.16.0.0/24*Mar 17 15:58:12.144: into: eigrp AS 1 event: 1Related Commands
debug eigrp address-family neighbor
Displays debugging information about EIGRP service family neighbors.
debug eigrp fsm
To display debugging information about Enhanced Interior Gateway Routing Protocol (EIGRP) feasible successor metrics (FSMs), use the debug eigrp fsm command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp fsm
no debug eigrp fsm
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command helps you observe EIGRP feasible successor activity and to determine whether route updates are being installed and deleted by the routing process.
Examples
The following is sample output from the debug eigrp fsm command:
Router# debug eigrp fsmDUAL: dual_rcvupdate(): 172.25.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0DUAL: Find FS for dest 172.25.166.0 255.255.255.0. FD is 4294967295, RD is 4294967295 foundDUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/4294967295DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0In the first line, DUAL stands for diffusing update algorithm. It is the basic mechanism within EIGRP that makes the routing decisions. The next three fields are the Internet address and mask of the destination network and the address through which the update was received. The metric field shows the metric stored in the routing table and the metric advertised by the neighbor sending the information. If shown, the term "Metric... inaccessible" usually means that the neighbor router no longer has a route to the destination, or the destination is in a hold-down state.
In the following output, EIGRP is attempting to find a feasible successor for the destination. Feasible successors are part of the DUAL loop avoidance methods. The FD field contains more loop avoidance state information. The RD field is the reported distance, which is the metric used in update, query, or reply packets.
The indented line with the "not found" message means a feasible successor (FS) was not found for 192.168.4.0 and EIGRP must start a diffusing computation. This means it begins to actively probe (sends query packets about destination 192.168.4.0) the network looking for alternate paths to 192.164.4.0.
DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216DUAL: 0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295The following output indicates the route DUAL successfully installed into the routing table:
DUAL: RT installed 172.25.166.0 255.255.255.0 via 0.0.0.0The following output shows that no routes to the destination were discovered and that the route information is being removed from the topology table:
DUAL: Dest 192.168.4.0 255.255.255.0 not entering active state.DUAL: Removing dest 192.168.4.0 255.255.255.0, nexthop 0.0.0.0DUAL: No routes. Flushing dest 192.168.4.0 255.255.255.0debug eigrp neighbor
To display neighbors discovered by the Enhanced Interior Gateway Routing Protocol (EIGRP), use the debug eigrp neighbor command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp neighbor [siatimer] [static]
no debug eigrp neighbor [siatimer] [static]
Syntax Description
Command Default
Debugging for EIGRP neighbors is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug eigrp neighbor command:
Router# debug eigrp neighbor staticEIGRP Static Neighbors debugging is onRouter# configure terminalRouter(config)# router eigrp 100Router(config-router)# neighbor 10.1.1.1 e3/1Router(config-router)#22:40:07:EIGRP:Multicast Hello is disabled on Ethernet3/1!22:40:07:EIGRP:Add new static nbr 10.1.1.1 to AS 100 Ethernet3/1Router(config-router)# no neighbor 10.1.1.1 e3/1Router(config-router)#22:41:23:EIGRP:Static nbr 10.1.1.1 not in AS 100 Ethernet3/1 dynamic list22:41:23:EIGRP:Delete static nbr 10.1.1.1 from AS 100 Ethernet3/122:41:23:EIGRP:Multicast Hello is enabled on Ethernet3/1!Related Commands
debug eigrp notifications
To debug notifications sent from the L2L3 API interface, use the debug eigrp notifications command in privileged EXEC mode. To turn off debugging, use the no form of this command.
debug eigrp notifications {rib | interface}
Syntax Description
rib
Captures notifications from the routing information base (RIB)
interface
Captures notifications from the interface.
Command Default
Debugging of EIGRP notifications for the L2L3 API interface is not enabled.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Consult Cisco technical support before using this command.
Caution
Examples
The following example displays information about the L2L3 API Interface:
Router# debug eigrp notifications ribRelated Commands
debug eigrp nsf
To display nonstop forwarding (NSF) events in the console of the router, use the debug eigrp nsf command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp nsf
no debug eigrp nsf
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The output from the debug eigrp nsf command displays NSF-specific events. This command can be issued on an NSF-capable or NSF-aware router.
Examples
The following example enables Enhanced Interior Gateway Routing Protocol (EIGRP) NSF debugging:
Router# debug eigrp nsfRelated Commands
timers nsf route-hold
Sets the route-hold timer for NSF-aware routers that run EIGRP.
debug eigrp packet
To display debugging information for Enhanced Interior Gateway Routing Protocol (EIGRP) for IPv6 packets, use the debug eigrp packet command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp packet [SIAquery | SIAreply | ack | hello | ipxsap | probe | query | reply | request | retry | stub | terse | update | verbose]
no debug eigrp packet
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If a communication session is closing when it should not be, an end-to-end connection problem can be the cause. The debug eigrp packet command is useful for analyzing the messages traveling between the local and remote hosts.
Note
Examples
The following is sample output from the debug eigrp packet command:
Router# debug eigrp packetEIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Sending HELLO on Ethernet0/1AS 109, Flags 0x0, Seq 0, Ack 0EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x1, Seq 1, Ack 0EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,AS 109, Flags 0x0, Seq 0, Ack 1EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,AS 109, Flags 0x0, Seq 2, Ack 0The output shows transmission and receipt of EIGRP packets. These packet types may be hello, update, request, query, or reply packets. The sequence and acknowledgment numbers used by the EIGRP reliable transport algorithm are shown in the output. Where applicable, the network-layer address of the neighboring router is also included.
Table 81 describes the significant fields shown in the display.
debug eigrp service-family
To troubleshoot an Enhanced Interior Gateway Routing Protocol (EIGRP) service-family external client, client, neighbor, notification, topology, or a VRF instance, use the debug eigrp service-family command in privileged EXEC mode.
debug eigrp service-family
[external-client {client client-label | messages [client-label] | protocol [client-label]}]
| {ipv4 | ipv6} [[vrf vrf-name | autonomous-system-number | service-instance-number] |
| client client-label
| neighbor neighbor-ip-address
| notifications
topology service-instance-number]Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug eigrp service-family external-client client command to display information to help manage clients and TCP connections. Use the debug eigrp service-family external-client messages command to display message content and decoded messages. Use the debug eigrp service-family external-client protocol command to display encode and decode information to help manage the interaction with the Cisco SAF internal API.
Note
Examples
The following is sample output of a Cisco SAF External-Client debugging message:Router# debug eigrp service-family external-client messages *Jun 11 14:25:10.051: 2 found c1 c1 *Jun 11 14:25:10.051: SAF-EC: 100 byte message from c1 *Jun 11 14:25:10.051: 0001 0050 7F5A 9BC7 D285 A1D8 3C54 552F 37AE 655B 0014 0005 2253 4146 2200 *Jun 11 14:25:10.051: 0000 0006 0005 756E 616D 6500 0000 1005 0002 6331 0000 1003 0004 0001 0000 *Jun 11 14:25:10.051: 1001 0002 6331 0000 1004 0004 0000 0005 0008 0014 45F4 57A9 42CF 0556 4077 *Jun 11 14:25:10.051: 7AA3 B94A 703F 1BA3 ACA7 *Jun 11 14:25:10.051: *Jun 11 14:25:10.051: Class: Success Response Method: Register *Jun 11 14:25:10.051: Packet Length: 52 Not including 20 byte Saf Header *Jun 11 14:25:10.051: Magic Cookie: 7F5A9BC7 Transaction ID: D285A1D83C54552F37AE65 Router#5B *Jun 11 14:25:10.051: Realm: 014: Length: 5: "SAF" *Jun 11 14:25:10.051: Keep Alive: 1006: Length: 4: 360000 *Jun 11 14:25:10.051: Client Handle: 1002: Length: 4: 2 *Jun 11 14:25:10.051: Message Integrity: 008: Length: 20: 86839D4C64E36476D743AAF26112D28C32E3DF99 *Jun 11 14:25:10.051: 0101 0034 7F5A 9BC7 D285 A1D8 3C54 552F 37AE 655B 0014 0005 2253 4146 2200 *Jun 11 14:25:10.051: 0000 1006 0004 0005 7E40 1002 0004 0000 0002 0008 0014 8683 9D4C 64E3 6476 *Jun 11 14:25:10.051: D743 AAF2 6112 D28C 32E3 DF99 *Jun 11 14:25:10.055: *Jun 11 14:25:10.055: SAF-EC: kicked timer 360000The following is sample output of a Cisco SAF External-Client debugging protocol message:Router# debug eigrp service-family external-client protocol *Jun 11 14:27:11.467: SAF-EC: attribute found, type: 1005 *Jun 11 14:27:11.467: No error *Jun 11 14:27:11.467: Class: Request Method: Register *Jun 11 14:27:11.467: Packet Length: 80 bytes Not including 20 byte Saf Header *Jun 11 14:27:11.467: Magic Cookie: 7F5A9BC7 Transaction ID: 8F1F3F36EE43784D0DFABEA6 *Jun 11 14:27:11.467: Realm: 014: Length: 5: "SAF" *Jun 11 14:27:11.467: Username: 006: Length: 5: uname *Jun 11 14:27:11.467: Client Label: 1005: Length: 2: c1 *Jun 11 14:27:11.467: Protocol Version: 1003: Length: 4: 10000 *Jun 11 14:27:11.467: Client Name: 1001: Length: 2: c1 *Jun 11 14:27:11.467: Page Size: 1004: Length: 4: 5Router#*Jun 11 14:27:11.467: Message Integrity: 008: Length: 20: AB3D7C39E4E0673B1539750D6E21A79ACFCE51F8 *Jun 11 14:27:11.467: SAF-EC: request start. *Jun 11 14:27:11.467: SAF-EC: client successfully registered. client_handle 3Router#Related Commands
exit-service-family
Exits service-family configuration mode.
router eigrp
Configures the EIGRP process.
service-family
Specifies service-family configuration mode.
debug eigrp transmit
To display transmittal messages sent by the Enhanced Interior Gateway Routing Protocol (EIGRP), use the debug eigrp transmit command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
no debug eigrp transmit [ack] [build] [detail] [link] [packetize] [peerdown] [sia] [startup] [strange]
Syntax Description
Command Default
Debugging for EIGRP transmittal messages is not enabled.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the debug eigrp transmit command:
Router# debug eigrp transmit
