In the add new VI domain wizard, you may see a yellow banner warning stating:
No version compatible matrix fetched from LCM for NSX_MANAGER
After inputting the Virtual Infrastructure Name and the Organization Name, the wizard takes over 2 minutes to move on to the Cluster page. The wizard spins as per screenshot below:
This has been observed in a VCF 4.4 environment but the same implementation process is in place in 5.x as well.
During an add-domain operation, SDDC needs to fetch the compliance matrix details in order to be aware what versioning is compatible for the new domain.
/var/log/vmware/vcf/lcm/lcm-debug.log:
2024-06-27T03:15:00.241+0000 INFO [vcf_lcm,3ccb0080811f4d2e,f07a] [c.v.e.s.l.a.r.c.i.ImageManagementController,http-nio-127.0.0.1-7400-exec-2] get version compliance matrix for domain VI
2024-06-27T03:15:00.242+0000 INFO [vcf_lcm,3ccb0080811f4d2e,f07a] [c.v.e.s.l.s.i.ImageManagementServiceImpl,http-nio-127.0.0.1-7400-exec-2] VI domain compliance matrix - getting the VCENTER, ESX, NSX-V/NSX-T install versions from the config file
From the log snippet above we can see that lcm needs the following component versions:
VCENTER
ESX
NSX-V/NSX-T
However the NSX_MANAGER component is not being included in the compliance matrix API response.
The versions are listed in the /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties file. However the NSX_MANAGER version is missing:
e.g.
vcenter.install.version=7.0.3.02000-24026615
nsxt.install.version=3.1.3.7.4-20340907
esx.install.version=7.0.3-23144291
Add the required NSX_MANAGER version to the /opt/vmware/vcf/lcm/lcm-app/conf/application-prod.properties file.
e.g.
vcenter.install.version=7.0.3.02000-24026615
nsxt.install.version=3.1.3.7.4-20340907
esx.install.version=7.0.3-23144291
nsx.install.version=6.4.7-15000561
5. Save the file and restart lcm service
systemctl restart lcm
6. Try the add-domain operation again.