Hi All,
Have 3 no of IBM x3850 X5 Server with Emulex oneconect 10gb (be3). All are running with ESXi 5.1 version.
In first two Hosts, I can see the Emulex oneconect 10 GB ports under network adapter section but for third and last, I am unable to any Emulex 10 GB ports in vsphere network adapter. However, I can see it under PCI Hardware sensors.
Any guess, why Emulex is not visible for third host under network adapter.
Thanks in Advance.
Can anyone suggest on this ?
Hi,
First you need to identify if they are running and also if Drivers and Firmware are updated to the ESXi version.
Check if the cards are present: https://kb.vmware.com/kb/1002413
Also you can get more information with this: https://kb.vmware.com/kb/1027206
Here you can find latest drivers for 5.1: Index of /hpe/apr2016/esxi-510-drv-vibs/lpfc
Try this then provide feedback.
Hope this can help.
Hi Again
Also try to update the device
Hi,
I found that the third server is having the lower IBM UEFI firmware version than those two servers, which are working ok. Do you think, if this lower UEFI version can cause this Emulex adapter discovery issue in vSphere ?
Regards,
It looks like your Network Card is there but it is not being loaded. Take a look on the vmkernel.log and hostd.log to check if the driver presents any type of error when loading. Those errors might be caused by a deprecated EFI/driver as you suspect.
Also use this KB where you find information to make sure it is not a hardware problem and better identify the cause.
Hi
Drivers should always be updated with Servers BIOS, Firmware etc.
So yes it could be that old firmware and up to date drivers are not compatible and because of that Card is not working. It can happen is not the case, but it could be. So to bypass that, updated all.
So always update firmware, drivers even Card firmware.
Check if you have NIC connected physically.
Check if compatible drivers are installed.
Check if Firmware version is installed as compatible to drivers.
If it's not physical NIC issue, then sure it would be Firmware and Driver mismatch issue.
Try to flush existing firmware and driver and reinstall as per compatible guide.
Hi All,
Thanks for your reply.
I have tried by upgrading the problematic host's uEFI BIOS version and driver version for this Emulex card but did not worked, still Emulex is not detecting on the vSphere Console. However, I could see both the Emulex ports as nic6 and nic7 in the below command,
~ # lspci -v | grep -A1 -i Ethernet
Any other troubleshooting steps ?
Regards,
Hi
This is the KB how to check drivers and also firmware version
https://kb.vmware.com/kb/1027206
But you can download the VIB for emulex that I have added above and installed. If is installed when installing it will say he did installed(and remove the old ones).
How to install VIBs
VMware KB: Installing patches on an ESXi 5.x/6.x host from the command line
PS: Take attention that you always need to give full path in the command, even you are inside of the folder where the files are located.
Hi,
As you correctly mentioned, when I upgraded the Emulex drive VIB file, I got the same message like, VIB Installed and VIB Removed.
it is still not listed under esxcfg-nics -l. I went through this link without any luck VMware KB: Network cards not detected on an ESXi/ESX host
Thanks,
Hi All,
Finally, I tried by re-installing ESXi 5.1 but still it is not detecting It is detecting under lspci -v | grep -A1 -i Ethernet but not detecting under esxcfg-nics -l
I see below logs related to be2net and vmnic6 (Emulex nic) in /var/log/vmkernel.log). Does this help to identify the root cause ?
=========================================================================================
2016-05-25T13:22:01.814Z cpu8:17002)skb_mem_info mempool for module be2net created - max size 23068672
2016-05-25T13:22:09.556Z cpu8:17002)PCI: driver be2net claimed 0 device
2016-05-25T13:22:03.786Z cpu8:17002)WARNING: LinNet: GetNICSupportedModes:7371:No supported speed/duplex found in vmnic6, mas
<6>bnx2 0000:04:00.0: vmnic0: NIC Copper Link is Up, 1000 Mbps full duplex2016-05-25T13:22:03.833Z cpu32:16416)<c>
cpu8:17002)Disabling MSIX for dev 0000:18:00.1
2016-05-25T13:22:01.814Z cpu8:17002)skb_mem_info mempool for module be2net created - max size 23068672
2016-05-25T13:22:01.814Z cpu8:17002)module heap: using memType 0
2016-05-25T13:22:01.814Z cpu8:17002)module heap vmklnx_be2net: creation succeeded. id = 0x410027400000
2016-05-25T13:22:01.814Z cpu8:17002)PCI: driver be2net is looking for devices
2016-05-25T13:22:09.556Z cpu8:17002)LinPCI: LinuxPCI_DeviceUnclaimed:147: Device 0000:18:01 unclaimed.
2016-05-25T13:22:09.556Z cpu8:17002)PCI: driver be2net claimed 0 device
2016-05-25T13:22:09.556Z cpu8:17002)Mod: 4485: Initialization of be2net succeeded with module ID 24.
2016-05-25T13:22:09.556Z cpu8:17002)be2net loaded successfully.
2016-05-25T13:22:09.556Z cpu8:17002)LinPCI: LinuxPCI_DeviceUnclaimed:147: Device 0000:18:01 unclaimed.
2016-05-25T13:22:09.556Z cpu8:17002)PCI: driver be2net claimed 0 device
2016-05-25T13:22:03.786Z cpu8:17002)VMK_PCI: 706: Device 00:18:00.0 name: vmnic6
2016-05-25T13:22:03.786Z cpu8:17002)WARNING: LinNet: GetNICSupportedModes:7371:No supported speed/duplex found in vmnic6, mas
<6>bnx2 0000:04:00.0: vmnic0: NIC Copper Link is Up, 1000 Mbps full duplex2016-05-25T13:22:03.833Z cpu32:16416)<c>
===============================================================================================
Regards,
Hi All,
We have tried by replaced the Emulex 10 GB card as well but still it is not detecting in VMware adapters.
Any thought on this ?
Thanks
Hi,
First I recommend that you get rid of that 5.1. You should upgrade that to the latest version, or at least 5.5.
ESXi 5.1 End of General Support or End of Technical Guidance will end in next August.
https://www.vmware.com/files/pdf/support/Product-Lifecycle-Matrix.pdf
https://www.vmware.com/support/policies/enterprise-infrastructure/faq
Second, have you check if you have the proper drivers those NICs?? Or did you check if they are compatible with 5.1?
Hi,
We have other server with same make/model and card on ESXi 5.1 and those are working fine. also tried with upgrading the drivers but it did not worked.