Videos: HP Service Health Reporter

These two videos shows HP SHR reports extended value when integrates with HP NNMi and HP OMi

First video illustrating Network reporting use cases in HP SHR

Second video illustrating OMI Event Reporting use cases in HP SHR

HP OMi: How to connect an HP Operations agent

In this video, you will learn how to connect an HP Operations agent to OMi so you can monitor availability and performance and remediate issues on a monitored server.

OMi is the only product that dynamically and automatically discovers and correlates—even as the environment changes—three sets of data: event data that indicates infrastructure- or service-impacting issues, for more details check OMi data sheet  http://h20195.www2.hp.com/V2/GetDocument.aspx?docname=4AA2-3879ENW&cc=us&lc=en

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.

HP Operations Orchestration Software Video Demo

 

HP OO Software Demo Series -- Part 1: Introduction to Operations Orchestration

 

Part 2: Incident Management using HP OO

 

 

 

Part 3: Automated Service Request Demonstration

 

 

 

Part 4: Automated Provisioning with OO Software

 

HP Software for IT Operations

HP Software for IT Operations

View more webinars from HP Software Solutions

Check OM Oracle DB Status

 

To check the database:
#su - oracle
Verify that ORACLE_HOME and ORACLE_SID are set correctly.

Check status by command tnsping:
$tnsping ov_net

Check status by SQL query:

$ORACLE_HOME/bin/sqlplus /nolog
SQL> connect / as sysdba
SQL>

   1: set lines110

   2: col strtd hea 'STARTED'

   3: col instance_name for a8 hea 'INSTANCE'

   4: col host_name for a15 hea 'HOSTNAME'

   5: col version for a10

   6: select instance_name, version, host_name, status

   7: , database_status, to_char(startup_time,'DD-MON-YYYY HH:MI:SS') strtd

   8: from v$instance;

SQL> exit

Start the database:

$ORACLE_HOME/bin/sqlplus /nolog
SQL> connect / as sysdba
SQL> STARTUP MOUNT
SQL> exit

Usually default database setting is as below:
ORACLE_SID is [openview]
Password of Oracle user 'system' is [manager]
Oracle Service name is [ov_net]

Screenshot-1

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1471367

Moving from NNMi using Postgres to NNMi with Oracle

This is a Draft Article

I just want to share my experience related to the migration from NNMi using local DB (postgress) to NNMi using Oracle DB

System was as specified:

NNMi 9.00 with Patch 1

Same Machine hosting the Embedded database (postgress)

Objective:

Migrate the configuration data to NNMi and Oracle Database.

Step X Backup NNMi for disaster recovery

nnmbackup.ovpl –type offline –scope all –force –archive –target c:\

a file with tar extension will be created on  drive c:\ started nnm-bak- and the current date and time .tar like nnm-bak-20100721183731.tar

Extra-Step X Backup any custome scripts you created for Incident actions.

%NnmDataDir%\shared\nnm\actions

aslo these files can be found under your backup archive

nnm-bak-20100721183731.tar\nnm-bak-20100721183731\data\shared\nnm\actions

Step X Backup you configuration (configuration Export)

in this step we will export the configuration using nnmconfigexport.ovpl

nnmconfigexport.ovpl –c all –file c:\exportedconfig

Hint: the export export remember to create the folder before run the above command “mkdir c:\exportedconfig”

Step X export Nodes as seed file

 

Step X Remove current NNMi installation

1st - Remove i-SPI

2nd – Remove Patches

3rd – Remove NNMi

Restart your server.

Step X Oracle configuration 

In this section we will create the table space that will hold the NNMi database that will be created during NNMi installation.

Section 1: Create Tablespace

CREATE SMALLFILE
    TABLESPACE "NNMI"
    LOGGING
    DATAFILE 'H:\ORADATA\NNMIDB\NNMI01.dbf' SIZE 4096M,
    'H:\ORADATA\NNMIDB\NNMI02.dbf' SIZE 4096M,
    'H:\ORADATA\NNMIDB\NNMI03.dbf' SIZE 4096M EXTENT MANAGEMENT
    LOCAL SEGMENT SPACE MANAGEMENT  AUTO

 

 

Section 2: Create NNMi User

CREATE USER "NNMI"  PROFILE "DEFAULT"
    IDENTIFIED BY "nnmi" DEFAULT TABLESPACE "NNMI"
    TEMPORARY TABLESPACE "TEMP"
    ACCOUNT UNLOCK;

  Section 3: Assign Permissions for NNMi User

