But this is always a mess, usually the storage vendor tells what driver/fw on server side are supported - at least that's what HPE is telling us over an over. So in the end it's trial and error. Using native VMware drivers is probably a good idea as VMware then also takes care of issues. Which is a problem if you use the async vendor drivers
Also keep in mind that sometimes the vendor updates the drivers in their custom ESXi images. For example we noticed that when we want to upgrade from 6.7 to 7 we shouldn't use the latest version of their ESXi image A06 because it contains a version of the lpfc driver that doesn't work. Using the A04 version works just fine.
Emulex Esxi Drivers
If the drivers are not in the update then you may have to download them and manually update the HBA. First you have to check the compatibility guide to see if it is compatible. Please see the kb's below.VMware Compatibility Guide - System SearchDetermining Network/Storage firmware and driver version in ESXi (1027206) (vmware.com)How to download and install async drivers in VMware ESXi (2005205)
It says that vmax os version and emulex driver need to be updated (12.8.542.25 or later).When I look through vmware compability, the latest driver for dell branded emulex cards is 12.8.511.0. When I check on Broadcom site, there are more up-to-date drivers for esxi 7. But which one should I choose to solve the problem?
This problem started to occur after the esx 7 update. We did not have such a problem when using 6.5. It does not always happen. We opened a case on the vmware and dell side about the problem. They examined it and said that there is no problem on the vmware or san switch side.They told us that the problem might be in the storage layer.I thought it might be because I couldn't find any information other than the link I sent you. The explanations in the link were the closest to our problem. I thought that the esx 7 version might be included in the explanation. Can't we use the newer drivers that the manufacturer has released for hba? Because vmware compatibility list is updating late.
Then I'm confused, because your link takes you to 12.8.511.0, but the link I sent and specifically the version I point out is for 12.8.542.25, which is what you stated above: "It says that vmax os version and emulex driver need to be updated (12.8.542.25 or later)."You dont want the 12.8.542.25 version? #iwork4Dell
The CIM is an open standard that defines how computing resources can be represented and managed. It enables a framework for agentless, standards-based monitoring of hardware resources for ESXi. This framework consists of a CIM object manager, often called a CIM broker, and a set of CIM providers. CIM providers are used as the mechanism to provide management access to device drivers and underlying hardware.
2- Upload the offline bundle ZIP file (VMW-ESX-5.0.0-emulex-cim-provider-3.6.12.1-01-offline_bundle-799300.zip) to any of the Datastore via Putty or vSphere Client Datastore browser, to an ESX/ESXi host.
/vmfs/volumes/50bd9d4d-adf00e08-78e9-002655e66551/emulex #/vmfs/volumes/50bd9d4d-adf00e08-78e9-002655e66551/emulex # esxcli software vib install -d /vmfs/volumes/50bd9d4d-adf00e08-78e9-002655e66551/emulex/VMW-ESX-5.0.0-emulex-cim-provider-3.6.12.1-01-offline_bundle-799300.zipInstallation ResultMessage: The update completed successfully, but the system needs to be rebooted for the changes to be effective.Reboot Required: trueVIBs Installed: Emulex-Corporation_bootbank_emulex-cim-provider_3.6.12.1-01VIBs Removed:VIBs Skipped:/vmfs/volumes/50bd9d4d-adf00e08-78e9-002655e66551/emulex #
IMPORTANT: If your source system contains the ESXi 7.0 Update 2 release (build number 17630552) or later builds with Intel drivers, before upgrading to ESXi 7.0 Update 3d, see the What's New section of the VMware vCenter Server 7.0 Update 3c Release Notes, because all content in the section is also applicable for vSphere 7.0 Update 3d. Also, see the related VMware knowledge base articles: 86447, 87258, and 87308.
In vSphere 7.0, VMKLinux driver compatibility has been deprecated and removed. vSphere 7.0 will not contain support for VMKLinux APIs and associated VMKLinux drivers. Custom ISO will not be able to have any VMKLinux async drivers. All drivers contained in an ISO must be native drivers. All currently supported devices which are not supported by native drivers will not function and will not be recognized during installation or upgrade. VCG will not show any devices not supported by a native driver as supported in vSphere 7.0.
In vSphere 7.0, 32-bit userworld support has been deprecated. Userworlds are the components of ESXi used by partners to provide drivers, plugins, and other system extensions (distributed as VIBs). Userworlds are not customer accessible.
The ESXi and esx-update bulletins are dependent on each other. Always include both in a single ESXi host patch baseline or include the rollup bulletin in the baseline to avoid failure during host patching. Updates the esx-dvfilter-generic-fastpath, vsanhealth, vdfs, vsan, esx-base, crx, native-misc-drivers, esx-xserver, gc, bmcal, esxio-combiner, trx and cpu-microcode VIBs to resolve the following issues:
After updating ESXi to 7.0 Update 3 or later, hosts might disconnect from vCenter Server and when you try to reconnect a host by using the vSphere Client, you see an error such as A general system error occurred: Timed out waiting for vpxa to start.. The VPXA service also fails to start when you use the command /etc/init.d/vpxa start. The issue affects environments with RAIDs that contain more than 15 physical devices. The lsuv2-lsiv2-drivers-plugin can manage up to 15 physical disks and RAIDs with more devices cause an overflow that prevents VPXA from starting.
If hardware support manager is unavailable for a cluster that you manage with a single image, where a firmware and drivers addon is selected and vSphere HA is enabled, the vSphere HA functionality is impacted. You may experience the following errors.
Mellanox ConnectX-4 or ConnectX-5 native ESXi drivers might exhibit less than 5 percent throughput degradation when DYN_RSS and GEN_RSS feature is turned on, which is unlikely to impact normal workloads.
When using the lsi_msgpt3, lsi_msgpt35 and lsi_mr3 controllers, there is a potential risk to see dump file lsuv2-lsi-drivers-plugin-util-zdump. There is an issue when exiting the storelib used in this plugin utility. There is no impact on ESXi operations, you can ignore the dump file.
esxist8 ## lspci grep -i -e net -e iscsi.... 00:04:00.0 Network controller: Emulex Corporation HP FlexFabric 10Gb 2-port 554FLB Adapter [vmnic0]... 00:04:00.1 Network controller: Emulex Corporation HP FlexFabric 10Gb 2-port 554FLB Adapter [vmnic1]... 00:04:00.2 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3).... 00:04:00.3 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3)... 00:21:00.0 Network controller: Emulex Corporation NC555m 10Gb 2-port FlexFabric Network Adapter [vmnic2]... 00:21:00.1 Network controller: Emulex Corporation NC555m 10Gb 2-port FlexFabric Network Adapter [vmnic3]... 00:21:00.2 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3)... 00:21:00.3 Mass storage controller: Emulex Corporation OneConnect 10Gb iSCSI Initiator (be3)
But, looking for drivers:.esxist7 ## ls /usr/lib/vmware/vmkmod/grep -i -e net -e ^be -e ... iscsi... be2net... iscsi_linux_92... iscsi_linux_9_2_0_0... iscsi_trans... iscsi_vmk... netsched... usbnet... vmkapi_v2_0_0_0_iscsi_shim... vmw_vaaip_netapp... vmxnet3.we don't see a be2iscsi or whatever it is now.
Then on the Vmware page, they have new drivers for the card for 5.0/5.1""VMware View > Drivers & Tools > VMware ESXi 5.0/5.1 Driver CD for Emulex OneConnect OCe10102 10GbE Adapter (Network Function)"""but *only* the network function.
You can deploy faster and manage less when you combine Host Bus Adapters (HBAs) and Virtual Fabric Adapters (VFAs) that are developed by Emulex. Lenovo HBAs and VFAs use the same installation and configuration process, streamlining the effort to get your system up and running, and saving you valuable time. They also use the same Fibre Channel drivers, reducing the time to qualify and manage storage connectivity. And with the Emulex HBA Manager (formerly named Emulex OneCommand Manager), you can manage Lenovo HBAs and VFAs that are developed by Emulex through the data center from a single console. 2ff7e9595c
Comments