We're setting up a new VCenter 6 install using the VCSA. There are two VCenters, each with an external PSC. The PSC appliances are in the same SSO domain.
This is going to be our production VSphere 6 environment, but it isn't yet so I can still do some reconfiguration on it.
The initial install was on an AMD based host (we didn't have the "permanent" hardware available). Later, we got the new hosts so I wanted to move the appliances to the new hosts (Intel based).
Since the processor type is changing, I know I can't do a live vmotion, so I shut the PSC and VCenter appliances down, migrated them to the Intel host, then powered them back up. We've done this before on regular VM's (primarily Windows) with no issue.
Things seemed to work OK at first, but now I'm intermittently getting errors accessing the web client. I don't have the exact error in front of me, but it's something to the effect that it can't authorize. However, I'm not even getting the login screen before the error comes up, so it looks like the VCenter appliance isn't talking to the PSC.
I powered down the appliances and moved them back to the AMD hosts and powered back up and it seems to be working OK (although it seemed to work correctly before!).
I came across an article that says when you migrate VCenter between processor types, you should shut the vm down, remove it from the inventory, then browse the datastore and add the VM back in on the new host.
However, I also found another web site that says some Linux distributions tune themselves during install based on the CPU type, and that on those, you can't move it to a new processor type. I don't know if the VCSA falls under that.
Do I just need to do a remove from inventory/re-add? Or at this point, should I just start over and build the appliances on the intel hosts? I would prefer not doing a complete rebuild unless I have to, since I've set up the permissions, folder structure, etc., but I also don't want to take any chance if the VCSA installation is questionable.
Any suggestions would be appreciated.
Mike O.