Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

Problem with Port-Channel

Friends, I have a problem with two cisco 4500 switches connected by port-channel, these two modules and has two switches are interconnected by 16 ports, 8 ports on module 2 and 8-port module 3, and every day I have problems when I put the show logging command has the following information:

027338: Jun 28 08:21:40: %SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port Port-channel13 on VLAN0174.

027339: Jun 28 08:21:42: %SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port Port-channel13 on VLAN0001.

027340: Jun 28 08:21:44: %GLBP-6-FWDSTATECHANGE: Vlan178 Grp 1 Fwd 2 state Listen -> Active

027341: Jun 28 08:21:44: %GLBP-6-FWDSTATECHANGE: Vlan173 Grp 1 Fwd 2 state Listen -> Active

027342: Jun 28 08:21:44: %GLBP-6-FWDSTATECHANGE: Vlan174 Grp 1 Fwd 2 state Listen -> Active

027343: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan30 Grp 1 Fwd 2 state Listen -> Active

027344: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan170 Grp 1 Fwd 2 state Listen -> Active

027345: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan171 Grp 1 Fwd 2 state Listen -> Active

027346: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan175 Grp 1 Fwd 2 state Listen -> Active

027347: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan190 Grp 1 Fwd 2 state Listen -> Active

027348: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan20 Grp 1 Fwd 2 state Listen -> Active

027349: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan24 Grp 1 Fwd 2 state Listen -> Active

027350: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan51 Grp 1 Fwd 1 state Listen -> Active

027351: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan176 Grp 1 Fwd 2 state Listen -> Active

027352: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan26 Grp 1 Fwd 1 state Listen -> Active

027353: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan128 Grp 1 Fwd 2 state Listen -> Active

027354: Jun 28 08:21:45: %GLBP-6-FWDSTATECHANGE: Vlan180 Grp 1 Fwd 2 state Listen -> Active

027355: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet2/46 left the port-channel Port-channel13

027356: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet2/45 left the port-channel Port-channel13

027357: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet3/48 left the port-channel Port-channel13

027358: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet3/46 left the port-channel Port-channel13

027359: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet2/48 left the port-channel Port-channel13

027360: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet2/47 left the port-channel Port-channel13

027361: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet3/47 left the port-channel Port-channel13

027362: Jun 28 08:21:52: %EC-5-UNBUNDLE: Interface GigabitEthernet3/45 left the port-channel Port-channel13

027363: Jun 28 08:22:03: %EC-5-BUNDLE: Interface GigabitEthernet2/45 joined port-channel Port-channel13

027364: Jun 28 08:22:03: %EC-5-BUNDLE: Interface GigabitEthernet2/46 joined port-channel Port-channel13

027365: Jun 28 08:22:03: %EC-5-BUNDLE: Interface GigabitEthernet2/47 joined port-channel Port-channel13

027366: Jun 28 08:22:03: %EC-5-BUNDLE: Interface GigabitEthernet2/48 joined port-channel Port-channel13

027367: Jun 28 08:22:46: %EC-5-UNBUNDLE: Interface GigabitEthernet2/46 left the port-channel Port-channel13

027368: Jun 28 08:22:46: %EC-5-UNBUNDLE: Interface GigabitEthernet2/45 left the port-channel Port-channel13

027369: Jun 28 08:22:46: %EC-5-UNBUNDLE: Interface GigabitEthernet2/48 left the port-channel Port-channel13

027370: Jun 28 08:22:46: %EC-5-UNBUNDLE: Interface GigabitEthernet2/47 left the port-channel Port-channel13

027371: Jun 28 08:23:20: %EC-5-BUNDLE: Interface GigabitEthernet2/45 joined port-channel Port-channel13

027372: Jun 28 08:23:20: %EC-5-BUNDLE: Interface GigabitEthernet2/46 joined port-channel Port-channel13

027373: Jun 28 08:23:20: %EC-5-BUNDLE: Interface GigabitEthernet2/48 joined port-channel Port-channel13

027374: Jun 28 08:23:21: %EC-5-BUNDLE: Interface GigabitEthernet2/47 joined port-channel Port-channel13

027375: Jun 28 08:23:53: %EC-5-UNBUNDLE: Interface GigabitEthernet2/47 left the port-channel Port-channel13

027376: Jun 28 08:23:54: %EC-5-UNBUNDLE: Interface GigabitEthernet2/48 left the port-channel Port-channel13

027377: Jun 28 08:23:54: %EC-5-UNBUNDLE: Interface GigabitEthernet2/46 left the port-channel Port-channel13

