ip route

Defines a static route.

ip route <network_address> <network_mask> {<next_address> | <interface>}
 
no ip route <network_address> <network_mask> 
 
            [<next_address> | <interface>]
 

• network_address--IP address of the destination, in dotted decimal format (a.b.c.d)
• network_mask--network mask of the destination, in dotted decimal format (e.f.g.h.i
• next_address--IP address of the next hop to the destination
• interface--name of a specific interface to be used; can be either:
• ethernetN/0 (where N is slot number on which the interface is configured)
• tunnelN (where N is the GRE tunnel number on a USTAT module)

Must be in configuration, engine, ustat or interface configuration mode (config, config-engine, config-ustat, or config-if), which requires privileged-level access.

Available for use multiple times in the configuration.

Use the ip route command to create a static route between CNA and a destination.

If you use the command in config mode on a 5000 series device, the route will be applied to the management module.

If you use the command while in module configuration mode (config-engine or config-ustat), the route will be applied to the module being configured.

If you use the command while in interface configuration mode (config-if), the route will be applied to the interface.

NOTE: On a 3000 series device, you should always configure a static route on the interface assigned to the engine module if you have a globally defined route. This will avoid possible routing problems from a static route being shared between the management and engine modules. See Static Routes in Appendix D: Migrating Configurations Between Models of the CNA Appendices Guide.

When interfaces or tunnels are created, you specify them as ethernet N/N or tunnel N with a space between the name and number portion of the value; when using them as values for the interface argument, they are specified as ethernetN/N or tunnelN--a single string with no spaces.

While CNA will allow you to define multiple static routes to a single destination, the device does not perform any round-robin, destination-based load optimization. It will use the first reachable default route in the list. If the next hop in that route subsequently goes down, CNA will lose connectivity to remote networks that rely on that route.

If you then bring the failed next-hop interface back up, CNA will then exercise correct fail-over behavior and move to the next route on the list.

Use the no form of the command to remove a static route. If neither next_address nor interface are specified, all matching static routes defined for the specified network_address and network_mask will be removed.