- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- VSA for Hyper-V 2012 nic teaming
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
Discussions
Forums
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
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
тАО04-12-2013 07:16 AM
тАО04-12-2013 07:16 AM
VSA for Hyper-V 2012 nic teaming
What is the best practice for VSA for Hyper-V 2012 NIC teaming? Should we use Address Hash or Hyper-V Port load balancing mode? I didn't find any documentation about this, is there any?
- Tags:
- Hyper-V
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2013 10:12 AM
тАО04-12-2013 10:12 AM
Re: VSA for Hyper-V 2012 nic teaming
Your physical switch configuration will be the deciding factor in this case. Are you using etherchannel or LACP? Unless you have 10Gb ethernet available, you likely want to use some form of link aggregagtion. The Hyper-V port load-balancing will place all of your VSA traffic on one physical NIC. If you plan your IP scheme correctly, IP hash allows a VM to use multiple NICs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-12-2013 11:27 AM
тАО04-12-2013 11:27 AM
Re: VSA for Hyper-V 2012 nic teaming
5y,
the two options the OP listed are both switch independent options so I think he's ruling out the LCAP option. Given that assumption, I don't know which is better for running VSAs, but I do think this is something that should be in a document from HP given 2012 is now supported.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-13-2013 05:54 AM
тАО04-13-2013 05:54 AM
Re: VSA for Hyper-V 2012 nic teaming
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-15-2013 06:32 AM
тАО04-15-2013 06:32 AM
Re: VSA for Hyper-V 2012 nic teaming
According to the windows2012 Team management interface, There are two "Switch Independent" Team modes: Hyper-V Port and Address Hash. I blieve the Hash is pretty much ALB and Hyper-V Port is similar to Adapter Fault Tolerance.