Lab: Configure VCF Operations with NSX Adapter and Custom Dashboards
Objectives
- Add NSX adapter to VCF Operations for network topology monitoring
- Create custom dashboard with NSX-aware widgets (DFW analytics, segment health)
- Configure cross-component correlation between vCenter, NSX, and vSAN metrics
- Differentiate metrics, properties, and logs with hands-on examples
Prerequisites
VCF management domain with VCF Operations deployed and NSX Manager operational
Prior labs: vcp-admin-01
Required skills:
- VCF Operations UI
- NSX Manager basics
Lab Environment
Holodeck VCF pod with management domain, NSX Manager cluster, VCF Operations.
Credentials
| System | Username | Password |
|---|---|---|
| VCF Operations | admin |
Tasks
Task 1 Add the NSX Account and Verify Network Metrics Collection
manageabilityNSX adapter enables network topology visualization and DFW analytics — key VCF-only capability not in VVF.
In VCF Operations go to Administration > Integrations, open the Accounts tab, click Add and choose NSX. Enter a Name, the NSX Manager VIP/FQDN and a credential: either NSX Credentials (a dedicated read-only user such as one with the Auditor role, which collects all data except the load balancer) or NSX Client Certificate Credentials (Principal Identity). Select the collector group, click Validate Connection, accept the certificate if prompted, then Add. In a VCF instance the NSX account may already exist from the instance connection — review it rather than adding a duplicate.
Wait a few collection cycles (5-minute cycles; allow 10-15 minutes). Open the NSX adapter instance object (Environment > Object Browser, or the account's object link) and verify Tier-0/Tier-1 gateways, segments, Edge nodes and transport nodes appear with metrics beginning to populate.
Confirm the NSX management pack dashboards are available: Visualize > Dashboards, filter on 'NSX'. The management pack ships NSX Configmax Metrics, NSX Inventory, NSX Edge, NSX Segment Inventory, NSX Transport Node Performance, NSX Segment Performance and NSX Load Balancer Performance dashboards (VCF 9.0.1 docs, 'Dashboards in NSX Management Pack'). The pack is part of VCF Operations in 9.0; no separate content pack install is needed ('Content Pack' is VCF Operations for logs terminology).
Open the NSX Inventory and NSX Edge dashboards. Review the widgets: object counts (gateways, segments, transport nodes), Edge node health and resource utilisation. Then open NSX Configmax Metrics and compare current object counts against the configuration maximums.
Validation Gate
Check: Administration > Integrations > Accounts shows the NSX account collecting; the NSX adapter inventory shows Tier-0 gateway, segments and Edge nodes; the NSX management pack dashboards open with data
Expected: NSX inventory populated with all managed objects and the NSX dashboards show current values
Common Errors
Task 2 Create Cross-Component Dashboard
manageabilityCross-component dashboards demonstrate the VCF Operations value proposition — correlating compute, network, and storage metrics in a single view.
Create new dashboard: 'VCF Infrastructure Health'. Add widgets: (1) Heatmap — hosts by CPU, (2) NSX segment traffic chart, (3) vSAN latency trend, (4) Top-N VMs by network throughput.
Configure widget interactions: Host heatmap → filters NSX segment widget to show segments on selected host. Top-N → links to VM detail.
Add alert list widget filtered to Critical/Immediate alerts across all adapters (vCenter + NSX + vSAN).
Save and share dashboard with operator role (read-only access).
Validation Gate
Check: Dashboard 'VCF Infrastructure Health' loads with all widgets showing data from vCenter, NSX, and vSAN
Expected: Cross-component widgets populated, interactions working
Common Errors
Task 3 Demonstrate Metrics vs Properties vs Logs
manageabilityUnderstanding the three data types is an explicit exam objective. Hands-on differentiation builds exam confidence.
Select any ESXi host → Metrics tab. Identify: CPU Usage % (metric — numeric, changes every 5 min). Note collection interval and retention.
Same host → Properties tab. Identify: ESXi Version (property — static, changes only on upgrade). Note: properties enable filtering and grouping.
Navigate to Operations for Logs → Explore Logs → filter by source = same ESXi host. Identify: Log entry (log — text event, timestamped, used for troubleshooting).
Document the three data types with one example each. This is a common exam question format.
Validation Gate
Check: Can articulate metric vs property vs log with concrete examples from the lab environment
Expected: Clear understanding demonstrated through hands-on exploration
Common Errors
Task 4 Configure Alert Definitions and Notification Channels
availabilityAlert configuration transforms VCF Operations from a passive monitoring tool to an active operational assistant. Proper alerting reduces MTTR and prevents incidents.
From the left menu click Infrastructure Operations > Configurations, then the Alert Definitions tile (VCF 9.0.1 docs p.3224). Review existing alerts for NSX objects. Key alerts: NSX Manager cluster health degraded, Edge node CPU >80%, DFW rule push failure, Transport node disconnected. Enable notification for each critical alert.
Create a custom alert: 'vSAN Capacity Warning'. Configure: Metric=vSAN Used Capacity %, Condition=> 70%, Criticality=Warning, Wait Cycles=3 (confirms trend over 15 min). Add recommendation text: 'Review capacity trending and plan expansion. Check for orphaned snapshots consuming space.'
Configure notifications in two parts. (1) Outbound instances: from Infrastructure Operations > Configurations, click the Outbound Settings tile (VCF 9.0.1 docs p.3206) and add outbound plug-in instances: Standard Email Plugin with your SMTP server, Webhook Notification Plugin for ServiceNow/Jira (or the Service-Now Notification Plugin), and optionally SNMP Trap or Slack. Test each instance before saving. (2) Notification rule: from Infrastructure Operations > Configurations, click the Notifications tile (p.3197), click Add and create a rule that sends Critical and Immediate alerts to ops-team@company.com through the email outbound instance. Documented plug-in types are Log File, Rest Notification (deprecated), Standard Email, SNMP Trap, Webhook Notification, Slack and Service-Now Notification (VCF 9.0.1 docs p.3199, p.3202, p.3205).
Design an alert escalation matrix: Tier 1 (Info/Warning) — dashboard review during daily standup. Tier 2 (Immediate) — email to on-call engineer, 30-minute response. Tier 3 (Critical) — email + webhook to PagerDuty/ServiceNow, 15-minute response. Document the matrix and map VCF Operations alert levels to organizational response tiers.
Validation Gate
Check: Custom alert created, notification channel configured, escalation matrix documented
Expected: Alert fires on threshold breach, notification reaches operations team, escalation matrix ready for production use
Common Errors
Task 5 Create Super Metrics for Cross-Component Analysis
manageabilitySuper Metrics combine data from multiple objects into custom calculated metrics — enabling business-relevant KPIs that no single adapter provides.
From the left menu click Infrastructure Operations > Configuration, then the Super Metrics tile (VCF 9.0.1 docs p.4178). Create a new Super Metric: 'Cluster CPU Overcommit Ratio'. Formula: Sum of VM vCPU across all VMs in cluster / Total physical cores in cluster. Assign to cluster object type.
Create a second Super Metric: 'vSAN Days to 70%'. Formula: (0.70 x Total vSAN capacity - Current used) / Average daily growth (30-day trend). Assign to the vSAN cluster object type. Compare the result with the cluster's native Capacity > Time Remaining value, which is the documented capacity-engine answer to the same question.
Add both Super Metrics to the VCF Infrastructure Health dashboard created in Task 2. Create widgets: Scoreboard showing overcommit ratio (green <2:1, yellow 2-3:1, red >3:1) and Trend chart showing vSAN days to 70% over last 30 days.
Document the Super Metric design pattern for VCDX: (a) identify the business question (When will we run out of capacity?), (b) identify the source metrics (vSAN used, vSAN total, daily growth), (c) define the formula, (d) assign to object type, (e) create dashboard widget, (f) configure alert threshold. This pattern can be applied to any cross-component KPI.
Validation Gate
Check: Super Metrics created, dashboard widgets configured, design pattern documented
Expected: Overcommit ratio and vSAN days to 70% visible on dashboard with color-coded thresholds
Common Errors
Final Validation
VCF Operations fully configured with NSX adapter, cross-component dashboards, alerting, and custom Super Metrics.
✓ NSX adapter collecting data → NSX objects visible in inventory with metrics populating
✓ Cross-component dashboard operational → Widgets from vCenter, NSX, and vSAN with interactions
✓ Metrics/Properties/Logs differentiated → Can articulate differences with concrete examples
✓ Alert configuration complete → Custom alerts, notifications, and escalation matrix documented
✓ Super Metrics providing business KPIs → Overcommit ratio and capacity forecast on executive dashboard
Cleanup / Restore
• Take snapshot 'post-vcf-ops-nsx-dashboard'
• Export dashboard definitions for backup
• Save alert escalation matrix document
• Document Super Metric formulas for knowledge transfer
Design Reflection (VCDX)
Panelist: How does VCF Operations with NSX adapter change your monitoring strategy compared to VVF? What network metrics would you alert on for a multi-tier application?
Requirements
- Unified monitoring across compute, network, and storage
- Proactive alerting with <15 minute response for critical issues
- Business-relevant capacity forecasting for procurement planning
Constraints
- NSX adapter adds additional object count to VCF Operations sizing
- Super Metric calculation increases VCF Operations CPU overhead
- Notification channels require outbound network access (SMTP, webhook)
Assumptions
- NSX Manager accessible from VCF Operations network
- SMTP server available for email notifications
- Operations team trained on alert response procedures
Risks
- Oversized VCF Operations may be needed for large NSX deployments (10,000+ segments)
- Alert fatigue from poorly tuned thresholds reduces response effectiveness
- Super Metric formulas may produce misleading results with incorrect source metrics
Self-Assessment Discussion Prompts
- How would you size VCF Operations for 10,000 NSX segments?
- What DFW metrics indicate a security policy misconfiguration?
- How do you design dashboards for different stakeholder audiences?
- What Super Metrics would you create for a VCDX design review?
Extensions
What-If and Capacity Planning in VCF Operations
VCF Operations (formerly VMware Aria Operations) includes what-if analysis for workload and infrastructure planning (VCF 9.0.1 docs p.5262). Model adding 50 VMs to the management cluster and removing one host, compare the result with the vSAN Days to 70% super metric, and record which gives the more defensible procurement date.
Custom Content Pack Development
Create a custom Content Pack with dashboards tailored to your organization. Include: executive health summary, operations detail view, security compliance dashboard, and capacity planning view. Export and version-control the Content Pack.
VCF Operations API Automation
Use the VCF Operations REST API to automate: dashboard creation, alert configuration, Super Metric definition, and report generation. Build a Python script that deploys a standardized monitoring configuration to new VCF environments.
⚠ Known Pitfalls
References
- VCF Operations NSX Adapter GuideTier 1 — Official