- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProLiant BL p-Class Interconnect Switch becoming S...
Switches, Hubs, and Modems
1752287
Members
4615
Online
108786
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2004 01:59 AM
08-20-2004 01:59 AM
ProLiant BL p-Class Interconnect Switch becoming STP Root Bridge
Is there a way to configure/prevent the Interconnect switch from becoming STP RootBridge in a Cisco Environment running 802.1Q.
We have Trunking enable to the ICS (three Vlans) and one of the three VLAN's has become root bridge.
In the Cisco Environment we have configured the primary RootBridge and the Secondary bridge , However the ICS has still become the Root bridge. It seems as if the ICS is not learning STP/BPDU's from the Cisco Environment ?
We have Trunking enable to the ICS (three Vlans) and one of the three VLAN's has become root bridge.
In the Cisco Environment we have configured the primary RootBridge and the Secondary bridge , However the ICS has still become the Root bridge. It seems as if the ICS is not learning STP/BPDU's from the Cisco Environment ?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-07-2005 09:23 PM
08-07-2005 09:23 PM
Re: ProLiant BL p-Class Interconnect Switch becoming STP Root Bridge
I had almost the same problem some time ago and that was because we use Multiple Spanning Tree and use mst 1 and mst 2 in our Cisconetwork.
When we conncted the Internet connecting switch for our BL p- and e-class they became root bridge for mst 0 for some reason. My guess is that the switches doesn't support MST and therefore use mst0 as "default".
And since we hadn't specificed any priorities for mst 0 in our Cisco environment the whole network went down for a few seconds while negotiating for root bridge.
What we did was to specify mst 0 in our Ciscos and gave it a lover priority:
spanning-tree mst 0,2 priority 24576
spanning-tree mst 1 priority 28672
And we gave the Interconnect switches a priority of 32768.
Let me know if this is confusing. It was over a year ago I did this but I think I have some documents explaining how we did it.
When we conncted the Internet connecting switch for our BL p- and e-class they became root bridge for mst 0 for some reason. My guess is that the switches doesn't support MST and therefore use mst0 as "default".
And since we hadn't specificed any priorities for mst 0 in our Cisco environment the whole network went down for a few seconds while negotiating for root bridge.
What we did was to specify mst 0 in our Ciscos and gave it a lover priority:
spanning-tree mst 0,2 priority 24576
spanning-tree mst 1 priority 28672
And we gave the Interconnect switches a priority of 32768.
Let me know if this is confusing. It was over a year ago I did this but I think I have some documents explaining how we did it.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP