Objectives
The simulator ticks each one as soon as the network meets it.
On R1, add a static route to 192.168.2.0/24 through R2 (next hop 10.0.12.2).
On R1, add a floating backup route to the same network through R3 (10.0.13.3) with preference 100.
On R2, add the return routes to 192.168.1.0/24: through R1 (10.0.12.1), and a floating one through R3 (10.0.23.3) with preference 100.
PC1 pings PC2 over the direct link; display ip routing-table protocol static on R1 lists the backup route as inactive.
Shut down R1 G0/0/1 (the direct link): the floating routes take over and PC1 still reaches PC2, now through R3.
Rate this lab
No ratings yet.
Sign in to rate this lab and keep track of the labs you finish.
Before you start
ip route-static [preference ]. Lower preference wins; a route whose next hop is unreachable leaves the table, so the one waiting behind it is installed. Both directions need a backup, or the replies get lost.
Concept
Floating static routes
Two static routes can lead to the same network. The one with the lower preference is installed; the other “floats” behind it and is installed only when the first one’s next hop becomes unreachable.
Concept
Static routes and the routing table
A static route is an entry you type yourself: “to reach this network, send to this next hop”. Routers know only their directly connected subnets until you add routes or run a routing protocol.