A couple days ago I faced a problem with HP Virtual Connect and vSphere configuration. My HPVC are configurated with „Mapped Mode” and Legacy Mode. In that configuration I can only set 28 VLANs per one HPVC NIC. A problem was that I had to have more than 30 VLANs on my production cluster with vDS.
My first idea was to set Expanded VLAN Capacity on HPVC and increase VLANs capacity from 28 to 162. I didn’t use this solution because no one could tell me how this change will affect to the other running blade servers. So I decided to add two new NICs with new VLANs and connect them to vDS as a new two active uplinks.
IMO this solution should work fine, without problems. Unfortunately, I was wrong.
In that configuration I was strange problems with new VLANs on VMs. Some VLANs were working fine and some were not. So I started to do some tests.
For eg. I mapped management vlan (vmkernel) on 1 and 2 NIC – everything worked fine. When I mapped mgmt vlan only on 1st or 2nd NIC then vSphere Host went down in vCenter…. When I put new VLAN 100 on 3rd and 4th NIC everything was ok, on only 3rd NIC was ok, on only 4th NIC VLAN 100 was unreachable.
After that I came to the conclusion that is something with failover and loadbalance.
On ever port group we can edit „Failover and Load Balancing” and set „Failover Detection”, default is „Link Status only”.
As we can read on VMWare pubs a „Link Status only” is a simple method of failures detection. A second option is „Beacon Probing” which is more advance. So i choosed it.
Since then everything works fine, no matters on which NIC VLAN is..
So if you have a problems with network on vSphere and Virtual Connect try to set Beacon Probing as a method of failover detection.