automation using compliance
Automation can save significant personnel hours and it can be used for more than performing regulatory compliance audits. Cisco Prime Infrastructure has two features that can deploy configuration changes: Templates and Compliance.
The primary use of Templates is the deployment of a feature or configuration change, but it requires knowing what and where to implement the change. In addition, there's no way of knowing if that configuration remains consistent through future device configuration changes. We argue that Compliance is a better method of deploying changes.
The primary use of Compliance is the auditing of device configurations to ensure that they are following your configuration standards or baseline requirements. However, Compliance can also perform enforcement of configuration standards or baseline requirements. This feature of Compliance allows deployment of changes to the appropriate devices, interfaces, etc. and also ensure that they continue to follow configuration standards or baseline requirements. Therefore, all the major benefits of Templates resides within the Compliance feature, which enables automation of virtually any task.
Here are a few examples about how to use the power of Compliance to deploy configuration changes and automate repetitive tasks.
The policies provided on this page are covered by the following Licensing and Exculpatory Clause.
Cisco IOS Image MD5 HASH Verification
You've deployed a new software image and your network management tool is reporting a successful file transfer, but often this is not accurate. It is a best practice to check the image hash before taking the leap of faith and rebooting your network device.
We are offering a free automation policy using your Cisco Prime Infrastructure that can save you from logging into each device to perform this task manually.
Here is our Cisco Image MD5 Hash Verification policy that will automate this task for you and a guide for implementing it.