- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Spanning Tree
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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-11-2018 10:57 PM
12-11-2018 10:57 PM
Spanning Tree
Hello,
we use hp procurve and aruba switches.
My predecessor configured the switch as follows:
spanning-tree
no spanning-tree 4 auto-edge-port
no spanning-tree 6 auto-edge-port
spanning-tree 7 admin-edge-port
no spanning-tree 7 auto-edge-port
spanning-tree 7 root-guard bpdu-filter bpdu-protection
spanning-tree 8 admin-edge-port
no spanning-tree 8 auto-edge-port
spanning-tree 8 root-guard bpdu-filter bpdu-protection
spanning-tree 9 admin-edge-port
no spanning-tree 9 auto-edge-port
spanning-tree 9 root-guard bpdu-filter bpdu-protection
spanning-tree 10 admin-edge-port
no spanning-tree 10 auto-edge-port
spanning-tree 10 root-guard bpdu-filter bpdu-protection
spanning-tree 11 admin-edge-port
no spanning-tree 11 auto-edge-port
spanning-tree 11 root-guard bpdu-filter bpdu-protection
spanning-tree 12 admin-edge-port
no spanning-tree 12 auto-edge-port
spanning-tree 12 root-guard bpdu-filter bpdu-protection
spanning-tree 13 admin-edge-port
no spanning-tree 13 auto-edge-port
spanning-tree 13 root-guard bpdu-filter bpdu-protection
spanning-tree 14 admin-edge-port
no spanning-tree 14 auto-edge-port
spanning-tree 14 root-guard bpdu-filter bpdu-protection
spanning-tree 15 admin-edge-port
no spanning-tree 15 auto-edge-port
spanning-tree 15 root-guard bpdu-filter bpdu-protection
spanning-tree 16 admin-edge-port
no spanning-tree 16 auto-edge-port
spanning-tree 16 root-guard bpdu-filter bpdu-protection
spanning-tree 17 admin-edge-port
no spanning-tree 17 auto-edge-port
spanning-tree 17 root-guard bpdu-filter bpdu-protection
spanning-tree 18 admin-edge-port
no spanning-tree 18 auto-edge-port
spanning-tree 18 root-guard bpdu-filter bpdu-protection
spanning-tree 19 admin-edge-port
no spanning-tree 19 auto-edge-port
spanning-tree 19 root-guard bpdu-filter bpdu-protection
spanning-tree 20 admin-edge-port
no spanning-tree 20 auto-edge-port
spanning-tree 20 root-guard bpdu-filter bpdu-protection
spanning-tree 21 admin-edge-port
no spanning-tree 21 auto-edge-port
spanning-tree 21 root-guard bpdu-filter bpdu-protection
spanning-tree 22 admin-edge-port
no spanning-tree 22 auto-edge-port
spanning-tree 22 root-guard bpdu-filter bpdu-protection
spanning-tree 23 admin-edge-port
no spanning-tree 23 auto-edge-port
spanning-tree 23 root-guard bpdu-filter bpdu-protection
spanning-tree 24 admin-edge-port
no spanning-tree 24 auto-edge-port
spanning-tree 24 root-guard bpdu-filter bpdu-protection
no spanning-tree Trk1 auto-edge-port
spanning-tree Trk1 priority 4
spanning-tree bpdu-protection-timeout 300 force-version RSTP-operation
We have a trunk on ports 1-4 and we have ports 5 and 6 ready in case a trunk ports is defect.
On the other ports are server (also VMware) and clients connected.
How should I configure spanning tree?
I have read this document: https://www.ingentive.net/sites/default/files/anwenderdokumente/procurve_best_practice_spanning_tree.pdf
Is that what my predecessor did okay?
I would do it this way:
spanning-tree
spanning-tree 7-24 root-guard bpdu-filter bpdu-protection
spanning-tree 7-24 admin-edge port (because the clients and servers)
spanning tree Trk1 priority 4
spanning tree bpdu-protection-timeout 300 force-version RSTP-operation
I am thankful for any help
Kind regards
Tobias
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2019 04:29 AM
01-02-2019 04:29 AM
Re: Spanning Tree
Hi there,
what you wrote at the bottom is the same like in the config. Once entered the switch will stretch it to the bigger size for whatever reason.
The command "spanning tree Trk1 priority 4" is created automatically whenever you create a new trunk port.
Just be sure to implement loop-protection on the client ports. When you filter the bpdus with the "bpdu-filter" command, the port will always be in a forwarding state and not send or receive bpdus on this port. Because of that the switch will not detect loops via STP on these ports.
More info: http://h22208.www2.hpe.com/eginfolib/networking/docs/switches/WB/15-18/5998-8156_wb_2926_atmg/content/ch03s05.html
I only activate the bpdu filter at the network edge (if the switch is also a router to another company), but I can see why you would deactivate it.