migration to oml9 tips-tricks

83
1 ©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice Tips and tricks for HP Operations Manager, including how to successfully migrate from UNIX to Linux Hans-Peter Schmollinger HP Operations Manager Unix Architect

Upload: mooooo0

Post on 01-Dec-2014

398 views

Category:

Documents


9 download

TRANSCRIPT

Page 1: Migration to OML9 Tips-Tricks

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

Tips and tricks for HP Operations Manager, including how to successfully migrate from UNIX to Linux

Hans-Peter SchmollingerHP Operations Manager Unix Architect

Page 2: Migration to OML9 Tips-Tricks

2

Business Service ManagementOperations Center

– Subtitle goes here

Page 3: Migration to OML9 Tips-Tricks

3

Agenda

OMU 9 Overview

Demo

Virtualized environments

Migrating to HP OM 9

Tips and Tricks

Summary

Page 4: Migration to OML9 Tips-Tricks

4

OMU 9

Overview

Page 5: Migration to OML9 Tips-Tricks

5

Investment protection with OM family of products

Stability with HP Operations Manager

1993

1994

1995

1996

1997

1998

1999

2000

2001

2002

2003

2004

2005

2006

2007

2008

OperationsManageron Unix

OperationsManageron Windows

OpC

1.0

OpC

2.0

ITO

3.0ITO

4.0 ITO

5.0

ITO

5.3

VPO

6.0

OVOU

7.0

OVOU

8.10

OVOU

8.0

OMU

8.27OMU

8.31

OMU

8.20

VPW

6.0VPW

6.10

OMW

8.0

OMW

8.10

OMW

7.50OVOW

7.20

OVOW

7.10

OVOW

7.0

OVOW

7.21OVOW

00189

OVOW

00210

OVOW

00228

OVOW

00229

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

2009

OML

9.0

OperationsManageron Linux

2010OMU

9.0Solaris

OMU

9.0HP-UX

OMU

8.35

OMW

8.16

Page 6: Migration to OML9 Tips-Tricks

6

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

Page 7: Migration to OML9 Tips-Tricks

7

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‖

Page 8: Migration to OML9 Tips-Tricks

8

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)

Page 9: Migration to OML9 Tips-Tricks

9

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)

opcpolicy –list_pols

Distinguish policy type ‗GUI‘ and ‗agent‘

–Improved subagent handling (subagent policy type)

Page 10: Migration to OML9 Tips-Tricks

10

OMi Ready

– All events sent to OMi go via a singleOM server.

– All tools / action requests initiated from the OMi server are channelled thru the OM server to OM agents.

– Graphs require the agent infrastructure.– All deployment / configuration of OM

agents is initiated and performed from the OM server(s).

– External notification interfaces (TT, paging etc.) are still maintained on the OM server.

OMi with OML 9.0

OM

AgentsAgents

OM SiteScopeNNM3rd

party

AgentsAgentsalerts

Discovery

OM SPIs

HP BSM Foundation UCMDB

Event

Health TBEC

eventsExternal

Notification

OMi

Page 11: Migration to OML9 Tips-Tricks

12

OperationsManager

OM/PA Agents

OperationsOrchestration

1

2 3

OM consolidates events from many sources. OM Agents, NNM, SiteScope, BAC, 3rd parties, etc1

Central event console, actions, graphs2

Users can invoke OO flows for troubleshooting issues

3

OO delegates command execution to OM5

Workflows update events4

OO command execution via the secure, http OM communication channel

6

Remote command via telnet, ssh, etc7

Remote OOmanaged

node

OMConsole

5

76

4

– OO Remote Commands via Operations manager

– Workflow steps execution with the OM agent

– Actions are delegated from OO to the OM server using web services

– Access managed nodes securely through Firewalls

– Reduce the credential management problem!

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

Page 12: Migration to OML9 Tips-Tricks

13

Demo

Page 13: Migration to OML9 Tips-Tricks

14

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

Page 14: Migration to OML9 Tips-Tricks

15

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

For HP and Channel Partner Internal Use.

Page 15: Migration to OML9 Tips-Tricks

16

Management Server Managed Node

Policy is deployed

Instrumentation

DiscoveryPolicy

discovery agent

Read/execute

Model Repository

Writesinstances

SPI TeamDevelops SPI

CustomerInstalls SPI

Instrumentation

DiscoveryPolicyCfg

Upload

Communication

(BBC)Discovery

Server

Publishresults

Auto-discovery—the Big Picture

Page 16: Migration to OML9 Tips-Tricks

17

