vNICs for Live Migration and Heartbeat

[Hythim Ali El Hadad]

Hi,

I have created 1-vNIC for Live Migration and another vNIC for heartbeat for Hyper-V installation on B200M3 and B200M4 with 2 adapters

these vNICs are enabled failover

When I check VIF path, I found they are created on path A1 and B1 not like other vNICs and vHBAs that is created on A1 and B2

So when adapter 1 fail, path A1 and B1 will come down which will stop Live Migration and Heartbeat traffic

Is there a better way for deploying these 2 vNICs noting that they only provide L2 connectivity between blades

Thanks

[Walter Dey]

Hi

If I understand you correctly, you have 2 adaptors on the blade ?

This means, in your service profile you have vcon0 and vcon1.

Just use manual vnic/vhba placement in your SP ! connecting vnic0 to vcon0 and vnic1 to vcon1.

If this is W2012, I would not use hardware failover, but let the OS do HA; you would just create 2 vnics (connected to fabric A and B) for live migration resp. heartbeat, and configure teaming on the OS.

Walter.

[Hythim Ali El Hadad]

Thanks Walter

So is it normal to do nic teaming on OS for vmotion ports

Thanks