/var/log/vmware/vcf/lcm/lcm-debug.log 2025-09-08T06:46:33.666+0000 ERROR [vcf_lcm,1967###b00b####,####,precheckId=4aadefbc-####-4dc1-####-021a####9f3d,resourceType=NSX_T,resourceId=nsx-mgr-01.nsx.com] [c.v.e.s.l.p.i.nsxt.NsxtUpgradeUtil,Precheck-170] UC might not be running/active25-09-08T06:46:33.666+0000 ERROR [vcf_lcm,1967###b00b####,####,precheckId=4aadefbc-####-4dc1-####-021a####9f3d,resourceType=NSX_T,resourceId=nsx-mgr-01.nsx.com] [c.v.e.s.l.p.i.nsxt.NsxtPrimitiveImpl,Precheck-170] Failed while setting UC connection for NSX-T upgrade coordinator check {}java.lang.NullPointerException: null at com.vmware.evo.sddc.lcm.primitive.impl.nsxt.NsxtPrimitiveImpl.setNsxtUcConnectionForUpgradeCoordinatorChecks(NsxtPrimitiveImpl.java:2540)VMware NSX
The NSX Manager VIP certificate SAN field was incorrectly configured, using the NSX manager node name instead of the correct VIP name.
This incorrect SAN field caused authentication and communication failures between SDDC Manager and NSX-T Manager during audit verification, leading to precheck failure.
Make sure the NSX Manager VIP certificate SAN field with the correct VIP name. Instead of the individual node name.
Similar pre-check error KBs, but the cause might be different
https://knowledge.broadcom.com/external/article?articleNumber=327213
https://knowledge.broadcom.com/external/article?articleNumber=324042