omu / linux tips and tricks - vivit-germany · omu / linux tips and tricks , introduction of ......

1 ©2010 HP Confidential 1

OMU / Linux Tips and Tricks , introduction of OMX 9.10, OM Agent 11 and Performance Manager 9

– Hans-Peter Schmollinger

HP Operations Manager Unix Architect

Bad Honnef 14.-15. September 2010

2

Business Service Management Operations Center

– Subtitle goes here

3

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.

4

AGENDA

OMU 9.10 Overview / What‟s new

OM Agent 11

Cloud and Virtualized environments

PM 9 demo

More Tips & Tricks


OMU 9 OVERVIEW

6

Investment protection with OM family of products

Stability with HP Operations Manager

Interoperability and Configuration Exchange between 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

19 93

19 94

19 95

19 96

19 97

19 98

19 99

20 00

20 01

20 02

20 03

20 04

20 05

20 06

20 07

20 08

Operations Manager on Unix

Operations Manager on Windows

OpC 1.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.0

OMU

8.27 OMU

8.31

OMU

8.20

VPW

6.0 VPW

6.10

OMW

8.0

OMW

8.10

OMW

7.50 OVOW

7.20

OVOW

7.10

OVOW

7.0

OVOW

7.21 OVOW

00189

OVOW

00210

OVOW

00228

OVOW

00229

20 09

OML

9.01

Operations Manager on Linux

20 10 OMU

9.02 Solaris

OMU

9.00 HP-UX

OMU

8.35

OMW

8.16

OMU

9.10 Linux, HPUX, Solaris

7

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

©2009 HP Confidential 8 ©2009 HP Confidential 8

OMU 9.x Features

9

WEB-BASED ADMINISTRATION UI

New web-based Admin UI replaces the MOTIF UI

Supports multiple administrators with granular user roles

Online sync between admin and operator GUI, e.g. nodes are added in realtime with no need for “Reload configuration”

10

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)

11

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)

12

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.X

Multiple OM‟s

(Win, OMX, OMi)

Agents Agents

OM SiteScope NNM 3rd

party

Agents Agents alerts

Discovery

OM SPIs

HP BSM Foundation UCMDB

Event

Health TBEC

Events and Topology

External Notification

Additional patch on top of OMX 9.10 needed to

enable the Runt-Time syn. Available ca. Nov. 2010

(We are looking for Beta/EPR customers)

13

Operations Manager

OM/PA Agents

Operations Orchestration

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

1

2 3

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

Central event console, actions, graphs 2

Users can invoke OO flows for troubleshooting issues

3

OO delegates command execution to OM 5

Workflows update events 4

OO command execution via the secure, http OM communication channel

6

Remote command via telnet, ssh, etc 7

Remote OO managed

node

OM Console

5

7 6

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!


Performance Results

©2009 HP Confidential 15

Core system tests 1

Message Throughput depending on number of Nodes (no GUI / 1 CMA! / opcle)

Criteria: event flow rate into DB

# of nodes OMW low cost

HP-UX

Linux 64 low cost

