Lab: Collect Support Bundle & Analyze Logs
Objectives
- Collect a vCenter and ESX support bundle with Export System Logs and confirm each covers the incident window (Obj 5.8)
- Locate vmkernel.log, hostd.log and vpxd.log in the bundles and extract the incident-window errors
- Transfer a bundle to a Broadcom support case with Log Assist and record the transfer
Prerequisites
Holodeck VVF 9.0 instance running; a reproducible incident (for example a failed vMotion or a stopped service) in the last hour; VCF Operations with Log Assist on a unified cloud proxy if the Log Assist step is done
Lab Environment
Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF; -vSANMode OSA by default, ESA where the physical layer supports it): vCenter managing one vSAN cluster of nested ESX hosts, plus VCF Operations. VVF has no SDDC Manager and no NSX.
Credentials
| System | Username | Password |
|---|---|---|
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
| VCF Operations | admin | Holodeck documented default (Post Deployment table) |
| Nested ESX hosts | root | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Collect, read and transfer support bundles
In the vSphere Client, go to Hosts and Clusters, right-click the vCenter instance (or an individual ESX host) and select Export System Logs. Select the hosts to include and tick 'Include vCenter Server and vSphere UI Client logs' (VCF 9.0.1 docs p.1788: the ESX bundle is collected from Hosts and Clusters > right-click the host > Export System Logs).
Leave the defaults (or set a password for encrypted core dumps if the vSAN datastore is encrypted), click Finish and choose a download location. Wait for the collection to complete; the download is a .zip holding the vCenter bundle and one esx-*.tgz per host (file pattern esx.date_and_time.tgz).
Extract the archive. Review the host logs var/run/log/vmkernel.log and var/run/log/hostd.log, and the vCenter log var/log/vmware/vpxd/vpxd.log, filtered to the incident window (±30 minutes). vsanmgmtd.log is an ESX host log, found in the host bundle.
In VCF Operations open Administration > Control Panel and, on the Log Assist card, click Initiate a Transfer. Select the affected object from the VCF inventory tree (down to ESX host level — a dimmed object has no unified collector mapped; fix that under Infrastructure Operations > Configurations > Log Assist Assignment), click Next for the connectivity validation, enter the Broadcom support case ID and start the transfer (VCF 9.0.1 docs pp.3910-3911). Log Assist needs Connected mode and a unified cloud proxy with Log Assist activated.
Export a summary: list the 5 most significant errors with timestamps for the support case, and note the Log Assist transfer ID from Transfer/Download History.
Validation Gate
Check: Collect the vCenter bundle and at least one ESX host bundle with Export System Logs; verify each is complete (non-zero size) and covers the incident window; complete one Log Assist transfer to a case.
Expected: Bundles collected: vCenter bundle plus one esx-*.tgz per selected host, each covering the incident window and not truncated; Log Assist shows the transfer completed and linked to the case. (VVF has no NSX Manager or SDDC Manager — those bundles are VCF only.)
Common Errors
Final Validation
Gate: every check below passes with the evidence recorded in the lab log.
✓ vCenter bundle and one esx-*.tgz per selected host downloaded → Each bundle non-zero, covers the incident window
✓ Five significant errors listed with timestamps → Taken from vmkernel.log, hostd.log or vpxd.log in the bundles
✓ Log Assist transfer (if done) → Transfer/Download History shows it completed against the case ID
Cleanup / Restore
• Delete the downloaded bundles from the workstation once the case is closed (they contain host configuration and logs)
Design Reflection (VCDX)
Troubleshooting methodology is part of operational design. VCDX panelists may ask about your log collection strategy, incident response procedures, and how you ensure root cause analysis is possible after remediation.
Requirements
- Collect appropriate support bundles for each component
- Filter log analysis to incident time window
- Preserve evidence before remediation
Constraints
- Bundle must be collected before service restart
- Bundle size can be large — compress before transfer
- Log retention varies by component — collect promptly
Assumptions
- SSH access is available for bundle collection
- Storage space available for bundle collection on each component
Risks
- Evidence loss from restarting services before bundle collection
- Incomplete analysis from collecting wrong component's bundle