GRANT CREATE ANY INDEX TO "NNMI" ;
GRANT CREATE ANY SEQUENCE TO "NNMI" ;
GRANT CREATE ANY TABLE TO "NNMI" ;
GRANT CREATE ANY VIEW TO "NNMI" ;
GRANT CREATE SEQUENCE TO "NNMI";
GRANT CREATE SESSION TO "NNMI" ;
GRANT CREATE TABLE TO "NNMI" ;
GRANT CREATE VIEW TO "NNMI" ;
GRANT FLASHBACK ANY TABLE TO "NNMI" ;
GRANT "CONNECT" TO "NNMI";
GRANT "OEM_ADVISOR" TO "NNMI";
GRANT "RESOURCE" TO "NNMI";

Step X Install NNMi 9.x

Install using the installation guide.

 

Step X Load old node list a seed files 

 

Step X Load Node Groups and Maps information

1- load Nodegroup Map configuration

loading Nodegroup Map configuration will fail as per the screenshot but some required identification are imported that facilitate the nodegroup import

D:\Program Files (x86)\HP\HP BTO Software\bin>nnmconfigimport.ovpl  -f C:\export
edconfig\ngmap.xml

2- Load nodegroup configuration

D:\Program Files (x86)\HP\HP BTO Software\bin>nnmconfigimport.ovpl  -f C:\export
edconfig\nodegroup.xml
Successfully imported nodegroup.xml.

3- load Nodegroup Map Configuration again

D:\Program Files (x86)\HP\HP BTO Software\bin>nnmconfigimport.ovpl  -f C:\export
edconfig\ngmap.xml
Successfully imported ngmap.xml.

Import Configuration from NNMi 8.X to 9.x : Part 1

In this article I am just giving example of on of the configuration setting that can be exported from NNMi 8.x to NNMi 9.x
Node Groups “nodegroup.xml” file contains nodegroup information in XML format, in NNMi 9.x there one more attribute is needed in the xml file which is not part of the export details
<ns2:calculateStatus>true</ns2:calculateStatus>
Open in Wordpad nodegroup.xml
From edit menu –> replace
in find what <ns2:additionalNodes/>  and in replace with write <ns2:additionalNodes/> <ns2:calculateStatus>true</ns2:calculateStatus>


Note: I have used find and replace (as stated above "to search for and to replace it with the same tag plus the line needed" )to make it easy in adding the tag as bere the example below I have highlighted this line just to clarify that this is the only addition needed.

<ns2:nodeGroup>
            <ns2:addToPerfSPIReports>true</ns2:addToPerfSPIReports>
            <ns2:addToViewFilterList>true</ns2:addToViewFilterList>
            <ns2:additionalNodes/> <ns2:calculateStatus>false</ns2:calculateStatus>             <ns2:children/>
            <ns2:filterExpressions/>
            <ns2:name>APC (American Power Conversion)</ns2:name>
            <ns2:nodeDeviceFilters>
                <ns2:item>
                    <ex:ref>
                        <ex:key>40e2ab16-e401-492f-88e0-88f81cb0c6c9</ex:key>
                        <ex:type>com.hp.ov.nms.monitoring.groups.model.NodeDeviceFilter</ex:type>
                    </ex:ref>
                </ns2:item>
            </ns2:nodeDeviceFilters>
            <ns2:parents/>
            <ns2:type>USER</ns2:type>
            <ns2:uuid>74e4ddba-9e82-4e91-a660-9b8f6fe4c267</ns2:uuid>
        </ns2:nodeGroup>

nnmconfigimport.ovpl -u system -p password -f nodegroup.xml

Using HP CAE to collect user information Part 1

You can use HP Client Automation Enterprise to local user accounts information and to be displayed as part of the built-in reports in HP Reporting Manager.

You can assign WBEM_USER_GROUP “WBEM Scan for User/Group “ under Audit domain to computer or OU to get this data collected.

Then notify computers for Audit

Install HP Performance Manager license

To install license to OVPM you can use the steps below

cd %ovinstalldir%\bin

ovpm license

a new text window is open for controlling license and you will get message like license expired

type gui to launch Autopass for OVPM

Select Install/restore License

Click Browse to locate the license file

Click view content

Click Install