Linux 64 High (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


OMU/L 9.1 server enhancements

17 © Copyright 2010 Hewlett-Packard Development Company, L.P - For HP Internal and HP Partners only. 17 © 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

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

New CLI options for: opcragt, opcpolicy, opcsrvconfig, opctempl 1/5


• -> 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.




• Updates policy assignments related to policy groups, nodes or node groups (several filter methods can be applied).

opcpolicy

-upd_pol_assigns

• Copies policy assignments from one node, node group, or policy group to another.

opcpolicy

-copy_pol_assigns

• Duplicates a policy group to a different location. opcpolicy

-copy_group

• Duplicate a policy to different name or/and version. opcpolicy

-copy_pol




•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 between active 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


Detailed opcpolicy examples for each option can be found in the man page.

More details on policy versioning strategies and usage can be found in the concepts guide in a separate chapter.






• Lists the details of the audit configuration. opcsrvconfig -audit -list_events

• Difference to OMU/L 9.0: Commands opctempl –add, and opctempl –modify are now also revitalized. They work like for OMU 8.x. Can be used to upload single OMU 8.x templates which get converted into OMU/L 9.x policies. The version numbers for such policies is always 1.0.

opctempl –add

opctempl = opcpolicy


New server variables - overview


OPC_ALLOW_DUPLICATE_IP (see separate slide)

OPC_CSA_ALLOW_IP_MISMATCH (see separate slide)

OPC_CFGDWN_OMIT_VIRTUAL_GROUP_DOWNLOAD

OPC_MSGKEY_MODIFY_TEXT


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 addresses need 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_DOC


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


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.




• calls ovolicense 3 times to collect license and component feature information

• ovolicense –m > /var/opt/OV/tmp/el_mappings.txt

• ovolicense –l > /var/opt/OV/tmp/el_pwd_list.txt

• ovolicense –r –p HPOM –xml –out /var/opt/OV/tmp/el_xml_report.xml

• calls OMLicenseReporter.jar after information has been collected

omlicreporter

• license report formatter

• creates the HTML license reports

• if not differently specified, the HTML report files will be stored in:

• /opt/OV/www/htdocs/ito/OMLicenseReport.html http://omlinux9.deu.hp.com:8081/ITO/OMFeatureLicenseReport.html

• /opt/OV/www/htdocs/ito/OMFeatureLicenseReport.html

• /opt/OV/www/htdocs/ito/OMLicensePasswordReport.html

• /opt/OV/www/htdocs/ito/OMNodeLicenseReport.html

OMLicenseReporter

Entry Page




– OM License Report

• entry page of the OM License Report

• available with upcoming OMU Core server 9.x patch (not yet available):

PHSS_41410, ITOSOL_00742, OML_00030




– 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‟


The License Password Report

The License Password Report is the report of the license passwords (license keys). Capacity (LTUs)

in this one password

Summarized feature capacities (LTUs) of all of this passwords

The annotation of this one password






– Node License Report

• displays nodes and its licenses requirements

• available with upcoming OMU Core server 9.x patch (not yet available):

PHSS_41410, ITOSOL_00742, OML_00030

Number of required licenses for the feature, as reported from the Agent

OM Server name that hosts the licenses for this feature for this node


Recap: ovolicense 1/2


Get the license status

„ovolicense –s –p HPOM‟ shows the license status of each feature

The same is shown in the 'OM Feature License Report' in a better structure.


Recap: ovolicense 2/2


List installed license passwords

„ovolicense –list –a HPOM‟ lists the content of all OM license passwords with its explicit feature ID and name.

Useful, when the presented information is needed in addition to the 'OM License Password Report'

License Password 1:

Description : HP Operations Manager Server

Annotation : IPP09A84I37H38RI TA444AA HP OpsMgr Mgmt Server SW LTU

IP-Address : 192.168.178.120

Expiration Date : --

Feature ID : 6505

Number of Licenses : 1

License Capacity : 1

License Password 2:

Description : HP Operations Manager Desktop Agent

Annotation : OMU Test Licenses 2008 : HP OVO Desktop Agent

IP-Address : 192.168.178.120

Expiration Date : --

Feature ID : 530

Number of Licenses : 10

License Capacity : 10


MIB to policy (mib2policy) contribution tool 1/2


CLI 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


MIB to Policy (MIB2Policy) contribution tool 2/2


Example: mib2policy –p virtual virtual.mib

• Results in virtual_data policy file and virtual_header.xml header file.

• Assume the policy files are located in /tmp/my_dir, it can be uploaded to the DB like this: # /opt/OV/bin/OpC/utils/opcpolicy –upload dir=/tmp/my_dir

mib2policy –c <config_file> … Within a config file, you can specify the values for the fields in the policy and in the conditions

If not set, defaults apply (see mib2policy –man for details)

The configuration lines relate to the policy defaults regarding the

• policy fields

• condition fields

• header fields


Cloning HPOM Management Server image


Cloud readiness: Server cloning

Unsupported tool to clone a mgmt server: /opt/OV/contrib/OpC/om_server_switch.sh

Cloned image needs some modifications. e.g. new hostname, new IP address etc. which are done through this script.

Usage: /opt/OV/contrib/OpC/om_server_switch.sh \ <new_long_hostame> <new_IP_Address> <old_long_hostame> \ <old_IP_Address> [ nowait ]


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 with

IP 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.


43

SOME TIPS AND TRICKS


VIRTUALIZED ENVIRONMENTS

45

OM in the private Cloud

45

46

YOU CAN CLONE THE OML MGMT SERVER

47

Application Template based on VMWares

NEW Application Instance

Clone

HP Operations Manager HP Operations Manager Template

Clone

48

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)

