Configuring static routes

Configuring static routes 

6.1.3

This page lists the steps used to configure static routes and gives an example of a simple network for which static routes might be configured.
Use the following steps to configure static routes:
Step 1 Determine all desired prefixes, masks, and addresses. The address can be either a local interface or a next hop address that leads to the desired destination.
Step 2 Enter global configuration mode.
Step 3 Type the ip route command with a prefix and mask followed by the corresponding address from Step 1. The administrative distance is optional.
Step 4 Repeat Step 3 for all the destination networks that were defined in Step 1.
Step 5 Exit global configuration mode.
Step 6 Use the copy running-config startup-config command to save the active configuration to NVRAM.
The example network is a simple three-router configuration. Hoboken must be configured so that it can reach the 172.16.1.0 network and the 172.16.5.0 network. Both of these networks have a subnet mask of 255.255.255.0.
Packets that have a destination network of 172.16.1.0 need to be routed to Sterling and packets that have a destination address of 172.16.5.0 need to be routed to Waycross. Static routes can be configured to accomplish this task.
Both static routes will first be configured to use a local interface as the gateway to the destination networks. Since the administrative distance was not specified, it will default to 1 when the route is installed in the routing table.
The same two static routes can also be configured with a next-hop address as their gateway. The first route to the 172.16.1.0 network has a gateway of 172.16.2.1. The second route to the 172.16.5.0 network has a gateway of 172.16.4.2. Since the administrative distance was not specified, it defaults to 1.
The Lab Activity will help students learn how to configure static routes.
The next page will explain how default routes are configured.