Expert Insights Series
Cisco Network as a Code: Getting Started
Join us for a two-part series designed to help network and platform teams move from one-off CLI changes to predictable, repeatable automation using infrastructure as code (IaC). In the first session, we will define IaC in practical terms, show where AI genuinely helps, and outline a sensible first adoption path for your environment. In the second session, we will apply the same model to Cisco Catalyst SD-WAN — using structured templates, APIs, and controlled pipelines to drive consistent policy, reduce drift, and produce audit-friendly change history across hundreds of sites. Whether you are just exploring IaC or looking to operationalize it on your WAN, you will leave with a clear framework, realistic expectations, and a practical starting point for your own network.
Network and platform teams still need predictable, repeatable changes—what infrastructure as code (IaC) is built for. This session defines IaC in practical terms: describing desired state, storing it in version control, and applying it through pipelines instead of one-off CLI sessions. We will separate useful AI assistance (drafting, reviewing, explaining diffs) from the governance you still own: peer review, testing, and rollback. You will leave with a clear picture of how IaC fits into day-to-day network delivery and a sensible first adoption path for your environment.
Cisco SD-WAN environments scale quickly, and hand-edited changes make it hard to keep policy consistent and easy to audit across hundreds of sites. This session explains how to treat Cisco SD-WAN configuration as code: structured templates, APIs, and controlled pipelines that apply intent the same way every time. We will connect that model to compliance outcomes—standard security policies, drift reduction, and evidence-friendly change history—without slowing legitimate network changes. Network engineers will leave with a practical view of what “as code” means for Cisco SD-WAN in real operations, not just in diagrams.
