- Manuals
- Brands
- Dell
- Converged Infrastructure
- EMC
- Cluster Migration User's Guide
Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide PDF
Summary of Content for Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide PDF
Users Guide
Dell EMC VxRail 4.7.x Cluster Migration
Users Guide
Abstract VxRail Cluster Migration enables users to migrate a VxRail cluster from the
source VC to the designated target VC without impacting all of the running VMs.
July 2020
2 VxRail Cluster Migration Users Guide
Revision history
Date Description
December 2019 Initial release
June 2020 Updated to include precheck, DVS, and port groups in versions 4.7.510 and later
The information in this publication is provided as is. Dell Inc. makes no representations or warranties of any kind with respect to the information in this
publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.
Use, copying, and distribution of any software that is described in this publication requires an applicable software license.
Copyright 2020 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, Dell EMC, and other trademarks are trademarks of Dell Technologies. or
its subsidiaries. Other trademarks may be trademarks of their respective owners. [7/13/2020] [Users Guide] [H18396]
3 VxRail Cluster Migration Users Guide
Table of contents
1 About VxRail Cluster Migration .............................................................. 4
2 Scope ..................................................................................................... 5
2.1 Supported scenarios ........................................................................................................................................... 5
2.2 Unsupported scenarios ....................................................................................................................................... 5
3 Validations .............................................................................................. 6
3.1 Risks ................................................................................................................................................................... 6
3.1.1 Possible impacts ................................................................................................................................................. 6
4 Requirements ......................................................................................... 8
4.1 Operating system and .NET framework ............................................................................................................. 8
4.2 PowerShell 5.1.................................................................................................................................................... 8
4.3 PowerShell environment configuration ............................................................................................................... 8
4.4 Posh-SSH ........................................................................................................................................................... 9
5 Usage ................................................................................................... 10
5.1 Standard clusters .............................................................................................................................................. 10
5.1.1 Syntax ............................................................................................................................................................... 10
5.1.2 Parameters ....................................................................................................................................................... 10
5.1.3 Examples .......................................................................................................................................................... 12
5.2 Stretched clusters ............................................................................................................................................. 13
5.2.1 Syntax ............................................................................................................................................................... 14
5.2.2 Parameters ....................................................................................................................................................... 14
5.2.3 Examples .......................................................................................................................................................... 15
5.3 Monitoring ......................................................................................................................................................... 17
5.3.1 Example ............................................................................................................................................................ 17
6 Error handling ....................................................................................... 18
6.1 Retry ................................................................................................................................................................. 18
6.1.1 Example ............................................................................................................................................................ 19
7 Troubleshooting ................................................................................... 20
8 Logging ................................................................................................ 21
8.1 Log file .............................................................................................................................................................. 21
8.2 Log content ....................................................................................................................................................... 21
4 VxRail Cluster Migration Users Guide
1 About VxRail Cluster Migration VxRail Cluster Migration is a script-driven feature designed to help you automate the cluster migration process
using a PowerShell script file named vxrail-cluster-migration.ps1. You can migrate a VxRail cluster from the
source VC to the designated target VC without impacting all the running VMs.
1.1 Nomenclature Source vCenter Server -The vCenter Server that is currently managing the VxRail Cluster. It can be either a
VxRail vCenter Server (internal VC) or a customer-supplied vCenter Server (external VC).
Target vCenter Server -The vCenter Server that will manage the VxRail Cluster going forward. It must be a
customer-supplied vCenter Server (external VC).
5 VxRail Cluster Migration Users Guide
2 Scope This script must be run on a machine that can access vCenter and VxRail Manager.
This script only applies to VxRail 4.7.410 and later.
This script can perform operations for only one cluster at a time.
2.1 Supported scenarios Standard VxRail cluster
Stretched VxRail cluster -A specific deployment of VxRail cluster that extends the vSAN datastore
across two sites. See VMWare document https://docs.vmware.com/en/VMware-
vSphere/6.7/com.vmware.vsphere.vsan-planning.doc/GUID-FD6CD8A6-319B-434A-9E38-
ACF4DD9136A4.html for detailed information.
2-Node VxRail cluster -A special case of stretched cluster that has only two nodes and one witness
host. See VMWare document https://storagehub.vmware.com/t/vmware-vsan/vsan-2-node-guide/ for
more information.
SRS-enabled VxRail cluster -Dell EMC Secure Remote Service that allows your appliance to
periodically send health data to Support. It also allows Support to connect to your appliance to
correct problems, often before they become serious.
Note: If the activated internal SRS version is 3.42 or 3.44, you must shut down this VM before
migration. For details, refer to https://support.emc.com/kb/544028
Switch Automation-enabled VxRail cluster -If a VxRail cluster is deployed with a Dell TOR switch,
the SmartFabric Services can be enabled along with the deployment of OMNI plug-in in the vCenter,
which can simplify and automate the network configuration and management. See
https://i.dell.com/sites/csdocuments/Product_Docs/en/dell_emc_solution_brief_smartfabric_for_vxrai
l.pdf for more information.
Mixed VxRail cluster -The cluster is deployed with different appliance models, such as G410, E560,
P570, etc.
2.2 Unsupported scenarios Migration is not supported if any of the following scenarios apply to your environment.
Any kind of external storage devices are attached, including but not limited to the following:
- NFS
- iSCSI (including PR4VM)
- FC
Active Directory is enabled on any of the hosts.
vSAN encryption is enabled in the cluster.
The cluster is a non-VxRail datacenter or cluster managed by the internal VC/PSC of another
cluster.
Either source vCenter server or target vCenter server is Windows-based.
Either source vCenter server or target vCenter server has VC HA configured.
VC HA refers to the High Availability configuration for the VMs of the source/target VC.
6 VxRail Cluster Migration Users Guide
3 Validations The script will terminate if any of the following validations fail.
1. All the input parameters (IP, hostname, account etc.) are correct.
If any of these parameters are incorrect, they will be shown directly on the screen.
2. Deployment environment is supported.
None of the items described in the Unsupported Scenarios section apply to your environment.
3. The version of the target VC is not earlier than the source VC.
4. The vSAN health state of the VxRail cluster is not Error or Critical.
5. The VxRail Manager health state is not Error or Critical.
6. No host under the VxRail cluster is disconnected or in maintenance mode.
7. No VM is in fault tolerance state.
8. No name conflict exists between the source VC and the target VC.
- Cluster name
- DVS name
- Custom vSAN Storage Policy name
9. The external DNS server is valid.
If the DNS server on the target VC is different from that on the source VC, it must resolve all the
hostnames correctly.
10. The system time and time settings on all the components are synchronized.
- If the NTP server on the target VC is the same as that on the source VC, the time difference
between source/target VC and the NTP server cannot be longer than 5 minutes.
- If the NTP server on the target VC is different than that on the source VC, the time difference
between the source VC and the target VC cannot be longer than 5 minutes.
11. Migration might cause I/O error. All the user-defined virtual machines should be shut down before
migration. Allow for downtime before attempting the migration.
Note: There is a known issue involving virtual machine network loss. Virtual machine network
connection might be lost during cluster migration. If you encounter the following symptoms, refer to
KB https://support.emc.com/kb/543830.
An error message Failed to boot up VxRail Manager prints in PowerShell terminal.
Migration session stays on task- hostsConnectToDvsAction or VmMoveIntoFolderAction for more
than 20 minutes.
12. After migration, you will need to re-assign the VxRail vSAN license that was available in the
Source vCenter Server to the Target vCenter Server. Make sure the VxRail vSAN license key is
at hand before starting migration.
If the current cluster is upgraded from 4.0.x or 4.5.x, refer to https://support.emc.com/kb/542375
3.1 Risks Do not perform the migration if vSAN resync or vMotion is active on the cluster. Wait until these tasks
finish and then perform the migration. Forcing a cluster to migrate while these tasks are in progress
might cause adverse effects.
3.1.1 Possible impacts Acknowledge these possible impacts before performing the migration.
7 VxRail Cluster Migration Users Guide
1. If the original cluster is Log Insight enabled, after migration, the source VC/PSC and the target
VC/PSC will not be added into monitor scope of Log Insight.
2. The VMs of the internal VC/PSC still exist after migration, even though they are not in use.
3. Customer-installed software such as Switch plug-in, NSX, and any other 3rd party plugins will not
be migrated. They will need to be reinstalled and reconfigured.
4. VxRail value-added APP downloaded and configured from VxRail Market place will not be
migrated. Any value-added APP or 3rd party tools registered with VxRail vCenter Server, such as
RecoverPoint, VDP, Horizon Air, NSX, etc., will be invalid after the migration. Do not attempt to
migrate unless you have a migration plan for the value-added APPs.
5. All the VM snapshots taken before migration might NOT be usable in the target VC due to
different network information.
6. Most of the settings stored on the source vCenter server, such as vAPP, resource pool and etc.,
will be lost after migration. They can be re-created on the target vCenter server after migration. It
is better to back up all the settings before the migration.
Following are some examples, but this is not an exhaustive list:
- Resource pool(s)
- vAPPs
- Permissions/Roles/Users
- VM/Host Groups and rules.
- Host profiles
- Host affinity
Custom vSAN storage policies will be migrated if there is no conflict. See the Usage section for
more details.
8 VxRail Cluster Migration Users Guide
4 Requirements
4.1 Operating system and .NET framework This script supports Windows systems with .NET Framework. Other operating systems are not supported
at this time. Following is the compatibilities list.
Operating System .NET Framework Run Cluster Migration Script
Windows 10 4.7 Success
Windows Server 2012 4.7 Success
Windows 7 & Server 2008 4.6 Success
4.2 PowerShell 5.1 1. Run $PSVersionTable to check PowerShell version.
If you are running a PS version earlier than 5.1, see https://docs.microsoft.com/en-
us/powershell/scripting/install/installing-windows-powershell?view=powershell-5.1 to install the
correct version.
4.3 PowerShell environment configuration 1. Change Execution Policy to RemoteSigned
Launch a PowerShell console as administrator, run the following command to apply the change:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned
And verify the change with:
Get-ExecutionPolicy
9 VxRail Cluster Migration Users Guide
2. Restart PowerShell
After these environment configurations are done, restart PowerShell (also as administrator) to
make the change effective.
4.4 Posh-SSH 1. Install the Posh-SSH module for PowerShell. The minimum version is 2.1.
Launch a PowerShell console as administrator and run the following command to Install:
Install-Module -Name Posh-SSH
Verify the installation with:
Get-Module -ListAvailable -Name Posh-SSH
10 VxRail Cluster Migration Users Guide
5 Usage To use this script, open a PowerShell console as administrator, go to the directory of this script, run
vxrail-cluster-migration.ps1 -parameters to start migration process.
There are four workflows in total to be performed sequentially, and each has different functionalities.
1. ClusterMigrationScan
- Environment precheck
- Input parameter validation.
2. ClusterMigrationEnvPrepare
- Backup necessary configs on source VC, and recreate/import them on target VC
- Change necessary configs on the cluster and the hosts
3. ClusterMigrationExec
- Remove hosts from source VC
- Add hosts to target VC
- Reconfigure necessary resources on target VC
o DVS and port groups
o VMs
o Storage policy
o EVC settings
4. ClusterMigrationWrapup
- Update config files and DB in VxRail Manager VM
- Restore configs changed in ClusterMigrationEnvPrepare to the original state
- Remediate vSAN cluster inconsistency
- Register VxRail HTML5 plug-in on target VC
Each workflow will return a RequestId and display on the console. You can use the requestId to monitor
the current process, or retry the process if error occurs.
The workflows are performed in a fixed order, they cannot be skipped or reversed. If any workflow fails,
the script will be terminated instantly, hence all the subsequent workflows are blocked. Refer to Error
Handling section to see how to resolve the failure.
5.1 Standard clusters
5.1.1 Syntax .\vxrail-cluster-migration.ps1 -VxMIP
-VxMMysticPassword
-TargetVCAdminAccount
-TargetPSCManagementAccount
-TargetVCIp
-DatacenterName
-EsxiRootAccount
[-NoPrompt] [-NewDvsName
Note: Highlighted section is available in VxRail 4.7.510 and later.
Parameters
11 VxRail Cluster Migration Users Guide
-VxMIP
Required. Specify the VxRail Manager IPv4 address.
-VxMRootPassword
Required. Specify the VxRail Manager root account password.
-VxMMysticPassword
Required. Specify the VxRail Manager mystic account password. Note that this is different than the
root password.
-SourceVCAdminAccount
Required. Specify username and password for source VC admin account.
-TargetVCAdminAccount
Required. Specify username and password for target VC admin account.
-TargetVCManagementAccount
Required. Specify username and password for target VC management account.
-TargetPSCManagementAccount
Required. Specify username and password for target PSC management account.
-TargetVCHostname
Required. Specify the host name of target VC.
-TargetVCIp
Required. Specify the IP address of target VC.
-TargetPSCHostname
Required. Specify the host name of target PSC.
-TargetPSCIp
Required. Specify the IP address of target PSC.
-DatacenterName
Required. Specify the name of the datacenter that you plan to migrate to on target VC.
-VxMName
Required. Specify the VM name of the VxRail Manager of current cluster.
-SSOTenant
Required. Specify the SSO tenant on target VC.
-EsxiRootAccount
Required. Specify the root accounts for all the ESXi hosts.
-ReuseCustomPolicy
Optional. Specify that the existing custom storage policies created on target VC should be reused
during cluster migration.
-RequestId
Optional. Specify the request Id for a certain workflow.
-Action
Optional. Specify whether to retry or dismiss the operation with provided request Id.
-NoPrompt
Optional. Turns off the warning message prompt. This parameter is reserved for automation script
development when used with this script. It is not recommended for manual script execution.
Note: The following additional parameters are available in VxRail 4.7.510 and later.
-NewDvsName
Optional. Modifies the name of Distributed Switch at ClusterMigrationScan when DVS name is
conflicted in the target VC. When the parameter is inputted, the DVS name will be modified at
ClusterMigrationScan before the migration is performed.
-PortGroups
12 VxRail Cluster Migration Users Guide
Optional. Modifies the name of Port Groups Switch at ClusterMigrationScan when the names of some
port groups are conflicted in the target VC. When the parameter is inputted, the port groups name will
be modified at ClusterMigrationScan before the migration is performed.
-Precheck
Optional. Specify to perform a precheck ClusterMigrationScan to see if the cluster is ready for
migration.
5.1.2 Examples
5.1.2.1 Run a precheck (Vxrail 4.7.510 and later) Only perform precheck to see if the cluster is ready for migration.
.\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-Precheck
5.1.2.2 Modify DVS or Port Groups during the migration (Vxrail 4.7.510 and
later) If the names of DVS or Port Groups are conflicted in target VC, modify them by specifying -NewDvsName
or -PortGroups
.\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-NewDvsName "dell13g switch"
-PortGroups @(@{current_name="VMware HCIA Dist-DVUplinks-319";new_name="VMware HCIA Dist-
DVUplinks-319-test"},@{current_name="VM Network A";new_name="Dev Network A"})
13 VxRail Cluster Migration Users Guide
5.1.2.3 Run Migration Run the command in PowerShell console to see if the cluster is ready for migration. It will show the
progress and status message.
.\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
Note: If -NoPrompt is NOT specified, warning messages will display. You must read these
messages, and then press y to proceed.
5.2 Stretched clusters For 2-Node clusters and stretched clusters, the following parameters are needed in addition the ones for
standard clusters.
14 VxRail Cluster Migration Users Guide
5.2.1 Syntax .\vxrail-cluster-migration.ps1 -VxMIP
-VxMMysticPassword
-TargetVCAdminAccount
-TargetPSCManagementAccount
-TargetVCIp
-DatacenterName
-EsxiRootAccount
-WitnessAccount
[-Action
Precheck]
Note: Highlighted section is available in VxRail 4.7.510 and later.
5.2.2 Parameters -VxMIP
Required. Specify the VxRail Manager IPv4 address.
-VxMRootPassword
Required. Specify the VxRail Manager root account password.
-VxMMysticPassword
Required. Specify the VxRail Manager mystic account password. Note that this is different than the
root password.
-SourceVCAdminAccount
Required. Specify username and password for source VC admin account.
-TargetVCAdminAccount
Required. Specify username and password for target VC admin account.
-TargetVCManagementAccount
Required. Specify username and password for target VC management account.
-TargetPSCManagementAccount
Required. Specify username and password for target VC management account.
-TargetVCHostname
Required. Specify the host name of target VC.
-TargetVCIp
Required. Specify the IP address of target VC.
-TargetPSCHostname
Required. Specify the host name of target PSC.
-TargetPSCIp
Required. Specify the IP address of target PSC.
-DatacenterName
Required. Specify the datacenter name on target VC.
-VxMName
Required. Specify the VM name of the VxRail Manager of current cluster.
-SSOTenant
Required. Specify the SSO tenant on target VC.
-EsxiRootAccount
Required. Specify the root accounts for all the ESXi hosts.
15 VxRail Cluster Migration Users Guide
-WitnessHostname
Required. Specify the witness host name for the stretched cluster.
-WitnessIP
Required. Specify the IP address of the witness host.
-WitnessAccount
Required. Specify the root account for the witness host.
-Stretched
Required. Specify the cluster is a stretched cluster.
ReuseCustomPolicy
Optional. Specify that the existing custom storage policies created on target VC should be reused
during cluster migration.
-RequestId
Optional. Specify the request Id for the certain workflow.
-Action
Optional. Specify either to retry or dismiss regarding the operation with provided request Id.
-NoPrompt
Optional. Specify if the warning message prompt should be turned off.
Note: The following additional parameters are available in VxRail 4.7.510 and later.
-NewDvsName
Optional. Specify a new name of the Distributed Switch if need to modify the name of Distributed
Switch at ClusterMigrationScan. When the parameter is inputted, the DVS name will be modified at
ClusterMigrationScan before the migration is performed.
-PortGroups
Optional. Modifies the name of Port Groups Switch at ClusterMigrationScan. When the parameter is
inputted, the port groups name will be modified at ClusterMigrationScan before the migration is
performed.
-Precheck
Optional. Specify to perform a precheck ClusterMigrationScan to see if the cluster is ready for
migration.
5.2.3 Examples
5.2.3.1 Run a precheck (Vxrail 4.7.510 and later) Only perform precheck to see if the cluster is ready for migration.
.\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
16 VxRail Cluster Migration Users Guide
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-WitnessHostname 10.10.200.100 -WitnessIP 10.10.200.100
-WitnessAccount @{username="root";password="Witnesspassword!"}
-Stretched
-Precheck
5.2.3.2 Modify DVS or Port Groups during the migration (Vxrail 4.7.510 and
later) If the names of DVS or Port Groups are conflicted in target VC, modify them by specifying -NewDvsName
or -PortGroups
.\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-WitnessHostname 10.10.200.100 -WitnessIP 10.10.200.100
-WitnessAccount @{username="root";password="Witnesspassword!"}
-Stretched
-NewDvsName "dell13g switch"
-PortGroups @(@{current_name="VMware HCIA Dist-DVUplinks-319";new_name="VMware HCIA Dist-
DVUplinks-319-test"},@{current_name="VM Network A";new_name="Dev Network A"})
5.2.3.3 Run Migration Run the command in PowerShell console, it will show the progress and a status message.
.\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-WitnessHostname 10.10.200.100 -WitnessIP 10.10.200.100
-WitnessAccount @{username="root";password="Witnesspassword!"}
-Stretched
17 VxRail Cluster Migration Users Guide
Notes:
Witness host name, witness IP and witness account are required. Also, -Stretched indicator is a
must. The other parameters are similar to standard cluster.
If the witness host is deployed in another datacenter, it will be moved to the same datacenter along
with the Stretched/2-Node cluster after migration.
5.3 Monitoring Specify the request Id and watch the progress for this operation.
5.3.1 Example .\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-RequestId "SBI_49"
Notes:
The monitor operation does not require -Action parameter. It will query VxRail Manager for the
latest status of the given requestId and show it on the console.
If the given requestId has already completed, it will automatically perform the next workflow if there
are any remaining ones to be done.
18 VxRail Cluster Migration Users Guide
6 Error handling Errors or failure might occur during the migration process. Refer to the KB article
https://support.emc.com/kb/537361 to resolve these errors.
Following is an example of an error.
Each workflow has different ways to report and handle errors. The following table below shows the
differences.
Scan EnvPrepare | Exec | Wrapup
Report failure Report after all steps complete Report immediately
Abandon when failure Automatically abandoned Not abandoned
Retry after failure Unsupported Supported
Restart after failure Supported Unsupported
If ClusterMigrationScan fails, you will not be able to retry with given request Id. Instead, you must restart the
whole process using the same input parameters.
If ClusterMigrationEnvPrepare, ClusterMigrationExec, or ClusterMigrationWrapup fails, you will not be able
to restart the whole process. Instead, retry the failed workflow with the given request Id.
6.1 Retry To retry a failed request, specify the given requestId and invoke the -Action Retry parameter. This
action will resume the workflow execution from the point where the error occurred.
19 VxRail Cluster Migration Users Guide
6.1.1 Example .\vxrail-cluster-migration.ps1 -VxMIP "10.10.10.10"
-VxMRootPassword "Password!"
-VxMMysticPassword "Password!"
-SourceVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCAdminAccount @{username="administrator@vsphere.local";password=" Password!"}
-TargetVCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetPSCManagementAccount @{username="lairy@vsphere.local";password=" Password!"}
-TargetVCHostname exvc100.externalvc.com
-TargetVCIp 10.10.100.100 -TargetPSCHostname exvc100.externalvc.com
-TargetPSCIp 10.10.100.100 -DatacenterName "dell13g"
-VxMName "VxRail Manager" -SSOTenant "vsphere.local"
-EsxiRootAccount @{"dell13g-01.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-02.externalvc.com"=@{"username"="root";"password"="Esxpassword!"};
"dell13g-03.externalvc.com"=@{"username"="root";"password"="Esxpassword!"}}
-RequestId "SBI_49" -Action Retry
Note: ClusterMigrationScan does not support retry. It will automatically be abandoned regardless
of whether errors occur. Run the script again to restart Scan.
20 VxRail Cluster Migration Users Guide
7 Troubleshooting When an error occurs, an error message and the corresponding KB article link will display on the screen.
Follow the instructions in the KB articles to resolve the error, and then retry.
21 VxRail Cluster Migration Users Guide
8 Logging Logging functionality is implemented such that you can verify the success and failure after automated batch
process.
8.1 Log file In the same directory as vxrail-cluster-migration.ps1, a log file is created with the following naming
convention:
ClusterMigration-
For example, ClusterMigration-10.10.10.10-2019-08-21.log.
ClusterMigration- is the log prefix, 10.10.10.10 is the VxRail Manager IP address,
2019-08-21 is the date, and the log file name ends with .log.
8.2 Log content Each log record has these components:
Timestamp LogLevel [InvocationFunction] - Log Message
For example, the following log record shows an event regarding ClusterMigrationScan.
2019-08-20T11:26:27.8239566+08:00 INFO [Call-ClusterMigrationAPI] - ClusterMigrationScan Triggered
with RequestId [SBI_10]
Log Level is usually INFO. When exceptions occur, log level can become ERROR. For example:
<Related manuals for Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide
Manualsnet FAQs
If you want to find out how the EMC Dell works, you can view and download the Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide on the Manualsnet website.
Yes, we have the Cluster Migration User's Guide for Dell EMC as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.
The Cluster Migration User's Guide should include all the details that are needed to use a Dell EMC. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.
The best way to navigate the Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.
This Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.
You can download Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.
To be able to print Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell EMC VxRail 4.7.x Converged Infrastructure Cluster Migration User's Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.