OPERATIONAL DEFECT DATABASE
...
...
On an HPE Synergy Gen10 compute module with the HPE Synergy 3820c 10/20GbE CNA installed in Mezzanine Slot 3 and configured to legacy PXE boot to a VMware ESXi 6.x image and host profiles in vSphere Auto Deploy, when the HPE Synergy 3820c 10/20/25GbE Converged Network Adapter (CNA) is replaced with the HPE Synergy 4820c 10/20/25GbE and added back to the Synergy Frame (which has the server profile with Ethernet & FCoE network connections assigned) the server profile state will change to Profile Error.This occurs because a new Server Hardware Type is generated by HPE OneView for a unique Synergy Compute Module and HPE Synergy 4820c 10/25/50GbE CNA configuration. If the HPE OneView server profile is edited and applied to accommodate the new server hardware type using the auto port assignment option, the Ethernet connections after FCoE networks are assigned to Mezzanine port 3:1-d and port 3:2-d.The issue takes place because the HPE Synergy compute module will legacy BIOS PXE boot to vSphere Auto Deploy to load the VMware ESXi 6.x image and get the configuration from the host profile. The VMware ESXi 6.x host remediation fails because the host is not compatible with the existing host profile.The FCoE adapter device alias will bevmnic2andvmnic3,and thevmnic4andvmnic5are enumerated tovmnic128andvmnic129respectively. The qedf driver for QLogic FastLinQ 45xx GbE FCoE Controller directly binds to PCI function exposed by the CNA device. The qedf is not dependent on a network driver, therefore, no configuration is needed to initiate device discovery.There are no FCoE/physical networks (vmnic2andvmnic3) listed against the original configuration. The HPE Synergy compute module with the HPE Synergy 4820c 10/20/25GbE CNA is added to VMware vCenter Server Appliance 6.x, but it is not compatible with the existing host profile. Since the FCoE/Physical NICs (vmnic2&vmnic3) are missing andvmnic4andvmnic5are enumerated asvmnic128andvmnic129, the remediation fails and the FCoE adapter device alias will bevmnic2andvmnic3instead ofvmhbaXX&vmhbaXX.Find the vmnic listing and storage adapters below from the VM-Support logs:c:\<esxi host name>-<date--time>\commands\localcli_storage-core-adapter-list.txtc:\<esxi host name>-<date--time>\commands\localcli_storage-core-adapter-list.txt
Any HPE Synergy Gen10 Compute Module when replacing the HPE Synergy 3820C 10/20Gb CNA with the HPE Synergy 4820C 10/20/25Gb CNA in the conditions described above.
ImportantEvery unique combination of HPE Synergy server model and mezzanine configuration will have a different Server Hardware Type that starts at 1 and increments from there.Note the existing server hardware type and review the existing server profile configuration and note all configuration mappings so that they can be restored after the CNA is swapped. Once the server is added back in, note the new Server Hardware Type created, for example "SY 480 Gen10 6". The HPE OneView profile is re-applied with the new server hardware type.As a workaround if this issue is encountered, perform the following configuration steps:1. Take a backup of the host profile to be edited.2. Power off the HPE Synergy 480 Gen10 Compute Module, which has the HPE Synergy 4820c 10/20/25GbE CNA added.3. Edit the server profile to manually reassign the port 3:1-c to 3:1-d and 3:2-c to 3:2-d and apply the server profile.4. Customize the Host Profile to rename the Device Alias back to the original Device Alias.5. Login to vSphere Web Client, Navigate to Menu -> Policies and Profiles.6. Select the Host Profiles.7. Select the <Host Profile Name> from the list Host Profiles Name list.8. Click EDIT HOST PROFILE; the Edit host profile opens.9. Navigate to General System Settings -> Device Alias Configuration -> Device Alias Configuration.10. Select "Device Alias Configuration" with the following values:Bus type: logicalBus address: pci#s00000003.03#0Alias: vmnic3Rename the Alias "vmnic3" to "vmhbaXX" (Example: vmhba65)11. Delete the "Device Alias Configuration" with the following values:Bus type: logicalBus address: logical#logical#pci#s00000003.03#1#1#0Alias: vmhbaXX (Example: vmhba65)12. Select "Device Alias Configuration" with the following values:Bus type: logicalBus address: pci#s00000003.02#0Alias: vmnic2Rename the Alias "vmnic2" to "vmhbaXX" (Example: vmhba64)13. Delete the "Device Alias Configuration" with the following values:Bus type: logicalBus address: logical#logical#pci#s00000003.02#1#1#0Alias: vmhbaXX (Example: vmhba64)14. Navigate to Networking configuration -> Physical NIC configuration -> Physical NIC Configuration and deselect the following "Physical NIC Configuration" with the following values for Physical network adapter:Physical NIC to configure to vmnic2Physical NIC to configure to vmnic315. Navigate to Software FCoE Configuration-> Adapter Configuration -> Activation Profile.Deselect "Activation Profile" (3rd position)Deselect "Activation Profile" (4th position)Note: If no software FCoE configuration used, can deselect the Software FCoE Configuration at the top.RECEIVE PROACTIVE UPDATES: Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL:Proactive Updates Subscription Form.NAVIGATION TIP: For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for HPE systems and Options, refer to theNavigation Tips document.SEARCH TIP: For hints on locating similar documents on HPE.com, refer to theSearch Tips Document.
Operating Systems Affected:VMware vSphere 6.5, VMware vSphere 6.7
No external links available for this bug
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
