
Configuring IP
IP Forwarding
OmniSwitch AOS Release 7 Network Configuration Guide
June 2013
page 15-11
Creating a Static Route or Recursive Static Route
Static routes are user-defined and carry a higher priority than routes created by dynamic routing
protocols. That is, if two routes have the same metric value, the static route has the higher priority. Static
routes allow you to define, or customize, an explicit path to an IP network segment, which is then added to
the IP Forwarding table. Static routes can be created between VLANs to enable devices on these VLANs
to communicate.
Use the
command to create a static route. Specify the destination IP address of the route as
well as the IP address of the first hop (gateway) used to reach the destination. For example, to create a
static route to IP address 171.11.0.0 through gateway 171.11.2.1, you would enter:
-> ip static-route 171.11.0.0 gateway 171.11.2.1
If you want to use the natural subnet mask, the subnet mask is not required. By default, the switch imposes
a natural mask on the IP address. In the above example, the Class B mask of 255.255.0.0 is implied. If you
do not want to use the natural mask, enter a subnet mask. For example, to create a static route to IP
address 10.255.11.0, enter the Class C mask of 255.255.255.0:
-> ip static-route 10.255.11.0 mask 255.255.255.0 gateway 171.11.2.1
Specifying the length of the mask in bits is also supported. For example, the above static route is also
configurable using the following command:
-> ip static-route 10.255.11.0/24 gateway 171.11.2.1
When you create a static route, the default metric value of 1 is used. However, you can change the
priority of the route by increasing its metric value. The lower the metric value, the higher the priority. This
metric is added to the metric cost of the route. The metric range is 1 to 15. For example:
-> ip static-route 10.255.11.0/24 gateway 171.11.2.1 metric 5
Static routes do not age out of the IP Forwarding table; delete them from the table. Use the
no ip static
route
command to delete a static route. Specify the destination IP address of the route as well as the IP
address of the first hop (gateway). For example, to delete a static route to IP address 171.11.0.0 through
gateway 171.11.2.1, you would enter:
-> no ip static-route 171.11.0.0 gateway 171.11.2.1
The IP Forwarding table includes routes learned through one of the routing protocols (RIP, OSPF, BGP)
as well as any static routes that are configured. Use the
show ip routes
command to display the IP
Forwarding table.
Creating a Recursive Static Route
Recursive static routes are similar to the static routes described above. However, with a recursive static
route the route to reach the gateway is learned through a dynamic routing protocol such as RIP or OSPF. If
a better route to the gateway is learned, the path to a recursive route can be changed dynamically. This
feature can be used to configure a uniformed static route for all routers on a network, but the path to reach
the gateway can differ for each router. To create a recursive static route use the
follows
parameter:
-> ip static-route 171.11.0.0 follows 192.168.10.1
A route to the
192.168.10.1
address must be learned by a dynamic routing protocol for the recursive static
route to be active.