Debug Commands

This chapter contains an alphabetical listing of the debug commands. Documentation for each command includes a brief description of its use, command syntax, usage guidelines, sample output, and a description of that output.

Output formats vary with each debug command. Some generate a single line of output per packet, whereas others generate multiple lines of output per packet. Some generate large amounts of output; others generate only occasional output. Some generate lines of text, and others generate information in field format. Thus, the way the debug commands are documented also varies. For example, for debug commands that generate lines of text, the output is described line by line. For debug commands that generate output in field format, tables are used to describe the fields.

By default, the network server sends the output from the debug commands to the console terminal. Sending output to a terminal (virtual console) produces less overhead than sending it to the console. Use the privileged EXEC command terminal monitor to send output to a terminal. For more information about redirecting output, see the "Using Debug Commands" chapter.

debug aaa authentication

Use the debug aaa authentication command to display information on AAA/TACACS+ authentication. Use the no form of the command to disable debugging output.

Syntax Description

This command has no arguments of keywords.

Command Mode

EXEC

Usage Guidelines

Use this command to see what methods of authentication are being used and what the results of these methods are.

Sample Display

Figure 2-1 shows sample debug aaa authentication output. A single EXEC login that uses the "default" method list and the first method, TACACS+, is displayed. The TACACS+ server sends a GETUSER request to prompt for the username and then a GETPASS request to prompt for the password, and finally a PASS response to indicate a successful login. The number 50996740 is the session ID, which is unique for each authentication. Use this ID number to distinguish between different authentications if several are occuring concurrently.

router# debug aaa authentication
6:50:12: AAA/AUTHEN: create_user user='' ruser='' port='tty19' rem_addr='171.69.60.15' authen_type=1 service=1 priv=1
6:50:12: AAA/AUTHEN/START (0): port='tty19' list='' action=LOGIN service=LOGIN
6:50:12: AAA/AUTHEN/START (0): using "default" list
6:50:12: AAA/AUTHEN/START (50996740): Method=TACACS+
6:50:12: TAC+ (50996740): received authen response status = GETUSER
6:50:12: AAA/AUTHEN (50996740): status = GETUSER
6:50:15: AAA/AUTHEN/CONT (50996740): continue_login
6:50:15: AAA/AUTHEN (50996740): status = GETUSER
6:50:15: AAA/AUTHEN (50996740): Method=TACACS+
6:50:15: TAC+: send AUTHEN/CONT packet
6:50:15: TAC+ (50996740): received authen response status = GETPASS
6:50:15: AAA/AUTHEN (50996740): status = GETPASS
6:50:20: AAA/AUTHEN/CONT (50996740): continue_login
6:50:20: AAA/AUTHEN (50996740): status = GETPASS
6:50:20: AAA/AUTHEN (50996740): Method=TACACS+
6:50:20: TAC+: send AUTHEN/CONT packet
6:50:20: TAC+ (50996740): received authen response status = PASS
6:50:20: AAA/AUTHEN (50996740): status = PASS

debug aaa authorization

Use the debug aaa authorization command to display information on AAA/TACACS+ authorization. Use the no form of the command to disable debugging output.

Syntax Description

This command has no arguments of keywords.

Command Mode

EXEC

Usage Guidelines

Use this command to see what methods of authorization are being used and what the results of these methods are.

Sample Display

Figure 2-2 shows sample debug aaa authorization output. In this display, an EXEC authorization for user "carrel" is performed. On the first line, the username is authorized. On the second and third lines, the AV (attribute value) pairs are authorized. The debug output displays a line for each attribute value pair that is authenticated. Next, the display indicates the authorization method used. The final line in the display indicates the status of the authorization process, in this case, a failure.

2:23:21: AAA/AUTHOR (0): user='carrel'
2:23:21: AAA/AUTHOR (0): send AV service=shell
2:23:21: AAA/AUTHOR (0): send AV cmd*
2:23:21: AAA/AUTHOR (342885561): Method=TACACS+
2:23:21: AAA/AUTHOR/TAC+ (342885561): user=carrel
2:23:21: AAA/AUTHOR/TAC+ (342885561): send AV service=shell
2:23:21: AAA/AUTHOR/TAC+ (342885561): send AV cmd*
2:23:21: AAA/AUTHOR (342885561): Post authorization status = FAIL

Table 2-1 describes attribute value pairs associated with the aaa authorization command which may show up in the debug output.

debug apple arp

Use the debug apple arp EXEC command to enable debugging of the AppleTalk Address Resolution Protocol (AARP). The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

This command is helpful when you experience problems communicating with a node on the network you control (a neighbor). If the debug apple arp display indicates that the router is receiving AARP probes, you can assume that the problem does not reside at the physical layer.

Sample Display

Figure 2-3 shows sample debug apple arp output.

router# debug apple arp
Ether0: AARP: Sent resolve for 4160.26
Ether0: AARP: Reply from 4160.26(0000.0c00.0453) for 4160.154(0000.0c00.8ea9)
Ether0: AARP: Resolved waiting request for 4160.26(0000.0c00.0453)
Ether0: AARP: Reply from 4160.19(0000.0c00.0082) for 4160.154(0000.0c00.8ea9)
Ether0: AARP: Resolved waiting request for 4160.19(0000.0c00.0082)
Ether0: AARP: Reply from 4160.19(0000.0c00.0082) for 4160.154(0000.0c00.8ea9)

Explanations for representative lines of output in Figure 2-3 follow.

The following line indicates that the router has requested the hardware MAC address of the host at network address 4160.26:

Ether0: AARP: Sent resolve for 4160.26

The following line indicates that the host at network address 4160.26 has replied, giving its MAC address (0000.0c00.0453). For completeness, the message also shows the network address to which the reply was sent and its hardware MAC address (also in parentheses).

Ether0: AARP: Reply from 4160.26(0000.0c00.0453) for 4160.154(0000.0c00.8ea9)

The following line indicates that the MAC address request is complete:

Ether0: AARP: Resolved waiting request for 4160.26(0000.0c00.0453)

debug apple domain

Use the debug apple domain EXEC command to enable debugging of the AppleTalk domain activities. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Use the debug apple domain command to observe activity for domains and subdomains. Use this command in conjunction with the debug apple remap command to observe interaction between remapping and domain activity. Messages are displayed when the state of a domain changes, such as creating a new domain, deleting a domain, and updating a domain.

Sample Display

Figure 2-4 shows sample debug apple domain output intermixed with output from the debug apple remap command; the two commands show related events.

router# debug apple domain
router# debug apple remap
AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1
AT-REMAP: ReshuffleRemapList for subdomain 1 
AT-REMAP:  Could not find a remap for cable 3000-3001
AT-DOMAIN: atdomain_DisablePort for Tunnel0
AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]
AT-DOMAIN: Disabling interface Ethernet1 
AT-DOMAIN: atdomain_DisablePort for Ethernet1
AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]
AT-DOMAIN: CleanSubDomain for inbound subdomain 1 
AT-REMAP: Remap for net 70 inbound subdomain 1 has been deleted
AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 
AT-DOMAIN: CleanSubDomain for outbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 Remaped Net 10000
AT-REMAP: Remap for net 50 outbound subdomain 1 has been deleted
AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 
AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 
AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]
AT-DOMAIN: CleanSubDomain for inbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 
AT-DOMAIN: CleanSubDomain for outbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 

Related Command

debug apple remap

debug apple errors

Use the debug apple errors EXEC command to display errors occurring in the AppleTalk network. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

In a stable AppleTalk network, the debug apple errors command produces little output.

To solve encapsulation problems, enable debug apple errors and debug apple packet together.

Sample Display

Figure 2-5 shows sample debug apple errors output when a router is brought up with a zone that does not agree with the zone list of other routers on the network.

router# debug apple errors
%AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19
%AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19
%AT-3-ZONEDISAGREES: Ethernet0: AppleTalk port disabled; zone list incompatible with 4160.19

As Figure 2-5 suggests, a single error message indicates zone list incompatibility; this message is sent out periodically until the condition is corrected or debug apple errors is turned off.

Most of the other messages that debug apple errors can generate are obscure or indicate a serious problem with the AppleTalk network. Some of these other messages follow.

In the following message, RTMPRsp, RTMPReq, ATP, AEP, ZIP, ADSP, or SNMP could replace NBP, and "llap dest not for us" could replace "wrong encapsulation":

Packet discarded, src 4160.12-254,dst 4160.19-254,NBP,wrong encapsulation

In the following message, in addition to invalid echo packet, other possible errors are unsolicited AEP echo reply, unknown echo function, invalid ping packet, unknown ping function, and bad responder packet type.

Ethernet0: AppleTalk packet error; no source address available
AT: pak_reply: dubious reply creation, dst 4160.19
AT: Unable to get a buffer for reply to 4160.19
Processing error, src 4160.12-254,dst 4160.19-254,AEP, invalid echo packet

The debug apple errors command can print out additional messages when other debugging commands are also turned on. When you turn on both debug apple errors and debug apple events, the following message can be generated:

Proc err, src 4160.12-254,dst 4160.19-254,ZIP,NetInfo Reply format is invalid

In the preceding message, in addition to NetInfo Reply format is invalid, other possible errors are NetInfoReply not for me, NetInfoReply ignored, NetInfoReply for operational net ignored, NetInfoReply from invalid port, unexpected NetInfoReply ignored, cannot establish primary zone, no primary has been set up, primary zone invalid, net information mismatch, multicast mismatch, and zones disagree.

When you turn on both debug apple errors and debug apple nbp, the following message can be generated:

Processing error, ...,NBP,NBP name invalid

In the preceding message, in addition to NBP name invalid, other possible errors are NBP type invalid, NBP zone invalid, not operational, error handling brrq, error handling proxy, NBP fwdreq unexpected, No route to srcnet, Proxy to "*" zone, Zone "*" from extended net, No zone info for "*", and NBP zone unknown.

When you turn on both debug apple errors and debug apple routing, the following message can be generated:

Processing error, ...,RTMPReq, unknown RTMP request

In the preceding message, in addition to unknown RTMP request, other possible errors are RTMP packet header bad, RTMP cable mismatch, routed RTMP data, RTMP bad tuple, and Not Req or Rsp.

debug apple events

Use the debug apple events EXEC command to display information about AppleTalk special events, neighbors becoming reachable/unreachable, and interfaces going up/down. Only significant events (for example, neighbor and route changes) are logged. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

The debug apple events command is useful for solving AppleTalk network problems because it provides an overall picture of the stability of the network. In a stable network, the debug apple events command does not return any information. If the command generates numerous messages, those messages can indicate possible sources of the problems.

When configuring or making changes to a router or interface for AppleTalk, enable debug apple events. Doing so alerts you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.

The debug apple events command is also useful to determine whether network flapping (nodes toggling online and offline) is occurring. If flapping is excessive, look for routers that only support 254 networks.

When you enable debug apple events, you will see any messages that the configuration command apple event-logging normally displays. Turning on debug apple events, however, does not cause apple event-logging to be maintained in nonvolatile memory. Only turning on apple event-logging explicitly stores it in nonvolatile memory. Furthermore, if apple event-logging is already enabled, turning on or off debug apple events does not affect apple event-logging.

Sample Display

Figure 2-6 shows sample debug apple events output that describes a nonseed router coming up in discovery mode.

Figure 2-6: Sample Debug Apple Events Output with Discovery Mode State Changes

As Figure 2-6 shows, the debug apple events command is useful in tracking the discovery mode state changes through which an interface progresses. When no problems are encountered, the state changes progress as follows:

1. Line down
   
   
2. Restarting
   
   
3. Probing (for its own address [node ID] using AARP)
   
   
4. Acquiring (sending out GetNetInfo requests)
   
   
5. Requesting zones (the list of zones for its cable)
   
   
6. Verifying (that the router's configuration is correct. If not, a port configuration mismatch is declared.)
   
   
7. Checking zones (to make sure its list of zones is correct)
   
   
8. Operational (participating in routing)
   

Explanations for individual lines of output in Figure 2-6 follow.

The following message indicates that a port is set. In this case, the zone multicast address is being reset:

Ether0: AT: Resetting interface address filters

The following messages indicate that the router is changing to restarting mode:

%AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restarted
Ether0: AppleTalk state changed; unknown -> restarting

The following message indicates that the router is probing in the startup range of network numbers (65280-65534) to discover its network number:

Ether0: AppleTalk state changed; restarting -> probing

The following message indicates that the router is enabled as a nonrouting node using a provisional network number within its startup range of network numbers. This type of message only appears if the network address the router will use differs from its configured address. This is always the case for a discovery-enabled router; it is rarely the case for a nondiscovery-enabled router.

%AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148

The following messages indicate that the router is sending out GetNetInfo requests to discover the default zone name and the actual network number range in which its network number can be chosen:

Ether0: AppleTalk state changed; probing -> acquiring
%AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configuration

Now that the router has acquired the cable configuration information, the following message indicates that it restarts using that information:

Ether0: AppleTalk state changed; acquiring -> restarting

The following messages indicate that the router is probing for its actual network address:

Ether0: AppleTalk state changed; restarting -> line down
Ether0: AppleTalk state changed; line down -> restarting
Ether0: AppleTalk state changed; restarting -> probing

The following message indicates that the router has found an actual network address to use:

%AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 4160.148

The following messages indicate that the router is sending out GetNetInfo requests to verify the default zone name and the actual network number range from which its network number can be chosen:

Ether0: AppleTalk state changed; probing -> acquiring
%AT-6-ACQUIREMODE: Ether0: AT port initializing; acquiring net configuration

The following message indicates that the router is requesting the list of zones for its cable:

Ether0: AppleTalk state changed; acquiring -> requesting zones

The following messages indicate that the router is sending out GetNetInfo requests to make sure its understanding of the configuration is correct:

Ether0: AppleTalk state changed; requesting zones -> verifying
AT: Sent GetNetInfo request broadcast on Ethernet0

The following message indicates that the router is rechecking its list of zones for its cable:

Ether0: AppleTalk state changed; verifying -> checking zones

The following message indicates that the router is now fully operational as a routing node and can begin routing:

Ether0: AppleTalk state changed; checking zones -> operational

Figure 2-7 shows sample debug apple events output that describes a nondiscovery-enabled router coming up when no other router is on the wire.

Figure 2-7: Sample Debug Apple Events Output Showing Seed Coming Up by Itself

As Figure 2-7 shows, a nondiscovery-enabled router can come up when no other router is on the wire; however, it must assume that its configuration (if accurate syntactically) is correct, because no other router can verify it. Notice that the last line in Figure 2-7 indicates this situation.

Figure 2-8 shows sample debug apple events output that describes a discovery-enabled router coming up when there is no seed router on the wire.

router# debug apple events
Ether0: AT: Resetting interface address filters
%AT-5-INTRESTART: Ether0: AppleTalk port restarting; protocol restarted
Ether0: AppleTalk state changed; unknown -> restarting
Ether0: AppleTalk state changed; restarting -> probing
%AT-6-ADDRUSED: Ether0: AppleTalk node up; using address 65401.148
Ether0: AppleTalk state changed; probing -> acquiring
AT: Sent GetNetInfo request broadcast on Ether0
AT: Sent GetNetInfo request broadcast on Ether0
AT: Sent GetNetInfo request broadcast on Ether0
AT: Sent GetNetInfo request broadcast on Ether0
AT: Sent GetNetInfo request broadcast on Ether0

As Figure 2-8 shows, when you attempt to bring up a nonseed router without a seed router on the wire, it never becomes operational; instead, it hangs in the acquiring mode and continues to send out periodic GetNetInfo requests.

Figure 2-9 shows sample debug apple events output when a nondiscovery-enabled router is brought up on an AppleTalk internetwork that is in compatibility mode (set up to accommodate extended as well as nonextended AppleTalk) and the router has violated internetwork compatibility.

Figure 2-9: Sample Debug Apple Events Output Showing Compatibility Conflict

The three configuration command lines that follow indicate the part of the router's configuration that caused the configuration mismatch shown in Figure 2-9:

lestat(config)#int e 0
lestat(config-if)#apple cab 41-41
lestat(config-if)#apple zone Marketign

The router shown in Figure 2-9 had been configured with a cable range of 41-41 instead of 40-40, which would have been accurate. Additionally, the zone name was configured incorrectly; it should have been "Marketing," rather than being misspelled as "Marketign."

debug apple nbp

Use the debug apple nbp EXEC command to display debugging output from the Name Binding Protocol (NBP) routines. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

To determine whether the router is receiving NBP lookups from a node on the AppleTalk network, enable debug apple nbp at each node between the router and the node in question to determine where the problem lies.

Sample Display

Figure 2-10 shows sample debug apple nbp output.

router# debug apple nbp
AT: NBP ctrl = LkUp, ntuples = 1, id = 77
AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW Lab
AT: LkUp =:ciscoRouter@Low End SW Lab
AT: NBP ctrl = LkUp-Reply, ntuples = 1, id = 77
AT: 4160.154, skt 254, enum 1, name: lestat.Ether0:ciscoRouter@Low End SW Lab
AT: NBP ctrl = LkUp, ntuples = 1, id = 78
AT: 4160.19, skt 2, enum 0, name: =:IPADDRESS@Low End SW Lab
AT: NBP ctrl = LkUp, ntuples = 1, id = 79
AT: 4160.19, skt 2, enum 0, name: =:IPGATEWAY@Low End SW Lab
AT: NBP ctrl = LkUp, ntuples = 1, id = 83
AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW Lab
AT: LkUp =:ciscoRouter@Low End SW Lab
AT: NBP ctrl = LkUp, ntuples = 1, id = 84
AT: 4160.19, skt 2, enum 0, name: =:IPADDRESS@Low End SW Lab
AT: NBP ctrl = LkUp, ntuples = 1, id = 85
AT: 4160.19, skt 2, enum 0, name: =:IPGATEWAY@Low End SW Lab
AT: NBP ctrl = LkUp, ntuples = 1, id = 85
AT: 4160.19, skt 2, enum 0, name: =:IPGATEWAY@Low End SW Lab

The first three lines in Figure 2-10 describe an NBP lookup request:

AT: NBP ctrl = LkUp, ntuples = 1, id = 77
AT: 4160.19, skt 2, enum 0, name: =:ciscoRouter@Low End SW Lab
AT: LkUp =:ciscoRouter@Low End SW Lab

Table 2-2 describes the fields in the first line of output shown in Figure 2-10.

Table 2-3 describes the fields in the second line of output shown in Figure 2-10.

The third line in Figure 2-10 essentially reiterates the information in the two lines above it, indicating that a lookup request has been made regarding name-address pairs for all objects of the ciscoRouter type in the Low End SW Lab zone.

Because the router is defined as an object of type ciscoRouter in zone Low End SW Lab, the router sends an NBP lookup reply in response to this NBP lookup request. The following two lines of output from Figure 2-10 show the router's response:

AT: NBP ctrl = LkUp-Reply, ntuples = 1, id = 77
AT: 4160.154, skt 254, enum 1, name: lestat.Ether0:ciscoRouter@Low End SW Lab

In the first line, ctrl = LkUp-Reply identifies this NBP packet as an NBP lookup request. The same value in the id field (id = 77) associates this lookup reply with the previous lookup request. The second line indicates that the network address associated with the router's entity name (lestat.Ether0:ciscoRouter@Low End SW Lab) is 4160.154. The fact that no other entity name/network address is listed indicates that the responder only knows about itself as an object of type ciscoRouter in zone Low End SW Lab.

debug apple packet

Use the debug apple packet EXEC command to display per-packet debugging output. The output reports information online when a packet is received or a transmit is attempted. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

With this command, you can monitor the types of packets being slow switched. It displays at least one line of debugging output per AppleTalk packet processed.

When invoked in conjunction with the debug apple routing, debug apple zip, and debug apple nbp commands, the debug apple packet command adds protocol processing information in addition to generic packet details. It also reports successful completion or failure information.

When invoked in conjunction with the debug apple errors command, the debug apple packet command reports packet-level problems, such as those concerning encapsulation.

Sample Display

Figure 2-11 shows sample debug apple packet output.

router# debug apple packet
Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000
AT: src=Ethernet0:4160.47, dst=4160-4160, size=10, 2 rtes, RTMP pkt sent
AT: ZIP Extended reply rcvd from 4160.19
AT: ZIP Extended reply rcvd from 4160.19
AT: src=Ethernet0:4160.47, dst=4160-4160, size=10, 2 rtes, RTMP pkt sent
Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000
Ether0: AppleTalk packet: enctype SNAP, size 60, encaps000000000000000000000000

Table 2-4 describes the fields in the first line of output shown in Figure 2-11.

Table 2-5 describes the fields in the second line of output shown in Figure 2-11.

The third line in Figure 2-11 indicates the type of packet received and its source AppleTalk address. This message is repeated in the fourth line because AppleTalk hosts can send multiple replies to a given GetNetInfo request.

debug apple remap

Use the debug apple remap EXEC command to enable debugging of the AppleTalk remap activities. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Use the debug apple remap command with the debug apple domain command to observe activity between domains and subdomains. Messages from debug apple remap are displayed when a particular remapping function occurs, such as creating remaps or deleting remaps.

Sample Display

Figure 2-12 shows sample debug apple remap output intermixed with output from the debug apple domain command; the two commands show related events.

router# debug apple remap
router# debug apple domain
AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1
AT-REMAP: ReshuffleRemapList for subdomain 1 
AT-REMAP:  Could not find a remap for cable 3000-3001
AT-DOMAIN: atdomain_DisablePort for Tunnel0
AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]
AT-DOMAIN: Disabling interface Ethernet1 
AT-DOMAIN: atdomain_DisablePort for Ethernet1
AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]
AT-DOMAIN: CleanSubDomain for inbound subdomain 1 
AT-REMAP: Remap for net 70 inbound subdomain 1 has been deleted
AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 
AT-DOMAIN: CleanSubDomain for outbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-REMAP: RemapProcess for net 30000 domain AURP Domain 1 Remaped Net 10000
AT-REMAP: Remap for net 50 outbound subdomain 1 has been deleted
AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 
AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 
AT-DOMAIN: CleanUpDomain for domain 1 [AURP Domain 1]
AT-DOMAIN: CleanSubDomain for inbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-DOMAIN: DeleteAvRemapList for inbound subdomain 1 
AT-DOMAIN: CleanSubDomain for outbound subdomain 1 
AT-DOMAIN: DeleteRemapTable for subdomain 1 
AT-DOMAIN: DeleteAvRemapList for outbound subdomain 1 

