HP Operations Manager Unix/Linux Tips and Tricks

©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Session ID: BTOT-TU-1800/2 Twitter hashtag #HPSWU

©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Speaker Name: Hans-Peter Schmollinger (OM Architect)Date: November 30, 2010Session ID: BTOT-TU-1800/2

HP Operations Manager Unix / Linux Tips and Tricks. Introduction of version 9.10 including HP Performance Manager.

Business Service ManagementOperations Center

Forward Looking Statements

This document contains forward looking statements regarding future operations, product development, product capabilities and availability dates. This information is subject to substantial uncertainties and is subject to change at any time without prior notification. Statements contained in this document concerning these matters only reflect Hewlett- Packard's predictions and / or expectations as of the date of this document and actual results and future plans of Hewlett-Packard may differ significantly as a result of, among other things, changes in product strategy resulting from technological, internal corporate, market and other changes. This is not a commitment to deliver any material, code or functionality and should not be relied upon in making purchasing decisions.

This is a Statement of Direction and is subject to change without notice.

HP Restricted. For HP and Channel Partner Internal Use. May be Shared with Select Customers.

AGENDA

OMU 9.10 Overview / What’s new

OM Agent 11

Cloud and Virtualized environments

PM 9 demo

More Tips & Tricks

6

OMU 9

OVERVIEW

Investment protection with OM family of productsStability with HP Operations Manager

Interoperability and Configuration Exchangebetween UNIX /Windows/Linux management servers

OM UNIX/OM Windows/OM Linux consoles can manage agents deployed from any server

Migration of server platform can still manage “old” agents unless new functionality needed.

Product name changes for marketing reasons only!

Significant new functionality added from release to release

1993

1994

1995

1996

1997

1998

1999

2000

2001

2002

2003

2004

2005

2006

2007

2008

OperationsManageron Unix

OperationsManageron Windows

OpC1.0 OpC

2.0

ITO

3.0 ITO

4.0 ITO

5.0

ITO

5.3

VPO

6.0

OVOU

7.0

OVOU

8.10

OVOU

8.0OMU

8.27OMU

8.31

OMU

8.20

VPW

6.0VPW

6.10

OMW

8.0

OMW

8.10OMW

7.50OVOW

7.20

OVOW

7.10

OVOW

7.0

OVOW

7.21OVOW00189

OVOW00210

OVOW00228

OVOW00229

2009

OML

9.01

OperationsManageron Linux

2010OMU

9.02Solaris

OMU

9.00HP-UX

OMU

8.35

OMW

8.16

OMU

9.10Linux,HPUX,Solaris

OMW

9.0

OMU

9.10Linux,HPUX,Solaris

RECAP: WHAT’S NEW in OMX 9?

Web-based Administration UI

Alignment/convergence of Operations Manager

New policy types

Cockpit viewBSM9/OMi ready

OO integration

Operations Agent 8.60, Performance Agent 5.0

9

OMU 9.x

Features

WEB-BASED ADMINISTRATION UINew web-based Admin UI replaces the MOTIF UI

Supports multiple administrators with granular user rolesOnline sync between admin and operator GUI, e.g. nodes are added in realtime with no need for “Reload configuration”

ALIGNMENT/CONVERGENCE OF OMPolicy versioning

Category based instrumentation/deployment

Same SPIs for all OM flavors

Policy exchange with OMWCommon web-service interfaces (for OMU 8 as add-on)

New Policy Types– Policy types

– Newly supported standard policy types • ConfigFile• Node Info• Service Auto Discovery• Service Process Monitoring• Windows Event Log• WMI

– Modified• Measurement Threshold

(previously: Monitor)

– Improved subagent handling (subagent policy type)

BSM 9 OMi Ready

Multi OM server can connect to BSM/OMi 9

Bi-directional Message sync via MoM interphase, including most message based operations. Tool launch still uses the Web-Service.

Run-Time sync of Node, Node Group, ServiceModel, Service Type.Also mass updates possible via discovery policy scheduled based

BSM 9 OMi with OMX 9.10

Multiple OM’s

(Win, OMX, OMi)

AgentsAgents

OMSiteScop

