VMware ESXi 7.0 Update 3s = cisco custom add on incompatible

[Big Vern]

currently on (as seen in vmware vcenter on the cluster updates tab under 'image') - we use vclm
ESXi Version 7.0 U3p - 23307199
Vendor Addon Cisco-UCS-Addon-ESXi 4.3.2-a.1
Firmware and Drivers Addon None

need to patch as per title, all  the 'vendor add on' options for cisco come back with an incompatibility error
Can someone briefly walk me through how I can patch without removing the cisco stuff (can I just edit the image and vcenter and remove Vendor Addon)
Cisco-UCS-Addon-ESXi 4.3.2-a.1
or will this remove all the cisco drivers/other stuff on there ?? - Im unclear on this.
Any advice appreciated, do I have to drop to command line and install, always used the gui an pretty new to this,.

I noted a cisco employee on another thread posted ;
"Since you Cisco custom image, you should not use generic image to install the patch as there might be Cisco drivers that is not on the image. This was also confirmed by Broadcom TAC for one my cases."
https://community.cisco.com/t5/unified-computing-system-discussions/vmware-esxi-7-0u3p-cisco-custom-image/td-p/5127245

I dont pretend to understand the mix of vendor addons and firmware and drivers add on and how they interface with standard esxi updates / patches - we initially used a cisco custom iso to install some time ago.

[Kirk J]

Greetings.

I can see how that would happen if referencing the new image's profile (which would be different than the customized one).
I haven't tried this in lab yet, but will it let you install the patch more as a 'vib' type update vs profile update?

https://knowledge.broadcom.com/external/article/343840/esxcli-software-vib-commands-to-patch-an.html

Kirk...

[Kirk J]

Actually attempting that with dry run shows:

esxcli software vib update -d "/vmfs/volumes/xxxxxxxxxxxxxxxxxxxx/VMware-E
SXi-7.0U3s-24585291-depot.zip" --no-sig-check --dry-run
[InstallationError]
This upgrade transaction would skip ESXi Base Image VIB(s) VMW_bootbank_iavmd_2.7.0.1157-3vmw.703.0.105.22348816, which could cause failures post upgrade. Please use an alternative upgrade method that would install the above VIB(s). For example, use an image profile instead of VIBs to perform the upgrade.
Please refer to the log file for more details.

[edit]   Looks like there a no errors if you run the above command with 'install' vs update.

Kirk...

[Big Vern]

Thanks Kirk, and for your info and lab test
My concern is the vib install, seems to me dangerous as it sates in the notes
"The install method has the possibility of overwriting existing drivers" - which drivers etc.? - / which parts of the Cisco add on
what post install steps would this leave,
Image profile - when creating the image and using the same cisco addon is this just not avoiding the compatibility error by the backdoor?