QUESTION:
> What is the default precedence: local-route, static-route,
OSPF-route?
> Based on ipForwardProto (2/1/13)
> Need a reference (RFC?)

CLARIFICATION:

ipForwardProto is an SNMP MIB. Let's not pay very much attention to the
results of SNMP values and stick with the selection of routes from your
question.
The revisied question that I will answer is, "What is the selection process
for routing?"

The most specific routing entries are selected first, no matter the source
of the routing information. If more then one entry for the exact same route
is available, the one with the lowest administrative distance value is
selected. If more than one entry for the exact same route is available with
the same administrative distance, the one with the better metric is
selected.
1) Most specific route entry, no matter the method which is is learned
2) Lowest administrative distance of the method which the route is learned
(routing protocol)
3) Best metric of the available routes within that method (routing
protocol)

The exception to this is when the administrative distance is changed.
Static routes normally have an administrative distance of 1. This makes them
less preferable than routing information from the interface configuraiton
but more preferable than routing information from dynamic routing protocols
like EIGRP and OSPF. This administrative distance of a static route can be
changed.
This is a normal static route which will have an administrative distance of
1:
ip route 10.0.0.0 255.255.255.0 192.168.1.1
This is a modified static route which will have an administrative distance
of 220:
ip route 10.0.0.0 255.255.255.0 192.168.1.1 220
These are sometimes referred to as "floating static routes" because other
routing methods are more likely to be used.

The IP address 10.1.1.1 matches all four of the routing table entries
equally with no one entry being more specific than the other. Therefore
administrative distance is used and the static route with an administrative
distance of 1 is used. No other routing table entries have the same
administrative distance so the routing metric is not a factor.

The IP address 10.1.1.1 does match all four of the routing table entries but
the routing table entry 10.1.1.0/24 is more exact than the other entries
using 10.1.0.0/16. Administrative distance is not considered because this
one route matched more accurately. Metric is not considered because this
one route matched more accurately.

EXAMPLE #3:

A router with interfaces Serial0/0, Serial0/1, and FastEthernet0/0 is
running EIGRP and OSPF while also having some static routes.
The results of "show ip route" contain these entries:
D 10.1.0.0/16 [90/180000] via 192.168.1.1, 2w3d, Serial0/0
O 10.1.0.0/16 [110/65] via 192.168.2.1, 2w3d, Serial0/1
S 10.1.0.0/16 [100/0] via 192.168.1.1
Where will traffic to 10.1.1.1 normally be routed?
If the EIGRP learned route is lost, where will traffic to 10.1.1.1 be
routed?

If traffic is being routed to 10.1.1.1, it will go to 192.168.1.1.
If the EIGRP learned route is lost, traffic to 10.1.1.1 will go to
192.168.1.1.

The IP address 10.1.1.1 matches all three of the routing table entries
equally including the two entries which would remain after the EIGRP routing
table entry is lost. The administrative distance of EIGRP, 90, would be the
first choice but the modified administrative distance of the static route,
100, makes a second choice before considering routes from OSPF with an
administrative distance of 110. No other routing table entries have the
same administrative distance so the routing metric is not a factor.
The EIGRP route to 192.168.1.1 is used first.
The static route to 192.168.1.1 is used second.
The OSPF route to 192.168.2.1 is used third.

The IP address 10.0.1.1 matches three of the four routing table entries.
The routing table entry for 10.0.0.0/16 is the most exact of the three and
is the best match. Therefore administrative distance is used and the static
route with an administrative distance of 1 is used. Administrative distance
is not considered because one route matched with the most accuracy. Metric
is not considered because this one route matched with the most accuracy.

REFERENCE:

There is not an RFC for this route selection process because this is
specific to Cisco devices. Other router manufacturers will very likely not
have IGRP and EIGRP so the administrative distance table cannot apply to
them.
The methods by which dynamic routing protocols determine their own internal
metrics are available in RFCs for each specific routing protocol.

Share This Page

Welcome to Velocity Reviews!

Welcome to the Velocity Reviews, the place to come for the latest tech news and reviews.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to chat with other enthusiasts and get tech help from other members.
Sign up now!