CIS-3210, Lab #3: Static Routing

Reading: Read the section on static routing in Chapter 6 of Engineers' Handbook of Routing and Switching. The section is the first one in the chapter. Read Chapter 7 in the CCNA Routing and Switching Portable Command Guide on static routing.

In this lab, you will configure static routes that enable a router to send packets to networks that are not directly connected to it. You will also configure a switch virtual interface in the switches.

NOTE! Recall that in addition to submitting your Packet Tracer file for this lab, you should also submit a document that includes all the commands you used to configure your device(s), along with any comments or observations you made, and the answers to any questions asked.

Part 1: Configure The Network

Using Packet Tracer, construct the following network:

Lab #3 Network

Device Interface IP Address Subnet Mask Default Gateway
R1 Gig0/0 192.168.0.1 255.255.255.0 N/A
Gig0/1 10.1.1.1 ? N/A
R2 Gig0/0 192.168.1.1 255.255.255.0 N/A
Gig0/1 10.1.1.2 ? N/A
S1 VLAN1 192.168.0.10 255.255.255.0 192.168.0.1
S2 VLAN1 192.168.1.10 255.255.255.0 192.168.1.1
Addressing Table

Use 1941 routers and 2960-24TT switches (might be shown as just "2960" in Packet Tracer's menu of switches). Note that the switches have separate uplink ports that are higher speed. Those ports would be connected to upstream devices (e.g., routers) while the end systems would be connected to the slower, normal ports. Be sure to connect them in this way.

Notice that a crossover cable is used to connect to the two routers directly. That is the appropriate kind of cable to use in that case.

Configure the router basic settings as you did in Lab #1 (Global Settings and Console Access; you do not need to configure remote access for this lab). Configure the network interfaces using the addresses in the addressing table. Be sure to provide a description for the network interfaces as was done in the previous lab.

For the switches, you can also run through the same Global Settings and Console Access settings as for the routers. Switches don't "normally" have IP addresses since they operate at layer 2. However, it is possible to connect a switch virtual interface (SVI) to the same link that the switch is handling, and assign that SVI an IP address. This is done using virtual LANs (VLANs), which we will discuss at length later. See the section "A Note About Switches" at the bottom of the basic settings document.

Be sure your Packet Tracker model has appropriate names for the devices (as in the diagram above) and label the IP addresses as shown.

Check your work by logging onto S1's console and trying to ping R1. Similarly, log onto S2's console and try to ping R2.

From R1 are you able to ping the Gig0/0 interface of R2? Similarly, from R2 are you able to ping the Gig0/0 interface of R1? Explain. Hint: View the routing table on R1 using `show ip route` and see if there is an entry that explains what to do with the packets headed to Gig0/0 on R2.

Part 2: Configure Static Routes

  1. Configure a static route in R1 for the remote (relative to R1) network of 192.168.1.0/24 by specifying the next-hop address toward that network. Refer to the slides for the details.

  2. Configure a static route in R2 for the remote (relative to R2) network of 192.168.0.0/24 by specifying the exit interface to use for packets destined to that network. Refer to the slides for the details.

  3. From R1, once again try to ping the Gig0/0 interface of R2. This ping should now succeed. View the routing table on R1 to see the static route that is used for the echo request packet (sent by ping). View the routing table on R2 to see the static route that is used for the echo reply packet (sent in response to the echo request).

  4. From R1, try to ping the SVI in S2. Similarly, from R2, try to ping the SVI in S1. These pings should still be failing. Why?

  5. On S1, configure R1's interface on the same link as a default gateway. Similarly, on S2, configure R2's interface on the same link as a default gateway. Refer to the slides for the details.

  6. Verify that it is now possible to ping the SVI in S2 from R1, and similarly for the SVI in S1 from R2.

  7. Verify that it is now possible to ping the SVI in S2 from S1 and vice-versa.

Submission

For this lab, submit your final Packet Tracer model, along with a document containing the commands you used to configure your devices, and your answers to the questions. The preferred document format is PDF, but Word, ODT, or plain text is also acceptable.


Last Revised: 2023-09-05
© Copyright 2023 by Peter Chapin <peter.chapin@vermontstate.edu>