Chapter 2: L2F Troubleshooting Lab Solutions
This section provides solutions for L2F Troubleshooting Labs 1, 2, and 3. Note that the directory L2F/LabSolution directory contains working configuration files for all routers for your reference.
Troubleshooting Lab 1 Solution
| A1: | In Troubleshooting Lab 1, the domain is incorrectly specified under the VPDN group (vpdn-group 1). It should be mjlnet.com and not mjl.com. Make sure that you remove the mjl.com domain (no domain mjl.com), before adding the mjlnet.com domain (domain mjlnet.com). For more details on troubleshooting this issue, see the section entitled “Partial PPP Authentication Fails on the NAS” on page 64. |
Troubleshooting Lab 2 Solution
| 1: | The IP address of the PERRIS_HGW1 is incorrectly specified on LODI_NAS1 (initiate-to ip 172.16.2.3) under the VPDN-group (vpdn-group 1). It should be 172.16.2.2.
Ensure that you remove the incorrect IP address (no initiate-to ip 172.16.2.3) before adding the correct IP address (initiate-to ip 172.16.2.2). More details on troubleshooting this issue can be found in the section entitled “Troubleshooting L2F Tunnel Establishment” on page 69. Additionally, one of the tunnel passwords is mismatched between LODI_NAS1 and PERRIS_HGW1 (username username password password). See the section entitled “Tunnel Authentication Failure” on page 74 for more information on troubleshooting this issue. |
Troubleshooting Lab 3 Solution
| A1: | The vpdn softshut command is configured on PERRIS_HGW1. This should be removed to allow new L2F sessions to be established (no vpdn softshut). See the section entitled “Troubleshooting L2F Session Establishment” on page 80 for more details on troubleshooting this issue.
Also, there is no IP address configured on interface Virtual-Template1 on PERRIS_HGW1. Configure an IP address on this interface (ip unnumbered interface_name) to resolve this issue. The section entitled “NCP Negotiation Failure” on page 91 has more information on this issue. |