OMi MGMT Infrastructure1.12 UserGuide

HP OMi Management Pack for
Infrastructure
Software Version: 1.12
HP Operations Manager i for Linux and Windows® operating systems
User Guide
Document Release Date: June 2015

Software Release Date: May 2015
User Guide
Legal Notices
Warranty
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Restricted Rights Legend

Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software,
Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
Copyright Notice
© Copyright 2013-2015 Hewlett-Packard Development Company, L.P.
Trademark Notices
Adobe™ is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
UNIX® is a registered trademark of The Open Group.
This product includes an interface of the 'zlib' general purpose compression library, which is Copyright © 1995-2002 Jean-loup Gailly and Mark Adler.
Documentation Updates
The title page of this document contains the following identifying information:
l Software Version number, which indicates the software version.
l Document Release Date, which changes each time the document is updated.
l Software Release Date, which indicates the release date of this version of the software.
To check for recent updates or to verify that you are using the most recent edition of a document, go to: https://softwaresupport.hp.com/group/softwaresupport/search-
result?keyword=.
This site requires an HP Passport account. If you do not have one, click the Create an account button on the HP Passport Sign in page.
Support
Visit the HP Software Support web site at: https://softwaresupport.hp.com
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software Support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your
business. As a valued support customer, you can benefit by using the support web site to:
l Search for knowledge documents of interest
l Submit and track support cases and enhancement requests
l Download software patches
l Manage support contracts
l Look up HP support contacts
l Review information about available services
l Enter into discussions with other software customers
l Research and register for software training
Most of the support areas require that you register as an HP Passport user and sign in. Many also require a support contract. To register for an HP Passport ID, go to
https://softwaresupport.hp.com and click Register.
To find more information about access levels, go to: https://softwaresupport.hp.com/web/softwaresupport/access-levels
HP Software Solutions & Integrations and Best Practices

Visit HP Software Solutions Now at https://h20230.www2.hp.com/sc/solutions/index.jsp to explore how the products in the HP Software catalog work together, exchange
information, and solve business needs.
Visit the Cross Portfolio Best Practices Library at https://hpln.hp.com/group/best-practices-hpsw to access a wide variety of best practice documents and materials.
HP OMi Management Pack for Infrastructure (1.12) Page 2 of 178

Contents
Chapter 1: OMi Management Pack for Infrastructure 7
Chapter 2: Getting Started 8

Task 1: Adding Nodes to the BSM 9.2x or OMi 10.x Console 8
Task 2: Deploying the Infrastructure Discovery Aspect 8
Task 3: Verifying the Discovery 10
Task 4: Deploying the Infrastructure Management Templates or Discovery Aspects 10
Data Collection 11
Task 4a: Identifying and Deploying Infrastructure Management Template 11
Task 4b: Deploying Infrastructure Aspects 12
Task 5: Updating the Management Templates and Aspects to a Newer Version 13
Topology Synchronization for Smart Plug-in for Infrastructure 16
Chapter 3: Components of OMi MP for Infrastructure 18

Infrastructure Management Templates 18
Overview of Infrastructure Management Templates 19
How to Access Infrastructure Management Templates 19
How to Deploy Infrastructure Management Templates 20
How to Automatically Assign Management Templates & Aspects 20
Essential Cluster Management Template 22
How to Access the Essential Cluster Management Template 22
Essential IBM Power Management Template 23
How to Access the Essential IBM Power Management Template 23
Essential KVM Management Template 24
How to Access the Essential KVM Management Template 24
Essential Oracle Solaris Management Template 24
How to Access the Essential Oracle Solaris Management Template 25
Essential System Management Template 25
How to Access the Essential System Management Template 25
Essential VMware vSphere Management Template 26
How to Access the Essential VMware vSphere Management Template 26
Essential XEN Management Template 27
How to Access Essential XEN Management Template 27
Extensive IBM Power Management Template 27

User Guide
How to Access Extensive IBM Power Management Template 28

Extensive KVM Management Template 28
How to Access the Extensive KVM Management Template 28
Extensive Oracle Solaris Management Template 29
How to Access the Extensive Oracle Solaris Management Template 29
Extensive System Management Template 30
How to Access the Extensive System Management Template 30
Extensive VMware vSphere Management Template 31
How to Access the Extensive VMware vSphere Management Template 31
Extensive XEN Management Template 31
How to Access the Extensive XEN Management Template 32
Infrastructure Aspects 32
How to Access the Infrastructure Aspects 33
How to Create Infrastructure Aspects 33
How to Deploy Infrastructure Aspects 35
Systems Infrastructure Aspects 36
User Interface Reference 36
Bandwidth Utilization and Network IOPS 37
CPU Performance 37
General System Services Availability 38
Key System Services Availability 50
Memory and Swap Utilization 55
Remote Disk Space Utilization 55
Resource Bottleneck Diagnosis 56
Server Hardware Fault 58
Space Availability and Disk IOPS 60
System Infrastructure Discovery 61
System Fault Analysis 61
User Logins 66
Virtualization Infrastructure Aspects 69
IBM Power Guest Health 70
IBM Power Guest Performance 71
IBM Power Host Health 72
KVM Guest Health 73
KVM Guest Performance 74
KVM Host Health 74
Oracle Solaris Guest Health 75
Oracle Solaris Guest Performance 75

User Guide
Oracle Solaris Host Health 77

VMware Cluster Performance 78
VMware Datastore Performance 80
VMware Host Health 81
VMware Resource Pool Monitor 82
VMware Guest Health 83
VMware vSphere Events 85
Virtual Infrastructure Discovery 86
Xen Guest Health 86
Xen Guest Performance 87
Xen Host Health 87
Cluster Infrastructure Aspects 88
Cluster Infrastructure Discovery 89
Cluster Strength and Status 89
Parameters 91
Types of Parameters 92
Parameter Flags 92
Infrastructure Parameters 92
Tuning of Parameters 105
Configuration Items and Configuration Item Types 106
CI Types Mapped in OMi 106
Run Time Service Model (RTSM) Views 107
How to Access the RTSM Views 107
Event Type Indicators 119
How to Access the Event Type Indicators (ETIs) 119
Health Indicators 120
How to Access Health Indicators (HIs) 120
Topology Based Event Correlation (TBEC) Rules 129
How to Access the Correlation Rules 129
Mapping Rules 135
Operations Orchestration (OO) Flows 137
Tools 139
How to Access Tools 139
Chapter 4: Customizing OMi MP for Infrastructure 143

Creating Infrastructure Management Templates 143

User Guide
Editing Infrastructure Management Templates 145

Editing Parameters - Changing the Default Values 145
Editing Aspects - Deleting an Aspect 146
Chapter 5: Troubleshooting 147
Appendix: Graph Templates 148

Systems Infrastructure Graph Templates 148
Virtualization Infrastructure Graph Templates 165
Send Documentation Feedback 178

Chapter 1: OMi Management Pack for
Infrastructure
The HP OMi Management Pack for Infrastructure (OMi MP for Infrastructure) works with
HP Operations Manager i (OMi) and enables you to seamlessly monitor the various systems operating
in a data center environment. It includes Indicators - Health Indicators (HIs), Event Type Indicators
(ETIs), and Topology Based Event Correlation (TBEC) Rules that analyze and categorize the events
occurring in the systems and report the health status of the systems. It also includes Management
Templates for monitoring the availability, health, and performance of individual systems, clusters, and
virtual nodes. These Management Templates consists of a wide range of Aspects which enable
monitoring the system components.
The Management Templates can be seamlessly deployed by administrators for monitoring the systems
in any environment. The Management Templates can also be easily customized by subject matter
experts (SMEs) and developers to suit different monitoring requirements.
OMi MP for Infrastructure works with OMi and provides the following salient features:
l Ready-to-deploy, management solutions to suit different monitoring requirements.
l Aspects for creating customized solutions.
l Infrastructure element based deployment and configuration.

User Guide
Chapter 2: Getting Started

The following section provides step-by-step instructions on how to get started using OMi Management
Pack for Infrastructure:
Task 1: Adding Nodes to the BSM 9.2x or OMi 10.x

Console
Note: If the Node already exists in Run-time Service Model (RTSM), you can skip this step and
proceed to Task 2.
Before you begin monitoring, you need to add the nodes:
1. Open the Monitored Nodes pane from Administration:
On BSM 9.2x, click Admin > Operations Management > Setup > Monitored Nodes.
On OMi 10.x, click Administration > Setup and Maintenance > Monitored Nodes.
2. In the Node Views pane, click Predefined Node Filters > Monitored Nodes and then click
and then click Computer > <select the OS Type>. The Create New Monitored Nodes dialog
box appears.
3. Specify the Primary DNS Name, IP Address, Operating System, and Processor Architecture of
the node and click OK.
The newly created node is saved as a CI instance in RTSM.
Note: The node with HP Operations Agent needs to be connected to the HP OMi server and
certificate needs to be granted.
Task 2: Deploying the Infrastructure Discovery Aspect

The OMi MP for Infrastructure has three Discovery Aspects and they are: System Infrastructure
Discovery, Virtual Infrastructure Discovery, and Cluster Infrastructure Discovery. Depending on the
type of node, you can deploy one or a combination of these Aspects.

User Guide
Type of Node Aspects to be Deployed
Standalone Node Deploy the System Infrastructure Discovery Aspect.

(Windows)
Standalone Node Deploy the System Infrastructure Discovery Aspect.

(Linux)
Cluster Node Deploy the System Infrastructure Discovery Aspect first and then deploy the
Cluster Infrastructure Discovery Aspect.
ESX Host (Virtual Deploy the Virtual Infrastructure Discovery Aspect.

Appliance (VA))
To discover the CIs on the added managed nodes, you must deploy the Infrastructure Discovery
Aspect.
1. Open the Management Templates & Aspects pane:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Management
Templates & Aspects.
On OMi 10.x, click Administration > Monitoring > Management Templates & Aspects.
2. In the Configuration Folders pane, click Configuration Folders > Infrastructure Management.
3. In the Management Templates & Aspects pane, right-click the respective Infrastructure Discovery
Aspect, and then click Assign and Deploy Item. The Assign and Deploy Wizard opens.
4. In the Configuration Item tab, click the CI to which you want to deploy the Discovery aspect and
then click Next.
5. In the Required Parameters tab, all mandatory parameters are listed in the management
template that do not have a value.
6. In the All Parameters tab on BSM 9.2x or Parameter Summary tab on OMi 10.x, you can
change the default values of the parameters.
Note: In the All Parameters tab on BSM 9.2x or Parameter Summary tab on OMi 10.x, you
can override the default values of any parameter. You can specify a value for each parameter
at the Aspect level. By default, parameters defined as expert parameters are not displayed.
To display expert parameters, click Show Expert Parameters.
7. (Optional). If you do not want to enable the assignment immediately, clear the Enable Assigned
Objects check box on BSM 9.2x or Enable Assignment(s) check box on OMi 10.x. You can then
enable the assignment later using the Assignments & Tuning pane.
8. Click Finish.

User Guide
Note:
l After the Infrastructure Discovery Aspect is deployed, a message stating the Assignment and
deployment jobs created appears. To check the status of the deployment jobs:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Deployment Jobs.
On OMi 10.x, click Administration > Monitoring > Deployment Jobs.
l For monitoring VMware vSphere virtualization, IBM Power, and Oracle Solaris zones
environment, see Monitoring using OMi MP for Infrastructure section in the OMi Management
Pack for Infrastructure Installation Guide.
Task 3: Verifying the Discovery

After you deploy the Infrastructure Discovery Aspect, you must verify if the CIs are populated in the
Top View.
1. Open the Event Perspective pane:
On BSM 9.2x, click Applications > Operations Management > Event Perspective.
On OMi 10.x, click Workspaces > Operations Console > Event Perspective.
2. In the Browse Views tab, select the HACluster_Infrastructure, Sol_Zones_Infrastructure,

Virtual_Infrastructure or Systems_Infrastructure view.
The CIs are populated in Browse Views.
Note: For more information about the Views, see Run Time Service Model (RTSM) Views.
Task 4: Deploying the Infrastructure Management

Templates or Discovery Aspects
Note: If you are using the Monitoring Automation (9.2x) for Composite Applications license,
you can either deploy the Infrastructure Management Templates or Infrastructure Aspects to the
CIs. For more information about deploying the Infrastructure Management Template, see Task 4a:
Identifying and Deploying Infrastructure Management Template.

User Guide
Note: If you are using the Monitoring Automation for Servers license, you can deploy the
Infrastructure Aspects. For more information about deploying the Infrastructure Aspects, see Task
4b: Deploying Infrastructure Aspects.
Data Collection
Frequency (polling interval) at which each Aspect must be monitored is predefined with a default value
in a specific frequency parameter. Frequency parameter is an expert parameter that is defined for each
of the metrics regardless of whether they are for generating events or not.
Following are the four predefined frequency parameters:
Parameter Frequency
Very High 5 mins
High 15 mins
Medium 1 hour
Low 24 hours
After Management Templates and Aspects are deployed, the collector is triggered based on the
predefined frequency parameter in a specific Aspect. You can modify the default value of the parameter
at the following levels:
l During deployment of the Management Template or Aspects using the Management Templates &
Aspects pane.
l After deployment using the Assignments & Tuning pane.
For more information about how to modify the parameter values, see Tuning Parameters.
Task 4a: Identifying and Deploying Infrastructure

Management Template
You must deploy the Infrastructure Discovery Aspect even if the CIs are already populated by any
other source such as SiteScope, DDM and so on. For more information on deploying the Discovery
Aspect, see Task 2: Deploying the Infrastructure Discovery Aspect.
To deploy the Infrastructure Management Templates to the CIs, follow these steps:

User Guide
2. In the Configuration Folders pane, click Configuration Folders > Infrastructure Management >
Infrastructure Management Templates.
3. In the Management Templates & Aspects pane, click the Management Template that you want to
deploy, and then click Assign and Deploy Item. The Assign and Deploy wizard opens.
4. In the Configuration Item tab, click the CI to which you want to assign the Management
Template, and then click Next.
5. In the Required Parameters tab, all mandatory parameters are listed in the Management
Template that do not have a value.
6. Click Next to go to All Parameters tab on BSM 9.2x orParameter Summary tab on OMi 10.x.
at the Aspect level. By default, parameters defined as expert parameters are not displayed.
To display expert parameters, click Show Expert Parameters.
7. Click Next.
9. Click Finish.
Task 4b: Deploying Infrastructure Aspects

You must deploy the Infrastructure Discovery Aspect even if the CIs are already populated by any
other source such as SiteScope, DDM, and so on. For more information on deploying the Discovery
Aspect, see Task 2: Deploying the Infrastructure Discovery Aspect.
Note: If you are using the Monitoring Automation for Composite Applications license and
have assigned the Infrastructure Management Templates to the CI, you can skip this task.

User Guide
2. In the Configuration Folders pane, click Configuration Folders > Infrastructure Management.
3. In the Management Templates & Aspects pane, select the Aspect you want to deploy, and then
click Assign and Deploy Item. The Assign and Deploy wizard opens.
4. In the Configuration Item tab, select the CI to which you want to assign the Aspect and then
click Next.
6. In the All Parameters tab on BSM 9.2x or the Parameter Summary tab on OMi 10.x, you can
change the default values of the parameters.
7. Click Next.
9. Click Finish.
Task 5: Updating the Management Templates and

Aspects to a Newer Version
You can update the existing deployed Management Templates and Aspects to the latest version. The
following are two scenarios when you need to update the Management Templates or Aspects:
Use Case 1: You have already deployed Infrastructure Aspects and/or Management Templates to the
managed nodes before installing OMi MP for Infrastructure 1.12. We recommend you to use the latest
version of Aspects or Management Templates on those nodes.
To update to the latest version, select the Management Templates or Aspects on the managed nodes.
Perform the following steps for each Management Template and Aspect assignment on each of the
managed nodes:
For BSM 9.2x:
1. Open the Management Templates & Aspects pane and click Admin > Operations Management
> Monitoring > Management Templates & Aspects.

User Guide
2. Select 1.100 Infrastructure Aspects and/or Management Templates that has been deployed to
nodes.
3. Edit the parameters and redeploy to each of the Node CIs.
For OMi 10.x:
1. Open the Assignments & Tuning pane and click Administration > Monitoring > Assignments
& Tuning.
2. In the Browse Views pane, select the Infrastructure_Common view and select each Node CI
where version update is required.
3. Click Show Assignments That Require an Update.
All the Management Templates and Aspects that requires an update are listed.
4. Select each of the Management Templates and Aspects and click Update Assigned Item.
The Update Assigned Item dialog box appears.
5. In the Update Options tab, follow these steps:
n Select the latest version from the Update to Version drop down list.
n If you select Use parameter values from existing assignments, only the new mandatory
parameters that do not have a default value are listed.
n If you select Use default parameter values from version selected above, all mandatory
parameters from the selected Management Template or Aspect version that do not have a
default value are displayed. These parameters must be edited before proceeding to the next
step of the wizard.
6. Click Next to go to Required Parameters.
To change a parameter, double-click or select the parameter from the list and click Edit.
The Edit Parameter dialog opens. If there are no mandatory parameters that require editing for this
assignment, you are automatically taken to the All Parameters tab on BSM 9.2x or the
Parameter Summary tab on OMi 10.x.
7. Click Next to go to the All Parameters tab on BSM 9.2x or the Parameter Summary tab on OMi
10.x or click Finish to save the changes and close the wizard.
8. Click Finish to save the changes and close the wizard. The assigned item is updated to the
specified Management Template or Aspect version.
Use Case 2: You are using a Management Pack that internally uses the OMi MP for Infrastructure
Aspects and you need to update the Infrastructure Aspects to the latest version. For example, OMi MP

User Guide
for Oracle Database, OMi MP for Oracle WebLogic, OMi MP for Microsoft Exchange Server, OMi MP
for SAP, and so on use Infrastructure Aspects to monitor Infrastructure performance such as Resource
Bottleneck Diagnosis, System Fault Analysis and so on.
To update all items in a Management Template on BSM 9.2x and OMi 10.x Servers, do the
following:
2. Select each Management Template that contains the Infrastructure Aspects.
3. Click Update to Latest.
The Update to Latest Wizard appears.
4. In the Options tab, click Next.
5. In the Preview tab, a preview of the update is shown as an expanded tree view of the Aspect,
where items that will be updated are labeled "(old version > new version)", and items that will not
be updated are labeled "(current version)".
6. Click Finish to apply the update as shown in the preview.
To update the Management Templates to latest on the managed nodes:
For BSM 9.2x:
1. Click Admin > Operations Management > Monitoring > Management Templates &
Aspects.
2. Select each of the application Management Templates of latest version which includes updated
Infrastructure Aspects.
3. Edit the parameters and redeploy to each of the CIs.
For OMi 10.x:
1. Click Administration > Monitoring > Assignments & Tuning.
2. In the Browse Views pane, select the specific application view and select each CI where version
update is required.
3. Click Show Assignments That Require an Update.
All the Management Templates and Aspects that requires an update are listed.

User Guide
4. Select each Management Templates and click Update Assigned Item.
The Update Assigned Item dialog box appears.
5. In the Update Options tab, follow these steps:
n Select the latest version from the Update to Version drop down list.
n If you select Use parameter values from existing assignments, only the new mandatory
parameters that do not have a default value are listed.
n If you select Use default parameter values from version selected above, all mandatory
parameters from the selected Management Template or Aspect version that do not have a
default value are displayed. These parameters must be edited before proceeding to the next
step of the wizard.
6. Click Next to go to Required Parameters.
To change a parameter, double-click or select the parameter from the list and click Edit.
The Edit Parameter dialog opens. If there are no mandatory parameters that require editing for this
assignment, you are automatically taken to the All Parameters tab on BSM 9.2x or the
7. Click Next to go to All Parameters tab on BSM 9.2x or the Parameter Summary tab on OMi 10.x
or Finish to save the changes and close the wizard.
8. Click Finish to save the changes and close the wizard. The assigned item is updated to the
specified Management Template or Aspect version.
Topology Synchronization for Smart Plug-in for

Infrastructure
Note: It is recommended to check the Topology Synchronization settings if a Node or a CI is
monitored by HP Operations Manager.
If you use Smart Plug-in for Infrastructure with HP Operations Manager, perform the following steps to
forward topology data from the HPOM server to the BSM or OMi Server. For more information about
Topology Synchronization, see the HP Operations Manager i Administration Guide.
1. Open the Infrastructure Settings from Administration:
On BSM 9.2x, click Admin > Platform > Setup and Maintenance > Infrastructure Settings.
On OMi 10.x, click Administration > Setup and Maintenance > Infrastructure Settings.

User Guide
2. In the Infrastructure Settings pane, select Applications > Operations Management.
3. To verify if the topology synchronization package to be synced is added, click Operations

Management - HPOM Topology Synchronization Settings.
4. If the package is not added, in Packages for Topology Sync, click Edit.
5. In Value, add default;nodegroups;operations-agent;HPOprSys;HPOprClu;HPOprVir and

click Save.

Chapter 3: Components of OMi MP for
Infrastructure
The OMi MP for Infrastructure includes the following components for monitoring the availability, health
and performance of individual systems, clusters, and virtual nodes.
l Infrastructure Management Templates
l Infrastructure Aspects
l Parameters
l Configuration Items and Configuration Item Types
l Run Time Service Model (RTSM) Views
l Event Type Indicators
l Health Indicators
l Policies Setting HIs/ETIs
l Topology Based Event Correlation (TBEC) Rules
l Mapping Rules
l Tools
Infrastructure Management Templates

