Academy/VCF 9.0 Support (2V0-15.25)/VCF Operations for vSphere Foundation
This lab targets VCF 9.0

VCF Operations for vSphere Foundation

VCF 9.0Beginnersupportadmin⏱ 60 min

VCFFTS9 course content — VCF 9.0 focused. VCF Operations scope in VVF vs VCF.

Objectives

  • Navigate VCF Operations Console Launchpad and inventory tree in VVF context
  • Monitor vSAN health and capacity using vSAN Insights and Storage Operations Dashboard
  • Use Infrastructure Security and Log Analysis tools available in VVF
  • Identify which VCF Operations capabilities unlock when upgrading from VVF to VCF
  • Configure log-based alerts and diagnostic bundle transfer via Log Assist
  • Understand GPU monitoring capabilities in VVF environments

Prerequisites

Active Holodeck VCF 9.0 lab or access to VCF Operations documentation

Prior labs: vcffts9-02, vcffts9-07

Required skills:

  • Basic VMware terminology
  • Web UI navigation

Tasks

Task 1 VCF Operations Console Navigation for VVF

Foundation navigation task. Panelists probe: What is different in the VVF Operations Console vs full VCF? What management tasks require vSphere Client instead of Operations Console?

Learn the VCF Operations Console as the primary management interface for VVF, understanding what is visible and what is absent compared to full VCF.

Step 1
Launchpad Overview

Access VCF Operations Console at https://<vcf-ops-fqdn>. The Launchpad is the landing page showing quick-access tiles for common operations. In VVF, the Launchpad is simplified: tiles for vCenter management, vSAN monitoring, VKS cluster management, and system health. Compare: full VCF Launchpad adds tiles for NSX monitoring, SDDC Manager operations, fleet management, and VCF Automation. Document which tiles are present and which are absent.

Step 2
Inventory Tree Navigation

Navigate to the Inventory section in the left navigation pane. VVF inventory tree shows: vCenter instances (one or more), Clusters, Hosts, VMs, Datastores, and Networks (standard/distributed port groups only). Absent in VVF: NSX Manager nodes, Transport Zones, Logical Switches, Edge clusters, SDDC Manager. This reflects the VVF component scope: vSphere, vSAN, VKS, VCF Operations only.

Step 3
Dashboard Overview

Explore the monitoring dashboards available in VVF: Overview Dashboard (environment health summary), Compute Dashboard (CPU/memory utilization across hosts), Storage Dashboard (vSAN capacity and performance), Network Dashboard (limited to DVS monitoring, no NSX overlay metrics). Each dashboard provides real-time and historical data. Document the refresh interval and data retention period.

Step 4
System Configuration

Navigate to Administration settings. Configure: (a) data collection interval for metrics, (b) alert notification targets (email, webhook), (c) user access management (local users and AD/LDAP integration), (d) certificate management for VCF Operations. Document: VCF Operations in VVF does not have fleet management capabilities (managing multiple VVF/VCF instances from a single console — this requires full VCF).

Validation Gate

Check: Complete navigation of VCF Operations Console with VVF-specific documentation

Expected: All VVF-available sections documented, absent VCF-only sections identified.

Common Errors

Looking for NSX monitoring in VVF Operations — NSX is not deployed in VVF
Expecting VCF fleet functions (lifecycle, certificates, passwords) in a VVF deployment — in VCF 9.0 these run from VCF Operations fleet management, which VVF does not include
Confusing VCF Operations (monitoring and admin console) with VCF Automation (self-service portal)

Task 2 vSAN Monitoring & Storage Operations

Operational monitoring task. Panelists ask: How do you monitor vSAN in VVF vs VCF? What capacity planning tools are available? Where in VCF Operations do you model growth (What-If Analysis) rather than calculating by hand?

Use VCF Operations vSAN-specific monitoring tools to assess storage health, capacity planning, and performance in the VVF environment.

Step 1
vSAN Insights Dashboard

Navigate to vSAN Insights in VCF Operations. This dashboard provides: cluster health overview (green/yellow/red), disk health status for all devices, object compliance status (FTT policy adherence), and capacity trending. Key metrics to monitor: used capacity percentage (alert at 70%), disk health SMART indicators, resync activity (indicates ongoing rebuild), and deduplication/compression savings ratio. Document current values for each metric.

