Table of Contents
Advertisement
NAS Name
Gateway Name
test-mmp
test-gateway
192.168.1.99
192.168.1.119
L2F MIDs = 10
Name
rw56
rw55
rw54
rw57
rw57
rw54
rw55
rw16
rw16
rw56
Tips
If you are having trouble:
•
Troubleshoot the VPDN protocol by using its debug commands to view information for the
errors, events, and packets and check the Gateway name, network access server (NAS) name, and
if the virtual access interface is up.
— Enter debug vpdn ? command to view a list of debug vpdn commands:
5300# debug vpdn ?
error
event
l2f-errors
l2f-events
l2f-packets
packet
— Enter debug commands to view error information. When you finish viewing the messages,
enter no debug vpdn command to turn off the debug messages:
This is sample output for the debug vpdn event command:
5300# debug vpdn event
VPN events debugging is on
*May 15 17:55:49.367: %LINK-3-UPDOWN: Interface Virtual-Access239,
changed state to down
*May 15 17:55:49.547: Virtual-Access249 VPN reset
*May 15 17:55:49.547: %LINK-3-UPDOWN: Interface Virtual-Access249,
changed state to down
This is sample output for the debug vpdn l2f-events command:
5300# debug vpdn l2f-events
L2F protocol events debugging is on
*May 15 17:56:46.259: L2F_OPEN received
*May 15 17:56:46.263: L2F Got a MID management packet
*May 15 17:56:46.339: %LINK-3-UPDOWN: Interface Virtual-Access239,
changed state to up
This is sample output for the debug vpdn l2f-errors command:
5300# debug vpdn l2f-errors
L2F protocol errors debugging is on
*May 15 17:57:57.827: %LINK-3-UPDOWN: Interface Virtual-Access251,
changed state to down
NAS CLID
272
NAS Name
test-mmp
test-mmp
test-mmp
test-mmp
test-mmp
test-mmp
test-mmp
test-mmp
test-mmp
test-mmp
VPDN Protocol errors
VPDN event
L2F protocol errors
L2F protocol events
L2F protocol packets
VPDN packet
Gateway CLID
State
272
open
Interface
MID
Vi238
1
Vi240
3
Vi242
4
Vi246
7
Vi248
8
Vi245
13
Vi244
14
Vi249
97
Vi251
98
Vi250
100
Verify
State
open
open
open
open
open
open
open
open
open
open
Basic Configuration 3-59
Advertisement
Table of Contents