49

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 òvcoreid` 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 ò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` 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

50

OM Agent cloning

50

51

Application Template based on VMWares

NEW Application Instance

Clone

HP Operations Manager

52

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

53

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 0

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

54

OM in the public Cloud

54

55

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?

Don‟t fear the Cloud

55

56

Anywhere and anytime ….

HP Operations Manager is Cloud ready!

DMZ http proxy

HP Operations Manager (NOC Console)

HP OPC RC Proxy

Tickets

OM agents

HP OM agents

Internet

HP Performance Insight HP Performance Manager

Performance graphs and 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

Cloud i.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.

56

57

Unified monitoring of physical, virtual & 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 & Cloud

systems

• Single event console • Unified processes &

integrations

57

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.00 What’s New

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

Unified Agent

• Agent Install Media/ESD

• Change from the current OM release vehicle

• Releases independent of OM management server

• Caters to the server attach and ops attach user base

Unified Release Vehicle


− Present releases of all products/components prior to the jointure:

• OA‟s latest version is 8.53 / 8.6X

• PA‟s latest version is 4.72 / 5.X

• LCore Stack version is 6.x

• Embedded Collector (Coda) latest version is 10.50.XXX

− Equalize versioning of these components

Uplifted to the next major version 11.00

Reason for 11.00

HP Operations Agent 11.00 What’s new in the OA 11.00 installer

• Lightweight script oainstall replaces opc_inst to install, uninstall and check the agent version on server attach and operations attach environments

• Back up of earlier agent versions on management server

• Enhanced logging to identify cause of install failures

• De-installation of OA 11.00 will restore back previously installed highest version of Operations and Performance agents

• Pre-requisite check in agent installer

Install Improvements

HP Operations Agent 11.00 How Are We Solving These Problems

• Consolidated Install Scripts and Logs

• Single record of Install log - oainstall.log

• Stream lined configuration with –defer_configure install option

Ease of Use

• Platform alignment for Operations and Performance components

• Infrastructure SPIs instrumented to use One Collector Technology

Consistency


• Ability to work with IPv6

• Support for IPv6/IPv4 dual stack nodes

• Remote monitoring of IPv6 nodes using SNMP Get/ WMI

• Operations monitor agent state persistence

• Real time system performance monitoring with RTM sub-agent

• CPU metrics logging based on active cores for hyper-threaded processors

New Features

HP Performance Manager 9.0 What’s new?

HP Performance Manager 9.0 What’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.0 What’s New in EPR2

Ability to switch between Real-Time and Near-Real-Time data

Ability 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

69

Diagnostic View

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

71

Real-Time Datasource

Month Year [or Rev. #]


• 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


OML/U PM integration

75

DEMO

Demo PM 9 / OM Agent 11 Realtime Graph

Contrib convert OM Nodes and Node Groups into PM

76 76 9/9/2010

Section title here

Tips and Tricks with configfile policy

type

77

E.G. osspi_global_fsmon.cfg as configfile

78

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

79

Q&A

omu / linux tips and tricks - vivit-germany · omu / linux tips and tricks , introduction of ......

Documents