The Infrastructure Management Templates provide a complete management solution for monitoring the
health and performance of individual systems, virtual, and clusters in a datacenter environment.
By default, OMi MP for Infrastructure consists of a set of Infrastructure Management Templates with
predefined settings to monitor the systems in an environment. You can deploy the Infrastructure
Management Templates with the default parameters and seamlessly monitor the systems in your
environment. These Infrastructure Management Templates comprises several Aspects which enable
you to monitor the systems.
Based on the monitoring requirements, you can also customize the Infrastructure Management
Templates or create Infrastructure Management Templates to monitor the systems in your
environment.

User Guide
Chapter 3: Components of OMi MP for Infrastructure
Overview of Infrastructure Management Templates

OMi MP for Infrastructure comprises the following Infrastructure Management Templates:
l Essential Cluster Management Template
l Essential IBM Power Management Template
l Essential KVM Management Template
l Essential Oracle Solaris Management Template
l Essential System Management Template
l Essential VMware vSphere Management Template
l Essential XEN Management Template
l Extensive IBM Power Management Template
l Extensive KVM Management Template
l Extensive Oracle Solaris Management Template
l Extensive System Management Template
l Extensive VMware vSphere Management Template
l Extensive XEN Management Template
How to Access Infrastructure Management Templates
2. Click Configuration Folders > Infrastructure Management > Infrastructure Management

Templates.
Note: The version number of OMi MP for Infrastructure is 1.12, whereas the version number of
Management Templates and Aspects is 1.1 and the version number of the Policy Templates is
1.1000.

User Guide
How to Deploy Infrastructure Management Templates

For more information about deploying Infrastructure Management Templates, see Task 4b: Identifying
and Deploying Infrastructure Management Template.
How to Automatically Assign Management Templates & Aspects
1. Open the Automatic Assignment Rules window:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Automatic
Assignment Rules.
On OMi 10.x, click Administration > Monitoring > Automatic Assignment Rules.
The screen consists of the Auto-Assignment Rules pane at the top, and a parameter list at the
bottom.
2. Click New Assignment in the toolbar of the Auto-Assignment Rules pane and select the
appropriate option. The Create Auto-Assignment Rule wizard appears.
3. In the Select Target View tab, select an Infrastructure view containing the CIs for which you want
to create an automatic assignment, and click Next.
4. In the Select Item to Assign tab, click the Infrastructure management template or aspect that
you want to automatically assign to all CIs with a CI type appearing in the selected view.
The latest version of the management template or aspect that you want to assign is selected by
default. Click Next.
template that do not yet have a value. As they are mandatory, however, all listed parameters must
be given a value before the management template can be deployed.
If all required values are specified, you can choose one of the following actions:
n Click Finish to assign the configuration object to the selected CI and close the wizard or
dialog.
n Click Next to go to All Parameters tab on BSM 9.2x or Parameter Summary tab on OMi 10.x,
where you can override the default value of any parameter, including those that are not
required.
Note: To access the Configure Options tab, click Next in this step, and Next again in the
All Parameters tab on BSM 9.2x or Parameter Summary tab on OMi 10.x.

User Guide
To change a parameter, double-click it, or select it in the list and click Edit.
n For standard parameters, the Edit Parameter dialog opens.
Click Value, specify the value, and then click OK.
n For instance parameters, the Edit Instance Parameter dialog opens.
Add instance values, and then for each instance value, specify dependent parameter values.
After you specify the instances and dependent parameter values, click OK.
6. (Optional). In the All Parameters tab on BSM 9.2x or Parameter Summary tab on OMi 10.x,
specify a value for each parameter that needs to be monitored against a different value than the
default value.
To change a parameter, double-click it, or select it in the list and click Edit.
n For standard parameters, the Edit Parameter dialog opens.
n For instance parameters, the Edit Instance Parameter dialog opens.
Add instance values, and then for each instance value, specify dependent parameter values.
After you specify the instances and dependent parameter values, click OK.
Click Next to go to the Configure Options tab, or Finish to save the assignment and close
the wizard.
7. (Optional). In the Configure Options tab, clear the Enable Assigned Objects check box on
BSM 9.2x and Enable Assignment(s) check box on OMi 10.x if you do not want to activate the
assignment rule immediately.
You can activate automatic assignment rules later using the Automatic Assignment Rules pane
at:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Automatic
Assignment Rules.
On OMi 10.x, click Administration > Monitoring > Automatic Assignment Rules.
8. Click Finish to save the changes and close the wizard. The assignment rule is added to the list of
auto-assignment rules.
An assignment may trigger an event to be sent to OMi if one of the following situations applies:
l A deployment job fails.
l An auto-assignment fails.
l An auto-assignment succeeds. This behavior can be configured in the Infrastructure Settings.

User Guide
You can check if the automatic assignment rule successfully created the expected assignments as
follows:
1. Open the Assignments & Tuning pane:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Assignments &
Tuning.
On OMi 10.x, click Administration > Monitoring > Assignments & Tuning.
2. In the Browse Views tab, select the view you identified when creating your automatic assignment
rule.
3. Expand the view, and select a node that corresponds to the root CI type of the assigned item.
Assignments created as a result of Automatic Assignment Rules are shown in the list of
assignments at the top of the right pane, and have the value Auto-Assignment in the column
Assigned By.
You can consider the following options for tuning the assignment:
l Use the Auto-Assignment Rules pane to tune the parameter values for all assignments triggered by
the automatic assignment rule.
l Use the Assignments pane to tune, redeploy, delete, and enable or disable individual assignments.
How to Display an Assignment Report for a Management Template
1. Select the Management Template you want to create the report for.
2. Click Generate Assignment Report in the Management Templates & Aspects pane.
The pre-configured Assignment Report is displayed.
You can display additional types of reports from the Assignments & Tuning pane.
Essential Cluster Management Template

The Essential Cluster Management Template monitors the high availability (HA) components such as
the cluster strength, nodes and resource pool availability in a clustered environment. It monitors the
single point of failure (SPOF), quorum conditions and node strength of the components in a clustered
environment. The Essential Cluster Management Template comprises of specific Aspects for
monitoring these features.
How to Access the Essential Cluster Management Template

User Guide

Templates > Essential Cluster Management.
Management Template - Aspects
The Essential Cluster Management Template consists of the following Aspects:
l Cluster Strength and Status
l Cluster Infrastructure Discovery
Essential IBM Power Management Template

The Essential IBM Power Management Template manages the health and availability of IBM Power
virtualization environment. It monitors the basic functionality of the Virtualized IBM LPAR environment
- Guest availability, memory and CPU utilization of Frame and discovers the virtual components such
as hypervisor host, guest, and resource pool. The Essential IBM Power Management Template
comprises specific Aspects to monitor these features.
How to Access the Essential IBM Power Management Template

Templates > Essential IBM Power Management.
The Essential IBM Power Management Template consists of the following Aspects:
l IBM Power Host Health
l IBM Power Guest Health

User Guide
Essential KVM Management Template

The Essential KVM Management Template manages the health and availability of KVM Virtualization
Environment in a Datacenter. It monitors the basic functionalities of Virtualized KVM environment -
resource usage for KVM host and individual Guest, Guest availability and resources, and discovers the
virtual components like hypervisor host, guest, and resource pool. The Essential KVM Management
Template comprises specific Aspects to monitor these features.
How to Access the Essential KVM Management Template

Templates > Essential KVM Management.
Note: You can deploy Essential KVM Management Template only on the host.
The Essential KVM Management Template consists of the following Aspects:
l Virtual Infrastructure Discovery
l KVM Guest Health
l KVM Host Health
Essential Oracle Solaris Management Template

The Essential Oracle Solaris Management Template manages the health and availability of Oracle
Solaris Virtualization Environment. It monitors the basic functionality of the Oracle Solaris Zones
environment - Guest resources, Host Resource Utilization and discovers the virtual components such
as hypervisor host, guest, and resource pool. The Essential Oracle Solaris Management Template
comprises of specific Aspects to monitor these features.

User Guide
How to Access the Essential Oracle Solaris Management Template

Templates > Essential Oracle Solaris Management.
Note: You can deploy Essential Oracle Solaris Management Template only on the host.
The Essential Oracle Solaris Management Template consists of the following Aspects:
l Oracle Solaris Host Health
l Oracle Solaris Guest Health
Essential System Management Template

The Essential System Management Template monitors the health of all the systems - individual,
clusters, and virtual in a data center environment. It monitors the basic functionalities - availability of
system services and processes, software resources (CPU, memory, network, and disk), checks for
system downtime risks by tracking congestion and bottlenecks in system resources and failed logins
and last logins on your system. The Essential System Management Template comprises of specific
Aspects to monitor these features.
How to Access the Essential System Management Template

Templates > Essential System Management.

User Guide
The Essential System Management Template consists of the following Aspects:
l Resource Bottleneck Diagnosis
l Key System Services Availability
l System Fault Analysis
l User Logins
l System Infrastructure Discovery
Essential VMware vSphere Management Template

The Essential VMware vSphere Management Template monitors the health, availability and status of
hosts or guests in a VMware vSphere Environment. It monitors the basic functionality in a virtualized
VMware vSphere environment - Datastore utilization, Guest availability and resources, resource usage
for individual hosts and virtual machines from vCenter and discovers the virtual components such as
hypervisor host, guest, and resource pool. The Essential VMware vSphere Management Template
How to Access the Essential VMware vSphere Management Template

Templates > Essential VMware vSphere Management.
The Essential VMware vSphere Management consists of the following Aspects:
l VMware Host Health
l VMware Guest Health
l VMware Datastore Performance
l VMware vSphere Events

User Guide
Essential XEN Management Template

The Essential XEN Management Template monitors the resource usage for XEN host and individual
guest systems. It monitors the basic functionalities of XEN virtualization environment - Guest
availability and resources, Host resource utilization and discovers the virtual components like
hypervisor host, guest, and resource pool. The Essential XEN Management Template comprises
specific Aspects to monitor these features.
How to Access Essential XEN Management Template

Templates > Essential XEN Management.
Note: You can deploy Essential XEN Management Template only on the host.
The Essential XEN Management Template consists of the following Aspects:
l Xen Guest Health
l Xen Host Health
Extensive IBM Power Management Template

The Extensive IBM Power Management Template monitors the performance and health of IBM Power
virtualization environment. It monitors the Guest performance as an advanced feature in addition to the
basic functionality - Guest availability, memory and CPU utilization of Frame and discovers the virtual
components such as hypervisor host, guest, and resource pool. The Extensive IBM Power
Management Template comprises of specific Aspects to monitor these features.

User Guide
How to Access Extensive IBM Power Management Template

Templates > Essential XEN Management.
The Extensive IBM Power Management Template consists of the following Aspects:
l IBM Power Host Health
l IBM Power Guest Health
l IBM Power Guest Performance
Extensive KVM Management Template

The Extensive KVM Management Template monitors the performance and health of host and guest
systems in a KVM Virtualization Environment. It monitors the Guest performance as an advanced
feature in addition to the basic functionalities - resource usage for KVM host and individual Guest,
Guest availability and resources, and discovers the virtual components like hypervisor host, guest, and
resource pool. The Extensive KVM Management Template comprises of specific Aspects to monitor
these features.
How to Access the Extensive KVM Management Template

Templates > Extensive KVM Management.

User Guide
Note: You can deploy Extensive KVM Management Template only on the host.
The Extensive KVM Management Template consists of the following Aspects:
l KVM Guest Health
l KVM Guest Performance
l KVM Host Health
Extensive Oracle Solaris Management Template

The Extensive Oracle Solaris Management Template monitors the performance and health of Oracle
Solaris Virtualization Environment. It monitors the Guest performance as an advanced feature in
addition to the basic functionalities of Oracle Solaris Zones environment - Guest resources, Host
Resource Utilization and discovers the virtual components such as hypervisor host, guest, and
resource pool. The Extensive Oracle Solaris Management Template comprises of specific Aspects to
monitor these features.
How to Access the Extensive Oracle Solaris Management Template

Templates > Extensive Oracle Solaris Management.
Note: You can deploy Extensive Oracle Solaris Management Template only on the host.
The Extensive Oracle Solaris Management Template consists of the following Aspects:
l Oracle Solaris Guest Health
l Oracle Solaris Guest Performance

User Guide
l Oracle Solaris Host Health
Extensive System Management Template

The Extensive System Management Template monitors the in-depth performance of a system by
analyzing availability and performance of individual system resources. It monitors the advanced
features - network I/O operations and performance, CPU performance and statistics, memory
performance, space utilization of remote disk, health and status of HP ProLiant servers and the basic
functionalities - availability of system services and processes, software resources (CPU, memory,
network, and disk), checks for system downtime risks by tracking congestions and bottlenecks in
system resources and failed logins and last logins on your system. The Extensive System
Management Template comprises of specific Aspects to monitor these features.
How to Access the Extensive System Management Template

Templates > Extensive System Management.
The Extensive System Management Template consists of the following Aspects:
l Bandwidth Utilization and Network IOPS
l CPU Performance
l Memory and Swap Utilization
l Remote Disk Space Utilization
l Resource Bottleneck Diagnosis
l Space Availability and Disk IOPS
l System Infrastructure Discovery

User Guide
Extensive VMware vSphere Management Template

The Extensive VMware vSphere Management Template monitors the health, availability, and status of
hosts or guests in a VMware vSphere Environment. It monitors the advanced features such as the
CPU and memory Utilization for VMware clusters and resource pools. It also monitors the basic
functionality such as Datastore utilization, Guest availability and resources, resource usage for
individual hosts and virtual machines from vCenter and discovers the virtual components such as
hypervisor host, guest, and resource pool. The Extensive VMware vSphere Management Template
How to Access the Extensive VMware vSphere Management Template

Templates > Extensive VMware vSphere Management.
The Extensive VMware vSphere Management consists of the following Aspects:
l VMware Host Health
l VMware Cluster Performance
l VMware Guest Health
l VMware Datastore Performance
l VMware Resource Pool Monitor
l VMware vSphere Events
Extensive XEN Management Template

The Extensive XEN Management Template monitors the performance and health of host and guest
systems in a XEN Virtualization Environment. It monitors Guest Performance as an advanced feature
in addition to the basic functionalities - Guest availability and resources, Host resource utilization and
discovers the virtual components like hypervisor host, guest, and resource pool. The Extensive
XEN Management Template comprises of specific Aspects to monitor these features.

User Guide
How to Access the Extensive XEN Management Template

Templates > Extensive XEN Management.
Note: You can deploy Extensive XEN Management Template only on the host.
The Extensive XEN Management Template consists of the following Aspects:
l XEN Guest Health
l XEN Guest Performance
l XEN Host Health
Infrastructure Aspects
Infrastructure Aspects monitor the system resources operating in a data center environment. The
systems can be stand-alone, virtual, or clustered systems. Each Infrastructure Aspect consists of
policy templates, instrumentation, and parameters for monitoring the health and performance of the
systems. Each Aspect provides the ability to monitor a Computer, VMware VirtualCenter, and
FailoverCluster CI.
Grouping of Infrastructure Aspects
The Infrastructure Aspects are grouped as follows:
l Systems Infrastructure Aspects
l Virtualization Infrastructure Aspects
l Cluster Infrastructure Aspects

User Guide
How to Access the Infrastructure Aspects
2. Click Configuration Folders > Infrastructure Management > <aspect folder>.
Note: The version number of OMi MP for Infrastructure is 1.12, whereas the version number of
Management Templates and Aspects is 1.1 and the version number of the Policy Templates is
1.1000.
How to Create Infrastructure Aspects
2. In the Configuration Folders pane:
Configuration Folders > Infrastructure Management
3. In the Configuration Folders pane, click the configuration folder in which you want to create the
new Aspect. If you need to create a new configuration folder, click the .
4. In the Management Templates & Aspects pane, click the , and then click . The Create
Aspect wizard opens.
5. In the General tab, type a unique Name for the new Aspect. Click Next.
6. Each Aspect enables you to manage one feature or characteristic of one or more types of
configuration item. In the CI Types tab, select one or more Available CI Type(s) to which this
Aspect can be assigned, and then click to add them to the list of assigned CI types. (Press
CTRL to select several CI types). Click Next.
7. In the Instrumentation tab, click to add instrumentation to the Aspect. The Add

User Guide
Instrumentation dialog box opens, which enables you to select the instrumentation that you want
to add. Click Next.
8. (Optional). In the Aspects tab, click , and then click . The Add Existing Aspect dialog box
opens, which enables you to select an existing Aspect that you want to nest within this Aspect.
Click an Aspect, and then click OK.
If suitable Aspects do not exist, click , and then click to create a new Aspect. Click Next.
9. In the Policy Templates tab, click Add Policy Templates on BSM 9.2x and Add Policy
Templates From Liston OMi 10.x.
The Add Policy Template to Aspect dialog box opens. Select the policy templates that you want to
add, and then click OK. (Press CTRL to select several policy templates.)
If suitable policy templates do not exist, click , and then click to create a policy template.
10. In the Policy Templates tab, select the Version of the policy templates that you want to add.
Each modification to a policy template is stored in the database as a separate version. Aspects
contain specific versions of policy templates. If a new version of a policy template becomes
available later, you have to update the Aspect to include the latest version.
11. (Optional). In the Policy Templates tab, click the policy template to which you want to add a
deployment condition, click , and then click .
The Edit Deployment Condition dialog box opens, which enables you to specify deployment
conditions for the selected policy template.
Set the condition and then click OK.
In the Policy Templates tab, click Next.
12. In the Parameters tab, the list of all the parameters added to this Aspect from the policy templates
is displayed.
To combine parameters:
a. Press CTRL and click the parameters that you want to combine.
b. Click . The Edit/Combine Parameters dialog box opens.
c. Type a Name for the combined parameters.
d. (Optional). Specify a Description, Default Value, and whether the combined parameter is
Read Only, an Expert Setting, or Hidden.

User Guide
You can either set a specific default value, or you can click From CI Attribute and then
browse for a CI attribute. When you specify a CI attribute, Operations Management sets the
parameter value automatically during deployment of the policy templates, using the actual
value of this attribute from the CI. You can also set conditional parameter values here.
Note: Read Only prevents changes to the parameter value when the Aspect is assigned
to a configuration item. Hidden also prevents changes, but additionally makes the
parameter invisible. Users can choose whether to show expert settings when they make
an assignment.
e. Click OK.
You can also edit the parameters without combining them, to override the defaults in the policy
template. Click one parameter, and then click . The Edit/Combine Parameters dialog box
opens.
13. In the Create Aspect wizard, click Finish to save the Aspect and close the wizard. The new
Aspect appears in the Management Templates & Aspects pane.
How to Deploy Infrastructure Aspects
Configuration Folders > Infrastructure Management
3. In the Management Templates & Aspects pane, click the Aspect that you want to deploy, and then
click . The Assign and Deploy wizard opens.
4. In the Configuration Item tab, click the configuration item to which you want to assign the
Aspect, and then click Next.
If all required values are specified, click Next to go to the All Parameters tab on BSM 9.2x

User Guide
To change a parameter, double-click it, or click .
a. Select the Instance parameter in the list, and then click . The Edit Parameter Value dialog
box opens.
b. Click Value, specify the value, and then click OK.
c. Select the Dependent Parameters and specify the value. Click Next.
6. Click Next to go to the All Parameters tab on BSM 9.2x Parameter Summary tab on OMi 10.x.
To change the default values of the parameters, you can select the parameter and then click .
The Edit Parameter dialog box opens. Click Value, specify the value, and then click OK.
at the Management Template level. By default, parameters defines as expert parameters are
not shown. To show expert parameters, click Show Expert Parameters.
Click Next.
Objects check box on BSM 9.2x or Enable Assignment(s) check box on OMi 10.x. You can
then enable the assignment later using the Assignments & Tuning pane.
8. Click Finish.
Systems Infrastructure Aspects

Systems Infrastructure Aspects manage the health of every single system in the environment. Each
system will have its own set of resources, hardware and software that needs to be managed for the
system to be healthy. It also monitors the performance of all system resources such as CPU, Memory,
Disk, FileSystem, Network Interface, System process and services, Security, System logging and so
on. Systems Infrastructure Aspects monitors the Computer CI types.
User Interface Reference

General Provides an overview of the general attributes of the Systems Infrastructure
Aspects.
CI Type The type of CIs that can be assigned to the Aspect. This is the type of CI
which is assigned to the Management Template. The Systems Infrastructure
Aspects contain the Computer CI types.
Instrumentation Provides an overview of the programs deployed to the CI types which

contains the System Infrastructure Aspect.

User Guide
Aspects Provides an overview of any Aspects that contain the Systems Infrastructure
Aspect. You can expand each item in the list to see more details about the
nested Aspect.
Policy Templates Provides an overview of the policy templates that contain the Systems
Infrastructure Aspect. You can expand each item in the list to see more
details about the policy template.
The Systems Infrastructure Aspects consists of the following:
Bandwidth Utilization and Network IOPS
This Aspect monitors IO operations, and performance of the systems in the network. It monitors the
network IO operations and performance based on the bandwidth used, outbound queue length and
average bytes transferred per second. This Aspect contains the following policy template:
CI Type Policy Template Policy Description Policy Type
Computer Sys_ Monitors the network usage of the Measurement

NetworkUsageAndPerformance systems and shows error rates and Threshold
collisions to identify potential Template
network bottlenecks. It also monitors
the physical NICs of only the vMA
machines. It does not monitor
performance data for package
collision on Windows as the
BYNETIF_COLLISION metric is not
available on Windows operating
systems.
CPU Performance
This Aspect monitors the overall CPU performance such as the CPU utilization percentage and spike
in CPU usage. Individual CPU performance monitoring is based on total CPU utilization, CPU
utilization in user mode, CPU utilization in system mode and interrupt rate. This Aspect contains the
following policy template:

User Guide
CI Type Policy Template Indicator Policy Description Policy Type
Computer Sys_ CPUUsageLevel Monitors the variation in Measurement

