K

kernel

Routes added through means other than by using the CLI; for example by using the operating system route command.

Static routes added using kernel commands and static routes added using OcNOS commands are different. The kernel static routes are not redistributed when you give the redistribute static command in a protocol. However, the kernel static routes can be redistributed using the redistribute kernel command.

C

connected

Routes directly connected to the local device that were not distributed via IGP. The device inherently knows of these networks, so there is no need to learn about these from another device.

Connected routes are preferred over routes for the same network learned from other routing protocols.

Routes for connected networks always exist in the kernel routing table but as an exception are not marked as kernel routes because OcNOS always calculates entries for these routes upon learning interface information from the kernel.

S

static

Routes manually configured via CLI which are not updated dynamically by IGPs.

The codes below are for routes received and dynamically learned via IGP neighbors. These networks are not directly connected to this device and were announced by some other device on the network. IGPs update these routes as the network topology changes.

R

RIP

RIP routing process and enter Router mode.

B

BGP

Route is from an Border Gateway Protocol.

O

OSPF

Modifiers for OSPF:

IA - OSPF inter area

N1 - OSPF NSSA external type 1

N2 - OSPF NSSA external type 2

E1 - OSPF external type 1

E2 - OSPF external type 2

i

IS-IS

Modifiers for IS-IS:

L1 - IS-IS level-1

L2 - IS-IS level-2

ia - IS-IS inter area

Other modifiers:

v

vrf leaked

The device has two or more VRFs configured and each has at least one interface bound to it. While each VRF will have its own routing table, the VRFs can learn each other’s routes.

*

candidate default

Route has been added to the FIB. With equal cost paths to a destination, the router does per-packet or per-destination load sharing. An asterisk ("*") means that the route is being used at that instant for forwarding packets. If you run the same show ip route x.x.x.x command over and over, you might see the * moving between the route entries.

>

selected route

When multiple routes are available for the same prefix, the best route.

When multiple entries are available for the same prefix, OcNOS uses an internal route selection mechanism based on protocol administrative distance and metric values to choose the best route. OcNOS populates the FIB with the best route to each destination

p

stale info

A route information that is marked stale due to graceful restart.

Codes and modifiers

As explained in Table 21-66.

IP address

IP address of the remote network.

Administrative distance and metric

The administrative distance determines how trustworthy this route is. If there is a similar route but with a smaller administrative distance, it is used instead, because it is more “trustworthy”. The smaller the administrative distance, the more trustworthy the route. Directly connected routes have an administrative distance of 0, which makes them the most trustworthy type of route.The metric varies from protocol to protocol, and for OSPF the metric is cost, which indicates the best quality path to use to forward packets. Other protocols, like RIP, use hop count as a metric. For neighboring routers, the metric value is 1.

Next hop router IP address

This route is available through the next hop router located at this IP address. This identifies exactly where packets go when they match this route.

Outgoing interface name

Interface used to get to the next-hop address for this route.

Duration

Length of time that this route has been present in the routing table. This is also the length of time this route has existed without an update. If the route were removed and then re-added (if the cable was disconnected, for instance), this timer would begin again at 00:00:00.