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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Spanningtree behavior in multiple VTP domains

What's the expected behavior when one VLAN crosses over several VTP domains that have spanningtree enabled? I observed that all switches picked the same root switch, but instead of putting a port in blocking, it puts it in "type-inconsis" state.

  • Other Network Infrastructure Subjects
2 REPLIES

Re: Spanningtree behavior in multiple VTP domains

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen

If anyone else in the forum has some advice, please reply to this thread.

Thank you for posting.

New Member

Re: Spanningtree behavior in multiple VTP domains

My understanding of vtp domains is that a group of switches learns from the switch setup as "server" and gets a list of valid vlans. It then uses normal rules of spanning tree to choose a switch to be used as the root based upon mac address, priority etc (normal bridge priority is 32768 by default). If you have a vlan that is not a valid vlan for a particular vtp domain ie because maybe it doesn't exist then it will not be able to forward the vlan across the switches to another point. You need to add the vlan to the list of other vtp domains to ensure it gets acted upon with normal spanning tree rules.

As for all switches picking the same root switch this is probably a switch with either a lower priority than 32768 eg 8192 and it should be a core switch.

Another possibility for type-inconsistent is that the native vlan's do not match but that may be wrong

105
Views
0
Helpful
2
Replies