Related Command

debug apple domain

debug apple routing

Use the debug apple routing EXEC command to enable debugging output from the Routing Table Maintenance Protocol (RTMP) routines. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

This command can be used to monitor acquisition of routes, aging of routing table entries, and advertisement of known routes. It also reports conflicting network numbers on the same network if the network is misconfigured.

Sample Display

Figure 2-13 shows sample debug apple routing output.

router# debug apple routing
AT: src=Ethernet0:4160.41, dst=4160-4160, size=19, 2 rtes, RTMP pkt sent
AT: src=Ethernet1:41069.25, dst=41069, size=427, 96 rtes, RTMP pkt sent
AT: src=Ethernet2:4161.23, dst=4161-4161, size=427, 96 rtes, RTMP pkt sent
AT: Route ager starting (97 routes)
AT: Route ager finished (97 routes)
AT: RTMP from 4160.19 (new 0,old 94,bad 0,ign 0, dwn 0)
AT: RTMP from 4160.250 (new 0,old 0,bad 0,ign 2, dwn 0)
AT: RTMP from 4161.236 (new 0,old 94,bad 0,ign 1, dwn 0)
AT: src=Ethernet0:4160.41, dst=4160-4160, size=19, 2 rtes, RTMP pkt sent

Explanations for representative lines of the debug apple routing output in Figure 2-13 follow.

Table 2-6 describes the fields in the first line of sample debug apple routing output.

AT: Route ager starting (97 routes)
AT: Route ager finished (97 routes)

Table 2-7 describes the fields in the following line of debug apple routing output.

AT: RTMP from 4160.19 (new 0,old 94,bad 0,ign 0, dwn 0)

debug apple zip

Use the debug apple zip EXEC command to display debugging output from the Zone Information Protocol (ZIP) routines. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

This command reports significant events such as the discovery of new zones and zone list queries. It generates information similar to that generated by debug apple routing, but generates it for ZIP packets instead of RTMP packets.

You can use he debug apple zip command to determine whether a ZIP storm is taking place in the AppleTalk network. You can detect the existence of a ZIP storm when you see that no router on a cable has the zone name corresponding to a network number that all the routers have in their routing tables.

Sample Display

Figure 2-14 shows sample debug apple zip output.

router# debug apple zip
AT: Sent GetNetInfo request broadcast on Ether0
AT: Recvd ZIP cmd 6 from 4160.19-6
AT: 3 query packets sent to neighbor 4160.19
AT: 1 zones for 31902, ZIP XReply, src 4160.19
AT: net 31902, zonelen 10, name US-Florida

Explanations of the lines of output shown in Figure 2-14 follow.

The first line indicates that the router has received an RTMP update that includes a new network number and is now requesting zone information:

AT: Sent GetNetInfo request broadcast on Ether0

The second line indicates that the neighbor at address 4160.19 replies to the zone request with a default zone:

AT: Recvd ZIP cmd 6 from 4160.19-6

The third line indicates that the router responds with three queries to the neighbor at network address 4160.19 for other zones on the network:

AT: 3 query packets sent to neighbor 4160.19

The fourth line indicates that the neighbor at network address 4160.19 responds with a ZIP extended reply, indicating that one zone has been assigned to network 31902:

AT: 1 zones for 31902, ZIP XReply, src 4160.19

The fifth line indicates that the router responds that the zone name of network 31902 is US-Florida, and the zone length of that zone name is 10:

AT: net 31902, zonelen 10, name US-Florida

debug appn all

Use the debug appn all command to turn on all possible debugging messages for Advanced Peer-to-Peer Networking (APPN). The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command shows all APPN events. Use other forms of the debug appn command to display specific types of events.

Caution  Debugging output takes priority over other network traffic. The debug appn all command generates more output than any other debug appn command and can alter timing in the network node. This command can severely diminish router performance or even render it unusable. In virtually all cases, it is best to use specific debug appn commands.

Related Commands

debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn ss
debug appn trs

debug appn cs

Use the debug appn cs command to display APPN Configuration Services (CS) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Configuration Services (CS) component is responsible for defining link stations, ports, and connection networks. It is responsible for the activation and deactivation of ports and link stations and handles status queries for these resources.

Sample Display

Figure 2-15 shows sample debug appn cs output. In this example a link station is being stopped.

router# debug appn cs
Turned on event 008000FF
router# appn stop link PATTY
APPN: ----- CS  ----- Deq STOP_LS message
APPN: ----- CS  ----- FSM LS: 75 17 5  8 
APPN: ----- CS  ----- Sending DEACTIVATE_AS - station PATTY
APPN: ----- CS  ----- deactivate_as_p->ips_header.lpid = A80A60
APPN: ----- CS  ----- deactivate_as_p->ips_header.lpid = A80A60
APPN: ----- CS  ----- Sending DESTROY_TG to PC - station PATTY - lpid=A80A60
APPN: ----- CS  ----- Deq DESTROY_TG - station PATTY
APPN: ----- CS  ----- FSM LS: 22 27 8  0 
APPN: ----- CS ----- Sending TG update for LS PATTY to TRS
APPN: ----- CS  ----- ENTERING XID_PROCESSING: 4 
%APPN-6-APPNSENDMSG: Link Station PATTY stopped

Table 2-8 shows describes the fields and messages shown in Figure 2-15.

Related Commands

debug appn all
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn ss
debug appn trs

debug appn ds

Use the debug appn ds command to to display debugging information on APPN Directory Services (DS) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Directory Services (DS) component manages searches for resources in the APPN network. DS is also responsible for registration of resources within the network.

Sample Display

Figure 2-16 shows sample debug appn ds output. In this example a search has been received.

router# debug appn ds
Turned on event 080000FF
APPN: NEWDS: LS: search from: NETA.PATTY
APPN: NEWDS: pcid: DD3321E8B5667111
APPN: NEWDS: Invoking FSM NNSolu
APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 0 col: 0 inp: 80200000
APPN: NEWDS: LSfsm_parent: 00A89940 row: 0 col: 0 inp: 80000000
APPN: NEWDS: Rcvd a LMRQ
APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 12 col: 1 inp: 40000000
APPN: NEWDS: LSfsm_parent: 00A89940 row: 8 col: 1 inp: 40000000
APPN: NEWDS: LSfsm_child: 00A89BE8 row: 0 col: 0 inp: 80000080
APPN: NEWDS: PQenq REQUEST_ROUTE(RQ) to TRS
APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 1 col: 0 inp: 80000008
APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 5 col: 1 inp: 80C04000
APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 7 col: 1 inp: 80844008
APPN: NEWDS: Rcvd a LMRY
APPN: NEWDS: LSfsm_NNSolu: 00A67AA0 pcid: DD3321E8B5667111 row: 16 col: 6 inp: 40800000
APPN: NEWDS: LSfsm_child: 00A8A1C0 row: 14 col: 5 inp: 40800000
APPN: NEWDS: LSfsm_parent: 00A89940 row: 3 col: 1 inp: 80840000
APPN: NEWDS: send locate to node: NETA.PATTY

Table 2-9 provides explanations for fields in the debug appn ds output shown in Figure 2-16.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn ss
debug appn trs

debug appn ms

Use the debug appn ms command to display to display debugging information on APPN Management Services (MS) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Management Services (MS) component is responsible for generating, sending, and forwarding network management information in the form of traps and alerts to a network management focal point, such as Netview, in the APPN network.

Sample Display

Figure 2-17 shows sample debug appn ms output. In this example an error occurred that caused an alert to be generated.

router# debug appn ms
APPN: ----- MSS00 ----  Deq ALERT_MSU msg
APPN: --- MSP70 --- ALERT MV FROM APPN WITH VALID LGTH 
APPN: --- MSCPL --- Find Active FP
APPN: --- MSP30 --- Entering Build MS Transport
APPN: --- MSP31 --- Entering Building Routing Info.
APPN: --- MSP34 --- Entering Build GDS
APPN: --- MSP32 --- Entering Building UOW correlator
APPN: --- MSP34 --- Entering Build GDS
APPN: --- MSP30 --- Building GDS 0x1310
APPN: --- MSP30 --- Building MS Transport
APPN: --- MSP72 --- ACTIVE FP NOT FOUND, SAVE ONLY  
APPN: --- MSUTL --- UOW <= 60, ALL COPIED in extract_uow
APPN: --- MSCAT --- by enq_cached_ms QUEUE SIZE OF QUEUE after enq 4

Table 2-10 describes fields in the debug appn ms output shown in Figure 2-17.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn ss
debug appn trs

debug appn nof

Use the debug appn nof command to display debugging information on APPN Node Operator Facility (NOF) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Node Operator Facility (NOF) component is responsible for processing commands entered by the user such as start, stop, show, and configuration commmands. NOF forwards these commands to the proper component and wait for the response.

Sample Display

Figure 2-18 shows sample debug appn nof output. In this example an APPN connection network is being defined.

router# debug appn nof
Turned on event 010000FF
router# config term
Enter configuration commands, one per line.  End with CNTL/Z.
router(config)#appn connection-network NETA.CISCO
router(config-appn-cn)#port TR0
router(config-appn-cn)#complete
router(config)#
APPN: ----- NOF ----- Define Connection Network Verb Received
APPN: ----- NOF ----- send define_cn_t ips to cs   
APPN: ----- NOF ----- waiting for define_cn rsp from cs   
router(config)#

Table 2-11 describes fields in the debug appn nof output shown in Figure 2-18.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn pc
debug appn ps
debug appn scm
debug appn ss
debug appn trs

debug appn pc

Use the debug appn pc command to display debugging information on APPN Path Control (PC) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Path Control (PC) component is responsible for passing Message Units (MUs) between the Data Link Control (DLC) layer and other APPN components. PC implements transmission priority by passing higher priority MUs to the DLC before lower priority MUs.

Sample Display

Figure 2-19 shows sample debug appn pc output. In this example a MU is received from the network.

router# debug appn pc
Turned on event 040000FF
APPN: ----- PC ----- PC Deq REMOTE msg variant_name 2251
APPN: --PC-- mu received to PC lpid: A80AEC
APPN: --PC-- mu received from p_cep_id: 67C6F8
APPN: ----- PC ----- PC Deq LSA_IPS from DLC
APPN: --PCX dequeued a DATA.IND
APPN: --- PC processing DL_DATA.ind 
APPN: --PC-- mu_error_checker with no error, calling frr
APPN: --PC-- calling frr for packet received on LFSID: 1 2 3
APPN: ----- PC ----- PC is sending MU to SC A90396
APPN: ----- SC ----- send mu: A90396, rpc: 0, nws: 7, rh.b1: 90
APPN: SC: Send mu.snf: 8, th.b0: 2E, rh.b1: 90, dcf: 8

Table 2-12 describes fields in the debug appn pc output shown in Figure 2-19.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn ss
debug appn trs

debug appn ps

Use the debug appn ps command to display debugging information on APPN Presentation Services (PS) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Presentation Services (PS) component is responsible for managing the Transaction Programs (TPs) used by APPN. TPs are used for sending and receiving searches, receiving resource registration, and sending and receiving topology updates.

Sample Display

Figure 2-20 shows sample debug appn ps output. In this example a CP capabilities exchange is in progress.

router# debug appn ps
Turned on event 200000FF
APPN: ---- CCA --- CP_CAPABILITIES_TP has started
APPN: ---- CCA --- About to wait for Partner to send CP_CAP
APPN: ---- CCA --- Partner LU name: NETA.PATTY
APPN: ---- CCA --- Mode Name: CPSVCMG
APPN: ---- CCA --- CGID: 78
APPN: ---- CCA --- About to send cp_cp_session_act to SS
APPN: ---- CCA --- Waiting for cp_cp_session_act_rsp from SS
APPN: ---- CCA --- Received cp_cp_session_act_rsp from SS
APPN: ---- CCA --- About to send CP_CAP to partner
APPN: ---- CCA --- Send to partner completed with rc=0, 0
APPN: ---- RCA --- Allocating conversation
APPN: ---- RCA --- Sending CP_CAPABILITIES
APPN: ---- RCA --- Getting conversation attributes
APPN: ---- RCA --- Waiting for partner to send CP_CAPABILITIES
APPN: ---- RCA --- Normal processing complete with cgid = 82
APPN: ---- RCA --- Deallocating CP_Capabilities conversation

