> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/switch-infrastructure/config-manager/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/switch-infrastructure/config-manager/_mcp/server.

# Spectrum-X Switch Management

NVIDIA Config Manager supports the day-0 and day-2 management of Spectrum-X
Ethernet switches. A Spectrum-X switch running Cumulus Linux follows the same
provisioning, configuration, validation, and lifecycle workflows as any other
Cumulus Linux switch in Config Manager.

This page is the starting point for Spectrum-X switch support. It summarizes the
management path and links to the detailed operator guides.

## Where Config Manager fits

```mermaid
flowchart LR
    N["Nautobot<br />source of truth"] --> R["Render Service"]
    T["Cumulus Linux<br />configuration templates"] --> R
    R --> C["Config Store<br />versioned intent"]
    C --> Z["DHCP and ZTP<br />day-0 bootstrap"]
    C --> W["Temporal workflows<br />day-2 operations"]
    Z --> S["Spectrum-X switches<br />Cumulus Linux"]
    W <--> S
    W -->|running-config backups| C
```

* **Nautobot is the source of truth.** Device identity, platform, role,
  interfaces, cabling, addressing, tenant data, and config contexts define the
  intended state.
* **The Render Service converts intent into device configuration.** It combines
  Nautobot data with the Cumulus Linux templates selected for the switch role
  and software version.
* **The Config Store versions intended and running configurations.** ZTP and
  deployment workflows consume the rendered intent; backup workflows write
  running-state snapshots for audit and drift detection.
* **DHCP and ZTP handle initial provisioning.** A factory-default switch obtains
  its boot information, installs the intended Cumulus Linux image when needed,
  downloads its rendered configuration, and reports its provisioning state.
* **Temporal workflows handle ongoing operations.** Config Manager reaches the
  switch over the management network to calculate and apply configuration
  changes, collect state, validate the fabric, rotate credentials, and manage
  the switch lifecycle.

The [System Architecture](/switch-infrastructure/config-manager/config-manager/overview/architecture) describes the component model. [Which Interface Should I Use?](/switch-infrastructure/config-manager/getting-started/which-interface-should-i-use) explains the Config Manager UI, Nautobot UI, Temporal Web, and API boundaries.

## Spectrum-X switch workflows

The following workflows are the normal operational path for Spectrum-X
switches. The linked guides contain prerequisites, UI inputs, execution stages,
verification steps, and failure recovery.

| Phase     | Task                                                                                              | Config Manager path                                                                                                                                                                                                                                   |
| :-------- | :------------------------------------------------------------------------------------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Model     | Register switches, interfaces, cabling, addressing, roles, software targets, and config contexts. | [Nautobot Bootstrap](/switch-infrastructure/config-manager/config-manager/nautobot) and [DHCP Modeling in Nautobot](/switch-infrastructure/config-manager/services/dhcp/dhcp-modeling-in-nautobot)                                                    |
| Bootstrap | Provision factory-default switches with the intended Cumulus Linux image and configuration.       | [New Site Bringup](/switch-infrastructure/config-manager/user-guides/new-site-bringup) and [Network ZTP](/switch-infrastructure/config-manager/services/network-ztp/overview)                                                                         |
| Validate  | Compare observed LLDP, FDB, and ARP data with the modeled cabling.                                | [Cable Validation](/switch-infrastructure/config-manager/user-guides/validation/cable-validation)                                                                                                                                                     |
| Validate  | Collect Cumulus platform, environmental, and inventory health across the site.                    | [Cumulus Hardware Validation](/switch-infrastructure/config-manager/user-guides/validation/hardware-validation)                                                                                                                                       |
| Observe   | Identify hosts connected to each switch interface.                                                | [Connected Host Metadata](/switch-infrastructure/config-manager/user-guides/validation/connected-host-metadata)                                                                                                                                       |
| Configure | Review and apply a rendered change to one switch, with human approval of the diff.                | [Configuration Deploy](/switch-infrastructure/config-manager/user-guides/configuration-deploy/configuration-deploy)                                                                                                                                   |
| Configure | Apply a reviewed change across multiple switches with grouped, per-batch approval.                | [Multi-Device Deploy](/switch-infrastructure/config-manager/user-guides/configuration-deploy/multi-device-deploy)                                                                                                                                     |
| Audit     | Capture running configurations and compare them with intended state.                              | [Configuration Backup](/switch-infrastructure/config-manager/user-guides/configuration-deploy/configuration-backup) and [Site Configuration Backup](/switch-infrastructure/config-manager/user-guides/configuration-deploy/site-configuration-backup) |
| Recover   | Factory-reset a reachable switch, re-run ZTP, and capture a fresh backup.                         | [Device Reprovision](/switch-infrastructure/config-manager/user-guides/lifecycle/device-reprovision)                                                                                                                                                  |
| Maintain  | Upgrade Cumulus Linux through the image install, reboot, ZTP, and post-upgrade validation cycle.  | [Switch OS Upgrade](/switch-infrastructure/config-manager/user-guides/lifecycle/switch-os-upgrade)                                                                                                                                                    |
| Secure    | Rotate device credentials on one switch or across a site.                                         | [Device Password Rotation](/switch-infrastructure/config-manager/user-guides/lifecycle/device-password-rotation) and [Site Password Rotation](/switch-infrastructure/config-manager/user-guides/lifecycle/site-password-rotation)                     |

