VMware / Virtualization Centre, BAOI
VMware / Virtualization Center
Guided diagnostics and field commands for ESXi, vCenter, VMs, snapshots, datastores, shared storage, virtual networking, HA, DRS and backup.
vim-cmd vmsvc/getallvms
esxcli vm process list
esxcli storage filesystem list
vim-cmd vmsvc/power.getstate <VMID>
vim-cmd vmsvc/power.on <VMID>
vim-cmd vmsvc/power.shutdown <VMID>
vim-cmd vmsvc/power.off <VMID>
vim-cmd vmsvc/snapshot.get <VMID>
vim-cmd vmsvc/snapshot.removeall <VMID>
esxcli storage core device list
esxcli storage core path list
esxcli storage nmp device list
esxcli iscsi adapter list
vmkfstools -D /vmfs/volumes/<DATASTORE>/<VM>/<DISK>.vmdk
esxcli network nic list
esxcli network ip interface list
esxcli network ip interface ipv4 get
esxcli network ip route ipv4 list
esxcli network vswitch standard list
vmkping -I vmk0 <TARGET_IP>
/etc/init.d/hostd status
/etc/init.d/vpxa status
services.sh restart
/etc/init.d/fdm status
tail -n 100 /var/log/fdm.log
tail -n 100 /vmfs/volumes/<DATASTORE>/<VM>/vmware.log
tail -n 100 /var/log/vmkernel.log
tail -n 100 /var/log/hostd.log
Connect-VIServer -Server <VCENTER>
Get-VM
Get-VM | Get-Snapshot
Get-Datastore | Select Name,CapacityGB,FreeSpaceGB
Get-VMHost
Get-VM | Select Name,@{N='ToolsStatus';E={$_.ExtensionData.Guest.ToolsStatus}}
Get-VM | Get-NetworkAdapter | Select Parent,Name,NetworkName,MacAddress
Datastore capacity calculator
Estimate remaining space after adding or expanding VMs.
Snapshot ≠ backup
A snapshot is temporary and depends on the original VM disks and datastore.
Avoid keeping snapshots for long periods
Delta files can grow and complicate consolidation, backups and performance.
Never delete a VMDK blindly
Identify the disk chain and descriptors before any deletion.
Keep free capacity
A nearly full datastore can prevent snapshots, consolidation or VM startup.
Test the VMkernel interface
For vMotion, iSCSI or management, test from the vmkernel actually affected.
Document SAN paths
Record HBAs, WWPNs, zoning, LUNs and multipathing policies in the infrastructure documentation.
Center mission
8 playbooksTroubleshoot ESXi/vCenter by separating host capacity, datastore, VM state, snapshots, networking, VMware Tools, vMotion and HA before infrastructure changes.
Quick triage
- Check vCenter/ESXi alarms and triggering event.
- Check host health, CPU/RAM and datastores.
- Identify whether one VM, one datastore or the whole cluster is affected.
- Check snapshots/consolidation before storage operations.
- Keep tasks/events and timestamps before restarting agent/host.
Decision tree
Start with VM state, files, snapshot, Tools and virtual network.
Prioritize capacity, latency and storage connectivity.
Check management, resources, agents and hardware.
Check vCenter, HA heartbeat, admission control and management network.
Intervention playbooks
Start read-only, collect evidence, then change one variable at a time.
01VM will not power onControlled change
Power On fails with resource, file lock or configuration error.
Checks
- Read exact task/event in vCenter.
- Check datastore free space, host resources and VM files.
- Check lock or snapshot/consolidation.
Commands / evidence
vim-cmd vmsvc/getallvmsvim-cmd vmsvc/power.getstate <vmid>esxcli storage filesystem listExpected result
VM has resources, accessible files and no illegitimate lock.
Corrective actions
- Fix identified resource/datastore/lock before re-register or heavier action.
- Avoid manually deleting snapshot files.
Escalate when
VM files corrupted, multi-host lock or unstable storage.
02Datastore nearly fullIntrusive / escalation
Capacity alarm, snapshot failures or VMs suspended due to space.
Checks
- Measure capacity/free and recent growth.
- Identify snapshots, ISOs and orphan files without blind deletion.
- Check array-side thin provisioning.
Commands / evidence
esxcli storage filesystem listdu -h /vmfs/volumes/<datastore>/<vm> 2>/dev/nullvim-cmd vmsvc/snapshot.get <vmid>Expected result
Growth source is identified and safety margin is restored.
Corrective actions
- Consolidate/remove snapshots through vSphere with enough working space.
- Extend or migrate if capacity use is legitimate.
Escalate when
Critical datastore >95%, array also full or consolidation needs substantial temporary space.
03Snapshot / consolidation neededIntrusive / escalation
Consolidation needed, very old snapshot or deletion fails.
Checks
- List snapshots and age/size.
- Check sufficient datastore space.
- Check backup tasks that may hold snapshot.
Commands / evidence
vim-cmd vmsvc/snapshot.get <vmid>esxcli storage filesystem listls -lh /vmfs/volumes/<datastore>/<vm>/Expected result
Snapshot chain is understood, datastore has margin and no competing task.
Corrective actions
- Run consolidation from vSphere in a monitored window.
- Stop cause of recurring snapshots on backup side.
Escalate when
Inconsistent chain, huge delta or consolidation fails with disk/lock error.
04VM has no networkRead-only
VM is running but has no network, gateway or services.
Checks
- Check vNIC is connected and correct port group.
- Check port group/vSwitch/dvSwitch VLAN.
- Compare another VM on same port group.
Commands / evidence
esxcli network vm listesxcli network nic listesxcli network vswitch standard listExpected result
vNIC is connected to correct network and physical uplink is up.
Corrective actions
- Fix port group/VLAN/uplink according to failing layer.
- Do not change multiple trunk VLANs without impact analysis.
Escalate when
dvSwitch/vCenter inconsistency, complex teaming or shared physical network outage.
05ESXi host overloadedRead-only
VMs slow, high ready time, balloon/swap memory or datastore latency.
Checks
- Separate CPU contention, memory pressure and storage latency.
- Identify consuming VMs.
- Compare other cluster hosts.
Commands / evidence
esxtopesxcli hardware memory getesxcli system stats uptime getExpected result
Limiting resource is identified, not just a global average.
Corrective actions
- Rebalance/migrate load or fix responsible VM.
- Avoid further overcommit to hide contention.
Escalate when
Cluster-wide contention, slow shared storage or capacity planning needed.
06VMware Tools missing or outdatedControlled change
Guest status unknown, graceful shutdown unavailable or old network/storage drivers.
Checks
- Read Tools state in vCenter.
- Check OS version and compatibility.
- Plan reboot if drivers require it.
Commands / evidence
vim-cmd vmsvc/get.guest <vmid>vmware-toolbox-cmd -vsystemctl status open-vm-toolsExpected result
Tools runs and vCenter receives heartbeat/guest info.
Corrective actions
- Update using supported method for OS.
- Test snapshot backup afterward if VSS/quiescing is involved.
Escalate when
Legacy OS, critical driver or Tools update causes regression.
07vMotion failsRead-only
Live migration fails at precheck, network or storage stage.
Checks
- Read compatibility/precheck error.
- Check vMotion vmkernel, MTU and connectivity.
- Check shared datastore access and EVC/CPU.
Commands / evidence
esxcli network ip interface listvmkping -I vmk<Vmotion> <peer-ip>esxcli network ip route ipv4 listExpected result
vmkernel interfaces reach each other with expected MTU and hosts are compatible.
Corrective actions
- Fix targeted vmkernel network or compatibility issue.
- Retest a non-critical VM before bulk migration.
Escalate when
Complex vDS, NSX, EVC or multipath storage.
08HA / host isolationIntrusive / escalation
Host disconnected, isolation response or VMs restarted by HA.
Checks
- Check management network and isolation gateways.
- Check HA agents and datastore heartbeat access.
- Read cluster events before reconnecting anything.
Commands / evidence
vmkping <management-gateway>esxcli network ip interface list/etc/init.d/hostd statusExpected result
Host remains management-reachable and HA sees enough heartbeats.
Corrective actions
- Fix management network before HA reconfiguration.
- Validate cluster capacity before maintenance.
Escalate when
Network/storage split-brain, multiple isolated hosts or double-start VM risk.
End-of-intervention checklist
- Verify vCenter alarms returned green.
- Check datastore, host and VM after fix.
- Retest network/Tools/application from affected VM.
- Document snapshot, migration or infrastructure change.
- Monitor backup/HA tasks after intervention.