VCF 9 ESXi monitoring and troubleshooting commands cheat sheet
Inspect ESXi 9 identity, resources, networking, storage and time when investigating a VCF workload issue.
ESXi 9 host in a VCF 9 environment. Commands are read-only inspection examples; privileges and available namespaces vary by release.
Updated · VMware VCF · 6 min read
| Command | What it does |
|---|---|
vmware -v | Identify the hypervisor version |
esxcli system uptime get | Inspect host uptime |
esxcli network ip interface list | Inspect VMkernel interfaces |
esxcli network nic list | Inspect physical network adapters |
esxcli storage filesystem list | Inspect mounted filesystems and capacity |
esxcli storage core path list | Inspect storage path states |
esxtop | Observe live host resource usage |
Walkthrough
Use authorized ESXi Shell or SSH access to the affected host. Confirm the management context and maintenance policy before collecting output; host information and logs can contain sensitive data.
Step 1: Identify the hypervisor version
vmware -v
Record the installed ESXi product version and build. Compare the host with the VCF supported bill of materials before interpreting a command result or planning a change.
Step 2: Inspect host uptime
esxcli system uptime get
Compare the uptime with the incident timeline and planned maintenance. A recent reboot can explain an interruption but does not establish its cause; correlate events and logs.
Step 3: Inspect VMkernel interfaces
esxcli network ip interface list
Identify management, vMotion and storage VMkernel interfaces and their state. Compare MTU and service topology with the design; an interface being enabled does not prove end-to-end connectivity.
Step 4: Inspect physical network adapters
esxcli network nic list
Compare link status and speed with the intended uplinks and switch ports. A down link can be expected for an unused adapter; verify the host design before treating it as a fault.
Step 5: Inspect mounted filesystems and capacity
esxcli storage filesystem list
Find the datastore and compare mount state, free space and total size. A mounted datastore can still experience latency or path failures; correlate with storage paths and vCenter performance data.
Step 6: Inspect storage path states
esxcli storage core path list
Compare device identifiers, adapters and path states with the expected multipath design. An inactive standby path may be intentional; inspect the path policy and array design before drawing conclusions.
Step 7: Observe live host resource usage
esxtop
Run interactively and consult the ESXi version-specific documentation for display keys and counters. Compare sustained CPU, memory, disk and network pressure with a baseline; one sample does not establish the source of a VM performance issue.
WORKED INCIDENT
Practical case: A datastore workload becomes slow
Fictional teaching scenario; observations are examples, not captured production output.
Situation
A VM on one host shows storage latency while other services remain online.
Investigation sequence
1. Identify the hypervisor version
vmware -vRecord the host version and build for correlation with the VCF inventory.
2. Inspect mounted filesystems and capacity
esxcli storage filesystem listCheck that the relevant datastore is mounted and has available capacity.
3. Inspect storage path states
esxcli storage core path listCompare storage path states with the approved multipath design.
4. Observe live host resource usage
esxtopObserve sustained storage latency and resource behavior during an approved incident window.
Example findings
Example: the datastore remains mounted, but a required path is unavailable and latency is elevated over several samples.
Interpret the findings
A path issue is a plausible contributor, but a mounted datastore or one inactive path alone does not prove root cause. Correlate array health, path policy and latency across hosts.
Verify the outcome
After the storage owner resolves the approved issue, compare path state and performance over time and verify the affected workload.
Escalation handoff
Provide host build, datastore identifier, timestamps, path states and performance samples to the virtualization and storage teams.
Broadcom ESXCLI storage reference
Broadcom ESXCLI network reference