Close the application

in the text program type status to get the current status.

now you can log to system normally

How to use WBEMTEST to get WMI data level 1

Launch wbemtest from command prompet or RUN

Here is the interface

to locate WMI classes attributes or instances you have to connect with account with sufficient privilege (note: all users has privilege to WMI but depend of type of action you want to execute which may require administrator priv.)

press on connect then type which namespace you want to connect to: by default Windows (Win32_*)built-in classes almost located under root\cimv2 then click connect.

This will connect you with the current user account, you may specify another account to gain more privilege

This is the screen after connection.

If you know certain class you can click on Open Class

If you do not know and you want to search manually you may click Enum Classes

To get all the classes you may select Recursive and press OK

A full list of classes will be displayed as below

Browse to any class and double click

for example User Account on the local machine are under Win32_UserAccount class

 

Click on Instances to list all the instances

Here is the list of User Account

 

To be continued.

please remind me to continue it.

Allow OVPI to send emails through Exchange 2007

Remember one thing that there is two tasks you should do

1- create Receive Connector to accept OVPI connection

2-PowerShell Command to assign Permission for anonymous to relay from OVPI

To troubleshoot this  Create dummy schedule and run the reports inside and you can open %dpipe_home%\log\piweb.log

If you got  Unable to relay

To use the Exchange Management Console to create a new Receive connector that grants the relay permission to anonymous connections

1. Open the Exchange Management Console. Perform one of the following steps:

   1. To create a Receive connector on a computer that has the Edge Transport server role installed, select Edge Transport, and then in the work pane, click the Receive Connectors tab.
   2. To create a Receive connector on a Hub Transport server role, in the console tree, expand Server Configuration, and select Hub Transport. In the result pane, select the server on which you want to create the connector, and then click the Receive Connectors tab.

2. In the action pane, click New Receive Connector. The New SMTP Receive Connector wizard starts.

3. On the Introduction page, follow these steps:

   1. In the Name: field, type a meaningful name for this connector. This name is used to identify the connector.
   2. In the Select the intended use for this connector: field, select Custom.
   3. Click Next.

4. On the Local network settings page, follow these steps:

1. Select the existing All Available entry, and then click .
2. Click Add. In the Add Receive Connector Binding dialog box, select Specify an IP address. Type an IP address that is assigned to a network adapter on the local server that is best able to communicate with the remote messaging server.

Note: In simple exchange implementation, you can leave it as default.

1. On the Local network settings page, in the Port field, type 25, and then click OK.
2. Click Next.

1. On the Remote Network settings page, follow these steps:

   1. Select the existing 0.0.0.0 - 255.255.255.255 entry, and then click .
   2. Click Add or the drop-down arrow located next to Add and type the IP address or IP address range for the remote messaging server or servers that are allowed to relay mail on this server. When you are finished entering the IP addresses, click OK.
   3. Click Next.

2. On the New Connector page, review the configuration summary for the connector. If you want to modify the settings, click Back. To create the Receive connector by using the settings in the configuration summary, click New.

3. On the Completion page, click Finish.

In the work pane, select the Receive connector that you created.

• Under the name of the Receive connector in the action pane, click Properties to open the Properties page.

• Click the Permission Groups tab. Select Anonymous users.

• Click OK to save your changes and exit the Properties page

Open the Exchange Management Shell.

• Run the following command using the name of the Receive connector that you created in steps 1 through 11:

  Get-ReceiveConnector "Receive Connector Name" | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "Ms-Exch-SMTP-Accept-Any-Recipient"

  
  

 

to list the Receive Connector Name you can type Get-ReceiveConnector

How to install SiteScope 10 License

1. Stop Sitescope service
2. Look for the following lines and check their values in master.config located in <sitescope dir>\groups (in Sitescope 10 they should be correct):
3. _doWorkWithConfigFilePersistency_current=true
4. _doWorkWithConfigFilePersistency_next=CHECKED
5. Change "_license", "_licenseOld" and "_licenseForX" values in master.config using a new valid license key.
6. Open <sitescope dir>\bin\PersistencyViewer.bat, select persistency folder under sitescope directory and then click open.
7. Select in the "Filter by type" "com.mercury.sitescope.platform.configmanager.MasterConfig" and double click on "__masterConfig"