CPUSpikeCheck processor performance. A Threshold
system experiences CPU spike Template
when there is a sharp rise in the
CPU usage immediately
followed by a decrease in
usage. It also monitors the CPU
time spent in user mode and
system mode. It also monitors
the total CPU time when the
CPU is busy.
General System Services Availability
This Aspect monitors the availability of system services and processes. This Aspect monitors the
following system services and processes:
l HP-UX: Bootpd, Cron, and Network File System (NFS)
l Linux: Dynamic Host Configuration Protocol (DHCP), Named, NFS, Sendmail, Cron, and Server
Message Block (Smb)
l Windows: Distributed File System (DFS), DHCP, Domain Name system (DNS), File Transfer
Protocol (FTP), Firewall, Fax, NFS, Remote Procedure Call (RPC), RRA, Print, Simple Network
Management Protocol (SNMP), Terminal server, Web Management Tools, and Web Server
Service.
l AIX: Cron, DHCP, Named, NFS, Portmap, Sendmail, and Webserver
l Solaris: DHCP, Named, NFS, Sendmail, Cron, and SNMP
l Debian: Apache, Cron, Exim, Internet Service Daemon (InetD), Named, Nfs, NetBIOS Message
Block Daemon (Nmbd), Samba, and Single Sided High Density (Sshd).
This Aspect consists of the following policy templates:

User Guide
Policy
Descriptio
CI Type Policy Template Indicator n Policy Type
Comput Sys_AIXCronProcessMonitor BatchJobService Monitors Service/Proce

er the Cron ss Monitoring
daemon Template
processes
running on
the AIX
operating
systems.
Sys_AIXDHCPProcessMonitor DHCPServerServi Monitors

ce the DHCP
server
daemon
processes
running on
AIX
operating
systems.
Sys_AIXNamedProcessMonitor DNSService Monitors

the Named
processes
running on
the AIX
operating
systems.
Sys_AIXNfsServerProcessMonitor FileServerService Monitors

the NFS
server
related
processes
running on
the AIX
operating
systems.

User Guide
Policy
Descriptio
Sys_AIXPortmapProcessMonitor RPCService Converts

the RPC
program
numbers
into
Internet
port
numbers
running on
the AIX
operating
systems.
Sys_AIXQdaemonProcessMonitor PrintService Monitors

the job
requests
and the
resources
required to
complete
the jobs
running on
AIX
operating
systems.
Sys_AIXSendmailProcessMonitor EmailService Monitors

the
Sendmail
daemon
processes
running on
the AIX
operating
systems.
Sys_AIXWebserverProcessMonitor WebServerServic Monitors

e the httpd
daemon
processes
running on
the AIX
operating
systems.

User Guide
Policy
Descriptio
Sys_HPUXBootpdProcessMonitor DHCPServerServi Monitors

ce the Bootpd
daemon
processes
running on
the HP-UX
operating
systems.
Sys_HPUXCronProcessMonitor BatchJobService Monitors

the Cron
daemon
processes
on the HP-
UX
operating
systems.
Sys_ FileServerService Monitors

HPUXNfsServerProcessMonitor the state of
NFS
daemon
processes
running on
the HP-UX
operating
systems.
Sys_LinuxDHCPProcessMonitor DHCPServerServi Monitors

ce the DHCP
daemon
processes
running on
Linux
operating
systems.

User Guide
Policy
Descriptio
Sys_LinuxNamedProcessMonitor DNSService Monitors

the Named
daemon
processes
running on
Linux
operating
systems.
Sys_LinuxNfsServerProcessMonitor FileServerService Monitors

the state of
NFS
daemon
processes
running on
Linux
operating
systems.
Sys_LinuxSendmailProcessMonitor EmailService Monitors

the
Sendmail
daemon
processes
running on
the Linux
operating
systems.

LinuxSmbServerProcessMonitor SMB
daemon
processes
running on
the Linux
operating
systems.

User Guide
Policy
Descriptio
Sys_MSWindowsDFSRoleMonitor NA Monitors
the
availability
of system
services
required for
the
DFS role
service.
Sys_ DHCPServerServi Monitors

MSWindowsDHCPServerRoleMonit ce the
or availability
of system
services
required for
the DHCP
server role
service.
Sys_ DNSService Monitors

MSWindowsDNSServerRoleMonitor the
availability
of system
services
required for
the
DNS serve
r role
service.
Sys_ FTPService Monitors

MSWindowsFTPServiceRoleMonito the
r availability
of system
services
required for
the FTP
publishing
service role
service.

User Guide
Policy
Descriptio
Sys_ NA Monitors
MSWindowsFaxServerRoleMonitor the
availability
of system
services
required for
the fax
server role
service.
Sys_ FirewallService Monitors

MSWindowsFirewallRoleMonitor the
availability
of system
services
required for
the
Windows
firewall.
Sys_MSWindowsNFSRoleMonitor NA Monitors
the
availability
of system
services
required for
the NFS
role
service.
Sys_ PrintService Monitors

MSWindowsPrintServiceRoleMonito the
r availability
of system
services
required for
print
services
role
service.

User Guide
Policy
Descriptio
Sys_ NA Monitors
MSWindowsRRAServicesRoleMoni the
tor availability
of system
services
required for
routing and
remote
access
services
role
service.
Sys_MSWindowsRpcRoleMonitor RPCService Monitors

the
availability
of system
services
required for
RPC.
Sys_ NA Monitors
MSWindowsSnmpProcessMonitor the SNMP
service on
Windows
operating
systems.
Sys_ NA Monitors
MSWindowsTSGatewayRoleMonito the
r availability
of system
services
required for
Terminal
Services
(TS)
gateway
role
service.

User Guide
Policy
Descriptio
Sys_ NA Monitors
MSWindowsTSLicensingRoleMonit the
or availability
of system
services
required for
TS
licensing
role
service.
Sys_ NA Monitors
MSWindowsTSWebAccessRoleMo the
nitor availability
of system
services
required for
TS web
access role
service.
Sys_ MSTerminalServic Monitors

MSWindowsTerminalServerRoleMo e the
nitor availability
of system
services
required for
terminal
server role
service.
Sys_ NA Monitors
MSWindowsWebMgmtToolsRoleMo the
nitor availability
of system
services
required for
web
manageme
nt tools role
service.

User Guide
Policy
Descriptio
Sys_ WebServerServic Monitors

MSWindowsWebServerRoleMonitor e the
availability
of system
services
required for
web server
role
service.
Sys_OpenSshdProcessMonitor SecureLoginServi Monitors

ce SSH
daemon
processes
running on
the system
Sys_RHELCronProcessMonitor BatchJobService Monitors

Cron
daemon
processes
running on
RHEL
operating
systems.
Sys_SLESCronProcessMonitor BatchJobService Monitors

Cron
daemon
processes
running on
SLES
operating
systems.
Sys_ BatchJobService Monitors

SunSolarisCronProcessMonitor Cron
daemon
processes
running on
Sun Solaris
operating
systems.

User Guide
Policy
Descriptio
Sys_ DHCPServerServi Monitors

SunSolarisDHCPProcessMonitor ce DHCP
daemon
processes
running on
Sun Solaris
operating
systems.
Sys_ DNSService Monitors

SunSolarisNamedProcessMonitor Named
daemon
processes
running on
Sun Solaris
operating
systems.
Sys_SunSolarisNfsProcessMonitor FileServerService Monitors

NFS
processes
running on
Sun Solaris
operating
systems.
Sys_ EmailService Monitors

SunSolarisSendmailProcessMonitor the
Sendmail
daemon
processes
running on
Sun Solaris
operating
systems.
Sys_UnixSnmpdProcessMonitor NA Monitors
the SNMP
processes
running on
Linux and
Unix
operating
systems.

User Guide
Policy
Descriptio
Sys_DebianApacheProcessMonitor WebServerServic Monitors

e the Apache
processes
running on
Debian
operating
systems.
Sys_DebianCronProcessMonitor BatchJobService Monitors

the Cron
daemon
processes
running on
Debian
operating
systems.
Sys_DebianEximProcessMonitor EmailService Monitors

Exim
processes
running on
the Debian
operating
systems.
Sys_DebianInetdProcessMonitor NA Monitors
the Inetd
processes
running on
the Debian
operating
systems.
Sys_DebianNamedProcessMonitor DNSService Monitors

the Named
processes
running on
Debian
operating
systems.

User Guide
Policy
Descriptio

DebianNfsServerProcessMonitor the Nfs
processes
running on
Debian
operating
systems.
Sys_DebianNmbdProcessMonitor FileServerService Monitors

the Nmbd
processes
running on
Debian
operating
systems.
Sys_DebianSambaProcessMonitor FileServerService Monitors

the Samba
processes
running on
Debian
operating
systems.
Sys_DebianSshdProcessMonitor NA Monitors
the SSH
daemon
processes
running on
Debian
operating
systems.
Key System Services Availability
This Aspect monitors the key processes that run in the background to support the different tasks
required for the operating system or application. This Aspect monitors availability of following
processes and services:
l HPUX, Linux, Solaris: Syslog and SSH daemon (Sshd)
l AIX: Syslog

User Guide
l Windows: Event log, Fileserver, Network policy server, task scheduler and Windows Server 2003
(Win2k3) file services.
Policy
Indicato Descriptio
CI Type Policy Template r n Policy Type
Compute Sys_AIXSyslogProcessMonitor NA This policy Service/Proces

r template s Monitoring
monitors Template
the Syslog
processes
running on
AIX
operating
systems.
Sys_HPUXSshdProcessMonitor NA This policy

template
monitors
the SSH
daemon
processes
running on
HP-UX
operating
systems.
Sys_HPUXSyslogProcessMonitor NA This policy

template
monitors
the Syslog
daemon
processes
running on
HP-UX
operating
systems.

User Guide
Policy
Indicato Descriptio
Sys_LinuxSshdProcessMonitor NA This policy

template
monitors
the SSH
daemon
processes
running on
Linux
operating
systems
Sys_MSWindowsEventLogRoleMonitor NA This policy

template
monitors
the
availability
of system
services
required for
event log
role
service.
Sys_MSWindowsFileServerRoleMonitor NA This policy

template
monitors
the
availability
of system
services
required for
files server
role
service.

User Guide
Policy
Indicato Descriptio
Sys_ NA This policy

MSWindowsNetworkPolicyServerRoleMoni template
tor monitors
the
availability
of system
services
required for
network
policy
server role
service.
Sys_ NA This policy

MSWindowsTaskSchedulerRoleMonitor template
monitors
the
availability
of system
services
required for
task
scheduler
role
service.
Sys_ NA This policy

MSWindowsWin2k3FileServicesRoleMonit template
or monitors
the
availability
of system
services
required for
Win2k3
files
services
role
service.

User Guide
Policy
Indicato Descriptio
Sys_RHELSyslogProcessMonitor NA This policy

template
monitors
the Syslog
daemon
processes
running on
RHEL
operating
systems.
Sys_SLESSyslogProcessMonitor NA This policy

template
monitors
the Syslog
daemon
processes
running on
SLES
operating
systems.
Sys_SunSolarisSshdProcessMonitor NA This policy

template
monitors
the SSH
daemon
processes
running on
Sun Solaris
operating
systems.
Sys_SunSolarisSyslogProcessMonitor NA This policy

template
monitors
the system
log
processes
running on
Sun Solaris
operating
systems.

User Guide
Memory and Swap Utilization
The Memory and Swap Utilization Aspect monitors memory performance of the system. Memory
performance monitoring is based on Memory utilization (in percentage), Swap space utilization (in
percentage), Free memory available (in MBs), and Free swap space available (in MBs). This Aspect
consists of the following policy templates:
Policy
CI Type Policy Template Indicator Description Policy Type
Computer Sys_ MemoryUsageLevel Monitors the Measurement

MemoryUsageAndPerformance memory usage Threshold
of the system Template
and shows
error rates and
collisions to
identify
potential
memory
bottlenecks.
Sys_SwapCapacityMonitor SwapUsageLevel Monitors the

swap space
utilization of
the system.
Remote Disk Space Utilization
The Remote Disk Space Utilization Aspect monitors space utilization of remote disk. This Aspect
Policy
Descriptio
Computer, Sys_ NetworkFileShareUsageLev Monitors Measuremen

FileSyste LinuxCifsUtilizationMonit el space t Threshold
m or utilization Template
level for
CIFS
remote
filesystems
on Linux
platforms.

User Guide
Policy
Descriptio
Sys_ NetworkFileShareUsageLev Monitors

LinuxNfsUtilizationMonit el space
or utilization
level for
NFS
remote
filesystems
on Linux
platforms.
Resource Bottleneck Diagnosis
This Aspect identifies congestions and bottleneck conditions for system resources like the CPU,
memory, network, and disk. CPU bottleneck monitoring is based on global CPU utilization and load
average (Run Queue Length) Memory bottleneck monitoring is based on memory utilization, free
memory available, and memory swap out rate. Filesystem monitoring is based on space utilization
level for busiest filesystem on the node. Network monitoring is based on Packet collision rate, packet
error rate, and outbound queue length. This Aspect contains the following policy templates:
Policy
Computer Sys_CPUBottleneckDiagnosis CPULoad Detects CPU Measurement

bottlenecks such Threshold
as exceeding the Template
thresholds for
CPU utilization
percentage,
processor queue
length, and total
number of CPUs
running on an
operating
system.
For example, if
the threshold for
CPU utilization is
violated along
with threshold for
number of
processes in the

User Guide
Policy
queue waiting for

CPU time, the
policy sends an
alert. The
message also
displays a list of
the top ten CPU
utilization
processes.
Sys_DiskPeakUtilMonitor DiskUsageLevel Monitors the

utilization level of
the disk on the
system. It
checks whether
the utilization
level is full.
Sys_ MemoryLoad Monitors the

MemoryBottleneckDiagnosis physical memory
utilization and the
bottlenecks.
Memory
bottleneck
condition occurs
when the memory
utilization is high
and the available
memory is very
low. It causes the
system to slow
down affecting
overall
performance.
High memory
consumption
results in
excessive page
outs, high page
scan rate, swap-
out byte rate, and
page request
rate, eventually
slowing down the
system. The

User Guide
Policy
message also
displays a list of
top ten memory
utilization
processes.
Sys_ SESSION Monitors the

NetworkInterfaceErrorDiagnosis network usage of
the system and
checks for
potential network
bottlenecks or
errors.
Server Hardware Fault
This Aspect monitors the health and status of the HP ProLiant servers. These policies monitor the
Simple Network Management Protocol SNMP traps generated by the SIM Agent and send alert
messages to the HPOM console. All these policies are of the type SNMP Interceptor. This Aspect
Computer Sys_HPProLiant_ NA This policy intercepts SNMP Interceptor

BladeType2Traps SNMP traps related to Template
Blade Type 2.
Sys_HPProLiant_ NA This policy intercepts

CPQCLUSTraps SNMP traps related to
clusters in terms of
the state of the
battery, monitor, Hot
Plug Slot Board,
memory, and hood.

User Guide

CPQCMCTraps SNMP traps related to
the health of the
Console Management
Controller (CMC) in
terms of power
consumption, smoke,
humidity,
temperature, and fan.

CPQHLTHTraps SNMP traps related to
the health of the
server.

CPQNICTraps SNMP traps related to
the performance and
availability of the
Network Interface
Card (NIC).

CPQRackTraps SNMP traps related to
rack information in
terms of temperature,
power, and status.

CPQRCTraps SNMP traps related to
the performance and
availability of the
RAID Controller.

CPQRPMTraps SNMP traps related to
Rack Power Manager.

User Guide

CPQSSTraps SNMP traps related to
storage systems in
terms of fan status,
temperature, and
power supply.

CPQSysInfoTraps SNMP traps related to
system information in
terms of the state of
the battery, monitor,
Hot Plug Slot Board,
memory, and hood.

CPQUPSTraps SNMP traps related to
Uninterrupted Power
Supply (UPS) in terms
of status, battery, and
actions initiated by
UPS.

FwdDriveArrayTraps SNMP traps related to
Compaq’s Intelligent
Drive Array.

VCDomainTraps SNMP traps related to
virtual connect
domain.

VCModuleTraps the SNMP trap related
to virtual connect
module.
Space Availability and Disk IOPS
This Aspect monitors the disk IO operations and space utilization of the system. This Aspect consists
of the following policy template:

User Guide
Computer Sys_ DiskUsageLevel Monitors the Measurement

FileSystemUtilizationMonitor utilization of the file Threshold
systems on the Template
node.
System Infrastructure Discovery
This Aspect discovers and gathers information regarding the system resources, operating system, and
applications on a managed node. This Aspect contains the following policy templates:
Policy
CI Type Policy Template Indicator Policy Description Type
Computer OPC_PERL_ NA Is used for setting OPC_PERL_INCLUDE_ Node Info

INCLUDE_ INSTR_DIR in the HP Operations Agent Template
INSTR_DIR xpl config namespace. Set the value to
TRUE for Infrastructure SPI policies to
work.
Sys_ NA Gathers service information from the Service

SystemDiscovery managed nodes such as hardware Auto-
resources, operating system attributes, Discovery
and applications. Template
System Fault Analysis
This Aspect monitors the kernel log file, boot log file, and event log file for critical error conditions and
instructions. This Aspect contains the following policy templates:
Indicato Policy
CI Type Policy Template r Policy Description Type
Comput Sys_LinuxKernelLog NA This policy template monitors the kernel Logfile

er log file /var/log/ and alerts in case of Entry
any kernel service failure. It checks for Templat
error conditions that match the <*> e
kernel: <@.service>: <*.msg>
failed pattern in the kernel log file. If
any matches are found, this condition
sends an alert with minor severity.
Comput Sys_LinuxBootLog NA This policy template monitors the boot

er log file /var/log/boot.log and alerts
in case of any system boot errors. It

User Guide
Indicato Policy
checks for the following conditions:
l Service startup failed - Checks for

error conditions that match the <*>
<@.service>: <@.daemon>
startup failed pattern in the boot
log file. If any matches are found,
this condition sends an alert with
minor severity.
l Service failed - Checks for error

conditions that match the <*>
<@.service>: <*.msg> failed
pattern in the log file. If any matches
are found, this condition sends an
alert with critical severity.
Comput Sys_LinuxSecureLog NA This policy template alerts the user in

er case of any secure login failure. It
checks for the error conditions that
match the <*> sshd : Failed
password for <@.user> from
<*.host> port <#> ssh2 pattern. If
any matches are found, this condition
sends an alert with warning severity.
Comput Sys_AIXErrptLog NA This policy template monitors the errpt

er log file
/var/opt/OV/tmp/sispi/errpt.log
and generates an error report from
entries in an error log. It checks for error
conditions that match <@.errcode>
<2#.mo><2#.dd><2#.hh><2#.mm><2#.
yy> <@> <@> <@.object>
<*.msgtext> each column in the errpt
log file. If any matches are found, this
condition sends an alert with warning
severity.

User Guide
Indicato Policy
Comput Sys_ NA This policy template monitors the log Window

er MSWindowsServer_ file for the Microsoft DNS server s Event
DNSWarnError service and its corresponding process Log
and forwards the error log entries with a Templat
warning, or error severity. The policy e
looks for the following errors recorded in
the DNS log file:
l The DNS server could not allocate

memory for the resource record.
l The DNS server was unable to

service a client request due a
shortage of available memory.
l The DNS server could not create a

zone transfer thread.
l The DNS server encountered an

error while writing to a file.
l The DNS server could not initialize

the remote procedure call (RPC)
service.
Comput Sys_ NA This policy template monitors the

er MSWindowsServer_ DHCP event logs and forwards the
DHCPWarnError event log entries with warning, or error
severity. The policy looks for the
following errors:
l Iashlpr cannot contact the NPS

service.
l There are no IP addresses available

for BOOTP clients in the scope or
superscope.
l The DHCP server is unable to reach

the NPS server for determining the
client's NAP access state.
l There are no IP addresses available

for lease in the scope or
superscope.

User Guide
Indicato Policy
l The DHCP service failed to initialize

the audit log.
l The DHCP/BINL service on the

local computer has determined that
it is not authorized to start.
l The DHCP/BINL service on this

workgroup server has encountered
another server with IP Address.
l The DHCP service failed to restore

the DHCP registry configuration.
l The DHCP service was unable to

read the global BOOTP file name
from the registry.
l The DHCP service is not servicing

any clients because there are no
active interfaces.
l There is no static IP address bound

to the DHCP server.
l The DHCP Server service failed to

register with Service Controller.
l The DHCP Server service failed to

initialize its registry parameters.

User Guide
Indicato Policy
Comput Sys_ NA This policy template monitors the NFS

er MSWindowsServer_ event logs and forwards the event log
NFSWarnError entries with warning, or error severity.
The policy looks for the following errors:
l Server for NFS detected a low disk

space condition and has stopped
recording audits.
l The audit log has reached its

maximum file size.
l Server for NFS could not register

with RPC Port Mapper.
l The Server for NFS received a

failure from the NFS driver during
phase 2 initialization.
Comput Sys_ NA This policy template forwards the

er MSWindowsServer_ terminal service event logs entries with
TerminalServiceWarnEr warning, or error severity. The policy
ror looks for the following errors:
l A connection request was denied

because the terminal server is
currently configured to not accept
connections.
l Autoreconnect failed to reconnect

user to session because
authentication failed.
l Terminal Service start failed.
l The terminal server received large

number of incomplete connections.
Comput Sys_ NA This policy template monitors the

er MSWindowsServer_ Windows logon and initialization event
WindowsLogonWarnErr logs and forwards the error log entries
or with warning, or error severity. The
policy looks for the following errors
recorded in the Windows log file:
l Windows license is invalid.

User Guide
Indicato Policy
l Windows license activation failed.
l The Windows logon process has

failed to switch the desktop.