Step 2
Storage Operations Dashboard

Access the Storage Operations Dashboard for detailed vSAN analytics. Available views: (a) capacity breakdown (raw, used, free, slack, metadata), (b) IOPS and throughput per datastore, (c) latency metrics (read/write average and peak), (d) per-VM storage consumption (thin provisioning actual vs provisioned), (e) storage policy compliance (which VMs meet their assigned FTT policy). Use this dashboard for capacity planning: project when the cluster will reach 70% based on current growth rate.

Step 3
vSAN Health Checks via Operations Console

Run vSAN health checks from VCF Operations (complements the vSphere Client vSAN health view). Check categories: Network (vSAN VMkernel connectivity between hosts), Physical Disk (device health, firmware currency), Data (object health, component placement), Limits (maximum components per host, maximum hosts per cluster). Document any warnings and create remediation plans for each.

Step 4
Capacity Planning & Forecasting

Use VCF Operations capacity tools to forecast vSAN growth. Steps: (a) review historical capacity usage (30/60/90 day trends), (b) identify growth rate (GB/month), (c) project when cluster will reach 70% threshold, (d) calculate hosts needed for expansion (each host adds X TB raw capacity). Document the capacity forecast and expansion timeline. Use VCF Operations Capacity → Plan → What-If Analysis to model added workloads or hosts in VVF and VCF alike (VCF Operations is the former Aria Operations; there is no separate, more capable product).

Validation Gate

Check: Complete vSAN monitoring assessment with capacity forecast

Expected: vSAN health verified, current metrics documented, capacity forecast with expansion timeline created.

Common Errors

Not monitoring vSAN capacity trending — sudden growth from new workloads can exceed thresholds unexpectedly
Ignoring SMART disk health indicators — proactive replacement prevents data-at-risk scenarios
Looking for 'Aria Operations' as a separate, more capable tool — VCF Operations is its 9.0 name and includes What-If Analysis in VVF and VCF

Task 3 Security, Logging & GPU Monitoring

Operational tooling task. Panelists ask: What security monitoring is possible without NSX? How do you troubleshoot without centralized log management?

Use the security monitoring, log analysis, and GPU capabilities available in VVF Operations to maintain operational visibility.

Step 1
Infrastructure Security Dashboard

Navigate to Infrastructure Security in VCF Operations. In VVF, security monitoring covers: ESXi host security posture (SSH access, lockdown mode, password policy), vCenter security configuration (SSO policies, certificate status, role assignments), and vSAN encryption status (if enabled). Compare: full VCF adds NSX DFW security monitoring, micro-segmentation compliance, and network traffic flow analysis. Document current security posture and any findings that need remediation.

Step 2
Log Analysis & Alerts

Access Log Analysis tools in VCF Operations. Available capabilities: (a) centralized log collection from vCenter and ESXi hosts, (b) log search with filters (time range, source, severity), (c) log-based alert creation (trigger alerts based on specific log patterns), (d) Log Assist for creating and transferring diagnostic bundles to VMware support. Configure a sample log-based alert: trigger when vCenter shows 'vpxd crash' pattern in logs. Set notification to email.

Step 3
Log Assist for Diagnostic Bundles

Practice using Log Assist for troubleshooting workflows. Prerequisites: VCF Operations licensing registered in Connected Mode, Log Assist activated on a unified cloud proxy (a VVF deployment includes no cloud proxy by default — Table 812, p.1265 — so add one first) and inventory objects assigned under Log Assist Assignment; the transfer needs a Broadcom support case ID. The docs state that the Diagnostic Findings capability has no licence dependency and works on vSphere Foundation as well as VCF (VCF 9.0.1 docs p.3897); Diagnostic Findings provide a shortcut to Log Assist (p.3892, p.3902), but Log Assist licensing for VVF is not stated there, so record what your environment shows. Log Assist: (a) collects logs from multiple VVF components (vCenter, ESX hosts, VCF Operations), (b) packages into a diagnostic bundle, (c) enables secure transfer to VMware/Broadcom support for SR analysis. Steps: select components to include, define time range for log collection, generate bundle, download or transfer. Document: bundle size, components included, and transfer options.

Step 4
GPU Monitoring (if applicable)

