Every 30seconds, a router receives from one of its neighbors RIP updates for a specific route. Suddenly that route gets down and then the router received immediately triggered update from that neighbor for that route, now with metric=16. The route is immediately removed from its routing table, though for the next 60 seconds it keeps advertising this route to all its neighbors, with metric=16. After that it stops advertising the route.
RIP hello time is 30 seconds. If a hello is not received from the neighbor after 180 seconds (invalid timer)it advertises it with 'infinite' metric, 16 in RIP case. This way it advice its neighbors not to use that 'dead' route.
The 60 seconds timer is called the 'flush timer' or the 'garbage collector timer' and it is used by RIP only as a routing table cleaning tool.
Another advantage is that the route will remain in the routing table after the flush timer expires, that way if a new hello is received, the route still will be on the table.
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...