- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Re: stp priority vs cost
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
06-27-2011 05:34 AM
06-27-2011 05:34 AM
stp priority vs cost
Need some help with stp config,
i have two sites (1 prod, 1 dev) set up stretched layer 2 with an ATT gigaman because of nonroutable iscsi traffic. We have a new vdi project that started last week and have this traffic at our prod site going to a solid state san. I noticed the iscsi traffic flow is going to both sites across the gigman and causing latency to the san. It should be staying local to prod site, even local to the same switch and passing right to the san.
The STP config that was set up here has the main core switch as root and the main switch across the gigaman at the dev site as the next lowest priority and then back across the gigman to core switch 2 and then back across again and so on between 4 core 6600s. If this traffic is on the same vlan (ISCSI traffic from VDI esx host to san) could it still be being sent across the gigaman because of stp priority? I checked everything else and the proper ports are being blocked and the host and virtual connect that the host connects to are all configured correctly. this switch priority is the only thing i can see that might force it across the gigaman. And of course it cant be default gateways or anything right? because iscsi doesnt route. Thanks for the input.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2011 10:19 AM
06-27-2011 10:19 AM
Re: stp priority vs cost
iSCSI runs over TCP, so should route fine; maybe you're thinking of FCoE.
Is the traffic from the production site going both ways over the WAN link? If so, that's a routing problem for sure.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-28-2011 07:15 PM
06-28-2011 07:15 PM
Re: stp priority vs cost
Richard is absolutely right about iSCSI - it is fully routable - but if you're running a stretched L2 segment over your gigaman, then routing is not likely to be the issue.
I'm not sure what the best practice recommendation is, but i can't think of a reason why you would want to alternate your STP priorities across sites. If your central site is connected to your remote site via a single logical L2 link, then it shouldn't make much difference.
If you can post your configs and perhaps a topology diagram, we might be able to make more sense of it.
Paul