The cisco.catalystcenter Ansible Collection, delivered jointly by Cisco and Red Hat via Ansible Automation Hub, brings infrastructure-as-code practices to Cisco Catalyst Center campus network management. It offers over 70 use cases and 300+ playbooks covering zero-touch device provisioning (PnP), SD-Access fabric orchestration, software image management, compliance/assurance checks, and configuration state extraction for GitOps workflows. Key benefits highlighted include eliminating fragile CLI screen-scraping in favor of native JSON APIs, enabling YAML-defined network state in Git, integrating with SSoT platforms like NetBox or ServiceNow, and abstracting scale so a single task can push policy changes across thousands of devices.
Table of contents
High-Value Enterprise Use Cases and Playbook BlueprintsDay 0/1: Zero-Touch Discovery and ProvisioningDay 2: SD-Access (SDA) Fabric OrchestrationDay N: Software Image Management (SWIM) and AssuranceConfiguration Generation and “State” ExtractionEngineering Benefits: Automating Cisco Catalyst Center with AnsibleReady to Build?Questions this post answers
How can I automate zero-touch provisioning of Cisco switches with Ansible and Catalyst Center?
The pnp_workflow_manager module in the cisco.catalystcenter Ansible collection automates Plug and Play onboarding by inserting device serial numbers into the controller's inventory and binding them to a site layout automatically. Playbooks can also set device credentials, IP pools, and standardized settings like SNMP and telemetry before a device even connects. daily.dev surfaces practical automation workflows for engineers scripting Cisco Catalyst Center provisioning.
What is the cisco.catalystcenter Ansible collection and where do I get it?
It is a Cisco and Red Hat validated Ansible collection with over 70 use cases and 300+ playbooks for automating Cisco Catalyst Center, covering device provisioning, SD-Access fabric orchestration, software image management, and compliance checks. It is distributed through Red Hat Ansible Automation Hub and works via Catalyst Center's REST APIs instead of CLI scraping. Network engineers evaluating IaC tooling for Catalyst Center can track collection updates on daily.dev.
How does using Catalyst Center APIs with Ansible avoid the fragility of CLI screen scraping?
The cisco.catalystcenter collection works exclusively with JSON structures natively returned by Catalyst Center APIs, so it avoids regular-expression parsing tools like TextFSM that break when a Cisco IOS XE update changes whitespace in show command output. This makes automation more resilient to platform updates compared to legacy CLI scripting. daily.dev helps engineers weighing API-driven automation over brittle CLI parsing for network infrastructure.