HP Network Node Manager i Software—HP Business Service Management/Universal CMDB Topology Integration Guide

 

The HP Business Service Management (BSM) platform provides tools for managing the availability of applications in production, monitoring system performance, monitoring infrastructure performance, and proactively resolving problems when they arise.

The HP NNMi–HP BSM/UCMDB Topology integration populates NNMi topology into either the BSM Run-time Service Model (RTSM) or the UCMDB database. Each device and device component in the NNMi topology is stored as a configuration item (CI) in RTSM or UCMDB. BSM or UCMDB users and integrated applications can also see the relationships between NNMi managed layer 2 network devices and BSM-discovered or UCMDB-discovered servers, hosted applications, and more.
Additionally, the integration stores the identifier of populated CIs in the NNMi database. Uses for the CIs of the NNMi-managed devices include the following:

• NNMi components in the MyBSM portal.
• Path health views available from the BSM Real User Monitor (RUM).
• Using the agent implementation of the HP NNMi—HPOM integration, and pointing to a BSM Connector, results in an HP NNMi–HP BSM Operations Management integration that associates incidents regarding NNMi-managed devices with BSM CIs.
• The comprehensive relationships maintained by RTSM or UCMDB enable an NNMi operator to view the impact of a network access switch infrastructure failure on other supported devices and applications. The NNMi operator selects an incident or a node in NNMi and then enters a request for impacted CIs.

Full details are in this document http://support.openview.hp.com/selfsolve/document/KM00830093/binary/nnmi_integration_business_service_mgmt_10.00.pdf

HP uCMDB: Creating New CIs using Enrichment Rules

In this article, I have used one of the HP uCMDB features to create additional CIs based on the discovered data on certain CI

Scenario:

Operators want to display Operating System name as CI linked with Node CI

Steps:

1-Create New CIT for the Operating System

2-Create relation between Operating System CIT an d Node CIT

3- Create Correlation Rule

3a- in Query Mode adding your Searching criteria  TQL

3b- in Enrichment Mode add the CIT you want to create

3c- Add  Query Node Definition (How the new CI Attributes will be populated)

4- Create Scheduler task to run the Enrichment Rule

 

1-Create New CIT for the Operating System

Under Modeling > CI Type Manager right click the CIT tree and create a new CIT

I recommend to create the CIT under NodeElement CIT to inherit all the relations and configurations as all NodeElement child CITs

Note: Remove ABSTRACT_CLASS from Type Qualifiers to be able to create CIs

 

2-Create relation between Operating System CIT an d Node CIT

Select Node CIT and OS CIT and right click select Add/remove Relationship.

 

3- Create Correlation Rule

Move to Modeling > Enrichment manager and create new rule

 

 

3a- in Query Mode adding your Searching criteria  TQL

In Query mode

I will Edit the Query Node Properties and filter my TQL

I will select DiscoverOSName is Not Null to ensure that this will apply to only nodes that Has this attribute populated

 

 

3b- in Enrichment Mode add the CIT you want to create

Change the Operations to Enrichment Mode and add the operating System CIT, and Add the relation between Node CIT and Operating System CIT

 

3c- Add  Query Node Definition (How the new CI Attributes will be populated)

Fill the Operating System attributes as needed.

for Name attribute use the option By Attribute and select Node CIT and DiscoveredOsName

 

Note: You may create combination of Node attributes as a value by choosing Advanced

 

4- Create Scheduler task to run the Enrichment Rule

 

Go to Administration >  Scheduler

Create New Schedule

Add Run an Enrichment Rule

Select your schedule

Run the schedule

 

The Outcome will be like this, create a view to with Node and OS CITs to get the result.

HP uCMDB: Modeling: Grouping Node CIs by Operating System

Create New View or Modify the current view.

Add Node CIT

In the Hierarchy pane, right click Node CIT and select Add Group by Attribute

 

Select DiscoveredOSName as Group by

 

This is a preview on How it should look like.

Modeling: Creating relationship between OS and Nodes

The main idea here is to group multiple Servers under Operating System name, this may be needed by some operators to identify operating system for Node CIs by just a glimpse.

My objective is to show how simply this can be done in HP uCMDB

Steps:

1. Create a new CIT for Operating System.
2. Create several OS instances
3. Create a Virtual calculated relationship between OS and Node CIs

1- Create a new CIT for Operating System.

Open CI Type Manager  by Modeling > CI Type Manager

Create CIT for Operation System

Assign the Name attribute as Key

Create CIT instances that matches the operating system names populated in your Node CIs like DiscoveredOSName

Assign the Name attribute as Key

2- Create several OS instances

Create CIT instances that matches the operating system names populated in your Node CIs like DiscoveredOSName

 

Modeling > IT Universe Manager

Click on New CI

3- Create a Virtual calculated relationship between OS and Node CIs

Modify your View or Model or Prospective to have this relation, below I have created a new view.

Modeling > Modeling Studio 

Create New View  I named it “OS2Node”

Add both Operating System and Node CITs

Create Joined Relationship

Select Name Attribute from Operating System CIT and DiscoverOSName from Node CIT and select Operator Sub string ignore case

This is the final result of the CIs and its relations.