When attempting to onboard the NSX Manager to the Shared Services Platform (SSP), the process fails. The SSP user interface displays the following error message:
SSP - "No Valid License Error" seen after onboarding NSX Manager - Infra Sync Down
The following warning and exception snippet are logged in the NSX Manager file /var/log/proton/nsxapi.log:
WARN CommonAgentDeltaProcessor CommonAgentDeltaConfigProducerImpl 1010408 NAPP [nsx@6876 comp="nsx-manager" level="WARNING" s2comp="CommonAgent" subcomp="manager"] Caught exception in ScheduledExecutorService. java.lang.NullPointerException: null
at vmware.nsx.napp.CommonAgentProtos$CertificateMsg$Builder.setCertificate(CommonAgentProtos.java:1340) ~[?:?]
at com.vmware.nsx.management.proton.commonagent.utils.DataConverter.buildCertUpdateMessage(DataConverter.java:94) ~[?:?]
at com.vmware.nsx.management.proton.commonagent.service.CommonAgentCertificateChangeListenerImpl.lambda$sendAllCertificates$3(CommonAgentCertificateChangeListenerImpl.java:239) ~[?:?]
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(Unknown Source) ~[?:?]
...
vDefend Security Services Platform Version: 5.0
NSX Version: 4.2.X
This issue occurs because Transport Node (TN) certificates are not synchronized with the SSP.
When these certificates fail to sync, the SSP environment triggers a false "No Valid License Error" pop-up.
You can verify the exact cluster and host status by navigating to:
NSX Manager UI > System > Fabric > Hosts
To resolve this issue, fix the underlying NSX installation on the affected ESX host(s).
Once the host-level installation is corrected and stabilized, the certificates will synchronize properly with the SSP, and the NSX Manager will onboard successfully without errors.
If the steps above do not address your specific issue, please refer to the Master KB for NSX Onboarding Issues, which outlines all known onboarding failure scenarios, root causes, and advanced troubleshooting methods.