If GPU-equipped hosts exist in the VVF environment, navigate to GPU Metrics dashboard. Available metrics: GPU utilization percentage, GPU memory usage, GPU temperature, VM-to-GPU assignment mapping. GPU monitoring is available in both VVF and VCF. For environments without GPUs, document: what GPU monitoring would show if GPUs were present, and which workloads benefit from GPU acceleration (AI/ML inference, VDI graphics, scientific computing).

Step 5
Security Operations Dashboard

Access the Security Operations Dashboard for aggregated security status. Review: (a) overall security compliance score, (b) hosts with security findings (SSH enabled, lockdown mode disabled), (c) certificate expiry tracking, (d) vulnerability assessment status. Create a security remediation plan: prioritize findings by severity, assign remediation actions, set target dates. Document: VVF security monitoring focuses on infrastructure hardening; VCF adds network security (NSX DFW) and application-level security monitoring.

Validation Gate

Check: Security assessment completed, log alerts configured, diagnostic bundle tested

Expected: Infrastructure security posture documented, log-based alert active, Log Assist bundle generated.

Common Errors

Expecting NSX DFW security monitoring in VVF — DFW is not deployed in VVF, so no micro-segmentation visibility
Not configuring log-based alerts for critical events — miss early warning signs of component failures
Overlooking certificate expiry tracking — expired certificates cause cascading authentication failures

Task 4 VVF to VCF Operations Expansion & VCDX Context

Comparative analysis with design implications. Panelists ask: What monitoring gaps exist in VVF? When do those gaps become unacceptable? How does the upgrade change operations team responsibilities?

Understand exactly what additional VCF Operations capabilities unlock when upgrading from VVF to full VCF, and position this in VCDX design context.

Step 1
Capabilities Unlocked by VCF Upgrade

Document the VCF Operations capabilities that unlock after VVF-to-VCF converge: (a) NSX monitoring — transport node health, DFW rule effectiveness, overlay network performance, (b) VCF Operations fleet management — lifecycle task status, certificate and password management health, compliance drift (SDDC Manager is the per-instance service behind these, p.1347), (c) Fleet management — manage multiple VCF instances from a single VCF Operations console, (d) VCF Automation integration — catalog item usage analytics, project quota monitoring, tenant health, (e) Unified tag management — consistent tagging across vSphere, NSX and the VCF Operations/Automation components for governance.

Step 2
Operational Impact Assessment

Analyze how VCF upgrade changes daily operations: (a) monitoring scope expands (more components = more alerts = more operational overhead), (b) troubleshooting complexity increases (NSX adds overlay network layer to diagnose), (c) security monitoring deepens (DFW micro-segmentation adds granular visibility), (d) lifecycle management automates (VCF Operations fleet management drives patching and upgrades across the instance). Net assessment: VCF requires more skilled staff but provides more automation and visibility.

Step 3
Monitoring Gap Analysis

Identify monitoring gaps in VVF that VCF addresses: (a) no east-west traffic visibility (no DFW, no IPFIX flow monitoring), (b) no overlay network monitoring (no Geneve tunnel health), (c) no automated lifecycle monitoring (no fleet-management lifecycle task tracking), (d) no multi-instance fleet view (each VVF instance monitored independently). For each gap, assess: is this gap acceptable for the current environment? At what scale or compliance requirement does this gap become unacceptable?

Step 4
VCDX Design Positioning

Prepare design recommendations: (a) VVF Operations is sufficient for single-site, single-cluster environments without compliance-driven micro-segmentation monitoring, (b) VCF Operations is required when: multiple workload domains need unified monitoring, NSX security compliance requires DFW effectiveness reporting, fleet management across sites is needed, or self-service portal analytics are required. Document as design decision: D-OPS-001 with RCAR format justifying VVF Operations vs VCF Operations selection.

Step 5
Upgrade Transition Planning

Design the operations team transition plan for VVF-to-VCF upgrade: (a) pre-upgrade: train team on NSX concepts and VCF Operations fleet management (lifecycle, certificates, passwords), (b) during upgrade: expand monitoring dashboards, configure new alert policies for NSX and the fleet-management components, (c) post-upgrade: establish new operational runbooks covering NSX troubleshooting, lifecycle operations from VCF Operations fleet management (lifecycle, certificates, passwords), and expanded security monitoring. Document training requirements and timeline.

