- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- MSTP configuration - adding last switch fails with...
Switches, Hubs, and Modems
1753375
Members
5382
Online
108792
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
12-16-2008 05:40 AM
12-16-2008 05:40 AM
MSTP configuration - adding last switch fails with lockup
Our LAN consists of six ProCurve 2650 and two ProCurve 2510-24G switches. These switches are stacked with one commander and seven members. All switches are linked using the highest portnumbers and schematically the current setup is like so:
|---|
| switch1
| |
| switch2
| |
| switch3
| |
| switch4
| |
| switch5
| |
| switch6
| |
| switch7
| |
| switch8
|-X-|
The X in the bottom of the schema represents a cut in the loop. Last weekend I tried implementing a MSTP configuration so I could close this loop and have basic redundancy added to this topology.
On all switches the same VLAN configuration is created and the uplink ports to other switches are configured with the default VLAN untagged and the other VLANs tagged.
When creating the MSTP config I had created an instance per switch and made each switch the root for one VLAN. Here's the MSTP config section of switch one:
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "bzlan"
spanning-tree instance 1 vlan 1
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 2
spanning-tree instance 2 priority 1
spanning-tree instance 3 vlan 3
spanning-tree instance 3 priority 1
spanning-tree instance 4 vlan 4
spanning-tree instance 4 priority 1
spanning-tree instance 5 vlan 5
spanning-tree instance 5 priority 1
spanning-tree instance 10 vlan 10
spanning-tree instance 10 priority 1
spanning-tree instance 16 vlan 16
spanning-tree instance 16 priority 1
spanning-tree priority 0
And here's the MSTP config section of switch 2:
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "bzlan"
spanning-tree instance 1 vlan 1
spanning-tree instance 1 priority 1
spanning-tree instance 2 vlan 2
spanning-tree instance 2 priority 0
spanning-tree instance 3 vlan 3
spanning-tree instance 3 priority 1
spanning-tree instance 4 vlan 4
spanning-tree instance 4 priority 1
spanning-tree instance 5 vlan 5
spanning-tree instance 5 priority 1
spanning-tree instance 10 vlan 10
spanning-tree instance 10 priority 1
spanning-tree instance 16 vlan 16
spanning-tree instance 16 priority 1
spanning-tree priority 1
In a similar way the instance priority is set per switch so that all switches have priority 0 for one VLAN.
Now the issue is that as I setup MSTP on the switches one by one all seemed to go well until I reached the last one. I could enter the MSTP parameters (for this switch an exact copy of the previous switch (there are seven VLANs and eight switches), but when I tried enabling the MSTP configuration by entering "span" the switch would freeze and a power cycle of the switch was the only means to get it back online. It would come online with the MSTP parameters saved, but no spanning tree enabled.
All switches are loaded with the latest firmware available at the moment.
STP is a new area for me and I have done my best to read up on the subject. Unfortunately I have no idea how to troubleshoot from here. How could I work out where this configuration goes wrong or find out why the switch freezes?
Thanks in advance for your time.
|---|
| switch1
| |
| switch2
| |
| switch3
| |
| switch4
| |
| switch5
| |
| switch6
| |
| switch7
| |
| switch8
|-X-|
The X in the bottom of the schema represents a cut in the loop. Last weekend I tried implementing a MSTP configuration so I could close this loop and have basic redundancy added to this topology.
On all switches the same VLAN configuration is created and the uplink ports to other switches are configured with the default VLAN untagged and the other VLANs tagged.
When creating the MSTP config I had created an instance per switch and made each switch the root for one VLAN. Here's the MSTP config section of switch one:
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "bzlan"
spanning-tree instance 1 vlan 1
spanning-tree instance 1 priority 0
spanning-tree instance 2 vlan 2
spanning-tree instance 2 priority 1
spanning-tree instance 3 vlan 3
spanning-tree instance 3 priority 1
spanning-tree instance 4 vlan 4
spanning-tree instance 4 priority 1
spanning-tree instance 5 vlan 5
spanning-tree instance 5 priority 1
spanning-tree instance 10 vlan 10
spanning-tree instance 10 priority 1
spanning-tree instance 16 vlan 16
spanning-tree instance 16 priority 1
spanning-tree priority 0
And here's the MSTP config section of switch 2:
spanning-tree
spanning-tree protocol-version MSTP
spanning-tree config-name "bzlan"
spanning-tree instance 1 vlan 1
spanning-tree instance 1 priority 1
spanning-tree instance 2 vlan 2
spanning-tree instance 2 priority 0
spanning-tree instance 3 vlan 3
spanning-tree instance 3 priority 1
spanning-tree instance 4 vlan 4
spanning-tree instance 4 priority 1
spanning-tree instance 5 vlan 5
spanning-tree instance 5 priority 1
spanning-tree instance 10 vlan 10
spanning-tree instance 10 priority 1
spanning-tree instance 16 vlan 16
spanning-tree instance 16 priority 1
spanning-tree priority 1
In a similar way the instance priority is set per switch so that all switches have priority 0 for one VLAN.
Now the issue is that as I setup MSTP on the switches one by one all seemed to go well until I reached the last one. I could enter the MSTP parameters (for this switch an exact copy of the previous switch (there are seven VLANs and eight switches), but when I tried enabling the MSTP configuration by entering "span" the switch would freeze and a power cycle of the switch was the only means to get it back online. It would come online with the MSTP parameters saved, but no spanning tree enabled.
All switches are loaded with the latest firmware available at the moment.
STP is a new area for me and I have done my best to read up on the subject. Unfortunately I have no idea how to troubleshoot from here. How could I work out where this configuration goes wrong or find out why the switch freezes?
Thanks in advance for your time.
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