1. Change "_license", "_licenseOld" and "_licenseForX" using same value used before, then click commit.
2. Select in the "Filter by type" "com.mercury.sitescope.platform.configmanager.preferences.PreferencesConfig" and double click on "GeneralDefaultPreferences_"
3. Change "_license", "_licenseOld" and "_licenseForX" using same value used before, then click commit.
4. Start Sitescope service.

Installing HP OM Agent on non-default drive

One day you may face a need to install agent on another drive “filespace in Unix based systems” to free up some of the space used by the Agent but keep in mind that the agent itself is not consuming much space but hp products (SPIs and Performance Agent) when being installed it is looking for the HP Software date directory and other certain variables and does not allow you to choose where to install their files.

So  I will show in the next few lines how to install the agent on another drive.

to give you an overview of the agent installation.

Agent installation files for Windows and Unix environment contain multiple components (for Windows-based there are multiple .msi files  and for Unix-based there are multiple .gz files for these components.) that need to be installed in certain  order to ensure the agent will work this process is done through an installation script called opc_inst (in Windows-based the file is named opc_inst.vbs)

• We supposed that we want to install the agent on drive e on windows environment so we may execute the below commands in the installation source files:

cscript.exe opc_inst.vbs -srv YOUROVOSERVER -cert_srv YOUROVOSERVER-inst_dir "E:\program files\HP\HP BTO software" -dd "E:\program files\HP\HP BTO software\data"

• In unix evironment you have to download the agent files and almost you have to change opc_inst file to be executable by using the command below

chmod +x ./opc_inst

then you can execute the command below

opc_inst -srv YOUROVOSERVER -cert_srv YOUROVOSERVER-inst_dir "/var/opt/OV" -dd "/var/opt/OV/data"

 

Ahmed Douban writes this comment.

Thanks mahmoud
-srv Managment Server Hostname or ip
-Cert_srv Certificate server ip "most cases same as Management Server"
-inst_dir is for Agent installation files binaries
-dd for the data directory... Read More
thanks for the nice subject :)

Install HP OM Agent on Windows

to install HPOM Agent formerly known as OVO agent on a Windows machine

you have to copy the source files to your Windows temp location “you can use ftp but be careful against the binary and ASCII files transfer modes for different files”

the files located in the HP OMU server in the following path.

/var/opt/OV/share/databases/OpC/mgd_node/vendor/ms/x86/winnt/A.08.xx.yyy/RPC_BBC/

xx.yyy is the version of the client depend on how your Management server is patched.

insure that there is FTP service is installed and SNMP service configured to answer the management server request about the machine type while you adding the new node

then launch the installation using cscript opc_inst.vbs

On the Management Server

At the same time you can go for adding new node by using the Manage Node Bank then Action --- Node --- Add

 

After the installation if you did not configure configuration file for the server information, you can use opcactivate.vbs to do the following.

C:\ms\x86\winnt\A.08.10.160\RPC_BBC>cscript "C:\Program Files\HP OpenView\\bin\OpC\install\opcactivate.vbs" -srv ia64-13 -cert_srv ia64-13
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.

opcactivate Info: OVO activation script starting ...
opcactivate Info: Setting MANAGER to user supplied value ia64-13
opcactivate Info: Getting core ID of OVO system ia64-13 ...
opcactivate Info: Pinging OVO system ia64-13 using BBC ...
opcactivate Info: Successfully pinged OVO system ia64-13. Parsing results file out.out ...
opcactivate Info: Core ID of OVO system ia64-13 is 1bbd1b10-eb84-7535-1e49-a630571e5970
opcactivate Info: Setting CERTIFICATE_SERVER to user supplied value ia64-13
opcactivate Warning: Not registering opcauth.dll. Passwordless switch-user operations for OVO actions will not be possible.
opcactivate Info: Not disabling remote trace access.
opcactivate Info: Killing OV services ...
opcactivate Info: Killed OV services.
opcactivate Info: Starting OVO agent ...
opcactivate Info: Successfully started OVO agent.
opcactivate Info: Successfully activated OVO agent.

C:\ms\x86\winnt\A.08.10.160\RPC_BBC>

 

On the OVO server

to insure communcation for your new client you have to make the server trust the client certificate

so Select Action – Nodes --- OVO Node Certificate Requests

 

Select the node from the Managed Nodes Bank then click on Map to Selected Node

After successful mapping select Grant

note: you will get this error message if your are not configuring DNS or HOSTs file correctly