NSX Manager will not come back online after reboot.

Products

• VMware NSX

Issue/Introduction

• After reboot of the NSX manager appliance, access to the UI cannot be connected to directly.

  Some appliance components are not functioning properly.

  Component health: Unknown.

  Error code: 101|

• NSX manager VIP UI shows cluster degraded with services down on one NSX manager.
• Additional reboots do not change the status and NSX manager availability.
• Running command get cluster status in cli on the affected node shows all NSX services as "UNAVAILABLE"
• Checking /var/log/syslog shows errors with the words:

  “exceptionCaught: Exception DecoderException caught.”

• Running the CARR script from KB 369034, its output indicates the CBM_CLUSTER_MANAGER certificate does not match with the corfu server truststore.

Environment

VMware NSX

Cause

This issue is caused when the NSX Manager CBM_CLUSTER_MANAGER certificate in the Corfu server trust store is out of sync with the certificate present in the certificate keystore.

Resolution

Using the CARR script will fix the CBM_CLUSTER_MANAGER certificate.

Using Certificate Analyzer, Results and Recovery (CARR) Script to fix certificate related issues in NSX

Confirm NSX backups are available and/or initiate a new backup prior to running the CARR script.