This is a known issue impacting VMware NSX.
Workaround:
Perform the following steps on the NSX Manager shell as root user, one by one:
- Reboot all 3 NSX manager's:
- root@nsx-manager:~# reboot
- Once the manager reboot has completed, run the following command as root user to restart the mpa service:
- root@ns-xmanager:~# /etc/init.d/nsx-mpa restart
Note: Before rebooting the NSX manager appliances, please ensure you have up to date backups in place.
Before rebooting the NSX-T manager appliances, ensure the cluster is healthy by running the following command:
get cluster status
If the cluster is up and healthy, proceed to the next NSX-T manager.