Setting Up Your Routers and Loading the Configuration Files

There are two steps that you must complete before you can begin each lab:

Router Platforms and Cabling

All the labs were tested on Cisco 2611 routers loaded with Cisco IOS Software Release 12.2(16a) Enterprise Plus IPSec 56.

To do these labs, you will need five routers with a mix of ISDN Basic Rate Interface (BRI), Fast Ethernet and serial interfaces (see lab diagrams), as well as an IOS image that supports VPDNs for L2F and L2TPv2, MPLS (and, optionally, MPLS traceroute), and IPSec.

The quickest way to find an IOS image that supports these features is to use the Cisco Feature Navigator at the following URL (CCO account required):

http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp

Note that a 2600 minimum platform is required for MPLS.

For the L2F and L2TPv2 troubleshooting labs, you will also need a two-port ISDN simulator.

Follow the lab diagrams when cabling the your routers. Use back-to-back serial or cross-over Ethernet connections between routers, as appropriate.

Loading Configuration Files onto Your Lab Routers

If your lab routers have interface configurations different from those specified in the configuration files on the book's Web site, you will need to modify the interface numbering (and one or two other commands) before loading them on your routers. Again, check the lab diagrams, and compare the interface numbering carefully with your own routers.

Once you have cabled your routers, the next step is to navigate to the directory that contains configuration files for the lab that you are doing. This should be pretty easyfor example, the configuration files for L2TPv2 Troubleshooting Lab 1 are contained in the L2TPv2/Lab1 directory, and the configuration files for IPSec Troubleshooting Lab 2 are contained in the IPSec/Lab2 directory.

Now that you have found the correct directory, you can begin loading the configuration files onto your lab routers.

To load the configuration files on your routers, follow these instructions:

For example, in L2F Troubleshooting Lab 1, router DELAND_RTR has two serial interfaces numbered serial 0/0 and serial 1/0 (see lab diagram). If you are using a 2501 router for DELAND_RTR, however, you will need to modify the interface numbering in the DELAND_RTR.txt configuration file, as shown in Figure B-1.

As you can see, the numbering for the serial interfaces has been modified so that it conforms to 2501 router interface numbering (serial 0 and serial 1, as opposed to serial 0/0 and serial 0/1).

Before doing L2F and L2TPv2 Troubleshooting Labs 1, 2, and 3, you may also need to modify the isdn switch-type and dialer string commands on routers TATEBAYASHI@mjlnet.com and joebloggs@mjlnet.com. You might also need to add ISDN SPIDs using the isdn spid1 spid-number ldn [ldn] [ldn] and isdn spid2 spid-number ldn [ldn] [ldn] commands if required by your ISDN simulator. Note that you may also need to modify the isdn switch-type command on LODI_NAS1 and CalCity_LAC.

The ISDN switch type specified on TATEBAYASHI@mjlnet.com and joebloggs@mjlnetcom using the isdn switch-type command is basic-net 3 (on the BRI). Modify this if appropriate. Again, you may also have to add ISDN SPIDs, if required by your ISDN simulator.

The dialer string command on interface Dialer1 on TATEBAYASHI@mjlnet.com and joebloggs@mjlnet.com in the configuration files specifies 2222 as the number to dial for LODI_NAS1 and CalCity_LAC (in the L2F and L2TPv2 labs, respectively). Make sure you modify this number as appropriate.

Figure B-2 illustrates these modifications.

In Figure B-2, the ISDN switch type on interface BRI0/0 has been modified to be basic-ni (National), and the dialer string command on interface Dialer1 now specifies 1234 as the number to dial for LODI_NAS1.

The ISDN switch type specified on LODI_NAS1 and CalCity_LAC in the configuration files is also basic-net3 (on interface BRI0/0). Be sure to modify this if appropriate.

If you are in a hurry to get started, however, just modify the interface numbering as appropriate. You can make modification of ISDN switch types, dialer strings, and so on part of the lab exercises themselves.

Once you have made any necessary modifications to the configuration files, select all and copy and paste them to the Router(config)# prompt on your lab routers. This is shown in Figures B-3 and B-4.

Figure B-3. Select All

[View full size image]

When you have loaded all the configuration files on your lab routers, you are ready to start.

As a final thought: the purpose of the troubleshooting labs is to improve your VPN troubleshooting skills, and help you develop your understanding of relevant show and debug commands. So, try to use the VPN show and debug commands as you do the labs, and try to avoid using the show running-config command as much as possible.

Note that the console, Telnet, and enable password on all routers in all labs is mjlnet.

Figure B-4. Copy and Paste the Configuration Files to Your Lab Routers

[View full size image]