unexpectedly terminated.

failed to spawn a user application.

failed to terminate currently logged
on user's processes.

failed to disconnect the user
session.
User Logins
This Aspect checks the number of failed logins and last logins on your system. This Aspect consists of
the following policy templates:
Policy Policy
CI Type Policy Template Indicator Description Type
Computer Sys_ NA This policy Scheduled

MSWindowsFailedLoginsCollector checks for the Task
number of: Template
l Failed login
attempts on
Microsoft
Windows.
l Invalid logins,
either due to
unknown
username or
incorrect
password on
the managed
node.

User Guide
Policy Policy
n The policy
logs
individual
instances
of failed
login into
the GBL_
NUM_
FAILED_
LOGINS
metric in
EPC. By
default, the
time
interval is 1
hour.
Sys_ NA This policy

MSWindowsLastLogonsCollector template
performs the
following tasks:
l Checks for
the logon
details of all
the active
local user
accounts on
Microsoft
Windows.
l Logs
individual
instances of
user logon into
the
SECONDS_
SINCE_
LASTLOGIN
metric in
EPC. By
default, the
time interval is
1 hour.

User Guide
Policy Policy
Sys_UNIXFailedLoginsCollector NA This policy

checks for the
number of:
l Failed login
attempts on
RHEL and
SLES Linux
systems, HP-
UX, AIX, and
Solaris
operating
systems.
l Invalid logins,
either due to
unknown
username or
incorrect
password on
the managed
node.
n The
policies log
individual
instances
of failed
login into
the GBL_
NUM_
FAILED_
LOGINS
metric in
EPC. By
default, the
time
interval is 1
hour.
Sys_LinuxLastLogonsCollector NA This policy

checks for the
logon details of all
the active local
user accounts on
RHEL and SLES

User Guide
Policy Policy
Linux operating
systems. The
policy logs
individual
instances of user
logon into the
SECONDS_
SINCE_
LASTLOGIN
metric in EPC. By
default, the time
interval is 1 hour.
Note: You must have the following pre-requisites for the Sys_UNIXFailedLoginsCollector
policy to function correctly when deployed on the Solaris node:
l Set the following variables in /etc/default/login file
SYSLOG=YES
SYSLOG_FAILED_LOGINS=1
l In /etc/syslog.conf file, check if the following line is present:
auth.notice ifdef(LOGHOST', /var/log/authlog, @loghost)
l Refresh syslogd using the following command:
svcadm refresh system/system-log
Sys_UNIXFailedLoginsCollector policy is deployed in the following paths:
On Solaris nodes: /var/log/authlog
On Linux nodes: lastb command
On HP-UX nodes: lastb command
On AIX nodes: /etc/security/failedlogin log
Virtualization Infrastructure Aspects

Virtualization Infrastructure Aspects monitors the resource usage and availability of host, guests or
virtual machines. It includes the virtualization discovery which discovers all the elements in a
virtualized environment. It ensures the environment is healthy and available. Virtualization
Infrastructure Aspects monitor the VMware VirtualCenter CI types.

User Guide

General Provides an overview of the general attributes of the Virtualization
Infrastructure Aspects.
which is assigned to the Management Template. The Virtualization
Infrastructure Aspects contain the Computer CI types.

contains the Aspect.
Aspects Provides an overview of any Aspects that contain the Virtualization

details about the nested aspect.
Policy Templates Provides an overview of the policy templates that contain the Virtualization
The Virtualization Infrastructure Aspects consists of the following:
IBM Power Guest Health
The IBM Power Guest Health Aspect monitors Guest availability in a Virtualized IBM LPAR
Environment. This Aspect consists of the following policy templates:
Policy
Computer Virt_ NodeStatus Monitors the Measurement

IBMFrameAndLPARStateMonitor IBM Frames Threshold
and LPAR Template
states.
Virt_IBMWPARStateMonitor NodeStatus Monitors and

reports on the
state of IBM
WPARs.
Note: Before deploying Virt_IBMFrameAndLPARStateMonitor policy, run the

getSSHAuthentication.pl script to connect to the HMC. This script is located under the
/var/opt/OV/bin/instrumentation directory on the node (frame). The getSSHAuthentication.pl
script provides you password-less access to the configuration information on the HMC.

User Guide
IBM Power Guest Performance
The IBM Power Guest Performance Aspect monitors Guest performance in a Virtualized IBM LPAR
Environment. This Aspect consists of the following policy templates:
Policy
Computer Virt_IBMLPARCpuEntlUtilMonitor- CPULoad Calculates the Measurement

AT current CPU Threshold
utilization (in Template
percentage) of
AIX LPARs. It
indicates the
logical system’s
CPU utilization
against the
minimum entitled
CPU. Entitled
CPU is the
number of
guaranteed
processing units
allocated to a
logical system.
Virt_ MEMLoad Calculates the

IBMLPARMemoryEntlUtilMonitor- current memory
AT utilization (in
percentage) of all
IBM LPARs on
AIX in ACTIVE
state. It indicates
the LPARs
memory
utilization against
the minimum
entitled memory.

User Guide
Policy
Virt_ CPULoad Calculates the

IBMWPARCpuEntlUtilMonitor-AT current CPU
utilization (in
percentage) of
AIX WPARs. It
indicates the
logical system’s
CPU utilization
against the
minimum entitled
CPU. Entitled
CPU is the
number of
guaranteed
processing units
allocated to a
logical system.
Virt_ MEMLoad Calculates the

IBMWPARMemoryEntlUtilMonitor- current memory
AT utilization (in
percentage) of
IBM WPARs
(running on the
monitoring LPAR)
in ACTIVE state.
It indicates the
WPARs memory
utilization against
the minimum
entitled memory.
IBM Power Host Health
The IBM Power Host Health Aspect monitors Frame memory and CPU Utilization in a Virtualized IBM
LPAR environment. This Aspect consists of the following policy templates:

User Guide
CI Policy
Type Policy Template Indicator Description Policy Type
IBM Virt_ CPULoad Monitors the Measurement

Frame IBMLPARFrameCPUUtilMonitor LPAR Frame Threshold
CPU Template
utilization for
IBM LPAR
virtual
infrastructure.
Virt_ MemoryLoad Monitors the

IBMLPARFrameMemoryUtilMonitor LPAR Frame
Memory
utilization for
IBM LPAR
Frame virtual
infrastructure.
KVM Guest Health
The KVM Guest Health Aspect monitors the guest availability and resources in a virtualized KVM
environment. This Aspect consists of the following policy templates:
Computer Virt_LinuxHV_ CPULoad Monitors the Measurement

(Virtualization GuestCPUUtilMonitor CPU utilization of VMs Threshold
Layer within a host. The CPU Template
Software) utilization of each VM is
checked against the
threshold limits. In case
of any violation, alerts
are raised with the list of
VMs on that host.
Virt_LinuxHV_ NodeStatus Monitors and evaluates

StateMonitor the KVM and Xen logical
system which has any
one of the states such as
nostate, running,
run/idle, paused,
shutdown, crashed,
and shut off.

User Guide
KVM Guest Performance
The KVM Guest Performance Aspect monitors the guest performance in a virtualized KVM
Policy
Computer Virt_LinuxHV_ InterfaceUtilization Uses an Measurement

(Virtualization DiskPhysByteRateBaseline- instance Threshold
Layer AT baseline for Template
Software) monitoring the
average
number of
bytes
transferred per
second from
and to the
physical disk.
Virt_LinuxHV_ CPULoad Uses the

GuestCPUTotalUtilMonitor- multi-instance
AT baseline for
monitoring the
total CPU
utilization of
the guest
machines.
Virt_LinuxHV_ InterfaceUtilization Uses the

NetByteRateBaseline-AT instance
baseline for
monitoring the
net byte rate.
KVM Host Health
The KVM Host Health Aspect monitors the host resource utilization in a virtualized KVM environment.

User Guide
Computer Virt_LinuxHV_ CPULoad This policy template Measurement

HostCPUUtilMonitor monitors the host Threshold
CPU utilization for Template
KVM and Xen
systems in a
virtualized
environment.
Virt_LinuxHV_ MemoryUsageLevel This policy template

HostMemoryUtilMonitor monitors the host
physical memory
utilization for
KVM and Xen
systems in a
virtualized
environment.
Oracle Solaris Guest Health
The Oracle Solaris Guest Health Aspect monitors guest resources in Oracle Solaris zones
environment. This Aspect consists of the following policy template:
CI
Type Policy Template Indicator Policy Description Policy Type
Unix Virt_ NodeStatus Checks the logical system Measurement

OracleSolarisStateMonitor state and raises an alert for Threshold
Oracle Solaris containers. Template
Oracle Solaris Guest Performance
The Oracle Solaris Guest Performance Aspect monitors guest Performance in a virtualized Oracle
Solaris environment. This Aspect consists of the following policy templates:
CI Policy
Typ Descripti Policy
e Policy Template Indicator on Type
Uni Virt_ MemoryEntitlementUsageL Calculates Measureme

x OracleSolarisMemoryEntlUtilMonit evel the current nt
or-AT memory Threshold
utilization Template
(in

User Guide
CI Policy
percentag
e) of all
Solaris
zones in
RUNNIN
G state. It
indicates
the zone’s
memory
utilization
against the
minimum
entitled
memory.
Virt_ CPUEntitlementUsageLeve Calculates

OracleSolarisZoneCPUEntlUtilMo l the current
nitor-AT CPU
utilization
(in
percentag
e) of
Solaris
zones. It
indicates
the logical
system’s
CPU
utilization
against the
minimum
entitled
CPU.
Entitled
CPU is the
number of
guarantee
d
processing
units
allocated
to a logical
system.

User Guide
CI Policy
Virt_ SwapUsageLevel Monitors

OracleSolarisZoneSwapUtilMonito the swap
r-AT utilization
on Solaris
zones.
Oracle Solaris Host Health
The Oracle Solaris Host Health Aspect monitors the host resource utilization in a virtualized Oracle
Solaris zones environment. This Aspect consists of the following policy templates:
CI Policy
Unix Virt_ CPULoad Monitors the Measurement

OracleSolarisHostCPUUtilMonitor CPU Threshold
utilization on Template
the host
servers for
Solaris
zones.
Virt_ MemoryUsageLevel Monitors the

OracleSolarisHostMemoryUtilMonitor physical
memory
utilization on
Oracle
Solaris
zones.
Virt_ This policy

OracleSolarisFmdProcessMonitor template
monitors the
fault
manager
daemon
(fmd) running
on Solaris
zones.

User Guide
CI Policy
Virt_ This policy

OracleSolarisRcapdProcessMonitor template
monitors the
resource
capping
daemon
(rcapd)
running on
Solaris
zones.
Virt_PerfAgentProcessMonitor This policy

template
monitors the
performance
agent
processes
running on
the nodes.
VMware Cluster Performance
The VMware Cluster Performance Aspect monitors the CPU and memory utilization for VMware
clusters. This Aspect consists of the following policy templates:
Policy
Descripti Policy
CI Type Policy Template Indicator on Type
VMware Virt_ CPUUsageLevel Monitors Measurem

VirtualCen VMwareVCClusterCPUPerformanceMo the CPU ent
ter nitor Utilization Threshold
at the Template
VMware
cluster
level.
CPU
utilization
of cluster
can be
high if:
a) The
CPU

User Guide
Policy
Descripti Policy
utilization
of the
hosts in a
cluster is
constantly
high.
b) The
cluster
cannot
perform
vMotion to
maximize
the
hardware
utilization
when the
cluster
hosts are
in a
saturated
state.
Virt_ MemoryUsageL Monitors

VMwareVCClusterMemoryPerformance evel the
Monitor memory
utilization
at the
VMware
cluster
level.
Memory
utilization
of cluster
can be
high if:
a) The
Memory
Utilization
of the
hosts in a
cluster is
constantly
high.

User Guide
Policy
Descripti Policy
b) The
cluster
cannot
perform
vMotion to
maximize
the
hardware
utilization
if the
cluster
hosts are
in a
saturated
state.
VMware Datastore Performance
The VMware Datastore Performance Aspect monitors the utilization of datastore in a VMware vSphere
environment. This Aspect consists of the following policy template:
Policy Policy
VMware Virt_ Datastor Monitors the Measureme

VirtualCent VMwareVCDatastoreSpaceUtilizationM e_ space utilization nt
er onitor Utilizatio of each VMware Threshold
n datastore. Template
Space
utilization of
datastore can
be high due to
one of the
following
reasons.
l Snapshots:
Snapshot
files store
information
about virtual
machine
snapshots.

User Guide
Policy Policy
l Other VM
files:
Additional
files used by
all other files
associated
with a virtual
machine,
such as the
.vmx
configuration
file and log
files.
l Other: All
other non-
managed
files placed
on the
datastore,
such as
documentati
on, backups,
and ISO or
Floppy
images.
l Virtual
Disks:
Virtual disk
files store
the contents
of the virtual
machines
hard disk
drive.
VMware Host Health
The VMware Host Health Aspect monitors the host resource utilization in a virtualized VMware

User Guide
Policy
VMware Virt_ CPULoad Monitors the Measurement

ESX VMwareVCHostCPUSaturationMonitor consumption Threshold
server of host CPUs Template
by virtual
machines.
This policy
also monitors
the increased
CPU time of
VMs within a
host.
Virt_VMwareVCHostCPUUtilMonitor CPULoad Monitors the

CPU utilization
for ESX or
ESX/i host.
Virt_VMwareVCHostMemUtilMonitor MemoryLoad Monitors the

host memory
pressure on
Esx/i host in a
VMware
environment.
The factors
affecting the
host machines
memory are
memory over
commitment,
high memory
reservations,
high swap outs
and ballooning
in the VMs,
and number of
virtual
machines
running on the
host machine.
VMware Resource Pool Monitor
The VMware Resource Pool Monitor Aspect monitors CPU utilization levels for VMware resource
pools. This Aspect consists of the following policy template:

User Guide
Policy
VMware Virt_ CPULoad Monitors the Measurement

VirtualCenter VMwareVCRespoolCPUUtilMonitor CPU Threshold
utilization of Template
resource pool.
High CPU
utilization
creates
performance
problems at
virtual
machines.
The alert
message lists
the virtual
machines that
use a
significant
amount of the
CPU
resource.
VMware Guest Health
The VMware Guest Health Aspect monitors the guest availability and resources in a virtualized
VMware environment. This Aspect consists of the following policy templates:
Policy
Descriptio
Compute Virt_VMWareVCGuestStateMonitor NodeStatus Monitors Measureme

r the state of nt Threshold
VMware Template
logical
system. It
raises an
alert if the
VM is in
On, Off,
Suspende
d, or
Unknown
state.

User Guide
Policy
Descriptio
Virt_ CPULoad Monitors

VMwareVCGuestCPUPerformanceMonitor the CPU
utilization
of the guest
systems
and sends
an alert
message in
case the
performanc
e level goes
below the
set
threshold.
Virt_VMwareVCGuestLatencyMonitor NA Monitors
the read or
write
latency of a
guest
leading to
reduced
performanc
e of a
virtual
machine.
An alert is
raised if the
read or
write
latency is
greater than
the warning
threshold.

User Guide
Policy
Descriptio
Virt_ MemoryLoa Monitors

VMwareVCGuestMemoryPerformanceMoni d the memory
tor performanc
e of the
guest
systems.
High
memory
utilization
for a long
period of
time or high
memory
swap and
balloon
utilization
can impact
the
performanc
e of virtual
machines.
VMware vSphere Events
The VMware vSphere Events Aspect notifies when critical events are raised from VMware vSphere
Policy
VMware Virt_ VMRemoval Monitors the Measurement

VirtualCenter VMwareVCEventMonitor events from Threshold
ESX vCenter Template
server.
Virt_ NA Monitors Config File

VMwareVCEventTypes specific events Template
of interest by
adding or
removing the
event types.

User Guide
Virtual Infrastructure Discovery
The Virtual Infrastructure Discovery Aspect discovers the virtual components like hypervisor host,
guest, and resource pool in a virtualization environment. This Aspect consists of the following policy
template:
Policy Policy
CI Type Template Indicator Policy Description Type
Computer Virt_ NA Discovers the virtual infrastructure Service

Discovery components like hypervisor host, guest, Auto-
and resource pool in a virtualization Discovery
environment. Template
Xen Guest Health
The XEN Guest Health Aspect monitors the guest availability and resources in a virtualized XEN
Computer Virt_LinuxHV_ CPULoad Monitors the Measurement

(Virtualization GuestCPUUtilMonitor CPU utilization of VMs Threshold
Layer within a host. The CPU Template
Software) utilization of each VM is
checked against the
threshold limits. In case of
any violation, alerts are
raised with the list of VMs
on that host.
Virt_LinuxHV_ NodeStatus Monitors and evaluates the

StateMonitor KVM and Xen logical
system which has any one
of the states such as
nostate, running,
run/idle, paused,
shutdown, crashed, or
shut off. An alert is raised
only if the VM is in the
same transient state for
more than 30 minutes.

User Guide
Xen Guest Performance
The XEN Guest Performance Aspect monitors the guest performance in a virtualized XEN
Policy
Computer Virt_LinuxHV_ InterfaceUtilization Uses an Measurement

(Virtualization DiskPhysByteRateBaseline- instance Threshold
Layer AT baseline for Template
Software) monitoring the
average
number of
bytes
transferred per
second from
and to the
physical disk
for KVM or
XEN.
Virt_LinuxHV_ CPULoad Uses the multi-

GuestCPUTotalUtilMonitor- instance
AT baseline for
monitoring the
total CPU
utilization of
the guest
machines for
KVM or XEN.
Virt_LinuxHV_ InterfaceUtilization Uses an

NetByteRateBaseline-AT instance
baseline for
monitoring the
net byte rate
for KVM or
XEN.
Xen Host Health
The XEN Host Health Aspect monitors the host resource utilization in a virtualized XEN environment.

User Guide
Computer Virt_LinuxHV_ CPULoad Monitors the host Measurement

HostCPUUtilMonitor CPU utilization for Threshold
KVM and Xen Template
systems in a
virtualized
environment. The
CPU bottleneck
symptom is indicated
by high CPU
utilization rate in the
host system.
Virt_LinuxHV_ MemoryUsageLevel Monitors the physical

HostMemoryUtilMonitor memory utilization of
hosts in Linux
virtualization
environment. The
memory bottleneck
symptom is indicated
by high memory
utilization rate along
with low available
memory.
Cluster Infrastructure Aspects
Cluster Infrastructure Aspects discovers the high availability components such as cluster nodes and
resource pool availability in a clustered environment. It is used to monitor the single point of failure
(SPOF), quorum conditions, and node strength in a clustered environment. Cluster Infrastructure
Aspects monitor the FailoverCluster CI types.

General Provides an overview of the general attributes of the Cluster Infrastructure
Aspects.
which is assigned to the Management Template. The Cluster Infrastructure
Aspects contain the FailoverCluster CI types.

contains the Aspect.

User Guide
Aspects Provides an overview of any Aspects that contain the Cluster Infrastructure
Aspects. You can expand each item in the list to see more details about the
nested Aspect.
Policy Templates Provides an overview of the policy templates that contain the Cluster
Infrastructure Aspects. You can expand each item in the list to see more
The Cluster Infrastructure Aspects consists of the following:
Cluster Infrastructure Discovery
This Aspect discovers the high availability components such as cluster nodes and resource pool
availability in a clustered environment. This Aspect consists of the following policy template:
Policy
CI Type Policy Template Indicator Policy Description Type
Computer Clus_ NA Discovers the high availability Service

ClusterDiscovery infrastructure components such as cluster Auto-
nodes and resource groups in a clustered Discovery
environment. Template
Cluster Strength and Status
This Aspect monitors the single point of failure (SPOF), quorum conditions, and node strength in a
clustered environment. This Aspect consists of the following policy templates:
Policy
Descriptio
FailoverClust Clus_ NA Collects the Scheduled

er ClusterDataCollector availability Task
or state Template
data of a
cluster and
logs into
embedded
performanc
e
component
(CODA).
This policy
template is
scheduled

User Guide
Policy
Descriptio
to run every
5 minutes.
Clus_ClusterMonitor ClusterStrength Monitors Measureme

the single nt Threshold
point of Template
failure
(SPOF),
quorum
conditions,
and node
strength in a
clustered
environmen
t. A single
point of
failure alert
is raised
when a
single node
is active
and all other
nodes are
inactive in a
cluster.
This is a
risk in a
high
availability
environmen
t. If the
number of
inactive
nodes is
greater than
the number
of defined
nodes in a
cluster, the
quorum
value is not
met and an
alert is
raised.

User Guide
Policy
Descriptio
Clus_ NodeStatus Monitors

ClusterNodeMonitor the status
of a node in
a clustered
environmen
t. An alert is
raised when
a failure is
detected on
the node in
a cluster.
Clus_ ClusterResourceGroupStat Monitors

ClusterResGroupMonit us the state
or and
availability
of resource
groups in a
cluster. An
alert is
raised when
a failure is
detected on
the
resource
group in a
cluster
environmen
t. The
resource
group
cannot
provide its
services
unless it is
resumed
back again.
Parameters
Parameters are variables that are integral components of Infrastructure Management Templates,
Infrastructure Aspects, and Policy Templates. Each parameter corresponds to a variable. Parameters

User Guide
contain default values that are used for monitoring the different components of Infrastructure systems.
You can modify the values of the variables to suit your monitoring requirements.
Types of Parameters
OMi MP for Infrastructure parameters are grouped as follows:
l Simple Parameter: A simple parameter has a name and a value.
l Instance Parameter: An instance parameter has a name and a list of instance values.
Parameter Flags
l Mandatory: It is required during the assignment of a template to a CI.
l ReadOnly: The parameter cannot be modified while combining or assigning parameters.
l Hidden: This parameter will not be visible during the assignment or combining of parameters.
l Expert: By default, expert parameters are not shown during assignment. This must be explicitly
enabled by clicking Show Expert Parameters.
Infrastructure Parameters
The following table contains the list of parameters:
Parameter Default
Parameter Type Description Values
Avg Bytes Transferred Mandatory Set the threshold value for the average 5000
Per Sec from this bytes transferred per second at which you
interface want to receive a Major severity message.
Set the threshold value for the average 4500

