Using VLCM to upgrade vSphere and NSX it fails with "Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-monitoring..."
Article ID: 381161
Updated On:
Products
Issue/Introduction
Using VLCM to upgrade a non VCF system is an option that can be used.
This article addresses what happens when this procedure fails due to the use of the incorrect version of NSX VIB bundle in the VLCM baseline image.
Environment
NSX
vSphere 7 and newer
Cause
If the NSX VIB bundle supplied to VLCM is not a match with the installed NSX version the upgrade will fail.
NSX is expecting the version of the NSX VIBs to match it precisely. The upgrade will fail around 48% and throw the following error message.
Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-monitoring.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-vdpi.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-shared-libs.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-proxy.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-netopa.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-snproxy.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-python-utils.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-nestdb.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-esx-datapath.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-python-logging.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-context-mux.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-exporter.Node has invalid version 4.2.1.0.0-8.0.24302041 of software vsipfwlib.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-ids.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-opsagent.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-sfhc.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsxcli.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-cpp-libs.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-proto2-libs.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-adf.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-platform-client.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-cfgagent.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-host.Node has invalid version 4.2.1.0.0-8.0.24302041 of software nsx-mpa.Failed to install software on host. Software status file does not exists on the host aec308a9-cadd-4687-93e8-d6de07c905aa. Verify that nsx-sfhc is running on host.
NSX VIB bundle version 4.2.1.0.0-8.0.24302041 did not match with what NSX 24304122 expected. NSX VIB bundle 4.2.1.0.0.8.0.24302014 is what was expected.
Resolution
In vCenter the VIB bundle must be changed to the proper version. VLCM uses baselines which contain the upgrade bundles for the upgrades to be performed.
This assumes that the customer has already created a baseline with the correct VIB bundle. In the following example the given is that NSX is 4.2.0 as the current version.
VLCM has stated in the error message that the VIB it has is not a valid version.
First we must obtain the correct NSX VIB to use. These are located in the NSX manager in the /repository directory.
Example: NSX 4.2.0.0.0.24105817
ls -la repository/
This manager has 2 version of NSX. We are wanting the version that is currently in stalled ... 4.2.0. We are looking for the ESXi VIBs that are called out in the message. Remember that the ESXi version is 8.0. This must also be a match when selecting the VIB bundle
The VIBs for the ESXi 8 hosts are in the "esx80" directory.
This is the VIB file needed in our example for vLCM to successfully update the hosts NSX instance.
Now the vLCM image or basline must be corrected in vCenter to use the correct VIB bundle.
This can be done by creating a new baseline and deleting the old one, or editing the existing baseline with the correct version of the VIB bundle.
The process is found in the administrator guide. Click link below.
Edit a vSphere Lifecycle Manager Baseline or Baseline Group, Page 162
Additional Information
The signature for this article will also match article ESXi Host goes into NSX INSTALL FAILED state with error "Node has invalid version <vib verision> of <vib name>" post upgrade of ESX host OS and NSX vibs together
The cause of this issue is different but the error message is the same.
Feedback
