Holddown timer
jovanis
Member Posts: 1 ■□□□□□□□□□
in CCNA & CCENT
Hi,
I have a number of enquiries about holddown timer. I would be pleased if you could answer to some of them.
1. Is the scenario correct?
0 sec:
* router has the following ip route R 192.168.1.0 255.255.255.0 [120/2] 00:00:29 s0/0/1
* and receives R 192.168.1.0 255.255.255.0 [120/16] 00:00:00 s0/0/1
* holdown and invalid timer start
180th sec
* no updates with better or equal metric have been received
* flush timer starts
320th sec
* the route is erased, although an update with better metric has received
2. Is this scenario correct?
0 sec:
* there is an update for a route
* invalid timer starts
180 sec
* no update for this route has received
* flush timer starts
320 sec
* the route is erased, although an update has received
3. Also using the clear ip route * command, it is recommended to wait for 1 minute before routing table gets refreshed. Does this process has anything to do with the previous timers.
Thank you in advance,
John
I have a number of enquiries about holddown timer. I would be pleased if you could answer to some of them.
1. Is the scenario correct?
0 sec:
* router has the following ip route R 192.168.1.0 255.255.255.0 [120/2] 00:00:29 s0/0/1
* and receives R 192.168.1.0 255.255.255.0 [120/16] 00:00:00 s0/0/1
* holdown and invalid timer start
180th sec
* no updates with better or equal metric have been received
* flush timer starts
320th sec
* the route is erased, although an update with better metric has received
2. Is this scenario correct?
0 sec:
* there is an update for a route
* invalid timer starts
180 sec
* no update for this route has received
* flush timer starts
320 sec
* the route is erased, although an update has received
3. Also using the clear ip route * command, it is recommended to wait for 1 minute before routing table gets refreshed. Does this process has anything to do with the previous timers.
Thank you in advance,
John