- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Simple MST setup - config and some questions
Switches, Hubs, and Modems
1752634
Members
6041
Online
108788
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО10-25-2010 01:17 AM
тАО10-25-2010 01:17 AM
Hi all
(I also cross-posted to the new forums at http://h30499.www3.hp.com/t5/Legacy/bd-p/switching-legacy-forum)
Over the weekend I transitioned from RSTP to MST in our pretty simple network, but I wonder if I have done it right.
I am using one 3500yl and 5 3400cl. The topology is shown on the attached PNG...
All switches are in the same region and have the same mst configuration digest.
(all switches)# spanning-tree instance 1 vlan 1 2
(all switches)# spanning-tree instance 2 vlan 3 4
In order to have some load-balancing between the two fiber trunks MST was set up like this:
sw-1 and sw-3:
# spanning-tree instance 1 trk1 path-cost 6667
# spanning-tree instance 1 priority 2
# spanning-tree instance 2 trk1 path-cost 20000
# spanning-tree instance 2 priority 4
sw-2 and sw-4:
# spanning-tree instance 1 trk1 path-cost 20000
# spanning-tree instance 1 priority 4
# spanning-tree instance 2 trk1 path-cost 6667
# spanning-tree instance 2 priority 2
No special modifications on sw-5 and sw-6.
I also would like sw-3 or sw-4 to be both regional and IST roots, so I increase their priority:
sw-3# spanning-tree priority 0
sw-4# spanning-tree priority 1
Does this look correct? The network works as expected so far, and
show spanning-tree root-history ...
indicates that the correct switches are roots.
Some questions:
- What does "spanning-tree path-cost/priority nnn" do when using MST? Are these values just used for CST?
- Any suggestions on how to check that the VLAN-load-balancing actually works as expected?
Best
Maurice
(I also cross-posted to the new forums at http://h30499.www3.hp.com/t5/Legacy/bd-p/switching-legacy-forum)
Over the weekend I transitioned from RSTP to MST in our pretty simple network, but I wonder if I have done it right.
I am using one 3500yl and 5 3400cl. The topology is shown on the attached PNG...
All switches are in the same region and have the same mst configuration digest.
(all switches)# spanning-tree instance 1 vlan 1 2
(all switches)# spanning-tree instance 2 vlan 3 4
In order to have some load-balancing between the two fiber trunks MST was set up like this:
sw-1 and sw-3:
# spanning-tree instance 1 trk1 path-cost 6667
# spanning-tree instance 1 priority 2
# spanning-tree instance 2 trk1 path-cost 20000
# spanning-tree instance 2 priority 4
sw-2 and sw-4:
# spanning-tree instance 1 trk1 path-cost 20000
# spanning-tree instance 1 priority 4
# spanning-tree instance 2 trk1 path-cost 6667
# spanning-tree instance 2 priority 2
No special modifications on sw-5 and sw-6.
I also would like sw-3 or sw-4 to be both regional and IST roots, so I increase their priority:
sw-3# spanning-tree priority 0
sw-4# spanning-tree priority 1
Does this look correct? The network works as expected so far, and
show spanning-tree root-history ...
indicates that the correct switches are roots.
Some questions:
- What does "spanning-tree
- Any suggestions on how to check that the VLAN-load-balancing actually works as expected?
Best
Maurice
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2010 04:48 AM
тАО10-26-2010 04:48 AM
Solution
Hello Maurice,
some comments: You should assign unique prio values to each switch - i.e. prio 1 for sw-1, prio 2 for sw-3 and so on. otherwise the MAC address will decide which switch will be root.
But everything else is looking fine.
spanning-tree path-cost/priority nnn will assign path cost for instance 0 (IST).
Loadbalancing can be checked with:
# show int port-utilization
Cheers,
Michael
some comments: You should assign unique prio values to each switch - i.e. prio 1 for sw-1, prio 2 for sw-3 and so on. otherwise the MAC address will decide which switch will be root.
But everything else is looking fine.
spanning-tree
Loadbalancing can be checked with:
# show int port-utilization
Cheers,
Michael
Ingentive Networks GmbH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2010 07:17 AM
тАО10-26-2010 07:17 AM
Re: Simple MST setup - config and some questions
Thanks for the clarifications, Michael!
/Maurice
/Maurice
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