Quick Start

First Run Tour

View as Markdown

After Config Manager is installed, use this tour to confirm the platform is reachable and move through the first operational path in the right order: site bringup first, then workflow exploration.

Verify the deployment

  1. Confirm all Config Manager pods are running in the deployment namespace.
  2. Confirm service hostnames resolve from your workstation or jump host.
  3. Open the Config Manager UI and Nautobot UI.
  4. Confirm the intended site data exists in Nautobot.
  5. Confirm intended configuration exists in Config Store for devices that should render.

For deployment checks and commands, see Getting Started with Config Manager.

Local render preview

If you used Local Development Quick Start, inspect generated Nautobot data and rendered configs only. Do not run device-facing workflows as validation.

Bring up the site first

For a real lab or production site, start with New Site Bringup. Config Manager cannot run useful device-facing workflows against new switches until those devices have booted through DHCP/ZTP and completed provisioning through Config Manager.

Follow the site bringup guide until:

  1. Devices have received DHCP leases from Config Manager.
  2. Devices have fetched their ZTP boot artifacts.
  3. Devices have applied the rendered configuration.
  4. Nautobot shows the devices as provisioned.
  5. The device management addresses are reachable from the Config Manager environment.

Before ZTP completes, workflows such as backup, deploy, cable validation, password rotation, OS upgrade, firmware upgrade, and reprovisioning should be expected to fail or produce unhelpful results because Config Manager cannot yet reach or authenticate to the devices.

Real or simulated devices

After site bringup has completed, start with workflows that establish visibility before making broad changes.

WorkflowWhy run it first
New Site BringupDrives the Day-0 path when devices are factory-reset and ready for DHCP/ZTP. Run this before other device-facing workflows.
Configuration BackupCaptures current running configuration and verifies device reachability and credentials.
Configuration DeployApplies one reviewed intended-config change to one device.
Multi-Device DeployDemonstrates grouped diffs and per-batch approval after single-device deploy is proven.
Cable ValidationCompares observed cabling against Nautobot intent after devices can be reached.

Use Controlling Running Workflows before approving, rejecting, retrying, or terminating a live workflow.

Before destructive workflows

Reprovisioning, OS upgrades, firmware upgrades, and password rotation can disrupt devices. Before running them, confirm current backups, intended configuration, device reachability, credentials, maintenance approval, and recovery access.