### Human: Can you tell about MOVE: Nutanix Move Basic Troubleshooting Guide. ### Assistant: This article describes basic troubleshooting for Nutanix Move (version 3.x & 4.x).. With the release of Nutanix Move 3.0, the Move services are dockerised and all the Move agents now run as Docker Containers. This is a major milestone that allows add/update features without much service disruption as well as provides flexibility to run Move anywhere.

If you are running an older version of Move, upgrade to Move 4.x and later.

To upgrade, find the latest version and procedure below:

Latest Move bundle: here

Upgrade Procedure: here

Note: If you face issues in booting the VM after migration to Nutanix AHV, please collect logs on AHV cluster using Logbay.. Overview

Move File locationsWhich user do we use to SSH into the Move VMLog files locations for troubleshootingBasic CommandsHow to generate Move support bundle from cliHow to configure static IP on Move VMFirewall Ports requirements for MoveTesting Connectivity between Move and ESXi/vCenter/Hyper-VCommon user permissions required on the Windows OS if using the domain administrator or local administrator accountsMove is stuck at 0% while "Seeding Data"Move VM migration failure due to missing snapshotWhat happens if Move upgrade is stuckAre there any logs created on the VM by MoveIf there is a backup schedule, will it affect Move

Move File locationsMove will use the below host directories. All of them are created under /opt/xtract-vm/.

Files LocationDescription/opt/xtract-vm/certsPath to the certificate key-pairs used by Move/opt/xtract-vm/keyPath to the SSH keys generated and used by Move/opt/xtract-vm/kvstoreKVStore directories used by srcagent and diskwriter/opt/xtract-vm/logsPath to Move service logs

Which user do we use to SSH into the Move VMWhen logging in to the Move VM using SSH, use:

Username : admin
Note: 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:

Username : admin

Enter the password for admin. You will be able to change the mode to root user and have control over the Move VM. 

Log files locations for troubleshootingBelow are the log files which will be important for troubleshooting.

Logs File LocationDescription of the Log File/opt/xtract-vm/logs/diskreader.logUses NFC mechanism to take a copy of the disk and ship it to the AHV side using "pipe"./opt/xtract-vm/logs/diskwriter.logThis 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.logOrchestrator 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.logDealing 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.logDealing more on the AHV side. Collects cluster information and mounts the needed container to Move during migration and power on the VM on the AHV side.

Basic CommandsTo check the status of the services, run the command svcchk as below. Note that the last column will give you the name of the service (for example, bin_srcagent_1, bin_tgtagent_1, bin_diskreader_1).

Username : admin

Note: If restarting any service/Docker with an active Migration Plan, the Migration Plan will turn into failed state and the target vdisk can get corrupted. In this case, a manual cleanup on AHV and a new Migration Plan are needed.To restart any single service, run the command "docker restart <service name>" as shown below. You can get the individual service names from the svcchk command.

Username : admin
To restart all the services, run the command svcrestart. It will ask you to confirm. Enter "y" (yes) to continue:

Username : admin

You can also use svcstop and svcstart commands to stop and start all the container services, respectively.

How to generate Move support bundle from cliTo generate the Move support bundle from CLI, run the command "root@move on ~ $ /opt/xtract-vm/bin/support-bundle [--dump-path <directory>]" as shown below. This example dumps the support bundle under the location /opt/xtract-vm/supportdumps. You can select your own directory. If you leave it blank, it will generate the bundle in the /root directory.

Username : admin

How to configure static IP on Move VMIn case you deleted the Move NIC or want to give a static IP again to the Move VM, follow the procedure of Assigning a Static IP Address to Nutanix Move. 

Firewall Ports requirements for MoveVerify the ports between Move VM and ESX and Target AHV is open. If the environment has different subnets, refer to Port Requirements of Move. 

Testing connectivity between Move and ESXi/vCenter/Hyper-V

Move must be able to communicate with vCenter Server on port 443, ESXi hosts on 902 and 443, and AHV on 9440. You can run the following commands from Move VM to verify the connectivity:

Username : admin
Testing connectivity on port 902 between Move and ESXi hostThe port connectivity for port 902 could not be tested by nc -zv <ESXi Host IP> 902.Reason: Starting from move 3.0 onwards, iptables is handling the routing for the docker containers residing in the move appliance hence, one needs to run the test through a docker container, please find the steps below:

List all running docker images :
	Username : admin
	Example:

	Username : admin
	Test connectivity from within the docker container named srcagent using the following command :
	Username : admin
	Example:

	Username : admin
	
Common user permissions required on the Windows OS if using the domain administrator or local administrator accounts Any user account on a Windows VM must possess three properties to be used as a login account by the Move:
The user must have "Logon as Batch Job" enabled.UAC must be disabled (for local administrator, it is usually disabled).The users must have "Restore files and directories" rights.

Move is stuck at 0%, while "Seeding Data"Possible Causes

The customer uses third-party solutions that rely on snapshots.Third-party snapshots may cause stale snapshots to reside in the VM folder on the VMware datastore.Old snapshots that have been forgotten.
Possible Solutions

Leverage the Consolidate option in VMware.
	This can be done through the Web or vSphere client by right-clicking the VM and selecting "Consolidate".This may fail to work, and the snapshot files may still appear in the VM folder on the datastore.The Consolidate option may be greyed out and not available.
	For Hyper-V, delete checkpoints Create a new snapshot, and then delete it.Storage vMotion the VM from one datastore to another:
	The VM must move from one VMware datastore to a different VMware datastore to ensure consolidation. Verify the absence of stale snapshots in the new datastore location.If Migrate option is greyed out:
		Try powering off the VM to see if the option becomes available. There are many reasons a Storage vMotion may not be possible while the VM is running.Check for registration issues. Follow VMware KB 2044369. Remove the VM from the inventory and re-add it. Ensure you know which datastore the .vmx file lives in before removing it. In some cases, you may need to power the VM off to remove it from inventory.If none of these options works and you need to leverage this KB, it should only be done with the assistance of VMware, as it involves modifying the DB.
		
	
 

Move VM migration failure due to missing snapshotMove migration may fail due to missing snapshots. Consolidate snapshots from the VMware Snapshot Manager to resolve.

A common signature would be found in Move mgmtserver.log:

Username : admin

Check the Source VM Snapshot Manager, and you will be unable to find the snapshot the logs refer to.

        

Consolidate all snapshots of the source VM from VMware Snapshot Manager. Once finished, recreate a new job in the Move for migration.

What happens if Move upgrade is stuck?If the Move upgrade is stuck, check the updater.log on the Move VM. If you cannot figure out the exact reason, collect the logs, and share them with Nutanix Support.

Proceed with verification of the status for all the services (the expected state is UP and not crashing) by running the command svcchk.

To roll back the Move appliance to a previous version, run the script:

Username : admin

Are there any logs created on the VM by Move? Yes, logs are created on the VMs when Move triggers VirtIO installation and IP address retention scripts.On Windows, the logs can be found in:

Username : admin

On Linux, they can be found in:

Username : admin

If there is a backup schedule, will it affect Move?Yes, it will be difficult to take the number of changes into account on the disk when there is a backup job in progress. So, it would be best to perform the migration outside of backup hours or disable the backup until the migration is completed.. ### Human: Now explain this as a Nutanix support agent summarizing the answer step by step. In case, you don't know the answer say - I don't know.