Table Of Contents
debug v120 event
Use the debug v120 event EXEC command to display information on V.120 activity. The no form of this command disables debugging output.
[no] debug v120 event
Usage Guidelines
V.120 is an ITU specification that allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels.
For complete information on the V.120 process, use the debug v120 packet command along with the debug v120 event command. V.120 events are activity events rather than error conditions.
Sample Display
Figure 2-266 shows sample debug v120 event output of V.120 starting up and stopping. Also included is the interface that V.120 is running on (BR 0) and where the V.120 configuration parameters are obtained from (default).
Figure 2-266 Sample Debug V.120 Event Output
Router# debug v120 event0:01:47: BR0:1-v120 started - Setting default V.120 parameters0:02:00: BR0:1:removing v120Related Command
debug v120 packet
Use the debug v120 packet EXEC command to display general information on all incoming and outgoing V.120 packets. The no form of this command disables debugging output.
[no] debug v120 packet
Usage Guidelines
The debug v120 packet command shows every packet on the V.120 session. You can use this information to determine whether incompatibilities exist between Cisco's V.120 implementation and other vendors' V.120 implementations.
V.120 is an ITU specification that allows for reliable transport of synchronous, asynchronous, or bit transparent data over ISDN bearer channels.
For complete information on the V.120 process, use the debug v120 events command along with the debug v120 packet command.
Sample Display
Figure 2-267 shows sample debug v120 packet output for a typical session startup.
Figure 2-267 Sample Debug V.120 Packet Output
Router# debug v120 packet0:03:27: BR0:1: I SABME:lli 256 C/R 0 P/F=10:03:27: BR0:1: O UA:lli 256 C/R 1 P/F=10:03:27: BR0:1: O IFRAME:lli 256 C/R 0 N(R)=0 N(S)=0 P/F=0 len 430x83 0xD 0xA 0xD 0xA 0x55 0x73 0x650x72 0x20 0x41 0x63 0x63 0x65 0x73 0x730:03:27: BR0:1: I RR:lli 256 C/R 1 N(R)=1 P/F=00:03:28: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=0 P/F=0 len 20x83 0x630:03:28: BR0:1: O RR:lli 256 C/R 1 N(R)=1 P/F=00:03:29: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=1 P/F=0 len 20x83 0x310:03:29: BR0:1: O RR:lli 256 C/R 1 N(R)=2 P/F=0%LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0: B-Channel 1, changed state to up0:03:31: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=2 P/F=0 len 20x83 0x550:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=3 P/F=0 len 30x83 0x31 0x6F0:03:32: BR0:1: O RR:lli 256 C/R 1 N(R)=3 P/F=00:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=4 P/F=0 len 20x83 0x730:03:32: BR0:1: O RR:lli 256 C/R 1 N(R)=5 P/F=00:03:32: BR0:1: I IFRAME:lli 256 C/R 0 N(R)=1 N(S)=5 P/F=0 len 20x83 0xA0:03:32: BR0:1: O IFRAME:lli 256 C/R 0 N(R)=6 N(S)=1 P/F=0 len 90x83 0xD 0xA 0x68 0x65 0x66 0x65 0x72 0x3Edescribes the fields shown in the display.
Related Command
debug vg-anylan
To monitor error information and 100VG connection activity, use the debug vg-anylan EXEC command. The no form of this command disables debugging output.
[no] debug vg-anylan
Usage Guidelines
This command could create large amounts of command output.
Sample Display
shows sample output from the debug vg-anylan command.
Figure 2-268 Sample Debug VG-AnyLAN Output
Router# debug vg-anylan%HP100VG-5-LOSTCARR: HP100VG(2/0), lost carrierlists the possible messages that could be generated by this command.
Table 2-139 Debug VG-AnyLAN Message Descriptions
%HP100VG-5-LOSTCARR: HP100VG(2/0), lost carrier
Lost carrier debug message. The VG controller detects that the link to the hub is down due to cable, hub, or VG controller problem.
Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.
%HP100VG-5-CABLEERR: HP100VG(2/0), cable error, training failed
Bad cable error messages. Cable did not pass training.1
Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.
%HP100VG-5-NOCABLE: HP100VG(2/0), no tone detected, check cable, hub
No cable attached error message. The VG MAC cannot hear tones from the hub.1
Check, repair, or replace the cable or hub. If you determine that the cable and hub are functioning normally, repair or replace the 100VG-AnyLAN port adapter.
HP100VG-1-FAIL: HP100VG(2/0), Training Fail - unable to login to the hub
Training to the VG network failed. Login to the hub rejected by the hub.1
Take action based on the following error messages:
•
%HP100VG-1-DUPMAC: HP100VG(2/0), A duplicate MAC address has been detected
•
•
%HP100VG-1-DUPMAC: HP100VG(2/0), A duplicate MAC address has been detected
Duplicate MAC address on the same VG network. Two VG devices on the same LAN segment have the same MAC address.
Check the router configuration to make sure that no duplicate MAC address is configured.
%HP100VG-1-LANCNF: HP100VG(2/0), Configuration is not compatible with the network
Configuration of the router is not compatible to the network.
Check that the configuration of the hub for Frame Format, Promiscuous, and Repeater bit indicates the proper configuration.
%HP100VG-1-ACCESS: HP100VG(2/0), Access to network is not allowed
Access to the VG network is denied by the hub.
Check the configuration of the hub.
%HP100VG-3-NOTHP100VG: Device reported 0x5101A
Could not find the 100VG PCI device on a 100VG-AnyLAN port adapter.
Make sure the 100VG-AnyLAN port adapter is properly seated in the slot. Otherwise repair or replace the 100VG-AnyLAN port adapter.
%HP100VG-1-DISCOVER: Only found 0 interfaces on bay 2, shutting down bay
No 100VG interface detected on a 100VG-AnyLAN port adapter in a slot.
Make sure the 100VG-AnyLAN port adapter is properly seated in the slot. Otherwise repair or replace the 100VG-AnyLAN port adapter.
1 This message might display when the total load on the cascaded hub is high. Wait at least 20 seconds before checking to see if the training really failed. Check if the protocol is up after 20 seconds before starting troubleshooting.
debug vines arp
Use the debug vines arp EXEC command to display debugging information on all Virtual Integrated Network Service (VINES) Address Resolution Protocol (ARP) packets that the router sends or receives. The no form of this command disables debugging output.
[no] debug vines arp
Sample Display
shows sample debug vines arp output.
Figure 2-269 Sample Debug VINES ARP Output
Router# debug vines arpVNSARP: received ARP type 0 from 0260.8c43.a7e4VNSARP: sending ARP type 1 to 0260.8c43.a7e4VNSARP: received ARP type 2 from 0260.8c43.a7e4VNSARP: sending ARP type 3 to 0260.8c43.a7e4 assigning address 3001153C:8004VSARP: received ARP type 0 from 0260.8342.1501VSARP: sending ARP type 1 to 0260.8342.1501VSARP: received ARP type 2 from 0260.8342.1501VSARP: sending ARP type 3 to 0260.8342.1501 assigning address 3001153C:8005,sequence 143C, metric 2In , the first four lines show a non-sequenced ARP transaction and the second four lines show a sequenced ARP transaction. Within the first group of four lines, the first line shows that the router received an ARP request (type 0) from indicated station address 0260.8c43.a7e4. The second line shows that the router is sending back the ARP service response (type 1), indicating that it is willing to assign VINES Internet addresses. The third line shows that the router received a VINES Internet address assignment request (type 2) from address 0260.8c43.a7e4. The fourth line shows that the router is responding (type 3) to the address assignment request from the client and assigning it the address 3001153C:8004.
Within the second group of four lines, the sequenced ARP packet also includes the router' current sequence number and the metric value between the router and the client.
describes significant fields shown in .
debug vines echo
Use the debug vines echo EXEC command to display information on all MAC-level echo packets that the router sends or receives. Banyan VINES interface testing programs make use of these echo packets. The no form of this command disables debugging output.
[no] debug vines echo
Note
Sample Display
shows sample debug vines echo output.
Figure 2-270 Sample Debug VINES Echo Output
Router# debug vines echoVINESECHO: 100 byte packet from 0260.8c43.a7e4describes the fields shown in .
debug vines ipc
Use the debug vines ipc EXEC command to display information on all transactions that occur at the VINES IPC layer, which is one of the two VINES transport layers. The no form of this command disables debugging output.
[no] debug vines ipc
Usage Guidelines
You can use the debug vines ipc command to discover why an IPC layer process on the router is not communicating with another IPC layer process on another router or Banyan VINES server.
Sample Display
shows sample debug vines ipc output for three pairs of transactions. For more information about these fields or their values, refer to Banyan VINES documentation.
Figure 2-271 Sample Debug VINES IPC Output
Router# debug vines ipcVIPC: sending IPC Data to Townsaver port 7 from port 7r_cid 0, l_cid 1, seq 1, ack 0, length 12VIPC: received IPC Data from Townsaver port 7 to port 7r_cid 51, l_cid 1, seq 1, ack 1, length 32VIPC: sending IPC Ack to Townsaver port 0 from port 0r_cid 51, l_cid 1, seq 1, ack 1, length 0describes the fields shown in .
debug vines netrpc
Use the debug vines netrpc EXEC command to display information on all transactions that occur at the VINES NetRPC layer, which is the VINES Session/Presentation layer. The no form of this command disables debugging output.
[no] debug vines netrpc
Usage Guidelines
You can use the debug vines netrpc command to discover why a NetRPC layer process on the router is not communicating with another NetRPC layer process on another router or Banyan server.
Sample Display
shows sample debug vines netrpc output. For more information about these fields or their values, refer to Banyan VINES documentation.
Figure 2-272 Sample Debug VINES NetRPC Output
Router# debug vines netrpcVRPC: sending RPC call to TownsaverVRPC: received RPC return from Townsaverdescribes the fields shown in the first line of output in .
debug vines packet
Use the debug vines packet EXEC command to display general VINES debugging information. This information includes packets received, generated, and forwarded, as well as failed access checks and other operations. The no form of this command disables debugging output.
[no] debug vines packet
Sample Display
shows sample debug vines packet output.
Figure 2-273 Sample Debug VINES Packet Output
Router# debug vines packetVINES: s=30028CF9:1 (Ether2), d=FFFFFFFF:FFFF, rcvd w/ hops 0VINES: s=3000CBD4:1 (Ether1), d=3002ABEA:1 (Ether2), g=3002ABEA:1, sentVINES: s=3000CBD4:1 (Ether1), d=3000B959:1, rcvd by gwVINES: s=3000B959:1 (local), d=3000CBD4:1 (Ether1), g=3000CBD4:1, sentdescribes the fields shown in the first line of output.
Explanations for other lines in follow.
In the following line, the destination is the address 3002ABEA:1 associated with interface Ether2. Source address 3000CBD4:1 sent a packet to this destination through the gateway at address 3000ABEA:1.
VINES: s=3000CBD4:1 (Ether1), d=3002ABEA:1 (Ethernet2), g=3002ABEA:1, sentIn the following line, the router being debugged is the destination address (3000B959:1):
VINES: s=3000CBD4:1 (Ether1), d=3000B959:1, rcvd by gwIn the following line, (local) indicates that the router being debugged generated the packet:
VINES: s=3000B959:1 (local), d=3000CBD4:1 (Ether1), g=3000CBD4:1, sentdebug vines routing
Use the debug vines routing EXEC command to display information on all VINES RTP update messages sent or received and all routing table activities that occur in the router. The no form of this command disables debugging output.
[no] debug vines routing [verbose]
Syntax Description
Sample Displays
shows sample debug vines routing output.
Figure 2-274 Sample Debug VINES Routing Output
shows sample debug vines routing verbose output.
Figure 2-275 Sample Debug VINES Routing Verbose Output
Router# debug vines routing verboseVRTP: sending update to Broadcast on Ethernet0network 30011E7E, metric 0020 (0.4000 seconds)network 30015800, metric 0010 (0.2000 seconds)network 3003148A, metric 0020 (0.4000 seconds)VSRTP: generating change update, sequence number 0002C795network Router9 metric 0010, seq 00000000, flags 09network RouterZZ metric 0230, seq 00052194, flags 02VSRTP: sent update to Broadcast on Hssi0VSRTP: received update from LabRouter on Hssi0update: type 00, flags 07, id 000E, ofst 0000, seq 15DFC, met 0010network LabRouter from the servernetwork Router9 metric 0020, seq 00000000, flags 09VSRTP: LabRouter-Hs0-HDLC up -> up, change update, onemoredescribes two VINES routing updates; the first includes two entries and the second includes three entries. Explanations for selected lines of follow.
The following line shows that the router sent a periodic routing update to the broadcast address FFFFFFFF:FFFF through the Ethernet0 interface:
VRTP: sending update to Broadcast on Ethernet0The following line indicates that the router knows how to reach network 30011E7E, which is a metric of 0020 away from the router. The value that follows the metric (0.4000 seconds) interprets the metric in seconds.
network 30011E7E, metric 0020 (0.4000 seconds)The following lines show that the router sent a change routing update to the Broadcast addresses on the Hssi0 interface using the Sequenced Routing Update Protocol (SRTP) routing protocol:
VSRTP: generating change update, sequence number 0002C795VSRTP: Sending update to Broadcast on Hssi0The lines in between the previous two indicate that the router knows how to reach network Router9, which is a metric of 0010 (0.2000 seconds) away from the router. The sequence number for Router9 is zero, and according to the 0x08 bit in the flags field, is invalid. The 0x01 bit of the flags field indicates that Router9 is attached via a LAN interface.
network Router9 metric 0010, seq 00000000, flags 09The next lines indicate that the router can reach network RouterZZ, which is a metric of 0230 (7.0000 seconds) away from the router. The sequence number for RouterZZ is 0052194. The 0x02 bit of the flags field indicates that RouterZZ is attached via a WAN interface.
network RouterZZ metric 0230, seq 00052194, flags 02The following line indicates that the router received a routing update from the router LabRouter through the Hssi0 interface:
VSRTP: received update from LabRouter on Hssi0The following line displays all SRTP values contained in the header of the SRTP packet. This is a type 00 packet, which is a routing update, and the flags field is set to 07, indicating that this is a change update (0x04) and contains both the beginning (0x01) and end (0x02) of the update. This overall update is update number 000E from the router, and this fragment of the update contains the routes beginning at offset 0000 of the update. The sending router's sequence number is currently 00015DFC, and its configured metric for this interface is 0010.
update: type 00, flags 07, id 000E, ofst 0000, seq 00015DFC, met 0010The following line implies that the server sending this update is directly accessible to the router (even though VINES servers do not explicitly list themselves in routing updates). Because this is an implicit entry in the table, the other information for this entry is taken from the previous line.
network LabRouter from the serverAs the first actual entry in the routing update from LabRouter, the following line indicates that Router9 can be reached by sending to this server. This network is a metric of 0020 away from the sending server.
network Router9 metric 0020, seq 00000000, flags 09debug vines service
Use the debug vines service EXEC command to display information on all transactions that occur at the VINES Service (or applications) layer. The no form of this command disables debugging output.
[no] debug vines service
Usage Guidelines
You can use the debug vines service command to discover why a VINES Service layer process on the router is not communicating with another Service layer process on another router or Banyan server.
Note
Sample Display
shows sample debug vines service output.
Figure 2-276 Sample Debug VINES Service Output
As suggests, debug vines service lines of output appear as activity pairs—either a sent/response pair as shown, or as a received/sent pair.
describes the fields shown in the second line of output in . For more information about these fields or their values, refer to Banyan VINES documentation.
describes the fields shown in the third line of output in . This line is an extension of the first two lines of output. For more information about these fields or their values, refer to Banyan VINES documentation.
debug vines state
Use the debug vines state EXEC command to display information on the VINES SRTP state machine transactions. The no form of this command disables debugging output.
[no] debug vines state
Usage Guidelines
This command provides a subset of the information provided by the debug vines routing command, showing only the transactions made by the SRTP state machine. Refer to the debug vines routing command for descriptions of output from the debug vines state command.
debug vines table
Use the debug vines table EXEC command to display information on all modifications to the VINES routing table. The no form of this command disables debugging output.
[no] debug vines table
Usage Guidelines
This command provides a subset of the information produced by the debug vines routing command, as well as some more detailed information on table additions and deletions.
Sample Display
shows sample debug vines table output.
Figure 2-277 Sample Debug VINES Table Output
Router# debug vines tableVINESRTP: create neighbor 3001153C:8004, interface Ethernet0describes significant fields shown in .
debug vlan packet
Use the debug vlan packet EXEC command to display general information on virtual LAN (VLAN) packets that the router received but is not configured to support. The no form of this command disables debugging output.
[no] debug vlan packet
Usage Guidelines
The debug vlan packet command displays only packets with a VLAN identifier that the router is not configured to support. This command allows you to identify other VLAN traffic on the network. Virtual LAN packets that the router is configured to route or switch are counted and indicated when you use the show vlans command.
Sample Display
Figure 2-278 shows sample debug vlan packet output. In this example, a VLAN packet with a VLAN ID of 1000 was received on FDDI 0 interface and this interface was not configured to route or switch this VLAN packet.
Figure 2-278 Sample Debug VLAN Packet Output
Router# debug vlan packetvLAN: IEEE 802.10 packet bearing vLAN ID 1000 received on interfaceFddi0 which is not configured to route/switch ID 1000.debug vpdn
To display debug traces for the Virtual Private Dialup Network (VPDN) feature, which provides PPP tunnels using the Layer 2 Forwarding (L2F) protocol, use the debug vpdn EXEC command. The no form of this command disables debugging output.
[no] debug vpdn {errors | events | packets | l2f-errors | l2f-events | l2f-packets}
Syntax Description
Debug VPDN Events on a Network Access Server—Normal Operations
The network access server has the following VPDN configuration:
vpdn outgoing cisco.com stella ip 172.21.9.26username stella password stellashows sample output of the debug vpdn events command on a network access server when the L2F tunnel is brought up and CHAP authentication of the tunnel succeeds.
Figure 2-279 Debug VPDN Events on the Network Access Server—Tunnel Coming Up
Router# debug vpdn events%LINK-3-UPDOWN: Interface Async6, changed state to up*Mar 2 00:26:05.537: looking for tunnel -- cisco.com --*Mar 2 00:26:05.545: Async6 VPN Forwarding...*Mar 2 00:26:05.545: Async6 VPN Bind interface direction=1*Mar 2 00:26:05.553: Async6 VPN vpn_forward_user bum6@cisco.com is forwarded%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up*Mar 2 00:26:06.289: L2F: Chap authentication succeeded for stella.shows sample output of the debug vpdn events command on a network access server when the L2F tunnel is brought down normally.
Figure 2-280 Debug VPDN Events on the Network Access Server—Tunnel Coming Down Normally
Router# debug vpdn events%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down%LINK-5-CHANGED: Interface Async6, changed state to reset*Mar 2 00:27:18.865: Async6 VPN cleanup*Mar 2 00:27:18.869: Async6 VPN reset*Mar 2 00:27:18.873: Async6 VPN Unbind interface%LINK-3-UPDOWN: Interface Async6, changed state to downdescribes the fields in and . The output describes normal operations when a tunnel is brought up or down on a network access server.
Debug VPDN Events on the Home Gateway—Normal Operations
The home gateway has the following VPDN configuration, which uses stella as the tunnel name and the tunnel authentication name. The tunnel authentication name might be entered in a users file on an AAA server and used to define authentication requirements for the tunnel.
vpdn incoming stella stella virtual-template 1shows sample output of the debug vpdn events command on the home gateway when the tunnel is brought up successfully.
Figure 2-281 Debug VPDN Events on the Home Gateway—Tunnel Coming Up
Router# debug vpdn eventsL2F: Chap authentication succeeded for stella.Virtual-Access3 VPN Virtual interface created for bum6@cisco.comVirtual-Access3 VPN Set to Async interfaceVirtual-Access3 VPN Clone from Vtemplate 1 block=1 filterPPP=0%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to upVirtual-Access3 VPN Bind interface direction=2Virtual-Access3 VPN PPP LCP accepted sent & rcv CONFACK%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to upshows sample output of the debug vpdn events command on a home gateway when the tunnel is brought down normally.
Figure 2-282 Debug VPDN Events on the Home Gateway—Tunnel Coming Down Normally
Router# debug vpdn events%LINK-3-UPDOWN: Interface Virtual-Access3, changed state to downVirtual-Access3 VPN cleanupVirtual-Access3 VPN resetVirtual-Access3 VPN Unbind interfaceVirtual-Access3 VPN reset%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access3, changed state to downdescribes the fields in and . The output describes normal operations when a tunnel is brought up or down on a network access server.
Debug VPDN L2F-Events on the Network Access Server—Normal Operations
shows sample output of the debug vpdn l2f-events command on the network access server when the L2F tunnel is brought up successfully.
Figure 2-283 Debug VPDN L2F-Events on the Network Access Server—Tunnel Coming Up
Router# debug vpdn l2f-events%LINK-3-UPDOWN: Interface Async6, changed state to up*Mar 2 00:41:17.365: L2F Open UDP socket to 172.21.9.26*Mar 2 00:41:17.385: L2F_CONF received*Mar 2 00:41:17.389: L2F Removing resend packet (type 1)*Mar 2 00:41:17.477: L2F_OPEN received*Mar 2 00:41:17.489: L2F Removing resend packet (type 2)*Mar 2 00:41:17.493: L2F building nas2gw_mid0%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to up*Mar 2 00:41:18.613: L2F_OPEN received*Mar 2 00:41:18.625: L2F Got a MID management packet*Mar 2 00:41:18.625: L2F Removing resend packet (type 2)*Mar 2 00:41:18.629: L2F MID synced NAS/HG Clid=7/15 Mid=1 on Async6shows sample output of the debug vpdn l2f-events command on a network access server when the tunnel is brought down normally.
Figure 2-284 Debug VPDN L2F-Events on the Network Access Server—Tunnel Coming Down
Router# debug vpdn l2f-events%LINEPROTO-5-UPDOWN: Line protocol on Interface Async6, changed state to down%LINK-5-CHANGED: Interface Async6, changed state to reset*Mar 2 00:42:29.213: L2F_CLOSE received*Mar 2 00:42:29.217: L2F Destroying mid*Mar 2 00:42:29.217: L2F Removing resend packet (type 3)*Mar 2 00:42:29.221: L2F Tunnel is going down!*Mar 2 00:42:29.221: L2F Initiating tunnel shutdown.*Mar 2 00:42:29.225: L2F_CLOSE received*Mar 2 00:42:29.229: L2F_CLOSE received*Mar 2 00:42:29.229: L2F Got closing for tunnel*Mar 2 00:42:29.233: L2F Removing resend packet*Mar 2 00:42:29.233: L2F Closed tunnel structure%LINK-3-UPDOWN: Interface Async6, changed state to down*Mar 2 00:42:31.793: L2F Closed tunnel structure*Mar 2 00:42:31.793: L2F Deleted inactive tunnel
Debug VPDN L2F-Events on the Home Gateway—Normal Operations
shows sample output of the debug vpdn l2f-events command on a home gateway when the L2F tunnel is created.
Figure 2-285 Debug VPDN L2F-Events on the Home Gateway—Tunnel is Created
Router# debug vpdn l2f-eventsL2F_CONF receivedL2F Creating new tunnel for stellaL2F Got a tunnel named stella, respondingL2F Open UDP socket to 172.21.9.25L2F_OPEN receivedL2F Removing resend packet (type 1)L2F_OPEN receivedL2F Got a MID management packet%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to upshows sample output of the debug vpdn l2f-events command on a home gateway when the L2F tunnel is brought down normally.
Figure 2-286 Debug VPDN L2F-Events on a Home Gateway—Tunnel Coming Down Normally
Router# debug vpdn l2f-eventsL2F_CLOSE receivedL2F Destroying midL2F Removing resend packet (type 3)L2F Tunnel is going down!L2F Initiating tunnel shutdown.%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to downL2F_CLOSE receivedL2F Got closing for tunnelL2F Removing resend packetL2F Removing resend packetL2F Closed tunnel structureL2F Closed tunnel structureL2F Deleted inactive tunnel%LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to down
Debug VPDN on the Network Access Server—Error Conditions
shows sample output of the debug vpdn errors command on a network access server when the tunnel is not set up.
Figure 2-287 Debug VPDN Errors on the Network Access Server—Error Conditions
Router# debug vpdn errors%LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to down%LINK-5-CHANGED: Interface Async1, changed state to reset%LINK-3-UPDOWN: Interface Async1, changed state to down%LINK-3-UPDOWN: Interface Async1, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Async1, changed state to upVPDN tunnel management packet failed to authenticateVPDN tunnel management packet failed to authenticate
shows sample output of the debug vpdn l2f-errors command.
Figure 2-288 Debug VPDN L2F-Errors on the Network Access Server—Error Conditions
Router# debug vpdn l2f-errors%LINK-3-UPDOWN: Interface Async1, changed state to upL2F Out of sequence packet 0 (expecting 0)L2F Tunnel authentication succeeded for home.comL2F Received a close request for a non-existent midL2F Out of sequence packet 0 (expecting 0)L2F packet has bogus1 key 1020868 D248BA0FL2F packet has bogus1 key 1020868 D248BA0F
Debugging VPDN Packets for Complete Information
shows sample output of the debug vpdn l2f-packets command on a network access server. This example displays a trace for a ping command.
Figure 2-289 Debug VPDN L2F-Packets on a Network Access Server
Router# debug vpdn l2f-packetsL2F SENDING (17): D0 1 1 10 0 0 0 4 0 11 0 0 81 94 E1 A0 4L2F header flags: 53249 version 53249 protocol 1 sequence 16 mid 0 cid 4length 17 offset 0 key 1701976070L2F RECEIVED (17): D0 1 1 10 0 0 0 4 0 11 0 0 65 72 18 6 5L2F SENDING (17): D0 1 1 11 0 0 0 4 0 11 0 0 81 94 E1 A0 4L2F header flags: 53249 version 53249 protocol 1 sequence 17 mid 0 cid 4length 17 offset 0 key 1701976070L2F RECEIVED (17): D0 1 1 11 0 0 0 4 0 11 0 0 65 72 18 6 5L2F header flags: 57345 version 57345 protocol 2 sequence 0 mid 1 cid 4length 32 offset 0 key 1701976070L2F-IN Otput to Async1 (16): FF 3 C0 21 9 F 0 C 0 1D 41 AD FF 11 46 87L2F-OUT (16): FF 3 C0 21 A F 0 C 0 1A C9 BD FF 11 46 87L2F header flags: 49153 version 49
