cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1935
Views
5
Helpful
3
Replies

loopguard blocking inconsistent port causes neighboring switch to fail and drop SVI interfaces spanning-tree issue

leejm1988
Level 1
Level 1

I am uploading a topology diagram here. I believe I have the answer already, but I am confused as to what I was seeing. During a switch replacement, I know it looks sloppy but this is not the end result. Switch B has loopguad enabled globally. it shutddown inconsistent to switch A on that port. Switch A is the only uplink to the rest of the network for all downstream switches B,C,D,E switch A is layer 2 only and has a management IP on interface vlan 37 all switches are using Rapid-PVST and have loopguard disabled, except switch B. Switch E is the root bridge for all vlans I got a ping monitoring alert, that switch A went down. I cannot access it, but the uplink to jo_mdf_gig from switch A shows forwarding and up. Also I can ping everything else, but... nothing connected directly to switch A works. It seems to only allow layer 2 to pass through it. I can access switch B remotely, and everything downstream works, the uplink from B to A shows up and forwarding except: Switch B shows errors for loopguard inconsistent ports on the uplink to switch A I turned off loopguard on switch B, which fixed the problem. Upon further investigation, this site had Switch E as the root bridge for all vlans in spanning-tree, I have since moved it to a closer distribution layer switch upstream. My questions are... why would the int vlan 37 on switch A go down at all? and why would layer two still allow everything downstream to respond to pings still if switch B was blocking inconsistent to that uplink...?

1 Accepted Solution

Accepted Solutions

andresfr
Cisco Employee
Cisco Employee

Hello,

 

It's hard to say without having additional details about the configuration and the errors or the outputs of some commands collected while the issue was happening.

 

However, loopguard blocking inconsistent port will occur when no longer receiving BPDUs on a non-designated port, and a  VLAN SVI will go down if no access ports mapped to the VLAN are up/up , and if there are no trunk interfaces allowing that VLAN up/up.

 

Regards,

View solution in original post

3 Replies 3

andresfr
Cisco Employee
Cisco Employee

Hello,

 

It's hard to say without having additional details about the configuration and the errors or the outputs of some commands collected while the issue was happening.

 

However, loopguard blocking inconsistent port will occur when no longer receiving BPDUs on a non-designated port, and a  VLAN SVI will go down if no access ports mapped to the VLAN are up/up , and if there are no trunk interfaces allowing that VLAN up/up.

 

Regards,

Thanks andresfr!  That part of the answer: a  VLAN SVI will go down if no access ports mapped to the VLAN are up/up , and if there are no trunk interfaces allowing that VLAN up/up.

 

there were no access ports going to vlan 37 at all on that switch.  so since switch A couldn't reach the root bridge and that port became a blocking port, there were no up/up ports going to the only mgmt vlan on switch A.

A point of clarification - a VLAN interface will stop forwarding if there are no ports in the VLAN that are forwarding in STP.  So you can have up/up interfaces in the VLAN, but if none are "FWD" in STP then the VLAN interface will still be down.