The NNMi 8 Integra tion populates Operations Center elements and alarms based on mining information from NNMi 8 inventory objects (Nodes, Node Groups, Interfaces, IP Addresses, IP Subnets, L2 Connections) and incidents.
NNMi 8 incidents and inventory objects are polled by the integration at specific intervals as specified in the Poll Period (secs) adapter property. New objects are created when incidents and inventory objects are discovered, existing objects are updated, and objects are removed if no longer returned.
Because the NNMi 8 web services API does not have a last update time for incidents and inventory objects, all objects must be polled for to compare against. If an exception occurs during a poll (i.e. connection timeout) then the remainder of the poll is skipped, and another poll is performed at the regular poll period interval. However, no data should be lost.
The integration is a hybrid of an event-based and object-based integration in the following ways:
Incident alarms are sent through the hierarchy file to allow for organizing incidents as determined by the hierarchy file.
By default, alarms representing inventory objects are sent through the hierarchy file to allow for organizing inventory as determined by the hierarchy file. This can be disabled by setting the Process Inventory Alarms Adapter property to false.
Elements representing the NNMi inventory objects are represented in the elements tree to reflect the inventory objects as in NNMi.
NOTE:The Operations Center HP NNMi Integration adapter requires a NNMi SDK Enablement license from HP.
To integrate NNMi:
Start the Operations Center server and launch the Operations Center console.
Create an HP NNMi Integration adapter for each instance of NNM.
For instructions, see Section 2.1, Creating an Adapter.
Modify the HP NNMi Integration adapter properties.
For property descriptions, see Section A.12, HP Network Node Manager i-series.
Start the HP NNMi Integration adapter.
For instructions, see Section 2.2, Starting, Stopping, or Deleting an Adapter.
Each running integration instance has four top level folders: Incidents, Inventory, Topology Inventory, and Topology Maps.
Incidents and Inventory are event-based branches as determined by the hierarchy file. The names of these two folders and their element structures are determined by the hierarchy file MODL definition.
Topology Inventory and Topology Maps are object-based element tree branches.
Topology Inventory contains an element for each NNMi inventory object (Node, Node Group, Interface, IP Address, IP Subnet, L2 Connection) that is discovered. Only one element for any given NNMi inventory object exists under the Topology Inventory element branch, even if that node is a member of more than one node groups.
Topology Maps element branch represents the hierarchical parent/child structure of Node Groups and Nodes in the same structure as the NNMi web based client’s Topology Maps/ Node Group Overview view. There is only one element per inventory object in NNMi. The parent/child relationship is represented in the integration through element links. Child Nodes and Node Groups are linked to parent Node Groups. In addition to showing Nodes and Node Groups, Interfaces are linked to associated Node, and IP Addresses are linked to their associated Interface.
The element tree can be customized by doing the following:
Change the names of the Topology Inventory and Topology Maps branches by editing the Topology Inventory Folder Name and Topology Maps Folder Name adapter properties.
Create Topology Inventory subfolders for inventory objects using the Use Pattern adapter property. You can create subfolders if there are a large number of inventory objects. For example, IP Addresses under one parent can be broken out into subfolders representing a portion of the IP Address name, like a subnet.
All incidents and inventory objects have property pages defined but only properties available through the NNMi Web Services API are shown in the adapter. There is an information property page (i.e. “Node Information”, “Interface Information”, etc.) and for inventory objects that support notes, there is a notes property page (i.e. “Node Notes”, “Interface Notes”, etc.) with the notes property.
Various operations are available for incidents and inventory objects, but only those available via the NNMi Web Services API are shown in the adapter. Since the integration is polling based, changes made in NNMi or through an operation in the integration do not show until the next poll period is complete.
For example, if the integration polls every minute and it takes a minute to poll completely, changing a Node’s Note property via the Change Notes operation in the integration might not reflect on the Node’s property page for two minutes or until the next poll period is complete.
Table 3-15 lists available NNMi operations.
Table 3-15 NNMi Operations
|
Object Type |
Available Operations |
|---|---|
|
Incident alarms |
|
|
Node Groups and Node Group Inventory Alarms |
None |
|
Node Elements and Node Inventory Alarms |
|
|
Interface Elements and Interface Inventory Alarms |
|
|
IP Address elements and IP Address Inventory Alarms |
|
|
IP Subnet and IP Subnet Inventory Alarms |
|
|
L2 Connection and L2 Connection Inventory Alarms |
|
In Operations Center, alarms have severity and Elements have condition. The severity of NNMi alarms and condition of elements are based on properties of the NNMi incidents and inventory objects as described in Table 3-16 and Table 3-17.
Table 3-16 Severity and Condition Mappings for Objects
|
Object Type |
Property |
|---|---|
|
Incident |
severity |
|
Node Group |
status |
|
Node |
status |
|
Interface |
status |
|
IP Address |
none |
|
IP Subnet |
none |
|
L2 Connection |
status |
Table 3-17 Severity and Condition Mapping for Property Values
|
Property Value |
Severity/Condition |
|---|---|
|
CRITICAL |
CRITICAL |
|
WARNING |
INFO |
|
MINOR |
MINOR |
|
MAJOR |
MAJOR |
|
NORMAL |
OK |
|
DISABLED |
UNKNOWN |
|
UNKNOWN |
UNKNOWN |
|
NOSTATUS |
UNKNOWN |