027378: Jun 28 08:23:54: %EC-5-UNBUNDLE: Interface GigabitEthernet2/45 left the port-channel Port-channel13

027379: Jun 28 08:24:19: %EC-5-BUNDLE: Interface GigabitEthernet2/45 joined port-channel Port-channel13

027380: Jun 28 08:24:19: %EC-5-BUNDLE: Interface GigabitEthernet2/46 joined port-channel Port-channel13

027381: Jun 28 08:24:19: %EC-5-BUNDLE: Interface GigabitEthernet2/47 joined port-channel Port-channel13

027382: Jun 28 08:24:19: %EC-5-BUNDLE: Interface GigabitEthernet2/48 joined port-channel Port-channel13

027383: Jun 28 08:24:48: %EC-5-UNBUNDLE: Interface GigabitEthernet2/46 left the port-channel Port-channel13

027384: Jun 28 08:24:48: %EC-5-UNBUNDLE: Interface GigabitEthernet2/48 left the port-channel Port-channel13

027385: Jun 28 08:24:48: %EC-5-UNBUNDLE: Interface GigabitEthernet2/47 left the port-channel Port-channel13

027386: Jun 28 08:24:48: %EC-5-UNBUNDLE: Interface GigabitEthernet2/45 left the port-channel Port-channel13

027387: Jun 28 08:25:08: %EC-5-BUNDLE: Interface GigabitEthernet2/45 joined port-channel Port-channel13

027388: Jun 28 08:25:08: %EC-5-BUNDLE: Interface GigabitEthernet2/46 joined port-channel Port-channel13

027389: Jun 28 08:25:08: %EC-5-BUNDLE: Interface GigabitEthernet2/47 joined port-channel Port-channel13

027390: Jun 28 08:25:08: %EC-5-BUNDLE: Interface GigabitEthernet2/48 joined port-channel Port-channel13

027391: Jun 28 08:25:09: %EC-5-BUNDLE: Interface GigabitEthernet3/45 joined port-channel Port-channel13

027392: Jun 28 08:25:09: %EC-5-BUNDLE: Interface GigabitEthernet3/46 joined port-channel Port-channel13

027393: Jun 28 08:25:09: %EC-5-BUNDLE: Interface GigabitEthernet3/47 joined port-channel Port-channel13

027394: Jun 28 08:25:09: %EC-5-BUNDLE: Interface GigabitEthernet3/48 joined port-channel Port-channel13

027395: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan190 Grp 1 Fwd 2 state Active -> Listen

027396: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan30 Grp 1 Fwd 2 state Active -> Listen

027397: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan128 Grp 1 Fwd 2 state Active -> Listen

027398: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan174 Grp 1 Fwd 2 state Active -> Listen

027399: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan26 Grp 1 Fwd 1 state Active -> Listen

027400: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan170 Grp 1 Fwd 2 state Active -> Listen

027401: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan173 Grp 1 Fwd 2 state Active -> Listen

027402: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan180 Grp 1 Fwd 2 state Active -> Listen

027403: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan51 Grp 1 Fwd 1 state Active -> Listen

027404: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan20 Grp 1 Fwd 2 state Active -> Listen

027405: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan175 Grp 1 Fwd 2 state Active -> Listen

027406: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan178 Grp 1 Fwd 2 state Active -> Listen

027407: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan176 Grp 1 Fwd 2 state Active -> Listen

027408: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan171 Grp 1 Fwd 2 state Active -> Listen

027409: Jun 28 08:25:49: %GLBP-6-FWDSTATECHANGE: Vlan24 Grp 1 Fwd 2 state Active -> Listen

Could someone help me?

thank you

Everyone's tags (3)
2 REPLIES

Problem with Port-Channel

Did you check the Port config and channel config, maybe u can post that to let us check it?

Is there any loop on 2 VLANs. which type of STP are u using?

I'm sure we found the problem .

regards,
Sebastian

Problem with Port-Channel

Hi Tiago,

you should post the log of the events before the ones you have posted above. It is important to understand why the loopguard is receiving BPDU from the wrong side and where the loopguard is configured. Ideally you should post:

show interface intf switchport

show int po13

sh run int po13

and enable:

debug ip packet event

debug ip packet detail

debug spanning-tree bpdu (with the options you have)

and enabling

conf t

logg buff 16000 debug

end

!

Let us know and check the status of the spanning tree for each vlan. It looks it did not converge properly.

Happy to help

Alessio

1143
Views
0
Helpful
2
Replies
CreatePlease to create content