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

OMi Monitoring Automation

OMi Monitoring Automation(OMi M.A.) automates the configuration of monitoring for infrastructure and composite applications. It detects new instances of components, from servers to composite applications, and maps them to predefined management templates and “aspects” that model to the desired configuration and resource type.

 

Interactive Report Views in HP Service Health Reporter

Video illustrating how to make the best use of the Interactive mode of viewing reports in HP Service Health Reporter

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.

BSM 9.x – NNMi 9.x Integration

To integrate NNMi with BSM, you have two methods

NNMi – uCMDB  integration which uses Data Flow Probe (DDM Probe) and is the old method.

NNMi – BSM Topology integration which is integration between NNMi and RTSM (a uCMDB version hosted in BSM)

The configuration steps is very simple

Log in NNMi > Integration Module Configuration > HP BSM Topology

Enter your NNMi server name, username and password

For BSM enter your BSM server name and port number  and RTSM username and password.

The NNMi - BSM Topology integration creates the following CIs:
Node
Interface
IpAddress
IpSubnet
Layer2Connection
HardwareBoard
PhysicalPort

You should note that the Built-in view for Layer 2 is not compatible with this integration, so we have to update it.

The view below is the default and it is not working as the BSM integration is populating the routers and switches as Node CI not a network device and adds the device role to NodeRole attribute.

1- remove Net Device CI

2- Add Node CI

3- Add a Composition relationship between this new Node CI and its Interface CI.

4-  Re-establish the folding rule (fold Interface under Node).

5- For the Node CI, right click and select Query Node Properties  specify that the NodeRole attribute should contain lan_switch or router

 

NNM View

uCMDB View

Configure OMW to forward all events to OMi

1- Configure OMW to forward all events to OMi

a- Create Server-Flexible Management Policy

---

TIMETEMPLATES
# none

RESPMGRCONFIGS
    RESPMGRCONFIG DESCRIPTION "Forward all messages to HP OMi"
    SECONDARYMANAGERS
    ACTIONALLOWMANAGERS

    MSGTARGETRULES
        MSGTARGETRULE DESCRIPTION "forward all messages rule"
            MSGTARGETRULECONDS
            MSGTARGETRULECOND DESCRIPTION "forward all messages "
            MSGTARGETMANAGERS
                MSGTARGETMANAGER
                TIMETEMPLATE "$OPC_ALWAYS"
                OPCMGR IP 0.0.0.0 "dxb-bsm-01.mahmoudthoughts.com"
---

replace dxb-bsm-01.mahmoudthoughts.com with your OMi server.

b- Deploy the newly created policy to your OMW server and ensure it is enabled.

2- Configure HPOM Topology Sync

On BSM Console

Click Admin > Platform > Setup and Maintenance > Infrastructure Settings 

Under Select Context select Operations Management from Applications

Browse to Operations Management - HPOM Topology Synchronization Connection Settings Section

Type your OM Server Hostname, User, password and change other options as needed.

Run opr-startTopologySync.bat from BSM bin directory

%TOPAZ_HOME%\bin\opr-startTopologySync.bat

Check the result on Modeling Studio

Admin > ODB Administration > Modeling > Modeling Studio 

Select Views from Resource Type list

Select OM CI Collections  from Root > Operations Management

Click on Preview Icon

 

The Result should be the Node, Node Groups and Service Hierarchy

3- list the events forwarded by OMW

Click on Application > Operations Management

The list of events should be displayed under Event Perspective

In the video below I captured 30 seconds on generating test messages from OMW and how fast it shows in OMi

Message Sync between OMW and OMI