asked on
Count to Infinity Problem With Distance-Vector Routing Protocols
Hi,
I'm revising for my Cisco CCNA. I understand the general concept of count-to-infinity, but I have a problem with it: It was my understanding that routing tables only updated themselves if they were sent updates with routes that were shorter than that already stored. With the count-to-infinity scenario, the routing metric will always be bigger than that currently stored in the table, so the router shouldn't update the routing table to include it. How then, does the metric ever rise to infinity? And if this isn't the case (i.e. routers update regardless of metric values), surely the routing table can't be described as "a table containing the shortest known paths to different networks"?
Chris
I'm revising for my Cisco CCNA. I understand the general concept of count-to-infinity, but I have a problem with it: It was my understanding that routing tables only updated themselves if they were sent updates with routes that were shorter than that already stored. With the count-to-infinity scenario, the routing metric will always be bigger than that currently stored in the table, so the router shouldn't update the routing table to include it. How then, does the metric ever rise to infinity? And if this isn't the case (i.e. routers update regardless of metric values), surely the routing table can't be described as "a table containing the shortest known paths to different networks"?
Chris
RoutersNetwork Architecture
Last Comment
Don Johnston
Think of the scenario with routers A B and C connected as A-B-C. If router A goes down then router B does not receive any packets. Router C on the other hand will tell router B that router A is only 2 hops away. Router B will assume that router A is available from router C and it will slowly propagate through the network. The split-horizon method can reduce the probability of a count-to-infinity problem but in nearly all cases a hold timer within a routing protocol can remove the possibility of this happening.
ASKER
donjohnston> That ties in with something I briefly read. So packets enter a routing loop until the shorter metric gets aged out, at which point it is replaced by the higher metric and so on...? What determines the age-out time? Is it configurable or dependent on network management protocols? Typically, what would this time be?
Cheers
Cheers
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck
http://www.google.gr/url?sa=t&source=web&cd=4&ved=0CDMQFjAD&url=http%3A%2F%2Flearningnetwork.cisco.com%2Fservlet%2FJiveServlet%2Fdownload%2F8472-1-12383%2FDistance%2520Vector%2520Routing%2520Protocols.doc&rct=j&q=cisco%20count%20to%20infinity%20problem&ei=l0V3TbW8II7qOcu0yMcB&usg=AFQjCNHnckjPPxOH85llzG1bdQHTQj5OoA
This link is a document that describes the features of Distance Vector protocols and of course the count to infinity problem.
I think that this subject is a little difficult to explain without a diagram..
This link is a document that describes the features of Distance Vector protocols and of course the count to infinity problem.
I think that this subject is a little difficult to explain without a diagram..
ASKER CERTIFIED SOLUTION
Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
Because the route with the shorter metric ages out. Once that happens the route with the higher metric is now accepted.