- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- C7000 & Flex-10 - traffic between blades leaving c...
BladeSystem - General
1753917
Members
7780
Online
108810
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
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
12-09-2009 08:00 AM
12-09-2009 08:00 AM
C7000 & Flex-10 - traffic between blades leaving chassis
I have a c7000 chassis with flex-10 modules in Bay 1 and 2. I am using 4x 1Gb uplinks from each flex-10 module (ESX 4).
This means in the active/active config, I have 2 shared uplink sets (one per flex-10 module), each with 4 physical links. However, I have noticed that some inter-blade traffic is leaving the chassis to cross flex-10 modules.
In the instance of a file copy between blades - if the "source" and "destinations" servers happen to appear of the same flex-10 module, then no traffic leaves the chassis. However, if the "source" and "destination" servers happen to appear on different flex-10 modules then rather than the traffic crossing the flex-10 interconnect, the traffic goes out the chassis on one uplink set and re-enters the chassis on the other uplink set (wasting bandwidth back to the core switches).
Ideally, any inter-blade traffic should stay within the chassis. If I create a single SUS across BOTH flex-10 modules, then traffic IS routed across the flex-10 interconnect and NO traffic between blades leaves the enclosure. However, by creating 1 SUS across both flex-10 modules and leaving the connect type as "auto" - only 4 uplinks (from one flex-10 module) are active and the other 4 uplinks (from the other flex-10 module) are in stand-by.
How do I have all 8 uplinks active - but ensure no traffic between blades leaves the enclosure ? The situation described above seems inefficient. I am finding the flex-10 cookbook is not helping as it does not address the issue of traffic not using the flex-10 interconnect.
Has anyone else noticed this ?
This means in the active/active config, I have 2 shared uplink sets (one per flex-10 module), each with 4 physical links. However, I have noticed that some inter-blade traffic is leaving the chassis to cross flex-10 modules.
In the instance of a file copy between blades - if the "source" and "destinations" servers happen to appear of the same flex-10 module, then no traffic leaves the chassis. However, if the "source" and "destination" servers happen to appear on different flex-10 modules then rather than the traffic crossing the flex-10 interconnect, the traffic goes out the chassis on one uplink set and re-enters the chassis on the other uplink set (wasting bandwidth back to the core switches).
Ideally, any inter-blade traffic should stay within the chassis. If I create a single SUS across BOTH flex-10 modules, then traffic IS routed across the flex-10 interconnect and NO traffic between blades leaves the enclosure. However, by creating 1 SUS across both flex-10 modules and leaving the connect type as "auto" - only 4 uplinks (from one flex-10 module) are active and the other 4 uplinks (from the other flex-10 module) are in stand-by.
How do I have all 8 uplinks active - but ensure no traffic between blades leaves the enclosure ? The situation described above seems inefficient. I am finding the flex-10 cookbook is not helping as it does not address the issue of traffic not using the flex-10 interconnect.
Has anyone else noticed this ?
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