Troubleshooting static route configuration

Troubleshooting static route configuration 

6.1.6

This page will show students how to troubleshoot a static route configuration.
On an earlier page, students configured static routes on Hoboken to access networks on Sterling and Waycross. In this configuration, nodes on the Sterling 172.16.1.0 network cannot reach nodes on the Waycross 172.16.5.0 network.
From privileged EXEC mode on the Sterling router, ping to a node on the 172.16.5.0 network. The ping fails. Now use the traceroute command from Sterling to the address that was used in the ping statement. Note where the traceroute fails. The traceroute indicates that the ICMP packet was returned from Hoboken but not from Waycross. This implies that the trouble exists either on Hoboken or Waycross.
Telnet to the Hoboken router. Try again to ping the node on the 172.16.5.0 network connected to the Waycross router. This ping should succeed because Hoboken is directly connected to Waycross.
The Lab Activities on this page will teach students how to configure static routes for data transfer without dynamic routing protocols.
This page concludes this lesson. The next lesson will explain dynamic routing. The first page provides an overview of routing protocols.