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

Operations Manager for Windows (OMW)–Tips and Tricks

Alfred HermannTechnical Marketing

HP Software

2

Agenda

– OMW 8.16 – what‟s new?

– Installation and upgrade best practices

– Integrations – recently added

• Discovery Mapping Automation 8.10/8.20

• SiteScope Adapter 2.0

• Network Node Manager i 8.12

• Service Manager via scauto 1.4

• OM„s role with Operations Manager i

– Perl library for OM incident WS

– Performance testing with OMW 8.16 – what does it mean for you?

– Licensing changes

– Miscellaneous

3

What is Operations Manager 8.16 for Windows

- Release Objectives

- What‟s New

– Subtitle goes here

4

Release Objectives

HP Operations Manager 8.16 for Windows

Ease the installation, upgrade and deployment effort required to come to a successful implementation

Incorporate customer feedback and improve quality and stability of Operations Manager for Windows version 8.10

Include the additional capabilities offered after version 8.10 release, e.g. in the area of interoperability, co-existence and high availability

5

What‟s New

HP Operations Manager 8.16 for Windows

• Reduced amount of steps required for successful implementation

• Improved quality, e.g. incorporated fixes for reported critical & serious customer issues

• Installation/Upgrade patch OMW_00034 (supers. 9 and 19)

• Server/Console Patch OMW_00048 + OMW_00050 (incl. 20 + 29)

• Operations Agent 8.60

• Accessories patches OMW_00032, OMW_00039

• Server pooling support

• SiteScope Adapter version 2.0

• Agent based integration with HP NNMi version 8.12

• DMA version 8.20 support

Improved installation, deployment and implementation experience

Incorporation of the latest patch revisions

Capabilities beyond core version 8.10 release*

* Available for version 8.10 implementations via patches or post-8.10 certifications

6

How to get to OMW 8.16

- Upgrade- Upgrade Guide- Best Practices- Tuning WMI- SUTK – SPI Upgrade Tool Kit

7

Upgrade to Operations Manager 8.16

Multiple alternatives to upgrade from OMW 8.10 to OMW 8.16

Upgrade per 8.16 DVD:

• Preferred for different hardware or hostname

• Includes data download

1

Per patches 48+50, 32, 39 and 8.60 agent(s)

• No data download/upload

• Recommended on same system/hostname

2

• Direct upgrade from any OMW 7.5+ version to OMW 8.16

• No separation between in-place and side-by-side

• “Upgrade” supported from OMW 8.16 to 8.16 (eg. for different hardware, non-cluster to cluster, hostname change, …)

Upgrade Scenarios

8

Upgrade to Operations Manager 8.16

OVOW 7.52005.1 SPI-CD

2006.1 SPI-CD

2007.1 SPI-DVD

2007.2 SPI-DVD

2008.1 SPI-DVD

OMW 8.02007.1 SPI-DVD

Install OMW 8.16

OMW 8.16

2007.2 foundations SPIs

2005.1 SPI-CD

2006.1 SPI-CD

2007.1 SPI-DVD

2007.2 SPI-DVD

2008.1 SPI-DVD

2008.1 SPI DVD

OMW 8.16

2008.1 SPI-DVD

OMW 8.10/8.162007.2 SPI-DVD

2008.1 SPI-DVD

Win 2000Win 2003 / Cluster

Win 2003 / ClusterWin 2008 / Cluster

Win 2003 / ClusterWin 2008 / Cluster

Win 2003 / ClusterWin 2008 / Cluster

Win 2003 / ClusterWin 2008 / Cluster

FoundationInstallation

IntermediateVersion

ActivatesNew Features

TargetVersion

SourceVersion

9

Upgrade Guide

–Get the latest upgrade guide from

http://support.openview.hp.com/selfs

olve/document/KM549936

–Unzip the upgrade guide & select

conditions

–The procedures in the upgrade guide

are dynamic options which change

according to your selections.

–This tool creates an upgrade

procedure that is tailored to your

individual situation.

–When all options are correctly set for

