Lab: Troubleshoot VCF Operations Adapter and Verify Ops for Logs Syslog
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
| System | Username | Password |
|---|---|---|
| VCF Operations | admin | Holodeck documented default (Post Deployment table) |
| VCF Operations for logs | admin | Set during deployment (VCF Operations for logs is not among the components on the Holodeck 9.0 overview page, vmware.github.io/Holodeck/9.0) |
| vCenter | administrator@vsphere.local | Holodeck documented default (Post Deployment table) |
Tasks
Task 1 Troubleshoot VCF Operations vCenter Adapter
manageabilityThe 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.
VCF Operations: Administration > Integrations → the vCenter account. Check its status. Healthy adapter shows green checkmark with 'Collecting' status.
If adapter shows 'Not Collecting' or red status: Click adapter → View Details. Check error message. Common issues: invalid credentials, certificate mismatch, network connectivity.
Test adapter connectivity: Click 'Test Connection'. This validates vCenter FQDN resolution, port 443 access, and credential authentication.
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.
If adapter was reconfigured or vCenter certificate changed: Edit adapter → update credentials → re-accept certificate. Save and wait for next collection cycle.
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.
Validation Gate
Check: vCenter adapter is healthy and collecting metrics
Expected: Adapter status green. Collection stats show consistent data flow.
Common Errors
Task 2 Configure and Verify VCF Operations for Logs Syslog Ingestion
manageabilityCentralized 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.
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'.
Alternatively, configure via ESXCLI: ssh root@esxi → esxcli system syslog config set --loghost='udp://<ops-for-logs-fqdn>:514' && esxcli system syslog reload.
Configure vCenter syslog: VAMI (https://vcsa:5480) → Syslog → Add syslog server: Protocol=UDP, Server=<ops-for-logs-fqdn>, Port=514.
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.
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.
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.
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
Task 3 Troubleshooting Workbench and Log Assist
manageabilityThe 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.
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.
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).
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.
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).
Review bundle contents: Extract and examine key files — collector.log (data collection issues), analytics.log (capacity/alert engine), adapter logs (per-adapter connectivity).
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
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
- Why is syslog over TCP preferred over UDP for production environments?
- How does the Troubleshooting Workbench (exam: Observability Workbench) shorten MTTR compared with checking metrics and logs separately?
- 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
References
- VCF 9.0 documentation — VCF Operations Support Bundles (p.4243-4244)Tier 1 — Official
- VCF 9.0 documentation — Troubleshooting Using Troubleshooting Workbench (p.3912)Tier 1 — Official
- VCF 9.0 documentation — Use Log Assist to Accelerate Your Support Cases (p.3909-3912)Tier 1 — Official
- VCF 9.0 documentation — VCF Operations for logs integration and Log Collections (p.1316)Tier 1 — Official