Previously, Network Configuration Manager handled only devices with single configuration file states.

With the multi-config feature implementation, the system now supports devices with multiple configuration files by revisioning all config files defined in a device package -- for a device class .

Multi-Config offers you a known view of any device at any point-in-time!

With Multi-Configuration, Network Configuration Manager can ensure:

  • Cisco devices can be restored if they have a second configuration file.

  • Devices with multiple configurations are supported.

  • Firewalls are supported, along with new communication methods.

  • Compliance can be enforced on more than one configuration file on a device

Within configuration management, generally devices have 1 -n configuration units.

Note: A configuration unit can be a file or interpreted data. The term configuration unit is used interchangeably with configuration file . A good number of devices resemble "Unix-like" devices.

Following are the "families" of devices, based on multiple configuration units , that are supported:

  • Alcatel

  • Checkpoint

  • IOS Config

  • Juniper

  • Cisco Firewall Switch Module

  • Cisco VPN Concentrator

  • Passport MSS

  • Nortel ARN

Device Package

A device family (or class) is represented by a device package. A device package is a collection of driver code and class metadata that is used to manage all devices of that class. Device packages are field deployable.

The Device Package:

  • Declares the configuration files that are to be captured from the device

  • Declares the potential destinations and operations supported for the files

  • Ties every file with a choice of supported destinations and push mechanisms

  • Ties every file with a choice of activation methods and post operations. For example, pushToMemory, copyToStart.

  • Declares device level operations. For example, reboot.

  • Includes defaults that should be used for autonomous operations

Configuration Unit

A configuration unit is a logical set of information that describes or controls the behavior of a device in the context of a network and its relationship with other devices. A configuration unit may be available as "read-only" data, in which case, it may contribute to the state of a device but it is not available for modification.

Device States

When all the configuration units (as declared in the device package) are captured without any errors, the device state is Completed. Rollback and Restore can be performed from this completed state.

When a certain configuration unit (although declared in the device package) is not captured due to errors or intermediate pulls, the state of the device is Partial. You can complete a rollback or a restore from a single configuration unit in the partial state.

On the other hand, configuration units are available for modification that Network Administrators often modify to control the higher level services offered on that network.