Academy/vSphere Foundation 9.0 Support (2V0-18.25)/Lab: Collect Support Bundle & Analyze Logs
This lab targets VCF 9.0

Lab: Collect Support Bundle & Analyze Logs

VCF 9.0Intermediatevcp-foundation⏱ 90 min

VVF 9.0 support lab (2V0-18.25). Built for a Holodeck VVF instance.

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

SystemUsernamePassword
vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)
VCF OperationsadminHolodeck documented default (Post Deployment table)
Nested ESX hostsrootHolodeck documented default (Post Deployment table)

Tasks

Task 1 Collect, read and transfer support bundles

Support bundle collection is the first step in any troubleshooting engagement. Knowing which bundle to collect, when to collect it, and how to analyze the contents separates reactive firefighting from systematic root cause analysis.
Step 1

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).

Step 2

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).

Step 3

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.

Step 4

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.

Step 5

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

Collecting support bundle AFTER restarting the failed service
Fix: Restarting a service clears in-memory state and may rotate logs. Always collect the support bundle BEFORE any remediation action. The bundle captures the current state — restart erases the evidence. This is the #1 mistake that makes root cause analysis impossible.
Collecting only the ESXi bundle when the issue involves vCenter
Fix: Match the bundle to the component: ESX issue → Export System Logs on the host (vm-support). vCenter issue → Export System Logs on the vCenter instance with 'Include vCenter Server and vSphere UI Client logs'. VCF Operations or Operations for logs issue → their own support bundles. In VVF 9.0 there is no NSX Manager or SDDC Manager (VCF-only components, VCF 9.0.1 docs p.1264). Platform-wide issue → collect all of the above, or let Log Assist gather them for the case. Incomplete log collection leads to 'need more data' back-and-forth with support.
Not filtering log analysis by time window
Fix: Support bundles contain weeks of logs. Searching the entire bundle is time-consuming and produces noise. First identify the incident timestamp (from vCenter events, user report, or monitoring alert), then filter logs to a window of +/- 30 minutes around the incident. Key log locations: /var/log/vmkernel.log (ESXi), /var/log/vmware/vpxd/vpxd.log (vCenter).
Sending uncompressed bundles to support
Fix: ESXi vm-support bundles can be 500MB+. vCenter bundles can exceed 1GB. Always compress before transfer. The support bundle tools produce .tgz format by default — do not extract and re-upload individual files unless support specifically requests them.

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

⚠ Known Pitfalls

Collecting support bundle AFTER restarting the service — this is the single most common mistake that prevents root cause analysis.
Sending unfiltered 1GB+ bundles to support without identifying the incident time window — causes delays.

References

Was this page useful?
Type to search. ↑ ↓ to move, Enter to open, Esc to close.