- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem Virtual Connect
- >
- IEEE 802.3AD with IP HASH question with Virtual Co...
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-15-2012 09:16 AM
02-15-2012 09:16 AM
IEEE 802.3AD with IP HASH question with Virtual Connect Flex-10
Charlie has a customer question:
****************
I have a question from a customer hoping someone can assist?
According to HP’s documentation, 802.3ad is not supported in the context
Here is the reference document from HP:
http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA2-9642ENW.pdf
On Page 24 – read the table – “IP Hash” with 802.3ad is not supported on Flex-10.
802.3ad is “generically” supported for link aggregation across uplinks in the same module … not across modules. (I just triple-checked the cookbook on this too to make sure I am not missing anything)
2 issues are
a) the lack of VMWare support for IP hash,
b) the lack of ability to aggregate with 802.3ad across modules
*******************
Info from Chris:
******************
This is on the downlink ports only, not uplink ports. To support 802.1ad/.3ad on the downlink ports would require a significant development effort to support multi-device LACP.
802.1ad/.3ad is fully supported on the uplinks, but only from the same physical Virtual Connect Ethernet module.
*************
And from Dave:
******************
On the uplink ports, we support H3C’s IRF(Intelligent Resilient Framework) and Cisco’s vPC(virtual Port Channel).
As Chris said the document is referring to the downlinks.
Virtual Connect is a layer two device, but it is not a switch in the technical terms. It is more a port aggregator.
As the document says, ‘Requires switch assisted load balancing, 802.3ad.”, VC is not a switch.
******************
Comments? Questions?
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP