Configuration states

The Netcool Configuration Manager database can store multiple versions of a configuration for a resource. These include current version; a future version that is either not complete, not approved, or in the queue to be implemented; and all previous versions. Saved configurations are identified by date and timestamp, along with the state of the configuration (current, draft, or versioned). Use this information to learn about the different states of configuration that can exist within Netcool Configuration Manager.

Current configuration

The current configuration is the configuration that deems to be loaded on the network resource, and which is labeled as current in the Netcool Configuration Manager database. When you submit a configuration (creation or change), that configuration becomes the current configuration. You can create a configuration synchronization log (see “Synchronizing Configurations” on page 140) at anytime to see if there are any differences between the current configuration and the configuration running on the resource.

Stale configuration

A Stale Configuration is defined as a device configuration which is older on Netcool Configuration Manager than the configuration held on the network resource. An example of a Stale Configuration is if the config setting 'update on change' has been unticked in the resource access document used by the device, and a draft config is submitted to the device.

Draft configurations

The Netcool Configuration Manager supports draft configurations, which are modified configurations of existing resources waiting to be pushed to the resource. There can be multiple draft configuration per user per resource, but each must have a unique name. The system will alert you if you try to name a draft configuration the same as an existing draft.

Versioned configuration

Versioned configurations are copies of previous current configurations. After a draft configuration is submitted and becomes the current configuration, the old current configuration is saved as a versioned configuration. Should you need to, you can always revert the resource to a previous version of the configuration by selecting and submitting an old version.

Failed draft configurations

If a parent draft (a draft on which children drafts are based) fails to run for any reason, all child drafts are listed as being failed drafts. These drafts never got a chance to run because the parent draft on which they were based did not complete.

Locked configurations

When searching or modifying configurations, you may see a configuration that is listed as being “locked.” Locked configuration is a state that occurs while a draft configuration is waiting to be run, and also when a draft config is being applied to a device. Configurations remain locked after a successful execution, and will only be unlocked if they become either failed or expired.

You can view, but not edit, a locked configuration (though you can make changes to the locked configuration and save it as another name).

All configurations are stored in the Netcool Configuration Manager database. Each saved configuration includes the following information:

  • Description
  • Creator user name
  • Creation date and time stamp
  • Draft, versioned, or current flag

Each resource can have two different configurations: the running configuration and either a stored (CISCO) or a candidate (Juniper) configuration. The running configuration is just that: the configuration that is currently running on the resource. A stored configuration is a draft that is stored in non volatile RAM on a CISCO resource. A candidate is a draft that is stored on the file system of a Juniper resource.

When making a configuration change, Netcool Configuration Manager checks to be sure the current, running, and stored (or candidate) configurations are all the same. You will see a “mismatch” error message if any of the three configurations are different. The configuration synchronization function is useful for seeing what differences exist between the running and the current configurations, and for overwriting the selected configuration so they are back in sync.