← Back to posts
Networking

Nexus Dashboard: Unified Visibility for Your Cisco Data Center Fabric

What Is Nexus Dashboard?

Nexus Dashboard (ND) is Cisco’s unified management and orchestration platform for data center infrastructure. It replaced the aging DCNM (Data Center Network Manager) and serves as the control plane for:

  • Nexus Dashboard Fabric Controller (NDFC) — formerly DCNM, manages NX-OS and VXLAN fabrics
  • Nexus Dashboard Insights (NDI) — real-time telemetry and anomaly detection
  • Nexus Dashboard Orchestrator (NDO) — multi-site ACI policy management

Think of Nexus Dashboard as the operating system, and NDFC/NDI/NDO as applications running on top of it.

Deployment Options

Nexus Dashboard runs as a cluster — minimum 3 nodes for production. You have three deployment paths:

ModeWhereBest For
Physical (SE)UCS / bare metalLarge enterprises
Virtual (OVA)VMware ESXiMost deployments
CloudAWS / AzureHybrid scenarios
# Check cluster health post-deployment
nd cluster health
nd cluster nodes

All nodes must have L2 adjacency for the management network. Don’t put them across routed boundaries.

Nexus Dashboard Insights: The Real Value

NDI is where the platform earns its keep. It collects telemetry from your fabric using:

  • Streaming telemetry (gNMI/gRPC) from Nexus switches
  • Flow telemetry for microsegmentation visibility
  • SNMP as a fallback for older devices

What it gives you:

  • Anomaly detection — flags deviations from baseline behavior (unusual flows, interface errors, unexpected adjacencies)
  • Assurance — verifies your policy intent matches actual fabric behavior
  • Bug scan — checks your running software against Cisco’s known bug database

This last one is underrated. NDI can tell you “3 of your switches are running a version with a known memory leak in BGP” before you find out the hard way.

Multi-Site with NDO

If you’re running multiple ACI fabrics or VXLAN sites, Nexus Dashboard Orchestrator lets you stretch policy across them. Define a tenant, VRF, or EPG once — NDO pushes it to all registered sites.

Site A (ACI) ─┐
               ├─ NDO (policy sync) ─ Consistent policy everywhere
Site B (ACI) ─┘

The key concept is schema — a container for templates that get deployed to one or more sites. Changes to the schema propagate automatically.

Upgrades: Proceed With Caution

Nexus Dashboard upgrades are sequential — you can’t skip major versions. Always:

  1. Check the Upgrade Guide for your specific version path
  2. Take a full backup before starting (Admin → System Settings → Backup)
  3. Upgrade ND platform first, then services (NDFC, NDI, NDO)
  4. Validate cluster health between each step
# Pre-upgrade health check
nd cluster health
nd services status

Failing to follow the sequence is the #1 cause of broken deployments.

Bottom Line

Nexus Dashboard is a significant improvement over DCNM once you get past the initial learning curve. The insights and assurance capabilities alone justify the deployment — knowing your fabric’s state with confidence is worth the operational overhead.

Start with NDFC for basic fabric management, add NDI when you want real observability, and layer in NDO if you have multi-site requirements.

// Found this useful? Share it or start a conversation.