Security Service Platform node status down- False alarm on SSP.

Products

• VMware vDefend Firewall
• VMware vDefend Firewall with Advanced Threat Prevention

Issue/Introduction

You may observe an alarm on SSP indicating that a node status is Down after the cluster rollout restart and during the restoration of the Kubernetes control plane following a quorum loss.

 

However, the affected node does not appear in the Kubernetes cluster, including under nodes, machines, or in vCenter.

 

This can be verified by running the following commands:

 

# k get nodes -A -owide

# kubectl get machines -A -owide

 

Additionally, log in to vCenter and verify whether the node referenced in the alarm exists under the resource pool where all control plane and worker nodes are listed.

If the control plane node is not present in vCenter, you can proceed with the resolution steps outlined below.

Environment

SSP 5.1

Cause

N/A

Resolution

-- Check the cluster-api and monitor pod by following commands.

# k get pods -A | grep cluster

# k get pods -A | grep monitor

-- Restarted the cluster-api pod and monitor pod and this resolved the alarm.

 

# k delete pod <cluster-api pod name> -n nsxi-platform

# k delete pod <monitor pod name> -n nsxi-platform

 

This will resolve the node status down issue.