cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
538
Views
0
Helpful
3
Replies

Etherchannel went down when one stackmember lost power

pd.politiet.no
Level 1
Level 1

Hi.

I have 2 3750 running IOS 12.2(35)SE5. Today I lost power to one switch in one of the stacks.

Since I've configured etherchannel, it should work fine.  But it didn't.  The switch in the opposite end, reported interface Gi1/0/1, Gi2/0/1 and Po1 down.  No further logging in neither of the switches.

Why didn't the etherchannel configuration keep the trunk up?

Have I missed something, is there a bug in the IOS release or why did this happen?

Logging inn to one of the switches, issuing shut no shut on the interfaces (int gi1/0/1 and int po1) makes the interfaces come up.

I'm searching google for answers, while I'm hoping one of you guys can help me.

Br

Geir

SWITCHSTACK1            SWITCHSTACK2

-----------------------             -----------------------

Switch1-1 gi1/0/1 <-----> gi1/0/1 Switch2-1

Switch1-2 gi2/0/1 <-----> gi2/0/1 Switch2-2

----------switch 2--------------------

switch1#sh run int gi1/0/1

!

interface GigabitEthernet1/0/1

switchport trunk encapsulation dot1q

switchport trunk native vlan 998

switchport trunk allowed vlan 456,800-849,998

switchport mode trunk

switchport nonegotiate

storm-control broadcast level 5.00

storm-control multicast level 10.00

channel-group 1 mode active

end

switch1#sh run int gi2/0/1

!

interface GigabitEthernet2/0/1

switchport trunk encapsulation dot1q

switchport trunk native vlan 998

switchport trunk allowed vlan 456,800-849,998

switchport mode trunk

switchport nonegotiate

storm-control broadcast level 5.00

storm-control multicast level 10.00

channel-group 1 mode active

end

switch1#sh run int po1

!

interface Port-channel1

description Etherchannel mot Digiplex

switchport trunk encapsulation dot1q

switchport trunk native vlan 998

switchport trunk allowed vlan 456,800-849,998

switchport mode trunk

switchport nonegotiate

end

switch1#

----------switch 2--------------------

switch2#sh run int gi1/0/1

!

interface GigabitEthernet1/0/1

switchport trunk encapsulation dot1q

switchport trunk native vlan 998

switchport trunk allowed vlan 456,800-849,998

switchport mode trunk

switchport nonegotiate

storm-control broadcast level 5.00

storm-control multicast level 10.00

channel-group 1 mode active

end

switch2#sh run int gi2/0/1

!

interface GigabitEthernet2/0/1

switchport trunk encapsulation dot1q

switchport trunk native vlan 998

switchport trunk allowed vlan 456,800-849,998

switchport mode trunk

switchport nonegotiate

storm-control broadcast level 5.00

storm-control multicast level 10.00

channel-group 1 mode active

end

switch2#sh run int po1

!

interface Port-channel1

description Etherchannel mot Digiplex

switchport trunk encapsulation dot1q

switchport trunk native vlan 998

switchport trunk allowed vlan 456,800-849,998

switchport mode trunk

switchport nonegotiate

end

3 Replies 3

ranraju
Cisco Employee
Cisco Employee

If are able to reproduce this issue, and if you see the same issue again every time a member switch power cycles in your enviroment, then it might be a buggy behavior and you might have to open a TAC case to investigate further.

Regards,

ranraju

Leo Laohoo
Hall of Fame
Hall of Fame

I have 2 3750 running IOS 12.2(35)SE5.

Wow.  That's an old IOS. 

Joseph W. Doherty
Hall of Fame
Hall of Fame

Disclaimer

The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no  implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind.  Usage of this posting's information is solely at reader's own risk.

Liability Disclaimer

In no event shall Author be liable for any damages whatsoever  (including, without limitation, damages for loss of use, data or  profit) arising out of the use or inability to use the posting's  information even if Author has been advised of the possibility of such  damage.

Posting

Nothing looks wrong, but if you can reproduce the problem, you might try turning LACP off (i.e. use manual mode) and see if that makes a difference.

Review Cisco Networking for a $25 gift card