### Typical operating sequences

For a new Spectrum-X fabric:

1. Load the approved topology and device intent into Nautobot.
2. Upload the required Cumulus Linux images to the ZTP service.
3. Follow [New Site Bringup](/switch-infrastructure/config-manager/user-guides/new-site-bringup) to power on and
   provision the switches.
4. Run [Cable Validation](/switch-infrastructure/config-manager/user-guides/validation/cable-validation) and
   [Cumulus Hardware Validation](/switch-infrastructure/config-manager/user-guides/validation/hardware-validation) before
   handing the fabric to normal operations.

For a routine configuration change:

1. Change the source data in Nautobot or the applicable configuration template.
2. Confirm that the Render Service produced the expected intended configuration.
3. Run [Configuration Deploy](/switch-infrastructure/config-manager/user-guides/configuration-deploy/configuration-deploy) for one switch
   or [Multi-Device Deploy](/switch-infrastructure/config-manager/user-guides/configuration-deploy/multi-device-deploy) for a coordinated
   fabric-wide change.
4. Review the generated diff at the approval stage. After Config Manager applies the approved change, it captures a new running-configuration backup.

## Spectrum-X overlay lifecycle

Config Manager also includes workflows for switch-port tenant isolation on the
Spectrum-X underlay. These workflows manage the overlay, VRF, VXLAN, device, and
interface intent in Nautobot and can render and deploy the resulting
configuration.

| Workflow                                                                                                                                            | Purpose                                                                                                                                                                         | Device impact                                                     |
| :-------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | :---------------------------------------------------------------- |
| [Spectrum-X Overlay Creation](/switch-infrastructure/config-manager/user-guides/spectrum-x-overlay-lifecycle/spectrum-x-overlay-creation)           | Allocate the route distinguisher and create the Overlay, VRF, and L3 VXLAN objects in Nautobot.                                                                                 | No switch configuration is changed.                               |
| [Spectrum-X Overlay Assignment](/switch-infrastructure/config-manager/user-guides/spectrum-x-overlay-lifecycle/spectrum-x-overlay-assignment)       | Bind an existing overlay VRF to a device and selected interfaces in Nautobot. This is normally called by Spectrum-X Overlay Tenant Change; the standalone workflow is API-only. | No switch configuration is changed until a deploy runs.           |
| [Spectrum-X Overlay Tenant Change](/switch-infrastructure/config-manager/user-guides/spectrum-x-overlay-lifecycle/spectrum-x-overlay-tenant-change) | Orchestrate assignment, tenant-scoped rendering, and deployment to a switch.                                                                                                    | Applies the validated tenant configuration to the target switch.  |
| [Spectrum-X Overlay Deletion](/switch-infrastructure/config-manager/user-guides/spectrum-x-overlay-lifecycle/spectrum-x-overlay-deletion)           | Remove unused VRF, VXLAN, and Overlay metadata after assignments have been removed.                                                                                             | Deletes Nautobot intent; in-use VRFs are protected from deletion. |

The common operator path is:

1. Run **Spectrum-X Overlay Creation** once for the tenant overlay at the site.
2. Run **Spectrum-X Overlay Tenant Change** to assign the overlay to a switch and its
   ports, render the changed intent, and deploy it end to end.
3. Before deletion, remove the overlay from all interfaces and deploy the resulting configuration change. Then, run **Spectrum-X Overlay Deletion** to clean up the unused Nautobot objects.

These overlay workflows supplement the normal Spectrum-X switch
management path. They are not required for ZTP, general configuration
deployment, backup, validation, reprovisioning, software upgrades, or password
rotation.

## Management prerequisites

Before operating a Spectrum-X switch through Config Manager, confirm:

* The device is modeled in Nautobot with its Cumulus Linux platform, fabric
  role, serial number, management identity, interfaces, cabling, intended
  software, and required config contexts.
* Config Manager can reach the device management network and the required
  [firewall ports](/switch-infrastructure/config-manager/deployment/firewall-ports) are open.
* Device credentials are available through the configured secrets backend.
* The correct Cumulus Linux image is available to the
  [ZTP service](/switch-infrastructure/config-manager/services/network-ztp/upload-images).
* The Render Service has produced a current intended configuration in the
  Config Store before a deploy, backup, reprovision, or upgrade workflow runs.

For device-facing validation without physical hardware, use the
[DSX Air Simulation User Guide](/switch-infrastructure/config-manager/getting-started/dsx-air-simulation-user-guide), which provisions
simulated Cumulus Linux switches and supports the main Ethernet workflows.