IP Routing

Static Routing

Our Canadian friend has always wanted to see the New York Public Library. She gets directions at the information booth: “Make a right on 42nd Street; walk three blocks; look for the lions in front of the library.” The information-booth attendant may have no idea that the library is closed that day, or that the sidewalk on 42nd Street is blocked just then because of fire trucks and 41st Street may be the preferable route. The information booth has given the same directions to the library for the last hundred years and hopefully will for hundreds more -- the route from Grand Central Station to the library, in other words, is static.

In a similar vein, a network administrator can create a static route. So, to reach network 146.1.0.0, we may add the command:

ip route 146.1.0.0 255.255.0.0 1.1.1.2

which says to get to network 146.1.0.0/16, go to the next hop of 1.1.1.2. This specifies a fixed path to 146.1.0.0/16, as shown here, where the contents of the routing table are displayed using the EXEC command show ip route:

  R#sh ip route
  ...

1 S    146.1.0.0/16 [1/0] via 1.1.1.2

Even if 1.1.1.2 goes down, an alternate path -- shown via R2 in Figure 1-3 -- cannot be used until a second static route is specified:

ip route 146.1.0.0 255.255.0.0 1.1.1.3

Figure 1-3. Router R’s connectivity to 146.1.0.0

The syntax of the static route command is:

ip route network [mask] {address | interface} ...