STP EtherChannel Guard

Unanswered Question
Feb 13th, 2009

According to the guidance provided by multiple sources - one quoted here

"The EtherChannel Guard feature is used to detect EtherChannel misconfigurations between the switch and a connected device."

Could this vague reference to a "CONNECTED DEVICE" be considered as a NON-Cisco device OR even a Microsoft/Unix/Linux/etc SERVER performing link sharing?

Tks

Frank

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 2.5 (2 ratings)
Loading.
fsebera Fri, 02/13/2009 - 07:31

What?

Not asking at relevance - I can read - I am asking about what "CONNECTED DEVICE" is referring.

Giuseppe Larosa Fri, 02/13/2009 - 07:36

Hello Frank,

a server performing any form of teaming is usually not going to be an STP speaker of any form. (It may be with some new blade based servers that have their own front end to the network)

This feature is thought to protect inter-switch bundles from possible misconfigurations.

I can tell you that in our customer network two times a bridging loop was formed by the following event:

someone trying to add a vlan in the list of vlan permitted but on a member link instead of doing it on the logical port-channel.

In both cases it was a bundle of GE links between two C6500.

So I think the feature was introduced for dealing with this kind of events.

We are moving to a LACP based bundles to servers teaming bundles.

Hope to help

Giuseppe

Actions

This Discussion