Hello,

I have seen these problems happen when configuring Etherchannels mostly without the management protocol (PAgP or LACP) when one switch had already its ports put into Etherchannel while the other was not yet configured for Etherchannel.

If it is possible, I suggest double-checking the Port-channel configuration on both switches: make sure that the members ports are all identically configured and that all relevant configuration appears also on the Port-channel virtual interface. If you do not use a management protocol I suggest you implement the LACP or PAgP (I slightly prefer the LACP).

After this check (please be really thorough!), shutdown all member interfaces including the Port-channel interface itself on both switches. Make sure that all member ports including the Port-channel interface indeed contain the "shutdown" command on both switches. Then, one switch after another, turn on the Port-channel interface using the "no shutdown" command. After the Port-channel is brought up again on both switches, check if it is still reported as looped.

The best practices when setting up Etherchannels are:

1.) Shutdown all physical switchports on both switches before assigning them to a Port-channel interface.

2.) Do not ever activate a port channel against another switch whose ports have not yet been assigned to a port channel.

3.) The recommended order of operations is: First, shutdown the switchports to be bundled on both switches. Second, assign the ports into Port-channel groups. Third, turn on these ports, one switch at a time.

4.) Whenever possible, use a management protocol such as LACP or PAgP.

Please let us know if this worked for you.

Best regards,

Peter