- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Procurve 2910al series redundant paths
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
01-28-2013 02:27 PM
01-28-2013 02:27 PM
Procurve 2910al series redundant paths
I am managing an environment that is spread out over multiple floors. Each floor has multiple Procurve 2910 al series switches that are stacked and are daisy chained together using the 10-GbE al interconnect kits (single port 10Gb expansion modules). The stack is connected back to the Procurve 6600ml core switch with a single Fibre optic link from the Commander in the stack.
Obviously this is a bit of a problem from a redundancy standpoint as there are multiple points of failure with having only a single link back to the core and having only 1 core switch, but in addition to this, if ANY switch in the stack goes down, all switches that are connected below it also lose connectivity back to the core.
What I would like to do is add an additional Procurve 6600 to the Core and then add an additional link back to the new core from the bottom switch in the stack so that I have multiple paths from each stack back to the core. I just want to know if this is going to work the way in am invisioning.
It is probably worth noting that I have spanning tree on for all switches on the network so this shouldn't introduce any network loops. If i do go ahead with this change, should i set the spanning tree priority of the new link to be lower than the existing link, or should it work without this?
I have included a diagram of how things are currently set up and a diagram of how i want things set up. If there is any additional info needed please ask.