Table 2-13 describes fields in the debug appn ps output shown in Figure 2-20.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn scm
debug appn ss
debug appn trs

debug appn scm

Use the debug appn scm command to display debugging information on APPN Session Connector Manager (SCM) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Session Connector Manager (SCM) component is responsible for the activation and deactivation the local resources that route an intermediate session through the router.

Sample Display

Figure 2-21 shows sample debug appn scm output. In this example an intermediate session traffic is being routed.

router# debug appn scm 
Turned on event 020000FF
router#
APPN: ----- SCM ----- SCM Deq a MU
APPN: ----- SCM ----- SCM send ISR_INIT to SSI
APPN: ----- SCM ----- (i05) Enter compare_fqpcid()
APPN: ----- SCM ----- Adding new session_info table entry. addr=A93160
APPN: ----- SCM ----- SCM Deq ISR_CINIT message
APPN: ----- SCM ----- (i05) Enter compare_fqpcid()
APPN: ----- SCM ----- SCM sends ASSIGN_LFSID to ASM
APPN: ----- SCM ----- SCM Rcvd sync ASSIGN_LFSID from ASM
APPN: ----- SCM ----- SCM PQenq a MU to ASM
APPN: ----- SCM ----- SCM Deq a MU
APPN: ----- SCM ----- (i05) Enter compare_fqpcid()
APPN: ----- SCM ----- SCM PQenq BIND rsp to ASM

Table 2-14 describes fields in the debug appn ps output shown in Figure 2-21.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn ss
debug appn trs

debug appn ss

Use the debug appn ss command to display session services events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Session Services (SS) component generates unique session identifiers, activates and deactivates control point-to-control point (CP-CP) sessions, and assists LUs in initiating and activating LU-LU sessions.

Sample Display

Figure 2-22 shows sample debug appn ss output. In this example CP-CP sessions between the router and another node are being activated.

router# debug appn ss 
Turned on event 100000FF
APPN: ----- SS  ----- Deq ADJACENT_CP_CONTACTED message
APPN: ----- SS  ----- Deq SESSST_SIGNAL message
APPN: ----- SS  ----- Deq CP_CP_SESSION_ACT message
APPN: Sending ADJACENT_NN_1015 to SCM, adj_node_p=A6B980,cp_name=NETA.PATTY        
APPN: ----- SS  ----- Sending REQUEST_LAST_FRSN message to TRS
APPN: ----- SS  ----- Receiving REQUEST_LAST_FRSN_RSP from TRS
APPN: ----- SS  ----- Sending ACTIVE CP_STATUS CONLOSER message to DS
APPN: ----- SS  ----- Sending ACTIVE CP_STATUS CONLOSER message to MS
APPN: ----- SS  ----- Sending ACTIVE CP_STATUS CONLOSER message to TRS
APPN: ----- SS  ----- Sending CP_CP_SESSION_ACT_RSP message to CCA TP
APPN: ----- SS  ----- Sending PENDING_ACTIVE CP_STATUS CONWINNER message to DS
APPN: ----- SS  ----- Sending REQUEST_LAST_FRSN message to TRS
APPN: ----- SS  ----- Receiving REQUEST_LAST_FRSN_RSP from TRS
APPN: ----- SS  ----- Sending ACT_CP_CP_SESSION message to RCA TP
APPN: ----- SS  ----- Deq ASSIGN_PCID message
APPN: ----- SS  ----- Sending ASSIGN_PCID_RSP message to someone
APPN: ----- SS  ----- Deq INIT_SIGNAL message
APPN: ----- SS  ----- Sending REQUEST_COS_TPF_VECTOR message to TRS
APPN: ----- SS  ----- Receiving an REQUEST_COS_TPF_VECTOR_RSP from TRS
APPN: ----- SS  ----- Sending REQUEST_SINGLE_HOP_ROUTE message to TRS
APPN: ----- SS  ----- Receiving an REQUEST_SINGLE_HOP_ROUTE_RSP from TRS
APPN: ----- SS  ----- Sending ACTIVATE_ROUTE message to CS
APPN: ----- SS  ----- Deq ACTIVATE_ROUTE_RSP message
APPN: ----- SS  ----- Sending CINIT_SIGNAL message to SM
APPN: ----- SS  ----- Deq ACT_CP_CP_SESSION_RSP message
APPN: -- SS -- SS ssp00, act_cp_cp_session_rsp received, sense_code=0, cgid=5C, ips@=A93790
APPN: Sending ADJACENT_NN_1015 to SCM, adj_node_p=A6B980,cp_name=18s
APPN: ----- SS  ----- Sending ACTIVE CP_STATUS CONWINNER message to DS
APPN: ----- SS  ----- Sending ACTIVE CP_STATUS CONWINNER message to MS
APPN: ----- SS  ----- Sending ACTIVE CP_STATUS CONWINNER message to TRS

Table 2-15 describes fields in the debug appn ssoutput shown in Figure 2-22.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn trs

debug appn trs

Use the debug appn trs command to display debugging information on APPN Topology and Routing Services (TRS) component activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The Topology and Routing Services (TRS) component is responsible for creating and maintaining the topology database, creating and maintaining the class of service database, and computing and caching optimal routes through the network.

Sample Display

Figure 2-23 shows sample debug appn trs output.

router# debug appn trs 
Turned on event 400000FF
APPN: ----- TRS ----- Received a QUERY_CPNAME
APPN: ----- TRS ----- Received a REQUEST_ROUTE
APPN: ----- TRS ----- check_node node_name=NETA.LISA
APPN: ----- TRS ----- check_node node_index=0
APPN: ----- TRS ----- check_node node_weight=60
APPN: ----- TRS ----- add index 484 to origin description list
APPN: ----- TRS ----- add index 0 to dest description list
APPN: ----- TRS ----- origin tg_vector is NULL
APPN: ----- TRS ----- weight_to_origin = 0
APPN: ----- TRS ----- weight_to_dest = 0
APPN: ----- TRS ----- u_b_s_f weight = 30
APPN: ----- TRS ----- u_b_s_f prev_weight = 2147483647
APPN: ----- TRS ----- u_b_s_f origin_index = 484
APPN: ----- TRS ----- u_b_s_f dest_index = 0
APPN: ----- TRS ----- b_r_s_f weight = 30
APPN: ----- TRS ----- b_r_s_f origin_index = 484
APPN: ----- TRS ----- b_r_s_f dest_index = 0
APPN: ----- TRS ----- Received a REQUEST_ROUTE
APPN: ----- TRS ----- check_node node_name=NETA.LISA
APPN: ----- TRS ----- check_node node_index=0
APPN: ----- TRS ----- check_node node_weight=60
APPN: ----- TRS ----- check_node node_name=NETA.BART
APPN: ----- TRS ----- check_node node_index=484
APPN: ----- TRS ----- check_node node_weight=60
APPN: ----- TRS ----- add index 484 to origin description list
APPN: ----- TRS ----- add index 0 to dest description list
APPN: ----- TRS ----- origin_tg_weight to non-VN=30
APPN: ----- TRS ----- origin_node_weight to non-VN=60
APPN: ----- TRS ----- weight_to_origin = 90
APPN: ----- TRS ----- weight_to_dest = 0
APPN: ----- TRS ----- u_b_s_f weight = 120
APPN: ----- TRS ----- u_b_s_f prev_weight = 2147483647
APPN: ----- TRS ----- u_b_s_f origin_index = 484
APPN: ----- TRS ----- u_b_s_f dest_index = 0
APPN: ----- TRS ----- b_r_s_f weight = 120
APPN: ----- TRS ----- b_r_s_f origin_index = 484
APPN: ----- TRS ----- b_r_s_f dest_index = 0

Table 2-16 describes fields in the debug appn trs output shown in Figure 2-23.

Related Commands

debug appn all
debug appn cs
debug appn dlur
debug appn ds
debug appn ms
debug appn nof
debug appn pc
debug appn ps
debug appn scm
debug appn ss

debug arap

Use the debug arap command to display AppleTalk Remote Access Protocol (ARAP) events. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

Use the debug arap command with the debug callback command on access servers to debug dial-in and callback events.

Sample Display

Figure 2-24 shows sample debug arap output.

router# debug arap internal
ARAP: ---------- SRVRVERSION ----------
ARAP: ---------- ACKing 0 ----------
ARAP: ---------- AUTH_CHALLENGE ----------
arapsec_local_account setting up callback
ARAP: ---------- ACKing 1 ----------
ARAP: ---------- AUTH_RESPONSE ----------
arap_startup initiating callback ARAP 2.0
ARAP: ---------- CALLBACK ----------
TTY7 Callback process initiated, user: dialback dialstring 40
TTY7 Callback forced wait = 4 seconds
TTY7 ARAP Callback Successful - await exec/autoselect pickup
TTY7: Callback in effect
ARAP: ---------- STARTINFOFROMSERVER ----------
ARAP: ---------- ACKing 0 ----------
ARAP: ---------- ZONELISTINFO ----------
ARAP: ---------- ZONELISTINFO ----------
ARAP: ---------- ZONELISTINFO ----------
ARAP: ---------- ZONELISTINFO ----------
ARAP: ---------- ZONELISTINFO ----------

Related Command

debug callback

debug arp

Use the debug arp EXEC command to display information on Address Resolution Protocol (ARP) transactions. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Use this command when some nodes on a TCP/IP network are responding, but others are not. It shows whether the router is sending ARPs and whether it is receiving ARPs.

Sample Display

Figure 2-25 shows sample debug arp output.

router# debug arp
IP ARP: sent req src 131.108.22.7 0000.0c01.e117, dst 131.108.22.96 0000.0000.0000
IP ARP: rcvd rep src 131.108.22.96 0800.2010.b908, dst 131.108.22.7
IP ARP: rcvd req src 131.108.6.10 0000.0c00.6fa2, dst 131.108.6.62
IP ARP: rep filtered src 131.108.22.7 aa92.1b36.a456, dst 255.255.255.255 ffff.ffff.ffff
IP ARP: rep filtered src 131.108.9.7 0000.0c00.6b31, dst 131.108.22.7 0800.2010.b908

In Figure 2-25, each line of output represents an ARP packet that the router sent or received. Explanations for the individual lines of output follow.

The first line indicates that the router at IP address 131.108.22.7 and MAC address 0000.0c01.e117 sent an ARP request for the MAC address of the host at 131.108.22.96. The series of zeros (0000.0000.0000) following this address indicate that the router is currently unaware of the MAC address.

IP ARP: sent req src 131.108.22.7 0000.0c01.e117, dst 131.108.22.96 \
0000.0000.0000

The second line indicates that the router at IP address 131.108.22.7 receives a reply from the host at 131.108.22.96 indicating that its MAC address is 0800.2010.b908:

IP ARP: rcvd rep src 131.108.22.96 0800.2010.b908, dst 131.108.22.7

The third line indicates that the router receives an ARP request from the host at 131.108.6.10 requesting the MAC address for the host at 131.108.6.62:

IP ARP: rcvd req src 131.108.6.10 0000.0c00.6fa2, dst 131.108.6.62

The fourth line indicates that another host on the network attempted to send the router an ARP reply for its own address. The router ignores meaningless replies. Usually, meaningless replies happen if someone is running a bridge in parallel with the router and is allowing ARP to be bridged. This condition indicates a network misconfiguration.

IP ARP: rep filtered src 131.108.22.7 aa92.1b36.a456, dst 255.255.255.255 \
ffff.ffff.ffff 

The fifth line indicates that another host on the network attempted to inform the router that it is on network 131.108.9.7, but the router does not know that that network is attached to a different router interface. The remote host (probably a PC or an X terminal) is misconfigured. If the router were to install this entry, it would deny service to the real machine on the proper cable.

IP ARP: rep filtered src 131.108.9.7 0000.0c00.6b31, dst 131.108.22.7 \
0800.2010.b908

debug atm errors

Use the debug atm errors EXEC command to display Asynchronous Transfer Mode (ATM) errors. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-26 shows sample debug atm errors output.

router# debug atm errors
ATM(ATM2/0): Encapsulation error, link=7, host=836CA86D.
ATM(ATM4/0): VCD#7 failed to echo OAM. 4 tries

The first line of output in Figure 2-26 indicates that a packet was routed to the ATM interface, but no static map was set up to route that packet to the proper virtual circuit.

The second line of output shows that an OAM F5 (virtual circuit) cell error occurred.

debug atm events

Use the debug atm events EXEC command to display ATM events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command displays ATM events that occur on the ATM interface processor and is useful for diagnosing problems in an ATM network. It provides an overall picture of the stability of the network. In a stable network, the debug atm events command does not return any information. If the command generates numerous messages, the messages can indicate the possible source of problems.

When configuring or making changes to a router or interface for ATM, enable debug atm events. Doing so alerts you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.

Sample Display

Figure 2-27 shows sample debug atm events output.

router# debug atm events
ATM events debugging is on
RESET(ATM4/0): PLIM type is 1, Rate is 100Mbps
aip_disable(ATM4/0): state=1
config(ATM4/0)
aip_love_note(ATM4/0): asr=0x201
aip_enable(ATM4/0)
aip_love_note(ATM4/0): asr=0x4000
aip_enable(ATM4/0): restarting VCs: 7
aip_setup_vc(ATM4/0): vc:1 vpi:1 vci:1
aip_love_note(ATM4/0): asr=0x200
aip_setup_vc(ATM4/0): vc:2 vpi:2 vci:2
aip_love_note(ATM4/0): asr=0x200
aip_setup_vc(ATM4/0): vc:3 vpi:3 vci:3
aip_love_note(ATM4/0): asr=0x200
aip_setup_vc(ATM4/0): vc:4 vpi:4 vci:4
aip_love_note(ATM4/0): asr=0x200
aip_setup_vc(ATM4/0): vc:6 vpi:6 vci:6
aip_love_note(ATM4/0): asr=0x200
aip_setup_vc(ATM4/0): vc:7 vpi:7 vci:7
aip_love_note(ATM4/0): asr=0x200
aip_setup_vc(ATM4/0): vc:11 vpi:11 vci:11
aip_love_note(ATM4/0): asr=0x200

Table 2-17 describes significant fields in the output shown in Figure 2-27.

Explanations for representative lines of output in Figure 2-27 follow.

The following line indicates that the ATM Interface Processor (AIP) was reset. The PLIM TYPE detected was 1, so the maximum rate is set to 100 Mbps.

RESET(ATM4/0): PLIM type is 1, Rate is 100Mbps

The following line indicates that the ATM Interface Processor (AIP) was given a shutdown command, but the current configuration indicates that the AIP should be up:

aip_disable(ATM4/0): state=1

The following line indicates that a configuration command has been completed by the AIP:

aip_love_note(ATM4/0): asr=0x201

The following line indicates that the AIP was given a no shutdown command to take it out of shutdown:

aip_enable(ATM4/0)

The following line indicates that the AIP detected a carrier state change. It does not indicate that the carrier is down or up, only that it has changed:

aip_love_note(ATM4/0): asr=0x4000

The following line of output indicates that the AIP enable function is restarting all PVCs automatically:

aip_enable(ATM4/0): restarting VCs: 7

The following lines of output indicate that PVC 1 was set up and a successful completion code was returned:

aip_setup_vc(ATM4/0): vc:1 vpi:1 vci:1
aip_love_note(ATM4/0): asr=0x200

debug atm oam

Use the debug atm oam command to display ATM operation and maintnenance (OAM) events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-28 shows sample debug atm oam output.

router# debug atm oam
ATM4/0(O): VCD:0x0 DM:0x300 *OAM Cell* Length:0x39
0000 0300 0070 007A 0018 0100 0000 05FF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 
FFFF FFFF FFFF FFFF FF6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A6A 6A00 0000

Table 2-18 describes the output fields shown in Figure 2-28.

debug atm packet

Use the debug atm packet EXEC command to display per-packet debugging output. The output reports information online when a packet is received or a transmit is attempted. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The debug atm packet command displays all process-level ATM packets for both outbound and inbound packets. This command is useful for determining whether packets are being received and transmitted correctly.

For transmitted packets, the information is displayed only after the protocol data unit (PDU) is entirely encapsulated and a next hop virtual circuit (VC) is found. If information is not displayed, the address translation probably failed during encapsulation. When a next hop VC is found, the packet is displayed exactly as it will be presented on the wire. Having a display indicates the packets are properly encapsulated for transmission.

For received packets, information is displayed for all incoming frames. The display can show whether the transmitting station properly encapsulates the frames. Because all incoming frames are displayed, this information is useful when performing back-to-back testing and corrupted frames cannot be dropped by an intermediary ATM switch.

The debug atm packet command also displays the initial bytes of the actual PDU in hexadecimal. This information can be decoded only by qualified support or engineering personnel.

Sample Display

Figure 2-29 shows sample debug atm packet output.

router# debug atm packets
ATM packets debugging is on
router#
ATM2/0(O): VCD: 0x1,DM: 1C00, MUX, ETYPE: 0800,Length: 32
4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000
A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105

Table 2-19 describes significant fields shown in Figure 2-29.

4500 002E 0000 0000 0209 92ED 836C A26E FFFF FFFF 1108 006D 0001 0000 0000
A5CC 6CA2 0000 000A 0000 6411 76FF 0100 6C08 00FF FFFF 0003 E805 DCFF 0105

