Traffic Forwarding IP Static Routes (S-, K-Series)

Traffic forwarding IP static routes are configured by specifying the destination IPv4 prefix and mask or prefix/length for the route and one of the following:

• The next hop router IP address, optionally specifying the next hop interface ID or that the next hop interface is determined by route lookup
• The next hop interface name
• The next hop VLAN ID
• The egress VRF router as the next hop (IPv4 routes only)
• Packets destined for this route‘s subnet are silently dropped
• Packets destined for this route‘s subnet are dropped, and an ICMP network unreachable message is sent to the packet source

An administrative distance can be optionally configured that is used for route selection preference. The lower the numeric distance value, the greater the preference for the route. An OSPF tag-ID can be specified.

Routes are managed by the RTM (Route Table Manager) and are contained in the RIB (Route Information Base). The RIB contains up to 8 equal cost routes from any route source to each network and installs these routes in the FIB (Forwarding Information Base). The routes in the FIB are distributed to every module for use by the routerʹs ingress module as frames are received.

A probe can be configured on a static route. When configuring a probe for the static route using the probe option, the probe session is created on the nexthop address. When the probe session goes down, the static route is disabled. When the probe session comes up, the static route is enabled.

Traffic forwarding IP static routes are configured using the ip route command for IPv4 routes or the ipv6 route command for IPv6 routes, in global configuration mode.