I told you it wasn´t the easiest thing to troubleshoot! To sum it up, routes generally become SIA when a neighbor either doesn´t answer a query, or either the query or reply took a wrong turn somewhere. The link between the two routers is of low quality, allowing just enough packets through to keep the neighbor relationship intact, but not good enough to allow the replies through. The queried router´s memory is corrupt or otherwise unable to allow the router to answer the query. The queried router´s resources are unavailable, generally due to high CPU utilization. The link is unidirectional, so the query can´t possibly be answered. There are four main reasons a route becomes SIA: Think about if that 5 neighbors having each 3 neibhbors the and they to also quering there neighbors to know the feasible successor that will take a long time. This is also going to take long time depends up on your topology. If any one of the neighbors failed to replay for the query the router will send the unicast to that neighbor up to 16 times and waiting for the replay. once the rotuer recived the replay from all it is neighbors (5) after that once with the updates If the router is having the 5 neighbors it is going to send the multicast message to query it's all the neighbors to know the backup path.Īnd waiting for the replay from all it is neighbors. The roter set a query to all its neighbors. Router(config-router)# timers active-time disable.įor an exam, one of the neighbor is down and there is no feasible successor in the topology table, To disbale the stuck in active timer, the following command is used. To solve this problem, two method is used. The router who didn't replied back the query messages sent by the router. In this case, router reset the neighbor relationship with If reply is missing for 3 min, dat means router didn't get any reply from neighbors, then it becomes stuck in active. It is active state for that route.Now Router is waiting for reply from its neighbors. If the successor path is lost & there is no feasible successor path is available, router sends out query messages on all EIGRP enable interfaces & tries to find out an alternative path to the network.
I believe it is when a router does not get a response fromĪ query, if so what is the impact on the querying router etc ? Explain to me what this is and how it would happen, and what to do to
0 kommentar(er)