debug bri

Use the debug bri EXEC command to display debugging information on Integrated Services Digital Networks (ISDN) Basic Rate Interface (BRI) routing activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The debug bri command indicates whether the ISDN code is enabling and disabling the B-channels when attempting an outgoing call. This command is available for the low-end router products that have a multi-BRI network interface module installed.

Sample Display

Figure 2-30 shows sample debug bri output.

Router# debug bri
Basic Rate network interface debugging is on          
BRI: write_sid: wrote 1B for subunit 0, slot 1.
BRI: write_sid: wrote 15 for subunit 0, slot 1.
BRI: write_sid: wrote 17 for subunit 0, slot 1.
BRI: write_sid: wrote 6 for subunit 0, slot 1.
BRI: write_sid: wrote 8 for subunit 0, slot 1.
BRI: write_sid: wrote 11 for subunit 0, slot 1.
BRI: write_sid: wrote 13 for subunit 0, slot 1.
BRI: write_sid: wrote 29 for subunit 0, slot 1.
BRI: write_sid: wrote 1B for subunit 0, slot 1.
BRI: write_sid: wrote 15 for subunit 0, slot 1.
BRI: write_sid: wrote 17 for subunit 0, slot 1.
BRI: write_sid: wrote 20 for subunit 0, slot 1.
BRI: Starting Power Up timer for unit = 0. 
BRI: write_sid: wrote 3 for subunit 0, slot 1.
BRI: Starting T3 timer after expiry of PUP timeout for unit = 0, current state is F4. 
BRI: write_sid: wrote FF for subunit 0, slot 1.
BRI: Activation for unit = 0, current state is F7. 
BRI: enable channel B1 
BRI: write_sid: wrote 14 for subunit 0, slot 1.
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up
%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!!
BRI: disable channel B1 
BRI: write_sid: wrote 15 for subunit 0, slot 1.
%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to down
%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to down
%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to down

Explanations for individual lines of output from Figure 2-30 follow.

The following line indicates that an internal command was written to the interface controller. The subunit identifies the first interface in the slot:

BRI: write_sid: wrote 1B for subunit 0, slot 1.

The following line indicates that the power-up timer was started for the named unit:

BRI: Starting Power Up timer for unit = 0. 

The following lines indicate that the channel or the protocol on the interface changed state:

%LINK-3-UPDOWN: Interface BRI0: B-Channel 1, changed state to up
%LINK-5-CHANGED: Interface BRI0: B-Channel 1, changed state to up.!!!
%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to down

The following line indicates that the channel was disabled:

BRI: disable channel B1 

Lines of output not described are for use by support staff only.

Related Commands

debug isdn-event
debug isdn-q921
debug isdn-q931

debug broadcast

Use the debug broadcast EXEC command to display information on MAC broadcast packets. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Depending on the type of interface and the type of encapsulation used on that interface, the debug broadcast command can produce a wide range of messages.

Sample Display

Figure 2-31 shows sample debug broadcast output. Notice how similar it is to the debug packet output.

router# debug broadcast
Ethernet0: Broadcast ARPA, src 0000.0c00.6fa4, dst ffff.ffff.ffff, type 0x0800,
data 4500002800000000FF11EA7B, len 60
Serial3: Broadcast HDLC, size 64, type 0x800, flags 0x8F00
Serial2: Broadcast PPP, size 128
Serial7: Broadcast FRAME-RELAY, size 174, type 0x800, DLCI 7a

Table 2-20 describes significant fields shown in Figure 2-31.

debug bsc events

Use the debug bsc events command to display all events occuring in the Binary Synchronous Communication (BSC) feature. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command traces all interfaces configured with a bsc protocol-group number interface command.

Sample Display

Figure 2-32 shows sample debug bsc events output.

router# debug bsc events
BSC: Serial2         POLLEE-FSM inp:E_LineFail  old_st:CU_Down  new_st:TCU_EOFile
BSC: Serial2         POLLEE-FSM inp:E_LineFail  old_st:CU_Down  new_st:TCU_EOFile
BSC: Serial2         POLLEE-FSM inp:E_LineFail  old_st:CU_Down  new_st:TCU_EOFile
0:04:32: BSC: Serial2        :SDI-rx : 9 bytes
BSC: Serial2         POLLEE-FSM inp:E_RxEtx  old_st:CU_Down  new_st:TCU_EOFile
0:04:32: BSC: Serial2        :SDI-rx : 5 bytes
BSC: Serial2         POLLEE-FSM inp:E_RxEnq  old_st:CU_Down  new_st:TCU_EOFile
BSC: Serial2         POLLEE-FSM inp:E_Timeout  old_st:CU_Down  new_st:TCU_InFile
BSC: Serial2         POLLEE-FSM inp:E_Timeout  old_st:CU_Idle  new_st:TCU_InFile
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial2, changed state to up
%LINK-3-UPDOWN: Interface Serial2, changed state to up
BSC: Serial2         POLLEE-FSM inp:E_Timeout  old_st:CU_Idle  new_st:TCU_InFile
0:04:35: BSC: Serial2        :SDI-rx : 9 bytes
BSC: Serial2         POLLEE-FSM inp:E_RxEtx  old_st:CU_Idle  new_st:TCU_InFile
0:04:35: BSC: Serial2        :SDI-rx : 5 bytes
BSC: Serial2         POLLEE-FSM inp:E_RxEnq  old_st:CU_Idle  new_st:TCU_InFile
0:04:35: BSC: Serial2        :NDI-rx : 3 bytes

Related Command

debug bsc packet

debug bsc packet

Use the debug bsc packet command to display all frames traveling through the Binary Synchronous Communication (BSC) feature. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command traces all interfaces configured with a bsc protocol-group number interface command.

Sample Display

Figure 2-33 shows sample debug bsc packet output.

router# debug bsc packet
0:23:33: BSC: Serial2        :NDI-rx : 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D4013
0:23:33: BSC: Serial2        :SDI-tx : 12 bytes 00323237FF3232606040402D
0:23:33: BSC: Serial2        :SDI-rx : 2 bytes 1070
0:23:33: BSC: Serial2        :SDI-tx : 27 bytes 401A400227F5C31140C11D60C8C5D3D3D51D4013
0:23:33: BSC: Serial2        :SDI-rx : 2 bytes 1061
0:23:33: BSC: Serial2        :SDI-tx : 5 bytes 00323237FF

Related Command

debug bsc event

debug bstun

Use the debug bstun command to show connection establishment and overall status messages for the block serial tunnel (BSTUN) connection. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-34 shows sample debug bstun output.

router# debug bstun 
%BSTUN-6-TCPFINI: peer (all[2])192.195.80.161/1976 closed [previous state open]
BSTUN: Change state for peer (all[2])192.195.80.161/1976 at 4451380 (open->closed)
%BSTUN-6-TCPFINI: peer (all[1])192.195.80.161/1976 closed [previous state open]
BSTUN: Change state for peer (all[1])192.195.80.161/1976 at 4451380 (open->closed)
BSTUN: Change state for peer (all[2])192.195.80.161/1976 at 4451AA0 (closed->opening)
BSTUN: Change state for peer (all[2])192.195.80.161/1976 at 4451AA0 (opening->open wait)
%BSTUN-6-OPENING: CONN: opening peer (all[2])192.195.80.161/1976, 3
%BSTUN-6-OPENED: CONN: peer (all[2])192.195.80.161/1976 opened, [previous state open wait]

Related Command

debug bstun packet

debug bstun packet

Use the debug bstun packet command to display packet information on packets traveling through the BSTUN links. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Sample Display

Figure 2-35 shows sample debug bstun packet output.

router# debug bstun packet
BSTUN bsc-local-ack: 0:00:00 Serial2         SDI: Addr:  40 Data: 02C1C1C1C1C1C1C1C1C1
BSTUN bsc-local-ack: 0:00:00 Serial2         SDI: Addr:  40 Data: 02C1C1C1C1C1C1C1C1C1
BSTUN bsc-local-ack: 0:00:06 Serial2         NDI: Addr:  40 Data: 0227F5C31140C11D60C8

Related Command

debug bstun event

debug callback

Use the debug callback command to display callback events when the router is using a modem and a chat script to call back on a terminal line. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command is useful for debugging chat scripts on PPP and ARAP lines that use callback mechanisms. The output provided by the debug callback command shows you how the call is progressing when used with the debug ppp or debug arap commands.

Sample Display

Figure 2-36 shows sample debug callback output.

router# debug callback 
TTY7 Callback process initiated, user: exec_test dialstring 123456
TTY7 Callback forced wait = 4 seconds
TTY7 Exec Callback Successful - await exec/autoselect pickup
TTY7: Callback in effect

Related Commands

debug ppp
debug arap

debug cdp

Use the debug cdp EXEC command to enable debugging of Cisco Discovery Protocol (CDP). The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

Use debug cdp commands to display information about CDP packet activity, activity between CDP neighbors, and various CDP events.

Sample Display

Figure 2-37 shows a composite sample output from debug cdp packets, debug cdp adjacency, and debug cdp events.

router# debug cdp packets
CDP packet info debugging is on
router# debug cdp adjacency
CDP neighbor info debugging is on
router# debug cdp events
CDP events debugging is on
CDP-PA: Packet sent out on Ethernet0
CDP-PA: Packet received from gray.cisco.com on interface Ethernet0
CDP-AD: Deleted table entry for violet.cisco.com, interface Ethernet0
CDP-AD: Interface Ethernet2 coming up
CDP-EV: Encapsulation on interface Serial2 failed

debug channel love

Use the debug channel love command to display Channel Interface Processor (CIP) love letter events. This command is valid for the Cisco 7000 series routers only. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command displays Channel Interface Processor (CIP) events that occur on the CIP interface processor and is useful for diagnosing problems in an IBM channel attach network. It provides an overall picture of the stability of the network. In a stable network, the debug channel love command returns a statistic message (cip_love_letter) that is transmitted every ten seconds.

Sample Display

Figure 2-38 shows sample debug channel love output.

Router# debug channel love
Channel3/1: love letter received, bytes 3308
Channel3/0: love letter received, bytes 3336
cip_love_letter: recieved ll, but no cip_info

Channel3/1: love letter received, bytes 3308

cip_love_letter: recieved ll, but no cip_info

Related Commands

debug channel events
debug channel packets

debug channel events

The debug channel events EXEC command displays processing events that occur on the channel adapter interfaces of all installed adapters. This command is valid for the Cisco 7000 series routers only. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command displays Channel Interface Processor (CIP) events that occur on the CIP interface processor and is useful for diagnosing problems in an IBM channel attach network. It provides an overall picture of the stability of the network. In a stable network, the debug channel events command does not return any information. If the command generates numerous messages, they can indicate the possible source of the problems. To observe the statistic message (cip_love_letter) transmitted every ten seconds, use the debug channel love command.

When configuring or making changes to a router or interface that supports IBM channel attach, enable debug channel events. Doing so alerts you to the progress of the changes or to any errors that might result. Also use this command periodically when you suspect network problems.

Sample Display

Figure 2-39 shows sample debug channel events output.

Router# debug channel events
Channel3/0: cip_reset(), state administratively down
Channel3/0: cip_reset(), state up
Channel3/0: sending nodeid
Channel3/0: sending command for vc 0, CLAW path C700, device C0

Explanations for individual lines of output from Figure 2-39 follow.

The following line indicates that the CIP is being reset to an administrative down state:

Channel3/0: cip_reset(), state administratively down

The following line indicates that the CIP is being reset to an administrative up state:

Channel3/0: cip_reset(), state up

The following line indicates that the node id is being sent to the CIP. This information is the same as the "Local Node" information under the show extended channel slot/port subchannels command. The CIP needs this information to send to the host mainframe.

Channel3/0: sending nodeid

The following line indicates that a CLAW subchannel command is being sent from the RP to the CIP. The value vc 0 indicates that the CIP will use virual circuit number 0 with this device. The virual circuit number will also show up when you use the debug channel packets command.

Channel3/0: sending command for vc 0, CLAW path C700, device C0

Related Commands

debug channel love
debug channel packets

debug channel packets

Use the debug channel packets EXEC command to display per-packet debugging output. The output reports information when a packet is received or a transmit is attempted. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The debug channel packets command displays all process-level Channel Interface Processor (CIP) packets for both outbound and and inbound packets. You will need to disable fast switching and autonomous switching to obtain debugging output. This command is useful for determining whether packets are received or transmitted correctly.

This command is valid for the Cisco 7000 series routers only.

Sample Display

Figure 2-40 shows sample debug channel packets output.

Router# debug channel packets 
Channel packets debugging is on
(Channel3/0)-out size = 104, vc = 0000, type = 0800, src 198.92.0.11, dst 198.92.1.58
(Channel3/0)-in  size = 48, vc = 0000, type = 0800, src 198.92.1.58, dst 198.92.15.197
(Channel3/0)-in  size = 48, vc = 0000, type = 0800, src 198.92.1.58, dst 198.92.15.197
(Channel3/0)-out size = 71, vc = 0000, type = 0800, src 198.92.15.197, dst 198.92.1.58
(Channel3/0)-in  size = 44, vc = 0000, type = 0800, src 198.92.1.58, dst 198.92.15.197

Table 2-21 provides explanations for individual lines of output from Figure 2-40.

Related Commands

debug channel events
debug channel love

debug clns esis events

Use the debug clns esis events EXEC command to display uncommon End System-to-Intermediate System (ES-IS) events, including previously unknown neighbors, neighbors that have aged out, and neighbors that have changed roles (ES to IS, for example). The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-41 shows sample debug clns esis events output.

router# debug clns esis events
ES-IS: ISH from aa00.0400.2c05 (Ethernet1), HT 30
ES-IS: ESH from aa00.0400.9105 (Ethernet1), HT 150
ES-IS: ISH sent to All ESs (Ethernet1): NET 49.0001.AA00.0400.6904.00, HT 299, HLEN 20

Explanations for individual lines of output from Figure 2-41 follow.

The following line indicates that the router received a hello packet (ISH) from the IS at MAC address aa00.0400.2c05 on the Ethernet1 interface. The hold time (or number of seconds to consider this packet valid before deleting it) for this packet is 30 seconds.

ES-IS: ISH from aa00.0400.2c05 (Ethernet1), HT 30

The following line indicates that the router received a hello packet (ESH) from the ES at MAC address aa00.0400.9105 on the Ethernet1 interface. The hold time is 150 seconds.

ES-IS: ESH from aa00.0400.9105 (Ethernet1), HT 150

The following line indicates that the router sent an IS hello packet on the Ethernet0 interface to all ESs on the network. The network entity title (NET) address of the router is 49.0001.0400.AA00.6904.00; the hold time for this packet is 299 seconds; and the header length of this packet is 20 bytes.

ES-IS: ISH sent to All ESs (Ethernet1): NET 49.0001.AA00.0400.6904.00, HT 299, HLEN 20

debug clns esis packets

Use the debug clns esis packets EXEC command to enable display information on End System-to-Intermediate System (ES-IS) packets that the router has received and sent. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-42 shows sample debug clns esis packets output.

router# debug clns esis packets  
ES-IS: ISH sent to All ESs (Ethernet0): NET 
47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 33
ES-IS: ISH sent to All ESs (Ethernet1): NET 
47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34
ES-IS: ISH from aa00.0400.6408 (Ethernet0), HT 299
ES-IS: ISH sent to All ESs (Tunnel0): NET 
47.0005.80ff.ef00.0000.0001.5940.1600.O906.4023.00, HT 299, HLEN 34
IS-IS: ESH from 0000.0c00.bda8 (Ethernet0), HT 300

Explanations for individual lines of output from Figure 2-42 follow.

The following line indicates that the router has sent an IS hello packet on Ethernet0 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length.