eNNM

3rd part

y

AgentsAgents alerts

DiscoveryOM SPIs

HP BSM Foundation

UCMDB

Event

HealthTBEC

Eventsand

Topology

Additional patch on top of OMX 9.10 needed to enable the Run-Time configuration sync

Patch version 9.10.200

What‘s New in Service Discovery?

• Create services, nodes, and node groups in OM using service discovery

• Create your own service type hierarchies using the service type editor

•Discovery data received from the agents can be forwarded to other OM/i servers

• Changes to the OM model can be forwarded immediately

•Nodes, node groups, and services on several management servers can be kept in sync

1. User defined service discovery policies

2. Discovery data forwarding

You must synchronize nodes between OM servers otherwise

messages will be „rejected“

User defined service discovery polices

Operational flow:

1. Create your own service type(s) (optional step)

2. Create the discovery policy using the Management Module „Custom Discovery“

3. Create the discovery script which outputs XML according to the description in the online help

4. Deploy policy and script (eg. as instrumentation) to an agent

Custom Discovery Policy

<Service>

<NewInstance ref="Biz Svc 1"> <Std>DiscoveredElement</Std> <Virtual /> <Key>BizSvc1</Key> <Attributes> <Attribute name="hpom_realstdid" value="{E23E...}" /> <Attribute name="hpom_captionformat" value=“Order Processing" /> </Attributes> </NewInstance>

<NewRelationship> <Parent> <Instance ref="SystemServices" /> </Parent> <Components> <Instance ref="Biz Svc 1" /> </Components> </NewRelationship>

</Service>

New Servic

e Virtual, not

hosted-on

Reference to service

type definition

ID

Caption /

Label

New compone

nt underneath System Services

Script producesXML stdout

Discovery data forwarding - Architecture

OM BSM9/OMi

OMA

OMNew

Service Discovery server Patch

9.10.200

Event-driven vs. scheduled synchronization

• Server component listening on config change events.

• Real-time: All changes will be forwarded immediately to other servers

• Changes may get lost when WMI discards events under high load

• Based on a discovery policy deployed to the agent running on the management server

• Used for initial synchronization of all data

1. Event-driven (immediate) synchronization

2. Scheduled synchronization

Combine both to get real-time sync and

guaranteed delivery

19

Performance Results

Core system tests 1Message Throughput depending on number of

Nodes (no GUI / 1 CMA! / opcle)

Criteria: event flow rate into DB

# of nodes OMWlow cost

HP-UX Linux 64low cost

Linux 64High(Customer tested)

1,000 400-180 1000 1450 2900

10,000 400-120 950 1300 2700

50,000 380-1001 870 1250 2620

12.000 active nodes simulated with

Loadrunner and OMLinux 64 bit

21

OMU/L 9.1 server enhancements

22 © Copyright 2010 Hewlett-Packard Development Company, L.P - For HP Internal and HP Partners only.

OMU/L 9.1 server enhancements• New CLI options for: opcragt, opcpolicy, opcsrvconfig, opctempl

• New server variables

• New APIs

• Secure SSL connection to connect to the HPOM web pages

• Licenses Modifications

• MIB to policy (mib2policy) contribution tools

• Backup / restore enhancements and fixes

• Cloning HPOM Management Server image

• Error message msg 40-665 for reused core IDs

• Perl wrappers for the incident web services

New CLI options for: opcragt, opcpolicy, opcsrvconfig, opctempl


•-> Generates a listing of the instrumentation files which would be deployed to an agent. Useful for troubleshooting.

opcragt -dist –simulate

•-> Immediately executes config deployment request for a named agent even if many deployment requests to other agents started earlier are still in progress.

opcragt -dist –highprio

•-> Modify the way how a policy is assigned to a policy group, node or node group (modes: fix mode, latest, minor_to_latest). Can also be used for mass updates.# opcpolicy -chg_assign_mode group=/a/b/c mode=LATEST mass_upd=yes

opcpolicy -chg_assign_mode

•-> List policies assigned to policy groups, nodes or node groups (several filter methods can be applied). Can also be used to make forecasts which assignments would be updated.

opcpolicy -list_pol_assigns

