Static-route-lab

Three Router Static Route Lab

Objective

In this lab, you will configure static routes between all three routers. This will allow your routers to route packets so that all routers and all hosts will be able to reach (ping) each other. Once your configuration is complete, you will use basic techniques to test your network’s connectivity.

Scenario

Three separate classful networks need routing between them and their subnets. This will firstly be done using static routes, then by summarizing some of the networks and then using default routes.

Inintial Questions:

What are the different classful networks?
1. ________________2. ________________
3. ________________
4. ________________
5. ________________
Are there any subnets? If so, what are they?
1. _______________
2. _______________
3. _______________
4. _______________
5. _______________

Setup

Add 3 x 2811 routers to Packet Tracer workspace. You will need to add serial interfaces to each router.
Add a 2950-24 switch to each router's Fa0/0 interface. No other configuration of the switch is needed.
Configure the cabling as shown in the network diagram.
Serial links should run at 1Mbps. Use the Router(config-if)#clock rate 1000000 command on the DCE end of the serial link to achieve this.
Add one host PC to each switch. Give that PC the LOWEST available IP address (the next available after the Fa0/0 interface).
If the routers have a startup-config, erase it and perform a reload of the routers. This is only necessary if you are using hardware - not needed in Packet Tracer!
Important! Configure the routers to include hostnames and the proper interface commands including IP addresses, subnet masks, etc.
Each router should be able to ping the interface of the adjacent (neighboring) router and the host on its LAN (FastEthernet) interface. Test and troubleshoot as necessary.
Use the context sensitive help, previous labs, your books and /or handouts and if you are still having problems ask your partner or ask the instructor for assistance.

Remember to save your Packet Tracer file regularly - this application can become unstable and crash.

Step 1 – Configuring Static Routes

On each router configure a separate and specific static route for each network or subnet. You do not need to configure static routes for the router’s directly connected network(s) because like a host, by configuring the IP address and subnet mask on an interface tells the router that it belongs to that network/subnet.

Router1

Router1(config)# ip route 172.16.3.0 255.255.255.0 172.16.2.1
Router1(config)# ip route 192.168.2.0 255.255.255.0 192.168.1.1

Router2

Router2(config)# ip route 172.16.1.0 255.255.255.0 172.16.2.2
Router2(config)# ip route 192.168.1.0 255.255.255.0 172.16.2.2
Router2(config)# ip route 192.168.2.0 255.255.255.0 172.16.2.2

Router3

Router3(config)# ip route 172.16.1.0 255.255.255.0 192.168.1.2
Router3(config)# ip route 172.16.2.0 255.255.255.0 192.168.1.2
Router3(config)# ip route 172.16.3.0 255.255.255.0 192.168.1.2

Verify and Validate:

All hosts and all routers should be able to ping every interface in the network.
Do a “show running-config” and notice the static routes that you entered.
Router# show ip route
What routes to networks are displayed?
Which routes are static and which routes are directly connected? How can you tell the difference between Static routes and Directly connected networks?
What is the administrative distance for a static route?
What is the administrative distance for a directly connected network?

Questions:

How does the next-hop-ip-address help with the routing process?_____________________________________________.

Does it give the entire route, i.e., subnet mask?_____________________________________________________

What is it actually doing regarding the routing of the packet?____________________________________________
How does a packet get from Host 2 to Host 3?
____________________________________________
____________________________________________
____________________________________________
Instead of a next-hop-ip-address, what else could you have used?
____________________________________________.
What would you need to do if you added new networks or deleted/modified existing networks to ensure routing to the new networks was possible from all points in the existing network?
____________________________________________
____________________________________________
____________________________________________
Is there any way to summarize several static routes to multiple subnets (destinations) into a single static route?
_____________________________________________
_____________________________________________
_____________________________________________

Outputs

Router2#show ip route
(Output omitted)
Gateway of last resort is not set

     172.16.0.0/24 is subnetted, 3 subnets
S       172.16.1.0 [1/0] via 172.16.2.2
C       172.16.2.0 is directly connected, Serial0/0/0
C       172.16.3.0 is directly connected, FastEthernet0/0
S    192.168.1.0/24 [1/0] via 172.16.2.2
S    192.168.2.0/24 [1/0] via 172.16.2.2

Router1#show ip route
(output omitted)
Gateway of last resort is not set

172.16.0.0/24 is subnetted, 3 subnets
C       172.16.1.0 is directly connected, FastEthernet0/0
C       172.16.2.0 is directly connected, Serial0/0/0
S       172.16.3.0 [1/0] via 172.16.2.1
C    192.168.1.0/24 is directly connected, Serial0/0/1
S    192.168.2.0/24 [1/0] via 192.168.1.1

Router3#show ip route
(Output omitted)
Gateway of last resort is not set

172.16.0.0/24 is subnetted, 3 subnets
S       172.16.1.0 [1/0] via 192.168.1.2
S       172.16.2.0 [1/0] via 192.168.1.2
S       172.16.3.0 [1/0] via 192.168.1.2
C    192.168.1.0/24 is directly connected, Serial0/0/1
C    192.168.2.0/24 is directly connected, FastEthernet0/0

Step 2 – Configuring Summary Static Routes