ES-IS: ISH sent to All ESs (Ethernet0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 33

The following line indicates that the router has sent an IS hello packet on Ethernet1 to all ESs on the network. This hello packet indicates that the network entity title (NET) of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length.

ES-IS: ISH sent to All ESs (Ethernet1): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34

The following line indicates that the router received a hello packet on Ethernet0 from an intermediate system, aa00.0400.6408. The hold time for this packet is 299 seconds.

ES-IS: ISH from aa00.0400.6408 (Ethernet0), HT 299 

The following line indicates that the router has sent an IS hello packet on Tunnel0 to all ESs on the network. This hello packet indicates that the NET of the router is 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00. The hold time for this packet is 299 seconds. The packet header is 33 bytes in length.

ES-IS: ISH sent to All ESs (Tunnel0): NET 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00, HT 299, HLEN 34

The following line indicates that on Ethernet0, the router received a hello packet from an end system with an SNPA of 0000.0c00.bda8. The hold time for this packet is 300 seconds.

IS-IS: ESH from 0000.0c00.bda8 (Ethernet0), HT 300

debug clns events

Use the debug clns events EXEC command to display CLNS events that are occurring at the router. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-43 shows sample debug clns events output.

router# debug clns events
CLNS: Echo PDU received on Ethernet3 from 39.0001.2222.2222.2222.00!
CLNS: Sending from 39.0001.3333.3333.3333.00 to 39.0001.2222.2222.2222.00
         via 2222.2222.2222 (Ethernet3 0000.0c00.3a18)
CLNS: Forwarding packet size 117
      from 39.0001.2222.2222.2222.00
      to 49.0002.0001.AAAA.AAAA.AAAA.00
      via 49.0002 (Ethernet3 0000.0c00.b5a3)
CLNS: RD Sent on Ethernet3 to 39.0001.2222.2222.2222.00 @ 0000.0c00.3a18,
      redirecting 49.0002.0001.AAAA.AAAA.AAAA.00 to 0000.0c00.b5a3

Explanations for individual lines of output from Figure 2-43 follow.

The following line indicates that the router received an echo PDU on Ethernet3 from source network service access point (NSAP) 39.0001.2222.2222.2222.00. The exclamation point at the end of the line has no significance.

CLNS: Echo PDU received on Ethernet3 from 39.0001.2222.2222.2222.00!

The following lines indicate that the router at source NSAP 39.0001.3333.3333.3333.00 is sending a CLNS echo packet to destination NSAP 39.0001.2222.2222.2222.00 via an IS with system ID 2222.2222.2222. The packet is being sent on the Ethernet3 interface, with a MAC address of 0000.0c00.3a18.

CLNS: Sending from 39.0001.3333.3333.3333.00 to 39.0001.2222.2222.2222.00
         via 2222.2222.2222 (Ethernet3 0000.0c00.3a18)

The following lines indicate that a CLNS echo packet 117 bytes in size is being sent from source NSAP 39.0001.2222.2222.2222.00 to destination NSAP 49.0002.0001.AAAA.AAAA.AAAA.00 via the router at NSAP 49.0002. The packet is being forwarded on the Ethernet3 interface, with a MAC address of 0000.0c00.b5a3.

CLNS: Forwarding packet size 117
      from 39.0001.2222.2222.2222.00
      to 49.0002.0001.AAAA.AAAA.AAAA.00
      via 49.0002 (Ethernet3 0000.0c00.b5a3)

The following lines indicate that the router sent a redirect packet on the Ethernet3 interface to the NSAP 39.0001.2222.2222.2222.00 at MAC address 0000.0c00.3a18 to indicate that NSAP 49.0002.0001.AAAA.AAAA.AAAA.00 can be reached at MAC address 0000.0c00.b5a3.

CLNS: RD Sent on Ethernet3 to 39.0001.2222.2222.2222.00 @ 0000.0c00.3a18,
      redirecting 49.0002.0001.AAAA.AAAA.AAAA.00 to 0000.0c00.b5a3

debug clns igrp packets

Use the debug clns igrp packets EXEC command to display debugging information on all ISO-IGRP routing activity. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-44 shows sample debug clns igrp packets output.

router# debug clns igrp packets
ISO-IGRP: Hello sent on Ethernet3 for DOMAIN_green1
ISO-IGRP: Received hello from 39.0001.3333.3333.3333.00, (Ethernet3), ht 51
ISO-IGRP: Originating level 1 periodic update
ISO-IGRP: Advertise dest: 2222.2222.2222
ISO-IGRP: Sending update on interface: Ethernet3
ISO-IGRP: Originating level 2 periodic update
ISO-IGRP: Advertise dest: 0001
ISO-IGRP: Sending update on interface: Ethernet3
ISO-IGRP: Received update from 3333.3333.3333 (Ethernet3)
ISO-IGRP: Opcode: area
ISO-IGRP: Received level 2 adv for 0001 metric 1100
ISO-IGRP: Opcode: station
ISO-IGRP: Received level 1 adv for 3333.3333.3333 metric 1100

Explanations for individual lines of output from Figure 2-44 follow.

The following line indicates that the router is sending a hello packet to advertise its existence in the DOMAIN_green1 domain:

ISO-IGRP: Hello sent on Ethernet3 for DOMAIN_green1

The following line indicates that the router received a hello packet from a certain network service access point (NSAP) on the Ethernet3 interface. The hold time for this information is 51 seconds.

ISO-IGRP: Received hello from 39.0001.3333.3333.3333.00, (Ethernet3), ht 51

The following lines indicate that the router is generating a Level 1 update to advertise reachability to destination NSAP 2222.2222.2222 and that it is sending that update to all systems that can be reached through the Ethernet3 interface:

ISO-IGRP: Originating level 1 periodic update
ISO-IGRP: Advertise dest: 2222.2222.2222
ISO-IGRP: Sending update on interface: Ethernet3

The following lines indicate that the router is generating a Level 2 update to advertise reachability to destination area 1 and that it is sending that update to all systems that can be reached through the Ethernet3 interface:

ISO-IGRP: Originating level 2 periodic update
ISO-IGRP: Advertise dest: 0001
ISO-IGRP: Sending update on interface: Ethernet3

The following lines indicate that the router received an update from NSAP 3333.3333.3333 on Ethernet3. This update indicated the area the router at this NSAP could reach.

ISO-IGRP: Received update from 3333.3333.3333 (Ethernet3)
ISO-IGRP: Opcode: area

The following lines indicate that the router received an update advertising that the source of that update can reach area 1 with a metric of 1100. A station opcode indicates that the update included system addresses.

ISO-IGRP: Received level 2 adv for 0001 metric 1100
ISO-IGRP: Opcode: station

debug clns packet

Use the debug clns packet EXEC command to display information about packet receipt and forwarding to the next interface. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-45 shows sample debug clns packet output.

router# debug clns packet
CLNS: Forwarding packet size 157
      from 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.00 STUPI-RBS
      to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00
      via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)
CLNS: Echo PDU received on Ethernet0 from 4
7.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00!
CLNS: Sending from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00 to 
47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00
      via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)

Explanations for individual lines of output from Figure 2-45 follow.

In the following lines, the first line indicates that a Connectionless Network Service (CLNS) packet of size 157 bytes is being forwarded. The second line indicates the network service access point (NSAP) and system name of the source of the packet. The third line indicates the destination NSAP for this packet. The fourth line indicates the next-hop system ID, interface, and SNPA of the router interface used to forward this packet.

CLNS: Forwarding packet size 157
      from 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.00 STUPI-RBS
      to 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00
      via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)

In the following lines, the first line indicates that the router received an Echo PDU on the specified interface from the source NSAP. The second line indicates which source NSAP is used to send a CLNS packet to the destination NSAP, as shown on the third line. The fourth line indicates the next-hop system ID, interface, and SNPA of the router interface used to forward this packet.

CLNS: Echo PDU received on Ethernet0 from       47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00!
CLNS: Sending from 47.0005.80ff.ef00.0000.0001.5940.1600.8906.4023.00 to       47.0005.80ff.ef00.0000.0001.5940.1600.8906.4017.00
      via 1600.8906.4017 (Ethernet0 0000.0c00.bda8)

debug clns routing

Use the debug clns routing EXEC command to display debugging information for all Connectionless Network Service (CLNS) routing cache updates and activities involving the CLNS routing table. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-46 shows sample debug clns routing output.

router# debug clns routing
CLNS-RT: cache increment:17
CLNS-RT: Add 47.0023.0001.0000.0000.0003.0001 to prefix table, next hop 1920.3614.3002
CLNS-RT: Aging cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06
CLNS-RT: Deleting cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06

Explanations for individual lines of output from Figure 2-46 follow.

The following line indicates that a change to the routing table has resulted in an addition to the fast-switching cache:

CLNS-RT: cache increment:17

The following line indicates that a specific prefix route was added to the routing table, and indicates the next-hop system ID to that prefix route. In other words, when the router receives a packet with the prefix 47.0023.0001.0000.0000.0003.0001 in that packet's destination address, it forwards that packet to the router with the MAC address 1920.3614.3002.

CLNS-RT: Add 47.0023.0001.0000.0000.0003.0001 to prefix table, next hop 1920.3614.3002

The following lines indicate that the fast-switching cache entry for a certain network service access point (NSAP) has been invalidated and then deleted:

CLNS-RT: Aging cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06
CLNS-RT: Deleting cache entry for: 47.0023.0001.0000.0000.0003.0001.1920.3614.3002.06

debug compress

Use the debug compress EXEC command to display compression information. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-47 shows sample debug compress output.

router# debug compress
 DECOMPRESS xmt_paks 5 rcv_sync 5
         COMPRESS xmt_paks 10 version 1
         COMPRESS xmt_paks 11 version 1
 DECOMPRESS xmt_paks 6 rcv_sync 6
         COMPRESS xmt_paks 12 version 1
         COMPRESS xmt_paks 13 version 1
 DECOMPRESS xmt_paks 7 rcv_sync 7
         COMPRESS xmt_paks 14 version 1
         COMPRESS xmt_paks 15 version 1

Table 2-22 describes significant fields shown in Figure 2-47.

debug decnet adj

Use the debug decnet adj EXEC command to display debugging information on DECnet adjacencies. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-48 shows sample debug decnet adj output.

router# debug decnet adj
DECnet adjacencies debugging is on
router#
DNET-ADJ: Level 1 hello from 1.3
DNET-ADJ: sending hellos
DNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498
DNET-ADJ: Level 1 hello from 1.3
DNET-ADJ: 1.5 adjacency initializing
DNET-ADJ: sending triggered hellos
DNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498
DNET-ADJ: Level 1 hello from 1.3
DNET-ADJ: 1.5 adjacency up
DNET-ADJ: Level 1 hello from 1.5
DNET-ADJ: 1.5 adjacency down, listener timeout

Explanations for representative lines of output in Figure 2-48 follow.

The following line indicates that the router is sending hellos to all routers on this segment, which in this case is Ethernet 0:

DNET-ADJ: Sending hellos to all routers on interface Ethernet0, blksize 1498

The following line indicates that the router has heard a hello from address 1.5 and is creating an adjacency entry in its table. The initial state of this adjacency will be initializing.

DNET-ADJ: 1.5 adjacency initializing

The following line indicates that the router is sending an unscheduled (triggered) hello as a result of some event, such as new adjacency being heard:

DNET-ADJ: sending triggered hellos

The following line indicates that the adjacency with 1.5 is now up, or active:

DNET-ADJ: 1.5 adjacency up

The following line indicates that the adjacency with 1.5 has timed out, because no hello has been heard from adjacency 1.5 in the time interval originally specified in the hello from 1.5:

DNET-ADJ: 1.5 adjacency down, listener timeout

The following line indicates that the router is sending an unscheduled hello, as a result of some event, such as the adjacency state changing:

DNET-ADJ: hello update triggered by state changed in dn_add_adjacency

debug decnet connects

Use the debug decnet connects EXEC command to display debugging information of all connect packets that are filtered (permitted or denied) by DECnet access lists. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

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 any

You can then log all connect packets transmitted on interfaces to which you applied this list, in order to determine those elements on which your connect packets must be filtered.

Sample Display

Figure 2-49 shows sample debug decnet connects output.

router# debug decnet connects
DNET-CON: list 300 item #2 matched src=19.403 dst=19.309 on Ethernet0: permitted
  srcname="RICK" srcuic=[0,017]
  dstobj=42 id="USER"

Table 2-23 describes significant fields shown in Figure 2-49.

debug decnet events

Use the debug decnet events EXEC command to display debugging information on DECnet events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-50 shows sample debug decnet events output.

router# debug decnet events
DNET: Hello from area 50 rejected - exceeded 'max area' parameter (45)
DNET: Hello from area 50 rejected - exceeded 'max area' parameter (45)

Explanations for representative lines of output in Figure 2-50 follow.

The following line indicates that the router received a hello from a router whose area was greater than the max-area parameter with which this router was configured:

DNET: Hello from area 50 rejected - exceeded 'max area' parameter (45)

The following line indicates that the router received a hello from a router whose node ID was greater than the max-node parameter with which this router was configured:

DNET: Hello from node 1002 rejected - exceeded 'max node' parameter (1000)

debug decnet packet

Use the debug decnet packet EXEC command to display debugging information on DECnet packet events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-51 shows sample debug decnet packet output.

router# debug decnet packet
DNET-PKT: src 1.4 dst 1.5 sending to PHASEV
DNET-PKT: Packet fwded from 1.4 to 1.5, via 1.5, snpa 0000.3080.cf90, TokenRing0

Explanations for individual lines of output from Figure 2-51 follow.

The following line indicates that the router is sending a converted packet addressed to node 1.5 to Phase V:

DNET-PKT: src 1.4 dst 1.5 sending to PHASEV

The 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, TokenRing0

debug decnet routing

Use the debug decnet routing EXEC command to display all DECnet routing-related events occurring at the router. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-52 shows sample debug decnet routing output.

router# debug decnet routing
DNET-RT: Received level 1 routing from 1.3 on Ethernet0 at 1:16:34
DNET-RT: Sending routes
DNET-RT: Sending normal routing updates on Ethernet0
DNET-RT: Sending level 1 routing updates on interface Ethernet0
DNET-RT: Level1 routes from 1.5 on Ethernet0: entry for node 5 created
DNET-RT: route update triggered by after split route pointers in dn_rt_input
DNET-RT: Received level 1 routing from 1.5 on Ethernet 0 at 1:18:35
DNET-RT: Sending L1 triggered routes
DNET-RT: Sending L1 triggered routing updates on Ethernet0
DNET-RT: removing route to node 5

Explanations for individual lines of output from Figure 2-52 follow.

The following line indicates that the router has received a level 1 update on interface Ethernet 0:

DNET-RT: Received level 1 routing from 1.3 on Ethernet0 at 1:16:34

The following line indicates that the router is sending its scheduled updates on interface Ethernet 0:

DNET-RT: Sending normal routing updates on Ethernet0

The following line indicates that the route will send an unscheduled update on this interface as a result of some event. In this case, the unscheduled update is a result of a new entry created in the interface's routing table.

DNET-RT: route update triggered by after split route pointers in dn_rt_input

The following line indicates that the router sent the unscheduled update on Ethernet 0:

DNET-RT: Sending L1 triggered routes
DNET-RT: Sending L1 triggered routing updates on Ethernet0

The following line indicates that the router removed the entry for node 5 because the adjacency with node 5 timed out, or the route to node 5 through a next-hop router went away:

DNET-RT: removing route to node 5

debug dialer

Use the debug dialer EXEC command to display debugging information about the packets that are received on a dialer interface. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Table 2-24 describes the error messages that the debug dialer command can generate for a serial interface being used as a V.25bis dialer for dial-on-demand routing (DDR).

Dialing cause: Serial0: ip (s=131.108.1.111 d=131.108.2.22)

Dialing cause: Serial1: Bridge (0x6005)

debug dlsw

Use the debug dlsw EXEC command to enable debugging of data-link switching (DLSw). The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

When you specify no optional keywords, the debug dlsw command enables all available DLSw debugging output.

Sample Display

Figure 2-53 shows sample debug dlsw output.

router# debug dlsw 
DLSw reachability debugging is on
DLSw peer debugging is on
Data Link Switching Core:
  DLSw core XID C/R debugging is on
  DLSw core flow-control  debugging is on
  DLSw core flow-control sender debugging is on
  DLSw core flow-control receiver debugging is on
  DLSw core flow-control sender debugging is on
  DLSw core messages debugging is on
  DLSw core errors debugging is on
  DLSw core states debugging is on
  DLSw core all debugging is on

The lines of output in Figure 2-53 show that all possible debugging is enabled.

debug dspu activation

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

Syntax Description

Command Mode

EXEC

Usage Guidelines

The debug dspu activation command displays all DSPU activation traffic. To restrict the output to a specific host or physical unit (PU), include the host or PU name argument. You cannot turn off debugging output for an individual PU if that PU has not been named in the debug dspu activation command.

Sample Display

Figure 2-54 shows sample debug dspu activation output. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.

router# debug dspu activation 
DSPU: LS HOST3745 connected
DSPU: PU HOST3745 activated
DSPU: LU HOST3745-2 activated
DSPU: LU HOST3745-3 activated
. . .
DSPU: LU HOST3745-253 activated
DSPU: LU HOST3745-254 activated
DSPU: LU HOST3745-2 deactivated
DSPU: LU HOST3745-3 deactivated
. . .
DSPU: LU HOST3745-253 deactivated
DSPU: LU HOST3745-254 deactivated
DSPU: LS HOST3745 disconnected
DSPU: PU HOST3745 deactivated

Table 2-25 describes significant fields in the output shown in Figure 2-54.

Related Commands

debug dspu packet
debug dspu state
debug dspu trace

debug dspu packet

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

Syntax Description

Command Mode

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

Sample Display

Figure 2-55 shows sample debug dspu packet output.

router# debug dspu packet 
DSPU: Rx: PU HOST3745 data length 12 data:
    2D0003002BE16B80 000D0201
DSPU: Tx: PU HOST3745 data length 25 data:
    2D0000032BE1EB80 000D020100850000 000C060000010000 00
DSPU: Rx: PU HOST3745 data length 12 data:
    2D0004002BE26B80 000D0201
DSPU: Tx: PU HOST3745 data length 25 data:
    2D0000042BE2EB80 000D020100850000 000C060000010000 00

Table 2-26 describes significant fields in the output shown in Figure 2-55.

Related Commands

debug dspu activation
debug dspu state
debug dspu trace

debug dspu state

Use the debug dspu state EXEC command to display information on downstream physical unit (DSPU) finite state machine (FSM) state changes. The no form of this command disables debugging output.

Syntax Description

Command Mode

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.

Sample Display

Figure 2-56 shows sample debug dspu state output. Not all intermediate numbers are shown for the "activated" and "deactivated" logical unit (LU) address ranges.

