Query: Migrate to new vCenter server

[ERSpigle]

I already have a support case in with HPE support to address some questions, but feel I'm just getting some copy-and-paste responses without any real dialogue around my questions, so here I am to see what responses I get here. We currently have an HPE SimpliVity Federation (version 4.1.0) deployed under a vCenter 6.7 server. We need to migrate this to a new vCenter 7.0.2 server that we have stood up. The new vCenter Virtual Applicance is up and running and has the SimpliVity plug-in ready to go as well. I have seen the instructions on what is required to migrate, but had a few side questions first.

1. Is it possible to migrate to a new datacenter and cluster name on the new vCenter server? I gather from some other things that I have dug up that these both need to be named the exact same on the new vCenter server due to how engrained these are at low levels in an HPE Federation. If so, is there no way to use a new naming convention for our vCenter datacenter and cluster that is housing SimpliVity without a full re-deploy of the nodes (ESXi hosts)?

2. Currently we log into the OmniStackVC VMs via SSH using active directory credentials from an active directory domain that we are retiring. Is there something we need to do with the OmniStackVC VMs to change to this new domain for authentication purposes? I know this question is possibly unrelated to the vCenter migration, but we're no longer authenticating the new vCenter server or anything against this old domain and need to get this handled at the same time so we can retire this old AD domain.

Let me know what is possible so we can get this vCenter migration done and also move SSH authentication to the virtucal controllers to a different domain.

[support_s]

System recommended content:

1. VMware Update Manager 4.0 - After Migrating vCenter Server to New Domain, Cannot Connect to Update Manager

2. HPE Intelligent Management Center Windows Migration Guide

If the above information is helpful, then please click on "Thumbs Up/Kudo" icon.

Thank you for being a HPE community member.

[Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

[ERSpigle]

Irrelevant.

[gustenar]

Hello @ERSpigle ,

Regarding the naming used in new vCenter, what we have known so far is that it is necessary to recreate the same names for Datacenter/Clusters. After you add the SimpliVity hosts to the new vCenter you will need to use the local OVC account to login to it. The username for this account is "svtcli". After that you can type the following commands: 

"sudo su"

"source /var/tmp/build/bin/appsetup"

"dsv-update-vcenter --server <IP address of new vCenter Server> --user <vsphereadministrator with domain> --password <vsphere admin password>"

Hope this helps.

[ERSpigle]

A few questions:

A) After successfully updating the vCenter server with the appropriate command as you indicated, will the new vCenter Server administrator@vsphere.local account be usable for logging into the OmniStackVC OVAs like it is under the current vCenter Server?

B) Does this operation cause any reboot or other sort of downtime for the host and / or OmniStackVC? If so, is it disruptive? I presume if there is downtime for the OmniStackVC (such as for a reboot) and we have HA with two hosts in the same cluster, it should cause no downtime, correct?

C) Do I first need to disconnect and remove the hosts from the old vCenter server before adding to the new? All instructions I have dug up seem to skip disconnecting and removing from the old vCenter Server, but I presume this is assumed to be required first, correct?

[gustenar · Accepted solution]

@ERSpigle 

A. Yes, you will be able to use the administrator account to login once the move is complete. 

B. Yes, this command issues a reboot of the OVC. The OVC will failover and VMs will continue to run, but no HA available for the ones living on the Simplivity node getting the OVC rebooted. 

C. You have to disconnect the hosts from the old vCenter first before trying to add them to the new one. It is not necessary to remove them from inventory, but it is ok if you do so.