Cisco Logo


Inside Cisco IT

Device configuration management can be a complicated beast. Have you tamed it? Do your IT policies enforce archive retention periods, audit trails, security compliance, or secure transfer methods? Do your change management policies mandate the ability to quickly perform configuration rollback?

Whether you’ve got configuration management licked or whether you’re lucky to remember to execute “copy run start,” we would like to gain a better understanding of the approach you’ve taken to device configuration management.

Many organizations have their device configurations managed by a Cisco Remote Management Service. For those of you using a commercial or open source package, what is your tool of choice?

Have you rolled your own configuration archive tool because the available configuration management packages (above) lack functionality, or because of a lack IT funds or resources to administer? if you’ve rolled your own configuration archive tool, what combination of languages and frameworks are you using?

It’s not uncommon for our customers to use insecure protocols when transferring configuration files to and from their devices. Granted, they may restrict such file transfers to their intranet. What combination of communication and transfer protocols are you using to archive configs?

Cisco IOS Software includes a number of native configuration management utilities.  Are you employing these tools in your environment?

After the hard part is done and configurations have been archived, does your organization utilize a source control system to keep revisions of configuration changes? If so, which one?

Cognizant of the plethora of device configuration management tools available to Cisco customers, including commercial, open source, and homegrown tools, we’re very interested to hear which ones you have found to be the best fit in your environment.

Comments Are Closed

  1. Return to Countries/Regions
  2. Return to Home
  1. All Inside Cisco IT
  2. Return to Home