After one NSX Manager node reboot, the city Manager cluster VIP stops answering from the civic jump network. What should the administrator inspect?
Select an answer to reveal the explanation.
Short Explanation
The VIP is the front doorbell for the Manager cluster. After a node reboot, check whether the cluster still owns that doorbell. Carbon Black will not bring the control-plane VIP back.
Full Explanation
After one NSX Manager node reboot, when the city Manager cluster VIP stops answering from the civic jump network, the administrator should inspect NSX Manager cluster status and VIP health. The VIP is the shared front door for the Manager cluster; after a node reboot, cluster membership, leader election, or VIP ownership can be unhealthy even if individual nodes boot. Restoring VIP health restores civic jump access to the control plane without chasing unrelated products. Carbon Black Cloud sensor groups on the Manager VMs fail by concept because endpoint sensor groups do not own NSX Manager cluster VIP behavior. Workspace ONE Access policies for the jump users fail by concept because Access SSO policy does not heal an NSX Manager VIP that is down on the management network. Identity Firewall logon events for the VIP address fail by concept because IDFW tracks directory user-to-IP mapping for DFW, not Manager cluster VIP health. Exam caveat: Manager VIP outages after node reboot are cluster and VIP health problems—do not escalate to CBC, Access, or IDFW as the first fix. Operational check: check Manager cluster status and VIP, confirm the VIP answers from the jump network, verify UI and API access, and document the reboot and VIP recovery in the city NSX change record for municipal control-plane resilience.