In SSP UI, under NSX Manager > Connectivity Agent > View Details, both Infrastructure Sync and Inventory Sync show as Unknown.
Additionally, when attempting to onboard NSX Manager to SSP, the banner “No valid license available.” appears.
SSP 5.0
After deletion or undeployment of NAPP, some stale platform registry entries may remain in the NSX Manager.
These residual references — such as outdated Kubernetes API server IPs or kubeconfig details — can lead to communication and license validation failures when onboarding NSX to the Security Services Platform (SSP).
Log location: /var/log/proton/nsxapi.log
Example log:
2025-10-03T11:30:16.483Z WARN CloudNativeKubeconfigServiceImpl POLICY [comp="nsx-manager"]reqId="<UUID>" subcomp="manager" username="<abcd>"Error while validating kubeconf: com.vmware.nsx.management.cloudnative.exception.CloudNativeGeneralException:Kubectl get pod status operation failed. Unable to connect to the server: dial tcp <xx.yy.zz.0>:6443: i/o timeout
Please contact Broadcom support for further assistance.
If the Symptom in this KB does not address your issue, refer to the Master KB for NSX Onboarding Issues, which lists all known onboarding scenarios, causes, and troubleshooting methods.