bytes transferred per second at which you
want to receive a Minor severity message.
Set the threshold value for the average 4000

bytes transferred per second at which you
want to receive a Warning severity
message.

User Guide
Parameter Default
Outbound Queue Mandatory Indicates the number of packets waiting in 5

Length the outbound queue length for all network
interfaces.
Set the threshold value for outbound queue

length at which you want to receive a Major
severity message.
Set the threshold value for outbound queue 1

length at which you want to receive a
Warning severity message.
Set the threshold value for outbound queue 3

length at which you want to receive a Minor
severity message.
Bandwidth Used (%) Mandatory Indicates the percentage of bandwidth used 85

with respect to the total available
bandwidth.
Set the threshold value for bandwidth

utilization at which you want to receive a
Major severity message.
Set the threshold value for bandwidth 50

Set the threshold value for bandwidth 70

Minor severity message.
Memory Utilization (%) Mandatory Indicates the Memory utilization for the IBM 65525
LPAR Frame virtual infrastructure.
Set the threshold value at which you want to

receive a Critical severity message.
Set the threshold value at which you want to 96

receive a Major severity message.

receive a Minor severity message.

receive a Warning severity message.

User Guide
Parameter Default
CPU Utilization (%) Mandatory Indicates the CPU utilization for IBM LPAR 65525
Frame virtual infrastructure.




Memory Utilization (%) Mandatory Indicates the physical memory utilization for 65525
Oracle Solaris zones.




CPU Utilization (%) Mandatory Indicates the CPU utilization for Oracle 65525
Solaris zones.




Free memory available Mandatory Indicates the available memory for Oracle 65525
(MB) Solaris zones.


User Guide
Parameter Default



Message Group Mandatory Indicates the Message group for outgoing OS or

+ Expert messages. Virtualization
Setting or HA Cluster
CPU Utilization Level Mandatory Set the threshold value for global CPU 65535
(%) utilization level at which you want to receive
a Critical severity message.
Set the threshold value for global CPU 95

utilization level at which you want to receive
a Major severity message.

a Warning severity message.

a Minor severity message.
CPU Utilization Level Mandatory Indicates the CPU utilization during a CPU 65535
(%) Spike.




CPU Utilization Level Mandatory Set the threshold value for CPU utilization 65535
In User Mode (%) level in user mode at which you want to

User Guide
Parameter Default
CPU Utilization Level Mandatory Set the threshold value for CPU utilization 65535
In System Mode (%) level in system mode at which you want to
Set the threshold value for CPU utilization 35

level in system mode at which you want to


Rate of Interrupts (%) Mandatory Set the threshold value for the CPU 200, 180, 160
interrupt rate at which you want to receive a
Major, Warning or Minor severity message.
The threshold is expressed as the average
number of device interrupts per second for
the CPU during the sampling interval.
Number of free page Mandatory Set the threshold value for the number of -1
table entries available free page table entries available on the
on the system system at which you want to receive a
Critical severity message.
The Number of free page table entries

available on the system parameter is
applicable only to Windows OS.



Memory Utilization (%) Mandatory Set the threshold value for the memory 65535
Critical severity message.
Set the threshold value for the memory 98

Major severity message.

User Guide
Parameter Default


Free Memory Mandatory Set the threshold value for minimum 4, 10, 1064
Available (MB) memory available on the node at which you
want to receive a Major, Warning, or Minor
severity message. This parameter is
applicable only to Windows OS.
Memory Utilization (%) Mandatory Set the threshold value for minimum 65535
memory utilized on the node at which you
want to receive a Critical severity message.
Set the threshold value for minimum 98

want to receive a Major severity message.

message.

Swap Space Mandatory Set the threshold value for the swap space 65535
Utilization (%) utilized on the node at which you want to
Set the threshold value for the swap space 75

utilized on the node at which you want to



User Guide
Parameter Default
NFS space utilization Mandatory Monitors the disk utilization on remote 65535
filesystems (NFS).
Set the threshold value for the NFS space

utilized on remote filesystems at which you
Set the threshold value for the NFS space 95



message.
CIFS space utilization Mandatory Monitors disk utilization on remote 65535

filesystems (CIFS).
Set the threshold value for the CIFS disk




message.
Free Swap Space Mandatory Set the threshold value for free swap space 32
Available (in Mbs) available on the disk/filesystem at which
you want to receive a Critical severity
message.
Set the threshold value for free swap space 48

available on the disk/filesystem at which
you want to receive a Major severity
message.

User Guide
Parameter Default

you want to receive a Minor severity
message.

you want to receive a Warning severity
message.
CIFS Space Mandatory Indicates the percentage (0 to 100%) of 65535

Utilization (%) space utilization on the monitored remote
filesystem.
Set the threshold value for minimum free

space on the filesystem at which you want
to receive a Critical severity message.
Set the threshold value for minimum free 95

to receive a Major severity message.

to receive a Minor severity message.

to receive a Warning severity message.
CIFS FileSystem Mandatory Indicates the filesystem type that you would cifs
Type like to monitor for space utilization level.
For example, if you specify cifs, the policy

will monitor all CIFS remote filesystems for
space utilization level.
NFS FileSystem Type Mandatory Indicates the filesystem type that you would nfs
+ Expert like to monitor for space utilization level. For
Setting example, if you specify nfs, the policy will
monitor all NFS remote filesystems for
space utilization level.

User Guide
Parameter Default
NFS Space Utilization Mandatory The threshold is expressed as the 65535

(%) percentage (0 to 100%) of space utilization
on the monitored remote filesystem.
Set the threshold value for minimum free

to receive a Critical severity message.

to receive a Major severity message.

to receive a Minor severity message.

to receive a Warning severity message.
Summarized CPU Mandatory Monitors the global CPU utilization level in a 65535
Utilization (%) CPU Bottleneck situation.




Logical drive/fs Space Mandatory Indicates the space utilization for the logical 65535
Utilization drive or filesystem.





User Guide
Parameter Default
Space Utilization for Mandatory Set the threshold value for the utilization of 95, 90, 85
Busiest Disk/FS (%) the busiest disk or filesystem at which you
severity message.
Free Memory Mandatory Set the threshold value for free physical 4,10,1064
Available (MB) memory (in MBs) available on the disk or
filesystem at which you want to receive a
Major, Warning, or Minor severity message.
Memory Page Out Mandatory Set the threshold value for total number of 400, 40, 0
Rate (Pages Swapped pages swapped out from the physical
Out/sec) memory to the disk per second at which you
severity message.
Average number of Mandatory A page-in refers to an event when pages 65535

page-ins from disk per (memory) are written to the disk. This
second parameter monitors the total number of
page-ins from disk per second.

receive a Critical alert.

receive a Major alert.

receive a Minor alert.

receive a Warning alert.
Memory Page Mandatory Set the threshold value for the number of 100
Request Rate (Pages page requests from disk per second.
Requested/sec)
Memory Cache Flush Mandatory Set the threshold value for the rate at which 100
Rate (Data the file system cache flushes its contents to
Flushes/sec) disk.
Disk Instance Mandatory Set the threshold value for space utilization 65535
at which you want to receive the Critical
severity message.
Set the threshold value for space utilization 95

at which you want to receive the Major
severity message.

User Guide
Parameter Default

at which you want to receive the Warning
severity message.

at which you want to receive the Minor
severity message.
DiskPeakUtil Mandatory Monitors utilization level of fullest disk on 65535

system.
Set the threshold value for space utilization

at which you want to receive the Critical
severity message.

at which you want to receive the Major
severity message.

at which you want to receive the Warning
severity message.

at which you want to receive the Minor
severity message.
Ratio of collision Mandatory Monitors the ratio of collision packets to 5

packets to total total packets transmitted out of NIC.
packets transmitted
Set the threshold value for collision packets
out of this NIC
that are transmitted out of NIC at which you
want to receive the Major severity
message.
Set the threshold value for collision packets 3

want to receive the Minor severity
message.

want to receive the Warning severity
message.

User Guide
Parameter Default
Ratio of error packets Mandatory Monitors the ratio of error packets that are 5
to total packets transmitted to and from an NIC.
transmitted in and out
Set the threshold value for collision packets
of this NIC
want to receive the Major severity
message.

want to receive the Minor severity
message.

want to receive the Warning severity
message.
Free Space (MB) on Mandatory Indicates the free space available (in MBs) -1
device/filesystem on the disk or filesystem.




Space Utilization (%) Mandatory Set the threshold value for the space 95, 90, 85
utilized on the disk or filesystem at which
you want to receive a Major, Warning, or
VM CPU Utilization Mandatory Set the threshold value for the CPU 95, 90, 85
(%) Utilization of a virtual machine at which you
severity message.
Alert On Planned Mandatory Set the value to True or hh:mm:ss- False

Outage + Expert hh:mm:ss format, if you want to receive
Setting alerts for time-bound alerting. By default,
the value is set to False.

User Guide
Parameter Default
Host CPU Utilization Mandatory Set the threshold value for the 95, 90, 85
(%) CPU utilization of a host at which you want
to receive a Major, Warning, or Minor
severity message.
Host Memory Mandatory Set the threshold value for the 95, 90, 85
Utilization (%) memory utilization of a host at which you
severity message.
Host Free Memory Mandatory Set the threshold value for the free memory 50, 200, 1024
Available Thresholds available of a host at which you want to
(MB) receive a Major, Warning, or Minor severity
message.
Enable Trend Based Mandatory Set TrendingCheckFlag to On, if you want to off
monitoring enable trend based monitoring else set to
Off state.
Cluster CPU Mandatory Set the threshold value for the CPU 90, 80, 70
Utilization Thresholds utilization of a cluster at which you want to
receive a Major, Warning, or Minor severity
message.
Cluster Memory Mandatory Set the threshold value for the memory 90, 80, 70
Utilization Thresholds utilization of a cluster at which you want to
message.
Data Store Utilization Mandatory Set the threshold value for the datastore 90, 85, 80
(%) (disk space) utilization at which you want to
message.
VM CPU Utilization Mandatory Set the threshold value for the logical ready 90, 80, 70
Thresholds utilization of a virtual machine at which you
severity message.
Disk Read Latency for Mandatory Set the threshold value for the disk read 50, 25, 15
a Guest latency of a guest at which you want to
message.
Disk Write Latency for Mandatory Set the threshold value for the disk write 50, 25, 15
a Guest latency of a guest at which you want to
message.

User Guide
Parameter Default
VM Memory Utilization Mandatory Set the threshold value for the memory 90, 80, 70
Thresholds utilization of a virtual machine at which you
severity message.
Respool CPU Mandatory Set threshold value for the CPU utilization 95, 90, 85
Utilization (%) of a resource pool at which you want to
message.
Tuning of Parameters
You can edit the parameters of the Management Templates that are deployed to the CIs.
To edit the parameters:
1. Open the Assignments & Tuning pane:
Tuning.
2. In the Browse Views tab, select the view that contains the CI for which you want to tune
parameters. Alternatively, you can use the Search tab to find a CI.
3. In the list of CIs, select a CI. The Assignments pane shows details of any existing assignments
for the CI.
4. Click the assignment for which you want to tune parameters. The Details of Assignment pane
shows the current parameter values.
5. In the Details of Assignment pane, change the parameters:
a. (Optional). By default, the list shows only mandatory parameters. To see all parameters, click
.
b. Select a parameter in the list, and then click .
o For standard parameters, the Edit Parameter dialog box opens.
o For instance parameters, the Edit Instance Parameter dialog box opens.

User Guide
Change the instance values if necessary, and then for each instance value, change
dependent parameter values. After you change the instances and dependent parameter
values, click OK.
6. In the Details of Assignment pane, click Save Changes. Operations Management deploys the
new parameter values to the relevant HP Operations agent.
Configuration Items and Configuration Item Types

Configuration Item (CI) is a component that needs to be managed to deliver an IT Service.
Infrastructure CIs includes IT Services, hardware, software and so on. A Configuration Item Type (CIT)
describes the type of CI and its attributes. Infrastructure CIT includes Computer, VMware
VirtualCenter, Unix, FailoverCluster and so on. For a list of CITs used in OMi MP for Infrastructure, see
the section CI Types Mapped in OMi.
CI Types Mapped in OMi

The following table lists the CITs from HP Operations Manager (HPOM) that are mapped to the RTSM
database in OMi using the OMi MP for Infrastructure.
Package CI Type
HPOprVir Node
Computer
UNIX
Windows
VMware ESX server
VMware Cluster
VMware Resource Pool
VMware Virtual Center
VMware Datastore
Datacenter
Hypervisor
IBM Frame
IBM HMC

User Guide
Package CI Type
HPOprSys FileSystem
Disk Devices
HPOprClu Cluster Software
Failover Cluster
Clustered Resource Group
mscluster
serviceguardcluster
veritascluster
Run Time Service Model (RTSM) Views

A View enables you to visualize the context of an event. A typical View shows a subset of
Infrastructure CIs and their relationships with other neighboring CIs. Using the Views, you can
visualize the topology of an Infrastructure environment. In addition, Views can be used to do the
following:
l Manage the Event Perspective of Infrastructure CIs
l Manage the Health Perspective of Infrastructure CIs
l Assign and Tune the Management Templates, Aspects, and Policy Templates
How to Access the RTSM Views

1. Open the Modeling Studio pane:
On BSM 9.2x, click Admin > RTSM Administration > Modeling > Modeling Studio.
On OMi 10.x, click Administration > RTSM Administration > Modeling > Modeling Studio.
2. Go to the Resources tab. Select Views in the Resource Type drop down.
3. Select Operations Management > Infrastructure.
The OMi MP for Infrastructure contains the following views:

User Guide
l CPU_Infrastructure: This view shows the CPU and Computer CI types in a pictorial format.
l Filesystem_Infrastructure: This view shows the File System and Computer CI types in a pictorial
format.

User Guide
l HACluster_Infrastructure: This view shows the Computer (Windows or UNIX), Cluster Software,
Clustered Server, Failover Cluster, Software Element, and IP Address CI types in a pictorial
format.

User Guide
l Infrastructure_Common: This view represents a combined view for the HACluster_Infrastructure,

Systems_Infrastructure, and Virtualization_Infrastructure views.
Note: CPUs and disk devices are shown only for virtualization servers.

User Guide
l KVM_Infrastructure: This view shows the KVM host, hypervisor, and domains in a pictorial format.

User Guide
l NetworkInterface_Infrastructure: This view shows the Network Interface and Computer CI types
in a pictorial format.
l Systems_Infrastructure: This view shows the relationship between the Computer (Windows or
UNIX), CPU, File System, Network Interface, and IP Address CI types in a pictorial format.
l VA_Infrastructure: This view shows the Proxy Node, Operations Agent and relation between
Proxy Node to VMware VirtualCenter, ESX servers, and Virtual machines in a pictorial format.

User Guide
l Virtualization_Infrastructure: This view displays the Computer and Hypervisor CI types. The
following image shows the relationship between the CI types in a pictorial format.

User Guide
l vMA_Infrastructure: This view displays the vMA, virtual management software and relation
between vMA and virtual machines. vMA collects the data for hosts and virtual machines in a
pictorial format.

User Guide
l NNMi_Layer2: This view displays layer 2 connectivity between servers and the switches or routers
to which they are connected. The view also shows connectivity between the network switches and
routers.
l Xen_Infrastructure: This view displays the Xen host, hypervisor, and domains in a pictorial format.

User Guide
l NNMi_Layer3: This view displays layer 3 (IP Subnet) connectivity between servers and the
switches or routers in the same subnet as the servers. The view also shows layer 3 (IP Subnet)
connectivity between the network switches and routers.
l Sol_Zones_Infrastructure: This view shows the relationship between the Solaris global and non-
global zones in a pictorial format.

User Guide
l IBMHMC_Infrastructure: This view displays the IBM HMC, IBM Frame, and LPARs CI types. The
following image shows the relationship between the CI Types.

User Guide
l IBMHMC_Deployment: This view shows the Monitoring LPAR and Operations Agent and
relationship between Monitoring LPAR to IBM HMC, LPAR, and IBM Frame in a pictorial format.

User Guide
Event Type Indicators

Event Type Indicators (ETIs) are categorization of events based on the type of occurrence.
How to Access the Event Type Indicators (ETIs)
1. Open the Indicators pane:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Indicators.
On OMi 10.x, click Administration > Service Health > CI Status Calculation > Health- and
Event Type Indicators.
2. In the CI Types tab, select Infrastructure Element.
The ETIs are mentioned under Node, Node Element, and Running Software categories.
The OMi MP for Infrastructure includes the following ETIs to monitor Infrastructure-related events. The
CI Type is Computer.

User Guide
ETI Description Value
Batch Jobs Indicates when one or more scheduled tasks or cron jobs Failed
fail on the system.
VMCreation Indicates when a VM is created. Occurred
VMMigration Indicates when a VM is migrated. Occurred
VMRemoval Indicates when a VM is removed. Occurred
VMRename Indicates when a VM is renamed. Occurred
BatchJobService Indicates availability of the Batch Job Service (UNIX or Available,

Linux Cron, Windows Schedule Task Services). Unavailable
DHCPServerService Indicates status of the DHCP Server Service on the Available,

DHCP server system. This can be a very crucial service Unavailable
for many mobile users.
DNSService Indicates status of the DNS (Domain Nameserver) Available,

service. Multiple network dependent services could Unavailable
potentially fail if this service undergoes unplanned
downtime.
EventLoggingService Indicates availability of the Event Logging service (UNIX Available,

or Linux syslog and Windows Event Logger services). Unavailable
SecureLoginService Indicates availability of the SSH (Secure Shell) service Available,

on the host. Unavailable
WebServerService Indicates status of the Web Server service on the Available,

system. Associated services are IIS on Windows and Unavailable
Apache on UNIX or Linux.
Health Indicators
Health Indicators (HIs) analyze the events that occur in Infrastructure CIs and report the health of the
Infrastructure CIs.
How to Access Health Indicators (HIs)
1. Open the Indicators pane:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Indicators.
On OMi 10.x, click Administration > Service Health > CI Status Calculation > Health- and
Event Type Indicators.

User Guide
2. In the CI Types tab, click Infrastructure Element.
The HIs are mentioned under Node, Node Element, and Running Software categories.
The OMi MP for Infrastructure includes the following HIs to monitor Infrastructure-related events:
CI Type HI Description Value
Layer2 L2Connection Indicates that both (or all) ends of a Unavailable,

Connection Status connection are not responding to SNMP Available (default)
queries.
VMware DRSStatus Monitors the status of Distributed Enabled (default),

Cluster Resource Scheduler (DRS). Disabled
VMware Cluster Strength Indicates the cluster up or down status Normal, Major, Critical
Cluster based on node strength.
VMware CPU usage level Indicates CPU usage level. Normal (default),
Cluster Warning, Critical
VMware Legacy System Normal (default),

Cluster Warning, Minor, Major,
Critical, Unknown
VMware Memory Usage Indicates memory usage level. Normal (default),

Cluster Level Warning, Critical
VMware Performance Normal (default),

Cluster Analytics Warning, Minor, Major,
Critical, Informational
Node Ping Indicates the Processing System is Available (default),

Availability reachable through ping. Unavailable
Node NodeStatus Indicates the current state of the Up (default), Down,

computer system. The states Hang, Maintenance,
Unknown, Hang, and Suspended apply Suspended, Unknown
only to virtual machines.
Computer CPU Indicates the percentage of entitlement Much Lower Than

Entitlement (CPU cycles allotted) used by a virtual Normal, Higher Than
UsageLevel machine. May exceed 100%. Normal, Normal
(default), Lower Than
Normal, Much Higher
Than Normal

User Guide
Computer CPULoad Indicates if the system is undergoing Normal (default),

heavy processing load. Bottlenecked,
Overloaded, Busy,
Constrained, Critical,
Warning
Computer CPURunQueue Indicates the load on the processor job Normal (default),
queue. Overloaded, Much
Lower Than Normal,
Higher Than Normal,
Lower Than Normal,
Much Higher Than
Normal
Computer HostDisk Indicates the utilization level for disks. Normal (default), Much
Utilization Lower Than Normal,
Higher Than Normal,
Lower Than Normal,
Much Higher Than
Normal, Critical,
Warning
Computer InterfaceError Indicates the input error rate based on High, Normal (default)
Rate the reported change in the number of
input packets and the packet error
count on the interface.
Computer Interface Indicates the network utilization based Normal (default), Higher
Utilization on interface speed, and the change in Than Normal, Much
number of output bytes on the interface. Higher Than Normal,
The queried MIB (Management Much Lower Than
Information Bases) values can vary Normal, Lower Than
depending on the speed of the interface Normal, High, Low,
and whether the system supports high Critical, Warning, none
speed counters for the interface.
Computer Interface Indicates the output discard rate based Normal (default), High
DiscardRate on the change in the number of output
packets on the interface and the
discarded packet count. Packets may
be discarded due to issues like buffer
overflows, congestion, or system
specific issues.

User Guide
Computer Memory Indicates the memory entitlement Normal (default), Higher

Entitlement utilization for the virtual machine. May Than Normal, Lower
Usage Level exceed 100%. Than Normal, Much
Higher Than Normal,
Much Lower Than
Normal
Computer MemoryLoad Indicates the memory pressure on a Normal (default),

