component which actually does the configuring of network elements. The server Applications MO Updates Programming Configuration Interface Tasks and Devices Security Configuration Server Files Task Processing Task Manipulation Rollback Configuration Audit Provider Plugins Result Generation Resume Pending Tasks MULTI-PROTOCOL MANAGEMENT SERVER Telnet Configuration Management Architecture Figure 11.5 Configuration management architecture. OSS for Telecom Networks also ensures that each NE commences operation in the desired state, carries the required parameter values and has the desired relationship with other NEs. Thus, it interacts with components such as the task processing, configuration provider, security, audit and inventory update systems. Configuration attributes are represented as "tasks". Task processing involves identifying attributes and devices, performing authorization checks, storing attri- butes and devices separately, task manipulation, task execution and result gener- ation. The storage of attributes and devices in a persistent data store allows reuse of the information for other configuration operations. Before a task is applied to a device, task manipulation rules can be applied so that the task is modified. It is pos- sible to plug in user-specific task manipulation rules. Finally, result processing is equipped with a rollback feature. To communicate with NEs, providers of protocol-specific configuration com- mands can be associated with the configuration server. The configuration server integrates multiple configuration providers. The CMS makes it easier to configure NEs. To address the security threats that could arise, authorization checks are carried out by AdventNet security manage- ment services before the task is configured. When very large networks are involved, it is necessary to log configuration details. The configuration management solution has a customizable audit facility. Configuration changes trigger updates in the inventory database. To sum up, CMS helps network management staff