If the group attribute is not used then all assignments are

updated.Useful for development

env.

New CLI options for: opcragt, opcpolicy, opcsrvconfig, opctempl


•Lists assignment conflicts where different policy versions are indirectly assigned to the same agent (via policy groups or/and node groups).

opcpolicy -list_conflicts

•Lists the effective policies for a given agent. In addition can also list which agents receive a particular policy. Can be used for troubleshooting: Comparison betweenactive policies on the agent and policies which are assigned on the management server for this agent.Example:Execute on management server:/opt/OV/bin/OpC/utils/opcpolicy –list_resolved_assigns \ node_name=<my_node>

(accesses db)/opt/OV/bin/ovpolicy –list –host <my_node>

(access agent via RPC)

opcpolicy -list_resolved_assigns

Support of independent subnets with overlapping IP addresses


Feature can be enabled via# ovconfchg -ovrg server -ns opc -set OPC_ALLOW_DUPLICATE_IP TRUE

Different nodes with the same IP address must be reachable through HTTP proxies.

Not needed in NAT environments because NATed IP addressesneed to be unique on the management server anyway

Details in Administrator’s Reference-> HPOM Maintenance -> Duplicate IP Addresses for Different Managed Nodes

Full dup IP ready

New server variables - OPC_CSA_ALLOW_IP_MISMATCH


Enable ignorance of IP address mismatch in the certificate request via# ovconfchg -ovrg server -ns opc -set OPC_CSA_ALLOW_IP_MISMATCH TRUE

Could be useful for

• multi homed systems (the certificate request is sent from the non-primary IP address which is not the one in the DB)

• NAT environment

Feature was already introduced with A.08.35.010.

Secure SSL connection to connect to the HPOM web pages


Port number changes:

• HTTP - non-secure: 3443 is changed to 8081• HTTPS - secure: new 8444

Secure SSL connection can be used to connect to the HPOM web pages

Example: https://<management_server>:8444/ITO_OP

Overview

Licensing modifications

Admin GUI doesn't come up if no valid server license exists.• Server runs but login into Admin UI not possible if no valid OM license

exists.• Troubleshooting: Needs to restart Admin UI after installation of valid

licenses.Only one license need to be installed in HA environment.

Licenses can now be installed on shared disk in HA environments.License reporting tool, OM License Reporter (omlicreporter) introduced

• enables status and availability checks of HPOM licenses • generates HTML license reports.

HP OM License Reporter: omlicreporter


OM License Reporter (omlicreporter)

•checking HPOM licenses’•status•availability

•generating HTML license reports

The Admin UI does not run without a valid server license.

Note: Do not use the license report functionality in the Autopass GUI to check installed licenses. This functionality shows all installed license passwords, also those that are not valid on that system.

– HP OM License Reporter: omlicreporter


– Feature License Report• displays status of all licensed features

This ‘--’ means also ‘OK’This in the total

number of licenses of the groups ‘Operations OS Instances’, ‘Operations migration features’ and ‘Operations Tier based Agents’

OMU/L 9.1 server enhancementsCLI tool mib2policy transforms a MIB file into an SNMP trap policy

Syntax: mib2policy –p <policy_name> [options] <mib_file>

It’s a contribution tool, so not officially supported.

Location: /opt/OV/contrib/mib2policy/bin/mib2policy.sh

Feature was already introduced for• Linux via 9.01.300 (OML_00006)• Solaris via 9.02.300 (ITOSOL_00726)• Windows 8.1x via OMW_00058

For more information: mib2-policy –man

Hint: It’s not to convert NNM’s trapd.conf, but only for MIB sources.• NNM trap.conf files can still be converted into trap policies using

/opt/OV/bin/OpC/utils/ovtrap2opc – see man page for more information

Error message msg 40-665 for reused core IDs


Cloud readiness: Agent cloning

You get it when you do not initialize a VM copy (agent on VM – behaves as if it would be the ‘old’ agent, but isn’t, i.e. you would have several agents with the same Core ID, same certificate …)You get an error message.Multiple systems seem to use the same core ID 2e013b80-773c-7547-08d3-e206e3d0a0a2.Node in OMU database: elisa.deu.hp.com. Node which is not in DB: cloned.deu.hp.com withIP address(es) 1.2.3.4 and MAC address(es) 00:AB:CD:ED:12:34

