- Community Home
- >
- Servers and Operating Systems
- >
- BladeSystem
- >
- BladeSystem Server Blades
- >
- Which NIC teaming to use in Server 2012 on the new...
-
- 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
04-11-2014 09:13 AM
04-11-2014 09:13 AM
Which NIC teaming to use in Server 2012 on the new HP enclosures?
Denny had a NIC teaming question:
***************
My customer has used Transmit Load Balancing on legacy windows servers and is now moving to Server 2012 and are looking for recommendations on what WS 2012 is comparable. What might you suggest?
They are trying to come up with a standard for NIC teaming on Server 2012 on BL460c Gen8 enclosures. They want to use "transmit load balancing" TLB, but do not know what that means in the Microsoft terminology.
Their choices are:
Teaming mode: Static Teaming
Load balancing mode: Address Hash
Hyper-V Port
Dynamic
or
Teaming mode: Switch Independent
Load balancing mode: Address Hash
Hyper-V Port
Dynamic
LACP is not supported.
Thanks for your feedback.
**************
Input from Chad:
*************
Switch Independent - Address Hash, which is the default. If they are using Hyper-V servers, then Hyper-V Port is the current recommendation
*************
Comment from Aric:
************
A very good paper on this is available here: http://www.microsoft.com/en-us/download/details.aspx?id=40319
Switch Independent/Address Hash is most closely aligned to TLB. As to this being the best choice for the customer should be questioned and determined based on the use of the host. (Hyper-V virtual switches in use?)
Note that Dynamic is an option you only get with Windows Server 2012 R2.
************
Other questions?
- Tags:
- NIC
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP