Academy/vSphere Foundation 9.0 Support (2V0-18.25)/Lab: Troubleshoot VCF Operations Adapter and Verify Ops for Logs Syslog
This lab targets VCF 9.0

Lab: Troubleshoot VCF Operations Adapter and Verify Ops for Logs Syslog

VCF 9.0Advancedvcp-foundation⏱ 90 min

Covers Obj 5.8 (VCF Operations — adapter config, dashboards, Ops for Logs, Troubleshooting Workbench (exam: Observability Workbench), Log Assist). Comprehensive operations troubleshooting.

Objectives

  • Troubleshoot VCF Operations vCenter adapter connectivity and data collection
  • Configure and verify VCF Operations for Logs syslog ingestion
  • Use Explore Logs to search and filter log entries
  • Use the Troubleshooting Workbench (exam guide: Observability Workbench) to find potential evidence
  • Generate and upload a log bundle to a support case with Log Assist
  • Generate support log bundle from VCF Operations

Prerequisites

VVF lab with VCF Operations deployed (or deployable). vCenter operational with workloads running.

Prior labs: vvf-support-01, vvf-support-06

Required skills:

  • VCF Operations UI basics
  • Syslog concepts
  • Log analysis

Lab Environment

Holodeck vSphere Foundation 9.0 instance (New-HoloDeckInstance -VVF) with VCF Operations; VCF Operations for logs deployed from its .ova for this lab and integrated with VCF Operations; vCenter and ESX hosts as syslog sources.

Credentials

SystemUsernamePassword
VCF OperationsadminHolodeck documented default (Post Deployment table)
VCF Operations for logsadminSet during deployment (VCF Operations for logs is not among the components on the Holodeck 9.0 overview page, vmware.github.io/Holodeck/9.0)
vCenteradministrator@vsphere.localHolodeck documented default (Post Deployment table)

Tasks

Task 1 Troubleshoot VCF Operations vCenter Adapter

manageability

The vCenter adapter is the primary data source for VCF Operations. If it fails, no metrics/alerts are collected — diagnosing adapter issues is a core support skill.

Step 1

VCF Operations: Administration > Integrations → the vCenter account. Check its status. Healthy adapter shows green checkmark with 'Collecting' status.

Adapter shows 'Collecting' status with last collection timestamp within 5 minutes.
Step 2

If adapter shows 'Not Collecting' or red status: Click adapter → View Details. Check error message. Common issues: invalid credentials, certificate mismatch, network connectivity.

Error details identify the specific failure reason.
Step 3

Test adapter connectivity: Click 'Test Connection'. This validates vCenter FQDN resolution, port 443 access, and credential authentication.

Test Connection returns 'Success' or specific error code.
Step 4

Check collection stats: Adapter → Collection Status. Review: objects discovered, metrics collected per cycle, collection duration. Collection runs every 5 minutes (VCF 9.0.1 docs p.3088); look for gaps rather than a fixed metric count.

Collection stats show consistent metric count with no gaps.
Step 5

If adapter was reconfigured or vCenter certificate changed: Edit adapter → update credentials → re-accept certificate. Save and wait for next collection cycle.

After vCenter certificate renewal, ALL adapters pointing to that vCenter need certificate re-acceptance. This is a common post-maintenance troubleshooting scenario.
Step 6

Check VCF Operations logs: in the UI (Administration > Support Logs) or on the appliance under /storage/log/vcops/log/ — collector.log and adapters/<adapter>/ (VCF 9.0.1 docs p.4576, p.4634). Look for connection timeout or authentication failure messages.

Log entries show successful collection cycles or specific error messages.

Validation Gate

Check: vCenter adapter is healthy and collecting metrics

Expected: Adapter status green. Collection stats show consistent data flow.

Common Errors

Adapter shows 'Certificate changed' warning
Cause: vCenter SSL certificate was renewed but VCF Operations still has old certificate
Fix: Edit adapter → Test Connection → Accept new certificate → Save. Wait for next collection cycle.
Adapter collecting but no data for specific hosts
Cause: Host was recently added to cluster but adapter hasn't re-discovered inventory
Fix: Adapter → Actions → Force Discovery. Wait 10 minutes for inventory refresh.

Task 2 Configure and Verify VCF Operations for Logs Syslog Ingestion

manageability

Centralized log management via syslog is critical for VVF troubleshooting. Configuring ESXi and vCenter to forward logs, then verifying ingestion in Ops for Logs covers Obj 5.8.

