Configuring Static Routes
If the packet is to be routed, the router will do a route table lookup to acquire the
correct route. At a minimum, each route entry in the database must contain two
items:
A destination address. This is the address of the network the router can reach.
As this chapter explains, the router may have more than one route to the same
address and/or a group of subnets of the same or of varying lengths grouped
under the same major IP network address.
A pointer to the destination. This pointer either will indicate that the destination
network is directly connected to the router or it will indicate the address of another
router on a directly connected network. That router, which will be one router hop
closer to the destination, is a nexthop router.
The router will match the most specific address it can. In descending order of
specificity, the address may be one of the following:
• A host address (a host route)
• A subnet
• A group of subnets (a summary route)
• A major network number
• A group of major network numbers (a supernet)
• A default address
Figure 3.1. The minimum information needed for each route table entry
consists of the destination networks and the pointers to those networks.
Case Study: Simple Static Routes
The steps for creating simple static route configuration
The procedure for statically routing an inter-network has three steps:
1. For each data link within the inter-network, identify all addresses (subnet or
network).
2. For each router, identify all data links not directly connected to that router.
3. For each router, write a route statement for each data link not directly
connected to it.
For example, the inter-network in Figure 3.3 has six subnets:
[Link]/16
[Link]/24
[Link]/24
[Link]/27
[Link]/27
[Link]/27
To configure static routes for Piglet, the subnets that are not directly connected are
identified as follows:
[Link]/24
[Link]/24
[Link]/27
[Link]/27
These are the subnets for which static routes must be written. The commands for
entering Piglet's static
routes are as follows:
Piglet(config)# ip route [Link] [Link] [Link]
Piglet(config)# ip route [Link] [Link] [Link]
Piglet(config)# ip route [Link] [Link] [Link]
Piglet(config)# ip route [Link] [Link] [Link]
Following the same steps, the route entries for the other three routers are:
Pooh(config)# ip route [Link] [Link] [Link]
Pooh(config)# ip route [Link] [Link] [Link]
Pooh(config)# ip route [Link] [Link] [Link]
Pooh(config)# ip route [Link] [Link] [Link]
Tigger(config)# ip route [Link] [Link] [Link]
Tigger(config)# ip route [Link] [Link] [Link]
Tigger(config)# ip route [Link] [Link] [Link]
Eeyore(config)# ip route [Link] [Link] [Link]
Eeyore(config)# ip route [Link] [Link] [Link]
Eeyore(config)# ip route [Link] [Link] [Link]
Eeyore(config)# ip route [Link] [Link] [Link]
The routing commands themselves are easily read if the reader remembers that
each command describes a route table entry. The command is ip route, followed
by the address to be entered into the table, a mask for determining the network
portion of the address, and the address of the directly connected interface of the
next-hop router.
An alternative configuration command for static routes specifies the interface out
of which a network is reached instead of the address of the next-hop router. For
example, the route entries for Tigger could be as follows:
Tigger(config)# ip route [Link] [Link] S0
Tigger(config)# ip route [Link] [Link] E0
Tigger(config)# ip route [Link] [Link] S1
Case Study: Recursive Table Lookups
All route entries do not necessarily need to point to the next-hop router.
To reach network [Link], Pooh must perform three route table lookups.
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
Figure 3.12. Configuring Sanderz for recursive lookups enables the network
administrator to redirect all of that router's exit traffic from Heffalump to
Woozle by changing one route entry.
Figure 3.12 shows an example of an instance in which recursive lookups may be
useful. Here, Sanderz reaches all networks via Heffalump. However, the network
administrator plans to eliminate Heffalump and repoint all of Sanderz's routes
through Woozle. The first 12 entries point not to Heffalump, but to the appropriate
router attached to the [Link] subnet. The last entry specifies that the
[Link] subnet is reached via Heffalump.
With this configuration, all of Sanderz's entries can be re-pointed through Woozle
simply by changing the last static entry:
Sanderz(config)# ip route [Link] [Link] [Link]
Sanderz(config)# no ip route [Link] [Link] [Link]
RTA
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
RTB
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
RTC
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
ip route [Link] [Link] [Link]
Users are complaining of several connectivity problems in this internet. Find the
mistakes in the static route configurations.