What's the exact network adapter type/model in the blade?
Broadcom Corporation QLogic 57840 10 Gigabit Ethernet Adapter
(as per Web Client)
Bus Info: 0000:06:00.0
Firmware Version: bc 7.15.24
(as per esxcli network nic get -n vmnic0)
net-bnx2x 2.713.30.v60.9-1OEM.600.0.0.2494585 QLogic VMwareCertified 2018-05-29
(as per esxcli software vib list)
From what I saw by comparing the HPE custom images, HPE replaced the QLogic drivers with the Feb-2018 release.
However, I'm not really sure whether this is the root cause in this case. What confuses me is the MAC address you've posted. It's looks like a locally administered address rather than a vendor address. Do the other blade servers show similar MAC addresses, where bit 2 in the first octet is "1".?
You can ignore the mac address. It is assigned virtually from a range of MACs through HP OneView
I suspecting firmware and currently upgrading the C7000 Interconnects and the firmware on the OAs. I'll try to ESXi upgrade again and return when done.
When using a Virtual Connect (VC) domain running Virtual Connect Firmware Version 4.60 or 4.61, following a reset, reboot or power-cycle of a server blade or VC Module, the Stacking Link(s) between VC Modules either within a single enclosure or across multiple enclosures may be lost and/or Uplink(s) may not form a LACP Group, resulting in a network outage. Additionally, latency may be seen in FCoE Traffic.
This occurs due to an issue found in the control traffic handler within Virtual Connect Modules.
No. No change. Same message.
What log am I supposed to look into anyway? And how do I solve this problem?
When I upgraded from 6.0 to 6.5 these Qlogic VIB was in HP bulletins xml file:
Now, in 6.5 to 6.5 Update 1 only this one is present:
and no bnx2 nor any bnx2x
Ideas are welcome.
This leads me HPE Support document - HPE Support Center
to a HPE Custom Image for VMware ESXi 6.5 U1 Install CD from 2018-02-09 which does NOT contain the drivers.
Further below I can see a Pre-Gen9 Custom Image which does contain those drivers but the Host is a HP ProLiant BL460c Gen9 not a pre-Gen9
It looks like I should have been lead to a HPE Customized ESXi Image vSphere 6.5 U1 OCt 2017 but I get to one from 2018.
It's currently not easy to follow HPE with all of their different images (PereGen9, Gen9+), and driver versions within these images.
The October 2017 image still came with the BNX2X drivers, which have been replaced with the QLFE3 drivers in the current images.
The VMware driver page as well as HPE's vibsdepot already contain updated QLEF3 drivers (QLG-qcnic-ESXi6.5-8484591.zip). Although there's nothing specific regarding your issue in the release notes, it may be worth a try to create a custom image using the new drivers, because all newer images come with the QLEF3 driver package.
Ok. How would you suggest I create a custom image? Somehow register which VIB are installed today and compare with whats on the new one, manually adding those that are not present, keeping those that are replacing other or ?
I haven't done this before.
There are several ways to create a custom image. With vCenter Server in place it you can use the integrated Image Builder to do this. An example can be found at https://docs.vmware.com/en/VMware-Validated-Design/4.0/com.vmware.vvd.sddc-upgrade.doc/GUID-9248EB76-2612-4649-8035-61C4F16E5A58.html.
Simply replace the bundles mentioned in the example with the HPE Offline Bundle (VMware-ESXi-6.5.0-Update1-7388607-HPE-650.U184.108.40.206.23-Feb2018-depot.zip), and the driver package that I've mentioned before (please note that the driver download comes as a .zip archive, which contains several files, including the driver package itself).
Alternatively you can use Image Builder from the command line (requires VMware.PowerCLI to be installed).
Still on 6.5 and I maintenance mode:
Just lost contact to all Datastores on SAN after
esxcli system module set --enabled=true --module=qflge
esxcli system module set --enabled=true --module=qfle3
esxcli system module set --enabled=false --module=qflge
esxcli system module set --enabled=false --module=qfle3
Ok, I got access to the datastores back.
Enabling the native drivers is not the way forward and I suppose replacing the BNX2X drivers with QLEF3 drivers from the zip is also no-no or what do you think André?