up the link with error-disable

[petercinvest]

I need to create a etherchannel between SW1 and SW2,

SW1 port E1/0, E1/1 and SW2 port E1/0, E1/1 is the trunk port.

SW1 E1/0 show errdisable recovery : BPDUGUARD is disable

SW2 E1/0 sh errdisable recovery : BPDUGUARD is enable

now E1/0 to E1/1 in both two switches is down, I have finished create etherchannel between SW1 and SW2, do I need to run no errdisable recovery cause bpduguard in SW2? I need bring E1/0 and E1/1 in SW1,SW2 to up status

thanks

[Mark Malone]

Hi

is bpduguard configured under the port ?  it shouldn't be if its a trunk between switches and that's why its going err-disable mode , its for access poirts only with portfast

remove bpduguard if its there and bounce the interfaces they should come up

[petercinvest]

bpduguard is configured global for SW1 and SW2.

span portfast bpduguard default,

and bpduguard should not be removed , do I need to run no errdisable recovery cause bpduguard in SW2? or I can directly go to : int ran e1/0-1, no shut? thanks

[Mark Malone]

no if its enabled globally it will only act on access ports anyway not trunks , you can just bounce the port , but if it happens again its always good to have err-disable recovery enabled for automatic recovery so it just corrects itself save you having to login and do it

[Joseph W. Doherty]

. . . its always good to have err-disable recovery enabled for automatic recovery so it just corrects itself save you having to login and do it

Depending on what's causing the err-disable, you might not want auto recovery - to avoid port flapping.

[paul driver]

Hello

In addition to the other suggestions- May I suggest removing etherchannel completely and defaulting the physical interafaces in that order and re-creating it from scratch- This way you'll have a clean logical etherchannel.

let the port-channel get created automatically via the channel-group command on the physical interfaces and remember the portchannel will will take the existing configuration of the first physical interface defined to it so that's why it's best practice to default the physical interfaces and then join them to a channel group and then configure the trunk on the port-channel interface.

This will then propergate that config to the physical interfaces.

As for bpduguard-globally defined its only active when the access ports have portfast  enabled to them 

interface defined - it will erridisble without portfast as it not required 

res

paul

[Tausif Gaddi]

In networks where resources may be located far from where users might need them, some links between switches or between switches and servers become heavily solicited. The speed of these links can be increased, but only to a certain point. EtherChannel is a technology that allows you to circumvent the bandwidth issue by creating logical links that are made up of several physical links.

To configure BPDU Guard in Global mode use the spanning-tree portfast bpduguard default command in Global Configuration Mode:

SW2(config)# spanning-tree portfast bpduguard default

To configure BPDU Guard in Interface mode use the spanning-tree bpduguard enable command under the interface:

SW2(config-if)# spanning-tree bpduguard enable