What's changed: Initial version
4.3Controllers and programmable management (Catalyst Center, NETCONF, RESTCONF)
Covers the four intent-based workflows of Cisco Catalyst Center (formerly DNA Center) with Assurance and its AI/machine-learning anomaly detection, NETCONF which writes XML over SSH port 830 into a candidate datastore and applies it atomically with commit, and RESTCONF which maps CRUD onto HTTP methods with JSON--framed as the selection judgment of "which mechanism safely delivers this change."
In a world of configuring devices one at a time from the CLI, configuration drift (identically-roled devices whose configs quietly diverge) and partial change failure (an error on device 17 of 40 leaving half the fleet applied) are chronic sources of incident. Programmable management attacks both structurally, and the keys are transactionality and declaring intent. NETCONF can stage edits in a candidate datastore and apply them all-or-nothing with commit, while RESTCONF lets an existing HTTP toolchain touch YANG data easily. Catalyst Center, in turn, takes "how you want things to be" rather than "how to do it," and looks after drift detection and assurance as well. Read this section with the view that the right mechanism for the same change shifts with scale and with the blast radius of failure.
4.3.1Cisco Catalyst Center (formerly DNA Center)
Continue reading — free sign-up
You're reading the free preview. Sign up free to read this section in full, plus every chapter (including 4+) and all questions.