After updating a VMkernel IP address for vMotion or vSAN within vCenter, the changed IP is not automatically reflected in the SDDC Manager inventory. This can lead to inconsistencies between the physical environment and the SDDC Manager database. The following guidance is intended to help you manually update the SDDC Postgres database to ensure it aligns with the changes made in vCenter.
SDDC Manager 5.2
Because these modifications were performed outside of SDDC Manager, the IP changes will not be reflected in the SDDC Postgres database. If IP addresses have been updated on the ESXi hosts from the Workload Domain (WLD) vCenter, those updates must also be carried out on the SDDC database to maintain environment consistency. These records must be manually updated to ensure future tasks remain functional.
The resolution requires updating database tables. Please contact Broadcom support for assistance as there are some internal steps that are needed to be executed.
----------------------------------
The steps provided in the workaround involve changes to the SDDC Manager database. Incorrectly executed commands, commands with incorrect data have the potential to cause irreparable damage to the VCF Environment. Please do not proceed without taking a snapshot of the SDDC Manager VM, and ideally a full file based backup of the SDDC Manager.
Before making any IP related changes :
Carry out a Test vmkping commands to this host being updated from an existing host already setup in the cluster :
Vmk0 is normally Management, You will need to identified and confirmed for the customers environment for vMotions and vSAN vmk assignments to carry out these tests
Once tests have been confirmed and working you can then go ahead and follow the next steps in order to change the IP addresses from vCenter UI and also from the SDDC DB
vCenter changes: