Information Technology Reference
In-Depth Information
Task 7: Save the Packet Tracer File
Save your Packet Tracer file as LSG02-0201-end.pka.
Configuring a Static Route with an Exit Interface
In the previous sections, you saw how a static route can be configured with a next-hop address. Using
a next-hop address is a correct method in configuring static routes. However, in some situations, using
an exit interface can result in a more efficient route lookup process.
Static Routes with an Exit Interface Exercise
Explain in detail the difference between the next-hop address argument and the exit interface argument.
The next-hop argument requires a recursive route lookup, that is, the router still does not know the
exit interface and will have to look up the next-hop IP address in the routing table to locate the exit
interface. If the exit interface argument is used, no recursive lookup is necessary, and the router can
immediately forward the packet to the outbound interface.
The network shown in Figure 2-1 already has static routes with next-hop addresses configured. Before
configuring static routes with exit interfaces, you will need to remove the next-hop versions.
How do you remove a static route from the configuration?
Use the
no
form of the
ip route
command.
List the Static Route Commands
Assume that all the next-hop static routes have been removed. For each router in Figure 2-1, record
the static route commands you would use to configure the static routes with an exit interface specified.
Static routes with an exit interface for HQ:
!Static routes to B1 LANs
ip route 192.168.20.0 255.255.255.0 Serial0/0/0
ip route 192.168.21.0 255.255.255.0 Serial0/0/0
ip route 192.168.22.0 255.255.255.0 Serial0/0/0
ip route 192.168.23.0 255.255.255.0 Serial0/0/0
!Static routes to B2 LANs
ip route 192.168.160.0 255.255.255.0 Serial0/0/1
ip route 192.168.161.0 255.255.255.0 Serial0/0/1
ip route 192.168.162.0 255.255.255.0 Serial0/0/1
ip route 192.168.163.0 255.255.255.0 Serial0/0/1
Static routes with an exit interface for B1:
!Static routes to HQ LANs
ip route 172.16.0.0 255.255.0.0 Serial0/0/0
ip route 172.17.0.0 255.255.0.0 Serial0/0/0
!Static routes to B2 LANs
ip route 192.168.160.0 255.255.255.0 Serial0/0/0
ip route 192.168.161.0 255.255.255.0 Serial0/0/0
ip route 192.168.162.0 255.255.255.0 Serial0/0/0
