Dead timer expired suggests that there were lost hello packets between the two switches. Check to see if the link(s) between these OSPF neighbors is congested and/or if there is (or was) a high-cpu condition on either device.
are only 7 seconds just the time to rebuild the OSPF adjacency.
Down doesn't mean that the portchannel went down, but refers to ospf neighbor state machine from Full -> down because DEAD timer expired means router was not able to receive ospf hello during last 40 seconds. (with default timer values)
Jul 21 07:15:56.167: %OSPF-5-ADJCHG: Proces(s 1, Nbr 184.108.40.206 on Port-channel3 from FULL to DOWN, Neighbor Down: Dead timer expired
Jul 21 07:16:03.227: %OSPF-5-ADJCHG: Process 1, Nbr 220.127.116.11 on Port-channel3 from LOADING to FULL, Loading Done
The trouble comes if the event happens many times.
Try to investigate on how much the port-channel is used. A QoS scheduler to protect ospf traffic could be needed if the link is very busy.
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.