1. Make sure HP NNMi and HP BSM Connector are installed on same server.
2. Login into HP NNMi UI and create a new admin level user.
3. Goto path “C:\ProgramData\HP\HP BTO Software\Conf\backsync” and rename the file “OMBackSync.pl” to “OMBackSync.pl.original”
4. Copy the attached file to you desktop and copy the content to a text pad and then save it as “OMBackSync.pl”.
Now copy the file to the path “C:\ProgramData\HP\HP BTO Software\Conf\backsync”. (Make sure the file name is “OMBackSync.pl”) on the server where BSM Connector is installed.
5. Open OMBackSync.pl and update the following lines in the script:
my $nnmi_user = ‘username’;
my $nnmi_pass = ‘password’;
6. Run the following commands:
Open command prompt “Run as administrator” and goto path – “c:\Program Files (x86)\HP\HP BTO Software\newconfig\HPNmsCommon\scripts” and run the below commands:
a) nnm-configure-perl.ovpl -source “c:\Program Files (x86)\HP\HP BTO Software\newconfig\HPNmsCommon\perl\a” -target “c:\Program Files (x86)\HP\HP BTO Software\nonOV\perl\a”
b) ovc -restart ombacksync (once this command is run, make sure ombacksync is in running state)
7. Deactivate the present “NNMi Management Events” policy which is deployed from BSM Connector for HP NNM – HP OMi Integration
8. Recreate a new policy from NNMi server using the following command to take the effected changes:
nnmopcexport.ovpl -u system -p password -template “NNMi Management Events” -application “NNMi” -omi_policy -omi_hi
9. Load the new policy into BSM Connector and activate the same.
10. Test the backsync by carrying out following steps:
a.Login into NNMi and select a node for testing.
b.Goto HP NNMi JMX console and create a test event “Node Down” for the specific node
c.Make sure you see the event in HP NNMi under “Incident Management Open Key Incidents” and also in HP OMi “Event Prespective”
d.Also confirm respective auto-ticket is created in configured ITSM tool.
e.Now close the ticket in ITSM which in turn acknowledges the event in OMi and this should close the event in HP NNMi. (ITSM and HP OMI bi-directional integration should be in place before carrying out these steps).
While downloading the BSM media, we can see there are 4 Data Collectors available for download at the HP Site.
For your reference I have mentioned below the Data Collector names and what’s available in the Data Collectors.
Based on which you can download only the required once.
Software_HP_BSM_9.20_Data_Collectors_1: BPM, Vugen, RUM Installation bits
Software_HP_BSM_9.20_Data_Collectors_2: SiteScope Installation bits
Software_HP_BSM_9.20_Data_Collectors_3: Diagnostics Installation bits
Software_HP_BSM_9.20_Data_Collectors_4: BPI, DataFlowProbe, TV, UCMDBBrowser Installation bits
1. Go to the db manager (db) from SM Command bot.
2. Search for “screlconfig” table
3. Do a search and pull up the filename “cm3r”
Add the below line in “Post Open Expressions” (copy attachment from interaction to change)
if (filename($L.related)=”cm3r” and filename($L.primary)=”incidents”) then ($L.void=rtecall(“blobcopy”, $L.rc, “incidents”, incident.id in $L.primary, “cm3r”, number in $L.related))
Save and Exit
4. Do a search and pull up the filename “problem”
Add the below line in “Post Open Expressions” (copy attachment from interaction to incident)
if (filename($L.related)=”probsummary” and filename($L.primary)=”incidents”) then ($L.void=rtecall(“blobcopy”, $L.rc, “incidents”, incident.id in $L.primary, “probsummary”, number in $L.related))
Save and Exit
5. Logoff and Loginto SM and test by escalating the interaction to incident and change.
NNM9i all incidents view auto refresh is OFF.
You can turn on the same from the following location:
Change the following attribute : “com.hp.ov.nms.ui.refreshViewSecs.allIncidentsTableView = 60”
Restart ovjboss to take the changes effect.
HP Service Manager 9.X Implementation – Basic Port Requirement.
SM App Server should be accessible (two way communication) at port 13080 – 13100, 12670, 12690
SM Web server should be accessible (two way communication) at 7080, 8080, 9080, 80, 443 from all desktops and laptops
The port between SM Web and SM app should have a two way communication on 13080 – 13100
One of the major requirement we get form customers is to suppress the events from managed nodes during some activity going on server like patching, upgrades, restart, maintenance during which a large number of messages are triggered and some times it may lead to message flooding.
To achieve “Event Suppression” there is a file named “outage” in OML/OMU to control the flow of the messages.
The following steps are carried out to achieve the same:
1. Login into Operations Manager server using putty.
2. Go to the path and open the file “/etc/opt/OV/share/conf/OpC/mgmt_sv/tmpl_respmgrs/outage”
3. Edit the file as per your requirements. I am drafting a sample file which can be used for simple suppression’s, for any further customization you can refer to Admin Document of the product.
DESCRIPTION "template match service hours"
TIME FROM 09:00 TO 18:00
DATE ON 01/01/2014
CONDSTATUSVAR "CUSTOMER" True
DESCRIPTION "Outage Definition"
DESCRIPTION "MSGTARGETRULE for Maintenance Nodes"
DESCRIPTION "MSGTARGETRULECOND for maintenance nodes"
NODE IP 0.0.0.0 "nodename1"
NODE IP 0.0.0.0 "nodename2"
4. Once the above file is created. Copy the file to following location:
5. For the first time when you are creating the file you need to restart the management server processes (opcsv -stop & opcsv -start). Later any changes you make to the outage file you can just run the command “opccfgout -update”
As soon as you start the JAVA UI for your OML/OMU Management Server, it shows a default messages :
“welcome to HP Operations Manager for UNIX version 09.10.220. This release provides a lot of new functionality – especially in the area
of predictive service operations,improved ease of use and consistency as well as alignment with the Operations Manager for Windows to
allow customers to manage heterogeneous. IT infrastructure from a single pane of glass.”
In present days most of the customers want a custom message to be displayed to their employees. Follow the below steps to achieve the same:
1. Create a text file on OML/OMU management server with your custom data and save the file in any location.
2. Now execute the following command to set the custom messages as your JAVA UI start-up message.
opcuistartupmsg -f /tmp/filename.txt -e
3. You can cross check the same if the changes are taken place:
opcuistartupmsg -s –> will show the startup text message.
When there are issues with certificate request and granting on managed nodes and management server.
The following commands can be used to quicken the process.
1. Execute the following command on management server to generate a certificate for managed node.
opcnode -list_id node_list=Managed_Node_FQDN
Copy the coreid of the managed node from the above command output.
ovcm -issue -file filename-name Managed_Node_FQDN -coreid Managed_Node_Coreid -pass Any_Password
Now, transfer the generated file to the managed node and execute the following command:
ovcert -importcert -file file-name -pass Password_given_during_cert_creation
Once the certificate is imported successfully to the managed node, restart the agents (ovc -kill & ovc -start)
Now you should be able to get the agent status remotely from the management server (opcragt mgd_node_name)
Usually with standalone NNM9i product to trigger mails for events we use Blat or AlarmPoint Express.
Blat Usage has already been discussed in my blog, you can access the same from the below link:
Now, most of you have worked on Alarm Point Express Edition. Out-of-Box there are couple of alerts. Usually in NNM there are large numbers of the events that are very important. There are 2 files in Alarm Point which need to be edited to achieve the same.
I am attaching both the files to this blog for reference.
Below commands are useful to check the Status – Start – Stop the OMW Management Server Processes.
URL to access the web console of the OMW server.
Open the command prompt on the OMW Management Server with Administrator Privileges and execute the below commands
Command to Check the OMW Management Server Process:
vpstat -3 -l
To Stop and Start the OMW Management Server Process:
vpstat -3 -r STOP
vpstat -3 -r START
To Check the Management Server Local Agent and Performance Agent Status:
ovc -status –> Local Control Agent Status
opcagt -status –> Local Agent Status
perfstat -p –> Performance Agent Status
Web Page Access to OMW Console: (To be opened from Internet Explorer)