Interactive field lab // ESXi host CLI

ANGRYSYSOPS ESXi CLI OPERATIONS LAB

Master the command line. Own your infrastructure.
Practice ESXi tasks across network, storage, VMs,
logs, security, and host management.

Route the session Open command map

CLI commands33+

Hands-on phases10

AngrySysOps100%

ScenariosReal-world

01 // CONTEXT

Run commands on the right appliance

WHAT SHELL ARE YOU IN?

The same-looking prompt can belong to an ESXi host, the vCenter Server Appliance, or an administrator workstation. This lab teaches commands executed directly in ESXi Shell or over SSH to an ESXi host.

Host CLI route

Direct ESXi observation: the read-only command path is appropriate.

Capture output before changing state. Command availability still varies by release, installed components, and privileges.

Important: `esxcli system service ...` is not a valid ESXi service namespace. `service-control` is a VCSA command, not an ESXi host command. This lab keeps those surfaces separate.

02 // PRE-FLIGHT

Readiness gate

OBSERVE FIRST. CHANGE LAST.

Gate status0 / 8

The simulator stays locked until the execution context, evidence path, and disruptive-action controls are acknowledged.

Correct hostHostname, management IP, cluster, and environment have been verified from more than the shell prompt.

Release help checked`esxcli --help` and command-level `--help` are the final authority on the target build.

Read-only baselineVersion, network, storage, VM, and log state will be captured before a mutation.

Lifecycle ownershipvLCM, VCF, Auto Deploy, NSX, vSAN, and OEM ownership are not being bypassed.

Maintenance windowVM evacuation, console access, storage policy, and rollback or recovery steps are defined.

Agent restart caution`services.sh restart` will not be used on vSAN, NSX, LACP, or shared-graphics hosts.

Evidence destinationCommand output and support bundles have a persistent, capacity-checked destination.

Secret handlingPasswords, keys, tokens, and sensitive support-bundle data will not be exposed in shell history or public tickets.

Complete 8 controls to unlock.

03 // GUIDED LAB

Local command simulation

BUILD AN EVIDENCE-FIRST HOST SNAPSHOT.

Walk through ten phases. The first seven are observational. The final three demonstrate maintenance, reboot, and return-to-service syntax without connecting to a real host.

esx01.angrysysops.com // simulated shellPhase 01 / 10

Identify the host

[sim] Type `help` and press Enter, or complete pre-flight to run guided phases.

0 / 10 complete

04 // COMMAND MAP

Correct syntax with operational context

SEARCH BY TASK, NOT BY MEMORY.

Filter the verified command map. “Read” commands inventory state. “Change” commands alter configuration. “Disruptive” commands can interrupt workloads, management, or the host.

Common bad syntax	Correct approach	Why it matters
`esxcli network vswitch list`	`esxcli network vswitch standard list` `esxcli network vswitch dvs vmware list`	Standard and distributed switches use different namespaces.
`esxcli storage filesystem df`	`esxcli storage filesystem list` `df -h` or `vdf -h` for shell-specific usage views	There is no current ESXCLI `filesystem df` operation.
`esxcli storage core device rescan`	`esxcli storage core adapter rescan --all`	Rescans operate on storage adapters, not the device namespace.
`esxcli system service restart ...`	`/etc/init.d/hostd restart` `/etc/init.d/vpxa restart`	ESXi does not expose the fabricated `system service` syntax.
`esxcli system shutdown reboot`	`esxcli system shutdown reboot --delay=10 --reason="Approved change"`	A reason is required and the host must be in maintenance mode.
`esxcli system time set --date=... --time=...`	`esxcli system time set --year=2026 --month=7 --day=17 --hour=14 --min=30 --sec=00`	The command accepts individual date/time parameters. Prefer NTP for normal operations.
`esxbug.sh`	`vm-support -w /vmfs/volumes/<datastore>`	`vm-support` is the supported ESXi diagnostic collection tool.

05 // FAULT DRILL

Troubleshooting instinct

WHAT DO YOU DO FIRST?

Choose the first useful action, not the most dramatic command.

Fault 1 / 5

Loading...

Select the first investigation point.

06 // EVIDENCE

Close the session

BUILD THE CLI HANDOFF NOTE.

Record what was observed, what changed, and which commands produced the evidence.

Draft evidence note pending.

07 // SOURCE CONTROL

Authoritative references

VERIFY AGAINST THE TARGET RELEASE.

The command map is grounded in the current Broadcom ESXCLI reference and operational KBs. Use the version selector in the command reference and recheck release-specific support guidance before a production change.

ESXCLI system command referenceHostname, NTP, maintenance mode, accounts, encryption, time, shutdown, syslog, coredump, and process namespaces.
ESXCLI network command referenceVMkernel interfaces, physical NICs, firewall rulesets, VM ports, standard switches, distributed switches, and LACP.
ESXCLI storage command referenceFilesystems, adapters, devices, paths, NMP, NFS, NVMe, and adapter rescans.
Common VM tasks via command line`vim-cmd` inventory, power, guest operations, snapshots, registration, and VMware Tools examples.
Restarting management agents in ESXiTargeted `hostd` and `vpxa` restart syntax plus warnings for vSAN, LACP, NSX, and shared graphics.
Collecting ESXi diagnostics with vm-supportSupported host support-bundle collection and destination guidance.
Location and contents of ESXi logsCurrent `/var/run/log` locations and component-specific log purposes.
Using ESXi ShellEnablement, access, timeout, security, and operational policy for direct shell use.

SOURCE SET REVIEWED // 17 JUL 2026 // COMMAND AVAILABILITY VARIES BY ESXI / ESX RELEASE AND INSTALLED COMPONENTS