- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Q: ProCurve 5038; Any pitfalls when moving fro...
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
Discussions
Discussions
Forums
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
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
тАО05-29-2004 10:38 PM
тАО05-29-2004 10:38 PM
Q: ProCurve 5038; Any pitfalls when moving from mesh to trunk/rstp/routing
Because our lan requires routing functionality we plan to change our 5 ProCurve 5038xl's from mesh to trunk (/w rstp) config. There are 4 vlan's configured on various ports, for which the routing is required.
Question: Are there any known pitfalls i can expect (apart from performance degrade by not having the mesh and recalculating the spanning tree)?
Cheers, Adri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2004 10:23 PM
тАО09-26-2004 10:23 PM
Re: Q: ProCurve 5038; Any pitfalls when moving from mesh to trunk/rstp/routing
area you have then routing, vlansupport and loadbalancing over all switches, with no stp need, also you can configure xrrp for failover
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-26-2004 11:56 PM
тАО09-26-2004 11:56 PM
Re: Q: ProCurve 5038; Any pitfalls when moving from mesh to trunk/rstp/routing
Cheers, Adri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-27-2004 10:48 PM
тАО09-27-2004 10:48 PM
Re: Q: ProCurve 5038; Any pitfalls when moving from mesh to trunk/rstp/routing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-28-2004 06:15 PM
тАО09-28-2004 06:15 PM
Re: Q: ProCurve 5038; Any pitfalls when moving from mesh to trunk/rstp/routing
2. Also if you have hubs or switches connected to ports of RSTP-running switches, you may want to set "Point-to-Point=Force-False" for these ports.
3. For any port that is connected to a bridge or switch that is known to be using STP (not RSTP), "MCheck" should be set to "No".
All these make RSTP work faster.