My project team installed vCenter 6.0 U3 and ESXi 6.0U3 on a cluster of new UCSC-C220-M5SX stand-alone servers, 4 in the cluster, back in Feb. About 5 months later, we are seeing Received Packet Drops on the NICs of the hosts and VMware support says that the firmware on the MLOM card is too high (V4.2(3)) for the ESXi driver, pointing us to this compatibility matrix:
https://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=42983&vcl=true
It says that for a Cisco UCS VIC1387 MLOM card, running VMware V6.0.0 U3, the firmware on the card must not exceed 4.0(1j). VMware said that we need VMware ESXi 6.5 minimum to stop the packet drops so that the MLOM card firmware matches the ESXi driver.
My question is, in the matrix, it lists a few different driver versions for device drivers- so how do I ensure I get the "nenic version 1.0.26.0"? I noticed that when you click the :smileyplus: next to the version number, it says to download the driver from HTTP://.................... is that it? My problem should then be solved?
you want to see which enic driver is there ?
esxcli software vib list | grep enic
esxcli software vib list grep | gb
https://kb.vmware.com/s/article/1034674
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
you want to see which enic driver is there ?
esxcli software vib list | grep enic
esxcli software vib list grep | gb
https://kb.vmware.com/s/article/1034674
---------------------------------------------------------------------------------------------------------
Was it helpful? Let us know by completing this short survey here.
So once I've established the driver type/version, I can then compare it to the matrix above to see if it is supported by the VIC firmware, and if not, I just install the driver listed in the matrix and that's it?
Hello,
Hope you are doing well.
Rajiv Sir have given you the right commands to check the version installed.
You have to check with VMware HCL and UCS for correct version to install on the host to get rid of this issue.