E-Lab 6.1.6 - Static Routes
Configure static routes between routers to allow data transfer between routers without the use of dynamic routing protocols.
Step 1
Ping from Workstation_a to Workstation_b (172.18.0.2).
Step 2
Since the ping failed we want to try to find a solution.
Start by checking the router Lome.
Enter privileged EXEC mode.
Step 3
Check interface status.
Step 4
Switch to the Porto_Novo Router before doing the following step.
The output showed no problem with Lome's interfaces.
Next check the interfaces for Porto_Novo.
Enter privileged EXEC mode.
Step 5
Check interface status.
Step 6
Porto_Novo also has no interface related problems.
Now Check the routing table entries.
Step 7
Notice that the routing table for Porto_Novo has no route to the network 172.16.0.0. Since the router has no rule that specifies an output interface for packets bound for 172.16.0.0, such packets are dropped.
This explains why the ping failed.
One way to fix this is to add a static route.
Enter into global configuration mode.
Step 8
Add a static route that tells Porto_Novo that it needs to send packets destined for 172.16.0.0/16 to a next hop address of 172.17.0.1 (the neighbour router).
Step 9
Switch back to the Lome Router before doing the following step.
Configure a static route on the Lome router, except send packets destined for 172.18.0.0/16 to the next hop at 172.17.0.2.
Step 10
Use the command end to return to privileged EXEC mode.
Step 11
Now view the routing table to see the changes.
The entry tagged by an S is the static route entry.
Step 12
Try a ping now that both routers have a route to each other's ethernet networks.
Ping Workstation_b at 172.18.0.2.