Oneview for vCenter: from Basline to VLCM

[erki72]

I would like to have it explained to me. I'm sorry if I'm too stupid to understand that..

HPE Customization for HPE Servers 703.0.0.11.1.0-25 > cant save


HPE Customization for HPE Servers 703.0.0.10.10.0-12 > Host not compatible with the image



HPE Customization for HPE Servers 703.0.0.10.9.1-5 > Host not compatible with the image (is way too far behind in my opinion anyway)


If I'm really that difficult to understand, I would be grateful if you could mark the screenshot where I can adjust something

[PatrickLong]

What is the ACTUAL FC HBA hardware model installed in your hosts? At least SOME of the confusion results from the fact that some of those QLogic FC chipsets were acquired by Marvell -and it gets even more murky when dealing with CNA adapters.  If it is anything from the QLogic chipset lineage you can get some detailed info by issuing the below command:

/usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -a
Listing all system keys:
Key Value Instance: vmhba1/qlogic
Listing keys:
Name: ADAPTER
Type: string
value:
HPE SN1100Q 16Gb 2p FC HBA for SN1100Q:
FC Firmware Version: 9.09.00 (d0d5), Driver version 5.3.2.0

<followed by all the information you'd ever want to know about this hba and driver parameters>

Getting the driver vendor and version details via esxcli requires knowing either the vib name (in this case qlnativefc) or the three character case-sensitive vendor code (MVL):

esxcli software vib list |grep MVL
qlnativefc 5.3.2.0-1OEM.703.0.0.18644231 MVL VMwareCertified 2022-12-20

Maybe not so helpful to your immediate issue, but good commands to tuck away for future use.

[erki72]

Listing all system keys:
Key Value Instance: vmnic3/QLogic
Listing keys:
Name: rxrs
Type: integer
value: 64
Name: txrs
Type: integer
value: 64
Name: noq
Type: integer
value: 18446744073709551615
Name: dll
Type: integer
value: 0
Name: hwvlan
Type: integer
value: 1
Name: tpa
Type: integer
value: 1
Name: led
Type: integer
value: 2
Key Value Instance: vmnic2/QLogic
Listing keys:
Name: rxrs
Type: integer
value: 64
Name: txrs
Type: integer
value: 64
Name: noq
Type: integer
value: 18446744073709551615
Name: dll
Type: integer
value: 0
Name: hwvlan
Type: integer
value: 1
Name: tpa
Type: integer
value: 1
Name: led
Type: integer
value: 2
Key Value Instance: vmnic1/QLogic
Listing keys:
Name: rxrs
Type: integer
value: 64
Name: txrs
Type: integer
value: 64
Name: noq
Type: integer
value: 18446744073709551615
Name: dll
Type: integer
value: 0
Name: hwvlan
Type: integer
value: 1
Name: tpa
Type: integer
value: 1
Name: led
Type: integer
value: 2
Key Value Instance: vmnic0/QLogic
Listing keys:
Name: rxrs
Type: integer
value: 64
Name: txrs
Type: integer
value: 64
Name: noq
Type: integer
value: 18446744073709551615
Name: dll
Type: integer
value: 0
Name: hwvlan
Type: integer
value: 1
Name: tpa
Type: integer
value: 1
Name: led
Type: integer
value: 2

[:~] esxcli software vib list |grep MVL
qlnativefc 5.1.68.0-1OEM.703.0.0.18644231 MVL VMwareCertified 2022-10-31
[:~]

[pirx]

The MRVL package is also puzzling me. The HPE Upgrade Component is simply broken, the right package version would be 1.4.1 - that's what is installed with latest HPE ESXi ISO images and is in the HPE recipie. But... the 900 version is part of VMware's Non-Critical default baseline (but the package is from HPE). So if you patch your server with good old patch baseline incl non critical patches, the 900 version will be installed. And all other versions of upgrade component will be outdated. 

So if you still have 1.4.1 installed, overwrite version 900 with 1.4.1 in add component section, so that it never installes that forsaken version. But if you already have replaced 1.4.1 with 900 and get now the warning that you cannnot downgrade from 900... than replace whatever should be installed with version 900. Or unistall 900 manually and replace it with 1.4.1.  I've no idea what this component is used for and what the difference between the versions is. And HPE problably doesn't too, as I've opened a case for this and did not get any feedback yet.

This is all completely broken. And never try to setup image based backup with a mixed vendor cluster...

hpe-upgrade-component--1.4.1-1 and 900.0.2-1 - whe... - Hewlett Packard Enterprise Community

[erki72]

Yes, hpe-upgrade 900.0.2-1OEM.700.1.0.15843807 HPE PartnerSupported 2022-11-24 is installed on the Hosts.

But now it's getting exciting. I can't uninstall the part on all hosts at the same time. I try to save on one and then the image...

[T_1_6]

Hosts in this cluster are managed collectively. This image below will be applied to all hosts in this cluster.

ESXi Version 7.0 U3i - 20842708

Vendor Addon  HPE Customization for HPE Servers 703.0.0.10.10.0-12

Firmware and Drivers Addon  Gen10 Service Pack for ProLiant SPP-2022.09.01.00.703

Components  No additional components Show details

Works for me.

[pirx]

You installed your hosts with lasted ISO VMware-ESXi-7.0.3-20842708-HPE-703.0.0.11.1.0.25-Dec2022.iso from HPE from December? Because this comes with HPE-703.0.0.11.1.0.25-Dec2022-Addon-depot.zip and if you chose  703.0.0.10.10.0-12 is guess it will not work so straight forward.

[T_1_6]

Not installed, that was just the latest upgrade.

[pirx]

Which HPE Upgrade Components version is installed? 

[erki72]

No, but I still patched them with the update manager and the dynamic baselines.
Upgrade Baseline bevor patching in Update Manager:

VMware ESXi 7.0.3 Update 3, HPE-Custom-AddOn_703.0.0.10.10.0-12, 06/30/2022, 2:00:00 AM (created in vCenter)

Can I uninstall the piece of software on all hosts? Respectively what is the content in the component?
hpe-upgrade 900.0.2-1OEM.700.1.0.15843807