- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Link Aggregation Control Protocol (LACP) not suppo...
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
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
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-24-2011 10:10 AM
05-24-2011 10:10 AM
Link Aggregation Control Protocol (LACP) not supported in downstream server nics?
Ramon had a customer quesiton on LACP:
**********************
Hi,
Anyone who can help with a customer query below:
*********************************************************************************************************************************
Can you advise on the following excerpts I found on “HP Virtual Connect for the Cisco Network Administrator”:
-Virtual Connect supports NIC Teaming (or NIC bonding) on server NIC ports. For Windows on
x86, VC supports Network Fault Tolerance (NFT) and Transmit Load Balancing (TLB) but does not
support Switch-assisted Load Balancing (SLB). For Windows on Integrity, VC supports Network
Fault Tolerance (NFT), Transmit Load Balancing (TLB), and static Dual Channel with only two
NIC ports in the team, but does not support Switch-assisted Load Balancing (SLB). For Linux, VC
supports any NIC bonding type that does not require 802.3ad (static or dynamic using LACP) on
the server NIC ports.
-Virtual Connect does not support EtherChannel\802.3ad on the downlinks to server
NIC ports.
So what’s the point of having LACP on the Shared Uplink Sets and on the Cisco Switch?
*********************
Lee replied:
******************
Ramon,
LACP on the upstream ports gives you the ability to put multiple ports into a single logical pipe so you can aggregate the bandwidth. Once you create a SUS on both modules and create A-side and B-side networks on the modules, you can assign those networks to the blades and have an active/active configuration. The point of having LACP in the VC module is to have the ability to create LACP bonds to the upstream switch, which gives the benefits of additional redundancy if one of the ports in that trunk goes down.
Your customer may be used to creating a LAG from the upstream switch to the individual NIC on a rack server. This is all done with switch protocols and NIC drivers; Since VC is in the mix, the LAG will not work the same way due to various technical reasons. That’s why we almost always recommend a TLB/FT NIC team with an active/active VC configuration.
*********************
Any other comments for Ramon?