The upgrade process for the VCSA from a major release to another is as follows:
- A new VCSA with a temp IP is created in the vSphere host/cluster by the upgrade process.
- The upgrade process migrates the config/data from the old VCSA to the new one.
- The Old VCSA is shutdown and the new VCSA is renamed/re-ip with the values of the old VCSA. New VCSA is then rebooted.
At this point the new VCSA should have the old VCSA name and IP address. My question for those that have done this already is, how does the Nutanix cluster Prism element reacts to this in regards to its vcenter registration? Will all this be transparent to it or will it see the new VCSA as a new device and create a duplicate entry?
I assume the migration process will copy SSH keys and certs from the old VCSA to the new one so Prism won’t bat an eye, but I just wanted to confirm.
@Jose A. Hernandez AFAIK, VCSA is registered with the Prism through UUID. The UUID of the new VCSA shouldn’t change with the upgrade so it eventually shouldn’t impact the registration process.