When a port in the etherchannel is in a suspended state means the port configuration is not compatible with others in the same etherchannel. Check you port configurations and make sure they are 100% match.
thanks for your quick reply, i will check the ports configuration on each side? is there any link or reference on the cisco website that describe this issue?
N.B: the other side of the etherchannel is a Big IP loadbalancer.
You would have to check and see if they are trying to etherchannel to the load balancer or not . Maybe its a leftover config thats not supposed to be there.
I am not able to find any document on the suspended state. However, here is a link on configuring etherchannel with workstation/server.
One more thing that can cause the etherchannel ports to go into a suspended state is when you are using two different types of link control, IE: One side is using LACP, the other side is using PaGP.
Check the log on the device with the suspended ports to verify. You might have to "shut" then "no shut" the suspended ports to generate a fresh log statement.
The other box is a Big IP loadbalancer. it's configured to use the LACP protocol and the same duplex and speed settings.
so you suggest to shut and no shut the suspended interfaces ?
Absolutely, that is the only way to clear the suspended state, once in a suspended state it is very much like being err-disabled, it doesn't try to automatically recover.
You will probably need to shut and no shut your port channel interface as well.
If they go back into a suspended state, do a show log and it will tell you why they went back into a suspended state. Typically if all of the ports in the etherchannel went into a suspended state it's because of a mismatched control protocol or a mismatch with the port-channel interface configuration.
On some devices the default behavior for a port-channel is a routed interface, so adding the "switchport" to the port-channel interface is sometimes required. Also, sometimes during the configuration of one side or the other it can trigger the suspended state, even though your final configuration is correct, you just need to shut no shut to clear the suspended state.
Make sure that if only part of the port-channel is down, you only shut no shut the suspended interfaces and don't shut no shut the port-channel interface, or else you will loose connectivity comnpletely.
Is there any way for the UP interface(P state) to detect the remote suspended interface state(S) and bring its interface down, suspend or un-bundle from Port Channel, so that the traffic doesn't get black holed on one link.
(S)-------------traffic black holed------------------(P)
My colleague told me F5 supports LACP and static link aggregation.
Suggest you use static mode to establish channel.
And why not show the configuration here?