NSX compute manager is showing "Registered with Errors".
search cancel

NSX compute manager is showing "Registered with Errors".

book

Article ID: 403570

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Under compute managers tab NSX manager UI shows Connection Status as 'Up' and Registration Status as 'Registered with errors'.
  • You may have recently updated the certificate in vCenter.
  • Clicking on 'Registered with errors' results in following error in NSX manager -
    Failed to remove NSX ownership due to error Error in rest call. url= nsxapi/api//v1/managed-objects/lcm/nsx-ownership/####?action=clear , method= PUT , response= { "module_name" : "common-services", "error_message" : "General error has occurred.", "details" : "java.lang.RuntimeException: java.net.ConnectException: Connection timed out (Connection timed out)", "error_code" : 100 } , error= 500 : "{<EOL> "module_name" : "common-services",<EOL> "error_message" : "General error has occurred.",<EOL> "details" : "java.lang.RuntimeException: java.net.ConnectException: Connection timed out (Connection timed out)",<EOL> "error_code" : 100<EOL>}<EOL>" .. Please resolve the error and try again.

    Navigate to NSX UI > System > Fabric > Compute Manager.



  • NSX manager logs show same status.
    var/log/cm-inventory/cm-inventory.log
    connection_status: COMPUTE_MANAGER_CONNECTION_STATUS_UP
    registration_status: COMPUTE_MANAGER_REGISTRATION_STATUS_REGISTERED_WITH_ERRORS
    cm_plugin_status: CM_PLUGIN_STATUS_STARTED

  • Syslog shows error while doing login.
    /var/log/syslog
    NSX 4364 FABRIC [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] error while doing login to cm ####

 

Environment

VMware NSX

Resolution

Edit compute manager (System > Fabric > Compute Manager) on individual NSX nodes and re-enter username, password and thumbprint of compute manager. This would attempt to register compute manager again.

If the step above does not fix the issue then try a reboot of the vCenter. After the VC reboot attempt the register of the compute manager again.

If this does not work please open a support case with Broadcom.

Additional Information