Configuration Management is mistakenly synonymous with the textual based configuration files polled directly from network devices and stored on specific host servers. Such files should be good only for backup purposes and error/disaster recovery purposes and not necessarily used for configuration management as an NMS technology area/service concept!
As per our IMMS model (more on this below); Configuration Management defines the relationships between the network administrator exercised control over resources, events, and/or service levels on the network element and the actual resultant network operations performed by that network element at the different defined levels referred to above. This relationship could either be derived directly from mapping a particular level on the element from the cli to a corresponding MIB Object(s) or indirectly through measuring certain relevant Security, Accounting, Performance and/or Fault metrics. Configuration changes have other important aspects that are ignored; such as:
Running versus start-up configuration changes.
Running versus start-up configuration changes save times.
Information about configuration events such as the event time, command source, configuration data source, configuration source terminal type and number as well as terminal user and location.
Information about the host name and configuration source server that caused the change and the configuration file name at the storage file servers.
Configuration files copying operations data and management to and from the network device(s).
Configuration Management Solution Presentation:
To be provided.
[Small Solutions], [Professional Solutions], [Security
Solutions], [Development Solutions]
[Home], [About],
[Solutions
Center], [NMS
Market],
[Products & Services],
[Management
Technology], [Technical Support],
[Contact us],
[Site Map]