Administrative distance in Cisco proprietary protocols

Started by j.sivasankar92, April 03, 2015, 08:52:04 AM

Previous topic - Next topic

j.sivasankar92

Hello to all professionals,
                       
                        Default AD value for following,
   
Rip- 120
OSPF- 110
EIGRP-90

Then why we have the distance changing value options.

Like following when we enabled the protocols,

router(config-router)#distance ?


deanwebb

The options are for route tuning, to prefer certain routes over others.
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

j.sivasankar92

Oh! ok for Rip protocol default AD is 120 if I'm going to reduce as a 60.
60 is least than others. I meant that has a lowest AD value.
So it will be a prefer than others. I got it.
But there is any limitations to reduce upto ...I'm asking any limit range is there for to reduce on each protocols.

srg

som om sinnet hade svartnat för evigt.

NetworkGroover

Quote from: j.sivasankar92 on April 03, 2015, 08:52:04 AM
Hello to all professionals,
                       
                        Default AD value for following,
   
Rip- 120
OSPF- 110
EIGRP-90

Then why we have the distance changing value options.

Like following when we enabled the protocols,

router(config-router)#distance ?

There are some special case scenarios where you may need or want to do it.  It's a tool in the toolbox, basically. One that comes to mind that I did somewhat recently was modifying AD for iBGP and eBGP for a mutual redistribution scenario involving two vendors.
Engineer by day, DJ by night, family first always

Reggle

Another example is in a network where I'd like a third party EIGRP preferred over my own OSPF. All nice with default AD values (90 and 110) until the third party redistributed static routes, with come in as EIGRP External at... AD 170. Distance 180 for OSPF and it's solved.

NetworkGroover

Quote from: Reggle on April 09, 2015, 03:22:42 AM
Another example is in a network where I'd like a third party EIGRP preferred over my own OSPF. All nice with default AD values (90 and 110) until the third party redistributed static routes, with come in as EIGRP External at... AD 170. Distance 180 for OSPF and it's solved.

That's a good one.

I'd also like to add a little more context to the example I provided for the OP.  Sometimes vendors don't agree on what ADs should be for certain things, so when you have multivendor environments that's where you might often do things like modify AD, STP costs, etc. where you usually wouldn't in a single vendor environment.
Engineer by day, DJ by night, family first always