Speaker
Description
Our earlier framework configured a campus network by sending commands to switches task by task. It was slow, its dry run listed as changes lines the switch already had, and each switch was half-configured during a run. On the same campus of some 400 switches, we replace it with a configuration transform. Instead of trying commands on the switch, we record each platform's syntax in advance, read each switch's configuration and state, and compute its complete configuration locally. The transform rewrites the lines the site policy manages and copies every other line unchanged and in place, so every pending change can be reviewed as a diff. With configure replace, the switch computes the difference and applies it. On IOS from 12.2(55) and on NX-OS, the switch undoes the change if the session is lost, and a scheduled reload recovers a switch the change left refusing logins. A web application shows each pending change, ties approval to the exact file, and checks an edited line with the switch's parser without entering it. On Cisco switches the transform refuses to drop the management path or every login. Seven verification layers, including Lean and TLA+, check the transform and protocol. On ten leaf switches, the median read-only check falls from 227 s to 18.8 s, and the median real deployment from a modelled 592 s to 69.5 s. One rollout deployed 313 switches in 46 minutes without a failure. The cost is a platform table covering 23 hardware families and 19 software versions.