Home / Network / Routing / Static routing / Static routing… metric?!

Static routing… metric?!

In this post we explore the operation of static routing, epecially the use of the metric feature, in a network that already runs an IGP (RIP routing protocol).

network setup

In our 3 routers RIP network, both R1 and R3 advertise 13.13.13.13/32 network into RIP domain

R3 is configured to offset (to add) all network updates via interface fa1/0 by 10

check the operation of rip network

A debug ip rip command shows the output in the next figure:

R2 receives R3 route with a metric of 11 hops.

A debug ip rip events shows that only R1 route succeeds its entrance into R2 RIP database

In rip database only the best route is preserved

A debug ip routing on R2 shows that R3 route is not accepted by the routing table and returns code:19

As soon as we shutdown the lo13 interface on R1 the route gets poisoned and R3 route added. We bring up the lo13 interface on R1 and see that R3 route is removed because R2 receives now a better route metric from R1

In the R2 routing table the best protocol candidate route in terms of protocol metric (in our case hops) is added

The protocol metric is just copied to the structure of the default routing table entry describing this route

This entry includes a new attribute that was not in the protocol table or database (rip database): distance (of 120 in case of RIP) which indicates the source of the route information

redundant static routing with same AD

We configure static routing to the same destination and use a distance (AD administrative distance) of 120 (the same as RIP)

Now the static route is installed in the routing table with 120 as AD and a metric of 0

Not because of the administrative distance but rather the metric which is 0 for static routes (instead for rip route with metric 1 hops away).

Static routing provides a local routing information source to the router. It is different from dynamic routing because no routing information is exchanged between routers. Knowing that, why should I configure a metric for static routes?

Let’s add another static route to the same destination but that points to the opposite direction

Both routes are installed because they have the same cost (metric).

In static routing metric and administrative distance are both local and there’s no case that may apply only to the metric in choosing the best route to put in the routing table. In other words if static routes are orginated from the same router why a route should be more expensive than the other?

Using the metric in static routing is redundant not to say useless.

But the administrative distance is still needed to discriminate the routing information source. Additionally, we could use different administrative distances per routes… giving the administrator the ability to distinguish them

as a conclusion

in this post we’ve explored a simple routing case operation to understand metric use in adding routing information to router default routing table. In static routing, the use of metric can not have the same meaning as for dynamic routing. But the administrative distance do so giving the administrator the ability to locally classify routing information to put in the routing table.

Tagged:

Leave a Reply

802.11 (4) application (2) architecture (4) asm (4) automatisation (2) cagd (3) chd (2) cisco (6) command (5) controller (1) cost (6) coverage (5) debug (10) distance (6) dtls (2) dynamic rrm (5) firewall (2) fortinet (2) ieee (4) igmp (5) igp (8) interference (2) internet (3) ip (2) logique (2) loop (5) mac (3) machine learning (3) meraki (1) model (2) mpls (3) mroute (4) multicast (5) nat (2) ndp (2) network (3) next-hop (5) nurbs (3) osi (6) pat (2) pim (4) poisoning (6) projet (2) qos (2) radio (5) rib (5) rip (5) route (6) router (6) routing (15) rpf (4) rrm (10) security (3) show (5) simulation (2) sla (2) snr (2) solution (2) split-horizon (5) sql (1) ssl (2) ssm (4) static (6) stp (2) summarization (5) tcp (2) translation (1) travail (2) udp (2) vpn (3) vrf (3) wifi (11) wireshark (2) wlan (7) wlc (5)

  • vPC vs VSS
    Si l’objectif “historique” est le même : s’affranchir de la limitation de STP (blocage de ports pour prévenir les boucles), de l’usage des FHRP (HSRP, VRRP) pour équilibrer les liens, d’augmenter les performances en débit et capacité de calcul, d’éliminer les SPOF liés à l’utilisation d’un seul châssis ou stack de switches… les implémentations du
  • D.A.T(er) comme un professionnel, un Architecte…
    Dans ce blog, je présente ce travail sur le DAT ou Dossier d’architecture technique d’un point de vue d’un architecte réseau et services (sécurité, qualité de service, gestion d’infrastructure). Le lien vers le travail complet est: D.A.T(er) comme un professionnel, un Architecte… Le DAT… Le dossier d’architecture technique ou DAT s’inscrit en amont dans le
  • La dRRM du WiFi… en action!
    Ce blog présente le travail que vous pouvez retrouver sous le lien: La dRRM du WiFi… en action!, concernant la gestion des ressources radio dans un réseau wifi. La gestion des ressrouces radio ou RRM qui est au coeur de tout développement ou conception d’architecture wifi (d’entreprise ou publique). La RRM commen processus ou module
  • From router configuration to Excel… a basic how to automate configuration work process!
    comment récupérer une certaine information d’un fichier de configuration (routeur IOS de Cisco par exemple) et la mettre dans un fichier Excel en vue d’un traitement plus avancé ce traitement peut être simplement de comparer cette information de plusieurs sources (du routeur et du pare-feu, par exemple) à titre d’exemple nous souhaitons vérifier que les
  • Protected: An example network from scratch: Internet access
    This content is password protected.
September 2025
M T W T F S S
1234567
891011121314
15161718192021
22232425262728
2930  
Table of Contents
Copied!