computer - high memory utilization and Paging, Starving for
pressure to obtain more memory Memory, Bottleneck,
through paging. If left unattended the Critical, Warning
system may reach point of excessive
paging and an unstable state.
Computer MemoryUsage Indicates the memory usage level for Normal (default), Much
Level the system. Lower Than Normal,
Much Higher Than
Normal, Lower Than
Normal, Higher Than
Normal, Near Capacity,
Low, Critical, Warning
Computer NetworkFile Indicates the usage level for network Normal (default), Near
ShareUsage file shares - Microsoft Windows Capacity
Level Network Drives (mounts) and NFS,
CIFS mounts.
Computer PageFile_ Indicates how much of the paging file Normal (default), High,
UsageWIN capacity is used on a Window. Near Capacity
Computer Virtualization Indicates the additional memory used Normal (default), Much
Overhead by the VMware ESX or ESXi server to Lower Than Normal,
store the runtime information for virtual Much Higher Than
machines. Typically there is little Normal, Lower Than
variation in the value. The variation Normal, Higher Than
depends on size of the memory and the Normal
operating system running on the virtual
machine.
Computer ResourceUsage Indicates the system resource (CPU Normal (default), High
and memory) used by the processes
and services running on the system.

User Guide
Computer Root_disk_ Indicates the disk usage on primary Normal (default), High
Usage_level (root) disk on system. This would refer
to space utilization on root (/) filesystem
on UNIX and Linux systems. This
would refer to C: or whatever is defined
using SystemDrive setting on Windows
systems.
Computer SwapUsage Indicates the swap space usage level Normal (default), Near
Level on the system. Capacity, Much Higher
Than Normal, Much
Lower Than Normal,
Higher Than Normal,
Lower Than Normal
Computer KernelHandles Indicates capacity utilization by the Normal (default),

Usage kernel handles such as file handles, NearCapacity
process handles, semaphores, and
message queues.
Computer BatchJobService Indicates the availability of the batch Available (default),

job services on the system such as Unavailable
Schedule Task Service on Microsoft
Windows, and Cron services on UNIX
or Linux.
Computer EventLogging Indicates the availability of event Available (default),

Service logging services on the system such as Unavailable
event log service on Microsoft
Windows and syslog services on UNIX
or Linux.
Computer PrintService Indicates the status of print services on Available (default),

the system such as the print spooler Unavailable
service on Microsoft Windows, print
server role services on Windows 2008,
lp, and cupsd services on UNIX or
Linux.
Computer FileServer Indicates the status of the file server Available (default),
Service services on the system such as Unavailable
FileServer role services on Microsoft
Windows and NFS server and CIFS
server services on UNIX or Linux.

User Guide
Computer EmailService Indicates the status of E-Mail service Available (default),

on the system such as SMTP service Unavailable
on Microsoft Windows and sendmail
delivermail services on UNIX or Linux.
Computer WebServer Indicates the status of web server Available (default),

Service services on system such as IIS Unavailable
services on Windows and Apache
service on UNIX or Linux.
Computer RPCService Indicates the availability of the RPC Available (default),

service on the system. Unavailable
Computer FirewallService Indicates the status of firewall service Available (default),

on the system such as Windows Unavailable
Firewall service on Microsoft Windows
and iptables service on Linux.
Computer DNSService Indicates the status of DNS (Domain Available (default),

Nameserver) service on the system. Unavailable
Computer FTPService Indicates the state of FTP services on Available (default),

the system. FTP protocol is used for Unavailable
transferring files between systems.
Computer DHCPServer Indicates the status of DHCP Server Available (default),

Service Service on the DHCP server system. Unavailable
Computer SecureLogin Indicates the availability of SSH Available (default),

Service (Secure Shell) service on the system. Unavailable
UNIX Filesystem Indicates the file system usage on the Normal (default), High
Usage UNIX system.
UNIX SwapSpace Indicates the swap space available on Normal (default),

Available the system. Depleted, Near
Capacity
Windows LogicalDisk Indicates the degree of logical free disk Normal (default), Near
FreeSpaceWIN space on the system. Capacity
Windows TerminalServer Indicates the status of services for Available (default),

Service Windows Terminal Server on the Unavailable
Windows system.
Cluster Cluster Indicates the status of the resource Online (default) Failed,
Resource Resource Group group in a failover cluster. Offline, Reached SPOF
Group Status condition

User Guide
CPU CPUUsage Indicates the CPU usage level. Normal (default), Idle,
Level Busy, Spike, Much
Higher Than Normal,
Much Lower Than
Normal, Higher Than
Normal, Lower Than
Normal, High
File System DiskUsage Indicates the disk usage level. Normal (default),
Level NearCapacity, Low
File System Peak Disk Indicates utilization of fullest filesystem Normal (default), Major
Usage Level or logical desk
Disk DiskUtilization Indicates the disk utilization level. Normal (default), Much
Device Higher Than Normal,
Much Lower Than
Normal, Higher Than
Normal, Lower Than
Normal
Disk DiskService Indicates the average of disk I/O Normal (default), Much
Device Time service time. Higher Than Normal,
Much Lower Than
Normal, Higher Than
Normal, Lower Than
Normal
Interface InterfaceError Indicates the input error rate based on Normal (default), High
Rate the change in the number of input
packets on the interface and the packet
error count.
Interface Interface Indicates the network utilization based Normal (default), Lower
Utilization on the interface speed, and the change Than Normal, Much
in the number of output bytes on the Lower Than Normal,
interface. The queried MIB High, Higher Than
(Management Information Base) values Normal, Much Higher
vary based on the speed of the interface Than Normal, Low,
and whether the system supports high None
speed counters for interface.

User Guide
Interface Interface Indicates the output discard rate based Normal (default), High
DiscardRate on the change in the number of output
packets on the interface and the
discarded packet count. Packets may
be discarded due to reasons such as
receive buffer overflows, congestion, or
system specific issues.
Interface Interface Indicates the availability status of the Available (default),

Communication interface. Unavailable
Status
IpAddress AddressStatus Indicates the availability status of the Available (default),

IP Address. Unavailable
Cluster Cluster Indicates the availability status of the Available (default),

Software Software Cluster Service. Unavailable
Service
Failover Cluster Indicates the cluster availability status QuorumMet (default),

Cluster Strength based on node strength. NotAllNodesDown,
RedundantOkay,
QuorumNotMet, SPOF,
AllNodesDown
VMware Datastore Indicates high utilization on datastore Normal (default), High

Datastore Utilization
VMware Legacy System Normal (default),

Datastore Warning, Major, Minor,
Critical, Unknown
VMware Performance Normal (default),

Datastore Analytics Warning, Major, Minor,
Critical, Informational
Marge ESX VMFSUsage Indicates the usage level of the VMFS Normal (default),
Server Level (Virtual Machine File System). VMFS is NearCapacity
a clustered file system that is used by
the VMware host systems to store
virtual machines and virtual disk files.
VMware VMwareHost Data on all network interfaces, received Normal (default), Much
ESX Server NetworkUsage at or dispatched from the VMware Higher Than Normal,
ESX/ESXi Host (in MBs). Much Lower Than
Normal, Higher Than
Normal, Lower Than
Normal

User Guide
Hypervisor Virtualization Indicates the status of virtualization Available (default),

Service service running on Host such as Hyper- Unavailable
V service running on Microsoft
Windows 2008 Server. The service is
essential for running of virtual
machines.
Computer CPU Wait Total CPU time spent in wait state. Low (Normal) (default),
Medium (Minor), High
(Critical)
Computer Memory Amount of compressed and Low (Normal) (default),

Compression decompressed memory per second. Medium (Minor), High
(Critical)
Computer Host Disk Load Load on the Host storage device Low (Normal) (default),
Medium (Minor), High
(Critical)
Computer Memory Memory usage on ESX by VM. Low (Normal) (default),

Utilization Medium (Minor), High
(Critical)
Node Ping Quality Indicates percentage of packets Good (Normal)

reached the monitoring system. (default), Medium
(Minor), Bad (Critical)
VMware CPU Ready Percentage of time that the virtual Low (Normal) (default),
ESX Time machine was ready, but could not get Medium (Minor), High
scheduled to run on the physical CPU. (Critical)
CPU ready time is dependent on the
number of virtual machines on the host
and their CPU loads.
Computer CPU Usage CPU Usage Level Normal (default), Idle,

Level Busy, Spike, Much
Higher Than Normal,
Much Lower Than
Normal, Higher Than
Normal, Lower Than
Normal, High
Computer DiskIO Indicates the average Disk Input or Normal, Major

Output rate on the machine.
Computer KernelLatency Indicates the Kernel latency on the Normal, Major

host.

User Guide
Topology Based Event Correlation (TBEC) Rules

In event correlation, rules are applied to identify commonly occurring events or combinations of events
and helps handling of such events by automatically identifying events that can be withheld, removed or
need a new event to be generated and displayed to the operators.
For more information on how the correlation rules work, see the Operations Manager i Concepts Guide.
How to Access the Correlation Rules

Open the Correlation Rules pane:
On BSM 9.2x, click Admin > Operations Management > Event Correlation > Topology-Based
Event Correlation.
On OMi 10.x, click Administration > Event Processing > Correlation > Topology-Based Event
Correlation.
The OMi MP for Infrastructure includes the following rules to correlate Infrastructure- related events.
System::Computer:CPU Load >> CPU Usage Level
Description: CPU usage of one or more CPUs on the system is high as the system is in a
CPU bottleneck.
Cause
CIT: Computer ETI: CPU Load Value: Bottlenecked
Symptom
CIT: CPU ETI: CPU Usage Level Value: High/ Much Higher Than
Normal/ Spike
System::Computer:Memory Load >> CPU Load
Description: CPU bottleneck caused by paging
Cause
CIT: Computer ETI: Memory Load Value: Paging
Symptom
CIT: Computer ETI: CPU Load Value: Bottlenecked
System::Computer:Memory Load >> Memory Usage Level

User Guide
Description: Memory usage on system is high as the system is in a memory bottleneck
Cause
CIT: Computer ETI: Memory Load Value: Paging
Symptom
CIT: Computer ETI: Memory Usage Level Value: Much Higher Than Normal/ Near
Capacity
System::Computer:Memory Usage Level >> Swap Usage Level
Description: High memory usage results in swapping
Cause
CIT: Computer ETI: Memory Usage Level Value: Near Capacity
Symptom
CI: Computer ETI: Swap Usage Level Value: Much Higher Than Normal/ Near Capacity
System Down >> System Applications Down
Description: Services or applications are unavailable as the system is down
Cause
CIT: Computer ETI: Node Status Value: Down, Suspended, Unknown
Symptom
CIT: Computer ETI: Value:
Batch Jobs Job Failed
E-Mail Service Unavailable
Event Logging Service Unavailable
Firewall Service Unavailable
WebServer Service Unavailable
Print Service Unavailable
RPC Service Unavailable
System::Computer:Resource Usage >> CPU Usage Level

User Guide
Description: Process using high amount of cpu on system causing system cpu usage high
Cause
CIT: Computer ETI: Resource Usage Value: High
Symptom
CIT: CPU ETI: CPU Usage Level Value: High/ Much Higher Than Normal/
Spike
System::Computer:Resource Usage >> Memory Usage Level
Description: Process using high amount of memory on system causing system memory
usage high
Cause
CIT: Computer ETI: Resource Usage Value: High
Symptom
CIT: Computer ETI: Memory Usage Value: Higher Than Normal/ Much Higher Than
Level Normal/ Near Capacity
System::File System:Disk Usage Level >> Swap Usage Level
Description: Swap usage caused by system drive full
Cause
CIT: ETI: Disk Usage Value: Near Capacity

FileSystem Level
Symptom
CIT: ETI: Swap Usage Value: Higher Than Normal/ Much Higher Than Normal/
Computer Level Near Capacity
System::Node:PingAvailability >> NodeStatus
Description: Ping availability of node failed because node is down
Cause
CIT: Node ETI: Node Status Value: Suspended, Down, Unknown
Symptom
CIT: Node ETI: Ping Availability Value: Unavailable
System::File System:PingAvailability >> InterfaceCommunicationStatus

User Guide
Description: Node cannot be pinged because interface communication status is unavailable
Cause
CIT: Interface ETI: Interface Communication Value: Unavailable

Status
Symptom
CIT: Interface ETI: Ping Availability Value: Unavailable
Virtual::Computer:Memory Usage Level >> Hypervisor Memory Usage Level
Description: Hypervisor is constrained by high memory usage done by VM
Cause
CIT: Computer ETI: Memory Usage Value: Much Higher Than Normal
Level
Symptom
CIT: Computer ETI: Memory Usage Value: Much Higher Than Normal/ Near
Level Capacity
Virtual::Computer::CPU Usage >> Hypervisor System CPU Load
Description: A VM using high amount of physical CPU cycles on the hypervisor can cause
bottleneck in Hypervisor.
Cause
CIT: Computer ETI: CPU Load Value: Bottlenecked/ Busy/

Overloaded
Symptom
CIT: Computer ETI: CPU Load Value: Bottlenecked/ Busy/

Overloaded
Virtual::Computer::CPU Load>> CPU Entitlement Usage Level
Description: A VM using high amount of CPU entitled can cause CPU load to become high
on server.
Cause
CIT: Computer ETI: CPU Entitlement Value: Higher Than Normal/ Much Higher
Usage Level Than Normal
Symptom

User Guide
Description: A VM using high amount of CPU entitled can cause CPU load to become high
on server.
CIT: Computer ETI: CPU Load Value: Bottlenecked/ Busy/ Overloaded/

Constrained
Virtual::Computer::Memory Usage Level>> Memory Entitlement and Swap Usage Level
Description: Memory Entitlement and Swap Usage Level becoming high on VMs can cause
High Memory Usage levels on Server.
Cause
CIT: Computer ETI: Swap Usage Level Value: Near Capacity/ Higher Than
Normal/ Much Higher Than Normal
ETI: Memory Entitlement Value: Higher Than Normal/ Much Higher

Usage Level Than Normal
Symptom
CIT: Computer ETI: Memory Usage Level Value: Near Capacity/ Higher Than
Normal/ Much Higher Than Normal
Hypervisor::Ping Availability >> VM::Ping Availability
Description: VMs are unavailable as the hypervisor host running the VMs is down.
Cause
CIT: Computer ETI: Ping Availability Value: Unavailable
Symptom
CIT: Computer ETI: Ping Availability Value: Unavailable
Cluster Software Service Unavailable >> Clustered Server Offline
Description: Cluster software Services on cluster systems failing to run causes clustered
servers (resource groups) to be inactive.
Cause
CIT: ClusterSoftware ETI: Cluster Software Service Value: Unavailable
Symptom
CIT: ClusterResourceGroup ETI: Cluster Resource Group Value: Offline

Status
Cluster Nodes Down >> Cluster Resource Group Impacted

User Guide
Description: When 1 or more cluster nodes are down, clustered servers (resource groups)
running in failover mode on these nodes are impacted
Cause
CIT: Computer ETI: Node Status Value: Down/ Hang/

Suspended/ Unknown
Symptom
CIT: ClusterResourceGroup ETI: Cluster Resource Group Value: Offline

Status
Cluster Members Down >> FailoverCluster Impacted (many symptoms)
Description: When a few cluster members are unavailable, the cluster is down.
Cause
CIT: Computer ETI: Node Status Value: Down/ Hang/ Suspended/ Unknown
Symptom
CIT: FailoverCluster ETI: Cluster Strength Value: All Nodes Down/ Quorum Not met/
SPOF
Cluster Member Down >> Cluster Software Service Down
Description: When the cluster member is down, the cluster software service on the node is
down.
Cause
CIT: Computer ETI: Node Status Value: Down/ Suspended
Symptom
CIT: ClusterSoftware ETI: Cluster Software Service Value: Unavailable

User Guide
Mapping Rules
The OMi MP for Infrastructure contains the following mapping rules:
CI Type: ClusterSoftware
Map to
Indicator
Name Description Event Filter Indicator Value
hadUnAvailability VCS cluster process monitor HADMajor Cluster Based on

Software Severity
Service
hadAvailability VCS cluster process HADNormal Cluster Based on

availability Software Severity
Service
hashadow VCS cluster process Hashadow Cluster Based on

Unavailability unavailability Major Software Severity
Service
hashadow VCS cluster process Hashadow Cluster Based on

Availability availability Normal Software Severity
Service
HadUnavailability VCS cluster Windows Had HadWindows Cluster Based on

Windows process unavailability Unavailable Software Severity
Filter Service
HadAvailability VCS windows cluster service HadWindows Cluster Based on

WindowsFilter Had availability AvailableFilter Software Severity
Service
VCSComm VCS cluster process VCSComm Cluster Based on

UnAvailability VCSComm unavailability Unavailable Software Severity
Filter Service
VCSCommAvailable VCS Cluster Windows VCSComm Cluster Based on

process availability AvailableFilter Software Severity
Service
CmdServer VCS Windows Cluster CmdServer Cluster Based on

UnAvailable service CmdServer UnAvailable Software Severity
unavailable Filter Service
CmdServerAvailable VCS Windows cluster service CmdServer Cluster Based on

CmdServer availability Availability Software Severity
Filter Service

User Guide
CI Type: ClusterSoftware
Map to
Indicator
Name Description Event Filter Indicator Value
clusterUnavailability Sun cluster process Cluster Cluster Based on

unavailability Unavailable Software Severity
Filter Service
clusterAvailability Sun cluster process Cluster Cluster Based on

availability Available Software Severity
Filter Service
clurgmgrd Red Hat cluster process clurgmgrd Cluster Based on

Unavailability clurgmgrd unavailability Unavailable Software Severity
Filter Service
clurgmgrd Red Hat cluster process clurgmgrd Cluster Based on

Availability clurgmgrd availability AvailableFilter Software Severity
Service
ccsdUnavailability Red Hat cluster process ccsd Cluster Based on

/sbin/ccsd process Unavailable Software Severity
unavailability Filter Service
ccsdAvailable Red Hat cluster process ccsdAvailable Cluster Based on

/sbin/ccsd process Filter Software Severity
availability Service
ClusSvcUnavailability Microsoft cluster service ClusSvc Cluster Based on

ClusSvcunavailability Unavailable Software Severity
Filter Service
ClusSvcAvailability Microsoft cluster service ClusSvc Cluster Based on

ClusSvcavailability Available Software Severity
Filter Service
cmcldUnavailability MCSG cluster process cmcld cmcld Cluster Based on

unavailability Unavailable Software Severity
Filter Service
cmcldAvailability MCSH cluster process cmcld cmcldAvailable Cluster Based on

availability Filter Software Severity
Service
CI Type: Node
Name Description Event Filter Indicator Map to Indicator

Value

User Guide
CI Type: Node
Ping Indicates failure to contact node Ping Ping Based on

Unavailability using ping UnAvailibilty Availability Severity
Filter
PingAvailability Indicates node can be contacted Ping Ping Based on

using ping. UnAvailibilty Availability Severity
Filter
Operations Orchestration (OO) Flows

When creating the mapping for the Operations Orchestration (OO) flows, you can set default values for
the attributes listed in the following table. You need not specify these values each time you run the
flows.
Flow input Description
port Port number of the HPOM Tool WS. This attribute is optional.
username The user name for the HPOM Server that will use used in the HPOM Tool WS.
password The password for the HPOM Server that will use used in the HPOM Tool WS.
For more information about creating the mapping and Run Book automation rules, see the topics How
to Create a Run Book Automation Rule and Run Books Configuration Page in the OMi help.
The following section lists the OO flows:
Host Health
You can use the Host Health flow to check the health of a VmWare ESX Server.
Note: You can run this flow only on an HPOM node.
This flow analyzes the following:
l CPU Utilization
l Memory Utilization
You must map this flow to the CIT vmware_esx_server.
The following table lists the user input items when executing this OO flow.
hpomNode FQDN of the ESX Server. This must be a managed node for the HPOM Server and
must be specified each time you run the OO flow.

User Guide
host FQDN of the HPOM Server. You can map this input to the Event attribute Originating
Server.
ESX Server Name of the ESX Server.You can map this input to the CI attribute name of CI Type
Name vmware_esx_server.
Sanity check for VISPI

You can use this flow to check the sanity of VISPI utilization.
This flow checks the following:
l Performance Agent Version
l Operations Agent Version
l Firewall Settings
You must map this flow to the CIT UNIX or nt.
Note: You can run this flow only on a node, which is monitored by HPOM Smart Plug-in for
Virtualization Infrastructure.
Flow
input Description
hpomNode FQDN of the node. This must be a managed node for the HPOM Server and must be
specified each time you run the OO flow.
Server.
VM Health
You can use this flow to check the health of a VM.
Note: You can run this flow only on an HPOM node.
This flow analyses the following:
l CPU Utilization
l Memory Utilization
You must map this flow to the CIT host_node.

User Guide
Flow
input Description
hpomNode FQDN of the VM. This must be a managed node for the HPOM Server.
Server.
VM Name Name of the VM. You can map this input to the CI attribute name of CI Type host_
node.
Tools
The OMi MP for Infrastructure is packaged with tools which enable administering, monitoring, and
troubleshooting the Infrastructure CIs.
How to Access Tools

1. Open the Tools pane:
On BSM 9.2x, click Admin > Operations Console > Tools.
On OMi 10.x, click Administration > Operations Console > Tools.
2. In the CI Types pane, click ConfigurationItem > InfrastructureElement <CI Type>.
The OMi MP for Infrastructure contains the following tools of CI Type Unix:
CI
Type Tool Name Tool Description
Node Ping node from Shows the output of a ping from the NNMi server to a selected node in a
Network Node web browser.
Manager i (NNMi)
This tool requires that the NNMi server name and port are correctly
server
configured in the HP NNMi adapter section of the general server
configuration GUI.
Ping node from Shows the output of a ping from the NNMi server to a selected node in a
NNMi server web browser, using https connection.
(https)
configuration GUI.

