There is lots issues / errors we face while using any Nutanix Move tool for P2V / V2V migration from VMware ESXi , vCenter, Hyper-V, AWS cloud platform to Nutanix AHV cluster.
I would recommend to read the Nutanix Move Tool complete guide- Best Practice before migration to minimize the issues / errors possibility.
Nutanix Move tool Migration error / issues list
I have listed out the common issues / errors of Nutanix Move tool during V2V migration from from VMware ESXi , vCenter, Hyper-V, AWS cloud platform to Nutanix cluster. I have the solution of each one.
Common question – What are the Nutanix Move tool VMs are not supported ?
Following Windows / Linux VMs are not supported :
- VM with no NICs.
- VM with physical disks.
- VM with no Vdisks.
- VM with shared Vdisks (2016 onwards)
- VM which is not in powered ON/OFF state.
- VM with Warnings or alerts.
Lets troubleshoot the Nutanix Move tool V2V migration issue / errors occures during migration.
Issue 1: Windows Machine Permission issue ?
Solution :
Check 3 things for any user on Windows VM to be qualified for Move to use:
- User must have “Logon as Batch Job” enabled.
- UAC must be disabled (for local administrator, it is usually disabled)
- User must have “Restore files and directories” rights.
- WinRM Service should be enabled on the Guest OS level.
Issue 2: Migrate the Windows Domain Controller Server, Microsoft Exchange server ?
Solution: It is not recommended to migrate the Windows DC, Exchange server
No, it is not recommended as Move might time out the operation. It would be best to follow the Microsoft best practices, that is, perform the transfer of roles for the DC, and for Exchange Server, disable the Exchange Information Store Service for migration to complete.
Read also: Google acquire Nutanix Inc ?
Issue 3: VM’s Cut-over after days and weeks ?
Solution: Nutanix recommends starting the cut-over data seeding process in a few hours
If you perform the data seeding now and the cutover after 1 week, it will create confusion for Move as there might be a lot of changes to the data on the VM (if VM is I/O intensive) that might need more time and we will revert to data seeding.
However, according to Move, you are still on the cut-over process. Hence, Nutanix recommends starting the data seeding process in a few hours before you can actually take a downtime and by the time the cut-over process starts, there are less changes to the data to be taken into account and the VM will migrate successfully.
Read also: Top 10 Nutanix Useful Commands
Issue 4: Nutanix Move VM up-gradation is stuck ?
Solution:
You can roll back the Move appliance to a previous version, run the script:
/opt/xtract-vm/scripts/rollback-xtract
Read also: Nutanix AHV – Boot VM in BIOS UEFI Mode
Issue 5: Nutanix Move VM – SSH User-ID and Password ( Credential ) ?
Solution: SSH to using Nutanix Move VM IP Address
Username : admin Password : nutanix/4u (default for newly setup Move VM)
Read also: Configure Nutanix Virtual Network with IPAM
Issue 6 : How to switch as root account in Nutanix Move VM ?
Solution: SSH to Nutanix Move VM and run following command
The admin user on Move does not really have all the major rights, so best way is to change the user to root. To do that, on the Move VM, run:
admin@move$ rs [sudo] password for admin: (use same default password)
Enter the password for admin. You will be able to change the mode to root user and have control over the Move VM.
Read also: Nutanix Prism Supports Top 5 Web Browsers
Issue 7 : How to assign static IP Address to Nutanix Move VM ?
Solution;
Step 1: SSH to Nutanix Move VM
Step 2: Switch to the root user
# rs
Step 3: Configure the static IP address on Nutanix Move VM
#configure-static-ip
Enter the required information as shown in the following example.
Do you want to configure static IPv4 address?(y/N) y Enter Static IPv4 Address (e.g. 10.xx.xx.xx) 10.xx.xx.xx Enter Netmask (e.g. 255.255.255.0) 255.255.255.0 Enter Gateway IP Address (e.g. 10.xx.xx.xx) 10.xx.xx.xx Enter DNS Server 1 IP Address (e.g. 10.xx.xx.xx) 10.xx.xx.xx Enter DNS Server 2 IP Address (e.g. 10.xx.xx.xx) 10.xx.xx.xx Enter Domain (e.g. blr.ste.lab) bltr.ste.lab
The static IP address is assigned successfully.
Read aslo: Shutdown / Start Nutanix vSphere Cluster – Best Practice
Issue 8: Where is the Nutanix Move VM Logs location ?
Solution:
Nutanix Move VM logs location is here:
Below are the log files which will be important for troubleshooting.
| Logs File Location | Description of the Log File |
|---|---|
| /opt/xtract-vm/logs/diskreader.log | Uses NFC mechanism to take a copy of the disk and ship it to the AHV side using “pipe”. |
| /opt/xtract-vm/logs/diskwriter.log | This is the receiver of the copy disk through pipe and it writes it to the container mounted on the Move VM. |
| /opt/xtract-vm/logs/mgmtserver.log | Orchestrator service, exposes REST APIs to source, target side. If this service is working fine, then the UI will load perfectly. |
| opt/xtract-vm/logs/srcagent.log | Dealing with source side, it prepares the migration by enabling CBT (Changed Block Tracking), shutting down the VM and shipping the last snapshot before the VM finally boots up on AHV side. |
| /opt/xtract-vm/logs/tgtagent.log | Dealing more on the Nutanix AHV side. Collects cluster information and mounts the needed container to Move during migration and power on the VM on the AHV side. |
Read also: Nutanix AHV Supported Guest OS List
Issue 9: How to analyze / Read Nutanix Move VM Logs ?
Step 1: SSH to Nutanix Move VM
Step 2 : change to logs directory
root@move# cd /opt/xtract-vm/logs
Step 3: Read logs from required logs file
root@move# opt/xtract-vm/logs $ tail -f srcagent.log
Output will be similar below:
I1106 13:51:17.967628 13 srcagentapi_esxi_impl.go:272] server: entering VMValidateCredentials I1106 13:51:18.307828 13 esxvm.go:396] [VM:APP1|MOID:2] Populating username/password from common credentials I1106 13:51:18.313586 13 uvmcontroller.go:904] [VM:APP1|MOID:2] Validating credentials: vcIP=10.xx.xx.xx, vcUserName=root, VM UserName=admin I1106 13:51:18.318379 13 uvmcontroller.go:868] [VM:APP1|MOID:2] VMTools service is running. I1106 13:51:18.318404 13 uvmcontroller.go:183] [VM:APP1|MOID:2] Connecting to user VM I1106 13:51:18.323229 13 uvmcontroller.go:127] [VM:APP1|MOID:2] Retrying failed operation… (error: ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation., delay: 5s, retry: 9) I1106 13:51:23.323442 13 uvmcontroller.go:137] [VM:APP1|MOID:2] Resetting context after failed operation retry 9 with retryCtxTimeout: 3m20s I1106 13:51:23.327024 13 uvmcontroller.go:127] [VM:APP1|MOID:2] Retrying failed operation… (error: ServerFaultCode: Current license or ESXi version prohibits execution of the requested operation., delay: 10s, retry: 8) I1106 13:51:33.327271 13 uvmcontroller.go:137]
Read also: Install Nutanix LCM Dark Site Bundle on Linux Server
Issue 10: How to check Nutanix Move services status ?
Solution: Run the command svcchk as below
root@move$ svcchk
Restart all Nutanix Move VM Services
root@move$ svcrestart
Read also: What is Nutanix NCC Health Check ?
I tried to cover mostly asked issue / errors list of Nutanix Move tool. Hopefully you will get the resolution of your problem.
Thanks to being with HyperHCI Tech Blog to stay tuned with latest and trending technology post here.!
If have any issue / error’s resolution please mention in comment, it would helpful for other Nutanix geeks.