Error: NSX Application Platform Communication - Manager Disconnected Alarm in NSX

Products

• VMware NSX

Issue/Introduction

• The NSX Manager UI displays the alarm: `NSX Application Platform Communication - Manager Disconnected`.
  
  
  
  
• Security Services Platform (SSP) is deployed and integrated with the NSX environment
  
  
• The NSX Manager cluster is operational and in a healthy state.
  
  
• The NSX Application Platform (NAPP) or Security Services Platform (SSP) features appear unresponsive or show stale data
  
  
• Connectivity between the NSX Manager and the NAPP cluster is interrupted
  
  
• We see the below entries in the /var/log/proton/nsxapi.log

2026-06-10T23:56:07.419Z  INFO common-agent-alarm-status CommonAgentAlarmProviderPrototype 6650 NAPP [nsx@6876 comp="nsx-manager" level="INFO" s2comp="CommonAgent" subcomp="manager"] Feature NSX_APPLICATION_PLATFORM_COMMUNICATION, event type NSX_APPLICATION_PLATFORM_COMMUNICATION_MANAGER_DISCONNECTED, updated alarm instances: {######-####-####-####-###########=true/{"napp_cluster_id":"########-####-####-####-##########","intelligence_node_id":"#######-####-####-####-###########"}}.

2026-06-11T01:27:07.507Z  INFO ShaVerticalMessageDispatcher1 ShaVerticalMessageHandler 6650 MONITORING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Receive sha message with key ########-####-####-####-##########, need to handle false
2026-06-11T01:27:07.509Z  WARN common-agent-alarm-status CommonAgentKafkaClient 6650 NAPP [nsx@6876 comp="nsx-manager" level="WARNING" s2comp="CommonAgent" subcomp="manager"] Kafka not available: org.apache.kafka.common.errors.TimeoutException: Timeout expired while fetching topic metadata

Environment

VMware NSX

VMware NSX 4.2.3.1

Cause

This issue typically occurs due to a failed or unhealthy Security Services Platform (SSP) deployment. When the SSP infrastructure is not functioning correctly, the Kafka messaging bus used for communication between NSX Manager and NAPP becomes unavailable. 

Resolution

To resolve this alarm, you must ensure the underlying SSP/NAPP deployment is healthy. 

• Check the health of the SSP deployment and ensure all required pods and services are running as expected.
  
  
• If the SSP installation failed or is in a partial state, you must fix the deployment issues.
  
  
• The alarm clears automatically once the NSX Manager successfully establishes a connection to the NAPP/SSP cluster.
  
  
  
  

Additional Information

Note: If the issue persists, collect the SSP Support Bundle and raise a support ticket for further assistance, and upload the support bundle to the ticket.