Automation has simplified multi-vendor VPN provisioning and protects changes with safe rollbackI have performed automation for Layer 2 and Layer 3 VPN services provisioning during routing changes. In the data center, I completed provisioning tasks for Cisco switches using scripting in the YANG model and APIs. I deployed configuration remotely for approximately 400 to 500 switches, implementing automation instead of configuring devices individually. I also use Cisco Crosswork Network Automation Health Insights and change for streaming telemetry and KPI monitoring. The features have significantly helped decrease the complexity of using CLI commands. Using the YANG model and other tools for Cisco monitoring has been invaluable. Closed-loop automation and Health Insights have provided tremendous value through multi-vendor abstractions, including network elements and NEDs on YANG and NETCONF models. This has benefited my Layer 3 VPN configuration, and for the underlying commands, whether the target device is running Cisco IOS XR, Junos, or another platform, there are no restrictions between IOS types. Transactional rollback and multi-vendor support with closed-loop telemetry have been critical features. If a mass change fails on one device, the system cleanly reverses everything, ensuring I never end up with a half-configured device. This is an important capability in networking.
