HP Man SPI Systems Infrastructure 11.14 User PDF
HP Man SPI Systems Infrastructure 11.14 User PDF
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.
Copyright Notice
© Copyright 2008-2014 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 the Microsoft group of companies.
UNIX® is a registered trademark of The Open Group.
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: http://h20230.www2.hp.com/selfsolve/manuals
This site requires that you register for an HP Passport and sign in. To register for an HP Passport ID, go to: http://h20229.www2.hp.com/passport-registration.html
Or click the New users - please register link on the HP Passport login page.
You will also receive updated or new editions if you subscribe to the appropriate product support service. Contact your HP sales representative for details.
Support
Visit the HP Software Support Online web site at: http://www.hp.com/go/hpsoftwaresupport
This web site provides contact information and details about the products, services, and support that HP Software offers.
HP Software online 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:
http://h20229.www2.hp.com/passport-registration.html
To find more information about access levels, go to:
http://h20230.www2.hp.com/new_access_levels.jsp
HP Software Solutions Now accesses the HPSW Solution and Integration Portal Web site. This site enables you to explore HP Product Solutions to meet your
business needs, includes a full list of Integrations between HP Products, as well as a listing of ITIL Processes. The URL for this Web site is
http://h20230.www2.hp.com/sc/solutions/index.jsp
Contents
Contents 3
Chapter 1: Conventions Used in this Document 7
Chapter 2: Introduction 9
Chapter 3: Systems Infrastructure SPI Components 10
Map View on HPOM for Windows 10
Tools 13
Policies 13
Graphs 14
Reports 15
Discovery Policy 23
Restricting Discovery 23
Availability Policies 33
Capacity Policies 72
Performance Policies 90
Deploying SI SPI Policies from HPOM for Windows Management Server 118
Deploying SI SPI Policies from HPOM for UNIX Management Server 119
Convention Description
HPOM for UNIX HPOM for UNIX is used in the document to imply HPOM on HP-UX,
Linux, and Solaris.
l HPOM on HP-UX
l HPOM on Linux
l HPOM on Solaris
Infrastructure SPIs HP Operations Smart Plug-ins for Infrastructure. The software suite
includes three Smart Plug-ins:
Convention Description
$OvDataDir The data directory variable on HPOM for UNIX management server and
UNIX managed nodes. You must manually create this variable. The
data directory on all UNIX nodes and servers is as follows:
$OvInstallDir The install directory variable on HPOM for UNIX management server
and UNIX managed nodes. You must manually create this variable.
The install directory on all UNIX nodes and servers is as follows:
The Systems Infrastructure Smart Plug-ins (SI SPI) monitors the system infrastructure for the
Microsoft Windows, Linux, Oracle Solaris, IBM AIX, and HP-UX systems. The SI SPI helps to
analyze the system performance based on monitoring aspects such as capacity, availability, and
utilization.
The SI SPI is a part of the HP Operations Smart Plug-ins for Infrastructure suite (Infrastructure
SPIs). The other components in the suite include the Virtualization Infrastructure Smart Plug-ins (VI
SPI), the Cluster Infrastructure Smart Plug-ins (CI SPI), the Report pack, and the Graph pack.
Installation of SI SPI is mandatory while installing other components from the Infrastructure SPIs
media.
The SI SPI integrates with other HP software products such as the HP Operations Manager
(HPOM), HP Performance Manager, HP Performance Agent, and Embedded Performance
Component (EPC) of HP Operations agent. The integration provides policies, tools, and the
additional perspective of Service Views.
For information about the operating system versions supported by the SI SPI, see the HP
Operations Smart Plug-in for Systems Infrastructure Release Notes.
After you add a node to the HPOM console, the SI SPI service discovery policy is automatically
deployed to the nodes and adds discovered information to the HPOM Services area. This
information is used to populate the SI SPI map view for nodes and services.
The map view displays the real-time status of your infrastructure environment. To view, select
Services from the HPOM console, and click Systems Infrastructure. Map view graphically
represents the structural view of your entire service or node hierarchy in the infrastructure
environment including any subsystems or subservices. The following figure shows the Map view on
HPOM for Windows.
The icons and lines in your map are color-coded to indicate the severity levels of items in the map
and to show status propagation. Use the map view to drill down to the level in your node or service
hierarchy where a problem is occurring.
The graphical representation of discovered elements in the service views enables speedy diagnosis
of problems.
l To view the root cause of any problem indicated in your message browser, click View → Root
Cause.
l To display the services and system components affected by a problem, click View →
Impacted.
The map view displays the real-time status of your infrastructure environment. To ensure that the
operator can view the service map in the HPOM for HP-UX, Solaris, and Linux Operational
interface, run the following commands on the management server:
In this instance, <operator name> is the operator (for example, opc_adm or opc_op) to which you
want to assign the service.
The SI SPI service discovery policy does not automatically deploy policies to the nodes. You can
manually deploy these.
3. Select Services → Systems Infrastructure → Show Graph, to view the map view.
The map view graphically represents the structural view of your entire service or node hierarchy in
the infrastructure environment including any subsystems or subservices.
Tools
The SI SPI tools display data collected for a particular managed node. For information about the
tools provided by SI SPI, see "Systems Infrastructure SPI Tool" on page 121.
Policies
On HPOM for Windows, several default policies are automatically deployed on the supported
managed nodes during installation. These policies can be used as is to begin receiving system
infrastructure related data and messages from the environment. You can choose to turn off
automatic deployment of policies when services are discovered. In addition, you can modify and
save preconfigured policies with new names to create custom policies for your own specialized
purposes.
For information on deploying policies from the management server, see "Deploying SI SPI Policies
from HPOM for Windows Management Server" on page 118.
For HPOM for HP-UX, Linux, or Solaris, the SI SPI service discovery policy does not automatically
deploy policies to the nodes. You can manually deploy them.
For information on deploying policies from the management server, see "Deploying SI SPI Policies
from HPOM for UNIX Management Server" on page 119.
The SI SPI policies begin with SI for easy identification and modification. The policy types are as
follows:
l Service/Process Monitoring policies provide a means for monitoring system services and
processes.
l Logfile Entry policies capture status or error messages generated by the system nodes.
l Measurement Threshold policies define conditions for each metric so that the collected
metric values can be interpreted and alerts or messages can be displayed in the message
browser. Each measurement threshold policy compares the actual metric value against the
specified or auto threshold. A mismatch between the threshold and the actual metric value
generates a message and instruction text that helps you resolve a situation.
l Scheduled Task policies determine what metric values to collect and when to start collecting
metric. The policies define the collection interval. The collection interval indicates how often
data is collected for a specific group. The scheduled task policy has two functions: to run the
collector or analyzer at each collection interval on a node and to collect data for all metrics listed
within the polices’ Command text box.
l Service Discovery policy discovers individual system nodes instances and builds a map view
for all SI SPI discovered instances.
For more information about the policies provided by SI SPI, see "Systems Infrastructure SPI
Policies" on page 22.
Graphs
The SI SPI enables you to view and trace out the root cause of any discrepancy in the normal
behavior of an element being monitored. HPOM is integrated with HP Performance Manager, a
web-based analysis tool that helps you evaluate system performance, look at usage trends, and
compare performance between systems. Using HP Performance Manager you can see any of the
following:
l Baseline graphs
l Dynamic graphs in Java format that allow you to turn off display of individual metrics or hover
over a point on a graph and see the values displayed
You can view the data represented graphically for quick and easy analysis of a serious or critical
error message reported. For more information about the graphs provided by SI SPI, see "Systems
Infrastructure SPI Graphs" on page 125.
Reports
You can integrate the SI SPI by installing the HP Reporter to generate web-based reports on metric
data.
If HP Reporter is installed on the HPOM management server for Windows, you can view reports
from the console. To view a report, expand Reports in the console tree, and then double-click
individual reports.
If HP Reporter is installed on a separate system connected to the HPOM management server (for
Windows, UNIX, Linux, or Solaris operating system), you can view the reports on HP Reporter
system. For more information on integration of HP Reporter with HPOM, see HP Reporter
Installation and Special Configuration Guide.
For information about the reports provided by SI SPI, see "Systems Infrastructure SPI Reports" on
page 123.
The deployment checklist summarizes the tasks that you must complete before you start deploying
the policies.
Deployment Checklist
Complete
(Y/N) Tasks
1. Add the nodes that you want to monitor. When adding the nodes, the option of automatic
deployment of policies and packages is selected by default.
This option enables autodeployment of the following policies on the managed node:
n SI-SystemDiscovery
n InfraSPI-Messages
n OPC_OPCMON_OVERRIDE_THRESHOLD
n OPC_PERL_INCLUDE_INSTR_DIR
n AUTO_ADDITION_SETTINGS
In case of existing nodes (that were added before the installation of Infrastructure SPIs), or
where the automatic deployment of policies and packages check box was cleared while
adding the managed node, manually deploy these policies.
2. To access and deploy the policies (in any order) on the managed nodes, follow these options in
any order:
n OPC_OPCMON_OVERRIDE_THRESHOLD
n OPC_PERL_INCLUDE_INSTR_DIR
Note:
l To automatically add guest virtual machines, set the AutoAdd_Guests parameter in the
AUTO_ADDITION_SETTINGS policy to True. It is set as False by default.
l If a node is moved from one Windows management server to the other, make sure that you
clean up the variables in infraspi.nodegrp namespace. If these variables are not cleaned,
Auto Addition messages will not be triggered on the new Windows management server.
By default, QuickStart policies are assigned to these node groups. When a node is added to the
node group, these QuickStart policies get automatically deployed to the managed nodes (if policy
autodeployment is enabled).
After the infrastructure is discovered and the service map is populated on the HPOM for Windows
management server, the QuickStart policies are automatically deployed to the managed nodes (if
policy autodeployment is enabled). Available for all three Infrastructure SPIs, QuickStart policies
get you started immediately without having to spend much time customizing settings.
Autodeployment of policies is enabled by default. You can choose to turn off automatic deployment
of policies when services are discovered. In addition, you can modify and save preconfigured
policies with new names to create custom policies for your own specialized purposes.
The advanced policies are used in specific scenarios. You can manually deploy these policies as
required.
If you turned off autodeployment of policies, you can manually deploy the QuickStart policies by
accessing either of the two policies grouping provided by the Infrastructure SPIs. The groupings are
based on monitored aspects and vendor and operating system. The monitored aspects based
grouping helps you to access and deploy policies to monitor performance, availability, capacity,
logs, and security aspects across multiple operating systems. For example, to monitor availability
of scheduled job service on your infrastructure, expand:
The Policies grouped by Vendor help you to quickly access the policies relevant to your
operating system at one place. For example, to access SI-RHELCronProcessMonitor policy for
deploying it on a managed node, expand:
Before you start, make sure that you have installed the latest patches and hotfixes.
List of Patches
1. Add the nodes that you want to monitor on the management server. These nodes appear in the
Node Bank.
SI SPI creates the SI-Deployment node group and auto-assigns the following policies to the
node group:
n SI-SystemDiscovery
n SI-ConfigureDiscovery
n InfraSPI-Messages
n OPC_OPCMON_OVERRIDE_THRESHOLD
n OPC_PERL_INCLUDE_INSTR_DIR
n AUTO_ADDITION_SETTINGS
3. Deploy (distribute) the assigned policies and Infrastructure SPI instrumentation on the
managed nodes.
Note: To automatically add guest virtual machines, set the AutoAdd_Guests parameter in the
AUTO_ADDITION_SETTINGS policy to True. It is set as False by default.
By default, QuickStart policies are assigned to these node groups. When a node is added to the
node group, these QuickStart policies get assigned to the node automatically. You must then
deploy these policies manually on the node by selecting Deploy Configuration from the Actions
menu in the Admin GUI.
Available for all three Infrastructure SPIs, QuickStart policies get you started immediately without
having to spend much time customizing settings. Automatic assignment of policies is enabled by
default.
The groupings are based on monitored aspects and operating systems/vendor. The monitored
aspects based grouping helps you to access and deploy policies to monitor performance,
availability, capacity, logs, and security aspects across multiple operating systems. For example,
to monitor the availability of a scheduled job service on your infrastructure, select:
The policies grouped by operating system and vendor help you to quickly access the policies
relevant to your operating system at one place. For example, to access SI-CPUSpikeCheck policy
for deploying it on a managed node, select:
Policies grouped by operating system include two sub groups: QuickStart and Advanced. The
QuickStart group includes the policies that are used most often. The advanced policies like the disk
utilization policy and the disk capacity monitor policy are used in specific scenarios.
be CODA (HP Operations agent’s data store—also known as embedded performance component)
or HP Performance Agent.
To view graphs on HPOM for HP-UX, Linux, or Solaris you need to first integrate HP Performance
Manager with the HPOM management server.
l If HP Performance Manager is installed on the HPOM server, run the following command:
# /opt/OV/contrib/OpC/OVPM/install_OVPM.sh
install_OVPM.sh <nodename>:<port>
1. Copy the graph templates from the remote system where HP Performance Manager is
installed to the HPOM server. To learn about the graph types and their location on the system,
see HP Performance Manager Administrator Guide.
# /opt/OV/contrib/OpC/OVPM/install_OVPM.sh
install_OVPM.sh <nodename>:<port>
These steps set the host system configuration for HP Performance Manager, that is used when
launching graphs from events in the HPOM operator GUI.
2. Select Run.
Confirm that all the reports on the management server are in sync with the reports on the HP
Reporter GUI. Click the Reporter Status tab in the Reporter GUI to check for the number reports
sent to the console and also for any error message.
Managed Node
Reports Policies Platform SPI
To view reports for the Infrastructure SPIs from HPOM for Windows, expand Reports
Infrastructure Management → Systems Infrastructure in the console tree. To display a report,
select the desired report on the HPOM console, right-click, and then select Show report.
The folder Infrastructure Management group contains a subgroup arranged according to language.
For example, the subgroup for English policies is en, for Japanese language is ja, and for
Simplified Chinese language is zh.
In the console tree, the SI SPI policies are listed at the following location:
For information on deploying policies from the management server, see "Deploying SI SPI Policies
from HPOM for Windows Management Server" on page 118.
For HPOM for UNIX (HP-UX, Linux, or Solaris), the policy group on the console or Administration
interface is:
For information on deploying policies from the management server, see "Deploying SI SPI Policies
from HPOM for UNIX Management Server" on page 119. To access the policies on HPOM for
Windows, select the following:
For information on deploying policies from the management server, see "Deploying SI SPI Policies
from HPOM for Windows Management Server" on page 118.
Tracing
The policies for monitoring capacity and performance contain a script parameter for tracing: Debug
or DebugLevel. Using this parameter you can enable tracing. You can assign any of the following
values:
l Debug=2, trace messages will be logged in a trace file on the managed node. The trace file
location on managed node is $OvDataDir/Log
3. Select the Script-Parameters tab. The script parameters for that policy are listed.
You can also modify the parameter value based on your requirements. For information on how to
edit script parameter values, see HP Operations Smart Plug-in for Infrastructure Concepts Guide.
Discovery Policy
The SI-SystemDiscovery policy gathers service information from the managed nodes such as
hardware resources, operating system attributes, and applications.
Whenever you add a node to the appropriate node group in the HPOM console, the discovery
modules deployed along with the SI-SystemDiscovery policy run service discovery on the node.
These service discovery modules gather and send back the information to HPOM in the form of
XML snippets. These snippets generate a service tree that provides a snapshot of services
deployed on managed nodes at the time the SI SPI discovery process runs. After the first
deployment, the autodiscovery policy is set to run periodically. Each time the discovery agent runs,
it compares the service information retrieved with the results of the previous run. If the discovery
agent finds any changes or additions to the services running on the managed node since the
previous run, it sends a message to the HPOM management server, which updates the service
view with the changes. The default policy group for this policy is:
Restricting Discovery
The SI-ConfigureDiscovery policy is a ConfigFile policy that enables you to include or exclude the
discovery of specified resources on a virtual machine.
The SI-SystemDiscovery policy by default discovers all the services and resources running on a
node. You may however, not want to see all the resources in the service map.
To restrict discovery, you must deploy the SI-ConfigureDiscovery policy before running the
discovery policy.
The SI-ConfigureDiscovery policy has the configuration switch to include or exclude resources on
all for virtual machines across all the virtualization technologies that Infrastructure SPI supports.
After you deploy this policy to a node, it saves a configuration file SI-Discovery.cfg in the
following folder:
UNIX: /var/opt/OV/conf/sispi/configuration
Windows:%Ovdatadir%\Data\conf\sispi\configuration
#The resources which can be restricted or expanded for being discovered are
mentioned below:
#File System
#Disk
#Network
#CPU
#The values which can be part of the INCLUDE and EXCLUDE parameters with respect
to each of the resources can be as follows:
#FS include or exclude parameters should contain File system path(In general FS_
DIRNAME value)
# Example:
# FS_INCLUDE: /etc* Or
# FS_EXCLUDE: /zones*
#DSK include or exclude parameters should contain name of the Disk device(In
general BYDSK_DEVNAME value)
# Example:
# DSK_INCLUDE: vdc0 Or
# DSK_EXCLUDE: vdc1
# Example:
# NET_INCLUDE: lo0 Or
# NET_EXCLUDE: vnet0
#CPU include or exclude parameters should contain ID number of the CPU (In
general BYCPU_ID value)
# Example:
# CPU_INCLUDE: 0,1 Or
# CPU_EXCLUDE: 2,3
#For example if one wants to exclude 2 of the File Systems, then the following
entry should configured:
#FS_INCLUDE: /zones*,/etc*
#For example if one wants to add FS_EXCLUDE, then the following entry should be
configured separated with ":"
#FS_EXCLUDE: /zones*
FS_INCLUDE:
FS_EXCLUDE: /zones*
===
DSK_INCLUDE:
DSK_EXCLUDE:
===
NET_INCLUDE:
NET_EXCLUDE:
===
CPU_INCLUDE:
CPU_EXCLUDE:
To include or exclude resources from being discovered, edit the SIDiscovery.cfg file as per the
instructions provided in the file.
If you provide specific resource names under the INCLUDE parameter, SI discovery will discover
only those resources and show them in the service map. If you provide specific resource names
under the EXCLUDE parameter, SI discovery will not discover those resources and will not show
them in the service map.
You can either specify the entire resource name or use the wild card (*).
You can set only one parameter. It can be either EXCLUDE or INCLUDE. If you set values for both
the parameters or do not set values for either of the parameters, the SI discovery policy discovers
all the resources by default.
Note: If you set wrong instance values for the INCLUDE parameter, SI discovery will not
discover that specific resource instance and send the following alert message with severity
Warning to the HPOM console:
Improper usage as _INLUCDE parameter is not having the correct value.
However, if you set wrong instance values for the EXCLUDE parameter, SI discovery will
discover that resource instance.
The SI-SystemDiscovery policy sends the following alert message with severity Warning to the
HPOM console if it fails to open or read the SIDiscovery.cfg file:
Improper usage as both _INCLUDE and _EXCLUDE are configured.
Example
On an Oracle Solaris container with three non-global zones named email server, webserver1 and
webserver2, there may be several file systems like:
/etc/svc/volatile
/tmp
/var/run
/zones/emailserver/root/etc/svc/volatile
/zones/emailserver/root/tmp
/zones/emailserver/root/var/run
/zones/webserver1/root/etc/svc/volatile
/zones/webserver1/root/tmp
/zones/webserver1/root/var/run
/zones/webserver2/root/etc/svc/volatile
/zones/webserver2/root/tmp
/zones/webserver2/root/var/run
l If you want to discover only specific file systems, modify the SIDiscovery.cfg file by entering
one of the following values for the INCLUDE parameter:
n FS_INCLUDE:/zones/webserver2*
n FS_INCLUDE:/zones/webserver2/root/etc/svc/volatile
l If you do not want to discover specific file systems, modify the SIDiscovery.cfg file by
entering one of the following values for the EXCLUDE parameter:
n FS_EXCLUDE:/zones/emailserver*
n FS_EXCLUDE:/zones/emailserverroot/tmp
In this instance, <os> is the operating system of the managed node. The supported operating
systems are AIX, Debian, HP-UX, RHEL, SLES, Solaris, Ubuntu, and Windows. The following
tables list the processes and services along with the corresponding monitor policies that are
provided on the supported platforms.
Infrastructure SPIs provide availability policies for process monitoring on the Solaris zones. Solaris
machines have global and local zones (or containers). The policies monitor availability of Solaris
processes and send out an alert message to HPOM when not available.
Fax Service -
Firewall Service -
Network Services -
l SI-AIXLpdProcessMonitor
Terminal Services -
Apache SI-DebianApacheProcessMonitor
Cron SI-DebianCronProcessMonitor
Inetd SI-DebianInetdProcessMonitor
Named SI-DebianNamedProcessMonitor
Nmbd SI-DebianNmbdProcessMonitor
Samba SI-DebianSambaProcessMonitor
Sshd SI-DebianSshdProcessMonitor
Fax Service -
Firewall Service -
Network Services -
RPC Service -
l SI-OpenSshdProcessMonitor1
Terminal Services -
Fax Service -
l SI-LinuxSmbServerProcessMonitor
Firewall Service -
Network Services -
RPC Service -
l SI-OpenSshdProcessMonitor1
Terminal Services -
Fax Service -
l SI-LinuxSmbServerProcessMonitor
Firewall Service -
Network Services -
RPC Service -
l SI-OpenSshdProcessMonitor1
Terminal Services -
Fax Service -
Firewall Service -
Network Services -
RPC Service -
l SI-OpenSshdProcessMonitor1
Terminal Services -
Atd SI-UbuntuAtdProcessMonitor
Cron SI-UbuntuCronProcessMonitor
Inetd SI-UbuntuInetdProcessMonitor
Sshd SI-UbuntuSshdProcessMonitor
Udev SI-UbuntuUdevProcessMonitor
Email Service -
l SI-MSWindowsDFSRoleMonitor
l SI-MSWindowsFileServerRoleMonitor
l SI-MSWindowsNFSRoleMonitor
Internet Service -
l SI-MSWindowsNetworkPolicyServerRoleMonitor
l SI-MSWindowsTSGatewayRoleMonitor
l SI-MSWindowsTerminalServerRoleMonitor
l SI-MSWindowsTSLicensingRoleMonitor
1The policyis supported on AIX, HP-UX, Linux, MS windows, and Solaris operating systems.
Make sure you install openssh packages before deploying this policy on any of the supported
platforms.
Note: When the current process monitoring policy for Solaris is deployed on a global zone, the
SI SPI will monitor all processes running on global zone and non-global zone without
differentiating the zone that the process belongs to. Hence, to monitor processes running on
global zone, the threshold level must be set to include the non-global processes.
For example: If there are ‘x’ non-global zone processes that are part of a global zone, then the
threshold level must be set to include all the processes of global and non-global zones; x+1
You will get duplicate alerts if you deploy the same policy on a global and non-global zone,
where the non-global zone is part of the global zone.
l SI-CPUSpikeCheck
l SI-PerNetifInbyteBaseline-AT
l SI-PerNetifOutbyteBaseline-AT
l SI-PerDiskAvgServiceTime-AT
l SI-PerDiskUtilization-AT
Availability Policies
Availability monitoring helps to ensure adequate availability of resources. It is important to identify
unacceptable resource availability levels. The current load on IT infrastructure is computed and
compared with threshold levels to see if there is any shortfall in resource availability.
As the usage of IT resources changes, and functionality evolves, the amount of disk space,
processing power, memory, and other parameters also change. It is essential to understand the
current demands, and how they change over time. Monitoring these aspects over a period of time is
beneficial in understanding the impact on IT resource utilization.
A server role describes the primary function of the server such as fax server, email server, and so
on. A system can have one single server role or multiple server roles installed. Each server role can
include one or more role services described as sub-elements of a role. The availability policies
monitor the availability of role services on the managed nodes.
The availability policies monitor the availability of the processes and services on the Linux,
Windows, Solaris, AIX, and HP-UX managed nodes. The policies send a message to HPOM when
the process is unavailable or when the status of the service changes (for example, from running to
stopped or disabled). You can define the status to monitor and the action to take if the status
changes.
The availability policies are grouped based on the server roles and sub grouped based on the
operating system. You can select the required policy according to the operating system on the
managed node.
Required Configuration:
l To enable hardware monitoring, open the xpl config file on the node and add the following line
under the eaagt namespace:
n If you are using HP Operations agent 8.60, add:
[eaagt]
SNMP_SESSION_MODE=NO_TRAPD
SNMP_SESSION_MODE=NETSNMP
l On Linux nodes where SIM Agent is installed, open the SNMP configuration file located at
/etc/snmp/snmpd.conf and append the following line at the end:
trapsink <hostname of the node>
n NIC Agent
n Server Agent
n Storage Agent
If these are not installed, install HP Insight Management for the Windows Servers 2003/2008 x64
Editions.
a. Click Start → Run → type services.msc. The Services dialog box opens.
3. To change the XPL configuration settings on the managed node, type the command:
# ovconfchg -ns eaagt -set SNMP_TRAP_PORT <any allowed port>
5. To return all the attributes in the eaagt namespace, type the command:
# ovconfget eaagt
The SI-HPProLiant_CPQHLTHTraps policy intercepts SNMP traps related to the health of the
server and sends an alert to the HPOM console every time a trap is generated. The policy monitors
the following SNMP traps:
1.3.6.1.2.1.11.6.0 coldStart.
1.3.6.1.2.1.11.6.1 warmStart.
1.3.6.1.2.1.11.6.2 linkDown.
1.3.6.1.2.1.11.6.3 linkUp.
1.3.6.1.4.1.232.0.6055 The Fault Tolerant Fans have returned to a redundant state for the
specified chassis.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
The SI-HPProLiant_CPQRCTraps policy intercepts SNMP traps related to the performance and
availability of the RAID Controller and sends an alert to the HPOM console every time a trap is
generated. The policy monitors the following traps:
1.3.6.1.4.1.232.141.3.8.6.26 cpqCrExpCabTemperatureWarningTrap.
1.3.6.1.4.1.232.141.3.8.0.22 One of the power supplies in the expansion cabinet has failed.
1.3.6.1.4.1.232.141.3.7.0.16 One of the cooling fans in the primary enclosure has failed.
.1.3.6.1.4.1.232.141.3.5.6.31 cpqCrPhyDiskFailureTrap.
1.3.6.1.4.1.232.141.3.7.0.17 One of the cooling fans in the primary enclosure has recovered.
1.3.6.1.4.1.232.141.3.5.6.30 cpqCrPhyDiskInformationTrap.
1.3.6.1.4.1.232.141.3.8.0.21 One of the cooling fans in the expansion cabinet has recovered.
1.3.6.1.4.1.232.141.3.7.0.18 One of the power supplies in the primary enclosure has failed.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
The SI-HPProLiant_CPQNICTraps policy intercepts SNMP traps related to the performance and
availability of the Network Interface Card (NIC) and sends an alert to the HPOM console every time
a trap is generated. The policy monitors the following traps:
1.3.6.1.2.1.11.6.2 linkDown.
1.3.6.1.2.1.11.6.3 linkUp.
1.3.6.1.4.1.232.0.18006 Connectivity lost for logical adapter in slot contained in SNMP Varbind
3, port contained in SNMP Varbind 4.
1.3.6.1.4.1.232.6.18012 cpqNic3ConnectivityLost.
1.3.6.1.4.1.232.6.18011 cpqNic3ConnectivityRestored.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
The SI-HPProLiant_CPQCMCTraps policy intercepts SNMP traps related to the health of the
Console Management Controller (CMC) in terms of power consumption, smoke, humidity,
temperature, and fan. The policy sends an alert to the HPOM console every time a trap is
generated.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.232.0.2006 The Memory Module ECC status has been set to OK.
1.3.6.1.4.1.232.0.2005 The Memory Module ECC status has been set to degraded.
1.3.6.1.4.1.232.0.2009 Hot Plug Slot Board Inserted into Chassis contained in SNMP Varbind
3, Slot contained in SNMP Varbind 4.
1.3.6.1.4.1.232.0.2010 Hot Plug Slot Board Failed in Chassis contained in SNMP Varbind 3,
Slot contained in SNMP Varbind 4, Error contained in SNMP ind 5.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.11.5.7.5.2.1.2.0.5 vcFcFabricManagedStatusChange
1.3.6.1.4.1.11.5.7.5.2.1.2.0.3 vcCheckpointCompleted
1.3.6.1.4.1.11.5.7.5.2.1.2.0.9 vcProfileManagedStatusChange
1.3.6.1.4.1.11.5.7.5.2.1.2.0.6 vcModuleManagedStatusChange
1.3.6.1.4.1.11.5.7.5.2.1.2.0.8 vcPhysicalServerManagedStatusChange
1.3.6.1.4.1.11.5.7.5.2.1.2.0.1 vcDomainManagedStatusChange
1.3.6.1.4.1.11.5.7.5.2.1.2.0.2 vcCheckpointTimeout
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.232.154.2.5 cpqRPMTrapDeviceSettingsChanged
1.3.6.1.4.1.232.154.2.10051 A CMC device has entered an alarm condition for auxiliary input 1
1.3.6.1.4.1.232.154.2.10053 A CMC device has entered an alarm condition for auxiliary input 2
1.3.6.1.4.1.232.154.2.20001 cpqRPMTrapUPSInputVoltageBelowMin
1.3.6.1.4.1.232.154.2.20002 cpqRPMTrapUPSInputVoltageAboveMax
1.3.6.1.4.1.232.154.2.20003 cpqRPMTrapUPSInputVoltageNormal
1.3.6.1.4.1.232.154.2.20011 cpqRPMTrapUPSOutputVoltageBelowMin
1.3.6.1.4.1.232.154.2.20012 cpqRPMTrapUPSOutputVoltageAboveMax
1.3.6.1.4.1.232.154.2.20022 cpqRPMTrapUPSBatteryDepleted
1.3.6.1.4.1.232.154.2.20023 cpqRPMTrapUPSBatteryLevelNormal
1.3.6.1.4.1.232.154.2.20032 cpqRPMTrapUPSOnBypass
1.3.6.1.4.1.232.154.2.20101 cpqRPMTrapUPSTemperatureLow
1.3.6.1.4.1.232.154.2.20102 cpqRPMTrapUPSTemperatureHigh
1.3.6.1.4.1.232.154.2.20162 A UPS device is reporting bypass not available error has been
cleared
1.3.6.1.4.1.232.154.2.20171 cpqRPMTrapUPSUtilityFail
1.3.6.1.4.1.232.154.2.20172 cpqRPMTrapUPSUtilityFailCleared
1.3.6.1.4.1.232.154.2.20181 cpqRPMTrapUPSUtilityNotPresent
1.3.6.1.4.1.232.154.2.20182 cpqRPMTrapUPSUtilityNotPresentCleared
1.3.6.1.4.1.232.154.2.20191 cpqRPMTrapUPSBypassManualTurnedOn
1.3.6.1.4.1.232.154.2.20192 cpqRPMTrapUPSBypassManualTurnedOff
1.3.6.1.4.1.232.154.2.21033 The UPS has been powered off with user interaction
1.3.6.1.4.1.232.154.2.21053 A UPS device is reporting batteries are not connected to the UPS
1.3.6.1.4.1.232.154.2.50001 cpqRPMTestTrap
1.3.6.1.4.1.232.154.2.29999 cpqRPMTrapUPSDCStartOccurredCleared
1.3.6.1.4.1.232.154.2.29998 cpqRPMTrapUPSDCStartOccurred
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.232.0.3006 Intelligent Drive Array Accelerator lost battery power. Data Loss
possible.
1.3.6.1.4.1.232.0.3013 Intelligent Drive Array Accelerator lost battery power. Data loss
possible.
1.3.6.1.4.1.232.0.3021 Intelligent Drive Array Tape Library Door Status is OPEN, status
is contained in SNMP Varbind 7.
1.3.6.1.4.1.232.0.3022 Intelligent Drive Array Tape Drive Status is MISSING WAS OK,
status is contained in SNMP Varbind 7.
1.3.6.1.4.1.232.0.3026 Intelligent Drive Array Accelerator lost battery power. Data Loss
possible.
1.3.6.1.4.1.232.0.3028 Intelligent Drive Array Controller Board has cable problem, status
is contained in SNMP Varbind 4.
1.3.6.1.4.1.232.0.3032 Intelligent Drive Array Tape Drive status is MISSING WAS OK,
status is contained in SNMP Varbind 10.
1.3.6.1.4.1.232.0.3039 Intelligent Drive Array Accelerator lost battery power. Data Loss
possible.
1.3.6.1.4.1.232.0.3042 Intelligent Drive Array Tape Library Door Status is OPEN, status
is contained in SNMP Varbind 11.
1.3.6.1.4.1.232.0.3043 Intelligent Drive Array Tape Drive Status is MISSING WAS OK,
status is contained in SNMP Varbind 11.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.232.0.22002 The enclosure name has changed to SNMP Varbind 5 in rack SNMP
Varbind 3.
1.3.6.1.4.1.232.0.22003 The enclosure in SNMP Varbind 5 has been removed from rack SNMP
Varbind 3.
1.3.6.1.4.1.232.0.22004 The enclosure in SNMP Varbind 5 has been inserted into rack SNMP
Varbind 3.
1.3.6.1.4.1.232.0.22008 The enclosure in SNMP Varbind 5 fan in rack SNMP Varbind 3 has
been set to failed.
1.3.6.1.4.1.232.0.22009 The enclosure in SNMP Varbind 5 fan in rack SNMP Varbind 3 has
been set to degraded.
1.3.6.1.4.1.232.0.22010 The enclosure in SNMP Varbind 5 fan in rack SNMP Varbind 3 has
been set to ok.
1.3.6.1.4.1.232.0.22011 The enclosure in SNMP Varbind 5 fan in rack SNMP Varbind 3 has
been removed.
1.3.6.1.4.1.232.0.22012 The enclosure in SNMP Varbind 5 fan in rack SNMP Varbind 3 has
been inserted.
1.3.6.1.4.1.232.0.22019 The rack power supply detected an input line voltage problem in power
supply SNMP Varbind 6, enclosure in SNMP Varbind 5, rack in SNMP
Varbind 3.
1.3.6.1.4.1.232.0.22021 The server shutdown due to lack of power blade SNMP Varbind 6, in
enclosure SNMP Varbind 5, in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22026 Server power on via manual override on blade SNMP Varbind 6,in
enclosure SNMP Varbind 5, in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22027 Fuse open fuse SNMP Varbind 6, in enclosure SNMP Varbind 5,in
rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22029 Server blade in SNMP Varbind 6 inserted from position SNMP Varbind
7,in enclosure SNMP Varbind 5,in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22034 Power subsystem load balancing wire missing for enclosure SNMP
Varbind 5, in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22035 Power subsystem has too many power enclosures SNMP Varbind 5,
in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22042 A server blade e-keying has failed and there is a port mapping problem
between a server mezz card and the interconnect, in Blade SNMP
Varbind 6, in position SNMP Varbind 7,in enclosure SNMP Varbind
5,in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22041 The Onboard Administrator has taken the role of primary in enclosure
SNMP Varbind 5, in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22046 The interconnect status has been set to failed, in interconnect SNMP
Varbind 6, in position SNMP Varbind 7, in enclosure SNMP Varbind 5,
in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22048 The interconnect status has been set to ok, in interconnect SNMP
Varbind 6, in position SNMP Varbind 7, in enclosure SNMP Varbind 5,
in rack SNMP Varbind 3.
1.3.6.1.4.1.232.0.22052 cpqRackServerBladeStatusRepaired
1.3.6.1.4.1.232.0.22053 cpqRackServerBladeStatusDegraded
1.3.6.1.4.1.232.0.22054 cpqRackServerBladeStatusCritical
1.3.6.1.4.1.232.0.22055 cpqRackServerBladeGrpCapTimeout
1.3.6.1.4.1.232.0.22056 cpqRackServerBladeUnexpectedShutdown
1.3.6.1.4.1.232.0.22057 cpqRackServerBladeMangementControllerFirmwareUpdating
1.3.6.1.4.1.232.0.22058 cpqRackServerBladeMangementControllerFirmwareUpdateComplete
1.3.6.1.4.1.232.0.22059 cpqRackServerBladeSystemBIOSFirmwareUpdating
1.3.6.1.4.1.232.0.22060 cpqRackServerBladeSystemBIOSFirmwareUpdateCompleted
1.3.6.1.4.1.232.0.22061 cpqRackServerBladeFrontIOBlankingActive
1.3.6.1.4.1.232.0.22062 cpqRackServerBladeRemoteFrontIOBlankingInactive
1.3.6.1.4.1.232.0.22063 cpqRackServerBladeDiagnosticAdaptorInserted
1.3.6.1.4.1.232.0.22064 cpqRackServerBladeDiagnosticAdaptorRemoved
1.3.6.1.4.1.232.0.22064 cpqRackServerBladeDiagnosticAdaptorRemoved
1.3.6.1.4.1.232.0.22065 cpqRackServerBladeEnteredPXEBootMode
1.3.6.1.4.1.232.0.22066 cpqRackServerBladeExitedPXEBootMode
1.3.6.1.4.1.232.0.22067 cpqRackServerBladeWarmReset
1.3.6.1.4.1.232.0.22068 cpqRackServerBladePOSTCompleted
1.3.6.1.4.1.232.0.22069 cpqRackServerBladePoweredOn
1.3.6.1.4.1.232.0.22070 cpqRackServerBladePoweredOff
1.3.6.1.4.1.232.0.22071 cpqRackInformationalEAETrap
1.3.6.1.4.1.232.0.22072 cpqRackMinorEAETrap
1.3.6.1.4.1.232.0.22073 cpqRackMajorEAETrap
1.3.6.1.4.1.232.0.22074 cpqRackCriticalEAETrap
1.3.6.1.4.1.232.0.22075 cpqRackPowerMinorEAETrap
1.3.6.1.4.1.232.0.22076 cpqRackPowerMajorEAETrap
1.3.6.1.4.1.232.0.22077 cpqRackPowerCriticalEAETrap
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.232.0.12013 cpqUpsGenericCritical
1.3.6.1.4.1.232.0.12014 cpqUpsGenericInfo
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
The SI-HPProLiant_BladeType2Traps policy intercepts SNMP traps related to Blade Type 2. The
policy sends an alert to the HPOM console every time a trap is generated.
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.1 bt2SwPrimaryPowerSupplyFailure
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.35 bt2SwUfdfoLtMUP
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.32 bt2SwFanFailure
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.48 bt2SwHotlinksBackupUp
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.46 bt2SwHotlinksMasterUp
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.17 bt2SwVrrpNewBackup
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.36 bt2SwUfdfoGlobalEna
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.28 bt2SwSaveComplete
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.37 bt2SwUfdfoGlobalDis
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.2 bt2SwDefGwUp
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.47 bt2SwHotlinksMasterDn
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.38 bt2SwUfdfoLtDAutoEna
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.5 bt2SwDefGwNotInService
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.41 bt2SwCubeRemoved
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.49 bt2SwHotlinksBackupDn
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.27 bt2SwApplyComplete
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.45 bt2SwCistTopologyChanged
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.16 bt2SwVrrpNewMaster
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.40 bt2SwCubeInserted
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.29 bt2SwFwDownloadSucess
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.18 bt2SwVrrpAuthFailure
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.34 bt2SwUfdfoLtMFailure
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.44 bt2SwStgTopologyChanged
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.3 bt2SwDefGwDown
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.4 bt2SwDefGwInService
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.42 bt2SwStgNewRoot
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.50 bt2SwHotlinksNone
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.22 bt2SwTempExceedThreshold
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.31 bt2SwTempReturnThreshold
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.39 bt2SwUfdfoLtDAutoDis
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.30 bt2SwFwDownloadFailure
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.33 bt2SwFanFailureFixed
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.43 bt2SwCistNewRoot
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.26 bt2SwRackLocationChange
1.3.6.1.4.1.11.2.3.7.11.33.1.2.7.19 bt2SwLoginFailure
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
1.3.6.1.4.1.232.0.8001 This unit does not support fan monitoring, status contained in SNMP
Varbind 1.
1.3.6.1.4.1.232.0.8018 Storage System power supply UPS status changed to OK, status is
contained in SNMP Varbind 6.
1.3.6.1.4.1.232.0.8018 Storage System power supply UPS status changed to Battery low,
status is contained in SNMP Varbind 6.
1.3.6.1.4.1.232.0.8025 Storage system recovery server option status changed to OK, status
is contained in SNMP Varbind 5.
1.3.6.1.4.1.232.0.8028 Storage System power supply unit status is OK, status is contained
in SNMP Varbind 9.
The policy contains a rule for each of these SNMP traps. After the problem is resolved the previous
alert message is automatically acknowledged.
The SI-HPProLiant_VCModuleTraps policy intercepts the SNMP trap related to virtual connect
module. The policy sends an alert to the HPOM console every time the trap is generated.
1.3.6.1.4.1.11.5.7.5.2.3.2.11 vcModPortInputUtilizationUp
The policy contains a rule for this SNMP trap. After the problem is resolved the previous alert
message is automatically acknowledged.
Capacity Policies
Capacity monitoring helps to deliver performance at the required service level and cost. It ensures
that the capacity of the IT infrastructure corresponds to the evolving demands of the business. It
helps identify the under utilized and over utilized resources. Monitoring these aspects over a period
of time is beneficial in understanding the impact on IT resource utilization. You can analyze current
and historical performance of systems resources to accurately predict future capacity needs. The
default policy group for these policies is:
This policy monitors capacity parameters of the disks on the managed node. For each disk, the
policy checks for space utilization and free space available. In case the free space availability or
space utilization exceeds the threshold values specified, the policy sends out an alert to the HPOM
console.
This policy supports the use of wildcard characters '*' and '?' and using default values for all the
script parameters. For more information, see Using wildcard characters for all script parameters
and Using default values for all script parameters.
FS_SPACE_USED
FS_SPACE_UTIL
FS_TYPE
FS_DIRNAME
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
SpaceUtilCriticalThreshold The threshold is expressed as the space utilized on the disk. Set
the threshold value at which you want to receive a critical
message.
SpaceUtilMajorThreshold Set the threshold value at which you want to receive a major
message.
SpaceUtilMinorThreshold Set the threshold value at which you want to receive a minor
message.
SpaceUtilWarningThreshold Set the threshold value at which you want to receive a warning
message.
FreeSpaceCriticalThreshold The threshold is expressed as the free space (in MBs) available
on the disk or filesystem. Set the threshold value for minimum
free space on the disk, below which you want to receive a critical
message.
FreeSpaceMajorThreshold Set the threshold value for minimum free space on the disk,
below which you want to receive a major message.
FreeSpaceMinorThreshold Set the threshold value for minimum free space on the disk,
below which you want to receive a minor message.
FreeSpaceWarningThreshold Set the threshold value for minimum free space on the disk,
below which you want to receive a warning message.
InodeUtilMajorThreshold Set the threshold value at which you want to receive a major
message.
InodeUtilMinorThreshold Set the threshold value at which you want to receive a minor
message.
InodeUtilWarningThreshold Set the threshold value at which you want to receive a warning
message.
ExcludeFilesystems Specify the filesystems or the file system types that you want to
exclude from monitoring. If both filesystem and filesystem type
are specified, then the filesystem type takes precedence over
filesystem.
You can set different thresholds for the drives or filesystems on the managed node. The policy
parameters can take multiple comma separated values for setting these thresholds. These are
described in the following examples:
l FreeSpaceMinorThreshold=45
In this example, the threshold value is set at 45 MB for all disks or filesystems on the managed
node. If the free space available on disks or filesystems falls below the threshold value, the policy
sends a minor severity alert.
l SpaceUtilCriticalThreshold=80,/=65,c:=65
In this example, the threshold values are set at 65% for the '/' and 'C:' drives, and 80% for all other
drives/filesystems on the managed node. If the system utilization for these drives/filesystems
exceeds the threshold values, the policy sends out a critical alert.
l FreeSpaceMajorThreshold=256,E:=200,F:=512,c:=1024,/=1024
In this example, the threshold values are set at 200 for 'E:' drive, 512 for 'F:' drive, 1024 for 'C:'
drive, 1024 for '/' drive, and 256 for the remaining drives on the managed node. If the free space
available falls below the threshold values, the policy sends a major alert.
Using wildcard characters '*' and '?' for all script parameters
Use '*' to match one or more characters and '?' to match exactly one character. These are
described in the following examples:
l ExcludeFilesystems=/,/boot,/v*/?log
In this example, filesystems '/', '/boot' and filesystem such as '/var/vlog' that match the pattern
'/v*/?log', are excluded from monitoring.
The following examples show the use of wildcard characters for filesystems:
n /var/? match filesystems with names /var/a, /var/b but does not match filesystems with
names /var/abc, /var/xyzh.
n /var/??log match filesystems with names /var/ablog, /var/fslog but does not match
filesystems with names /var/alog, /var/log.
n /var*/?log match filesystems with names /var1/alog, /var123/blog but does not match
filesystems with names /var/log, /var123/log, /var/1log.
Specify default values for the script parameters. The policies only work if there are default values
without overriding the filesystem names. These are described in the following examples:
l SpaceUtilMinorThreshold=80,/=30,/boot=40
In this example, 30 is the threshold for '/', 40 is the threshold for '/boot' and 80 is the default
threshold for the rest of the filesystems.
l SpaceUtilMinorThreshold=/=30
The parameters specified in this example are not correct. You should always specify a default
value.
l MessageGroup=OS,/tmp=unix_admin,/ora/*=dba,/var/log?=unix_admin
In this example:
unix_admin is the message group assigned for alerts generated for /tmp filesystem.
dba is the message group assigned for alerts generated for filesystems beginning with /ora/
followed by 1 or more characters.
unix_admin is the message group assigned for alerts generated for filesystems beginning with
/var/log followed by exactly 1 character.
OS is the message group assigned for alerts generated for the rest of the filesystems.
Note: The threshold values for this policy must be set as an integer or decimal number with a
maximum of two digits to the right of the decimal point.
GBL_SWAP_SPACE_UTIL
HP-UX
IBM AIX
Oracle Solaris
Script-Parameter Description
FreeSwapSpaceAvailMajorThreshold Set the threshold value for minimum free swap space
on the disk at which you want to receive a major
severity message.
FreeSwapSpaceAvailMinorThreshold Set the threshold value for minimum free swap space
on the disk at which you want to receive a minor
severity message.
FreeSwapSpaceAvailWarningThreshold Set the threshold value for minimum free swap space
on the disk at which you want to receive a warning
severity message.
This policy monitors the overall memory usage by operating systems. The policy uses the
automatic threshold determination to automatically calculate the threshold values according to the
memory usage on previous days.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplication Type an appropriate value that helps you identify the messages sent by
the policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as
‘3600 seconds’. This period moves with the current time. The most
recent 3600-second (1-hour) period becomes the current baseline
period.
WarningDeviations Displays the number of standard deviation away from normal at which
the policy will send a warning message to HPOM console. Set an
appropriate value for the parameter. To disable the parameter, set value
as 5.
MinorDeviations Displays the number of standard deviation away from normal at which
the policy will send a minor message to HPOM console. Set an
appropriate value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which
the policy will send a major message to HPOM console. Set an
appropriate value for the parameter greater than the specified value for
MinorDeviations. To disable the parameter, set value as 5.
MemUtilCutOff Set a value below which you do not want to monitor memory utilization.
This policy monitors the overall swap space used by the systems on the managed node. The policy
uses the automatic threshold determination to automatically calculate the threshold values
according to the swap space usage on previous days.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplication Type an appropriate value that helps you identify the messages sent by
the policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as
‘3600 seconds’. This period moves with the current time. The most
recent 3600-second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum swap space usage as indicated by the metric.
MaximumValue Displays the maximum swap space usage as indicated by the metric.
WarningDeviations Displays the number of standard deviation away from normal at which
the policy will send a warning message to HPOM console. Set an
appropriate value for the parameter. To disable the parameter, set value
as 5.
MinorDeviations Displays the number of standard deviation away from normal at which
the policy will send a minor message to HPOM console. Set an
appropriate value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which
the policy will send a major message to HPOM console. Set an
appropriate value for the parameter greater than the specified value for
MinorDeviations. To disable the parameter, set value as 5.
WarningHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by
the value specified in WarningDeviations. To disable the parameter, set
value as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by
the value specified in MinorDeviations. To disable the parameter, set
value as none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by
the value specified in MajorDeviations. To disable the parameter, set
value as none.
WarningLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in WarningDeviations. To disable the parameter, set
value as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in MinorDeviations. To disable the parameter, set
value as none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in MajorDeviations. To disable the parameter, set
value as none.
SwapUtilCutOff Set a value below which you do not want to monitor swap utilization.
This policy monitors the utilization for each CPU on the managed node. This policy processes each
CPU instance separately for every interval. The policy uses automatic threshold determination to
automatically calculate the threshold values according to the CPU utilization on previous days.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplication Type an appropriate value that helps you identify the messages sent by
the policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as
‘3600 seconds’. This period moves with the current time. The most
recent 3600-second (1-hour) period becomes the current baseline period.
WarningDeviations Displays the number of standard deviation away from normal at which
the policy will send a warning message to HPOM console. Set an
appropriate value for the parameter. To disable the parameter, set value
as 5.
MinorDeviations Displays the number of standard deviation away from normal at which
the policy will send a minor message to HPOM console. Set an
appropriate value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which
the policy will send a major message to HPOM console. Set an
appropriate value for the parameter greater than the specified value for
MinorDeviations. To disable the parameter, set value as 5.
WarningHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by
the value specified in WarningDeviations. To disable the parameter, set
value as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by
the value specified in MinorDeviations. To disable the parameter, set
value as none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by
the value specified in MajorDeviations. To disable the parameter, set
value as none.
WarningLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in WarningDeviations. To disable the parameter, set
value as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in MinorDeviations. To disable the parameter, set
value as none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in MajorDeviations. To disable the parameter, set
value as none.
CPUUtilCutOff Set a value below which you do not want to monitor CPU utilization.
Script-Parameter Description
SpaceUtilMajorThreshold Set the threshold value for minimum free space on the drive
at which you want to receive a major severity message.
SpaceUtilMinorThreshold Set the threshold value for minimum free space on the drive
at which you want to receive a minor severity message.
SpaceUtilWarningThreshold Set the threshold value for minimum free space on the drive
at which you want to receive a warning severity message.
AssignMessageToRemoteHost Set the value to 1 to display the source of the alert message
as the remote host. By default, the messages are assigned
to the managed node from which the message is sent out.
The SI-LinuxNfsUtilizationMonitor policy monitors space utilization level for NFS remote
filesystems on Linux platforms. The default policy group for the policy is:
Script-Parameter Description
SpaceUtilMajorThreshold Set the threshold value for minimum free space on the
filesystem at which you want to receive a major severity
message.
SpaceUtilMinorThreshold Set the threshold value for minimum free space on the
filesystem at which you want to receive a minor severity
message.
SpaceUtilWarningThreshold Set the threshold value for minimum free space on the
filesystem at which you want to receive a warning severity
message.
NfsFileSystemType Specify the filesystem type that you would like to monitor for
space utilization level. For example, if you specify NFS, the
policy will monitor all NFS remote filesystems for space
utilization level.
AssignMessageToRemoteHost Set the value to 1 to display the source of the alert message as
the remote host. By default, the messages are assigned to the
managed node from which the message is sent out.
The SI-LinuxCifsUtilizationMonitor policy monitors space utilization level for CIFS remote
filesystems on Linux platforms. The default policy group for the policy is:
Script-Parameter Description
SpaceUtilMajorThreshold Set the threshold value for minimum free space on the
filesystem at which you want to receive a major severity
message.
SpaceUtilMinorThreshold Set the threshold value for minimum free space on the
filesystem at which you want to receive a minor severity
message.
SpaceUtilWarningThreshold Set the threshold value for minimum free space on the
filesystem at which you want to receive a warning severity
message.
CifsFileSystemType Specify the filesystem type that you would 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. The policy can be used to monitor cifs and
smb file system types.
AssignMessageToRemoteHost Set the value to 1 to display the source of the alert message as
the remote host. By default, the messages are assigned to the
managed node from which the message is sent out.
The SI-MSWindowsPagedPoolUtilization policy monitors the memory when the registry data is
written to the paging file. The SI-MSWindowsNonPagedPoolUtilization policy monitors the memory
that stores the data when the system is unable to handle page faults. The default policy group for
the policy is:
GBL_MEM_NONPAGED_POOL_BYTES
Script-Parameter Description
BaselinePeriod Type the time period you want to define as a baseline period, such as ‘900
seconds’. This period moves with the current time. The most recent 900-
second period becomes the current baseline period.
WarningDeviations Displays the number of standard deviation away from normal at which the
policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 4.5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.5
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
MinorDeviations. To disable the parameter, set value as 7.5.
This policy monitors the boot log file /var/log/boot.log and alerts in case of any system boot
errors. The default polling interval is 5 minutes.
Condition Description
Service startup Checks for error conditions that match the <*> <@.service>:
failed <@.daemon> startup failed pattern in the boot log file. If any
matches are found, this condition sends a message with minor
severity to the HPOM console with the appropriate message
attributes.
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 a message with critical severity to the
HPOM console with the appropriate message attributes.
This policy monitors the log file in /var/log/secure and /var/log/messages, and alerts in case
of any secure login failure. The default polling interval is 5 minutes.
Condition Description
Authentication Checks for error conditions that match the <*> sshd\[<#>\]: Failed
failure password for <@.user> from <*.host> port <#> ssh2 pattern in the
secure log file. If any matches are found, this condition sends a message
with minor severity to the HPOM console with the appropriate message
attributes.
This policy monitors the kernel log file /var/log/messages and alerts in case of any kernel service
failure. The default polling interval is 5 minutes.
Condition Description
Kernel service Checks for error conditions that match the <*> kernel: <@.service>:
failure <*.msg> failed pattern in the kernel log file. If any matches are found, this
condition sends a message with minor severity to the HPOM console with
the appropriate message attributes.
This policy monitors the NFS log file for the NFS server processes and forwards the errors to the
HPOM console with a severity level of warning or error. The default polling interval is 1 minute. The
policy looks for the following errors recorded in the NFS log file:
l The NFS server detected a low disk space condition and has stopped recording audits.
l The NFS server could not register with RPC Port Mapper.
This policy monitors the log file for the Microsoft DNS server service and its corresponding process
and forwards the error log entries to the HPOM console with a severity level of warning or error. The
default polling interval is 1 minute. The policy 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 initialize the remote procedure call (RPC) service.
This policy monitors the Windows logon and initialization event logs and forwards the error log
entries to the HPOM console with a severity level of warning or error. The default polling interval is 1
minute. The policy looks for the following errors recorded in the Windows log file:
l The Windows logon process has failed to terminate currently logged on user's processes
l The Windows logon process has failed to disconnect the user session
This policy monitors the log file for Windows Terminal service and its corresponding process and
forwards the error log entries to the HPOM console with a severity level of warning or error. The
default polling interval is 1 minute. The policy looks for the following errors recorded in the Windows
Terminal service log file:
l A connection request was denied because the terminal server is currently configured to not
accept connections
l Auto-reconnect failed to reconnect the user to the session because authentication failed
This policy monitors the log file for DHCP server and client services and their corresponding
processes, and forwards the error log entries to the HPOM console with a severity level of warning
or error. The default polling interval is 1 minute. The policy looks for the following errors recorded in
the Windows Terminal service log file:
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 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 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.
The output of ‘errpt’ command is stored as system errors in the errpt.log file. The SI-AIXErrptLog
policy monitors the log file and sends the log entries to the HPOM console as messages with
severity Warning. The alerts contain error codes, classes, and outages. The default policy group for
this policy is:
Performance Policies
Performance monitoring helps to preempt performance disruption and identify when the
infrastructure issues can threaten service quality. You can use the collected performance data to
correlate events across the entire infrastructure of servers, operating systems, network devices,
and applications in order to prevent or identify the root cause of a developing performance issue.
This policy monitors the disk performance on the managed node and sends out an alert when the
disk write and read service time violates the threshold levels. It is mandatory to run Performance
Agent on the managed node for this policy.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplicati Type an appropriate value that helps you identify the messages sent by the
on SI-PerDiskAvgServiceTime-AT policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as ‘3600
seconds’. This period moves with the current time. The most recent 3600-
second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum average time spent in processing each read or write
disk request as indicated by the metric.
MaximumValue Displays the maximum average time spent in processing each read or write
disk request as indicated by the metric.
WarningDeviation Displays the number of standard deviation away from normal at which the
s policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for MinorDeviations.
To disable the parameter, set value as 5.
WarningHighSeve Displays the severity of the alert messages to be sent to HPOM console in
rity case the current data meets or exceeds the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
WarningLowSever Displays the severity of the alert messages to be sent to HPOM console in
ity case the current data meets or falls below the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
DiskIOCutOff Set a value below which you do not want to monitor the disk write and reads
service time.
This policy monitors the performance of the CPUs on the managed node and sends out an alert
when the utilization across all CPUs violates the threshold levels.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplicati Type an appropriate value that helps you identify the messages sent by the
on SI-GlobalCPUUtilization-AT policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as ‘3600
seconds’. This period moves with the current time. The most recent 3600-
second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum percentage of time the CPUs were not idle, as
indicated by the metric.
MaximumValue Displays the maximum percentage of time the CPUs were not idle, as
indicated by the metric.
WarningDeviation Displays the number of standard deviation away from normal at which the
s policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for MinorDeviations.
To disable the parameter, set value as 5.
WarningHighSeve Displays the severity of the alert messages to be sent to HPOM console in
rity case the current data meets or exceeds the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
WarningLowSever Displays the severity of the alert messages to be sent to HPOM console in
ity case the current data meets or falls below the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
This policy monitors the number of processes waiting in the run queue of the CPU and sends out an
alert when the number of processes in run queue violates the threshold levels
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplicati Type an appropriate value that helps you identify the messages sent by this
on policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as ‘3600
seconds’. This period moves with the current time. The most recent 3600-
second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum average number of threads/ processes waiting in the
run queue over the interval, as indicated by the metric.
WarningDeviation Displays the number of standard deviation away from normal at which the
s policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for MinorDeviations.
To disable the parameter, set value as 5.
WarningHighSeve Displays the severity of the alert messages to be sent to HPOM console in
rity case the current data meets or exceeds the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
WarningLowSever Displays the severity of the alert messages to be sent to HPOM console in
ity case the current data meets or falls below the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
This policy monitors the system's network usage and shows error rates and collisions to identify
potential network bottlenecks. The SI-NetworkUsageAndPerformance policy monitors the physical
NICs of only the vMA machines.
The policy does not monitor performance data for package collision on the Windows operating
system, as the BYNETIF_COLLISION metric is not available on it
Note: The following metrics used in this policy require HP Performance Agent to be running on the
managed node: BYNETIF_UTIL and BYNETIF_QUEUE.Note.
BYNETIF_ID
BYNETIF_OUT_PACKET
BYNETIF_ERROR
BYNETIF_COLLISION
BYNETIF_OUT_BYTE_RATE
BYNETIF_IN_BYTE_RATE
BYNETIF_UTIL
BYNETIF_QUEUE
BYNETIF_NAME
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 100 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
Note: The threshold values for this policy can be specified as a default value, and also as
individual network interface names, network interface types, or both. If network interface name
and network interface type are both specified for a parameter, then the network interface type
takes precedence over network interface name.
For indicating multiple NIC names, you can use '*' to match one or more characters.
In this instance, the threshhold value 0 will apply to all NIC names whose first three characters
match eth.
This policy monitors the 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 policy first checks for memory bottleneck threshold violations, if the condition is not met it
checks for memory usage threshold violations. If both conditions for memory bottleneck and
memory usage, are not met, the policy checks for free page table condition. By default the free page
table thresholds contain Microsoft recommended values on the Windows systems. In case of
violation of multiple threshold values indicating a high utilization, the policy sends a message to the
HPOM console with appropriate message attributes. The message also displays a list of top 10
memory hogging processes.
The multiple metrics used to evaluate a memory bottleneck condition use different threshold values
on various platforms. To enable the right threshold values for a specific platform, deploy the
threshold overrides policies onto the managed node.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 101 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
GBL_MEM_PAGEOUT_RATE
GBL_MEM_PAGEOUT_BYTE_RATE
GBL_MEM_PAGE_REQUEST_RATE*
GBL_MEM_CACHE_FLUSH_RATE *
GBL_MEM_PG_SCAN_RATE
GBL_MEM_PHYS
HP-UX
IBM AIX
Oracle Solaris
Script-Parameter Description
MemPageOutRateMajorThreshold Set the threshold value for pages swapped out at which
you want to receive a major message.
MemPageOutRateMinorThreshold Set the threshold value for pages swapped out at which
you want to receive a minor message.
MemPageOutRateWarningThreshol Set the threshold value for pages swapped out at which
d you want to receive a warning message.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 102 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
MemPageReqRateHighThreshold Set the threshold value for the number of page requests
from disk per second.
MemCacheFlushRateHighThreshol Set the threshold value for the rate at which the file
d system cache flushes its contents to disk.
FreeMemAvailMajorThreshold Set the threshold value for minimum free memory on the
disk at which you want to receive a major severity
message.
FreeMemAvailMinorThreshold Set the threshold value for minimum free memory on the
disk at which you want to receive a minor severity.
FreeMemAvailWarningThreshold Set the threshold value for minimum free memory on the
disk at which you want to receive a warning severity.
MemSwapoutByteRateMajorThresh Set the threshold value for minimum free memory on the
old disk at which you want to receive a major severity
message.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 103 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
MemSwapoutByteRateMinorThresh Set the threshold value for minimum free memory on the
old disk at which you want to receive a minor severity.
MemSwapoutByteRateWarningThre Set the threshold value for minimum free memory on the
shold disk at which you want to receive a warning severity.
FreePageTableMajorThreshold Set the threshold value for minimum free page table entry
on the disk at which you want to receive a major severity
message.
FreePageTableMinorThreshold Set the threshold value for minimum free page table entry
on the disk at which you want to receive a minor severity
message.
FreePageTableWarningThreshold Set the threshold value for minimum free page table entry
on the disk at which you want to receive a warning
severity message.
This is a processor performance monitoring policy. A system experiences CPU spike when there is
a sharp rise in the CPU usage immediately followed by a decrease in usage. SI-CPUSpikeCheck
policy monitors CPU spikes per CPU busy time in system mode, per CPU busy time in user mode,
and total busy time per CPU.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 104 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
BYCPU_CPU_SYS_MODE_UTIL
BYCPU_ID
BYCPU_CPU_TOTAL_UTIL
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
CpuUtilCriticalThreshold The threshold is expressed as the total CPU time when the
CPU is busy. In other words, the total CPU utilization time. It
consists of total CPU time spent in user mode and system
mode. Set the threshold value for minimum total CPU
utilization time at which you want to receive a critical severity
message.
CpuUtilMajorThreshold Set the threshold value for minimum total CPU utilization time
at which you want to receive a major severity message.
CpuUtilMinorThreshold Set the threshold value for minimum total CPU utilization time
at which you want to receive a minor severity message.
CpuUtilWarningThreshold Set the threshold value for minimum total CPU utilization time
at which you want to receive a warning severity message.
CpuUtilUsermodeMajorThresh Set the threshold value for minimum CPU busy time in user
old mode at which you want to receive a major severity message.
CpuUtilUsermodeMinorThresh Set the threshold value for minimum CPU busy time in user
old mode at which you want to receive a minor message.
CpuUtilUsermodeWarningThre Set the threshold value for minimum CPU busy time in user
shold mode at which you want to receive a warning message.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 105 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
CpuUtilSysmodeMajorThreshol Set the threshold value for minimum CPU busy time in system
d mode at which you want to receive a major severity message.
CpuUtilSysmodeMinorThreshol Set the threshold value for minimum CPU busy time in system
d mode at which you want to receive a minor message.
CpuUtilSysmodeWarningThres Set the threshold value for minimum CPU busy time in system
hold mode at which you want to receive a warning message.
InterruptRateMajorThreshold Set the threshold value for minimum CPU interrupt rate at
which you want to receive a major severity message.
InterruptRateMinorThreshold Set the threshold value for minimum CPU interrupt rate at
which you want to receive a minor severity message.
InterruptRateWarningThreshold Set the threshold value for minimum CPU interrupt rate at
which you want to receive a warning severity message.
This policy detects CPU bottlenecks like exceeding the thresholds for CPU utilization percentage,
processor queue length, total number of CPU on the system, and operating systems.
If the threshold for CPU utilization is violated along with threshold for number of processes in the
queue waiting for CPU time, the policy sends a message to the HPOM console with the appropriate
message attributes. The message displays a list of the top 10 CPU hogging processes.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 106 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
GBL_LOADAVG
GBL_INTERRUPT_RATE
GBL_CSWITCH_RATE
GBL_INTERRUPT_RATE
HP-UX
IBM AIX
Oracle Solaris
Script-Parameter Description
GlobalCpuUtilMajorThresho Set the threshold value for minimum summarized CPU utilization
ld at which you want to receive a major message.
GlobalCpuUtilMinorThresho Set the threshold value for minimum summarized CPU utilization
ld at which you want to receive a minor message.
GlobalCpuUtilWarningThres Set the threshold value for minimum summarized CPU utilization
hold at which you want to receive a warning message.
MessageGroup You can type an appropriate value that helps you to identify the
messages sent by this policy. Whenever a threshold is violated,
the policy appends the value from this parameter in the message
before sending it to the management console.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 107 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
This policy monitors utilization for each disk on the managed node. This policy processes each disk
instance separately for every interval. The policy uses the automatic threshold determination to
automatically calculate the threshold values according to the disk utilization on previous days. It is
mandatory to run Performance Agent on the managed node for this policy.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplicati Type an appropriate value that helps you identify the messages sent by the
on SI-PerDiskUtilization-AT policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as ‘3600
seconds’. This period moves with the current time. The most recent 3600-
second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum value of disk utilization as indicated by the metric.
MaximumValue Displays the maximum value of disk utilization as indicated by the metric.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 108 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
WarningDeviation Displays the number of standard deviation away from normal at which the
s policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
MinorDeviations. To disable the parameter, set value as 5.
WarningHighSever Displays the severity of the alert messages to be sent to HPOM console in
ity case the current data meets or exceeds the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
WarningLowSeveri Displays the severity of the alert messages to be sent to HPOM console in
ty case the current data meets or falls below the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
DiskUtilCutOff Set a value below which you do not want to monitor disk utilization.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 109 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
This policy monitors the network interface outbyte rate for a network interface in a given interval. It
monitors the outgoing bytes on each network interface on the managed node individually. This
policy processes each instance of network interface separately for every interval. The policy uses
automatic threshold determination to automatically calculate the threshold values according to the
network interface outbyte rate on previous days.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent. The policy does not monitor the physical NIC of vMA
machines.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplicatio Type an appropriate value that helps you identify the messages sent by
n the SI-PerNetifOutbyteBaseline-AT policy to the management console.
BaselinePeriod Type the time period you want to define as a baseline period, such as
‘3600 seconds’. This period moves with the current time. The most recent
3600-second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum value of network interface outbyte rate as indicated
by the metric.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 110 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
WarningDeviations Displays the number of standard deviation away from normal at which the
policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
MinorDeviations. To disable the parameter, set value as 5.
WarningHighSeveri Displays the severity of the alert messages to be sent to HPOM console
ty in case the current data meets or exceeds the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or exceeds the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
WarningLowSeverit Displays the severity of the alert messages to be sent to HPOM console
y in case the current data meets or falls below the sample data average by
the value specified in WarningDeviations. To disable the parameter, set
value as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in MinorDeviations. To disable the parameter, set
value as none.
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console
in case the current data meets or falls below the sample data average by
the value specified in MajorDeviations. To disable the parameter, set
value as none.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 111 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
ByNetifOutByteCut Set a value below which you do not want to monitor the outbyte rate.
Off
This policy monitors the inbyte rate for a network interface in a given interval. It monitors the
incoming bytes on each network interface on the managed node individually. This policy processes
each instance of network interface separately for every interval. The policy uses the automatic
threshold determination to automatically calculate the threshold values according to the network
interface inbyte rate on previous days.
This policy relies on historical data. For accurate results, deploy the policy only after a week of data
collection by the performance agent. The policy does not monitor the physical NIC of vMA
machines.
HP-UX
IBM AIX
Oracle Solaris
Debian
Ubuntu
Script-Parameter Description
MessageApplicati Type an appropriate value that helps you identify the messages sent by the
on policy to the management console.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 112 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
BaselinePeriod Type the time period you want to define as a baseline period, such as ‘3600
seconds’. This period moves with the current time. The most recent 3600-
second (1-hour) period becomes the current baseline period.
MinimumValue Displays the minimum value of network interface inbyte rate as indicated by
the metric.
MaximumValue Displays the maximum value of network interface inbyte rate as indicated
by the metric.
WarningDeviation Displays the number of standard deviation away from normal at which the
s policy will send a warning message to HPOM console. Set an appropriate
value for the parameter. To disable the parameter, set value as 5.
MinorDeviations Displays the number of standard deviation away from normal at which the
policy will send a minor message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for
WarningDeviations. To disable the parameter, set value as 5.
MajorDeviations Displays the number of standard deviation away from normal at which the
policy will send a major message to HPOM console. Set an appropriate
value for the parameter greater than the specified value for MinorDeviations.
To disable the parameter, set value as 5.
WarningHighSeve Displays the severity of the alert messages to be sent to HPOM console in
rity case the current data meets or exceeds the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
MajorHighSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or exceeds the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
WarningLowSever Displays the severity of the alert messages to be sent to HPOM console in
ity case the current data meets or falls below the sample data average by the
value specified in WarningDeviations. To disable the parameter, set value
as none.
MinorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MinorDeviations. To disable the parameter, set value as
none.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 113 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
MajorLowSeverity Displays the severity of the alert messages to be sent to HPOM console in
case the current data meets or falls below the sample data average by the
value specified in MajorDeviations. To disable the parameter, set value as
none.
ByNetifInByteCut Set a value below which you do not want to monitor the inbyte rate.
Off
Script-Parameter Description
ProcessName Type the name of the process that you want to monitor.
CPUUsageHighWaterMar Type a threshold value for process CPU or memory usage above
k or which you want to receive an alert.
MemoryUsageHighWater
Mark
SI-JavaProcessCPUUsageTracker policy monitors the CPU usage for the Java process running
on your system. The default policy group for the policy is:
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 114 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
This policy monitors the utilization level of the disk on the system. It checks whether the utilization
level is full. In case the disk utilization level exceeds the threshold values specified, the policy
sends out an alert message to the HPOM console.
HP-UX
IBM AIX
Oracle Solaris
Script-Parameter Description
DiskPeakUtilMajorThreshol Set the threshold value at which you want to receive a major
d message.
DiskPeakUtilMinorThreshol Set the threshold value at which you want to receive a minor
d message.
DiskPeakUtilWarningThres Set the threshold value at which you want to receive a warning
hold message.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 115 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
In the console tree, the SI-DiskPeakUtilMonitor policy is listed at the following locations:
Security Policies
Suppose an unauthorized user tried to break into your system by entering different combinations of
username and password, or by deploying an automated script to do this. Such attempts may result
in too many login failures. To identify and preempt such a risk, you can deploy the System
Infrastructure security policies to periodically check the number of failed logins on your system. For
instance, these policies collect failed login data and send alerts in case of too many attempts.
Note: After deploying the security collector policies, make sure that you let the policies run for
at least 5 minutes to collect the required data.
This is a scheduled task policy that checks for the number of failed login attempts on Microsoft
Windows. It check for invalid logins, either due to unknown username or incorrect password on the
managed node. The policy logs individual instances of failed login into the GBL_NUM_FAILED_
LOGINS metric in Embedded Performance Component (EPC) at definite time intervals. By default,
the time interval is 1 hour. The recorded information stored in EPC can be used to send an alert to
the console or generate reports for the number of invalid logins over a period of time. The default
policy group for the policy is:
Note: On the first run of the policy that is after deployment and restart of the agent, the policy
proceeds with certain initializations. On successive run, the policy will start collecting the
number of failed logins since the last policy run.
This is a scheduled task policy that checks for the logon details of all the active local user accounts
on Microsoft Windows. The policy logs individual instances of user logon into the SECONDS_
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 116 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
This is a scheduled task policy that checks for the number of failed login attempts on RHEL and
SLES Linux systems, HP-UX, AIX and Solaris. The policy checks for invalid logins, either due to
unknown username or incorrect password on the managed node. The policies log individual
instances of failed login into the GBL_NUM_FAILED_LOGINS metric in Embedded Performance
Component (EPC) at definite time intervals. By default, the time interval is 1 hour. The recorded
information stored in EPC can be used to send an alert to the console or generate reports for the
number of invalid logins over a period of time. The default policy group for the policy is:
In this instance, the <os> can be AIX, HP-UX, SLES, RHEL, or Solaris
l The file /etc/default/login on solaris node must have the following settings:
SYSLOG=YES
SYSLOG_FAILED_LOGINS=1
l Remove the comment from the following line in /etc/syslog.conf file or add the line if it is
not present.
auth.notice ifdef(LOGHOST', /var/log/authlog, @loghost)
Solaris /var/log/authlog
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 117 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
This is a scheduled task policy that checks for the logon details of all the active local user accounts
on RHEL and SLES Linux systems. The policy logs individual instances of user logon into the
SECONDS_SINCE_LASTLOGIN metric in Embedded Performance Component (EPC) at definite
time intervals. By default, the time interval is 1 hour. The recorded information stored in EPC can be
used to send an alert to the console or generate reports for the number of user logons over a period
of time. The default policy group for the policy is:
/opt/OV/contrib/OpC/autogranting/enableAutoGranting.sh
2. To enable auto deployment for Infra SPI using XPL config change, run the following command:
3. To activate the node, run the following command on the management server:
6. Deploy configuration.
To manually deploy policies from the management server, follow these steps:
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 118 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
4. Select the option Select nodes from the tree. From the list of managed nodes, select the
nodes where you want to deploy the policy.
5. Click OK.
You can manually deploy the policies to the nodes or enable auto deployment of policies.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 119 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
/opt/OV/contrib/OpC/autogranting/enableAutoGranting.sh
2. To enable auto deployment for Infra SPI using XPL config change, run the following command:
3. To activate the node, run the following command on the management server:
Note: You must not add VA node to SI-Deployment node group because SI SPI policies
are not supported on VA node.
6. Deploy configuration.
To manually deploy policies or policy group from the management server for HPOM for UNIX (HP-
UX, Linux, or Solaris) follow these steps:
2. Click Policy Bank under the Objects Bank category. The Policy Bank window opens.
3. In the Policy Bank window, select the policy or policy groups you want to assign to a node or a
node group.
4. Select Assign to Node/Node group... from the Choose an Action drop-down box and click
submit. The select window opens.
5. Select the node or the node groups and click OK. The selected policies are assigned to the
nodes.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 120 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
1. From the HPOM Administration interface, click Node Bank under the Objects Bank category.
The Node Bank window opens.
2. In the Node Bank window, select the nodes or node groups on which you want to deploy
policies.
3. Select Deploy Configuration... from the Choose an Action drop-down box and click submit.
The selector window opens.
4. Select the Distribute Policies check box and click OK. The policies are deployed on the
selected nodes.
To access the SI SPI tool on HPOM for Windows, select the following:
To access the tool on console or Administration interface for HPOM for UNIX/ Linux, select the
following:
To launch the tool from the HPOM for Windows management server, follow these steps:
1. From the console tree Tools folder, select the Systems Infrastructure folder.
2. Select the Users Last Login tool from the details pane and right-click to open the shortcut
menu.
3. Select All Tasks → Launch Tool... to open the Select where to launch this tool dialog box.
The dialog box displays a list of the managed nodes on which the selected tool can be
launched.
4. Select the check box for each node to which you want to apply the tool. Selecting the Nodes
folder selects the entire group of tools the folder contains.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 121 of 132
User Guide
Chapter 5: Systems Infrastructure SPI Policies
5. Click Launch. The Tool Status dialog box opens to display the results of the launch operation.
You can save the results of the apply tool operations. Select one or more lines in the Launched
Tools box and click Save. The output is saved in text format.
To launch the tool from HPOM for UNIX management server, follow these steps:
2. Right-click the <tool name>tool, select Start Customized. Start Tool - Customized Wizard
window opens.
3. Under the nodes list, select the node to launch the tool.
4. On the wizard, click Get Selections. The node is added to the Selected Nodes list.
5. Click Next. On the page specify additional information needed to run the tool, you can specify
the additional information or leave the fields blank.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 122 of 132
Chapter 6: Systems Infrastructure SPI
Reports and Graphs
You can integrate the SI SPI with HP Reporter to generate reports based on collected metric data
from the managed nodes. The reports provide a picture of system resources. You can also generate
graphs to analyze the metric data collected. To generate and view reports and graphs from data
collected by the SI SPI, use HP Reporter and HP Performance Manager with HPOM.
You can access SI SPI reports from the HPOM for Windows console. To install HP Reporter
package for SI SPI, see HP Operations Smart Plug-in for Infrastructure Installation Guide.
To view reports for SI SPI from HPOM for Windows, expand Reports → Systems Infrastructure
in the console tree. To display a report, select the desired report, right-click, and then select Show
report.
If HP Reporter is installed on the HPOM management server, you can view the reports on the
management server directly.
If HP Reporter is installed on a separate system connected to the HPOM management server, you
can view the reports on HP Reporter system. For more information on integration of HP Reporter
with HPOM, see HP Reporter Installation and Special Configuration Guide. The following is an
example report.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 123 of 132
User Guide
Chapter 6: Systems Infrastructure SPI Reports and Graphs
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 124 of 132
User Guide
Chapter 6: Systems Infrastructure SPI Reports and Graphs
Report/ Report
Title Purpose
System Last Login This report displays the date when a particular login was last used on the
managed node. It also displays a list of users who have never logged in.
The information is sorted by day and time. You can use this information to
identify the unused or obsolete user accounts.
System Failed This report displays a list of all failed login attempts on the managed node.
Login You can use this information to identify unauthorized users repeatedly
trying to login the managed node.
System This report displays the availability information for the systems. You can
Availability use this information to know the system uptime percentage and system
downtime time for the range of dates in the database excluding outside of
shifts, weekends, or holidays.
Top CPU Process This report displays the top systems with high CPU consumption. You can
use this information to analyze the systems with high CPU cycles
consumed during the reporting interval.
Top Memory This report displays the top systems with high memory consumption. You
Process can use this information to analyze the systems with high memory
consumed during the reporting interval.
The SI SPI provides a set of pre-configured graphs. They are located on the HPOM console tree in
the Graphs folders. You can access this Graphs folder only if you install HP Performance Manager
on the HPOM management server. The following is an example graph.
To access the graphs on HPOM for Windows, select Graphs→ Infrastructure Performance
To access the graphs on HPOM for UNIX/ Linux/Solaris, select the active message, open the
Message Properties window, and click Actions. Under the Operator initiated action section, click
Perform. Alternatively you can, right-click active message, select Perform/Stop Action and click
Perform Operator-Initiated Action.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 125 of 132
User Guide
Chapter 6: Systems Infrastructure SPI Reports and Graphs
l Disk Summary
l Disk Throughput
l Disk Space
l Disk Details
l Global Details
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 126 of 132
User Guide
Chapter 6: Systems Infrastructure SPI Reports and Graphs
l Individual CPUs
l CPU Comparison
l CPU Gauges
l CPU Details
l Individual Networks
l System Configuration
l Transaction History
l Transaction Details
l Application History
l Application Details
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 127 of 132
Chapter 7: Troubleshooting
This chapter helps you troubleshoot SI SPI problems and provides you with information to help you
avoid problems from occurring.
Cause This error occurs when the SI-PerDiskUtilization-AT policy is deployed to a node
that does not have the HP Performance Agent installed on the node. The SI-
PerDiskUtilization-AT policy uses metrics provided by SCOPE for the calculations,
and requires HP Performance Agent for proper functioning.
Solution Install the HP Performance Agent on the managed node for the policy to function
properly.
Problem Advanced Monitoring policies modified in HPOM for UNIX Administrator GUI fail to
run after deployment to managed nodes.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 128 of 132
User Guide
Chapter 7: Troubleshooting
Cause When advanced monitoring policies are edited in user interface mode in HPOM for
UNIX policy editor, syntax errors are induced into the Perl code module. This
causes the policy to fail to execute. Errors such as the following appear:
#BEGIN_PROCESSES_LIST
#ProcName=/usr/sbin/sshd
#Params=
#Params=
#MonMode=>=
#ProcNum=1
#END_PROCESSES_LIST
@ProcNames"
. (OpC30-750)
Solution To edit the settings in the Measurement Threshold policy, use ‘Edit in Raw mode’
feature of the HPOM for UNIX Administrator GUI to change the policy contents.
This requires you to know the syntax of the policy data file.
Problem Operator initiated commands fail to launch the SI SPI graphs from HPOM for UNIX
(version 9.00) operator console
/opt/OV/contrib/OpC/OVPM/install_OVPM.sh <OMUServerName>:8081
Problem Discovery procedures and data collection gives error with non-English names.
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 129 of 132
User Guide
Chapter 7: Troubleshooting
Solution Make sure that the names for clusters and resource groups are in English.
Cause While automatically adding nodes for cluster and virtualized environments, the
system discovery policy generates alert messages with normal severity. These
messages take a while to get acknowledged as the auto-addition feature of the
policy takes time to populate the node bank.
Solution Disable the Auto-addition feature by changing the following default values in the
XPL configuration parameters:
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 130 of 132
User Guide
Chapter 7: Troubleshooting
. (OpC30-750)
Cause This error occurs on any policy and any *.pm file when the instrumentation is not
deployed on the node correctly.
Solution Run the following commands on the Windows node to recycle the CODA files:
2. rm -rf /var/opt/OV/datafiles/coda*
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 131 of 132
We appreciate your 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 (Operations Smart Plug-in for System Infrastructure 11.14)
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].
HP Operations Smart Plug-in for System Infrastructure (11.14) Page 132 of 132