User Guide
CI
Show Layer 2 Shows the Layer 2 Neighbors of the node from which the corresponding
Neighbors to NNMi incident originated.
related NNMi
This tool requires that it is started in the context of a forwarded NNMi
node
incident, so that the message contains custom message attributes
about the NNMi incident UUID, NNMi server name and the NNMi server
port.
Neighbors to NNMi incident originated, using https connection.
related NNMi
node (https)
port.
Neighbors to NNMi incident originated.
related NNMi
node
port.
Neighbors to NNMi incident originated, using https connection.
related NNMi
node (https)
port.
Show NNMi Shows the main console of the NNMi server in a web browser.
console
configuration GUI.

User Guide
CI
Show NNMi Shows the main console of the NNMi server in a web browser, using
console (https) https connection.
configuration GUI.
Show NNMi Shows the status of the NNMi server processes and services in a web
server status browser.
configuration GUI.
Show NNMi Shows the status of the NNMi server processes and services in a web
server status browser, using https connection.
(https)
configuration GUI.
Show node Shows the setup information of a selected node in a web browser.
information in
NNMi
configuration GUI.
Show node Shows the setup information of a selected node in a web browser, using
information in https connection.
NNMi (https)
configuration GUI.
Show related Shows the corresponding NNMi incident to a selected message in a web
NNMi incident browser.

port.

User Guide
CI
Show related Shows the corresponding NNMi incident to a selected message in a web
NNMi incident browser, using https connection.
(https)
port.
Show related Shows the NNMi setup information for the node from which the
NNMi node corresponding NNMi incident originated.

port.
Show related Shows the NNMi setup information for the node from which the
NNMi node corresponding NNMi incident originated, using https connection.
(https)
port.
Traceroute to Shows the output of a traceroute from the NNMi server to a selected
node from NNMi node in a web browser.
server
configuration GUI.
Traceroute to Shows the output of a traceroute from the NNMi server to a selected
node from NNMi node in a web browser, using https connection.
server (https)
configuration GUI.
UNIX VMware List Lists the Virtual Machines configured on ESX/ESXi servers managed by
VMs vMA.
VMware Host Lists information of the ESX and ESXi servers managed by vMA.
Info
VMware Lists information of the Resource Pools associated with ESX/ESXi

Resource Pool servers managed by vMA.
Info
VMware List Lists suspended and powered off Virtual Machines of ESX/ESXi servers
Suspended VMs managed by vMA.

Chapter 4: Customizing OMi MP for Infrastructure
OMi MP for Infrastructure can be customized to suit your monitoring requirements. You can edit the
existing Infrastructure Management Templates or create new Infrastructure Management Templates to
monitor the systems in your environment.
The following section provides information about the customization scenarios for OMi MP for
Infrastructure.
l Creating Infrastructure Management Templates
l Editing Infrastructure Management Templates
Creating Infrastructure Management Templates

Configuration Folders > Infrastructure Management > Infrastructure Management

Templates
3. If you need to create a new configuration folder, click . The Create Configuration Folder opens.
4. Type the name of the new configuration folder and the description. For example, you can type the
new configuration folder name as Test.
5. Click OK. The new configuration folder is created.
Configuration Folders > Infrastructure Management > Test
6. Select the new configuration folder. In the Management Templates & Aspects pane, click . The
Create Management Template wizard opens.
7. In the General tab, type a Name for the new Management Template. Click Next.
8. Select a Topology View that shows the CI type that you want to manage, and all the related CI
types. Click an item in the topology map to select the CI Type of the CIs that this Management
Template enables you to manage. You can assign the type of CI to a Management Template. For

User Guide
example, you can select Systems_Infrastructure as the topology view and Computer as the
CI Type. Click Next.
9. In the Aspects tab, click , and then click to add existing Aspects to the new Management
Template. The Add Existing Aspect dialog box opens. Select the Aspects that you want to add,
and then click OK.
If suitable Aspects do not exist, click , and then click to create an Aspect.
10. For each Aspect that you add, you must specify at least one Target CI.
Click an Aspect in the list, and then in the topology map, click the CI types you want the Aspect to
monitor when this Management Template is assigned. (Press CTRL to select several CI types.)
Each CI type that you select here must correspond to one of the CI types assigned within the
Aspect itself (or a child of one of those CI types). For example, you can select CI from the
topology map.
11. In the Parameters tab, the list of all the parameters added to this Aspect from the policy templates
is displayed.
To combine the parameters:
a. Press CTRL and click the parameters that you want to combine.
b. Click . The Edit/Combine Parameters dialog box opens.
c. Type a Name for the combined parameters.
d. (Optional). Specify a Description, Default Value, and whether the combined parameter is
Read Only, an Expert Setting, or Hidden.
You can specify either a specific default value, or you can click From CI Attribute and then
browse for a CI attribute. When you specify a CI attribute, Operations Management sets the
parameter value automatically during the deployment of the underlying policy templates, using
the actual value of this attribute from the CI. You can also change values of conditional
parameters. (The conditions are read-only and cannot be changed at Management Template
level.)
Note: Read Only prevents changes to the parameter value when the Aspect is assigned
to a configuration item. Hidden also prevents changes, but additionally makes the
parameter invisible. Users can choose whether to show expert settings when they make
an assignment.
e. Click OK.

User Guide
You can also edit the parameters without combining them, to override the defaults in the Aspects
or policy templates. Click one parameter, and then click . The Edit/Combine Parameters dialog
box opens.
12. In the Create Management Template wizard, click Finish to save the Management Template and
close the wizard. The new Management Template appears in the Management Templates &
Aspects pane.
Editing Infrastructure Management Templates

You can edit the Management Templates to change the following artifacts:
l Editing Parameters - Changing the default values
l Editing Aspects - Deleting an Aspect
Editing Parameters - Changing the Default Values

Use Case: You are using Essential System Management Template to monitor the health of every
single system in the datacenter. You are monitoring the availability and utilization of the system
resources in your environment. You want to modify the parameters corresponding to the resources of
the system like hardware and software to closely monitor the health of the system.
To edit the parameters:

Templates > Essential System Management
3. In the Management Templates & Aspects pane, select Essential System Management from the
list, and then click . The Edit Management Template dialog box opens.
4. Click the Parameters tab. The list of parameters appear.
5. Double-click the desired parameter. The Edit/Combine Parameters window appears.
6. You can change the default value by clicking .

User Guide
7. Specify the value and click OK. The Edit Management Template dialog box opens.
8. Click OK. The version of the Management Template is incremented.
Note: The version number of the Management Template is incremented when any customization
is made to the Management Template.
Editing Aspects - Deleting an Aspect

Use Case: You are using Extensive System Management Template to monitor the performance of
systems in a datacenter. You are monitoring the performance of all system resources like CPU,
memory, disk, filesystem, network interface, system process and services, security, system logging
and so on. You do not want to use some Aspects which are part of the Extensive System Management
Template.
To edit the Aspects:

Templates
3. In the Management Templates & Aspects pane, select Extensive System Management from the
list, and then click . The Edit Management Template dialog box opens.
4. Click the Aspects tab. The list of Aspects appear.
5. Select the Aspect that you want to delete from the list.
6. Click to delete the selected Aspect.
7. Click OK. The version of the Management Template is incremented.

Chapter 5: Troubleshooting
The following section provides information about troubleshooting scenarios:
Problem: Management Templates or Aspects are not deployed on the managed nodes.
Solution: To resolve the problem, check for the following:
1. Check for assignment of Management Template or Aspect under:
Tuning.
2. Check for deployment of Management Template or Aspect under:
On BSM 9.2x, click Admin > Operations Management > Monitoring > Deployment Jobs.
On OMi 10.x, click Administration > Monitoring > Deployment Jobs.
3. Check the following OMi log files:
Windows:
%topaz_home%\log\EJBContainer\opr-webapp.log
%topaz_home%\log\EJBContainer\opr-configserver.log
Linux:
/opt/HP/BSM/log/EJBContainer/opr-webapp.log
/opt/HP/BSM/log/EJBContainer/opr-configserver.log
Note: To debug a policy you must edit the policy and enable the debug parameter.
Problem: WPAR is not discovered in RTSM since BYLS_LS_PARENT_UUID is na

Solution: To discover WPAR, Parent UUID should not be na.

Appendix: Graph Templates
Graphs represent pictorial representation of metrics. The OMi MP for Infrastructure includes the
Systems Infrastructure and Virtualization Infrastructure graph family, which is mapped to the Computer
CI type. For information about creating and viewing graphs, see the Performance Graphing documents
available in the OMi documentation. The data source used for logging data is SCOPE.
How to Access the Graphs
1. Open the Performance Graph Mapping pane:
On BSM 9.2x, click Admin > Operations Console > Performance Graph Mappings.
On OMi 10.x, click Administration > Operations Console > Performance Graph Mappings.
2. In the CI Types tab, click Infrastructure Element.
Note: The Virtualization Infrastructure graph family is visible for all nodes under the CI type
Computer, however you can launch graphs only for virtual machines.
Systems Infrastructure Graph Templates

The following table lists the graph templates for System Infrastructure.
Configuration Details
The following table lists the Metric names corresponding to the Configuration Details graph template.
Metric Names Metric Description
GBL_SYSTEM_ID The network node hostname of the system.
GBL_OSNAME A string representing the name of the operating system.
GBL_OSRELEASE The current release of the operating system.
GBL_MACHINE_ CPU model

MODEL
GBL_COLLECTOR ASCII field containing collector name and version.
GBL_NUM_CPU Number of physical CPUs on the system. This includes all CPUs, either
online or offline.

User Guide
GBL_NUM_DISK Number of disks on the system. Only local disk devices are counted in this
metric.
GBL_NUM_ Number of network interfaces on the system. This includes the loopback
NETWORK interface.
GBL_MEM_PHYS Amount of physical memory in the system (in MBs unless otherwise
specified).
GBL_SWAP_ Total amount of potential swap space, in KB.

SPACE_AVAIL_
KB
TBL_PROC_ The configured maximum number of the proc table entries used by the kernel
TABLE_AVAIL to manage processes. This number includes both free and used entries.
GBL_LOGGING_ A 13-byte field indicating the types of data logged by the collector. This is
TYPES controlled by the LOG statement in the parm file.
GBL_ The percentage of CPU that a process must use to become interesting during
THRESHOLD_ an interval.
CPU
GBL_ The virtual memory in MB that a process must use to become interesting
THRESHOLD_ during an interval.
PROCMEM
GBL_ The rate of physical disk IOs that a process must generate to become
THRESHOLD_ interesting during an interval.
DISK
GBL_LOGFILE_ Three byte ASCII field containing the log file version number.
VERSION
GBL_MACHINE An ASCII string representing the Processor Architecture.
GBL_ This indicates the word size of the current kernel on the system.
OSKERNELTYPE_
INT
GBL_MEM_AVAIL The amount of physical available memory in the system (in MBs unless
otherwise specified).
TBL_BUFFER_ The size (in KBs unless otherwise specified) of the file system buffer cache
CACHE_AVAIL on the system
GBL_OSVERSION A string representing the version of the operating system.
MEMORY_
MEMFREE

User Guide
MEMORY_
AVAILABLE__
MBYTES
MEMORY_
MEMTOTAL
MEMORY_SWAP_
AVAIL
MEMORY_SWAP_
FREE
Free swap space

available
Process Details
The following table lists the Metric names corresponding to the Process Details graph template.
PROC_PROC_NAME The process (or kernel thread) program name.
PROC_PROC_CMD The full command line with which the process

was initiated.
PROC_PROC_ID The process ID number (PID) of this process

(associated process for kernel threads) that is
used by the kernel to uniquely identify the
process.
PROC_CPU_TOTAL_UTIL The total CPU time consumed by a process

(kernel thread) as a percentage of the total CPU
time available during the interval.
PROC_DISK_PHYS_IO_RATE The average number of physical disk IOs per

second made by the process or kernel thread
during the interval.
PROC_INTEREST A field of flags indicating why the process was

considered interesting enough to be logged.
PROC_STOP_REASON A text string describing what caused the process

(kernel thread) to stop executing.
PROC_APP_ID The ID number of the application to which the

process (kernel thread) belonged during the
interval.

User Guide
PROC_PRI The dispatch or current base priority of a process

(kernel thread) at the end of the interval.
PROC_MEM_RES The size (in KB) of resident memory allocated for

the process.
PROC_MEM_VIRT The size (in KB) of virtual memory allocated for

the process.
PROC_CPU_USER_UTIL
PROC_CPU_SYS_MODE_UTIL The percentage of time that the CPU was in

system mode in the context of the process during
the interval.
PROC_PARENT_PROC_ID The parent process PID number.
PROC_USER_NAME This is real user name of a process or the login

account (from /etc/passwd) of a process.
PROC_RUN_TIME The elapsed time since a process started, in

seconds.
PROC_INTERVAL_ALIVE The number of seconds that the process was

alive during the interval.
PROCESS_PID
PROCESS
PROCESS_CPU0D37
PROCESS_MEMSIZE
PROCESS_USER
PROCESS_PPID
PROCESS_0D37_PROCESSOR_TIME
PROCESS_IO_DATA_OPERATIONS_SEC
PROCESS_PRIORITY_BASE
PROCESS_PRIVATE_BYTES
PROCESS_VIRTUAL_BYTES
PROCESS_0D37_USER_TIME
PROCESS_CREATING_PROCESS_ID
PROCESS_ELAPSED_TIME

User Guide
CPU Gauges
The Metric name corresponding to the CPU Gauges graph template is GBL_CPU_TOTAL_UTIL. It is
the percentage of time the CPU was not idle during the interval.
CPU Utilization Baseline

The Metric name corresponding to the CPU Utilization Baseline graph template is GBL_CPU_TOTAL_
UTIL. It is the percentage of time the CPU was not idle during the interval.
CPU Summary
The following table lists the Metric names corresponding to the CPU Summary graph template.
Metric Names Metric Definition
GBL_CPU_INTERRUPT_UTIL The percentage of time that the CPU spent processing interrupts
GBL_CPU_SYS_MODE_UTIL Percentage of time the CPU was in system mode during the
interval.
GBL_CPU_USER_MODE_UTIL The percentage of time the CPU was in user mode during the
interval.
CPU_UTILIZATION_0D37SYS
CPU_UTILIZATION_
0D37USER
PROCESSOR_0D37_
INTERRUPT_TIME
Disk Summary
The following table lists the Metric names corresponding to the Disk Summary graph template.
GBL_DISK_UTIL_PEAK The utilization of the busiest disk during the interval.
GBL_FS_SPACE_UTIL_ The percentage of occupied disk space to total disk space for the
PEAK fullest file system found during the interval.
GBL_DISK_PHYS_BYTE_ The average number of KBs per second at which data was transferred
RATE to and from disks during the interval.
GBL_DISK_PHYS_IO_ The number of physical IOs per second during the interval.
RATE
GBL_DISK_LOGL_READ_ The average number of logical reads per second made during the
RATE interval.
BLOCK_DEVICE_
ACTIVITY_R0D43W_S

User Guide
PHYSICALDISK_DISK_
BYTES_SEC
LOGICALDISK_READS_
SEC
Global CPU Forecast

The Metric name corresponding to the Global CPU Forecast graph template is GBL_CPU_TOTAL_
Global Details
The following table lists the Metric names corresponding to the Disk Summary graph template.
GBL_CPU_TOTAL_UTIL Percentage of time the CPU was not idle during the interval.
GBL_ACTIVE_PROC It is the sum of the alive-process- time/interval-time ratios of every

process that is active (uses any CPU time) during an interval.
GBL_PRI_QUEUE The average number of processes or kernel threads blocked on

PRI (waiting for their priority to become high enough to get the
CPU) during the interval.
GBL_RUN_QUEUE The average number of threads waiting in the runqueue over the
interval.
GBL_DISK_PHYS_IO_RATE The number of physical IOs per second during the interval.
GBL_DISK_PHYS_BYTE_ The average number of KBs per second at which data was
RATE transferred to and from disks during the interval.
GBL_DISK_LOGL_IO_RATE The number of logical IOs per second during the interval.
GBL_MEM_CACHE_HIT_ The percentage of buffer cache reads resolved from the buffer
PCT cache (rather than going to disk) during the interval.
GBL_MEM_PAGEOUT_RATE The total number of page outs to the disk per second during the
interval.
GBL_MEM_SWAPOUT_ The number of swap outs per second during the interval.
RATE
GBL_MEM_UTIL The percentage of physical memory in use during the interval. This
includes system memory (occupied by the kernel), buffer cache
and user memory.

User Guide
GBL_MEM_USER_UTIL The percent of physical memory allocated to user code and data at
the end of the interval.
GBL_MEM_SYS_AND_ The percentage of physical memory used by the system (kernel)

CACHE_UTIL and the buffer cache at the end of the interval.
GBL_SWAP_SPACE_UTIL The percent of available swap space that was being used by
running processes in the interval.
GBL_FS_SPACE_UTIL_ The percentage of occupied disk space to total disk space for the
PEAK fullest file system found during the interval.
GBL_NET_PACKET_RATE The number of successful packets per second (both inbound and
outbound) for all network interfaces during the interval.
GBL_NET_IN_PACKET_ The number of successful packets per second received through all
RATE network interfaces during the interval.
GBL_NET_OUT_PACKET_ The number of successful packets per second sent through the
GBL_NFS_CALL_RATE The number of NFS calls per second the system made as either a
NFS client or NFS server during the interval.
GBL_NET_COLLISION_1_ The number of collisions per minute on all network interfaces

MIN_RATE during the interval.
GBL_NET_ERROR_1_MIN_ The number of errors per minute on all network interfaces during
RATE the interval.
GBL_SYSCALL_RATE The average number of system calls per second during the
interval.
GBL_CPU_SYS_MODE_UTIL Percentage of time the CPU was in system mode during the
interval.
GBL_CPU_USER_MODE_ Percentage of time the CPU was in user mode during the interval.
UTIL
GBL_NUM_USER The number of users logged in at the time of the interval sample.
GBL_ALIVE_PROC It is the sum of the alive-process-time/interval- time ratios for

every process.
GBL_STARTED_PROC_ The number of processes that started per second during the
RATE interval.
CPU_UTILIZATION_
0D37USR

User Guide
CPU__UTILIZATION_
0D37SYS
SYSTEM_SWAPPING_AND_
SWITCHING_ACTIVITY_
SWPOT_S
SYSTEM_SWAPPING_AND_
SWITCHING_ACTIVITY_
SWPIN_S
PAGING_ACTIVITY_PGIN_S
PAGE0D45OUT_AND_
MEMORY_FREEING_
ACTIVITIES_PGOUT_S
5MINAVG
MEMORY_FREEMEM
MEMORY_PERCENT_USED
BLOCK_DEVICE_ACTIVITY_
R0D43W_S
CACHE_COPY_READ_
HITS_0D37
SYSTEM_SYSTEM_CALLS_
SEC
SYSTEM_PROCESSOR_
QUEUE_LENGTH
Global History
The following table lists the Metric names corresponding to the Global History graph template.
GBL_CPU_ Percentage of time the CPU was not idle during the interval.
TOTAL_UTIL
GBL_DISK_ The utilization of the busiest disk during the interval.

UTIL_PEAK
GBL_SWAP_ The percent of available swap space that was being used by running processes in
SPACE_UTIL the interval.

User Guide
GBL_MEM_ The percentage of physical memory in use during the interval. This includes
UTIL system memory (occupied by the kernel), buffer cache and user memory.
GBL_ It is the sum of the alive-process- time/interval-time ratios of every process that is
ACTIVE_ active (uses any CPU time) during an interval
PROC
Global Run Queue Baseline

The following table lists the Metric names corresponding to the Global Run Queue Baseline graph
template.
GBL_RUN_QUEUE The average number of threads waiting in the run queue

over the interval.
SCALLS_S
5MINAVG
SYSTEM_PROCESSOR_QUEUE_
LENGTH
Memory Summary
The following table lists the Metric names corresponding to the Memory Summary graph template.
GBL_MEM_UTIL The percentage of physical memory in use during the interval. This
includes system memory (occupied by the kernel), buffer cache
and user memory.
GBL_MEM_USER_UTIL The percentage of physical memory allocated to user code and data
at the end of the interval.
GBL_MEM_SYS_AND_ The percentage of physical memory used by the system (kernel)

CACHE_UTIL and the buffer cache at the end of the interval.
GBL_MEM_CACHE_HIT_ The percentage of buffer cache reads resolved from the buffer
PCT cache (rather than going to disk) during the interval.
GBL_MEM_QUEUE The average number of processes or kernel threads blocked on

memory (waiting for virtual memory disk accesses to complete)
GBL_MEM_SWAPOUT_ The number of swap outs per second during the interval.
RATE

User Guide
GBL_MEM_PAGEOUT_ The total number of page outs to the disk per second during the
RATE interval.
GBL_MEM_PG_SCAN_ The number of pages scanned per second by the pageout daemon
RATE during the interval.
MEMORY_SWAP_FREE
MEMORY_MEMFREE
MEMORY_PERCENT__
USED
SYSTEM_SWAPPING_
AND_SWITCHING_
ACTIVITY_SWPOT_S
CACHE_COPY_READ_
HITS_0D37
Multiple Global Forecasts

The following table lists the Metric names corresponding to the Multiple Global Forecasts graph
template.
GBL_CPU_TOTAL_UTIL Percentage of time the CPU was not idle during the interval.
GBL_SWAP_SPACE_ The percentage of available swap space that was being used by running
UTIL processes in the interval.
GBL_RUN_QUEUE This is the average number of threads waiting in the runqueue over the
interval.
GBL_MEM_PAGEOUT_ The total number of page outs to the disk per second during the interval.
RATE
GBL_NET_IN_PACKET_ The number of successful packets per second received through all
GBL_NET_OUT_ The number of successful packets per second sent through the network
PACKET_RATE interfaces during the interval.
GBL_ACTIVE_PROC The sum of the alive-process- time/interval-time ratios of every process