Instruction text for 40-665 describes the solution for the problem.

Auto detection if

OM Agent got cloned and

still uses the same UUID

Perl wrappers for the incident web services


OMU/L 9.10 delivers Perl wrappers for the incident web services.

The according Perl modules with examples and docu are located in /opt/OV/contrib/OprWsIncPerl.

The Perl wrappers are for contribution only and not supported.

34

OM Unix/Linux 9.10 and SPI's

All SPI’s are available for OM Unix/Linux 9.10

Some add-on SPI patches are available since Nov. 2010

Businessapplication

Operating system

Database

Internetinfrastructure

Out-of-the-box coverage for many IT componentsused to support heterogeneous business processes

SPI’s for OM Unix/Linux 9.10 available

SOME TIPS AND TRICKS

37

VIRTUALIZEDENVIRONMENTS

OM in the private Cloud

38

YOU CAN CLONE THEOML MGMT SERVER

Application Template based on VMWares

NEW ApplicationInstance

Clone

HP Operations Manager

Man

age

HP Operations ManagerTemplate

Man

age

Clone

OM Server– It is more common now to ignite or clone an additional OM server via image

template

– This image need some modifications which are all possible within CLI’s and scripting.a. Need to change internal OM related config files b. DB listener files to the new hostname + ipaddress c. Create a new ovcoreid for agent and server d. Create a new set of node + root certificates e. Restart oracle and OM server + agent f. Need to clean policy cache g. Deploy policies to local agenth. Install new License (manual step)

OM Server (script which can be used) #!/bin/sh echousage(){ echo echo "Usage: $0 <new_long_hostame> <new_IP_Address> <old_long_hostame> <old_IP_Address> [ nowait ]"echo It is more common now to ignite or clone an additional OM server echo via image template.echo This image needs some modifications which are all possible echo within CLIs and scripting, thats the purpose of this script. echo The script does:echo - change internal OM related config files echo - DB listener files to the new hostname + ipaddress echo - Create a new ovcoreid for agent and server echo - Create a new set of node + root certificates echo - Restart oracle and OM server + agent echo - Need to clean policy cache echo - Deploy policies to local agent echo "- At the end install new License (manual step)" exit} if [ "$1" = "" ]then usageelse new_name=$1 new_name_long=${new_name} echo new_long_hostame = $new_name_longfi if [ "$2" = "" ]then usageelse address=$2 echo new address = $addressfiif [ "$3" = "" ]then usageelse old_hostname_long=$3 old_hostname=$3 echo old_long_hostame = $old_hostname_long fi if [ "$4" = "" ]then usageelse old_ip=$4 echo old IP=${old_ip}fi

