Solution to Configuration Exercise 1-1: Basic Connectivity
This section provides the answers to the questions in the Configuration Exercise.
NOTE
Some answers provided cover multiple steps; the answers are given after the last step for which that answer applies.
Solution to Task: Setting Up the Edge Routers
|
Step 1 |
Connect to each of your pod routers; they should not have configurations on them. If a router does have a configuration, delete the configuration using the erase start command, and then use the reload command to reboot. |
|
|
In this exercise, you will apply some minimal addressing and routing information so that your routers can reach the TFTP server. |
|
Step 2 |
Connect to each of your pod edge routers (PxR1 and PxR2). Configure the serial s0 interface of these routers for Frame Relay by turning on Frame Relay encapsulation. |
|
Step 3 |
Assign an IP address to your serial 0 interface. Your IP address is 172.31.x.y/24, where x is your pod number and y is your router number. |
|
Step 4 |
Inverse ARP has been turned off in the core Frame Relay network. Manually map a DLCI to BBR1 (172.31.x.3). The DLCI number will be in the form 1xy, where x is your pod number and y is your router number. For instance, P2R1 will use DLCI 121. |
|
|
Remember to specify the broadcast keyword so that the Frame Relay mapping supports broadcasts and multicasts, such as routing protocol traffic. |
|
Step 5 |
Use the no shutdown command on the interface and exit configuration mode. |
Solution:
The following shows how to perform the required steps on the P1R1 router:
|
Step 6 |
Verify successful connectivity from your PxR1 and PxR2 router to the core BBR1 router (172.31.x.3) using the ping command. |
Solution:
The following shows the ping from the P1R1 router:
|
Step 7 |
The goal of this exercise is to download a file from the TFTP server (at 10.254.0.254), which is connected to BBR1. Look at your PxR1 and PxR2 routing tables. Is there a route to the network that the TFTP server is located on? Why not? |
Solution:
The following shows the routing table on P1R1. There is no route to the 10.254.0.0 network. P1R1 only has a route to its connected S0 interface; it does not have any other interfaces configured, and it has not learned any other routes from other routers.
|
Step 8 |
Add a static route to 10.0.0.0/8 on your edge routers, through BBR1 (172.31.x.3), to provide a path to the TFTP server. Verify that the edge routers can see this route. |
Solution:
The following configuration and output are on the P1R1 router. P1R1 now has a route to the 10.0.0.0 network.
|
Step 9 |
Verify successful connectivity to the TFTP server (10.254.0.254) from your PxR1 and PxR2 router using the ping command. |
Solution:
The following ping is from the P1R1 router; the ping is successful:
The following ping is from the P1R2 router; the ping is successful:
|
Step 10 |
Retrieve the configuration file for your router from the TFTP server. The file should be named PxRy.txt. (For example, Pod 1 Router 2 will download P1R2.txt.) |
|
Filenames are not case-sensitive. |
|
|
The configuration files include the no ip classless command to force your router to behave classfully (although this command is on by default in IOS 12.0 and later). These files also include all required IP addresses and enable all required interfaces. Remember that files copied to running-config are merged, so this configuration complements what is already in your running-config. |
Solution:
The following output is from the P1R1 router. The download was successful.
|
|
The initial configuration files for the routers are provided in Appendix H. |
|
Step 11 |
Save your configuration before proceeding. |
Solution:
The following output is from the P1R1 router. The configuration was saved successfully.
Exercise Verification
You have successfully completed this exercise if you can ping the core BBR1 router and the TFTP server from your edge routers (PxR1 and PxR2) and you have downloaded the configuration files for your edge routers from the TFTP server.