your upgrade, print the instructions

and prepare your upgrade plan

10

Upgrade Practice–DOs and DON‟Ts

DON‘T... DO...

• Upgrade a DC OMW 8 will never install/run, 7.50 did

• Proceed before old version is cleanly un-installed (same hardware only)

• For upgrade with different hostname: Only uninstall source server once agents are re-directed to target server, and target server has distributed new certificates to all agents (8.0, 8.10, 8.16 only)

• Make sure all SPIs/older SPI versions are uninstalled

• If needed, OVOW 7.5 or OMW 8.0/8.10/8.16 removal tool (from support) may provide additional help, multiple cycles may be required

• Check log files for errors

• Consult OMW 8.10 Troubleshooting Guide in case of failures.

• From 7.5: Consider upgrading agents to HTTPS

11

Deployment Checklist and Tuning WMI

• Get the latest “OMW 8.16 Deployment Checklist”

• Set WMI parameters Win32_WMISetting

– “HighThresholdOnEvents” to 80000000 (~80MB)

– “LowThresholdOnEvents” to 60000000 (~60MB)

• Increase the WMI query size limit to 32768 via registry key HKLM\Software\Microsoft\WBEM\CIMOM\QueryLimit

Windows management server and consoles heavily rely on the WMI subsystem

12

1.0

1.1

1.2

2.0

SPI version 09.00;

Policy version 1.0

SPI version 10.00;

Policy version 2.0

Customized policy version 1.1

SPI Policy

Final Policy version after the upgrade with the customization preserved 2.1

BASE

FACTORY

CUSTOMER

MERGED

2.1

SUTK is a tool that will help the customers to upgrade from one version of a Smart Plug-in (SPI) to another without losing their policy customizations.

SUTK reduces time and resources required for

SPI upgrade

How the SPI Upgrade Tool Kit Analyzes PoliciesPolicy upgrade use case

13

PatchesPlatformsNew SPI DVD

– Subtitle goes here

14

PatchesEquivalent to Version Scope

Super-sedes What’s New?

OMW_00062Server / Console 60 License Reporting for

instance licenses

OMW_00060 Server / Console 58 Global filters for web GUI

OMW_00058 8.18 Server / Console 51, 50 mib2policy

OMW_00057Server / Accessories

Instruction text forOMi 9, move database

OMW_000508.16 Server / Console

20, 29, 48

Stabilize

OMW_00044/43/40 8.60 8.60 Agent 42 for

Windows

44=Win, 43=AIX, 40=Solaris,

OMW_00039 8.16 SiS Accessories SiS Adapter 2.0, SAM

OMW_00034 8.16 Install / Upgrade 9, 19 Stabilize

OMW_00032 8.16 DMA Accessories Accessories

http://support.openview.hp.com/selfsolve/patches/

15

New Supported Platforms

Management Server

Agents

Console

MMC: Windows 7, 32-bit OSMMC: Windows Server 2008, 32-bit OSWeb: IE 8

MS Windows Server 2008, 32-bit OS