PATH=$PATH:/opt/OV/bin:/opt/OV/bin/OpCORACLE_HOME=`grep ORACLE_HOME /etc/opt/OV/share/conf/ovdbconf | awk '{ print $2 }'` echo ORACLE_HOME = ${ORACLE_HOME}echoecho if [ "$5" = "nowait" ]then echo continue with nowaitelse echo "If this information is ok press ENTER to continue otherwise press CTRL-C to stop" read yfi CURR_DIR=`pwdèchoecho start adapting OM server to new hostname and IP address echo echo stopping OVO server ovc -stop echo stopping OVO agent ovc -kill echo adapt files: list="${ORACLE_HOME}/network/admin/listener.ora${ORACLE_HOME}/network/admin/tnsnames.ora/opt/OV/nonOV/tomcat/b/www/webapps/topaz/WEB-INF/classes/Tomcat_ConfigResources.properties/opt/OV/www/htdocs/ito_op/ito_op_ws.jnlp/opt/OV/OMU/adminUI/data/init/ovo/selfmon/C/APPLICATIONS/applications.dat/opt/OV/OMU/adminUI/conf/jetty.xml" for i in $listdo if [ -f ${i} ] then echo change file: ${i} cp ${i} ${i}.keep eval sed -e 's/${old_hostname}/${new_name}/g' ${i} > ${i}.tmp mv ${i}.tmp ${i} fidone if [ -f /etc/init.d/ovoracle ]then echo stopping database /etc/init.d/ovoracle stop echo starting db /etc/init.d/ovoracle startelse echo stopping database /sbin/init.d/ovoracle stop echo starting db /sbin/init.d/ovoracle startfi # adapt OVO/U serverecho Change server nameset -x/opt/OV/contrib/OpC/opcchgaddr -force -label ${new_name} IP ${old_ip} ${old_hostname_long} IP ${address} ${new_name_long} if [ "$?" != "0" ] then echo use opcchgaddr with NETWORK_IP /opt/OV/contrib/OpC/opcchgaddr -force -label ${new_name} NETWORK_IP ${old_ip} ${old_hostname_long} NETWORK_IP ${address} ${new_name_long} fi set +x /opt/OV/bin/OpC/opcsvcertbackup -force -remove -passwd opc_op -file /tmp/opc.cert ovcoreid -create -force ovcoreid -set òvcoreid` -force -ovrg server /opt/OV/bin/ovcm -newcacert ovcm -issue -file /tmp/ovnode.cert -name `hostname` -pass opc_op -coreid òvcoreid` ovcert -importcert -file /tmp/ovnode.cert -pass opc_op ovcert -importcert -file /tmp/ovnode.cert -pass opc_op -ovrg serverovconfchg -ns sec.core.auth -set MANAGER_ID òvcoreid -ovrg server`/opt/OV/bin/OpC/utils/opcnode -chg_id node_name=`hostname` id=òvcoreid` echo change XPL conf# Change all entries with with old server name to new serve name use below command:ovconfchg -ns eaagt -set OPC_IP_ADDRESS ${address}ovconfchg -ns sec.cm.client -set CERTIFICATE_SERVER ${new_name_long}ovconfchg -ns sec.core.auth -set MANAGER ${new_name_long}ovconfchg -ns sec.core.auth -set MANAGER_ID òvcoreid -ovrg serveròvconfchg -ns sec.core.auth -set CERTIFICATE_SERVER ${new_name_long} # Also server group has to be changed use:ovconfchg -ovrg server -ns opc -set OPC_MGMT_SERVER ${new_name_long} LIC="Instant on license: ` /opt/OV/bin/ovolicense -l`"# reset licif [ -f /opt/OV/contrib/OpC/AP-Tool.sh ] then # reset instant on lic echo reset lic /opt/OV/contrib/OpC/AP-Tool.sh resetelse if [ -f /net/elisa.deu.hp.com/VM_DATA/AP-Tool.sh ] then # reset instant on lic echo reset lic /net/elisa.deu.hp.com/VM_DATA/AP-Tool.sh reset else LIC="Make sure to install a valid OM Server license!" fifi echo Start serverovc -startovc echo Check serverset -xopcsv -statusset +x echo start OVO agentovc -start echo remove cached signed policiesecho distribute new ovpoliciesset -xrm -rf /etc/opt/OV/share/conf/OpC/mgmt_sv/templates/utf8/ux_compress/*opcragt -distrib -templates -forceset +x # cd /opt/midas31 cd /opt/OV/OMU/adminUI ./midas.sh ant -f conf/ant/admin.xml rename_hostname -Dhost=$new_name_long ./midas.sh ant -f conf/ant/admin.xml rename_backend -Dbackend=${new_name_long}_server ./midas.sh clean /opt/OV/bin/ovc -start # update URLS to launch admin out of JAVA GUI opccfgupld -replace -subentity /opt/OV/OMU/adminUI/data/init/ovo/selfmon opcmsg a=a o=o msg_t="server switch to ${new_name_long} successful done!" echo echo $LIC echo

Scrip

t part

of OMX

9.10

/opt/OV/co

ntrib/O

pC/om_serv

er_switc

h.sh

Also u

sed w

ith th

e SLI

CK POC

inst

allatio

n!

OM Agent cloning

43

Application Template based on VMWares

NEW ApplicationInstance

Clone

HP Operations Manager

Man

age

OM AgentMany customers do clone images for fast rollout of services and applications.You can also clone an OM Agent easily but you have to make sure to follow the below steps otherwise run into some trouble.

After cloning a machine which usually includes hostname and ip-address change as well you need to do the below steps:1.# create new core idovcoreid -create –force

2.# remove certificateovcert -remove òvcoreid`

