At the end of episode : Intro to Routing Protocols, I didn't get quite right the last definition Don mentioned, which was:
Admin Distance: tie breaker when same route from 2 different protocols
Metric: tie breaker when 2 routes from same protocol
So, does this definition applies also to static routes?
because on the example in class we used admin distance as the tie breaker for static routes.
Solved Administrative Distance vs Metric
Yes the definition should apply to static routes.
You can change the AD of a static route when setting up a static route. Example
Now, what i can't find out is how to show the AD of a static route without doing a show run. other protocols show it through show IP route.
The definition does apply to any route that gets into the routing table. They key difference though is this. With multiple routing protocols, they learn routes and if multiple routing protocols learn about the best path to the destination which one get's entered into the routing table? The initial decision maker technically is the protocol's administrative distance--the lower the better.
With a static route this is not a learned route. It is an administratively entered route which by default is 1. The only better one is a connected route with an AD of ZERO. This is because the route is considered most trustworthy is the one that the administrator has typed in himself. If you chooses to enter a different administrative distance that's perfectly fine--technically what we call a floating-static route. But this is normally done as a backup routing method in case the routing protocol we implement fails and cannot find a route to the destination.
Between static routes to the same destination...as in your class case, the AD wouldn't necessarily be the tie breaker but the metric unless you are manipulating the AD as in the floating-static route.
*if the post above has answered the question, please mark the topic as solved.
**All "answers" and responses are offered "as is" and my opinion. There is no implied support or guarantee by the ITProTV team.