Você está na página 1de 83

Tips and tricks for HP Operations

Manager, including how to successfully


migrate from UNIX to Linux

Hans-Peter Schmollinger
HP Operations Manager Unix Architect

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

Business Service
Management
Operations Center

2
Agenda

OMU 9 Overview
Demo
Virtualized environments
Migrating to HP OM 9
Tips and Tricks
Summary

3
OMU 9

Overview

4
Stability with HP Operations Manager
Investment protection with OM family of products
19 19 19 19 19 19 19 20 20 20 20 20 20 20 20 20 20 20
93 94 95 96 97 98 99 00 01 02 03 04 05 06 07 08 09 10
ITO OVOU OMU OMU OMU

Operations
OVOU
3.0 7.0 8.0 8.20 9.0 9.0
ITO VPO HP-UX Solaris
Manager Op
C
OpC 4.0 ITO
ITO
6.0 OVOU OMU
2.0 5.3 OMU OMU
on Unix 1. 5.0 8.10 8.27 8.31 8.35
0

Operations VPW
6.0
VPW
6.10
OVOW
7.0
OVOW
7.20
OMW
7.50
OVOW
00210
OVOW
00229
OMW
8.10
Manager
on Windows OVOW
7.10
OVOW
7.21
OVOW
00189
OVOW
00228
OMW
8.0
OMW
8.16

Operations OML

Manager 9.0

on Linux

Significant new functionality added OM UNIX/OM Windows/OM Linux consoles


from release to release can manage agents deployed from any server

Interoperability and Configuration Exchange


between UNIX /Windows/Linux management servers
Migration of server platform can still manage Product name changes for
―old‖ agents unless new functionality needed. marketing reasons only!
5
What‘s New?
Web-based Administration UI
Alignment/convergence of Operations Manager
New policy types
Cockpit view
OMi ready
OO integration
Platform support
–RHEL 5.2, 5.3 + Redhat Cluster 5.2, 5.3
–AMD and Intel x86-64
–Oracle 11
Operations Agent 8.60, Performance Agent 5.0
Performance Manager 8.21

6
Web-based Administration UI
New web-based Admin UI replaces the MOTIF UI

Supports multiple administrators with granular use roles

Online sync between admin and operator GUI,


e.g. nodes are added in realtime with no need for ―Reload configuration‖

7
Alignment/Convergence of OM
Policy versioning

Category based instrumentation/deployment

Same SPIs for all OM flavors

Policy exchange with OMW


Common web-service interfaces
(for OMU 8 as add-on)

8
Distinguish policy type
New Policy Types ‗GUI‘ and ‗agent‘
opcpolicy –list_pols
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)

9
OMi Ready
OMi
OMi with OML 9.0
HP BSM
Health TBEC
Foundation UCMDB
Event
– All events sent to OMi go via a single
OM server.
– All tools / action requests initiated from events
External
the OMi server are channelled thru the Notification
OM server to OM agents.
– Graphs require the agent infrastructure. OM OM SPIs
– All deployment / configuration of OM
Discovery
agents is initiated and performed from
the OM server(s).
– External notification interfaces (TT, Agents
alerts
Agents

paging etc.) are still maintained on the


OM server.
3rd
NNM OM SiteScope
party

Agents
Agents

10
New Operations Orchestration Integration
OO Command execution through OM Agent (OO 7.51.02)

– OO Remote Commands via Operations


manager
– Workflow steps execution with the OM agent
OM – Actions are delegated from OO to the OM
Console server using web services
– Access managed nodes securely through
Firewalls
2 3 – Reduce the credential management problem!

OM consolidates events from many sources. OM


Operations 4 Operations 1 Agents, NNM, SiteScope, BAC, 3rd parties, etc
Manager Orchestration
5 2 Central event console, actions, graphs
Users can invoke OO flows for troubleshooting
3
issues
1 6 7 4 Workflows update events

5 OO delegates command execution to OM