that is active (uses any CPU time) during an interval.
5MINAVG

User Guide
SYSTEM_
PROCESSOR_QUEUE_
LENGTH
Network Summary
The following table lists the Metric names corresponding to the Network Summary graph template.
GBL_NET_OUT_ The number of successful packets per second sent through the network
PACKET_RATE interfaces during the interval.
GBL_NET_IN_ The number of successful packets per second received through all
PACKET_RATE network interfaces during the interval.
GBL_NET_ERROR_ The number of errors per second on all network interfaces during the
RATE interval.
Seasonal CPU Forecast

The Metric name corresponding to the Seasonal CPU Forecast graph template is GBL_CPU_TOTAL_
System Configuration
The following table lists the Metric names corresponding to the System Configuration graph template.
GBL_SYSTEM_ID The network node hostname of the system.
GBL_MACHINE An ASCII string representing the Processor Architecture.
GBL_MACHINE_ The CPU model.

MODEL
GBL_CPU_CLOCK The clock speed of the CPUs in MHz if all of the processors have the
same clock speed.
GBL_OSNAME A string representing the name of the operating system.
GBL_OSVERSION A string representing the version of the operating system.
GBL_OSRELEASE The current release of the operating system.
GBL_MEM_PHYS The amount of physical memory in the system (in MBs unless otherwise
specified).
GBL_ACTIVE_CPU The number of CPUs online on the system.

User Guide
GBL_NUM_CPU The number of physical CPUs on the system. This includes all CPUs,
either online or offline.
GBL_NUM_DISK The number of disks on the system. Only local disk devices are counted in
this metric.
GBL_NUM_ The number of network interfaces on the system.

NETWORK
GBL_COLLECTOR ASCII field containing collector name and version.
GBL_SWAP_SPACE_ The total amount of potential swap space, in MB.

AVAIL
GBL_LOGGING_ A 13-byte field indicating the types of data logged by the collector.
TYPES
GBL_THRESHOLD_ The percentage of CPU that a process must use to become interesting
CPU during an interval.
GBL_GMTOFFSET The difference, in minutes, between local time and GMT.
MEMORY_SWAP_
FREE
MEMORY_
MEMTOTAL
CPU Comparison
The Metric name corresponding to the Seasonal CPU Forecast graph template is GBL_CPU_TOTAL_
Disk Throughput
The following table lists the Metric names corresponding to the Disk Throughput graph template.
BYDSK_PHYS_BYTE_ The average KBs per second transferred to or from this disk device
LOGICALDISK_DISK__
BYTES_SEC
Individual Networks
The following table lists the Metric names corresponding to the Individual Networks graph template.

User Guide
Metric
Names Metric Description
BYNETIF_ Number of KBs per second received from the network via this interface during the
IN_BYTE_ interval. Only the bytes in packets that carry data are included in this rate.
RATE
BYNETIF_ Number of KBs per second sent to the network via this interface during the interval.
OUT_BYTE_ Only the bytes in packets that carry data are included in this rate.
RATE
BYNETIF_ Number of successful physical packets per second received through the network
IN_PACKET_ interface during the interval.
RATE
BYNETIF_ Number of successful physical packets per second sent through the network
OUT_ interface during the interval. Successful packets are those that have been
PACKET_ processed without errors or collisions.
RATE
NETWORK_
INTERFACE_
IPKTS
NETWORK_
INTERFACE_
OPKTS
Individual CPUs
The Metric name corresponding to the Individual CPUs graph template is BYCPU_CPU_TOTAL_
UTIL. It is the percentage of time that this CPU was not idle during the interval.
Disk Space
The Metric name corresponding to the Disk Space graph template is FS_SPACE_UTIL. It is the
percentage of the file system space in use during the interval.
Disk Details
The following table lists the Metric names corresponding to the Disk Details graph template.
BYDSK_DEVNAME Name of the disk device
BYDSK_PHYS_ The average KBs per second transferred from this disk device during the
READ_BYTE_RATE interval.
BYDSK_PHYS_ The average number of physical reads per second for this disk device
READ_RATE during the interval.

User Guide
BYDSK_PHYS_ The average KBs per second transferred to this disk device during the
WRITE_BYTE_RATE interval.
BYDSK_PHYS_ The average number of physical writes per second for this disk device
WRITE_RATE during the interval.
BYDSK_UTIL The percentage of the time during the interval that the disk device had IO in
progress from the point of view of the Operating System.
BYDSK_REQUEST_ The average number of IO requests that were in the wait queue for this disk
QUEUE device during the interval.
BYDSK_AVG_ The average time, in milliseconds, that this disk device spent processing
SERVICE_TIME each disk request during the interval.
BYDSK_LOGL_ The number of logical reads per second for this disk device during the
READ_RATE interval.
BYDSK_LOGL_ The number of logical writes per second for this disk device during the
WRITE_RATE interval.
BYDSK_DIRNAME The name of the file system directory mounted on the disk device.
BYDSK_ID The ID of the current disk device.
PHYSICALDISK_
DISK_READS_SEC
PHYSICALDISK_
DISK_WRITES_SEC
FileSystem Details
The following table lists the Metric names corresponding to the FileSystem Details graph template.
FS_DIRNAME The path name of the mount point of the file system.
FS_SPACE_UTIL Percentage of the file system space in use during the interval.
FS_MAX_SIZE Maximum number that the file system could obtain if full, in MB.
FS_SPACE_USED The amount of file system space in MBs that is being used.
FS_SPACE_RESERVED The amount of file system space in MBs reserved for superuser
allocation.
FS_TYPE A string indicating the file system type.
FS_DEVNAME The path name string of the current device.

User Guide
FS_DEVNO The major and minor number of the file system.
FS_INODE_UTIL Percentage of the file system inodes in use during the interval.
FS_MAX_INODES Number of configured file system inodes
FS_BLOCK_SIZE The maximum block size of the file system, in bytes.
FS_FRAG_SIZE The fundamental file system block size, in bytes.
FILESYSTEMS_KBYTES
FILESYSTEMS_
10240D45BLOCKS
FILESYSTEMS_USED
FILESYSTEMS_AVAIL
FILESYSTEMS_FILESYSTEM
CPU Details
The following table lists the Metric names corresponding to the CPU Details graph template.
BYCPU_ID ID number of the CPU.
BYCPU_CPU_SYS_ The percentage of time that the CPU was in system mode during the
MODE_UTIL interval.
BYCPU_CPU_USER_ The percentage of time that the CPU was in user mode during the
MODE_UTIL interval.
BYCPU_CSWITCH_ The average number of context switches per second for this CPU
BYCPU_INTERRUPT_ The average number of device interrupts per second for this CPU
BYCPU_STATE A text string indicating the current state of a processor.
BYCPU_CPU_CLOCK The clock speed of the CPU in the current slot. The clock speed is in
MHz for the selected CPU.
BYCPU_CPU_TOTAL_ The percentage of time that this CPU was not idle during the interval.
UTIL
PROCESSOR_SYSTEM

User Guide
PROCESSOR_USER
PROCESSOR_
SYSEXEC
PROCESSOR_INFO_
CPU_MHZ
CPU_UTILIZATION_
0D37SYS
CPU_UTILIZATION_
0D37USR
Network Interface Details

The following table lists the Metric names corresponding to the Network Interface Details graph
template.
BYNETIF_NAME Name of the network interface
BYNETIF_IN_ The number of KBs per second received from the network via this interface
BYTE_RATE during the interval. Only the bytes in packets that carry data are included in
this rate.
BYNETIF_IN_ The number of successful physical packets per second received through the
PACKET_RATE network interface during the interval. Successful packets are those that
have been processed without errors or collisions.
BYNETIF_OUT_ The number of KBs per second sent to the network via this interface during
BYTE_RATE the interval. Only the bytes in packets that carry data are included in this
rate.
BYNETIF_OUT_ The number of successful physical packets per second sent through the
PACKET_RATE network interface during the interval. Successful packets are those that
have been processed without errors or collisions.
BYNETIF_QUEUE The length of the outbound queue at the time of the last sample.
BYNETIF_ The number of physical collisions per second on the network interface
COLLISION_RATE during the interval.
BYNETIF_ERROR_ The number of physical errors per second on the network interface during
RATE the interval.
NETWORK_
INTERFACE

User Guide
NETWORK_
INTERFACE_
RECEIVEBYTES
NETWORK_
INTERFACE_
RBYTES
NETWORK_
INTERFACE_
IPACKETS
NETWORK_
INTERFACE_
PACKETS__
RECEIVED_SEC
NETWORK_
INTERFACE_
TRANSMITBYTES
NETWORK_
INTERFACE_
OPACKETS
NETWORK_
INTERFACE_
PACKETS_SENT_
SEC
NETWORK_
INTERFACE_
COLLS
NETWORK__
INTERFACE_
COLLISIONS
NETWORK__
INTERFACE_ERRS
NETWORK_STATS
NETWORK_STATS_
IPKTS
NETWORK_STATS_
OPKTS
NETWORK_STATS_

User Guide
COLL
Virtualization Infrastructure Graph Templates

The following table lists the graph templates for Virtualization Infrastructure.
Graph Templates for Metric

Virtualization Infrastructure Metric Name Description
Virtualization Configurations GBL_SYSTEM_ID The network

node
hostname of
the system.
GBL_OSNAME A string
representing
the name of
the operating
system.
GBL_OSVERSION A string
representing
the version of
the operating
system.
GBL_OSRELEASE The current

release of the
operating
system.
GBL_LS_TYPE The
virtualization
technology if
applicable

User Guide

GBL_LS_ROLE Indicates
whether Perf
Agent is
installed on
logical system
or host or
standalone
system. This
metric will be
either
"GUEST",
"HOST" or
"STAND".
GBL_NUM_LS It indicates the

number of LS
hosted in a
system.
GBL_NUM_CPU The number of

physical
CPUs on the
system. This
includes all
CPUs, either
online or
offline.
BYLS_LS_ID An unique
identifier of the
logical
system.
BYLS_LS_NAME Name of the

computer.
BYLS_NUM_CPU The number of

virtual CPUs
configured for
this logical
system.

User Guide

BYLS_NUM_NETIF The number of

network
interfaces
configured for
this logical
system.
BYLS_NUM_DISK The number of

disks
configured for
this logical
system. Only
local disk
devices and
optical
devices
present on the
system are
counted in this
metric.
BYLS_LS_OSTYPE The Guest OS

the logical
system is
hosting
BYLS_CPU_ENTL_MIN The minimum

CPU units
configured for
the logical
system.
BYLS_CPU_ENTL_MAX The maximum

CPU units
configured for
a logical
system.

User Guide

BYLS_MEM_ENTL_MIN In a virtual
environment,
this metric
indicates the
minimum
amount of
memory
configured for
a logical
system (in
MB).
BYLS_MEM_ENTL_MAX In a virtual
environment,
this metric
indicates the
maximum
amount of
memory
configured for
a logical
system (in
MB).
CPU Entitlement by Logical BYLS_CPU_ENTL_MIN The minimum

Systems CPU units
configured for
the logical
system.
BYLS_CPU_ENTL_MAX The maximum

CPU units
configured for
a logical
system.
VMWARE_
GUARANTEED0D46SUMMATION0D910D93

User Guide

Percentage Utilization of CPU BYLS_CPU_ENTL_UTIL Percentage of

Entitlement by Logical Systems entitled
processing
units
(guaranteed
processing
units allocated
to this logical
system)
consumed by
the logical
system.
Percentage Utilization of Total BYLS_CPU_PHYS_TOTAL_UTIL Percentage of

Physical CPU by Logical total time the
Systems physical
CPUs were
utilized by this
logical system
during the
interval.
VMWARE_
USAGE0D46AVERAGE0D910D93
CPU Details of Logical System GBL_CPU_ENTL_UTIL Percentage of

entitled
processing
units
(guaranteed
processing
units allocated
to this logical
system)
consumed by
the logical
system.

User Guide

GBL_CPU_PHYS_USER_MODE_UTIL The
percentage of
time the
physical CPU
was in user
mode for the
logical system
during the
interval.
GBL_CPU_PHYS_SYS_MODE_UTIL The
percentage of
time the
physical CPU
was in system
mode (kernel
mode) for the
logical system
during the
interval.
GBL_CPU_PHYS_TOTAL_UTIL The
percentage of
time the
available
physical
CPUs were
not idle for this
logical system
during the
interval.
GBL_CPU_SHARES_PRIO The weightage

or priority
assigned to a
Uncapped
logical
system.
CPU__UTILIZATION_0D37SYS
CPU__UTILIZATION_0D37USR

User Guide

CPU Summary by Logical BYLS_LS_ID An unique

Systems identifier of the
logical
system.
BYLS_CPU_ENTL_UTIL Percentage of
entitled
processing
units
(guaranteed
processing
units allocated
to this logical
system)
consumed by
the logical
system.
BYLS_CPU_USER_MODE_UTIL On vMA, for a

host and a
logical
system, this
metric
indicates the
percentage of
time the CPU
was in user
mode during
the interval.
BYLS_CPU_SYS_MODE_UTIL On vMA, for a

host and a
logical
system, this
metric
indicates the
percentage of
time the CPU
was in system
mode.

User Guide

BYLS_CPU_PHYS_TOTAL_UTIL Percentage of
total time the
physical
CPUs were
utilized by this
logical system
during the
interval.
BYLS_CPU_SHARES_PRIO This metric

indicates the
weightage or
priority
assigned to a
Uncapped
logical
system.
VMWARE_
VMWARE_
READY0D46SUMMATION0D910D93
VMWARE_
EXTRA0D46SUMMATION0D910D93
Percentage Utilization of Memory BYLS_MEM_ENTL_UTIL The

Entitlement by Logical Systems percentage of
entitled
memory in use
during the
interval.
Memory Summary by Logical BYLS_LS_ID An unique

Systems identifier of the
logical
system.

User Guide

BYLS_MEM_ENTL_UTIL The
percentage of
entitled
memory in use
during the
interval. This
includes
system
memory
(occupied by
the kernel),
buffer cache
and user
memory.
BYLS_MEM_PHYS_UTIL On vMA, the

metric
indicates the
percentage of
physical
memory used
during the
interval by a
host, logical
system.
BYLS_MEM_SWAPPED PLATFORMS:
Linux On vMA,
for a host,
logical system
and resource
pool, this
metrics
indicates the
amount of
memory that
has been
transparently
swapped to
and from the
disk.

User Guide

BYLS_MEM_OVERHEAD The amount of

memory
associated
with a logical
system, that is
currently
consumed on
the host
system, due to
virtualization.
BYLS_MEM_SHARES_PRIO The weightage

or priority for
memory
assigned to
this logical
system.
VMWARE_
ACTIVE0D46AVERAGE0D910D93
VMWARE_
VMWARE_
SWAPPED0D46AVERAGE0D910D93
VMWARE_
OVERHEAD0D46AVERAGE0D910D93
CPU Entitlement Utilization BYLS_CPU_ENTL_UTIL Percentage of

Baseline entitled
processing
units
(guaranteed
processing
units allocated
to this logical
system)
consumed by
the logical
system.

User Guide

VMware ESX/ESXi Host BYLS_MEM_PHYS_UTIL The metric

Memory Utilization indicates the
percentage of
physical
memory used
during the
interval by a
host, logical
system.
VMware ESX/ESXi Host VMWARE_

Memory Utilization USAGE0D46AVERAGE0D910D93
VMware ESX/ESXi Host BYLS_MEM_PHYS_UTIL The metric

Memory Utilization Baseline indicates the
percentage of
physical
memory used
during the
interval by a
host, logical
system.
VMware ESX/ESXi Host VMWARE_

Memory Utilization Baseline USAGE0D46AVERAGE0D910D93
VMware ESX/ESXi Host Disk BYLS_DISK_UTIL The average

Utilization percentage of
time during the
interval
(average
utilization) that
all the disks
had IO in
progress.
VMware ESX/ESXi Host Disk VMWARE_

Utilization USAGE0D46AVERAGE0D910D93
VMware ESX/ESXi Host Disk VMWARE_READ0D46AVERAGE0D910D93

Utilization
VMware ESX/ESXi Host Disk VMWARE_

Utilization WRITE0D46AVERAGE0D910D93

User Guide

VMware ESX/ESXi Host - BYLS_NET_IN_BYTE Number of

Network MB bytes, in MB,
received
during the
interval.
VMware ESX/ESXi Host - BYLS_NET_OUT_BYTE Number of

Network MB bytes, in MB,
transmitted
during the
interval.
VMware ESX/ESXi Host - VMWARE_

Network MB USAGE0D46AVERAGE0D910D93
VMware ESX/ESXi - CPU BYLS_CPU_PHYS_TOTAL_UTIL Percentage of

Utilization across Resource total time the
Pools physical
CPUs were
utilized by the
logical system
during the
interval.
VMWARE_
IBM LPAR Frame level CPU BYLS_CPU_TOTAL_UTIL Percentage of

Utilization total time the
logical CPUs
were not idle
during this
interval.
IBM LPAR - CPU Utilization BYLS_NUM_CPU The number of

across Frame and LPARs virtual CPUs
configured for
the logical
system.
IBM LPAR - CPU Utilization BYLS_CPU_PHYSC This metric

across Frame and LPARs indicates the
number of
CPU units
utilized by the
logical
system.

User Guide

IBM LPAR - CPU Utilization (BYLS_NUM_CPU*(BYLS_CPU_TOTAL_ Number of

across Frame and LPARs UTIL/100)) CPU units
being used.
IBM LPAR - Memory Utilization BYLS_MEM_ENTL_UTIL The

across Frame and LPARs percentage of
entitled
memory in use
during the
interval. This
includes
system
memory
(occupied by
the kernel),
buffer cache
and user
memory.

Send Documentation Feedback
If you have comments about this document, you can contact the documentation team by email. If an
email client is configured on this system, click the link above and an email window opens with the
following information in the subject line:
Feedback on User Guide (OMi Management Pack for Infrastructure 1.12)
Just add your feedback to the email and click send.
If no email client is available, copy the information above to a new message in a web mail client, and
send your feedback to [email protected].
We appreciate your feedback!

OMi MGMT Infrastructure1.12 UserGuide

Uploaded by

Copyright:

Available Formats

OMi MGMT Infrastructure1.12 UserGuide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMi MGMT Infrastructure1.12 UserGuide

Uploaded by

Copyright:

Available Formats

HP OMi Management Pack for

Document Release Date: June 2015

Restricted Rights Legend

HP Software Solutions & Integrations and Best Practices

HP OMi Management Pack for Infrastructure (1.12) Page 2 of 178

Chapter 2: Getting Started 8

Chapter 3: Components of OMi MP for Infrastructure 18

HP OMi Management Pack for Infrastructure (1.12) Page 3 of 178

How to Access Extensive IBM Power Management Template 28

HP OMi Management Pack for Infrastructure (1.12) Page 4 of 178

Oracle Solaris Host Health 77

Chapter 4: Customizing OMi MP for Infrastructure 143

HP OMi Management Pack for Infrastructure (1.12) Page 5 of 178

Editing Infrastructure Management Templates 145

Chapter 5: Troubleshooting 147

Appendix: Graph Templates 148

Send Documentation Feedback 178

HP OMi Management Pack for Infrastructure (1.12) Page 6 of 178

l Ready-to-deploy, management solutions to suit different monitoring requirements.

l Aspects for creating customized solutions.

l Infrastructure element based deployment and configuration.

HP OMi Management Pack for Infrastructure (1.12) Page 7 of 178

Chapter 2: Getting Started

Task 1: Adding Nodes to the BSM 9.2x or OMi 10.x

Before you begin monitoring, you need to add the nodes:

1. Open the Monitored Nodes pane from Administration:

The newly created node is saved as a CI instance in RTSM.

Task 2: Deploying the Infrastructure Discovery Aspect

HP OMi Management Pack for Infrastructure (1.12) Page 8 of 178

Type of Node Aspects to be Deployed

Standalone Node Deploy the System Infrastructure Discovery Aspect.

Standalone Node Deploy the System Infrastructure Discovery Aspect.

ESX Host (Virtual Deploy the Virtual Infrastructure Discovery Aspect.

1. Open the Management Templates & Aspects pane:

HP OMi Management Pack for Infrastructure (1.12) Page 9 of 178

On OMi 10.x, click Administration > Monitoring > Deployment Jobs.

Task 3: Verifying the Discovery

1. Open the Event Perspective pane:

2. In the Browse Views tab, select the HACluster_Infrastructure, Sol_Zones_Infrastructure,

The CIs are populated in Browse Views.

Task 4: Deploying the Infrastructure Management

HP OMi Management Pack for Infrastructure (1.12) Page 10 of 178

Following are the four predefined frequency parameters:

Very High 5 mins

l After deployment using the Assignments & Tuning pane.

Task 4a: Identifying and Deploying Infrastructure

HP OMi Management Pack for Infrastructure (1.12) Page 11 of 178

1. Open the Management Templates & Aspects pane:

Task 4b: Deploying Infrastructure Aspects

HP OMi Management Pack for Infrastructure (1.12) Page 12 of 178

1. Open the Management Templates & Aspects pane:

Task 5: Updating the Management Templates and

For BSM 9.2x:

HP OMi Management Pack for Infrastructure (1.12) Page 13 of 178

3. Edit the parameters and redeploy to each of the Node CIs.

For OMi 10.x:

3. Click Show Assignments That Require an Update.

The Update Assigned Item dialog box appears.

5. In the Update Options tab, follow these steps: