Troubleshooting NSX-T and Compute Manager Disappearance During Cluster Patching

Have you ever experienced the sudden disappearance of NSX-T and Compute Manager while trying to perform patching on your clusters? This can be a frustrating experience, and it’s important to know how to handle it when it occurs.

When you’re managing your clusters using an image, you may receive a notification that the status of NSX-T cannot be checked. To investigate further, you can go to the NSX-T instance and navigate to System and Fabrics, and then Compute Manager. However, if you find that the Compute Manager is empty, you may need to take some additional steps.

To resolve this issue, you can try to add a Compute Manager. However, if you receive a message that your company provider is already registered, this may not be the best solution. Instead, you can try to perform the following steps:

Run this API:

GET: https://{nsx-t_nodeIP_or_hostname}/api/v1/fabric/compute-managers

In the output, find the”id” and note a long number. It will be at the bottom of the output for example: “125ac23f-e7de-40ab-65ef-bb3727604ae6” (this is an example}

Run this API:

POST: https://{nsx-t_nodeIP_or_hostname}/api/v1/error-resolver?action=resolve_error

BODY: {
 "errors": [
      {
          "user_metadata": {
          "user_input_list": [
            {
              "property_value": "password_for_administrator@vsphere.local",
              "property_name": "password",
              "data_type": "PASSWORD"
            },
            {
              "property_value": "administrator@vsphere.local",
              "property_name": "username",
              "data_type": "TEXT"
            }
          ]
        },
        "error_id": 7064,
        "entity_id": "provide id from previous GET call "
      }
    ]
 }