Gated Device Onboarding: Automated Validation
Ensuring reachability and data integrity before inventory commit.
The Problem: "Ghost" Inventory and Data Decay
A common failure in network automation is the creation of "ghost" records—devices added to the Source of Truth (NetBox) that are actually unreachable, misconfigured, or running incorrect software versions. Manual onboarding often bypasses vital reachability checks, leading to an inventory full of stale or inaccurate data. Without a validation gate, the SoT becomes a liability rather than an asset, triggering downstream automation failures and increasing troubleshooting noise.
Workflow Anatomy
How It Works
This workflow (internal ID: onboard_netbox_device) implements a gated logic pattern to ensure only verified, reachable hardware enters the production inventory:
- Inventory Abstraction: The flow targets a specific inventory object (node-l3) using pre-stored Nokia SR Linux credentials, eliminating manual credential handling and ensuring consistent access.
- Validation Gate: Before any record is created in NetBox, the workflow executes a show version command via SSH. This acts as a reachability and health check.
- Deterministic Branching: * On Success: The flow proceeds to create/update the device in NetBox, setting its status to active and populating custom fields with the actual software version retrieved during the validation step.
- On Failure: If the SSH session fails, the workflow terminates the onboarding path, preventing the creation of a "dead" record in the SoT.
- Multi-Channel Telemetry: Real-time execution status is pushed to Slack for immediate visibility, followed by a detailed execution report sent via email for auditability.
Execution Artifacts: SoT and ChatOps
Enriched Inventory Commit
The workflow executes a write operation to NetBox only after the SSH reachability gate has been successfully cleared. The new device record (Nokia node l3) is provisioned with an active status, and the exact software version retrieved directly from the hardware (e.g., SRLinux-v23.10.2) is injected into a custom field. This strict sequence ensures that the Source of Truth reflects the verified, real-world state of the network rather than a theoretical or statically assigned baseline.
Slack: Execution Telemetry
Simultaneous to the inventory update, Flow Weaver pushes a structured notification to the engineering team's communication channels. This payload delivers immediate, context-rich visibility—detailing the workflow name, target device, execution status, and the specific output from the validation step. By surfacing this telemetry directly in Slack, the workflow eliminates the need for operators to dig through backend execution logs to confirm a successful onboarding.