"Compute manager #.#.#.# with id ####-####-####-### connection config is invalid." error seen after the vCenter Server IP has been changed

Products

• VMware NSX

Issue/Introduction

• When attempting to update the Compute Manager with the new vCenter Server IP, the following error is displayed in the NSX UI under: System > Fabric > Computer Manager
  Compute manager <New_vCenter_IP> with id ####-####-####-### connection config is invalid. Edit Hostname and provide compute manager credentials. (Error code: 7055)
  
• Entries similar to the below are observed in the NSX Manager log /var/log/cm-inventory/cm-inventory.log
INFO http-nio-127.0.0.1-7443-exec-5 CmInventoryService 4543 FABRIC [nsx@6876 comp="nsx->manager" level="INFO" reqId="####-####-#####-#####" subcomp="cm-inventory" >username="[email protected]"] Active server IP value: "Old_vCenter_IP"
for CM value: "New_vCenter_IP" in getCmConfigDataDto

 

Environment

VMware NSX
VMware vCenter Server

Cause

After the vCenter Server IP address is changed, the vCenter status in NSX shows as Down, and attempts to update the Compute Manager (CM) with the new IP address have been unsuccessful.

Resolution

This issue is resolved in VMware NSX 4.1.1 or later available at Broadcom Downloads.
If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround:
If possible, create a temporary NAT rule to map the old vCenter IP to the new IP address, allowing NSX to maintain connectivity until a proper upgrade.