Manager Node has detected the NCP is down or unhealthy. Action required: To find the clusters which are having issues, use the NSX UI and navigate to the Alarms page. The Entity name value for this alarm instance identifies the cluster name. Or invoke the NSX API GET /api/v1/systemhealth/container-cluster/ncp/status to fetch all cluster statuses and determine the name of any clusters that report DOWN or UNKNOWN. Then on the NSX UI Inventory | Container | Clusters page find the cluster by name and click the Nodes tab which lists all Kubernetes and PAS cluster members. For Kubernetes cluster: 1. Check NCP Pod liveness by finding the K8s master node from all the cluster members and log onto the master node. Then invoke the kubectl command `kubectl get pods the NCP Pod, use kubectl logs command to check the issue and fix the error. 2. Check the connection between NCP and Kubernetes API server. The NSX CLI can be used inside the NCP Pod to check this connection status by invoking the following commands from the master VM. `kubectl exec -it <NCP-Pod-Name> -n nsx-system bash` `nsxcli` `get ncp-k8s-api-server status` If there is an issue with the connection, check both the network and NCP configurations. 3. Check the connection between NCP and NSX Manager. The NSX CLI can be used inside the NCP Pod to check this connection status by invoking the following command from the master VM. `kubectl exec -it <NCP-Pod-Name> -n nsx-system bash` `nsxcli` `get ncp-nsx status` If there is an issue with the connection, check both the network and NCP configurations. For PAS cluster: 1. Check the network connections between virtual machines and fix any network issues. 2. Check the status of both nodes and services and fix crashed nodes or services. Invoke the command `bosh vms` and `bosh instances -p` to check the status of nodes and services.