3.# adapt xpl conf variable OPC_NODENAMEovconfchg -ns eaagt -set OPC_NODENAME `hostname`

4.# restart OM Agentovc –killovc -start

5.# create new certificate requestovcert -certreq

OM AgentIdeally, you can create a clone template, which runs the script below automatically after cloning. May be integrate this into the startup of the agent.

#!/bin/shPATH=$PATH:/opt/OV/bin/OpC:/opt/OV/binOPC_NODENAME=òvconfget eaagt OPC_NODENAME`HOSTNAME=`hostnameìf [ "$OPC_NODENAME" == "$HOSTNAME" ]then echo hostname $HOSTNAME not changed exit 0fiecho y > /tmp/yesecho >> /tmp/yes

# remove certificateovcert -remove òvcoreid` < /tmp/yes# create new core idovcoreid -create –force# adapt xpl conf variable OPC_NODENAMEovconfchg -ns eaagt -set OPC_NODENAME `hostname`# restart OM Agentovc -killovc –startovagtrep -clearall# create new certificate requestovcert -certreq

Error message msg 40-665 for reused core IDs


Cloud readiness: Agent cloning

You get it when you do not initialize a VM copy (agent on VM – behaves as if it would be the ‘old’ agent, but isn’t, i.e. you would have several agents with the same Core ID, same certificate …)

You get an error message.Multiple systems seem to use the same core ID 2e013b80-773c-7547-08d3-e206e3d0a0a2.Node in OMU database: elisa.deu.hp.com. Node which is not in DB: cloned.deu.hp.com withIP address(es) 1.2.3.4 and MAC address(es) 00:AB:CD:ED:12:34

Instruction text for 40-665 describes the solution for the problem.

Auto detection if

OM Agent got cloned and

still uses the same UUID

HP Operations Agent 11.00

Focus Area

Operations Agent 11.00 • Bringing together of the Operations, Performance agents and Glance product lines into one installed agent• Reduced complexity of component conflicts • Reduced install time• Ability to monitor IPv6 nodes• Real-Time Metric Server for Operations Customers

Features

HP Operations Agent 11.00What’s New

•One installable package delivering the combined Operations, Performance Agent and GlancePlus

Unified Agent

•Agent Install Media/ESD•Chang

e from the current OM release vehicle

•Releases independent of OM management server

Unified Release Vehicle

New OM Agent patch

OM Agent 11 is a new media release

OM Agent patch 8.60.501 brings the Eaagt to the 11 code base.

51

Already available

HP Performance Manager 9.0

What’s new?

HP Performance Manager 9.0What’s New

Diagnostic View for highly interactive graphs

Real-Time Measurement datasource

Integration with SiteScope 11.0

Support for Active Directory based authentication

Ability to save the state of the UI for future use

Improved performance of nodelist

URL Based launch to show only graph window

Advanced Date Range Panel for better correlation of metrics

Improved nodelist search

HP Performance Manager 9.0Ability to switch between Real-Time and Near-Real-Time dataAbility to navigate to any timeframe in the agent

Guided Drilldown options for better troubleshooting

Reorganized out-of-the-box Graph Templates

Support for vMA version 4.0

Support for Firefox 3.6 browser

Support for RHEL 5.4

Configurable import of Reporter Nodelist

Defect fixes


•Highly interactive UI with features like drag and drop of metrics, adding/removing metrics, resizing of graphs, and so on.

•Compare multiple systems/instances simultaneously in the same/different graph.

•Easily navigate to any timeframe in the agent.

•Use the Date Range Panel to correlate metrics across timeframes.

•Drag and drop metrics from different graphs into single graph for better correlation.

•Export graph data into formats like CSV, TSV, Excel and XML.

Diagnostic View

Diagnostic View

56

