Real-time scenario-based questions and answers on VMware ESXi: Part-3

11. vMotion Fails – VM Stuck at 14% or 90%

Scenario:

When trying to migrate a VM using vMotion, the operation gets stuck at 14% or 90% and fails.

Possible Causes:

• Insufficient network bandwidth on the vMotion network.
• VM has an active CD/DVD drive connected to a local datastore.
• High CPU/RAM utilization causing resource contention.
• vMotion network is misconfigured.

Solution Steps:

1. Check vMotion Network Configuration
   • Ensure the vMotion NIC is configured correctly: bashCopyEditesxcli network ip interface list
   • Verify vMotion network reachability using: bashCopyEditvmkping <target_host_IP>
2. Check for Open VM Hardware (CD/DVD, ISOs, Floppy)
   • If a VM has an attached CD/DVD, disconnect it.
     • Right-click VM → Edit Settings → Uncheck “Connected” for CD/DVD.
3. Check Storage and CPU Load
   • If the VM is using a high CPU load, try again when usage is lower.
4. Use “Force vMotion” to Bypass CPU Compatibility Check bashCopyEditvim-cmd vmsvc/getallvms vim-cmd vmsvc/migrate <VM_ID> <Target_ESXi_ID>
5. Reconfigure vMotion if Needed
   • Disable and re-enable vMotion on both hosts.
   • Restart ESXi management services: bashCopyEdit/etc/init.d/hostd restart /etc/init.d/vpxa restart

---

12. ESXi Host Fails to Enter Maintenance Mode

Scenario:

When trying to put an ESXi host into Maintenance Mode, the process gets stuck or fails.

Possible Causes:

• A VM is still running on the host.
• vSphere HA is preventing the action.
• Storage or network issues causing lockups.

Solution Steps:

1. Manually Migrate or Power Off VMs
   • Use vMotion to move running VMs to another host.
   • If vMotion is unavailable, power off VMs.
2. Check HA Admission Control Settings
   • Navigate to Cluster → Configure → vSphere HA.
   • Disable Admission Control and retry.
3. Force Maintenance Mode from CLI bashCopyEditvim-cmd hostsvc/maintenance_mode_enter
4. Restart ESXi Services and Retry bashCopyEdit/etc/init.d/hostd restart /etc/init.d/vpxa restart
5. Check for Storage Connectivity Issues
   • If the host is waiting for storage access, check if a datastore is unresponsive.

---

13. VM Network Disconnected After ESXi Host Reboot

Scenario:

After rebooting an ESXi host, some VMs lose network connectivity.

Possible Causes:

• vSwitch or port group misconfiguration.
• Physical NIC failed or disconnected.
• VLAN configuration mismatch.

Solution Steps:

1. Check if vSwitch and Port Groups Exist bashCopyEditesxcli network vswitch standard list esxcli network vswitch standard portgroup list
2. Verify Physical NIC Status bashCopyEditesxcli network nic list
3. Ensure VLAN Tagging is Correct
   • Check if VLAN ID on the port group matches switch configuration.
4. Restart Network Services bashCopyEdit/etc/init.d/networking restart
5. Reconnect VM to the Correct Port Group
   • Right-click VM → Edit Settings → Network Adapter → Reassign Port Group.

---

14. ESXi Host Logs Show “Lost Connectivity to Storage Device”

Scenario:

The ESXi host loses connectivity to a shared iSCSI/FC storage device.

Possible Causes:

• Network failure (for iSCSI storage).
• Storage controller failure or LUN not assigned.
• HBA/Multipathing issue.

Solution Steps:

1. Check Storage Connectivity bashCopyEditesxcli storage core path list
2. Rescan All Storage Adapters bashCopyEditesxcli storage core adapter rescan --all
3. Check Multipathing and HBA Configuration bashCopyEditesxcli storage nmp device list
4. Restart Storage Services bashCopyEdit/etc/init.d/lwiod restart /etc/init.d/hostd restart /etc/init.d/vpxa restart
5. Verify Storage Visibility on SAN/NAS Side
   • Check SAN/NAS logs to see if the ESXi host is recognized.

---

15. vCenter Appliance (VCSA) is Not Accessible

Scenario:

The vCenter Server Appliance (VCSA) is unreachable via web or SSH.

Possible Causes:

• vCenter service failure.
• Storage or disk space issues.
• Network misconfiguration.

Solution Steps:

1. Check if VCSA is Running on ESXi bashCopyEditvim-cmd vmsvc/getallvms vim-cmd vmsvc/power.getstate <VCSA_ID>
2. Access VCSA Directly via Console
   • Open DCUI (Direct Console UI) → Check Network & Services.
3. Restart vCenter Services bashCopyEditservice-control --stop --all service-control --start --all
4. Check Storage and Disk Space bashCopyEditdf -h
5. Verify vCenter Certificate Expiry bashCopyEdit/usr/lib/vmware-vmca/bin/certificate-manager

---

16. Unable to Delete a VM – “File is Locked” Error

Scenario:

When trying to delete a VM, you get “Cannot delete file. File is locked.”

Possible Causes:

• VM files are in use by another process.
• ESXi host lock preventing deletion.

Solution Steps:

1. Check Which Host Owns the Lock bashCopyEditvmkfstools -D /vmfs/volumes/datastore/VM_Name/VM.vmdk
2. Power Off the VM and Retry bashCopyEditvim-cmd vmsvc/power.off <VM_ID>
3. Manually Remove Locked Files bashCopyEditrm -rf /vmfs/volumes/datastore/VM_Name
4. Restart ESXi Host (If Needed)
   • If the lock persists, restart the host holding the lock.

---

17. VM is Running but Not Responding

Scenario:

A VM is powered on but does not respond to ping, RDP, or SSH.

Possible Causes:

• Guest OS crash or freeze.
• Network adapter disabled or misconfigured.

Solution Steps:

1. Check VM’s Console for Any Errors
   • Open vSphere Client → VM Console → Look for OS errors.
2. Verify VM Network Adapter Status bashCopyEditesxcli network vm list esxcli network vm port list -w <VM_WORLD_ID>
3. Check for Disk or CPU Contention Issues
   • Run esxtop and check CPU %RDY and DAVG/cmd (Disk Latency).
4. Force Reboot the VM bashCopyEditvim-cmd vmsvc/power.reset <VM_ID>