Step 1

9.0 path: in VCF Operations integrate VCF Operations for logs, then use Infrastructure Operations > Configurations > Log Collections on the vCenter to configure its ESX hosts to send syslog (VCF 9.0.1 docs p.1316). Manual alternative per host: Configure → System → Advanced System Settings → Syslog.global.logHost = 'udp://<ops-for-logs-fqdn>:514'.

Syslog host configured on all ESXi hosts.
Step 2

Alternatively, configure via ESXCLI: ssh root@esxi → esxcli system syslog config set --loghost='udp://<ops-for-logs-fqdn>:514' && esxcli system syslog reload.

Syslog configuration updated and reloaded.
Step 3

Configure vCenter syslog: VAMI (https://vcsa:5480) → Syslog → Add syslog server: Protocol=UDP, Server=<ops-for-logs-fqdn>, Port=514.

vCenter syslog forwarding configured.
Step 4

Verify in Ops for Logs: Login → Explore Logs. Set time range to 'Last 15 minutes'. Search for source='esxi' or source='vcsa'. Confirm log entries arriving.

Log entries from ESXi hosts and vCenter visible in Explore Logs.
Step 5

Test with a trigger event: On any ESXi host, restart the hostd service: /etc/init.d/hostd restart. Then search Ops for Logs for 'hostd' — should see restart events within 1-2 minutes.

hostd restart events appear in Ops for Logs with correct timestamp and source host.
Step 6

Create a saved search: In Explore Logs → build query: text CONTAINS 'error' AND source MATCHES 'esxi*' → Save as 'ESXi Errors'. This becomes a reusable troubleshooting filter.

Saved search 'ESXi Errors' available in saved searches list.

Validation Gate

Check: Syslog forwarding active from all sources; logs visible in Ops for Logs

Expected: ESXi and vCenter logs appearing in Explore Logs. Saved search created.

Common Errors

No logs appearing in Ops for Logs despite syslog config
Cause: ESXi firewall blocking outbound syslog (UDP 514)
Fix: SSH to ESXi → esxcli network firewall ruleset set --enabled=true --ruleset-id=syslog. Then: esxcli network firewall refresh.
Logs appear but timestamps are wrong
Cause: NTP not synchronized between ESXi hosts and Ops for Logs appliance
Fix: Verify NTP configuration on all hosts and appliances. Use same NTP source.

Task 3 Troubleshooting Workbench and Log Assist

manageability

The Troubleshooting Workbench (exam guide: Observability Workbench) gathers potential evidence — events, property changes, anomalous metrics — around an object and a time window. Log Assist generates a support bundle for a selected inventory object and transfers it, with diagnostic findings, to a Broadcom support case. Both are new in VCF 9.0 and exam-relevant.

Step 1

Open the Troubleshooting Workbench (exam guide: 'Observability Workbench'): Infrastructure Operations > Troubleshooting Workbench (VCF 9.0.1 docs p.3912), or TROUBLESHOOT from an alert. Search an object (VM or ESX host) or a metric and start a session; set the scope and time range. Review the potential evidence: Events, Property Changes and Anomalous Metrics.

The workbench lists potential evidence (events, property changes, anomalous metrics) for the object and window.
Step 2

Correlate with logs: for an anomalous metric in the evidence list, note its time window, then open Explore Logs in VCF Operations for logs (or Analyze Logs in VCF Operations, VCF 9.0.1 docs p.100) for the same object and window to find the matching log events (VM migration, backup job, service restart).

The workbench's potential evidence is events, property changes and anomalous metrics (p.3913); the logs for the same window explain the 'why'. This evidence-plus-logs workflow is what the exam guide calls the Observability Workbench.
Step 3

Log Assist (bundle transfer to Broadcom Support): confirm VCF Operations is in Connected mode (License Management → Registration). Activate Log Assist on a unified cloud proxy (Administration → Control Panel → Cloud Proxies → ellipsis → Activate Log Assist) and assign objects (Infrastructure Operations → Configurations → Log Assist Assignment, drag and drop). Then Control Panel → Log Assist card → Initiate a Transfer → select the object (down to ESX host level; VMs cannot be selected) → Next (connectivity validation; RE-VALIDATE if it fails) → Transfer to Support Portal tab → enter the Support case ID → Transfer.

Transfer completes and returns to the home page; the bundle is linked to the support case. Any per-object failure is listed under Transfer/Download History (expand the case row for Activity Feed / Log Bundle Details); failed operations are not retried automatically.
Step 4

Generate a VCF Operations support bundle: Administration > Control Panel > Support Bundles tile > Add. Choose Light (last 24 hours of logs) or Full (all logs and configuration files), select the nodes or the cluster, then download the ZIP when it completes (VCF 9.0.1 docs p.4243-4244).

Support bundle generated as a ZIP; size depends on bundle type and node count.
Step 5

Review bundle contents: Extract and examine key files — collector.log (data collection issues), analytics.log (capacity/alert engine), adapter logs (per-adapter connectivity).

Bundle contains organized log files from all VCF Operations components.

Validation Gate

Check: Troubleshooting Workbench session run and its evidence matched to logs for the same window; Log Assist transfer prepared or completed; support bundle generated

Expected: Evidence (events, property changes or anomalous metrics) matched to log entries for the same window. Log Assist cloud proxy activated and object assigned; transfer linked to a case where one exists. Support bundle downloaded.

Common Errors

Expecting log entries inside the Troubleshooting Workbench
Cause: The workbench's evidence types are events, property changes and anomalous metrics; logs are read in VCF Operations for logs or Analyze Logs
Fix: Open Explore Logs (VCF Operations for logs) or Analyze Logs in VCF Operations (p.100) for the same object and time window; integrate VCF Operations for logs with VCF Operations (Administration > Integrations) if log data is missing there.
Log Assist not available
Cause: No unified cloud proxy with Log Assist activated, object not assigned under Log Assist Assignment, VCF Operations not in Connected mode, or missing privileges on the object (KB 375817)
Fix: Register licenses in Connected mode; activate Log Assist on a cloud proxy (the Log Assist adapter runs standalone, not alongside regular collection adapters); assign the object; fix privileges per KB 375817 and RE-VALIDATE. Disconnected (air-gapped) estates cannot transfer bundles to the Support Portal.

Final Validation

VCF Operations adapter healthy, syslog forwarding verified, Troubleshooting Workbench and Log Assist demonstrated

✓ vCenter adapter collecting metrics → Green status with consistent collection stats

✓ Syslog forwarding from ESXi and vCenter → Logs visible in Ops for Logs Explore Logs

✓ Troubleshooting Workbench evidence matched to logs → Evidence for the selected object matched to log entries for the same window

✓ Support bundle generated → ZIP bundle downloaded (Light or Full)

Cleanup / Restore

• Remove any test syslog configurations if not needed for subsequent labs

• Delete generated support bundles to free disk space

Design Reflection (VCDX)

Observability is a key architectural pillar. VCF Operations provides the monitoring layer; Ops for Logs provides the logging layer. Together with the Troubleshooting Workbench (exam: Observability Workbench), they shorten the path from symptom to cause.

Requirements

  • Centralized log collection from all VVF components
  • Correlated metrics-and-logs troubleshooting

Constraints

  • Ops for Logs appliance sizing limits retention period
  • Log Assist requires Connected mode and a unified cloud proxy with Log Assist activated; the transfer goes to the Broadcom Support Portal

Assumptions

  • Syslog UDP 514 is not blocked by host firewalls
  • NTP is synchronized across all components

Risks

  • Syslog over UDP can lose messages during network congestion — consider TCP for critical environments
  • VCF Operations adapter certificate mismatch after vCenter maintenance

Self-Assessment Discussion Prompts

  1. Why is syslog over TCP preferred over UDP for production environments?
  2. How does the Troubleshooting Workbench (exam: Observability Workbench) shorten MTTR compared with checking metrics and logs separately?
  3. What are the retention and sizing considerations for VCF Operations for Logs in a 100-host environment?

Extensions

Configure syslog over TCP (port 1514) for reliable log delivery

Create a VCF Operations dashboard showing adapter health across all integrations

Set up email notification for adapter connectivity failures

Walk the Log Assist transfer flow against a test case: assignment, connectivity validation, Transfer/Download History

⚠ Known Pitfalls

ESXi syslog firewall rule must be explicitly enabled — it's disabled by default on fresh ESXi installs
VCF Operations adapter certificate must be re-accepted after any vCenter certificate change
Expecting log lines inside the Troubleshooting Workbench — its potential evidence is events, property changes and anomalous metrics (p.3913); read the logs for the same window in Explore Logs or Analyze Logs

References

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