router# debug dspu state 
DSPU: LS HOST3745: input=StartLs, Reset -> PendConOut
DSPU: LS HOST3745: input=ReqOpn.Cnf, PendConOut -> Xid
DSPU: LS HOST3745: input=Connect.Ind, Xid -> ConnIn
DSPU: LS HOST3745: input=Connected.Ind, ConnIn -> Connected
DSPU: PU HOST3745: input=Actpu, Reset -> Active
DSPU: LU HOST3745-2: input=uActlu, Reset -> upLuActive
DSPU: LU HOST3745-3: input=uActlu, Reset -> upLuActive
. . . 
DSPU: LU HOST3745-253: input=uActlu, Reset -> upLuActive
DSPU: LU HOST3745-254: input=uActlu, Reset -> upLuActive
DSPU: LS HOST3745: input=PuStopped, Connected -> PendDisc
DSPU: LS HOST3745: input=Disc.Cnf, PendDisc -> PendClose
DSPU: LS HOST3745: input=Close.Cnf, PendClose -> Reset
DSPU: PU HOST3745: input=T2ResetPu, Active -> Reset
DSPU: LU HOST3745-2: input=uStopLu, upLuActive -> Reset
DSPU: LU HOST3745-3: input=uStopLu, upLuActive -> Reset
. . . 
DSPU: LU HOST3745-253: input=uStopLu, upLuActive -> Reset
DSPU: LU HOST3745-254: input=uStopLu, upLuActive -> Reset

Table 2-26 describes significant fields in the output shown in Figure 2-56.

Related Commands

debug dspu activation
debug dspu packet
debug dspu trace

debug dspu trace

Use the debug dspu trace EXEC command to display information on downstream physical unit (DSPU) trace activity, which includes all finite state machine (FSM) activity. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

Use the debug dspu trace command to display all FSM state changes. To see FSM state changes only, use the debug 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.

Sample Display

Figure 2-57 shows sample debug dspu trace output.

router# debug dspu trace 
DSPU: 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 2-28 describes significant fields in the output shown in Figure 2-57.

Related Commands

debug dspu activation
debug dspu packet
debug dspu state

debug eigrp fsm

Use the debug eigrp fsm EXEC command to display debugging information about Enhanced IGRP feasible successor metrics (FSM). The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command helps you observe Enhanced IGRP feasible successor activity and to determine whether route updates are being installed and deleted by the routing process.

Sample Display

Figure 2-58 shows sample debug eigrp fsm output.

router# debug eigrp fsm
DUAL: dual_rcvupdate(): 198.93.166.0 255.255.255.0 via 0.0.0.0 metric 750080/0
DUAL: Find FS for dest 198.93.166.0 255.255.255.0. FD is 4294967295, RD is 42949
67295 found
DUAL: RT installed 198.93.166.0 255.255.255.0 via 0.0.0.0
DUAL: dual_rcvupdate(): 192.168.4.0 255.255.255.0 via 0.0.0.0 metric 4294967295/
4294967295
DUAL: Find FS for dest 192.168.4.0 255.255.255.0. FD is 2249216, RD is 2249216
DUAL:   0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295
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.0
DUAL: No routes.  Flushing dest 192.168.4.0 255.255.255.0

Explanations for individual lines of output from Figure 2-58 follow.

In the first line of Figure 2-58, DUAL stands for Diffusing Update ALgorithm. It is the basic mechanism within Enhanced IGRP 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. "Metric ... inaccessible" usually means that the neighbor router no longer has a route to the destination, or the destination is in holddown.

In the following output, Enhanced IGRP 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 2249216
DUAL:   0.0.0.0 metric 4294967295/4294967295not found Dmin is 4294967295

The following output indicates the route DUAL successfully installed into the routing table.

DUAL: RT installed 198.93.166.0 255.255.255.0 via 0.0.0.0

The following output shows that no routes were discovered to the destination and 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.0
DUAL: No routes.  Flushing dest 192.168.4.0 255.255.255.0

debug eigrp packet

Use the debug eigrp packet EXEC command to display general debugging information. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

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.

Sample Display

Figure 2-59 shows sample debug eigrp packet output.

router# debug eigrp packet
EIGRP: Sending HELLO on Ethernet0/1
       AS 109, Flags 0x0, Seq 0, Ack 0
EIGRP: Sending HELLO on Ethernet0/1
       AS 109, Flags 0x0, Seq 0, Ack 0
EIGRP: Sending HELLO on Ethernet0/1
       AS 109, Flags 0x0, Seq 0, Ack 0
EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,
       AS 109, Flags 0x1, Seq 1, Ack 0
EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,
       AS 109, Flags 0x0, Seq 0, Ack 1
EIGRP: Sending HELLO/ACK on Ethernet0/1 to 192.195.78.24,
       AS 109, Flags 0x0, Seq 0, Ack 1
EIGRP: Received UPDATE on Ethernet0/1 from 192.195.78.24,
       AS 109, Flags 0x0, Seq 2, Ack 0

Table 2-29 describes significant fields in the output shown in Figure 2-59.

debug frame-relay

Use the debug frame-relay EXEC command to display debugging information about the packets that are received on a Frame Relay interface. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command helps you analyze the packets that have been received. However, because the debug frame-relay command generates a lot of output, only use it when traffic on the Frame Relay network is less than 25 packets per second.

To analyze the packets that have been sent on a Frame Relay interface, use the debug frame-relay packets command.

Sample Display

Figure 2-60 shows sample debug frame-relay output.

router# debug frame-relay
Serial0(i): dlci 500(0x7C41), pkt type 0x809B, datagramsize 24
Serial1(i): dlci 1023(0xFCF1), pkt type 0x309, datagramsize 13
Serial0(i): dlci 500(0x7C41), pkt type 0x809B, datagramsize 24
Serial1(i): dlci 1023(0xFCF1), pkt type 0x309, datagramsize 13
Serial0(i): dlci 500(0x7C41), pkt type 0x809B, datagramsize 24

Table 2-30 describes significant fields shown in Figure 2-60.

debug frame-relay events

Use the debug frame-relay events EXEC command to display debugging information about Frame Relay ARP replies on networks that support a multicast channel and use dynamic addressing. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command is useful for identifying the cause of end-to-end connection problems during the installation of a Frame Relay network or node.

Sample Display

Figure 2-61 shows sample debug frame-relay events output.

router# debug frame-relay events
Serial2(i): reply rcvd 131.108.170.26 126
Serial2(i): reply rcvd 131.108.170.28 128
Serial2(i): reply rcvd 131.108.170.34 134
Serial2(i): reply rcvd 131.108.170.38 144
Serial2(i): reply rcvd 131.108.170.41 228
Serial2(i): reply rcvd 131.108.170.65 325

As Figure 2-61 shows, debug frame-relay events returns one specific message type. The first line, for example, indicates that IP address 131.108.170.26 sent a Frame Relay ARP reply; this packet was received as input on the Serial2 interface. The last field (126) is the data link connection identifier (DLCI) to use when communicating with the responding router.

debug frame-relay lmi

Use the debug frame-relay lmi EXEC command to display information on the local management interface (LMI) packets exchanged by the router and the Frame Relay service provider. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

You can use this command to determine whether the router and the Frame Relay switch are sending and receiving LMI packets properly.

Sample Display

Figure 2-62 shows sample debug frame-relay lmi output.

Figure 2-62: Sample Debug Frame-Relay LMI Output

In Figure 2-62, the first four lines describe an LMI exchange. The first line describes the LMI request the router has sent to the switch. The second line describes the LMI reply the router has received from the switch. The third and fourth lines describe the response to this request from the switch. This LMI exchange is followed by two similar LMI exchanges. The last six lines in Figure 2-62 consist of a full LMI status message that includes a description of the router's two permanent virtual circuits (PVCs).

Table 2-31 describes significant fields in the first line of the debug frame-relay lmi output shown in Figure 2-62.

Table 2-32 describes significant fields in the third and fourth lines of debug frame-relay lmi output shown in Figure 2-62.

Table 2-33 describes significant fields in the last line of debug frame-relay lmi output shown in Figure 2-62.

debug frame-relay packets

Use the debug frame-relay packets EXEC command to display information on packets that have been sent on a Frame Relay interface. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command helps you analyze the packets that are sent on a Frame Relay interface. Because the debug frame-relay packets command generates large amounts of output, only use it when traffic on the Frame Relay network is less than 25 packets per second.

To analyze the packets received on a Frame Relay interface, use the debug frame-relay command.

Sample Display

Figure 2-63 shows sample debug frame-relay packets output.

Figure 2-63: Sample Debug Frame-Relay Packets Output

As Figure 2-63 shows, debug frame-relay packets output consists of groups of output lines; each group describes a Frame Relay packet that has been sent. The number of lines in the group can vary, depending on the number of data link connection identifiers (DLCIs) on which the packet was sent. For example, the first two pairs of output lines describe two different packets, both of which were sent out on a single DLCI. The last three lines in Figure 2-63 describe a single Frame Relay packet that was sent out on two DLCIs.

Table 2-34 describes significant fields shown in the first pair of output lines in Figure 2-63.

Explanations for other lines of output shown in Figure 2-63 follow:

The following lines describe a Frame Relay packet sent to a particular address; in this case AppleTalk address 10.2:

Serial0: broadcast - 0, link 809B, addr 10.2
Serial0(o):DLCI 100 type 809B size 104

The following lines describe a Frame Relay packet that went out on two different DLCIs, because two Frame Relay map entries were found:

Serial0: broadcast search
Serial0(o):DLCI 300 type 809B size 24
Serial0(o):DLCI 400 type 809B size 24

The following lines do not appear in Figure 2-63. They describe a Frame Relay packet sent to a true broadcast address.

Serial1: broadcast search
Serial1(o):DLCI 400 type 800 size 288

debug ip dvmrp

Use the debug ip dvmrp EXEC command to display information on Distance Vector Multiprotocol Routing Protocol (DVMRP) packets received and transmitted. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

Use the debug ip dvmrp detail command with care. This command generates a great deal of output and can interrupt other activity on the router when it is invoked.

Sample Display

Figure 2-64 shows sample debug ip dvmrp output.

router# debug ip dvmrp
DVMRP: Received Report on Ethernet0 from 131.119.244.10
DVMRP: Received Report on Ethernet0 from 131.119.244.11
DVMRP: Building Report for Ethernet0 224.0.0.4
DVMRP: Send Report on Ethernet0 to 224.0.0.4
DVMRP: Sending IGMP Reports for known groups on Ethernet0
DVMRP: Received Report on Ethernet0 from 131.119.244.10
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Building Report for Tunnel0 224.0.0.4
DVMRP: Send Report on Tunnel0 to 198.104.199.254
DVMRP: Send Report on Tunnel0 to 198.104.199.254
DVMRP: Send Report on Tunnel0 to 198.104.199.254
DVMRP: Send Report on Tunnel0 to 198.104.199.254
DVMRP: Radix tree walk suspension
DVMRP: Send Report on Tunnel0 to 198.104.199.254

Explanations for individual lines of output from Figure 2-64 follow.

The following lines show that the router received DVMRP routing information and placed it in the mroute table:

DVMRP: Received Report on Ethernet0 from 131.119.244.10
DVMRP: Received Report on Ethernet0 from 131.119.244.11

The following lines show that the router is creating a report to send to other DVMRP router:

DVMRP: Building Report for Ethernet0 224.0.0.4
DVMRP: Send Report on Ethernet0 to 224.0.0.4

Table 2-35 provides a list of internet multicast addresses supported for host IP implementations.

DVMRP: Sending IGMP Reports for known groups on Ethernet0

Figure 2-65 shows sample debug ip dvmrp detail output.

router# debug ip dvmrp detail 
DVMRP: Sending IGMP Reports for known groups on Ethernet0
DVMRP: Advertise group 224.2.224.2 on Ethernet0
DVMRP: Advertise group 224.2.193.34 on Ethernet0
DVMRP: Advertise group 224.2.231.6 on Ethernet0
DVMRP: Received Report on Tunnel0 from 198.104.199.254
DVMRP: Origin 150.166.53.0/24, metric 13, distance 0
DVMRP: Origin 150.166.54.0/24, metric 13, distance 0
DVMRP: Origin 150.166.55.0/24, metric 13, distance 0
DVMRP: Origin 150.166.56.0/24, metric 13, distance 0
DVMRP: Origin 150.166.92.0/24, metric 12, distance 0
DVMRP: Origin 150.166.100.0/24, metric 12, distance 0
DVMRP: Origin 150.166.101.0/24, metric 12, distance 0
DVMRP: Origin 150.166.142.0/24, metric 8, distance 0
DVMRP: Origin 150.166.200.0/24, metric 12, distance 0
DVMRP: Origin 150.166.237.0/24, metric 12, distance 0
DVMRP: Origin 150.203.5.0/24, metric 8, distance 0

Explanations for individual lines of output from Figure 2-65 follow.

The following lines show that this group is available to the DVMRP router. The mrouted process on the host will forward the S,G information for theis group through the DVMRP cloud so other members will know this S,G is available.

DVMRP: Advertise group 224.2.224.2 on Ethernet0

The following lines show the DVMRP route information:

DVMRP: Origin 150.166.53.0/24, metric 13, distance 0
DVMRP: Origin 150.166.54.0/24, metric 13, distance 0

Metric is the number of hops the route has covered. Distance is the administrative distance.

debug ip eigrp

Use the debug ip eigrp EXEC command to display information on Enhanced IGRP protocol packets. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command helps you analyze the packets that are sent and received on an interface. Because the debug ip eigrp command generates large amounts of output, only use it when traffic on the network is light.

Sample Display

Figure 2-66 shows sample debug ip eigrp output.

router# debug ip eigrp
IP-EIGRP: Processing incoming UPDATE packet
IP-EIGRP: Ext 198.135.3.0 255.255.255.0 M 386560 - 256000 130560 SM 360960 - 256
000 104960
IP-EIGRP: Ext 198.135.0.0 255.255.255.0 M 386560 - 256000 130560 SM 360960 - 256
000 104960
IP-EIGRP: Ext 198.135.3.0 255.255.255.0 M 386560 - 256000 130560 SM 360960 - 256
000 104960
IP-EIGRP: 198.92.43.0 255.255.255.0, - do advertise out Ethernet0/1
IP-EIGRP: Ext 198.92.43.0 255.255.255.0 metric 371200 - 256000 115200
IP-EIGRP: 192.135.246.0 255.255.255.0, - do advertise out Ethernet0/1
IP-EIGRP: Ext 192.135.246.0 255.255.255.0 metric 46310656 - 45714176 596480
IP-EIGRP: 198.92.40.0 255.255.255.0, - do advertise out Ethernet0/1
IP-EIGRP: Ext 198.92.40.0 255.255.255.0 metric 2272256 - 1657856 614400
IP-EIGRP: 192.135.245.0 255.255.255.0, - do advertise out Ethernet0/1
IP-EIGRP: Ext 192.135.245.0 255.255.255.0 metric 40622080 - 40000000 622080
IP-EIGRP: 192.135.244.0 255.255.255.0, - do advertise out Ethernet0/1

Table 2-36 describes significant fields in the debug messages shown in Figure 2-66.

debug ip icmp

Use the debug ip icmp EXEC command to display information on Internal Control Message Protocol (ICMP) transactions. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command helps you determine whether the router is sending or receiving ICMP messages. Use it, for example, when you are troubleshooting an end-to-end connection problem.

Sample Display

Figure 2-67 shows sample debug ip icmp output.

router# debug ip icmp
ICMP: rcvd type 3, code 1, from 128.95.192.4
ICMP: src 36.56.0.202, dst 131.108.16.1, echo reply
ICMP: dst (131.120.1.0) port unreachable rcv from 131.120.1.15
ICMP: src 131.108.12.35, dst 131.108.20.7, echo reply
ICMP: dst (255.255.255.255) protocol unreachable rcv from 192.31.7.21
ICMP: dst (131.120.1.0) port unreachable rcv from 131.120.1.15
ICMP: dst (255.255.255.255) protocol unreachable rcv from 192.31.7.21
ICMP: dst (131.120.1.0) port unreachable rcv from 131.120.1.15
ICMP: src 36.56.0.202, dst 131.108.16.1, echo reply
ICMP: dst (131.120.1.0) port unreachable rcv from 131.120.1.15
ICMP: dst (255.255.255.255) protocol unreachable rcv from 192.31.7.21
ICMP: dst (131.120.1.0) port unreachable rcv from 131.120.1.15

Table 2-37 describes significant fields in the first line of debug ip icmp output shown in Figure 2-67.

Table 2-38 describes significant fields in the second line of debug ip icmp output in Figure 2-67.

When an IP router or host sends out an ICMP mask request, the following message is generated when the router sends a mask reply:

ICMP: sending mask reply (255.255.255.0) to 160.89.80.23 via Ethernet0

The following two lines are examples of the two forms of this message. The first form is generated when a mask reply comes in after the router sends out a mask request. The second form occurs when the router receives a mask reply with a nonmatching sequence and ID. See Appendix I of RFC 950, "Internet Standard Subnetting Procedures," for details.

ICMP: mask reply 255.255.255.0 from 160.89.80.31
ICMP: unexpected mask reply 255.255.255.0 from 160.89.80.32

The following output indicates that the router sent a redirect packet to the host at address 160.89.80.31, instructing that host to use the gateway at address 160.89.80.23 in order to reach the host at destination address 131.108.1.111:

