Configuration management

Overview

OSS applications can use the XML API to perform configuration operations on NFM-P-managed network objects and their associated child objects. This is achieved by sending XML requests that allow the OSS to create, delete, or modify existing objects. These requests can also extend to the object’s children at the same time, if required.

Note: The configuration operations that are allowed on each object is defined in the XML schema. See the Schema Reference. See the XML API Reference for more information about the object hierarchies (relationship between parent and child objects).

The OSS user account privileges define the access and restrictions for configuration operations in NFM-P functional areas. See the chapter on NFM-P user security in the NSP System Administrator Guide for information about configuring user accounts and assigning privileges.

Most of the configuration operations that can be performed on the functional areas of the NFM-P using the GUI can also be performed using the XML API. The main areas for OSS configuration management include:

device configuration—for example, routers, cards, ports, GNE, and channels. See Chapter 16, Device configuration management for more information.
network configuration—for example, protocols, MPLS, service tunnels, and VRRP. See Chapter 17, Network configuration management for more information.
policy configuration—for example, service policy, routing policy, and network policy. See Chapter 18, Policy configuration management for more information.
service configuration—for example, VLL, VPLS, VPRN, VLAN, mirror composite, and customer/subscriber. See Chapter 19, Service configuration management for more information.
scripts and template configuration—See Chapter 20, Script and template configuration management for more information.

Use subject to agreed restrictions on disclosure and use.