Month Year [or Rev. #]


•Drawing graphs from Real Time Measurement datasource for real time performance graphs.

•Multi-level guided drilldown for easy Root Cause Analysis.

•Configurable list of metrics for default graphs/drilldown tables.

•Look at Real-Time data alongside Near-Real-Time data for better analysis.

Real-time DataSource

Real-Time Datasource

58

Month Year [or Rev. #]

Global History Graph needs to be enabled

59

/opt/OV/newconfig/OVPM/VPI_GraphsAgents.txt.bkp

To enable move toVPI_GraphsAgents.txt


•Draw graphs from Agentless(SiteScope) datasource.

•Seamless graphing of both agent based and agentless datasources.

•Configure HP SiteScope 11.0 to log data into HP Operations Agent, which can be retrieved by HP Performance Manager.

•Import nodes being monitored by HP SiteScope into HP Performance Manager.

•Configure HP Performance Manager to integrate with multiple HP Sitescope servers.

Integration with

SiteScope 11.0

SIS Log Files

SiteScope

CODA

OM Server & Performance

Manager

Node 1 Node 2 Node 3 Node N

Agentless

Node 1 Node 2 Node 3 Node N

Agent based

Monitor A, B, C Monitor A, B, D Monitor E, F Monitor X,Y OA PA PA

SiteScope Server

OA

PM - SiteScope Integration

62

OML/U PM integration

DEMO

Demo PM 9 / OM Agent 11 Realtime Graph

Contrib convert OM Nodes and Node Groups into PM

Tips and Tricks withconfigfile policy type

6404/13/2023

E.G. Alarmdef as configfile

E.G. linux.alarmdef as configfile

SyntaxVersion=1

Application=Performance_Collection_Component

SubGroup=Alarmdef_for_Linux

Filename=linux.alarmdef

CallFunctionClassID=

Data:

#$Installcommand=$OvPerlADir$/perl $OvInstrumentationDir$/PostDeployActions.pl alarmdef linux.alarmdef

#$Commandtype=3

# @(#)alarmdef 11.00.000 for PA/Linux =*=

After deployment of the policy

this script will be called

(post install script)

Everything below this header

In the body will be copied to/var/opt/OV/conf/Performance_agent/

Alarmdef_for_Linux/linux.alarmdef

/var/opt/OV/conf/$Application/

$SubGroup/$Filename

Q&A

Continue the conversation with your peers at the HP Software Community hp.com/go/swcommunity

Backup

HP Insight Integration for HP Operations Manager

ProLiant and Integrity server system monitoring

Web interface integration

Event forwarding

• Direct IM agent to OM agent integration. Capture events for server hardware problems.

• Very valuable in firewalled environments (DMZ, MSP use cases)

• Enables users to initiate contextual launch of HP SIM for a selected device. Page is provided by the HP SIM CMS.

• Launch the web interface for HP SIM, and the HP System Management Homepage.

• Show HP Server heath in HP OM and HP BSM consoles.• HP SIM events are forwarded to the HP OM. SIM events are

processed, classified and visualized on the HP-OM server. Further escalation paths to HP-OMi or ticket systems via standard integration.

• Uni-directional event acknowledgement/clearing on HP SIM

iHP Insight Integration for HP OM

HP Insight Integration

HP OM

HPSIMCMS

OpsBridge Operator SystemsSME

IM Agents

OM AgentsOM Agents

OM Agents

SIM CMS / HP OM integration

IM agent to OM agent integration

OMi, SM7, Remedy, etc

HP SiteScope for HP Operations Manager

“opcactivate”

Grant certificate Lo

g File

– Enables SiteScope to send events to OMSITESCOPE 11 ADAPTER

• Direct SiteScope to OM/OMi connection

• Ability to trigger events according to:

• Monitor’s metric status change

• Alert being fired• Much more integrated:

• OM agent is part of SiteScope installation

• Configured easily from SiteScope UI

• Has full event attributes values configuration – per monitor/alert instance

• Improved scalability and usability

• Automatic node creation of SiteScope monitored targets

Continue the conversation with your peers at the HP Software Community hp.com/go/swcommunity

Documents

HP Operations Manager Unix/Linux Tips and Tricks