Validation Gate

Check: VCF Operations expansion analysis complete with VCDX design positioning

Expected: Capabilities comparison documented, monitoring gaps assessed, transition plan created, design decision D-OPS-001 prepared.

Common Errors

Assuming VVF Operations is identical to VCF Operations — VVF is a significant subset with important monitoring gaps
Not planning for increased operational overhead after VCF upgrade — more components = more alerts = more staff training
Overlooking the training requirement for NSX concepts — operations team needs new skills before VCF converge
Not documenting monitoring gaps as design decisions — these gaps should be explicitly accepted or mitigated

Final Validation

Complete VCF Operations for VVF with monitoring, security, and VCF expansion analysis

✓ Console navigation mastered → All VVF sections explored, absent VCF sections identified

✓ vSAN monitoring configured → Health checks, capacity forecast, and alerts documented

✓ Security assessment complete → Infrastructure security posture reviewed, log alerts configured

✓ VCF expansion understood → Capabilities unlocked by VCF upgrade documented

✓ VCDX design prepared → Design decision D-OPS-001 with monitoring gap analysis

Cleanup / Restore

• Save security assessment report

• Document VCF Operations configuration settings

• Export dashboard screenshots for study notes

• Revert to snapshot if configuration changes were made

Design Reflection (VCDX)

VCF Operations scope analysis demonstrates understanding of operational monitoring requirements at different VCF deployment scales. The monitoring gap analysis maps directly to compliance and operational maturity requirements. This is a key VCDX competency: matching tooling to requirements.

Requirements

  • R-001: Operational monitoring must cover all deployed VCF/VVF components
  • R-002: Security monitoring must meet organizational compliance requirements
  • R-003: Capacity planning must provide 90-day forecasting capability

Constraints

  • VVF Operations lacks NSX monitoring and the VCF fleet-management functions (lifecycle, certificates, passwords)
  • VVF does not support fleet management across multiple instances
  • Log-based alerts are the primary proactive monitoring mechanism in VVF

Assumptions

  • Current VVF environment does not require micro-segmentation monitoring
  • Operations team has basic vSphere monitoring skills
  • Compliance requirements will expand to include network security monitoring within 12 months

Risks

  • Monitoring gaps in VVF may delay detection of security incidents — assess risk vs compliance requirements
  • Operations team unfamiliar with expanded VCF monitoring may miss critical alerts after upgrade
  • Capacity forecasts that bypass VCF Operations What-If Analysis and are done by hand introduce human error

Self-Assessment Discussion Prompts

  1. At what point do VVF monitoring limitations become a compliance risk?
  2. How would you bridge the VVF monitoring gap without upgrading to VCF?
  3. What is the minimum operations team size for managing VVF vs VCF?
  4. How does VCF Operations fleet management change the architecture for multi-site deployments?

Extensions

Custom Dashboard Creation

Create a custom VCF Operations dashboard for VVF that combines vSAN health, compute utilization, and security posture in a single view. Practice dashboard design for executive stakeholders vs operations team audiences.

What-If Analysis Exercise

In VCF Operations go to Capacity > Plan > What-If Analysis and click New to see the seven planning panes. Run a Workload Planning: Hyperconverged scenario that adds 20 VMs to the VVF vSAN cluster, then an Infrastructure Planning: Hyperconverged scenario that adds one host. Record whether the workload fits and when capacity runs out. Finally open the Committed Scenarios tab and commit one scenario to see how reserved capacity changes the cluster capacity view.

Automated Health Reporting

Build an automated weekly health report using VCF Operations data. Include: vSAN health summary, capacity trending, security findings, and recommended actions. Export as PDF or email format for stakeholder distribution.

⚠ Known Pitfalls

Assuming VCF Operations in VVF has the same depth as full VCF Operations — VVF is a subset with no NSX, no SDDC Manager, and no fleet management monitoring
Not configuring log-based alerts in VCF Operations — without proactive alerting, the console is only useful for reactive troubleshooting
Overlooking GPU monitoring capabilities — VVF supports GPU metrics which are valuable for AI/ML and VDI workloads
Not planning operations team training before VCF converge — expanded monitoring scope requires new skills for NSX, SDDC Manager, and Automation troubleshooting

References

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