- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect and VMware vSwitch question
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
02-29-2012 08:33 AM
02-29-2012 08:33 AM
Virtual Connect and VMware vSwitch question
Mike had a customer question:
***********************
I have the following from one of my customers. He’s using BL460/BL490 G6’s with VC Flex-10. Not sure of the current FW version. Any thoughts?
Question: When using the Virtual Connect is there a specific type of Load Balancing required on the VMware virtual switches? We are running ESX 4.1 with vmxnet3 drivers and standard virtual switches connecting through the HP Bladeframe to a physical Nexus 5k switch. I listed the 4 options below. We are currently running “Route based on the originating virtual port ID” which is not failing over properly.
1. Route based on the originating virtual port ID 2. Route based on IP hash 3. Route based on source MAC hash 4. Use explicit failover order.
*******************
From Dan:
********************
Those are load balancing choices and don't necessarily have anything to do with failover.
If they are configured for Active Active uplinks, make site they have Smart Link turned on for all networks that exit the chassis.
Virtual Connect does not support "Route based IP hash" load balancing, so your "route based on the originating virtual port ID" setting should be fine.
*****************
Other comments or questions?