ICMP: redirect sent to 160.89.80.31 for dest 131.108.1.111 use gw 160.89.80.23

The following message indicates that the router received a redirect packet from the host at address 160.89.80.23, instructing the router to use the gateway at address 160.89.80.28 in order to reach the host at destination address 160.89.81.34:

ICMP: redirect rcvd from 160.89.80.23 -- for 160.89.81.34 use gw 160.89.80.28

The following message is displayed when the router sends an ICMP packet to the source address (160.89.94.31 in this case), indicating that the destination address (131.108.13.33 in this case) is unreachable:

ICMP: dst (131.108.13.33) host unreachable sent to 160.89.94.31

The following message is displayed when the router receives an ICMP packet from an intermediate address (160.89.98.32 in this case), indicating that the destination address (131.108.13.33 in this case) is unreachable:

ICMP: dst (131.108.13.33) host unreachable rcv from 160.89.98.32

Depending on the code received (as Table 2-37 describes), any of the unreachable messages can have any of the following "strings" instead of the "host" string in the message:

net
protocol
port
frag. needed and DF set
source route failed
prohibited

The following message is displayed when the TTL in the IP header reaches zero and a time exceed ICMP message is sent. The fields are self-explanatory.

ICMP: time exceeded (time to live) send to 128.95.1.4 (dest was 131.108.1.111)

The following message is generated when parameters in the IP header are corrupted in some way and the parameter problem ICMP message is sent. The fields are self-explanatory.

ICMP: parameter problem sent to 128.121.1.50 (dest was 131.108.1.111)

Based on the preceding information, the remaining output can be easily understood.

ICMP: parameter problem rcvd 160.89.80.32
ICMP: source quench rcvd 160.89.80.32
ICMP: source quench sent to 128.121.1.50 (dest was 131.108.1.111)
ICMP: sending time stamp reply to 160.89.80.45
ICMP: sending info reply to 160.89.80.12
ICMP: rdp advert rcvd type 9, code 0, from 160.89.80.23
ICMP: rdp solicit rcvd type 10, code 0, from 160.89.80.43

debug ip igmp

Use the debug ip igmp EXEC command to display Internet Group Management Protocol (IGMP) packets received and transmitted, as well as IGMP-host related events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Notes

This command helps discover whether the IGMP processes are functioning. In general, if IGMP is not working, the router process never discovers that there is another host on the network that is configured to receive multicast packets. In dense mode this means the packets will be delivered intermittently (a few every 3 minutes). In sparse mode they will never be delivered.

Use this command in conjunction with debug ip pim and debug ip mrouting to observe additional multicast activity and to see what is happening the the multicast routing process, or why packets are forwarded out of particular interfaces.

Sample Display

Figure 2-68 shows sample debug ip igmp output.

router# debug ip igmp 
IGMP: Received Host-Query from 198.92.37.33 (Ethernet1) 
IGMP: Received Host-Report from 198.92.37.192 (Ethernet1) for 224.0.255.1 
IGMP: Received Host-Report from 198.92.37.57 (Ethernet1) for 224.2.127.255 
IGMP: Received Host-Report from 198.92.37.33 (Ethernet1) for 225.2.2.2 

Related Commands

debug ip pim
debug ip mrouting

debug ip igrp events

Use the debug ip igrp events EXEC command to display summary information on Interior Gateway Routing Protocol (IGRP) routing messages that indicates the source and destination of each update, as well as the number of routes in each update. Messages are not generated for each route. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

If the IP address of an IGRP neighbor is specified, the resulting debug ip igrp events output includes messages describing updates from that neighbor and updates that the router broadcasts toward that neighbor.

This command is particularly useful when there are many networks in your routing table. In this case, using debug ip igrp transaction could flood the console and make the router unusable. Use debug ip igrp events instead to display summary routing information.

Sample Display

Figure 2-69 shows sample debug ip igrp events output.

Figure 2-69: Sample Debug IP IGRP Events Output

Figure 2-69 shows that the router has sent two updates to the broadcast address 255.255.255.255. The router also received two updates. Three lines of output describe each of these updates.

The first line indicates whether the router sent or received the update packet, the source or destination address, and the interface through which the update was sent or received. If the update was sent, the IP address assigned to this interface is shown (in parentheses).

IGRP: sending update to 255.255.255.255 via Ethernet1 (160.89.33.8)

The second line summarizes the number and types of routes described in the update:

IGRP: Update contains 26 interior, 40 system, and 3 exterior routes.

The third line indicates the total number of routes described in the update.

IGRP: Total routes in update: 69

debug ip igrp transaction

Use the debug ip igrp transaction EXEC command to display transaction information on Interior Gateway Routing Protocol (IGRP) routing transactions. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

If the IP address of an IGRP neighbor is specified, the resulting debug ip igrp transaction output includes messages describing updates from that neighbor and updates that the router broadcasts toward that neighbor.

When there are many networks in your routing table, debug ip igrp transaction can flood the console and make the router unusable. In this case, use debug ip igrp events instead to display summary routing information.

Sample Display

Figure 2-70 shows sample debug ip igrp transaction output.

Figure 2-70: Sample Debug IP IGRP Transaction Output

Figure 2-70 shows that the router being debugged has received updates from two other routers on the network. The router at source address 160.89.80.240 sent information about ten destinations in the update; the router at source address 160.89.80.28 sent information about three destinations in its update. The router being debugged also sent updates--in both cases to the broadcast address 255.255.255.255 as the destination address.

The first line in Figure 2-70 is self-explanatory.

On the second line in Figure 2-70, the first field refers to the type of destination information: "subnet" (interior), "network" (system), or "exterior" (exterior). The second field is the Internet address of the destination network. The third field is the metric stored in the routing table and the metric advertised by the neighbor sending the information. "Metric ... inaccessible" usually means that the neighbor router has put the destination in holddown.

The entries in Figure 2-70 show that the router is sending updates that are similar, except that the numbers in parentheses are the source addresses used in the IP header. A metric of 16777215 is inaccessible.

Other examples of output that the debug ip igrp transaction command can produce follow.

The following entry indicates that the routing table was updated and shows the new edition number (97 in this case) to be used in the next IGRP update:

IGRP: edition is now 97

Entries such as the following occur on startup or when some event occurs such as an interface transitioning or a user manually clearing the routing table:

IGRP: broadcasting request on Ethernet0
IGRP: broadcasting request on Ethernet1

The following type of entry can result when routing updates become corrupted between sending and receiving routers:

IGRP: bad checksum from 160.89.64.43

An entry such as the following should never appear. If it does, the receiving router has a bug in the software or a problem with the hardware. In either case, contact your technical support representative.

IGRP: system 45 from 160.89.64.234, should be system 109

Use the debug ip mpacket EXEC command to display only IP multicast packets received and transmitted.The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

This command displays information for multicast IP packets that are forwarded from this router. By using the optional group, you can limit the display to a specific multicast group.

Use this command with debug ip packet to observe additional packet information.

Sample Display

Figure 2-71 shows sample debug ip mpacket output.

router# debug ip mpacket 224.2.0.1 
IP: s=131.188.34.54 (Ethernet1), d=224.2.0.1 (Tunnel0), len 88, mforward 
IP: s=131.188.34.54 (Ethernet1), d=224.2.0.1 (Tunnel0), len 88, mforward 
IP: s=131.188.34.54 (Ethernet1), d=224.2.0.1 (Tunnel0), len 88, mforward 
IP: s=140.162.3.27 (Ethernet1), d=224.2.0.1 (Tunnel0), len 68, mforward 

Table 2-39 defines fields shown in Figure 2-71.

Related Commands

debug ip dvmrp
debug ip igmp
debug ip mrouting
debug ip packet
debug ip sd

debug ip mcache

Use the debug ip mcache command to display IP multicast fast-switching events. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

Use this command when multicast fast-switching appears not to be functioning.

Sample Display

Figure 2-72 shows sample debug ip mcache output when an IP multicast route is cleared.

router# debug ip mcache
IP multicast fast-switching debugging is on
router#clear ip mroute *
MRC: Build MAC header for (171.69.60.185/32, 224.2.231.173), Ethernet0
MRC: Fast-switch flag for (171.69.60.185/32, 224.2.231.173), off -> on, caller ip_mroute_replicate-1
MRC: Build MAC header for (171.69.191.10/32, 224.2.127.255), Ethernet0
MRC: Build MAC header for (171.69.60.152/32, 224.2.231.173), Ethernet0

Table 2-40 provides explanations for representative lines of the debug ip mcache output shown in Figure 2-72.

Related Commands

debug ip dvmrp
debug ip igmp
debug ip igrp transaction
debug ip mrouting
debug ip sd

debug ip mrouting

Use the debug ip mrouting EXEC command to display changes to the IP multicast routing table. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Notes

This command tells when the router has made changes to the mroute table. Use the debug ip pim and debug ip mrouting commands at the same time to obtain additional multicast routing information. In addition, use the debug ip igmp command to see why an mroute message is being displayed.

This command generates a large amount of output. Use the optional group to limit the output to a single multicast group.

Sample Display

Figure 2-73 shows sample debug ip mrouting output.