Service Auto Discovery

Page 17: Migration to OML9 Tips-Tricks

18

Script Based Thresholding

Page 18: Migration to OML9 Tips-Tricks

19

Script Parameters

overwrite

Nodeinfo Policy;XPL config

[eaagt]

CpuUtilWarningThreshold=2

Base Policy

Parameter Tap in Policy

Parameter use in perl threshold evaluation

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

$Rule->Status(TRUE);

use

No need to changeThresshold changes done per node in node info

policy.

Page 19: Migration to OML9 Tips-Tricks

20

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 sourcesare defined‗Parameters‘ tab is added.

Page 20: Migration to OML9 Tips-Tricks

21

Embedded Scripting

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

Script Parameters can be referenced within any policy script

Page 21: Migration to OML9 Tips-Tricks

22

Parameterized ThresholdYou 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);

}

Page 22: Migration to OML9 Tips-Tricks

23

Script Parameters

Parameter values can easily be adapted in one place

Page 23: Migration to OML9 Tips-Tricks

24

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);

$Session->Value('CpuUtilWarningThreshold', $CpuUtilWarningThreshold);

Page 24: Migration to OML9 Tips-Tricks

25

Script Parameters

Script embedded

in Policy

#PARAMETER CpuUtilWarningThreshold INT DEFAULT 85 VALUE 85 NODEINFO \"CpuUtilWarningThreshold\" SESSION CAPTION utilization level - Warning threshold\"

my $CpuUtilWarningThreshold;

$CpuUtilWarningThreshold = $OVOSystem->ParameterGetNum(\"CpuUtilWarningThreshold\",85);

$Session->Value('CpuUtilWarningThreshold', $CpuUtilWarningThreshold

Page 25: Migration to OML9 Tips-Tricks

26

Recap: Script Parameters

overwrite

Nodeinfo Policy;XPL config

[eaagt]

CpuUtilWarningThreshold=2

Base Policy

Parameter Tap in Policy

Parameter use in perl threshold evaluation

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

$Rule->Status(TRUE);

use

No need to change

Thresshold changes done per node in node info policy.

Page 26: Migration to OML9 Tips-Tricks

27

Parameterized ThresholdsWithout Using Scripts

Page 27: Migration to OML9 Tips-Tricks

28

Without Script –Default Thresholds in Measurement Threshold Policy

MaxThreshold_1_base policy

For HP and Channel Partner Internal Use.

Page 28: Migration to OML9 Tips-Tricks

29

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]

For HP and Channel Partner Internal Use.

<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

Page 29: Migration to OML9 Tips-Tricks

30

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

Cockpit View

Page 30: Migration to OML9 Tips-Tricks

31

Performance Manager 8.21 Integration

http://yogibear.deu.hp.com/LasVegas2008/OMU_OVPM0005.avi

Page 31: Migration to OML9 Tips-Tricks

32

Performance Manger 8.21 Integration

Updated integration contrib tool with OMU 8.31 patch:

#/opt/OV/contrib/OpC/OVPM/install_OVPM.sh

Page 32: Migration to OML9 Tips-Tricks

33

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

Page 33: Migration to OML9 Tips-Tricks

34

VirtualizedEnvironments

Page 34: Migration to OML9 Tips-Tricks

35

HP Operations Manager

Smart Plug-in for Virtual Infrastructure

Page 35: Migration to OML9 Tips-Tricks

36

OM Agent Cloning

36

Page 36: Migration to OML9 Tips-Tricks

37

Application Template based on VMWares

NEW ApplicationInstance

Clone

HP Operations Manager

Page 37: Migration to OML9 Tips-Tricks

38

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 idovcoreid -create –force

2.# remove certificateovcert -remove `ovcoreid`

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

Page 38: Migration to OML9 Tips-Tricks

39

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/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

Page 39: Migration to OML9 Tips-Tricks

40

Some Tips and Tricks

Page 40: Migration to OML9 Tips-Tricks

41

NEW ApplicationInstance

HP Operations Manager

Public Key HP Operations Manager HP Operations Manager

Public Key Public Key

Application Template based on VMWares

Clone

1. Public Lock For Public key

1. Public Lock For Public key

Page 41: Migration to OML9 Tips-Tricks

42

NEW ApplicationInstance

HP Operations Manager

Public Key HP Operations Manager

HP Operations Manager

Public Key Public Key

Application Template based on VMWares

Clone

1. Public Lock For Public key

2. NEW Lockto secure access

Private Key

Page 42: Migration to OML9 Tips-Tricks

43

White Paper on the way

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.

Page 43: Migration to OML9 Tips-Tricks

44

You Can Also Clone theOML Mgmt Server

Page 44: Migration to OML9 Tips-Tricks

45

Application Template based on VMWares

NEW ApplicationInstance

Clone

HP Operations ManagerHP Operations ManagerTemplate

Clone

Page 45: Migration to OML9 Tips-Tricks

46

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)

