HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
Showing results for 
Search instead for 
Did you mean: 

Virtual Connect 4.10 - VMware 5.5 U1 Network Failover Problem

Frequent Advisor

Virtual Connect 4.10 - VMware 5.5 U1 Network Failover Problem



yesterday i installed following System for my customer:



- 1x c7000 Blade Enclosure

- 2x HP Flex-10/10D VC Modules

- HP BL460c Gen8 with FlexFabric 10GB 2-Port Adapter

- 2x HP 5920 10GB Switches in an IRF Stack



- OA: 4.11

- VC: 4.10

- HP BL460c Gen8 Server is up-to-date (bootet with actual Proliant Service Pack DVD)


Configuration (Virtual Connect Active/Active):

- 20GB/s LACP Trunk configured on VC Modul in Bay 1 (SUS with Name "SUS-Bay1")

- 20GB/s LACP Trunk configured on VC Modul in Bay 2 (SUS with Name "SUS-Bay2")

- One LACP Trunk configured on the IRF Switch for Bay 1 and one for Bay 2

- SmartLink is activated for each Network


Server Profile:

- Port 1 configured with Network on "SUS-Bay1"

- Port 2 configured with Network on "SUS-Bay2"


Configuration (VMware ESXi 5.5 U1):

The ESXi Host has configured one vSwitch (vSwitch0) with "vmnic0" and "vmnic1". Management Network is on that vSwitch and uses "vmnic0" as Active Adapter and "vmnic1" as Standby Adapter. In the Network Settings in leaved everything on default Settings.

Please see attached Screenshot.



After installing the c7000, VC and one VMware ESXi Host i wanted to try some Failover Scenarios. So i disconnected all FC Cables from VC Modul in Bay 1 and pinged the Management IP from the ESXi Host at the same time. "vmnic0" was disconnected and i was loosing one ping. Thats fine. Management now on "vmnic1".

After that, i reconnected the FC Cables back to VC Bay1. Now, i was loosing round about 6-7 Pings (about 30 Seconds).


I (and my customer) were a little shocked because 30 Seconds can be really long...

On other VMware Installations this "failover" should generate maybe one lost of ping, not more.


So i need some help how to solve this issue. Anyone with the same configuration? Any Tips?


Many Thanks!

Best Regards







Frequent Advisor

Re: Virtual Connect 4.10 - VMware 5.5 U1 Network Failover Problem



i found a possible Solution for this by myself.

I have to enable STP on the DAG (LACP Trunk) with following command:

stp edge-port enable


I will try it an will give an feedback to this.