router# debug ip mrouting 224.2.0.1 
IP multicast routing debugging is on 
MRT: Delete (13.0.0.0/8, 224.2.0.1) 
MRT: Delete (128.3.0.0/16, 224.2.0.1) 
MRT: Delete (128.6.0.0/16, 224.2.0.1) 
MRT: Delete (128.9.0.0/16, 224.2.0.1) 
MRT: Delete (128.16.0.0/16, 224.2.0.1) 
MRT: Create (*, 224.2.0.1), if_input NULL 
MRT: Create (198.92.15.0/24, 225.2.2.4), if_input Ethernet0, RPF nbr 131.108.61.15
MRT: Create (198.92.39.0/24, 225.2.2.4), if_input Ethernet1, RPF nbr 0.0.0.0
MRT: Create (13.0.0.0/8, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 
MRT: Create (128.3.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 
MRT: Create (128.6.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 
MRT: Create (128.9.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 
MRT: Create (128.16.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 

Explanations for individual lines of output from Figure 2-73 follow.

The following lines show that multicast IP routes were deleted from the routing table:

MRT: Delete (13.0.0.0/8, 224.2.0.1) 
MRT: Delete (128.3.0.0/16, 224.2.0.1) 
MRT: Delete (128.6.0.0/16, 224.2.0.1) 

The *,G entry in the following line is always null since it is a *,G. The *,G entries are generally created by receipt of an IGMP host-report from a group member on the directly connected lan or by a PIM join message (in sparse mode) which this router receives from a router that is sending joins toward the RP. This router will in turn, send a join toward the RP which creates the shared tree (or RP tree).

MRT: Create (*, 224.2.0.1), if_input NULL 

The following lines are an example of creating an S,G entry that show a mpacket was received on E0. The second line shows a route being created for a source that is on a directly connected LAN. The RPF means "reverse path forwarding," whereby the router looks up the source address of the multicast packet in the unicast routing table and asks which interface will be used to send a packet to that source.

MRT: Create (198.92.15.0/24, 225.2.2.4), if_input Ethernet0, RPF nbr 131.108.61.15
MRT: Create (198.92.39.0/24, 225.2.2.4), if_input Ethernet1, RPF nbr 0.0.0.0

The following lines show that multicast IP routes were added to the routing table. Note the 0.0.0.0 as the RPF, which means the route was created by a source that is directly connected to this router.

MRT: Create (128.9.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 
MRT: Create (128.16.0.0/16, 224.2.0.1), if_input Ethernet1, RPF nbr 0.0.0.0 

If the source is not directly connected, the nbr address shown in these lines will be the address of the router that forwarded the packet to this router.

The shortest path tree state maintained in routers consists of source (S), multicast address (G), outgoing interface (OIF), and incoming interface (IIF). The forwarding information is referred to as the multicast forwarding entry for (S,G).

An entry for a shared tree can match packets from any source for its associated group if the packets come through the proper incoming interface as determined by the RPF lookup. Such an entry is denoted as (*,G). A (*,G) entry keeps the same information a (S,G) entry keeps, except that it saves the rendezvous point (RP) address in place of the source address in sparse mode or 0.0.0.0 in dense mode.

Related Commands

debug ip dvmrp
debug ip igmp
debug ip pim
debug ip packet
debug ip sd

debug ip ospf events

Use the debug ip ospf events EXEC command to display information on Open Shortest Path First (OSPF)-related events, such as adjacencies, flooding information, designated router selection, and shortest path first (SPF) calculation. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-74 shows sample debug ip ospf events output.

router# debug ip ospf-events
OSPF:hello with invalid timers on interface Ethernet0
hello interval received 10  configured 10
net mask received 255.255.255.0  configured 255.255.255.0
dead interval received 40  configured 30

The debug ip ospf events output shown in Figure 2-74 might appear if any of the following occurs:

• The IP subnet masks for routers on the same network do not match.

• The OSPF hello interval for the router does not match that configured for a neighbor.

• The OSPF dead interval for the router does not match that configured for a neighbor.

If a router configured for OSPF routing is not seeing an OSPF neighbor on an attached network, do the following:

• Make sure that both routers have been configured with the same IP mask, OSPF hello interval, and OSPF dead interval.

• Make sure that both neighbors are part of the same area type.

In the following example line, the neighbor and this router are not part of a stub area (that is, one is a part of a transit area and the other is a part of a stub area, as explained in RFC 1247).

OSPF: hello packet with mismatched E bit

Related Command

debug ip ospf packet

debug ip ospf packet

Use the debug ip ospf packet EXEC command to display information about each Open Shortest Path First (OSPF) packet received. The no form of this command disables debugging output.

Sample Display

Figure 2-75 shows sample debug ip ospf packet output.

router# debug ip ospf packet
OSPF: rcv. v:2 t:1 l:48 rid:200.0.0.117
      aid:0.0.0.0 chk:6AB2 aut:0 auk:

The debug ip ospf packet command produces one set of information for each packet received. The output varies slightly depending on which authentication is used. Figure 2-76 shows sample debug ip ospf packet output when MD5 authentication is used.

router# debug ip ospf packet
OSPF: rcv. v:2 t:1 l:48 rid:200.0.0.116
      aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x0

Table 2-41 describes the fields shown in Figure 2-75 and Figure 2-76.

Related Command

debug ip ospf events

debug ip packet

Use the debug ip packet EXEC command to display general IP debugging information and IP security option (IPSO) security transactions. The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

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 ip packet command is useful for analyzing the messages traveling between the local and remote hosts.

IP debugging information includes packets received, generated, and forwarded. Fast-switched packets do not generate messages.

IPSO security transactions include messages that describe the cause of failure each time a datagram fails a security test in the system. This information is also sent to the sending host when the router configuration allows it.

Sample Display

Figure 2-77 shows sample debug ip packet output.

router# debug ip packet
IP: s=131.108.13.44 (Fddi0), d=157.125.254.1 (Serial2), g=131.108.16.2, forward
IP: s=131.108.1.57 (Ethernet4), d=192.36.125.2 (Serial2), g=131.108.16.2, forward
IP: s=131.108.1.6 (Ethernet4), d=255.255.255.255, rcvd 2
IP: s=131.108.1.55 (Ethernet4), d=131.108.2.42 (Fddi0), g=131.108.13.6, forward
IP: s=131.108.89.33 (Ethernet2), d=131.130.2.156 (Serial2), g=131.108.16.2, forward
IP: s=131.108.1.27 (Ethernet4), d=131.108.43.126 (Fddi1), g=131.108.23.5, forward
IP: s=131.108.1.27 (Ethernet4), d=131.108.43.126 (Fddi0), g=131.108.13.6, forward
IP: s=131.108.20.32 (Ethernet2), d=255.255.255.255, rcvd 2
IP: s=131.108.1.57 (Ethernet4), d=192.36.125.2 (Serial2), g=131.108.16.2, access denied

Figure 2-77 shows two types of messages that the debug ip packet command can produce; the first line of output describes an IP packet that the router forwards, and the third line of output describes a packet that is destined for the router. In the third line of output, "rcvd 2" indicates that the router decided to receive the packet.

Table 2-42 describes the fields shown in the first line of Figure 2-77.

The calculation on whether to send a security error message can be somewhat confusing. It depends upon both the security label in the datagram and the label of the incoming interface. First, the label contained in the datagram is examined for anything obviously wrong. If nothing is wrong, assume it to be correct. If there is something wrong, the datagram is treated as unclassified genser. Then the label is compared with the interface range, and the appropriate action is taken as Table 2-43 describes.

The security code can only generate a few types of ICMP error messages. The only possible error messages and their meanings follow:

• "ICMP Parameter problem, code 0"--Error at pointer

• "ICMP Parameter problem, code 1"--Missing option

• "ICMP Parameter problem, code 2"--See Note that follows

• "ICMP Unreachable, code 10"--Administratively prohibited

When an IP packet is rejected due to an IP security failure, an audit message is sent via DNSIX NAT. Also, any debug ip packet output is appended to include a description of the reason for rejection. This description can be any of the following:

• No basic

• No basic, no response

• Reserved class

• Reserved class, no response

• Class too low, no response

• Class too high

• Class too high, bad authorities, no response

• Unrecognized class

• Unrecognized class, no response

• Multiple basic

• Multiple basic, no response

• Authority too low, no response

• Authority too high

• Compartment bits not dominated by maximum sensitivity level

• Compartment bits do not dominate minimum sensitivity level

• Security failure: extended security disallowed

• NLESO source appeared twice

• ESO source not found

• Postroute, failed xfc out

• No room to add IPSO

debug ip pim

Use the debug ip pim EXEC command to display Protocol Independent Multicast (PIM) packets received and transmitted as well as PIM related events.The no form of this command disables debugging output.

Syntax Description

Command Mode

EXEC

Usage Guidelines

PIM uses IGMP packets to communicate between routers and advertise reachability information.

Use this command with debug ip igmp and debug ip mrouting to observe additional multicast routing information.

Sample Display

Figure 2-78 shows sample debug ip pim output.

router# debug ip pim 224.2.0.1 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 
PIM: Received Join/Prune on Tunnel0 from 10.3.84.1 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33
PIM: Received RP-Reachable on Ethernet1 from 131.108.20.31 
PIM: Update RP expiration timer for 224.2.0.1 
PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 
PIM: Prune-list (163.221.196.51/32, 224.2.0.1)   
PIM: Set join delay timer to 2 seconds for (163.221.0.0/16, 224.2.0.1) on Ethernet1 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.6 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 
PIM: Received Join/Prune on Tunnel0 from 10.3.84.1 
PIM: Join-list: (*, 224.2.0.1) RP 131.108.20.31 
PIM: Add Tunnel0 to (*, 224.2.0.1), Forward state 
PIM: Join-list: (13.0.0.0/8, 224.2.0.1)   
PIM: Add Tunnel0 to (13.0.0.0/8, 224.2.0.1), Forward state 
PIM: Join-list: (128.3.0.0/16, 224.2.0.1)   
PIM: Prune-list (198.92.84.16/28, 224.2.0.1) RP-bit set RP 198.92.84.16 
PIM: Send Prune on Ethernet1 to 198.92.37.6 for (198.92.84.16/28, 224.2.0.1), RP 
PIM: For RP, Prune-list: 128.9.0.0/16 
PIM: For RP, Prune-list: 128.16.0.0/16 
PIM: For RP, Prune-list: 128.49.0.0/16 
PIM: For RP, Prune-list: 128.84.0.0/16 
PIM: For RP, Prune-list: 128.146.0.0/16 
PIM: For 10.3.84.1, Join-list: 198.92.84.16/28 
PIM: Send periodic Join/Prune to RP via 198.92.37.6 (Ethernet1) 

Explanations for individual lines of output from Figure 2-78 follow.

The following lines appear periodically when PIM is running in sparse mode and indicate to this router which multicast groups and multicast sources other routers are interested in:

PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 
PIM: Received Join/Prune on Ethernet1 from 198.92.37.33 

The following lines appear when a rendezvous point (RP) message is received and the RP timer is reset. The expiration timer sets a checkpoint to make sure the RP still exists; otherwise a new RP must be discovered:

PIM: Received RP-Reachable on Ethernet1 from 131.108.20.31 
PIM: Update RP expiration timer for 224.2.0.1 
PIM: Forward RP-reachability packet for 224.2.0.1 on Tunnel0 

The prune-list message in the following line states that this router is not interested in the source address information. The prune message tells an upstream router to stop forwarding multicast packets from this source.

PIM: Prune-list (163.221.196.51/32, 224.2.0.1)   

In the following line, a second router on the network wants to override the prune message that the upstream router just received. The timer is set at a random value so that if there are additional routers on the network that still want to receive multicast packets for the group, only one will actually send the message. The other routers will receive the join message and then suppress sending their own message.

PIM: Set join delay timer to 2 seconds for (163.221.0.0/16, 224.2.0.1) on Ethernet1 

In the following line, a join message is sent towards the RP for all sources:

PIM: Join-list: (*, 224.2.0.1) RP 131.108.20.31 

In the following lines, the interface is being added to the outgoing interface (OIF) of the *,G and S,G mroute table entry so that packets from the source will be forwarded out that particular interface:

PIM: Add Tunnel0 to (*, 224.2.0.1), Forward state 
PIM: Add Tunnel0 to (13.0.0.0/8, 224.2.0.1), Forward state 

The following line appears in sparse mode only. There are two trees on which data may be received: the RP tree and the source tree. In dense mode there is no RP. After the source and the receiver have discovered one another at the RP, the first-hop router for the receiver will usually join to the source tree rather than the RP tree:

PIM: Prune-list (198.92.84.16/28, 224.2.0.1) RP-bit set RP 198.92.84.16 

The Send Prune message in the next line shows that a router is sending a message to a second router saying that the first router no longer wants to receive multicast packets for the S,G. The "RP" at the end of the message indicates that the router is pruning the RP tree and is most likely joining the source tree, although the router may not have downstream members for the group or downstream routers with members of the group. The output shows which specific sources this router no longer wants to receive multicast from.

PIM: Send Prune on Ethernet1 to 198.92.37.6 for (198.92.84.16/28, 224.2.0.1), RP 

The following lines indicate a prune message is sent toward the RP so that router can join the source tree rather than the RP tree:

PIM: For RP, Prune-list: 128.9.0.0/16 
PIM: For RP, Prune-list: 128.16.0.0/16 
PIM: For RP, Prune-list: 128.49.0.0/16 

In the following line, a periodic message is sent towards the RP. The default period is once per minute. Prune and join messages are sent toward the RP or source rather than directly to the RP or source. It is the responsibility of the next-hop router to take proper action with this message, such as continuing to forward it to the next router in the tree.

PIM: Send periodic Join/Prune to RP via 198.92.37.6 (Ethernet1) 

Related Commands

debug ip dvmrp
debug ip igmp
debug ip igrp transaction
debug ip mrouting
debug ip sd

debug ip rip

Use the debug ip rip EXEC command to display information on RIP routing transactions. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-79 shows sample debug ip rip output.

Figure 2-79: Sample Debug IP RIP Output

Figure 2-79 shows that the router being debugged has received updates from one router at source address 160.89.80.28. That router sent information about five destinations in the routing table update. Notice that the fourth destination address in the update--131.108.0.0--is inaccessible because it is more than 15 hops away from the router sending the update. The router being debugged also sent updates, in both cases to broadcast address 255.255.255.255 as the destination.

The first line in Figure 2-79 is self-explanatory.

The second line in Figure 2-79 is an example of a routing table update. It shows how many hops a given Internet address is from the router.

The entries in Figure 2-79 show that the router is sending updates that are similar, except that the number in parentheses is the source address encapsulated into the IP header.

Examples of additional output that the debug ip rip command can generate follow.

Entries such as the following appear at startup or when an event occurs such as an interface transitioning or a user manually clearing the routing table:

RIP: broadcasting general request on Ethernet0
RIP: broadcasting general request on Ethernet1

The following line is self-explanatory:

RIP: received request from 160.89.80.207 on Ethernet0

An entry such as the following is most likely caused by a malformed packet from the transmitter:

RIP: bad version 128 from 160.89.80.43

debug ip routing

Use the debug ip routing EXEC command to display information on Routing Information Protocol (RIP) routing table updates and route-cache updates. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Sample Display

Figure 2-80 shows sample debug ip routing output.

router# debug ip routing
RT: add 198.93.168.0 255.255.255.0 via 198.92.76.30, igrp metric [100/3020]
RT: metric change to 198.93.168.0 via 198.92.76.30, igrp metric [100/3020]
        new metric [100/2930]
IP: cache invalidation from 0x115248 0x1378A, new version 5736
RT: add 198.133.219.0 255.255.255.0 via 198.92.76.30, igrp metric [100/16200]
RT: metric change to 198.133.219.0 via 198.92.76.30, igrp metric [100/16200]
        new metric [100/10816]
RT: delete route to 198.133.219.0 via 198.92.76.30, igrp metric [100/10816]
RT: no routes to 198.133.219.0, entering holddown
IP: cache invalidation from 0x115248 0x1378A, new version 5737
RT: 198.133.219.0 came out of holddown
RT: garbage collecting entry for 198.133.219.0
IP: cache invalidation from 0x115248 0x1378A, new version 5738
RT: add 198.133.219.0 255.255.255.0 via 198.92.76.30, igrp metric [100/10816]
RT: delete route to 198.133.219.0 via 198.92.76.30, igrp metric [100/10816]
RT: no routes to 198.133.219.0, entering holddown
IP: cache invalidation from 0x115248 0x1378A, new version 5739
RT: 198.133.219.0 came out of holddown
RT: garbage collecting entry for 198.133.219.0
IP: cache invalidation from 0x115248 0x1378A, new version 5740
RT: add 198.133.219.0 255.255.255.0 via 198.92.76.30, igrp metric [100/16200]
RT: metric change to 198.133.219.0 via 198.92.76.30, igrp metric [100/16200]
        new metric [100/10816]
RT: delete route to 198.133.219.0 via 198.92.76.30, igrp metric [100/10816]
RT: no routes to 198.133.219.0, entering holddown
IP: cache invalidation from 0x115248 0x1378A, new version 5741

Explanations for representative lines of output in Figure 2-80 follow.

In the following lines, a newly created entry has been added to the IP routing table. The "metric change" indicates that this entry existed previously, but its metric changed and the change was reported by means of IGRP. The metric could also be reported via RIP, OSPF, or another IP routing protocol. The numbers inside the brackets report the administrative distance and the actual metric.

"Cache invalidation" means that the fast switching cache was invalidated due to a routing table change. "New version" is the version number of the routing table. When the routing table changes, this number is incremented. The hexadecimal numbers are internal numbers that vary from version to version and software load to software load.

RT: add 198.93.168.0 255.255.255.0 via 198.92.76.30, igrp metric [100/3020]
RT: metric change to 198.93.168.0 via 198.92.76.30, igrp metric [100/3020]
        new metric [100/2930]
IP: cache invalidation from 0x115248 0x1378A, new version 5736

In the following output, the "holddown" and "cache invalidation" lines are displayed. Most of the distance vector routing protocols use "holddown" to avoid typical problems like counting to infinity and routing loops. If you look at the output of show ip protocols you will see what the timer values are for "holddown" and "cache invalidation". "Cache invalidation" corresponds to "came out of holddown". "Delete route" is triggered when a better path comes along. It gets rid of the old inferior path.

RT: delete route to 198.133.219.0 via 198.92.76.30, igrp metric [100/10816]
RT: no routes to 198.133.219.0, entering holddown
IP: cache invalidation from 0x115248 0x1378A, new version 5737
RT: 198.133.219.0 came out of holddown

debug ip sd

Use the debug ip sd command to display all session directory (SD) announcements received. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command shows session directory announcements for multicast IP. Use it to observe multicast activity.

Sample Display

Figure 2-81 shows sample debug ip sd output.

router# debug ip sd
SD: Announcement from 171.69.58.81 on Serial0.1, 146 bytes
    s=*cisco: CBONE Audio
    i=cisco internal-only audio conference
    o=dino@dino-ss20.cisco.com
    c=224.0.255.1 16 2891478496 2892688096
    m=audio 31372 1700
SD: Announcement from 204.62.246.68 on Serial0.1, 147 bytes
    s=IMS: U.S. Senate
    i=U.S. Senate at http://town.hall.org/radio/live.html
    o=carl@also.radio.com
    c=224.2.252.231 95 0 0
    m=audio 36572 2642
    a=fmt:gsm

Table 2-44 provides explanations for representative lines of the debug ip sd output shown in Figure 2-81.

Related Commands

debug ip dvmrp
debug ip igmp
debug ip mcache
debug ip mrouting
debug ip pim

debug ip security

Use the debug ip security EXEC command to display IP security option processing. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The debug ip security command displays information for both basic and extended IP security options. For interfaces where ip security is configured, each IP packet processed for that interface results in debugging output regardless of whether the packet contains IP security options. IP packets processed for other interfaces that also contain IP security information also trigger debugging output. Some additional IP security debugging information is also controlled by the debug ip packet EXEC command.

Sample Display

Figure 2-82 shows sample debug ip security output.

router# debug ip security
IP Security: src 198.92.72.52 dst 198.92.72.53, number of BSO 1
     idb: NULL
     pak: insert (0xFF) 0x0
IP Security: BSO postroute: SECINSERT changed to secret (0x5A) 0x10
IP Security: src 198.92.72.53 dst 198.92.72.52, number of BSO 1
     idb: secret (0x6) 0x10 to secret (0x6) 0x10, no implicit
          def secret (0x6) 0x10
     pak: secret (0x5A) 0x10
IP Security: checking BSO 0x10 against [0x10 0x10]
IP Security: classified BSO as secret (0x5A) 0x10

Table 2-45 describes significant fields shown in Figure 2-82.

Explanations for representative lines of output in Figure 2-82 follow.

The following line indicates that the packet was locally generated, and it has been classified with the internally significant security level "insert" (0xff) and authority 0x0:

idb: NULL
pak: insert (0xff) 0x0

The following line indicates that the packet was received via an interface with dedicated IP security configured. Specifically, the interface is configured at security level "secret" and with authority information of 0x0. The packet itself was classified at level "secret" (0x5a) and authority 0x10.

idb: secret (0x6) 0x10 to secret (0x6) 0x10, no implicit
     def secret (0x6) 0x10
pak: secret (0x5A) 0x10

debug ip tcp driver

Use the debug ip tcp driver EXEC command to display information on Transmission Control Protocol (TCP) driver events; for example, connections opening or closing, or packets being dropped because of full queues. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

The TCP driver is the process that the router software uses to send packet data over a TCP connection. Remote source-route bridging, STUN (serial tunneling), and X.25 switching currently use the TCP driver.

Using the debug ip tcp driver command together with the debug ip tcp driver-pak command provides the most verbose debugging output concerning TCP driver activity.

Sample Display

Figure 2-83 shows sample debug ip tcp driver output.

router# debug ip tcp driver
TCPDRV359CD8: Active open 160.89.80.26:0 --> 160.89.80.25:1996 OK, lport 36628
TCPDRV359CD8: enable tcp timeouts
TCPDRV359CD8: 160.89.80.26:36628 --> 160.89.80.25:1996 Abort
TCPDRV359CD8: 160.89.80.26:36628 --> 160.89.80.25:1996 DoClose tcp abort

Explanations for individual lines of output from Figure 2-83 follow.

Table 2-46 describes the fields in the first line of output.

TCPDRV359CD8: enable tcp timeouts

TCPDRV359CD8: 160.89.80.26:36628 --> 160.89.80.25:1996 Abort

TCPDRV359CD8: 160.89.80.26:36628 --> 160.89.80.25:1996 DoClose tcp abort

debug ip tcp driver-pak

Use the debug ip tcp driver-pak EXEC command to display information on every operation that the Transmission Control Protocol (TCP) driver performs. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command turns on a verbose debugging by logging at least one debugging message for every packet sent or received on the TCP driver connection.

The TCP driver is the process that the router software uses to send packet data over a TCP connection. Remote source-route bridging, STUN (serial tunneling), and X.25 switching currently use the TCP driver.

To observe the context within which certain debug ip tcp driver-pak messages occur, turn on this command in conjunction with the debug ip tcp driver command.

Sample Display

Figure 2-84 shows sample debug ip tcp driver-pak output.

router# debug ip tcp driver-pak
TCPDRV359CD8: send 2E8CD8 (len 26) queued
TCPDRV359CD8: output pak 2E8CD8 (len 26) (26)
TCPDRV359CD8: readf 42 bytes (Thresh 16)
TCPDRV359CD8: readf 26 bytes (Thresh 16)
TCPDRV359CD8: readf 10 bytes (Thresh 10)
TCPDRV359CD8: send 327E40 (len 4502) queued
TCPDRV359CD8: output pak 327E40 (len 4502) (4502)

Explanations for individual lines of output from Figure 2-84 follow.

Table 2-47 describes the fields shown in the first line of output.

TCPDRV359CD8: output pak 2E8CD8 (len 26) (26)

TCPDRV359CD8: readf 42 bytes (Thresh 16)

debug ip tcp transactions

Use the debug ip tcp transactions EXEC command to display information on significant Transmission Control Protocol (TCP) transactions such as state changes, retransmissions, and duplicate packets. The no form of this command disables debugging output.

Syntax Description

This command has no arguments or keywords.

Command Mode

EXEC

Usage Guidelines

This command is particularly useful for debugging a performance problem on a TCP/IP network that you have isolated above the data link layer.

The debug ip tcp transactions command displays output for packets the router sends and receives, but does not display output for packets it forwards.

Sample Display

Figure 2-85 shows sample debug ip tcp transactions output.

router# debug ip tcp transactions
TCP: sending SYN, seq 168108, ack 88655553
TCP0: Connection to 26.9.0.13:22530, advertising MSS 966
TCP0: state was LISTEN -> SYNRCVD [23 -> 26.9.0.13(22530)]
TCP0: state was SYNSENT -> SYNRCVD [23 -> 26.9.0.13(22530)]
TCP0: Connection to 26.9.0.13:22530, received MSS 956
TCP0: restart retransmission in 5996
TCP0: state was SYNRCVD -> ESTAB [23 -> 26.9.0.13(22530)]
TCP2: restart retransmission in 10689
TCP2: restart retransmission in 10641
TCP2: restart retransmission in 10633
TCP2: restart retransmission in 13384 -> 26.0.0.13(16151)]
TCP0: restart retransmission in 5996 [23 -> 26.0.0.13(16151)]

Table 2-48 describes significant fields shown in Figure 2-85.