The configuration of the routers in Step 1 works well and is a valid way to configure routing on these networks.

Earlier, you should have noticed that the network 172.16.0.0 is divided into several subnets.

Router3 does not really need separate static routes for each subnet, since all of the 172.16.0.0 subnets can be reached via the same next-hop-ip-address, i.e. Router1.

Now we can reconfigure the static routes on Router3 so that it only uses a single static route to reach all of the 172.16.0.0 subnets.

Router1

No changes

Router2

No changes

Router3

First, remove the current static routes:
Router3(config)# no ip route 172.16.1.0 255.255.255.0 192.168.1.2
Router3(config)# no ip route 172.16.2.0 255.255.255.0 192.168.1.2
Router3(config)# no ip route 172.16.3.0 255.255.255.0 192.168.1.2
Now, add the new summary static route:
Router3(config)# ip route 172.16.0.0 255.255.0.0 192.168.1.2

Verify and Validate:

All hosts and all routers should be able to ping every interface in the network.
Do a “show running-config” and notice the static routes that you entered.
Router3# show ip route
What routes to networks do you now see? What difference do you notice in the subnet mask(s) for the new static route?

Questions:

What made this new summary static route work for all subnets?
_____________________________________________________
_____________________________________________________
_____________________________________________________
Why is a single summary static route an advantage regarding the size of the routing table?
_____________________________________________________
_____________________________________________________
_____________________________________________________
Why is a single summary static route an advantage regarding future changes to the 172.16.0.0 network?
_____________________________________________________
_____________________________________________________
_____________________________________________________

Outputs

Router3#show ip route
(Output omitted)

Gateway of last resort is not set
S    172.16.0.0/16 [1/0] via 192.168.1.2
C    192.168.1.0/24 is directly connected, Serial0/0/1
C    192.168.2.0/24 is directly connected, FastEthernet0/0

Step 3 – Configuring Default Static Routes

Both Step 1 and Step 2 are acceptable ways to configure routing for these networks. We notice that the 172.16.3.0/24 and the 192.168.2.0/24 networks are “stub networks,” meaning that there is only one way out (both via Router1).

Router1

No changes

Router2

First, remove the current static routes:
Router2(config)# no ip route 172.16.1.0 255.255.255.0 172.16.2.2
Router2(config)# no ip route 192.168.1.0 255.255.255.0 172.16.2.2
Router2(config)# no ip route 192.168.2.0 255.255.255.0 172.16.2.2
Now, add the new default static route:
Router2(config)# ip route 0.0.0.0 0.0.0.0 172.16.2.2

Router3

First, remove the current static routes:
Router3(config)# no ip route 172.16.0.0 255.255.0.0 192.168.1.2
Now, add the new default static route:
Router3(config)# ip route 0.0.0.0 0.0.0.0 192.168.1.2

Verify and Validate:

All hosts and all routers should be able to ping every interface in the network.
Do a “show running-config” and notice the static routes that you entered.
Router2# show ip route
What routes to networks do you now see?
Router3# show ip route
What routes to which networks do you now see?

Questions:

Do you think static routes are still used even with dynamic routing (RIP, OSPF, etc.)?
_______________. Hint: Think about the administrative distance.

Do you think default static routes are still used even with dynamic routing (RIP, OSPF, etc.)?
_______________.

What is the disadvantage of doing this? How would a default static route be properly used in a real world network? (How would a company’s network use a default route when connecting to the Internet?)
________________________________________
________________________________________
________________________________________

Outputs

Router2#show ip route
(Output omitted)

Gateway of last resort is 172.16.2.2 to network 0.0.0.0

     172.16.0.0/24 is subnetted, 2 subnets
C       172.16.2.0 is directly connected, Serial0/0/0
C       172.16.3.0 is directly connected, FastEthernet0/0
S*   0.0.0.0/0 [1/0] via 172.16.2.2

Router3#show ip route
(Output omitted)

Gateway of last resort is 192.168.1.2 to network 0.0.0.0

C    192.168.1.0/24 is directly connected, Serial0/0/1
C    192.168.2.0/24 is directly connected, FastEthernet0/0
S*   0.0.0.0/0 [1/0] via 192.168.1.2

Save your current configuration to NVRAM.

Tidying your Network

When you have finished, you should add passwords to your routers. The options are to add a non-encrypted password (insecure) or an encrypted password to the router to keep unwanted personnel from entering privileged exec mode.

The syntax to make the enable password class is:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#enable secret class
Router(config)#end

Do this for all routers in your network.

Add a message of the day - this can be a statement of your company policy regarding unauthorised access to digital resources perhaps.

Router2(config)#banner motd "Authorised Acess Only"

If you save your changes and logout of the router, the Message of the day will appear before you login again.

All interfaces can be given descriptions. This helps when you are making changes to a router's configuration and are not familiar with the network's layout.

Router2#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router2(config)#int fa0/0
Router2(config-if)#description Second floor LAN
Router2(config-if)#end

Add descriptions that are meaningful to all interfaces in your network.

Save your work and the answers to all questions. you will need to refer back to this work later in the course.

Lab idea courtesy of http://www.ciscokits.com/cisco-static-route-lab/
Customisation to Packet Tracer 5.x by MMClements 2009