Overview
NFM-P management of network objects
The NFM-P is used to create, configure, and manage a device with the various hierarchical objects required to be part of a network. Equipment such as the routers, which are at the top of the hierarchy, have properties that are configured using the CLI and discovered when the NFM-P discovery process is run. After the device is discovered, it is displayed as an object in the navigation tree. See Chapter 3, NFM-P navigation tree for more information about the navigation tree.
Objects in the NFM-P are considered to have parent/child relationships that are contained within a hierarchy. For example, a card in a card slot is the parent object of a daughter card. The behavior of each object is defined using parameters that are specific to the function required. Those parameters can be managed to suit the needs of the service required. Objects are created and managed using the properties forms found in the contextual menus of the equipment view.
The network is the top object in the navigation tree. The network icon in the navigation tree is the parent object of all managed devices. When you expand the network icon, all managed devices are shown as children of the network parent.
The device object is the discovered device at the top of the hierarchy in the navigation tree, directly below the network icon. The following children objects of the router are created automatically in the navigation tree after the device is discovered.
The following objects must be created using property forms or create forms from the contextual menus of the equipment view or the ring group view.
-
individual ISA-AA Groups with ISA-AA MDA or ESA-AA VM members and ISA-AA partitions
-
individual ISA-LNS Groups with ISA broadband applications MDA members
-
individual ISA-NAT Groups with ISA broadband applications MDA members
-
individual ISA-Video Groups with ISA-Video MDA or ESA Video Group members
-
Ports are automatically created when the daughter card is created.
Configuring an object is accomplished in two steps. First the object must exist or be created, second, the object parameters are modified. See To create an object to create objects using the navigation tree.
Object deployment status
When you configure an object using the NFM-P GUI or the NFM-P OSS, the NFM-P saves the configuration and attempts to deploy the changes to the network. Although the value is changed on the configuration forms, the configuration change may not be fully deployed to the NE.
The NFM-P allows you to monitor the deployment state for objects. The Deployment tab on all object properties forms notifies you of configuration changes that are not fully deployed to the NE. The parameter that was unsuccessfully deployed is listed, along with the old value and the new value. A deployment icon or warning indicator appears in the following locations when you change the configuration of an object:
-
beside all of the parameters on an object properties form for which a deployment is in progress (yellow icon) or has failed (red icon)
-
beside the object in the navigation tree (blue icon, regardless of state)
-
in info tables in map views (blue icon, regardless of state)
-
in the Deployment column on object list forms (blue icon, regardless of state)
See Chapter 25, NE deployment for information about how to configure a deployment policy, manage deployments, and troubleshoot failed deployments. See To monitor the deployment status of a network object for information about how to monitor the deployment of an object configuration change.