MS Windows Server 2008 / SP1 (32+64 bit OS)MS Windows Server 2008 R2 (hotfix req„d, limitat.MS Windows Server 2008 CoreMS Windows 7 (hotfix required, limitations)

MS SQL Server 2008 (patch OMW_00029)

Database

vSphere install – see separate WP

16

Agent Platforms Recently Added

– Cluster

• HP-UX 11.23 and 11.31, PA and

IA64, on MC/SG 11.19

• Novell SLES 10, on MC/SG 11.19

• Redhat RHEL 5.3, on Redhat

cluster

• Redhat RHEL 5, on MC/SG 11.19

• IBM AIX 5.3 and 6.1, on HACMP

5.5

• Sun Solaris 10, Sun Cluster 3.2

on zones

• Microsoft Windows 2003, on

VCS 5.0

– New Hypervisor Support

• IBM AIX 6.1, System WPAR

• Microsoft Windows 2008, HyperV

• Novell SLES 11 DomU and Dom0, Xen

• Redhat RHEL 5.3, Xen

• VMWare ESX 4

– New Operating System

• IBM AIX 6.1, P5 and P6

• Novell SLES 10 SP3

• Redhat RHEL 5.4

• Redhat Cent OS 5.4

• Redhat SELinux 5 (5.2)

Cluster Certifications Hypervisor Support

New Operating Systems

17

SPI DVD 2009 “Jumbo” – What‟s New?•Simultaneous release of SPI functionality for OMU, OMW, OML* and OMi*

•Consistency: Single version of the SPI across all management servers

•OMW 8.1x

•OMU 9.0x (both HP-UX/IA and Solaris)

•OML 9.0 (select SPIs)

•Support for HP Operations Agent 8.53 and 8.60. [DCE agent 7.35 for OMW 8.1* only.]

OM Components

•SPI for JBoss Web Application Server for OML, OMU and OMW

•Support for Microsoft Active Directory for OMU

•HP Operations Smart Plug-in for BlackBerry® Enterprise Server – 3.10

•Office Communications Server support in Microsoft Enterprise Servers SPI (SPI for OMW only)

Applications

•SUTK (SPI Upgrade Tool Kit)

•helps analyze, manage, preserve SPI policy customizations during SPI upgrades

•Version: SUTK 2.00

•Simplicity and standardization: List of Golden Metrics for all the major SPIs, revise instruction text in SPI policies to make them consistent

Tools

*Limited number of SPI Support OML and OMi

18

Summary of SPI DVD 2009 Release

New Application VersionsSupport for other application monitoring

enhancements and features

• Microsoft SQL Server 2008

• Informix 11.50

• Sybase 15 on Windows

• Weblogic 10g3/11gR1

• Microsoft Office Communication Server 2007

• BEA Tuxedo 10

• ...

• AIX 6.1 Support

• Windows 2003 IA Native Support

• Windows 2008 server core

• Windows 2008 server R2

• Windows 2008 server SP2

• SPI for BlackBerry Enterprise (BES) 3.10: Support for Windows 2003 and 2008, can connect to IBM Lotus Domino messaging servers

• JBoss AS SPI 7.00: JBoss Application Server

• AD SPI 7.00: Support for Windows Server 2003, 2008 Core, 2008 R2

• SPI for Oracle 12.00: Monitors Flash Recovery Area (FRA), Materialized views, and Streams

• SPI for MS SQL Server12.00: New replication policies based on WMI performance counters and enhanced log file monitoring

• SPI for MS Exchange Server 13.00: MS Exchange Server 2007 in SAN environment

• SPI for SAP 12.00: SAP Net weaver 7.1 Java monitoring, Net weaver multi instance

• SPI for IBM WebSphere AS 7.00: WebSphere AS 7 – dist. netw. Deployer

• SPI for Oracle Application Server 7.00: Golden metrics

• SPI for Oracle/BEA WebLogic AS 7.00: WebLogic 10.x

• SPI for Remedy ARS 4.00: Remedy ARS 7.5

New Platform Versions

19

Integrations

- DMA 8.10/8.20

- SiS Adapter 2.0- NNMi 8.12- SM via scauto 1.4- OMi- OO

20

SiS 9.x, 10.xSAM 9.5, 10

Operations Manager for WindowsThe Core Part of an Integrated Solution

SM 7.11SM 7.00

NNMi 9.0NNMi 8.03, 8.1xNNM 7.5x

OMU 8.x, 9.xOML 8.x, 9.x

BSM/BAC 9.0,BAC 7.x, 8.0

DMA 8.10DMA 8.20

Service Manager

NNMi

SiteScopeSAM Admin Operations Manager

for UNIX

DMA

Biz. Avail-ability Center

21

Server Accessories Patch OMW_00032 (included in OMW 8.16)

Integration with DMA 8.10 / 8.20

UCMDB

OM DMA

CI data and dependenciesOperations Manager

Discovery and CI maintenance

Discovery and

Dependency Mapping

Federation

Other HP Software

JRE 1.6: Upgrades JRE 1.5 which will be obsoleted soon

TomcatB 6: Tomcat is dependent on JRE and backward compatibility of JRE 1.6 to Tomcat 5 is not tested

Incident Web Service 8.30: Mandatory for OM enablement for OMi

CI-Web Service 8.30: Mandatory for DMA 8.20 and OM enablement for OMi

22

SiteScope Adapter 2.0

• OM agent is de-

ployed to SiteScope server

• Agent discovers SiteScope

configuration & monitor groups,

publishes discovered information

to service maps

• Synchronization of SiteScope

monitor state and OM service

map status can be done via OM

messages

• In-context launch of SiteScope

dashboard from OM console

• Multiple SiS servers supported

(install agent on each server)

New with Adapter 2.0:

Server Accessories Patch OMW_00039(included in OMW 8.16)

Predefined OM policies for each SiteScope monitor class

More structured information available in SiteScope alerts

SiteScope messages can be mapped to target nodes rather than the SiteScope server

More details in OM message text

Relevant for OMi:Policies determine monitored CI

23

Server B

NNMi

Causal

Engine

Northbound Interface

3rd PartySNMP Traps

Trap

Receiver

Events

OMAgent

Mgmt Events

SNMP Traps

Incidents

Server A

OM

Server

policy.dat

Network

OM Agent Implementation

NNMi 8.12

24

Web Service - Based Agent - Based

≥ NNMi 8.03/8.10 ≥ NNMi 8.12

Industry standard integration Light-weight solution with increased event throughput

Filters in NNMi that enable incidents to be forwarded to HPOMonly when they meet certain criteria

Filtering and enrichment capabilities using OM policies

Bi-directional synchronization of incidents between NNMi and HPOM

Uni-directional synchronization from NNMi„s point of view

No agent required on NNMi server Agent required. Similar integration to legacy NNM-OM

What is the preferred implementation?

Because of higher event throughput, the agent based implementation is preferred.

NNMi – OMW Integration Essentials

25

OM Message to SM Incident Correlation

SCAuto

scauto for OM

Operations Manager

Two-way: SCAuto for OM allows you to automate the process of creating, updating, and closing incident tickets. It has the capability to annotate, own, and acknowledge OM messages from modifications done on SM incident tickets

Service Manager

IncidentTickets

Assets

SLAs

Messages

New with scauto version 1.4: New method to set CMA. By default, OM message CMAs for the SM Incident ID and SM Incident Status are set.

26

OM for Windows is “OMi Ready”

• OM implements agent-based management. Deployment / configuration of OM agents from the OM server.

• OM = great underlying tool launching infrastructure for distributed heterogeneous environment.

• Built-in event correlation capabilities including base-lining per advanced threshold monitoring.

• Patch OMW_00057 includes support for instruction text for next OMi.

• OM as first-level event consolidator.

• Distributed data collection and storage of performance metrics for scalable performance graphing and reporting.

• OM service views and auto-discovery complement UCMDB discovery sources for OMi

• OMi enabled SPIs include CI resolution hints and ETIs.

• Events pre-correlated via OMW, then synchronized with OMi

OMOMSiteScopeOMOMNNMi

OMOM3rd PartyDomain Mgrs

BSM Platform

OMi(TBEC, Health Perspective)

OMOMOM agents

OMOMOM/PMOMOMBSM EUM

27

1. OO takes ownership of the

problem for diagnosis,

troubleshooting and resolution

2. OO documents the resolution of a problem as OM annotation

3. Link to OO flow report available in

OM annotation

4. Depending on diagnostic checks, OO can change the importance of the OM event

5. Once the OO steps have solved the problem, the OM message is automatically acknowledged

HP Operations OrchestrationTight integration with HP Operations Manager

28

Perl Library for OM Incident WS

– Subtitle goes here

29

OV TomcatBIIS

WSDL

WMI

WSDL

JNI

.NET Java

Consistent Incident Web Servicefor OM for Unix and Windows

Web Services enables clients to access OM messages using

standard interfaces instead of product-specific interfaces

OM Messages are exposed as ITIL Incidents

Clients can be implemented using tools that support WS-Mgmt, for example Wiseman

Operations Managerfor Windows

Operations Managerfor UNIX

Web Service ClientIncident WS

web applicationIncident WS

web application

Incident Web Service API: Access OM Messages via Industry Standards

30

Web Service Dataflow

Perl script

XML

Request

XML

Response

Web Service

OperationsManagerLibrary

- Provide methods for data input

- Generate Request XML data

- Provide error messages

- Send / Receive XML data using “SOAP::Lite” Perl module

- Distribute received XML data as easy accessible objects

31

Example: Create an Incident

use WSOM::Lib;

my $newIncident = WSOM::Lib->create->to('http://example.org:8081/opr-

webservice/Incident.svc‘)->auth('user', 'pass')->bodyTitle('Demo Incident')->bodyDnsEmittingNode(‘demo.local‘)->bodySeverity('Normal‘)->bodyDescription('This is a brand new incident‘)->execute;

if (!$newIncident->fault){

print "Incident was created: ".$newIncident->incidentI

32

Perl Library and Documentation

Easy access to the Incident Web Service, no XML needs to be written manually, no Web Services know-how required

Library works with OM for UNIX and OM for Windows

Platform independent: We tested Microsoft Windows, Linux, HP UX, Solaris. Need Perl >= 5.6.0 (March 2000)

Contrib tool, part of OMU 9.1, patch [TBD] of OMW, not supported

Provides access to complete set (24) of web service operations,eg. create incidents, fetch incidents, mark incidents as closed.

Benefits

Server Platforms

Client Platforms

Availability

33

OMW 8.16

Performance Testing

– Subtitle goes here

34

OMW 8.16 Performance Testing

Similar measurements between all platforms (Linux, Unix, Windows)

Quad-core processor for management server system

Windows 2008 R1

HTTPS vs. DCE for agent-manager and manager-to-manager communication

Major differences to testing performed with OVO for Windows version 7.50:

Platform

Hardware

OS

Communi-cations

35

Hardware Recommendations

– Quad-core processor for management server is able to process

approximately twice as much messages into the database compared to

a dual-core processor at the same clock rate.

– Increasing management server„s memory beyond 4 GB doesn„t offer

performance advantages.

– Remote database recommended on 64-bit system with 8GB memory,

a dual-core processor, fast disks connected via SAN and fast network

connection to the OMW management server.

– Virtual machines:

• Add up the requirements of the server, remote db and the host. Add 10% CPU clock rate

to compensate for host CPU usage.

• Management server performance will be reduced because of the lower network and disk

performance

Quad Core

Remote database 8 GB

4 GB

Virtual Machines

management server

36

Message Throughput – MMC Consoles

# MMC consoles

MinimumThroughput

MaximumThroughput

1 150 350

5 38 210

12 25 210

25 10 35

– End-to-end Performance, agent through console

– Message generator with 120,000 messages

200

60

40

15

Other factors that influence throughput: #CMAs, #MSI.

Duplicate message suppression recommended!

Typical Rate

37

Message Throughput – Web Console

# Web consoles

MinimumThroughput

MaximumThroughput

5 70 380

50 65 320

300 50 300

End-to-end performance, agent -> web console

1,200,000 messages

Web consoles do not have a strong impact on the throughput.

Up to 200 web consoles can be connected without problems.

Console response time is less than 10 seconds with 200 web consoles even when all operators request new information every 30 seconds.

38

How Many Systems Can be Managed by a Single OM for Windows Management Server?

Safe answer: It depends

Typical answer: Multiple 1,000s

Communication architecture / implementation: No hard-coded

limits

Real life deployments: 3 OM for Windows management servers

managing 7,000 systems [large US financial institution]

Performance Testing with OMW 8.16: Maximum number of

HTTPS agents that can be connected concurrently without

connection problems: 6,500 6,500

39

Licensing Changes

- Tier-less Agent Licenses- OMW Basic Suite

– Subtitle goes here

40

Operations Center: Licensing Changes

• Simplify our Pricing Model (easier to understand and validate

compliance)

• New structure independent of hardware platform and virtualization

changes

• Tier-less: One “Operations OS instance Advanced LTU” is required for

each instance of an operating system on each server that will be

monitored (physical and virtual).

• No separate operations agent only license on CPL, separate performance agent only license will exist on CPL (for PA only customers).

• 15 SiteScope system metrics & administration included with NEW LTU purchases

• Similar model for SPI aplication instance licenses.

• Existing OM customers will keep and continue to run their installations

using their existing, tier-based entitlements/keys

• New capacity must be purchased using the new instance-based product

structure.

• OM installations can be run using both types of keys (tiered-based keys

and instance-based keys) simultaneously.

Program Goals

What Is Changing

Moving Forward

41

– Aimed at small businesses or regional offices.

– A bundle including an OMW server and 20 “tierless” agents.

– SPIs included: • MS Active Directory x 1 • MS Exchange x 1 • MS SQL Server x 1• Oracle x 1

– Upgrade available to 30 agents – this was the MAXIMUM number of devices that can be managed (even if you proxy manage!).

– Full LTUs for Reporter and PM included (same as „full‟ OMW 8.x)

OMW Limited Edition OMW Basic Suite(Replacement Product)

• Aimed at small businesses or regional offices.

• A bundle including an OMW server and 20 “HP Operations OS Inst Adv SW LTU”.

• “HP Operations SPI for APPL In Adv LTUs” included:

− MS Active Directory x 1

− MS Exchange x 1

− MS SQL Server x 1

− Oracle x 1

− Virtualized Infrastructure x 1

• Each instance based LTU INCLUDES 15 SiS points – the same usage restrictions apply as for standalone instance based LTUs

• Fully extensible – can add as many additional agents as required

• Full LTUs for Reporter and PM included (same as „full‟ OMW 8.x)

42

Misc...

– Subtitle goes here

43

–Get the latest list of documents from

http://support.openview.hp.com/selfs

olve/manuals

–New deployment checklist

–New documents, eg. Installing the

Agent Software on vSphere

Management Assistant Nodes

–Updated white papers, eg.

• High Availability through Server Pooling

• High Availability utilizing Microsoft SQL Server

Log Shipping

• Target Connector Check Utility

Tons of 8.16 Material on the Manuals Website

44

–OM internal messages are directly

passed to the management server

–No processing takes place on the

agent

–The default severity for internal

messages may not be appropriate

eg. if all messages with severity

„critical“ are forwarded to a pager

or service desk

–As long as the problem is not

solved there may be many internal

messages

Recap: OM Internal MessagesTrigger available since VPW 6.0 in 2000!

opcinfo variable:OPC_INT_MSG_FLT FALSE|TRUE

Fine-tune and control the behavior of OM self management

FALSE: (=Default)Internal messages directly forwarded to management server.

TRUE:

MessageInterceptor

MessageAgent

Policy for OM Internal

Messages

45

Recap: How to Keep Multiple Servers in Sync?

– Manual synchronization of nodes / node groups is adequate for a

standby server. Perform daily or as part of change management:• ovpmutil can be used to manually sync nodes (and node groups).

• During upload disable auto-deploy „/noautodeploy“.

• Alternative: Database replication / logfile shipping.

– Where servers do message forwarding / synchronization a more

automated approach is desirable:• Automate sequences of ovpmutil down and upload. Overhead with short sync interval.

• ovownodeutil.vbs provides some capabilitiy to script addition of new nodes and node

groups in response to a WMI event. Prevent loops: Make sure synchronized node is not

added back to originating server.

– Synchronizing nodes continues to be a hot topic to be

addressed with a future release.

You must synchronize nodes between OMW servers otherwise messages will be „rejected“

46

Q&A

47 ©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

48