Remote OO OO command execution via the secure,
OM/PA 6
managed http OM communication channel
Agents
node 7 Remote command via telnet, ssh, etc

12
Demo

13
Demo

New policy types: E.G. Service Discovery, Advanced


Scripting
Policy parameterization

Performance Manager 8.21 integration

Cockpit view

More detailed demo at the booth

14
What Is Service Auto Discovery?
Provides generic infrastructure for OM SPI for discovering monitored
application(s)

SPIs provide specific discovery policies and instrumentation for the


applications they manage

With the new auto-discovery policy editor OM administrators can customize


the schedule for a discovery policy

Customized auto-discovery policies are deployed to a managed node using


the standard OM deployment mechanisms

Distributed discovery agents execute deployed policies and send discovery


results back to the discovery server on the management server, Service Tree
is populated with the discovered services

15

For HP and Channel Partner Internal Use.


Auto-discovery—the Big Picture

SPI Team Customer


Develops SPI Installs SPI

Instrumentation
Policy is
deployed Discovery
Policy
Model Discovery
Repository Cfg Policy
Upload Read/execute
Instrumentation
Writes
instances
Publish discovery agent
results

Discovery Communication
Server (BBC)
Management Server Managed Node

16
Service Auto Discovery

17
Script Based Thresholding

18
Script Parameters

Nodeinfo Policy Parameter Tap in Parameter use


