vCentre sends out an alert that the a vmnic is offline but it is not

[KBRGeek]

I have recently upgraded our ESXi 5.1 host to 10Gb nics, enabled IP Hash to match the ether channel configuration on the Nexus switch its connected to and configured the vmkernel to see one of the two adapter (vmnic5) where the management network only sees vmnic 0. The vswitch has both vmnic 0 and vmnic 5 as active.

For some reason vCentre is reporting vmnic 5 as being down/offline but it is not and there switch that it is patched into has no reports of the link being down.

Has anyone see this problem before?

[dhanarajramesh]

when you set Route based on IP hash, you  must at least have >= 2 active/active . so check all port group and vswitch NIC team is in active active.  the  please attache the configuration images.we can see what goes wrong.

[KBRGeek]

That is how it is already configured.

Both adapters are set to active with "IP hash" enable for load balancing.

vSwitch configuration

vmkernel

Management network

[dhanarajramesh]

in Vmkernel , management network, instead of unused Adapter,  please make changes all these two adapters to active active and try

[KBRGeek]

Sorry but I disagree with you as that change with drop the server offline completely. Confirmed by VMware

[mdangel1]

I have mine set both to active/active and I have no issues. Take a look

[KBRGeek]

Thanks but why did you override your settings and not inherit them from the switch? Also your network does not appear to have any Vlans assigned, which will make your environment completely different to mine.

Thanks for the reply though

[dhanarajramesh]

because below info are per-request and limitation of ether channel and IP hash Load balancing configuration   1) Switching infrastructure mush support static Etherchannel or static 802.3ad link aggregation and this must be configured for each hosts uplinks.   2)  To enable network switch redundancy the network switches must support stacking or functionality similar to Virtual Port Channel.   3)  Can’t use beacon probing.   4)  Can’t configure standby or unused uplinks.   5) Only support one Etherchannel per vNetwork Distributed Switch (vDS).   6)  vSwitch can be configured with between 1 and 8 uplinks.   7) To get effective load balancing requires many source/destination combinations.