Page 46: Migration to OML9 Tips-Tricks

47

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

echousage(){echoecho "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 + ipaddressecho - 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" = "" ]thenusageelsenew_name=$1new_name_long=${new_name}echo new_long_hostame= $new_name_longfi

if [ "$2" = "" ]thenusageelseaddress=$2echo new address = $addressfiif [ "$3" = "" ]thenusageelseold_hostname_long=$3old_hostname=$3echo old_long_hostame= $old_hostname_longfi

if [ "$4" = "" ]thenusageelseold_ip=$4echo 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" ]thenecho continue with nowaitelseecho "If this information is ok press ENTER to continue otherwise press CTRL-C to stop"read yfi

CURR_DIR=`pwd`echoecho 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 $listdoif [ -f ${i} ]thenecho change file: ${i}cp ${i} ${i}.keepeval sed -e 's/${old_hostname}/${new_name}/g' ${i} > ${i}.tmpmv ${i}.tmp ${i}fidone

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

echo starting db/etc/init.d/ovoracle startelseecho 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} fiset +x

/opt/OV/bin/OpC/opcsvcertbackup -force -remove -passwd opc_op -file /tmp/opc.cert ovcoreid -create -force ovcoreid -set ̀ ovcoreid` -force -ovrgserver /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_opovcert -importcert -file /tmp/ovnode.cert -pass opc_op -ovrg serverovconfchg -ns sec.core.auth -set MANAGER_ID `ovcoreid -ovrg server`/opt/OV/bin/OpC/utils/opcnode -chg_idnode_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 licif [ -f /opt/OV/contrib/OpC/AP-Tool.sh ] then# reset instant on licecho reset lic/opt/OV/contrib/OpC/AP-Tool.sh reset

elseif [ -f /net/elisa.deu.hp.com/VM_DATA/AP-Tool.sh ]then# reset instant on licecho 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/selfmonopcmsg a=a o=o msg_t="server switch to ${new_name_long} successful done!"echo

echo $LICecho

Page 47: Migration to OML9 Tips-Tricks

48

Virtual Appliance in OML Testcenter

Page 48: Migration to OML9 Tips-Tricks

49

Virtual Appliance in OML Testcenter

Page 49: Migration to OML9 Tips-Tricks

50

Virtual Appliance in OML Testcenter

Page 50: Migration to OML9 Tips-Tricks

51

Virtual Appliance in OML Testcenter

Page 51: Migration to OML9 Tips-Tricks

52

Virtual Appliance in OML Testcenter

Page 52: Migration to OML9 Tips-Tricks

53

Virtual Appliance in OML Testcenter

Page 53: Migration to OML9 Tips-Tricks

54

Virtual Appliance in OML Testcenter

Page 54: Migration to OML9 Tips-Tricks

55

OM in the Cloud

55

Page 55: Migration to OML9 Tips-Tricks

56

Key questions about systems monitoring and IaaS

Don‘t Fear the Cloud

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 secureand robust must the management solution be to mange through the Internet?

Page 56: Migration to OML9 Tips-Tricks

57

Anywhere and anytime ….

HP Operations Manager Is Cloud ready!

DMZhttpproxy

HP Operations Manager(NOC Console)

HP OPCRC Proxy

Tickets

OM agents

HP OM agents

Internet

HP Performance InsightHP Performance Manager

Performance graphsand reports

OM agents

HP OM Agents

In-house

HP Smart Plug-ins

HP Smart

Plug-ins

OM agents

HP OM agents

HP OPC SiteScope

Your Intranet

Cloudi.e. Amazon EC2

– Single console for managing the in-house IT infrastructure and the systems hosted in public Clouds

– Leverages Investments made into management tools

– Smart plug-ins– Integration

– Secure and unidirectional network communication

– Ensures consistent upstream processes such as incident management and SLM.

Page 57: Migration to OML9 Tips-Tricks

58

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

Page 58: Migration to OML9 Tips-Tricks

59

Migrating to OM 9

Page 59: Migration to OML9 Tips-Tricks

60

Converting OMU 8 Templates to OM 9 Policies

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.

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.

Page 60: Migration to OML9 Tips-Tricks

61

Converting OMU 8 Templates to OM 9 Policies

You can change all policy group assignments modes at once

Page 61: Migration to OML9 Tips-Tricks

62

Format Differences

text file

OM 9

Name = “Test”

InstanceId = “…”

SYNTAX_VERSION 6

MONITOR “Test"

DESCRIPTION “…”

UTF-8

UTF-8/blackbox

hea

der

Page 62: Migration to OML9 Tips-Tricks

63

Tips and Tricks

Page 63: Migration to OML9 Tips-Tricks

64

Exchange of Configurationbetween OMW 8.x and OM 9

Page 64: Migration to OML9 Tips-Tricks

65

Slide 1

OMW/OMU/OML: Configuration Exchange

OMW 8.10 w/ OMU/L 9

NodesW-> U ovowconfigexch. /opccfgupld

U-> W opccfgdwn/ovowconfigexch.

External NodesW-> U ovowconfigexch. /opccfgupld

U-> W opccfgdwn/ovowconfigexch.

Services

ovpmutil XML /

opcservive -add

Service Typesovpmutil/opccfgupld [for single files mof_cfgupld.sh]

Page 65: Migration to OML9 Tips-Tricks

66

Slide 2

OMW/OMU/OML: Configuration Exchange

OMW 8.10 w/ OMU/L 9

Agent Policies

ovpmutil /

opcpolicy

[both directions]

Policy Groups

ovpmutil /

opcpolicy

[both directions]

Instrumentation/

Category

ovpmutil /

opcpolicy

[both directions]

Instruction Text

ovowconfigexch. /

opcpolicy

Page 66: Migration to OML9 Tips-Tricks

67

Exchange of configuration

Policies

PoliciesPolicies

ovpmutil opcpolicy

opccfgdwnimport-policies

OMU/L 9 OMW

Page 67: Migration to OML9 Tips-Tricks

68

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.

Tips and Tricks with OMW Policies to OM 9?

Page 68: Migration to OML9 Tips-Tricks

69

Exchange of configuration

Nodes

Nodes Nodesovowconfig-exchange

opccfgdwn

C:> ovowconfigexchange -ent NODES -dnl nodes -dest_codeset utf8

opccfgupld <path>/nodes

OMW OMU/L 9

All nodes are put into nodebank\holding area

Page 69: Migration to OML9 Tips-Tricks

70

Exchange of configuration

Services

Services Servicesx

ovpmutilCFG XML

[iconv] /opccfgupld

OMU/LOMW

Page 70: Migration to OML9 Tips-Tricks

71

Import of Service Model fromOMW 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>

Page 71: Migration to OML9 Tips-Tricks

72

Exchange of configuration

Service Types, User Roles, Tools

Service TypesUser Roles

Tools

Service TypesUser Roles

Toolsxx

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

Page 72: Migration to OML9 Tips-Tricks

73

Import of Service TypeModel fromOMW 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.

Page 73: Migration to OML9 Tips-Tricks

74

Tips and Tricks withConfigfile Policy Type

747/8/2010

Page 74: Migration to OML9 Tips-Tricks

75

E.G. osspi_global_fsmon.cfg as configfile

Page 75: Migration to OML9 Tips-Tricks

76

E.G. linux.alarmdef as configfile

SyntaxVersion=1

Application=Performance_agent

SubGroup=Alarmdef_for_Linux

Filename=linux.alarmdef

CallFunctionClassID=

Data:

#$Installcommand=$OvPerlADir$/perl

$OvInstrumentationDir$/PostDeployActions.pl alarmdef

linux.alarmdef

#$Commandtype=3

# @(#)alarmdef 05.00.000 01JUN2009 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

Page 76: Migration to OML9 Tips-Tricks

77

OM 9 LICENSING

Page 77: Migration to OML9 Tips-Tricks

78

License Migration

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

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

Page 78: Migration to OML9 Tips-Tricks

79

License Exchange

Reporter (Windows)

HP Ops MgrPerformance Manager

Supported platforms – Linux, Windows, HP-UX 11i, Solaris

New bundle - HP Operations Manager, Performance Manager, Reporter

Page 79: Migration to OML9 Tips-Tricks

80

Summary

Page 80: Migration to OML9 Tips-Tricks

81

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‖

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

Page 81: Migration to OML9 Tips-Tricks

82

Q&A

Page 82: Migration to OML9 Tips-Tricks

83 ©2010 Hewlett-Packard Development Company, L.P.

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

Page 83: Migration to OML9 Tips-Tricks

84