;XPL config
Policy in perl threshold
[eaagt] evaluation
CpuUtilWarningThreshol overwrite use
d=2
if ($Session-
>Value('CPUbusytime') >=
$Session->
Value('CpuUtilWarningThre
shold')) {
$Rule-
>Status(TRUE);

Base Policy

Thresshold
changes done No need to change
per node in
node info
policy.
19
Additional Threshold Types

– Additional
Monitoring Types (Threshold Types):
VBScript, Perl
– Switching from single to multiple
sources automatically converts the
monitoring type to script-based.

When script is
selected as Monitor Type,
or when multiple sources
are defined
‗Parameters‘ tab
is added.

20
Embedded Scripting

Embedded scripts
(Perl/VBScript):
• Instance filters
• Threshold calculation
• Reset value
calculation

Script Parameters can


be referenced within
any policy script
21
Parameterized Threshold
You can use parameters

Script embedded
in Policy
# Get the values from sources
my $CPUbusytimeSrc = $Policy->Source(\"CPUbusytime\");
my $CPUbusytimeVal = $CPUbusytimeSrc->Value();
$Session->Value('CPUbusytime', $CPUbusytimeVal);

if ($Session->Value('CPUbusytime') >= $Session->


Value('CpuUtilWarningThreshold')) {
$Rule->Status(TRUE);
}

22
Script Parameters

Parameter values can easily be


adapted in one place

23
Script Parameters

Script embedded
in Policy
#PARAMETER CpuUtilWarningThreshold INT DEFAULT 85 VALUE 85 NODEINFO
\"CpuUtilWarningThreshold\" SESSION CAPTION \"CPU utilization level - Warning
threshold\"

my $CpuUtilWarningThreshold;
$CpuUtilWarningThreshold = $OVOSystem-
>ParameterGetNum(\"CpuUtilWarningThreshold\",85);
24
$Session->Value('CpuUtilWarningThreshold', $CpuUtilWarningThreshold);
Script Parameters

Script embedded
in Policy
#PARAMETER CpuUtilWarningThreshold INT DEFAULT
NODEINFO \"CpuUtilWarningThreshold\" SESSION CAP
utilization level - Warning threshold\"

my $CpuUtilWarningThreshold;
$CpuUtilWarningThreshold = $OVOSystem-
>ParameterGetNum(\"CpuUtilWarningThreshold\",85
$Session->Value('CpuUtilWarningThreshold', $CpuUtilWar

25
Recap: Script Parameters

Nodeinfo Policy Parameter Tap in Parameter use


;XPL config
Policy in perl threshold
[eaagt] evaluation
CpuUtilWarningThreshol overwrite use
d=2
if ($Session-
>Value('CPUbusytime') >=
$Session->
Value('CpuUtilWarningThre
shold')) {
$Rule-
>Status(TRUE);

Base Policy

Thresshold
changes done No need to change
per node in
node info
26
policy.
Parameterized Thresholds
Without Using Scripts

27
Without Script –
Default Thresholds in Measurement Threshold Policy

MaxThreshold_1_base policy

28

For HP and Channel Partner Internal Use.


Without Script –
Parameterized Thresholds in NodeInfo Policy
Use a NodeInfo policy to adapt the used value for the specific node!
You may even enable/disable the NodeInfo policy on the specific node
directly to work with the one or the other setting!

If you set thresholds,


place customized
values underneath
[eaagt.thresholds]

<arbitrary name> = <policy name>/<condition name>/<threshold>:<reset>

MaxThreshold_1_base policy

Use at the command line:


# opcragt -get_config_var ―eaagt.thresholds:" <my_nodes_list>
to view the parameterized values remotely
29

For HP and Channel Partner Internal Use.


Cockpit View

Web-based interface
displays state of
environment

Two main parts:


– Indicator Panel –
status of message
filers and groups of
message filters
– Java GUI – only
browser panel

30
Performance Manager 8.21
Integration
http://yogibear.deu.hp.com/LasVegas2008/OMU_OVPM0005.avi

31
Performance Manger 8.21 Integration
Updated integration contrib tool with OMU 8.31 patch:
#/opt/OV/contrib/OpC/OVPM/install_OVPM.sh

32
Performance Manager 8.21 Integration

1. Performance Manager 8.21 part of OML licenses.


2. Use script to upload tool/application definition
#/opt/OV/contrib/OpC/OVPM/install_OVPM.sh
3. Assign application group ―OVPM‖ to users/operator
4. NEW: Operator action defined by SPI‘s do launch
Performance Manager with context

33
Virtualized
Environments

34
Smart Plug-in for Virtual Infrastructure
HP Operations Manager

35
OM Agent Cloning

36 36
Application Template NEW Application
based on VMWares Instance

Clone

HP Operations Manager

37
OM Agent
Many 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 id
ovcoreid -create –force

2. # remove certificate
ovcert -remove `ovcoreid`

3. # adapt xpl conf variable OPC_NODENAME


ovconfchg -ns eaagt -set OPC_NODENAME `hostname`

4. # restart OM Agent
ovc –kill
ovc -start

5. # create new certificate request


ovcert -certreq

38
OM Agent
Ideally, 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/sh
PATH=$PATH:/opt/OV/bin/OpC:/opt/OV/bin
OPC_NODENAME=`ovconfget eaagt OPC_NODENAME`
HOSTNAME=`hostname`
if [ "$OPC_NODENAME" == "$HOSTNAME" ]
then
echo hostname $HOSTNAME not changed
exit 1
fi
echo y > /tmp/yes
echo >> /tmp/yes

# remove certificate
ovcert -remove `ovcoreid` < /tmp/yes
# create new core id
ovcoreid -create –force
# adapt xpl conf variable OPC_NODENAME
ovconfchg -ns eaagt -set OPC_NODENAME `hostname`
# restart OM Agent
ovc -kill
ovc –start
ovagtrep -clearall
# create new certificate request
ovcert -certreq
39
Some Tips and Tricks

40
Application Template NEW Application
based on VMWares Instance

Clone

1. Public Lock
1. Public Lock For Public key
For Public key

HP Operations Manager

Public Key HP Operations Manager HP Operations Manager

Public Key Public Key

41
Application Template NEW Application
based on VMWares Instance

Clone

2. NEW Lock
1. Public Lock to secure access
For Public key

HP Operations Manager Private Key

Public Key HP Operations HP Operations


Manager Manager

Public Key Public Key

42
4 Use Cases for Cloning Agents
1. The virtual system is cloned from an image and instantiated to get an own identity.
The responsible remote management server is already known on the virtual system.
The activation of the monitoring software shall happen as soon the system is started.

2. The virtual system is cloned from an image and instantiated to get an own identity.
The responsible remote management server is already known on the virtual system.
The activation of the monitoring software shall happen on demand of the management server.

3. The virtual system is cloned from an image and instantiated to get an own identity.
The responsible remote management server is not yet known on the virtual system.
The activation of the monitoring software shall happen as soon the system is started.

4. The virtual system is cloned from an image and instantiated to get an own identity.
The responsible remote management server is not yet known on the virtual system.
The activation of the monitoring software shall happen on demand of the management server.

White Paper
on the way
43
You Can Also Clone the
OML Mgmt Server

44
Application Template NEW Application
based on VMWares Instance

Clone

HP Operations Manager
Template HP Operations Manager

Clone

45
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 agent
h. Install new License (manual step)

46
OM Server (script which can be used)
#!/bin/sh

echo
usage()
{
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
usage
else
new_name=$1
new_name_long=${new_name}
echo new_long_hostame = $new_name_long
fi

if [ "$2" = "" ]
then
usage
else
address=$2
echo new address = $address
fi
if [ "$3" = "" ]
then
usage
else
old_hostname_long=$3
old_hostname=$3
echo old_long_hostame = $old_hostname_long
fi

if [ "$4" = "" ]
then
usage
else
old_ip=$4
echo old IP=${old_ip}
fi

PATH=$PATH:/opt/OV/bin:/opt/OV/bin/OpC
ORACLE_HOME=`grep ORACLE_HOME /etc/opt/OV/share/conf/ovdbconf | awk '{ print $2 }'`

echo ORACLE_HOME = ${ORACLE_HOME}


echo
echo

if [ "$5" = "nowait" ]
then
echo continue with nowait
else
echo "If this information is ok press ENTER to continue otherwise press CTRL-C to stop"
read y
fi

CURR_DIR=`pwd`
echo
echo 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 $list
do
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}
fi
done

if [ -f /etc/init.d/ovoracle ]
then
echo stopping database
/etc/init.d/ovoracle stop

echo starting db
/etc/init.d/ovoracle start
else
echo stopping database
/sbin/init.d/ovoracle stop

echo starting db
/sbin/init.d/ovoracle start
fi

# adapt OVO/U server


echo Change server name
set -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 `ovcoreid` -force -ovrg server
/opt/OV/bin/ovcm -newcacert ovcm -issue -file /tmp/ovnode.cert -name `hostname` -pass opc_op -coreid `ovcoreid` ovcert -importcert -file /tmp/ovnode.cert -pass opc_op ovcert -importcert -file /tmp/ovnode.cert -pass opc_op -ovrg server
ovconfchg -ns sec.core.auth -set MANAGER_ID `ovcoreid -ovrg server`
/opt/OV/bin/OpC/utils/opcnode -chg_id node_name=`hostname` id=`ovcoreid`

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 `ovcoreid -ovrg server`
ovconfchg -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 lic
if [ -f /opt/OV/contrib/OpC/AP-Tool.sh ] then
# reset instant on lic
echo reset lic
/opt/OV/contrib/OpC/AP-Tool.sh reset
else
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!"
fi
fi

echo Start server


ovc -start
ovc

echo Check server


set -x
opcsv -status
set +x

echo start OVO agent


ovc -start

echo remove cached signed policies


echo distribute new ovpolicies
set -x
rm -rf /etc/opt/OV/share/conf/OpC/mgmt_sv/templates/utf8/ux_compress/*
opcragt -distrib -templates -force
set +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

47
Virtual Appliance in OML Testcenter

48
Virtual Appliance in OML Testcenter

49
Virtual Appliance in OML Testcenter

50
Virtual Appliance in OML Testcenter

51
Virtual Appliance in OML Testcenter

52
Virtual Appliance in OML Testcenter

53
Virtual Appliance in OML Testcenter

54
OM in the Cloud

55

55
Don‘t Fear the Cloud
Key questions about systems monitoring and IaaS

How do I ensure the availability and performance of the systems, middleware


and applications running in the Cloud? Is that only up to the Cloud provider?

Do I need to buy new monitoring and management tools that are Cloud
ready? Can I use my well established tools and management processes?

Why should I treat those Cloud systems differently?

How do I manage those Cloud systems through the Internet? Do I have to


request additional open ports on my company‘s Firewalls?

Does this monitoring increase the required network bandwidth? How secure
and robust must the management solution be to mange through the Internet?

56
HP Operations Manager Is Cloud ready!
Anywhere and anytime ….
HP Performance Insight HP Operations Manager
Tickets
(NOC Console)
– Single console for HP Performance Manager

managing the in-house IT


infrastructure and the In-house
Performance graphs
systems hosted in public and reports

Clouds http DMZ


proxy OM HP
Your Intranet HP OM
– Leverages Investments made
agents
Agents Smart
Plug-ins
into management tools
– Smart plug-ins Internet
– Integration
– Secure and unidirectional HP OPC
SiteScope
HP OPC
RC Proxy Cloud
network communication i.e. Amazon EC2

– Ensures consistent upstream


processes such as incident HPOM
OM
management and SLM. HPOM
OM
agents
agents HP Smart
agents
agents
Plug-ins
57
Unified Monitoring of Physical, Virtual and
Cloud Systems
– Discovery and visualization of systems
and applications
– In-house and Cloud systems in one view

– Performance graphing and reporting


– Comparison of physical, virtual and
Cloud systems

– Single event console


– Unified processes
and integrations
58
Migrating to OM 9

59
Converting OMU 8 Templates
to OM 9 Policies
With HPOM 9.0x, templates have been converted to
policies. The conversion takes place automatically during
the upload. The version of all newly created policies is set
to 1.0, while the version of all HPOM 9.0x delivered
default policies is 9.0.

All HPOM 8.xx template assignments to nodes, node


groups, and template groups will point to 1.0 policy
versions after the migration to HPOM 9.0x. All HPOM
8.xx template assignments are converted into fix version
policy assignments.

All HPOM 8.xx monitor templates are converted into


monitor threshold policies during the migration.

60
Converting OMU 8 Templates
to OM 9 Policies
You can change
all policy group
assignments
modes at once

61
Format Differences
OM 9

Name = “Test”
header

InstanceId = “…”

UTF-8
SYNTAX_VERSION 6

MONITOR “Test"
DESCRIPTION “…”

UTF-8/
blackbox

text file

62
Tips and Tricks

63
Exchange of Configuration
between OMW 8.x
and OM 9

64
OMW/OMU/OML: Configuration Exchange
Slide 1

OMW 8.10 w/ OMU/L 9


W-> U ovowconfigexch. /opccfgupld
Nodes
U-> W opccfgdwn/ovowconfigexch.
W-> U ovowconfigexch. /opccfgupld
External Nodes
U-> W opccfgdwn/ovowconfigexch.
ovpmutil XML /
Services opcservive -add

ovpmutil/
Service Types opccfgupld
[for single files mof_cfgupld.sh]
65
OMW/OMU/OML: Configuration Exchange
Slide 2

OMW 8.10 w/ OMU/L 9


ovpmutil /
Agent Policies opcpolicy
[both directions]
ovpmutil /
Policy Groups opcpolicy
[both directions]
ovpmutil /
Instrumentation/
opcpolicy
Category
[both directions]
ovowconfigexch. /
Instruction Text opcpolicy

66
Policies
Exchange of configuration

OMW OMU/L 9

ovpmutil opcpolicy

import-
Policies policies
opccfgdwn Policies

67
Tips and Tricks with OMW Policies to OM 9?
Download policies on OMW server
– Using
ovpmutil CFG POL DNL <targetdir> /p <policy group path> /8x
/instrum

– E.G.
ovpmutil CFG POL DNL adv_hpux /p "SPI for Unix
OS\en\HP-UX\Advanced HP-UX Policies" /8x /instrum

Upload policies on OM 9 server


– Apply ‗opcpolicy –upload mode=replace dir=<directory>‘

This will also upload instrumentation/categories.


Hint:
You can use winzip on windows and unzip on linux to keep
directory structure.

68
Nodes
Exchange of configuration
OMW OMU/L 9
C:> ovowconfigexchange -ent NODES -dnl nodes -dest_codeset utf8
opccfgupld <path>/nodes

Nodes ovowconfig- opccfgdwn


Nodes
exchange

All nodes are put into nodebank\holding area

69
Services
Exchange of configuration

OMW OMU/L
ovpmutil [iconv] /
CFG XML opccfgupld
Services Services
x

70
Import of Service Model from
OMW to OMU/L
Use case: Use the graphical editor or service discovery with
OMW to create your service tree, then download and
upload on OMU/L

Synopsis: ovpmutil CFG XML DNL <configfile> /p


<serviceID>
– Can be used to download the complete subtree under <serviceID> into an XML file which
can be used with the OMU Service Navigator

– Creates an OMU/L compliant XML file

– Upload on OMU/L with


# opcservice –add <configfile>

71
Service Types, User Roles, Tools
Exchange of configuration

OMW OMU/L
Service Types can be installed on OMU via MOF files.

Service Types
x Service Types

x
User Roles User Roles
Tools Tools

72
Import of Service TypeModel from
OMW to OMU/L (this should not be necessary)

Synopsis: ovpmutil CFG SVT DNL ServiceType.mof


– Can be used to download the complete Service Types into a mof file

– Upload on OMU with


#/opt/OV/bin/OpC/utils/mof_cfgupld.sh <mof file>

– This should not be necessary because the SPI‘s do bring there mof files with them. If
you need to transfer a service discovery policy from windows to OMU then you
need to transfer also the related mof files.

73
Tips and Tricks with
Configfile Policy Type

74
7/8/2010
74
E.G. osspi_global_fsmon.cfg as configfile

75
E.G. linux.alarmdef as configfile
Everything below this header
SyntaxVersion=1
Application=Performance_agent In the body will be copied to
/var/opt/OV/conf/Performance_agent/
SubGroup=Alarmdef_for_Linux
Alarmdef_for_Linux/linux.alarmdef
Filename=linux.alarmdef /var/opt/OV/conf/$Application/

CallFunctionClassID= $SubGroup/$Filename

Data:
#$Installcommand=$OvPerlADir$/perl
$OvInstrumentationDir$/PostDeployActions.pl alarmdef
linux.alarmdef
#$Commandtype=3
After deployment
# @(#)alarmdef 05.00.000 01JUN2009 of the =*=
for PA/Linux policy
this script will be called
76
(post install script)
OM 9 LICENSING

77
License Migration
Customers upgrading from OMU 8.x to
OM 9 need to obtain a new OM
management server license key

Customer‘s existing Agent license keys


and Target Connector license keys will
continue to work with OM 9

Customers on support who have OMU 8.x


are entitled to NNMi license key which is
only supported on a remote OS instance

78
License Exchange
New bundle - HP Operations Manager,
Performance Manager, Reporter

Supported platforms – Linux, Windows,


HP-UX 11i, Solaris

HP Ops Mgr
Performance Manager

Reporter (Windows)

79
Summary

80
HP Operations Manager

Stable, ready to deploy, easy to migrate


–Management server now available on Linux

Leverage knowledge across OM‘s

Great scalability in a smaller footprint


Best in-class and most extensible event (message) management
– Huge message throughput improvement (more then 1500 msg/s)
Fits well into virtualized environments, cloud computing,
―Virtual Appliance‖

http://www.hp.com/go/opc
For more information, see, http://www.hp.com/go/opc

81
Q&A

82
To learn more on this topic, and to connect with your peers after
the conference, visit the HP Software Solutions Community:

www.hp.com/go/swcommunity
83 ©2010 Hewlett-Packard Development Company, L.P.
84

Você também pode gostar