- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
i'm having the exact same issue, atfer this the migration is left in an inconsistent state, the old VCSA is powered off, the new one is up but has the temporary IP and logging in to the 5480 port does not bring the migration menu but the regular appliance maintenance ui.
if i login to any of the esxi servers manually with vs client they complain about being managed by vcsa on the old IP.
what gives?, do i need to rollback and restart everything?.
indeed i do have a separate VUM instance in which i ran the migration assistant beforehand.
i exported the log as it asked me in tgz but i don't know what i'm looking for in them.
any ideas?.
edit: i found a solution of sorts..
after doing the rollback(turning on old VCSA, deleting new VCSA appliance VM), i uninstalled VUM from the windows server and then disabled the plugin in VCSA.
After this the upgrade ran succesfully