As you probably know EIGRP sends hello messages to each neighbor and expects to receive hello messages from the neighbors as a mechanism to verify that communication between neighbors is still valid. If EIGRP does not receive hello messages from a neighbor it has a timer (holding time) which it uses to determine how long to wait for a message from the neighbor before deciding that the neighbor is down. You have a bunch of neighbors on a bunch of interfaces from which you have not received hello messages and the holding time is expiring.
I do not yet know enough about your environment to be able to advise you whether to reconfigure the EIGRP timers. Was this an isolated event or does it do this frequently? Was there some loss of connectivity to parts of the network where these neighbors are?
In general I am in favor of leaving the EIGRP timers at their default values. I did discover on a group of routers that were running IPSec VPN with GRE over the Internet, that we were having a noticeable amount of EIGRP neighbor instability. I did reconfigure the EIGRP timers to longer values and did find that it improved neighbor stability.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.