I have a LACP based etherchannel configured b/w a Cisco catalyst 3750 switch and a server which implements LACP. The ports on the server are configured to be in 'active' LACP mode and the switch ports in 'passive' mode. The ports are configured for long timeout. The aggregation sets up normally without any issues and works fine.
Server -------- Cisco Sw
I have a situation where, due to some issue in the server, LACPDUs aren't being sent over P2 for a few seconds. The timer (current_while) expires at P2 on the Switch and LACP running on the port moves to 'Defaulted' state. Now, the switch moves port P2 to suspended state and doesn't forward any packets to that port. I don't understand why should the port be suspended. 802.3ad specs is not very clear on this. Is this the expected/correct behavior ...?
I tried this with another switch (diff make) and that also behaves in the same manner.
I recently upgraded my cisco switch software to the latest level (12.2(44)) and I don't see this issue anymore. That is, the port P2 on the switch is not suspended though LACP is in 'Defaulted' state. But my other switch still behaves the same. I am assuming that the new Cisco behavior is correct.
A small correction. The server actually wasn't sending LACPDUs for more than 90 seconds, which is the timeout period with 'long timeout' setting. Hence the timer at P2 on the switch timed out and the LACP moved to 'Defaulted' state. I am trying to understand if suspending the port and not forwarding any packets over the port is a correct behavior in this case.
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.