BBPM Perfmon MGMT

BMC ProactiveNet Performance
Management - Hardware
Version 1.9.00
User Documentation
January 2014
BMC ProactiveNet Performance Management - Hardware

Version 1.9.00
Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtain
information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada
Address
BMC Software, Inc.

2101 CityWest Blvd. Houston TX 770422827
Telephone
1 (713) 918 8800 or

1 (800) 841 2031 (Toll Free)
Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved.
BMC Software, the BMC Software logos, and all other BMC Software product or service names are
registered trademarks or trademarks of BMC Software, Inc.
All other trademarks belong to their respective companies.
BMC Software considers information included in this documentation to be proprietary and confidential.
Your use of this information is subject to the terms and conditions of the applicable End User License
Agreement for the product and the proprietary and restricted rights notices included in this
documentation.
Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER
THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and
computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR
Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS
252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101
CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.

Version 1.9.00
You can obtain technical support by using the Support page on the BMC Software Web site or by
contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see "Before
Contacting BMC Software."
Support Web Site

You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http://
www.bmc.com/support_home. From this Web site, you can
Read overviews about support services and programs that BMC Software offers:
Find the most current information about BMC Software products
Search a database for problems similar to yours and possible solutions
Order or download product documentation
Report a problem or ask a question
Subscribe to receive e-mail notices when new product versions are released
Find worldwide BMC Software support center locations and contact information, including e-mail
addresses, fax numbers, and telephone numbers
Support by Telephone or E-mail

In the United States and Canada, if you need technical support and do not have access to the Web, call
8005371813. Outside the United States and Canada, please contact your local support center for
assistance. To find telephone and email contact information for the BMC Software support center that
services your location, refer to the Contact Customer Support section of the Support page on the BMC
Software Web site at http://www.bmc.com/support_home.
Before Contacting BMC Software

Before you contact BMC Software, have the following information available so that Customer Support can
begin working on your problem immediately:
Product information
product name
product version (release number)
license number and password (trial or permanent)
Operating system and environment information machine type operating system type, version, and
service pack or other maintenance level such as:
PUT or PTF
system hardware configuration
serial numbers
related software (database, application, and communication) including type, version, and service
pack or maintenance
level
Sequence of events leading to the problem
Commands and options that you used
Messages received (and the time and date that you received them)
product error messages
messages from the operating system, such as "file system full"

Version 1.9.00
Table of Contents
User Goals and Features
...........................................................................................................................11
Product at a Glance
...........................................................................................................................11
Supported Platforms
...........................................................................................................................12
Solution Packages
...........................................................................................................................15
Importing the Monitoring
...........................................................................................................................18
Solution into Central Administration
Creating the Installation
...........................................................................................................................19
Package
Downloading the...........................................................................................................................20
Installation Package
Installing the Package
...........................................................................................................................20
Creating and Importing
...........................................................................................................................24
an Adapter for a BMC PATROL KM
Updating an Adapter
...........................................................................................................................30
for a BMC PATROL KM
Importing and Customizing
...........................................................................................................................31
Thresholds
Verifying the Data
...........................................................................................................................33
Collection
Managing Baselines
...........................................................................................................................34
and Key Performance Indicators
Adding Tags to PATROL
...........................................................................................................................37
Agents
Managing Policies
...........................................................................................................................37
Creating a policy...........................................................................................................................37
...........................................................................................................................38
Editing an existing
policy
Deleting a policy ...........................................................................................................................38
...........................................................................................................................39
Enabling/disabling
a policy
Configuring Monitor
...........................................................................................................................39
Settings
...........................................................................................................................39
Creating a Connection
to a Device
..................................................................................................................42
Using the SNMP Protocol
..................................................................................................................43
Using the SSH/Telnet
Protocol
..................................................................................................................45
Using the WBEM Protocol
..................................................................................................................46
Using the WMI Protocol
..................................................................................................................46
Using the Cisco UCS
Manager
..................................................................................................................47
Using the IPMI-Over-LAN
Protocol
...........................................................................................................................47
Configuring Global
Alert Settings
Configuring Alert ..................................................................................................................48
Actions
Configuring Alert ..................................................................................................................49
Delay
..................................................................................................................49
Configuring the Unknown
Status
..................................................................................................................50
Automatically Resetting
Error Count Parameters
Table of Contents

Version 1.9.00
...........................................................................................................................51
Configuring Global
Advanced Settings
Configuring Local ..................................................................................................................51
Commands
..................................................................................................................52
Configuring Intervals
..................................................................................................................53
Enabling the Debug
Mode
Setting Additional..................................................................................................................54
Configuration Variables
...........................................................................................................................59
Scheduling Automatic
Reports
Configuring Thresholds
...........................................................................................................................60
...........................................................................................................................60
Configuring Monitor
Thresholds
...........................................................................................................................61
Editing a Threshold
Configuration
...........................................................................................................................61
Deleting a Threshold
Configuration
Monitor Types and
...........................................................................................................................63
Attributes
...........................................................................................................................64
Managing Baselines
and Key Performance Indicators
Hardware Battery...........................................................................................................................65
Hardware Blade ...........................................................................................................................66
...........................................................................................................................66
Hardware Capacity
Report
...........................................................................................................................67
Hardware CPU Core
...........................................................................................................................67
Hardware Disk Controller
...........................................................................................................................69
Hardware Disk Enclosure
...........................................................................................................................7 0
Hardware Enclosure
Hardware Fan ...........................................................................................................................7 0
Hardware LED ...........................................................................................................................7 1
1
Hardware Logical...........................................................................................................................7
Disk
Hardware LUN ...........................................................................................................................7 2
...........................................................................................................................7
3
Hardware Memory
Module
...........................................................................................................................7
3
Hardware Network
Interface
5
Hardware Other ...........................................................................................................................7
Device
...........................................................................................................................7
5
Hardware Physical
Disk
7
Hardware Power...........................................................................................................................7
Supply
...........................................................................................................................7 7
Hardware Processor
...........................................................................................................................7 8
Hardware Robotics
8
Hardware Sentry...........................................................................................................................7
Connector
...........................................................................................................................7 9
Hardware Tape Drive
...........................................................................................................................80
Hardware Temperature
...........................................................................................................................80
Hardware Voltage
Device Additional...........................................................................................................................81
Table of Contents
Support Information

Version 1.9.00
This section contains information about how to contact Customer Support and the levels of support
offered for this and other releases.
If you have problems with or questions about a BMC product, or for the latest support policies, see the
Customer Support website at http://www.bmc.com/support. You can also access product documents
and search the Knowledge Base for help with an issue at http://www.sentrySoftware.com. If you do not
have access to the web and you are in the United States or Canada, contact Customer Support at 800
537 1813. Outside the United States or Canada, contact your local BMC office or agent.
Legal Notices

Version 1.9.00
Copyright 2011 BMC Software, Inc.

BMC, BMC Software, and the BMC Software logo are the exclusive properties of BMC Software, Inc., are
registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in
other countries. All other BMC trademarks, service marks, and logos may be registered or pending
registration in the U.S. or in other countries. All other trademarks or registered trademarks are the
property of their respective owners.
Linux is the registered trademark of Linus Torvalds.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
UNIX is the registered trademark of The Open Group in the US and other countries.
The information included in this documentation is the proprietary and confidential information of BMC
Software, Inc., its affiliates, or licensors. Your use of this information is subject to the terms and
conditions of the applicable End User License agreement for the product and to the proprietary and
restricted rights notices included in the product documentation.
BMC Softwa re Inc.
2101 City W e st Blv d, Houston T X 77042-2827, USA
713 918 8800
Custom e r Support: 800 537 1813 (Unite d Sta te s a nd Ca na da ) or conta ct y our loca l support ce nte r
Overview

Version 1.9.00
The pages in this section provide a high-level overview of the product.

Product at a Glance
Supported Platforms
Note that for conv enience and brev ity , reference to BMC Proactiv eNet Performance Management - Hardware, may
also be made as BPPM Hardware.

BMC ProactiveNet Performance Management - Hardware monitors the following in your environment:
Critical components: processors, memory modules, network adapters, fiber ports, etc.
Disks: RAID controllers, hard disks, RAIDs, etc.
Environment: temperature, voltage, fans, power supplies.
Network links: network adapters, link loss, data traffic, bandwidth utilization, etc.
Product at a Glance
BMC ProactiveNet Performance Management - Hardware provides current and historical information
through a centralized console so you can easily view and manage your entire IT infrastructure. The
product collects and brings critical performance data and useful metrics into the BMC ProactiveNet
Performance Management environment and enables administrators to be warned whenever Hardware
problem occurs in their IT infrastructure.
BMC ProactiveNet Performance Management - Hardware:
Provides visibility on 100% of the IT.
Detects hardware failures.
Reports on the energy usage of the IT infrastructure.
11

Version 1.9.00
Supported Platforms
BMC ProactiveNet Performance Management - Hardware requires specific instrumentation agents or
system management tools to be present on the managed system to collect hardware information.
Servers
Typical Platform
Operating System
Instrumentation
Prerequisites
Technology Used
Cisco UCS B-Series, C-Series
Windows
None
IPMI, WMI
Linux
ipmitool
IPMI, command lines
Dell PowerEdge
Windows
Dell OpenManage Server

Administrator
SNMP
Dell PowerEdge
Linux
Dell OpenManage Server

Administrator
SNMP
Fujitsu PRIMEPOWER
Servers (sun4us) -
Solaris
None
Command lines
Fujitsu-Siemens PRIMERGY
VMware
Fujitsu Serverview WBEM agent
WBEM
Windows
Fujitsu-Siemens Serverview
Fujitsu-Siemens ServerView RAID
Agent / Promise FastTrack SNMP
Agent / LSI GAM Server / LSI
MegaRAID SAS SNMP Agent / LSI
MegaRAID PowerConsole / Mylex
GAM Server (depending on the
server, follow Fujitsu-Siemens
recommendations)
SNMP
Linux
Fujitsu-Siemens ServerView RAID
Agent / Promise FastTrack SNMP
Agent / LSI GAM Server / LSI
MegaRAID SAS SNMP Agent / LSI
MegaRAID PowerConsole / Mylex
GAM Server (depending on the
server, follow Fujitsu-Siemens
recommendations)
SNMP
Linux
Fujitsu-Siemens Serveview WBEM

Agent
WBEM
Windows
Fujitsu-Siemens Serveview WBEM

Agent
WMI
HP 9000
HP-UX
HP-UX Support Tools Manager (STM)

or HP-UX WBEM Provider
Command lines, Telnet/

SSH, or WBEM
HP AlphaServer
Tru64
HP Insight Management Agent
SNMP
HP AlphaServer
OpenVMS
SNMP
HP Integrity
Windows
SNMP
HP Integrity
Linux
SNMP
Supported Platforms
12

Version 1.9.00
Typical Platform
Operating System
Instrumentation
Prerequisites
Technology Used
HP Integrity
HP-UX
HP-UX Support Tools Manager (STM)

or HP-UX WBEM Provider

SSH, or WBEM
HP NetServer
Windows
HP TopTools
SNMP, WMI
HP ProLiant
Windows
SNMP or WMI
HP ProLiant
Linux
SNMP
HP ProLiant
Solaris
SNMP
HP SuperDome (Itanium)
Windows
SNMP
Linux
SNMP
HP-UX
MP/GSP card

SSH
HP SuperDome (PA-RISC)
HP-UX
GSP card

SSH
IBM pSeries, IBM eServer
IBM AIX
None
Command lines
IBM v7000 Disk Arrays
Storage Device
--
Telnet/SSH
IBM VIO Server
IBM AIX
None
SSH
IBM xSeries, IBM Netfinity
Windows
IBM Director Agent
WMI
IBM xSeries, IBM Netfinity
Linux
IBM Director Agent
WBEM, command lines
NEC Express5800
Windows
NEC ESMPRO Agent
SNMP
NEC Express5800
Linux
NEC ESMPRO Agent
SNMP
Sun Fire (SPARC T1, T2)

2009 and newer firmware
Solaris
None
Command lines
Sun Fire (SPARC T1, T2)

pre-2009 firmware
Solaris
Access to the Sun Advanced LightsOut Management (ALOM) card over

the network
Command lines, SSH to

the ALOM card
Sun Fire (SPARC)
Solaris
None
Command lines
Sun Fire (X64)
Solaris
ipmitool, lsiutil
Command lines
Sun Fire (X64)
Linux
ipmitool, lsiutil
Command lines
Sun Fire (X64)
Windows
lsiutil
IPMI (WMI), command

lines
Sun Fire F12K, F15K, F20K,

F25K
Solaris
Access to the SMS utilities installed

on the System Controller (SC)
SSH to the System

Controller
Sun Fire Mx000
Solaris
Access to the eXtended System

Control Facility (XSCF)
SSH to the XSCF
Cross-Platform Technology
Technology
Operating
System
Instrumentation Prerequisites
Technology Used
Emulex HBA
Windows
None
WMI
Emulex HBA
Linux
hbacmd
Command lines
Emulex HBA
Solaris
hbacmd
Command lines
Supported Platforms
13

Version 1.9.00
Technology
Operating
System
Technology Used
QLogic HBA
Windows
None
WMI
QLogic HBA
Linux
scli
Command lines
QLogic HBA
Solaris
scli
Command lines
VMware ESX/ESXi
VMware ESX/ESXi
Access to the CIM server
WBEM
Blade Chassis
Chassis
Technology Used
Cisco UCS Interconnect Chassis Cisco UCS Manager on the Cisco UCS Interconnect
Switch
XML API (HTTP)
Dell Modular Chassis (blades)
DRAC/MC
Telnet/SSH
Fujitsu-Siemens BX Blade
Chassis
Fujitsu-Siemens Management Blade
SNMP
HP c-Class BladeSystem
HP BladeSystem On-Board Administrator
SNMP
HP p-Class BladeSystem
SNMP
Hitachi BladeSymphony
Hitachi BladeSymphony Management Module
SNMP
IBM BladeCenter
IBM BladeCenter Management Module
SNMP
Sun Blade Modular Chassis
Access to the Chassis Management Module (CMM)
SNMP
Typical Platform
Technology Used
3PAR InServ
3PAR SMI-S Provider
WBEM
Brocade SAN Switch
SNMP Enabled
SNMP
Cisco SAN Switch1
None
Telnet/SSH
Compellent
Compellent Enterprise Manager
WBEM
Dell EquaLogic PS Series
None
SNMP
Dell PowerVault TL2000 tape

libraries
Dell OpenManage Server Administrator
SNMP
Dell PowerVault TL4000 tape

libraries
SNMP
Dell TL2000/4000 Tape library
None
SNMP
EMC Clariion
EMC SMI-S Provider
WBEM
EMC Symmetrix
EMC SMI-S Provider
WBEM
EMC VNX series
EMC SMI-S Provider
WBEM
IBM TS3100 Tape Libraries
IBM SNMP Agent (IBM 3100-MIB)
SNMP
IBM TS3200 tape libraries
IBM SNMP Agent (IBM 3100-MIB)
SNMP
Storage Devices
Supported Platforms
14

Version 1.9.00
Typical Platform
Technology Used
Fujitsu Eternus
ETERNUS SMI-S Agent
WBEM
Hitachi AMS/HUS
Hitachi Device Manager
WBEM
Hitachi USP-V
WBEM
Hitachi VSP
WBEM
HP StorageWorks P6000
HP CommandView EVA
Command lines
HP StorageWorks XP
HP CommandView XP (or Hitachi Device Manager)
WBEM
HP StorageWorks P9000 Series
HP CommandView
WBEM
IBM DS 3000, 4000, 5000

Series
IBM DS Storage Manager (SMcli)
Command lines
IBM DS 6000, 8000 Series
IBM DS Storage Manager
WBEM
IBM 3584 Tape Library
None
SNMP
IBM TS3100/3200 Tape library
None
SNMP
IBM XiV
IBM XIV Storage System SMI-S Agent
WBEM
McData SAN Switch
None
SNMP
NetApp
None
SNMP
Quantum Tape Library
None
SNMP
StorageTek LSeries
None
SNMP
StorageTek StreamLine (SL)
None
SNMP
Cisco network switches are not supported by BMC Proactiv eNet Performance Management - Hardware.
Generally server manufacturers furnish instrumentation agents and system tools for free and these
are either found on the CD-ROM provided with the server or, on the manufacturers web site. Unless
mentioned otherwise, the manufacturers instrumentation agent must be installed on the
monitored server for BPPM Hardware to function properly. For details on how to install the required
instrumentation agent on the systems, please refer to the platform-specific guides available on the
Hardware Sentry page of the Sentry Software website.
Solution Packages
The BPPM Hardware packages are available on the Sentry Software Web site.
There are three packages, each of which can be used to install the KM on every PATROL component
(Agent, Console, etc.) according to the platform you are using.
For Windows systems: mshw_ALL_<version>.zip
For UNIX and Linux systems: mshw_ALL_<version>.tar
For OpenVMS systems: mshw_VMS_<version>.tar
Supported Platforms
15

Version 1.9.00
Java Runtime Environment Package

Java Runtime Environment version 1.5.00 or higher is required in some cases for the KM to operate
properly (notably when the KM needs to make WBEM or SSH connections).
A package of a suitable Java Runtime Environment, designed for use with the BMC Software Installation
Utility, is made available to download on the Sentry Software Web site.
A pa che J RE is not supporte d.
Solution Packages
16
Installing the Monitoring Solution

Version 1.9.00
The installation can be handled from A to Z from BMC ProactiveNet Central Monitoring Administration.
Once the latest version of the solution has been loaded into BMC ProactiveNet Central Monitoring
Administration, administrators can create all the installation packages required for their different
operating systems and platforms and save them for later use in the Monitoring Installation Packages list.
These packages can then be deployed to multiple computers. Administrators just have to connect to
BMC ProactiveNet Central Monitoring Administration from the server where they want to install the
package, download it and launch the installation.
This section describes the different steps to follow to install BPPM Hardware:
Importing BPPM Hardware into Central Administration
Creating the Installation Package
Downloading the Installation Package
Importing the Monitoring Solution

into Central Administration
The BMC ProactiveNet Central Monitoring Repository includes the current versions of the BMC PATROL
Agent and BMC PATROL Monitoring Solutions that you can use with BMC ProactiveNet. If the version
available in the Repository does not correspond to the latest one, you will have to manually import it:
1. Log on to BMC ProactiveNet Central Monitoring Administration.
2. Click the Repository drawer and select Manage Repository.
3. Check that the version of the BMC component available is actually the latest one. If not, download
the latest version corresponding to your operating system (Windows or UNIX/Linux) available on
the Sentry Software Website and save it on the local computer from which you are running the
Central Monitoring Administration web-based console.
4.
5.
6.
7.
From the BMC ProactiveNet Central Monitoring Administration, click Import

Select Single solution.
Browse to the .zip source file.
Click Import.
The selected archive file is imported to the repository.
18

Version 1.9.00

The installation package to deploy to managed systems can be created directly from BMC ProactiveNet
Central Monitoring Administration:
1. Log on to BMC ProactiveNet Central Monitoring Administration
2. Click the Repository drawer and select Monitoring Repository.
3. Click Add .
4. Select the operating system and platform for which you want to create a package. The components
available in the repository for the selected operating system and platform are displayed.
5. Select the Installation Package Component:
From the Available components list, select Hardware.
From the Version list, select the latest version.
Click the right arrow
button to move the component into the Selected Components list
By default, the appropriate BMC PA TROL A gent for the operating sy stem and platform that y ou chose is
included in the Selected components list.
6.
7.
8.
9.
10.
Click Next. The Add Component Installation Package wizard is displayed.

Go through the wizard and specify the required PATROL information. The Installation Package
Details is displayed:
Verify that:
the operating system and platform are correct
the components that you want to include are listed in the Included Components list.
Provide the following information:
Name: Enter a unique name for the package.
(Optional) Description: Enter a description of the package. The description is displayed in the
Monitoring Installation Packages list on the Monitoring Repository window.
Format: Select a file compression format for the package.
Click Save Installation Package.
Click Close. The package is now available in the Monitoring Installation Packages list.
Importing the Monitoring Solution into Central

Administration
19

Version 1.9.00
Downloading the Installation

Package
You can download an installation package and install the components on one or more hosts. The
installation runs silently with the information entered during package creation.
Recommendation
If you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in the
installation package, ensure the agents are started in phases. Do not start newly deployed agents all
at once. Start and configure monitoring for the agents in planned phases to reduce the performance
impact on the Integration Service nodes and on the BMC ProactiveNet Server associated with the
automatic workflow process.
1. Log on to BMC ProactiveNet Central Monitoring Administration from the computer on which
the PATROL Agent is installed.
2. Click the Repository drawer and select Monitoring Repository.
3. (Optional) To filter the list of installation packages, select an operating system from the Filter by
Operating System list.
4. Click the link for the installation package that you want to download.
5. Through the browser's download dialog box, save the installation package.

1. Copy the installation package to the host where BMC ProactiveNet Performance Management Hardware needs to be installed
2. Extract the installation package as appropriate for your operating system. The package is extracted
to the bmc_products directory on the current host.
3. From the bmc_products directory, run the installation utility for your operating system:
(UNIX or Linux) RunSilentInstall.sh
(Microsoft Windows) RunSilentInstall.exe
The package is installed on the current host. If the package includes a BMC PATROL Agent, the agent
sends a configuration request by passing its tags to BMC ProactiveNet Central Monitoring Administration,
via the Integration Service. Central Monitoring Administration evaluates policies that match the tags,
determines the final configuration to be applied, and sends the configuration information back to the
agent. Monitoring is based on the configuration information received by the agent.
If no policy matches the tags associated with the agent, the agent does not receive configuration
information. The agent does not begin monitoring until a matching policy is created.
20
Integrating the Monitoring Solution

Version 1.9.00
To integrate a BMC PATROL KM into BMC ProactiveNet Performance Management 8.5 or 8.6, you
need to install the KM on top of a PATROL Agent, then add a connection to the system to be monitored
and finally create a specific adapter.
An adapter for BMC PATROL is a software component designed to facilitate the integration of metrics
collected by a BMC PATROL KM into BMC ProactiveNet. The adapter allows you to import application
classes from a BMC PATROL KM into BMC ProactiveNet and displays the performance metrics into your
BMC ProactiveNet Performance Management environment. It also ensures a periodical synchronization
with the KM in order to provide updated and accurate data.
A da pte r for BMC PA T ROL A rchite cture
Two methods exist to create an adapter for BMC PATROL:

The automated workflow (recommended):
This method enables the PATROL Agent to automatically connect to the Integration Service, register
itself, and start sending performance data to the Integration Service. The PATROL Agent is added to
the default profile called "_SA_DEFAULT_" in the Integration Service. The Integration Service uses the
SAdapter (Staging Adapter) to accept inbound connections from the PATROL Agents. The SAdapter is
a component of the Integration Service which is used for the PATROL Agent phone-home feature.
This method requires PATROL Agent v3.8.50 or higher.
22

Version 1.9.00
A utom a te d W orkflow - T he PA T ROL A ge nt conne cts to the Inte gra tion Se rv ice
The manual method:

This method relies on the p3Adapter profile. Each p3adapter is responsible for querying a set of
PATROL Agents in a single security domain and retrieves data. This method is not documented in this
guide.
Ma nua l Me thod - Inte gra tion Se rv ice conne cts to PA T ROL A ge nt
You can also use the following methods to send events directly to the BPPM cell but you would lose the
benefit of the BMC ProactiveNet analytic engine (rate process). The rate process creates the alarms
when thresholds are breached and directly sends them to the BPPM cell.
PATROL Architecture
Method to be Used
PATROL 7
BMC Impact Integration for PATROL v7
PATROL 3
BMC Impact Integration for PATROL V3 (MCXP)
PATROL Agent 9.0
Wpconfig (Events will be directly sent to cells)
For more information about the abov e methods, please refer to the knowledge article:
Integrating the Ev ents Generated by the KMs into BMC Ev ent Manager.
23

Version 1.9.00
Creating and Importing a BPPM

Adapter for a BMC PATROL KM
Creating an Adapter for a BMC PATROL KM
This procedure is only required for BMC ProactiveNet Performance Management 8.5 and 8.6.
1. In Wpconfig, make sure that:

the /AgentSetup/integration/integrationServices is properly set for your PATROL Agents.
It should point to the BPPM Remote Agent where the Integration Service is running (pproxsrv)
using the following syntax: tcp:<BPPM_remote_agent>:3183.
the /AgentSetup/prealoadedKMs variable contains MS_HARDWARE_SENTRY1.km
2. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console
is displayed as shown in the following figure:
A cce ssing the A dm inistra tion ta b in the A dm inistra tion Console
3. Expand the Adapters folder, right-click BMC PATROL, and select Import and Add BMC PATROL.
This action can also be performed from the menu Tools > Configure > Integration Service.
4. Enter the required information:
Creating and Importing a BPPM Adapter for a

BMC PATROL KM
24

Version 1.9.00
Se tting the conne ction pa ra m e te rs
In the Instance Name field, enter a name for this instance of the Adapter that will perform the
integration of the targeted KM into BMC ProactiveNet (e.g. Adapter for Hardware).
From the Source Agent list, select the BPPM remote agent to which your PATROL agents are
sending data to
Enter the Integration Service Agent hostname or IP address
Enter the Integration Service Agent Port. The default port is 3182.
Enter the required credentials to connect to the Integration Service Agent

BMC PATROL KM
25

Version 1.9.00
5. Click Next to continue. If you have correctly set the integrationServices variable as explained
above, your PATROL Agents will be listed:
Re v ie wing the Inte gra tion Se rv ice configura tion
6. Click Next.

BMC PATROL KM
26

Version 1.9.00
Se le cting A pplica tion Cla sse s to im port
7. Select the application classes to import.
Unselecting will delete the application classes that have already been imported during a previous
operation. Application classes ready to be deleted are marked with a red x.
8. Click Next to start the import process. The system displays a summary of the application class
import, click Next to continue.
9. Select the application classes you wish to auto-synchronize with the Integration Service Agent.

BMC PATROL KM
27

Version 1.9.00
Se le cting A pplica tion Cla sse s for A uto-sy nc
10. Click Next to continue

11. If needed, set the Filter details.

BMC PATROL KM
28

Version 1.9.00
Se tting filte r de ta ils
12. Click Next to continue.

13. If needed, set the Auto-sync Poll Interval and/or Timeout.

BMC PATROL KM
29

Version 1.9.00
Sche duling A uto-sy nc polls
14. Click Finish. The system displays a summary of your settings, click Finish to confirm. The Adapter
has been added to the Adapters folder of the Administration Console.
15. To see the class instances that have been imported by the Adapter, expand the Adapters folder,
right-click the Adapter and select Details.
We strongly recommend that you create a specific adapter for each KM you need to integrate into
BMC ProactiveNet to enable the update of a single KM independently.
Updating an Adapter for a BMC

PATROL KM
1. Delete the Adapter instance.
2. Go through the Add an Adapter wizard to actually delete the monitor types that had been created
based on the previous version of the KM.
3. Close.
4. Resume the entire Creating an Adapter for a BMC PATROL KM procedure.

BMC PATROL KM
30

Version 1.9.00
For complete and detailed information on these procedures, please refer to the BMC Proactiv eNet documentation
av ailable from BMC W eb site.
Importing and Customizing

Thresholds
1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW
Commands as Administrator.
La unching BMC Proa ctiv e Ne t PW Com m a nds
2. Execute the following command line:

pw adapter -type patrol -get_thresholds <file name> -pproxy_host <hostname|ipaddress>
[-pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v
where
-get_thresholds <file name> = File name with absolute path at which thresholds will be imported
-pproxy_host <hostname|ipaddress> = Host name or IP Address of Patrol Proxy Server
-pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol
Proxy Server
-pproxy_user <username> = User name of Patrol Proxy user
-pproxy_passwd <password> = Password to authenticate Patrol Proxy user
-i = import Instance level thresholds
Updating an Adapter for a BMC PATROL KM
31

Version 1.9.00
-v = run in "verbose" mode,producing extra lines of output during extraction and conversion
processes
The command has produced a text file with all the parameter threshold settings.
3. Open the file in a text editor. Check that the global thresholds have been properly interpreted.
4. Then go to the # INSTANCE LEVEL THRESHOLDS section of the file.
5. Uncomment all instance level thresholds for the _PATROL__MS_HW_ prefixed instances.
Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properly
converted by the PATROL Adapter.
The import procedure fails to interpret properly the Voltage alert thresholds. If y ou want to activ ate alert thresholds
in BMC Proactiv eNet for Voltage parameters, y ou will need to manually describe them in the tex t file, as in the
ex ample below.
6. Save the file.
7. Execute the following command:

pw threshold loadpatrolthreshold [<thresholdfilename> [-v]]
where:
<thresholdfilename> is a thresholds file name. If no file path is specified then the default
'<Installation Directory>/pw/tmp/' is used
-v enables the Verbose mode
8. Check the result in the BMC ProactiveNet Operations Console. Class-level thresholds can be
displayed using the Absolute Global Thresholds panel in the BMC ProactiveNet Operator Console,
while instance-level thresholds are displayed in the Absolute Instance Thresholds panel:
Importing and Customizing Thresholds
32

Version 1.9.00
Thresholds have been successfully imported into BMC ProactiveNet.
Verifying the Data Collection

You can check that data collection is performed at the BPPM Integration Service and BPPM server levels:
Either by running a command on the BPPM Remote Agent machine where the Integration Service is
running.
Or through the Operations console.
Method 1: Running a Command

1. On the BPPM Remote Agent machine where the Integration Service is running, launch the command
prompt
2. Go to BPPMAgent\Agent\pproxy\PNS\bin
3. Run the following command:
pproxcli >c:\pprox.txt
/connect -host <BPPM_integration_service_hostname> -port <port> -username <username> -password
<password>
Example: /connect -host carnap -port 3182 -username admin -password ******
4. Run the following command:

/PATROL/query/getInstanceData -agent <patrol_agent>:<port>
Example:
/PATROL/query/getInstanceData -agent morgan:3181
5. Check the output (c:\pprox.txt).

6. To get more information about the data collection status, run the following commands:
Command
Description
/PATROL/config/listAgent
List the agents
/PATROL/query/getAgentDetails -agent ALL
Get all the agent details
/PATROL/query/getMonitorDetails -agent ALL
Get all the monitor details
/PATROL/query/getMonitorInstanceDetails -agent ALL
Get the monitor instance details
/PATROL/query/getInstanceData -agent ALL
Get instance data for all patrol agents
/PATROL/query/getInstanceData -agent
<agent_name>:<port_number> -appl
<application_name> -inst <instance_name> -param
<parameter_name>
Get instance data for given agent. Application name,

instance name and parameter name are optional
Method 2: Through the BMC ProactiveNet Operations

Console
1. In the Main navigation pane, click Devices.
Importing and Customizing Thresholds
33

Version 1.9.00
2. Click
to display the Grid View.
3. Select the monitor/parameter for which you want to check the data collection status.
4. Click
and select Show Graph.
5. Click
frame.
Export to Excel to get the list of all the data collection points between a selected time
Managing Baselines and Key

Performance Indicators
In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet
calculates baselines per parameter (metrics or attributes) based on values collected over a specified
period of time to determine a normal operating range. When the collected values for these parameters
are out of range, an alert is triggered.
Some parameters are identified by default as Key Performance Indicators and therefore automatically
included in the base lining calculation.
Managing baselines
The baseline is the expected normal operating range for a metric or attribute of a monitor.
The baseline is calculated by collecting the values for a monitors attributes and metrics over a specified
time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a
given time period) and a high baseline value (consisting of the 90th percentile of all the values for a
given time period), taking a weighted average of these values over time. A higher weight is given to the
latest data being factored into the baseline average. The accuracy of the baseline improves over time.
Requirements for baseline generation

For baselines to be generated for an attribute, that abnormality threshold means that the threshold
exists and is not suppressed.
Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an
active abnormality threshold and are also KPI attributes will have baselines generated for them.
A bsolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.
Managing Key Performance Indicators

The KPI attribute of a parameter can be activated or deactivated manually through the BMC ProactiveNet
Administration Console. In this KM, some parameters or attributes have been designated as important
indicators of performance (KPIs). We do not recommend that these default settings are modified.
Verifying the Data Collection
34

Version 1.9.00
However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration
Console.
To add or remove Key Performance Indicator (KPI) attributes for a

monitor type
1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The
KPI Administration dialog box is displayed.
2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI
attributes. A list of attributes for the selected monitor type is displayed.
3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators:
select the KPI check box to add the corresponding attribute as a KPI
deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor
type
For complete and detailed information on this procedure, please refer to the BMC Proactiv eNet documentation av ailable
from BMC W eb site.
Parameters for which the system by default calculates baselines as well as parameters considered as
KPIs are respectively identified by the following icons:
Baselining
KPI
Managing Baselines and Key Performance

Indicators
35
Configuring After Installation

Version 1.9.00
To configure BMC ProactiveNet Performance Management Hardware Sentry, you need to:
Add a tag to your PATROL Agents.
Create a policy, i.e. a template containing the PATROL Agent configuration.
Assign your policy to one or more PATROL Agents by using the tag that you would have previously
added.
Adding Tags to PATROL Agents

Tags must be set for all your PATROL Agents before creating a policy. If you have not already set your
tags during the installation, you can still manually add them by using wpconfig or PATROL
Configuration Manager.
The variable to add tags to PATROL Agents is:
/AgentSetup/Identification/Tags/TAG/tagName
where tagName must be replaced by the name of the tag (e.g.: sentryTag).
Managing Policies
A policy specifies a set of actions to be taken when a specific condition on the PATROL Agent is fulfilled.
First and foremost, actions include monitor configuration. Once a monitor is configured, policies can also
specify threshold creation and the setting of baselines. A policy can also include intelligent server-side
thresholds so that IT administrators can immediately be alerted on potential problems.
This topic provides general instructions for the following policy management tasks:
Creating a policy
Editing an existing policy
Deleting a policy
Enabling/disabling a policy
Creating a policy
A policy is a template that will be deployed to the PATROL Agent Configuration. To create it:
1. Log on to Central Monitoring Administration.
2. In the Navigation pane, click the Policies drawer and select a policy view (e.g. All).
3. Click Add
to open the Add Policy dialog box.
4. Enter a unique policy Name. In an environment with tenants, policy names must be unique for a
single tenant.
37

Version 1.9.00
5.
6.
7.
8.
(For environments with tenants) Select a Tenant name.

Use the up and down arrows to indicate the Precedence number from 0 to 999.
(Optional) Enter a policy Description.
Enter a Central Monitoring Administration Tag.
Tags are case sensitive and cannot contain spaces or any of the following characters: /, \, {, }, <, >,
, , &.
9. Click the:
Monitor Configuration tab to configure monitor types
Threshold Configuration tab to specify thresholds.
10. Click Save. The policy is then deployed to the PATROL agents.
Policy Precedence
When more than one policy is applied to a BMC PATROL Agent and BMC ProactiveNet Child Server,
configuration is a union of every attribute defined by the policies. If a conflict arises (that is, two policies
configure the same attributes), it is resolved in one of the following ways:
Policies with the same tag: If conflicting policies have the same tag, the precedence value
determines the order the policies are applied. The policy with the lower number value for
precedence is the policy from which the final configuration is applied.
Policies with different tags: If conflicting policies have different tags, then the policies are
applied according to the order they are listed on the BMC PATROL Agent. The policy listed last on
the agent is the policy from which the final configuration is applied.
Editing an existing policy

An existing policy can be edited as follows:
1. In the Navigation pane of Central Monitoring Administration, click the Policies drawer and select a
policy view (e.g. All).
2. Select a policy and click Edit .
3. Click the:
General tab to edit the policy general settings.
Monitor configuration tab to edit the monitor settings.
Threshold settings tab to modify the specified thresholds.
4. Click Update.The updated policy is then deployed to the PATROL agents
Deleting a policy
Deleting a policy deletes all monitor instances and most settings configured through the policy.
Devices remain in the User Groups to which they have been added.
To delete a monitoring policy:

Managing Policies
38

Version 1.9.00
2. Select one or more policies and click Delete

3. Click Yes to confirm deletion.
Enabling/disabling a policy
For maintenance and troubleshooting it can be useful to enable or disable policies. When a policy is
disabled, the policy and its associations remain intact, but the policy configuration is not applied until the
policy is enabled again.
2. Select one or more policies and click:
to enable your policy.
to disable your policy.
Configuring Monitor Settings

When you create or edit a policy, you can add and configure monitor types. The Add Monitor Types
dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that are
located in the Central Monitoring Repository.
To configure the Monitor Type settings

1. Log on to Central Monitoring Administration.
2. In the Navigation pane, click the Policies drawer and select a policy view (e.g. All).
3. Create a new policy or edit an existing one. Click the Monitor Configuration tab.
4.
5.
6.
7.
Click Add .
From the Solution menu, select Hardware.
From the Version menu, select the required version.
From the Monitor Type menu, select the Monitor Type for which you want to add a policy, that
is Hardware.
Creating a Connection to a Device

You can configure BPPM Hardware to monitor devices remotely. To remotely monitor devices, you need
to create a connection to this specific device.
To create a connection to a device:
1. Create a new policy or edit an existing one
Managing Policies
39

Version 1.9.00
40

Version 1.9.00
2. In the Device Information section:

Indicate the name of the device that you wish to monitor.
Enter the IP address of the device. If no IP address is provided, the device name previously
specified will be used.
(Optional for localhost) Select the Device Type.
3. Configure the protocol(s) to be used to monitor the remote device:
SNMP
SSH/Telnet
WBEM
WMI
Cisco UCS
IPMI-Over-LAN
4. (Optional) In the Device Advanced Settings section, click Connectors to choose the mode to be
used:
Select an option from the Connector Selection list:
Automatic (Recommended): to let the solution select the most relevant connectors.
Exclude Specified Connectors: to list the connectors that will not be used by the
solution.
Use Specified Connectors: to list the connectors to be used by the solution. This option
should only be selected and set if instructed by Sentry Support.
If you selected the Exclude Specified Connectors or Use Specified Connectors option, enter
the name of the connectors that will be used or not by the solution. Connector names must be
separated by a comma (,).
Click Close to validate.
5. (Optional) In the Device Advanced Settings section, click Adv. Variables to configure the device
additional configuration variables which will be applied to a single supervised host or device:
Enter the Name and Value of the configuration variable you need to configure. Multiple values
must be separated by a semi-colon (;).
Click Add to List
You can easily modify or remove a variable by selecting it in the list and clicking either the
Modify Selection or the Remove from List buttons.
Click Close to validate.
6. When all the required information is filled, click the Add to List button to validate and add the
defined device to the list below.
7. In the Add Monitor Types dialog box, click Add.
You can then select an ex isting dev ice and click Modify Se le ction to edit the settings of the selected dev ice or also
Re m ov e from List to delete the selected dev ice.
41

Version 1.9.00
Using the SNMP Protocol

You can use the SNMP protocol to monitor the hardware of servers and storage devices which are
instrumented through SNMP.
To monitor a server using the SNMP protocol:
1. First, create a connection to the device to be monitored.
2. Click SNMP.
SNMP Cre de ntia ls
3. Enter the SNMP Community String to use to perform SNMP v1 queries.

4. Use the spin button to indicate the SNMP port number you wish to use to perform SNMP queries.
By default the SNMP queries are performed through port 161.
5. Click Close to validate your creation.
6. In the Hardware Configuration section, click the Add to List button to validate your
configuration.
42

Version 1.9.00
Using the SSH/Telnet Protocol

SSH/Telnet (Secure Shell/TerminaL NETwork) can for example be used to monitor Linux/UNIX servers
or to communicate remotely with systems and devices which have an SSH/Telnet interface on their
management card on which commands can be run to determine their status, performance or capacity.
43

Version 1.9.00
To monitor a server using the SSH/Telnet protocol:

2. Click SSH/Telnet.
SSH/T e lne t Cre de ntia ls
3. In the SSH/Telnet section:

Select the Authentication Mode to use to establish a connection with the remote device.
Enter the Username to use to establish the connection with the remote device.
Enter the Password to use to establish the connection with the remote device. A Passphrase
may be required to establish a connection through SSH with Authentication Key.
Enter the OpenSSH Private Key File required for establishing connection through SSH with
Authentication Key. The key file must be accessible by the PATROL Agent that will make the
connection to the remote host through the SSH/Telnet protocol.
4. In the Sudo Options section:
Check the Use When root Privileges are Needed option to use the "sudo" utility in order to
execute external commands as "root" on UNIX/Linux platforms.
Enter the Sudo Command Line to execute.
configuration.
44

Version 1.9.00
Using the WBEM Protocol

You can use the WBEM (Web-Based Enterprise Management) protocol to communicate directly with a
SMI-S Provider/storage system and collect information.
To monitor a server using the WBEM protocol:
2. Click WBEM.
W BEM Cre de ntia ls
3. Enter the Username, Password and Port Number to use to establish the connection with the
remote device using the WBEM protocol.
4. Specify the port number. By default port 5989 is used for encrypted connections and 5988 for nonencrypted connections.
5. Check the Encryption option if the port used is 5989.
6. In the Advanced Options section:
Enter the IP address/device name of the Multi-Tier Authentication Server. This option is
mostly used for VMware servers. If left blank, the solution will automatically use the WBEM
credentials.
Enter the WBEM Namespace. Leave blank to let the solution detect the proper name
(recommended).
configuration.
45

Version 1.9.00
Using the WMI Protocol

You can use the WMI (Windows Management Instrumentation) protocol to remotely monitor systems or
devices:
2. Click WMI.
W MI Cre de ntia ls
3. Enter the Username and Password to use to establish the connection with the remote device
using the WMI protocol.
configuration.
Using the Cisco UCS Manager

To collect information about Cisco UCS Blade Chassis and Cisco Fabric Interconnect Switch:
2. Click Cisco UCS.
Cisco UCS Cre de ntia ls
46

Version 1.9.00
3. Enter the Username and Password to use to establish the connection with the Cisco Unified
Computing System.
4. Uncheck the Encryption option to disable the SSL Encryption for UCS login (HTTPS). By default,
the encryption is always enabled.
configuration.
Using the IPMI-Over-LAN Protocol

IPMI-Over-LAN is the out-of-band interface used by BPPM Hardware to bypass the usual hardware
agents and communicate directly with the motherboards BMC chip.
To monitor a server using the IPMI-Over-LAN protocol:
2. Click IPMI-Over-LAN.
IPMI-ov e r-LA N Cre de ntia ls
3. Enter the Username and Password to use to establish the connection with the IPMI chip out-ofband (IPMI-over-LAN).
configuration.
Configuring Global Alert Settings

Configuring Global Alert Settings consists in indicating:
the specific actions to be executed when a hardware failure is detected.
the number of consecutive times an attribute has to stay above (or below) the threshold for an alert
to be triggered.
the action to perform when the solution returns an Unknown Status on a device.
the delay after which Error Count attributes should be reset.
47

Version 1.9.00
Configuring Alert Actions

Alert Actions enable the administrator to choose specific actions to be executed when a hardware
failure is detected. With Alert Actions, it is possible to customize the way a hardware problem
notification is performed.
BPPM Hardware can be configured to run one, several, or all types of Alert Actions when an alert is
triggered regarding the monitored hardware.
To set the alert actions you want the solution to perform when a problem occurs:
1. Configure the Monitor Settings.
2. In the Global Alert Settings section, click Alert Actions.
Configuring A le rt A ctions
3. Select the type of event you want the solution to perform Upon a Hardware Problem Trigger
field and Upon a Connector Failure Trigger:
A STD 41 PATROL Event
A Specific PATROL Event
No Event
These ev ents are generated ev ery time a threshold is ex ceeded. They contain a full Hardware Health Report
detailing the fault that has occurred.
4. (BPPM 9.5 only) Check the Enable Annotations option to make the solution annotate the
parameters graph with a comprehensive report of the problem.
5. Click Close to save your settings.
48

Version 1.9.00
Configuring Alert Delay

Configuring the alert delay consists in indicating the number of consecutive times an attribute has to
stay above (or below) the threshold for an alert to be triggered. This setting will prevent false alerts to
be triggered. It can be applied on:
Numeric parameters (e.g.: Error Count parameters)

Discrete parameters (e.g.: Predicted Failure, Need Cleaning, status, etc.)
Connector Status Parameters
Present Parameters
To configure the Alert Delay:

2. In the Global Alert Settings section, click the Alert Delay button.
Configuring A le rt De la y
3. Use the spin button to indicate the number of consecutive times parameters have to stay above (or
below) the threshold of an alert to be triggered.
Configuring the Unknown Status

BPPM Hardware returns an Unknown Status when it is unable to detect the status of a monitored
device. Even though this situation is rare, you may want to get notified of this Unknown Status in a
particular way such as a warning or an alarm. To get this specific notice, you need to tell BPPM
Hardware how you want the Unknown Status to be interpreted by using the Unkn Status setting.
To configure the Unknown Status:
2. In the Global Alert Settings section, click Unkn Status.
49

Version 1.9.00
Configuring the Unknown Sta tus
3. From the drop-down list, select:

Nothing not to feed the Status attribute
0 (OK) to set the Status attribute to OK (default)
1 (Warning) to trigger a WARNING on the Status attribute
2 (Alarm) to trigger an ALARM on the Status attribute
Automatically Resetting Error Count Parameters

Error Count parameters keep increasing as new errors are encountered. To reset these parameters,
you can configure BPPM Hardware to automatically acknowledge an alert on the Error Count
parameters and reset it to zero after a specified period of time.
To automatically reset the Error Count Parameters:
2. In the Global Alert Settings section, click Auto Reset.
A utom a tica lly Re se tting ErrorCount Pa ra m e te rs
3. From the Error Count Parameters list, select the period of time after which you want the solution
to automatically reset the Error Count parameters.
50

Version 1.9.00
Configuring Global Advanced Settings

Configuring Global Alert Settings consists in:
indicating the credentials to be used to perform local commands.
specifying the discovery and polling intervals.
enabling the debug mode.
configuring additional variables.
Configuring Local Commands

To collect hardware information about the local host where the PATROL Agent is installed, you may
have to specify the credentials that will be used by BPPM Hardware to run the required commands.
To specify these credentials:
2. In the Global Advanced Settings section, click Local Cmd.
Configuring the Loca l Com m a nds
3. Enter the Username and Password to use to run OS commands on the local device (localhost)
4. (UNIX/Linux platforms) Configure the Localhost Sudo Options:
Check the Use When root Privileges are Needed option to use the "sudo" utility to execute
external commands as "root
Enter the Sudo Command Line to execute
51

Version 1.9.00
Configuring Intervals
BMC ProactiveNet Performance Management - Hardware periodically performs discoveries to detect new
components in your monitored environment. By default, the solution runs a discovery every hour, but
you can customize this interval to match your specific needs.
To configure the discovery and polling interval

2. In the Global Advanced Settings section, click Intervals.
Configuring the Discov e ry Inte rv a l
3. Use the spin buttons to:

Enter the frequency (in minutes) of the discovery process. By default, the discovery interval is set
to 60 minutes
Enter the interval at which the solution must poll the managed systems to collect hardware health
data. By default, the polling interval is set to 2 minutes
52

Version 1.9.00
Enabling the Debug Mode

When you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the
Debug Mode and provide the debug output to the Sentry Software support team.
To enable the debug mode

2. In the Global Advanced Settings section, click Debug.
Ena bling the De bug Mode
3. Check the Enable Debug Mode option. The solution will store debug information in a log file. By
default debug files are stored in the %PATROL_HOME%\log folder
4. In the Debug End Time field, enter the date and time at which the system must stop logging
debug information. The required format is: yyyy/mm/dd hh:mm:ss based on a 24 hour-day
For the debug mode to be enabled, the Enable Debug Mode must be checked and the Debug End
Time must be properly set to a date and time in the future.

53

Version 1.9.00
Setting Additional Configuration Variables

Advanced configuration variables can be used to manually set variables that cannot be configured
through the CMA interface.
These variables should only be set when instructed by Sentry Software Support.
To set configuration variables

2. In the Global Advanced Settings section, click Add Variables.
Se tting Configura tion Va ria ble s
3. Enter the Name and Value of the configuration variable you need to configure. Multiple values must
be separated by a semi-colon (;).
Variables
Description
automaticReinitialization
If set to 1, triggers a re-initialization of BPPM Hardware. The discovery checks

this variable every hour (by default) and deletes it before performing the reinitialization.
collectionHubHeapSizeMax
Maximum heap size in megabytes allocated to the Java Collection Hub.

Default: Not set (assumed 128 MB).
54

Version 1.9.00
Variables
Description
collectionHubHeapSizeMin
Minimum heap size in megabytes allocated to Java Collection Hub.

Default: Not set (assumed 128 MB).
collectionHubOverrideJavaCommandLine Command line used by BPPM Hardware to launch the Java Collection Hub. This
variable should only be set if instructed by Sentry Support.
collectTimeout
Maximum time in seconds the collectors wait for the previous collection to
complete. When this timeout is reached, it means the previous collection did
not complete in a timely fashion.
Default: Not set (assumed 300 seconds).
currentVersion
Indicates the version level of the configuration. This should always match with
the version of BPPM Hardware. BPPM Hardware uses this variable to perform
migration operations on the configuration variables. The variable is
automatically set during its initialization.
Default: 1.9.00.
deactivatedDeviceClassList
List of monitor types that are deactivated, for which no discovery and no
collection will be performed. Use this variable to completely disable the
monitoring of a specific type of objects.
defaultCommandTimeout
Timeout in seconds used when BPPM Hardware executes an OS Command.

Default: 30. Unit: seconds
dirCommand
OS Command used to list the files in a directory. This command is used to find
the installed connectors in the "hdfPath" directory.
Default:
On Windows: dir /A:-D /B /O:-D /T:W /S %{FOLDERPATH}
On UNIX/Linux: ls -atpR1 %{FOLDERPATH}
disableDebugSNMPWalk
When set to 1, prevents BPPM Hardware from performing an SNMP dump of

the monitored systems in debug mode.
Default: Not set.
disableForcedDefaultAccount
When set to 1, prevents BPPM Hardware from explicitly using the /

AgentSetup/defaultAccount credentials when running external commands.
Default: Not set.
disableI2D
If set to 1, no MetaTokenID and no MetaFQDN information will be set in the

PATROL namespace for any host.
disableJRECheck
When set to 1, disable the validation tests of the JRE used by BPPM Hardware
to run Java code. This can be used to force BPPM Hardware to use a non-Sun
or non-Oracle JRE.
disableMissingDeviceDetection
When set to 1, disables the missing device detection mechanism of BPPM

Hardware. By default, BPPM Hardware raises an alarm for devices that were
discovered and that are no longer discovered.
Default: Not set
disablePslExecuteBugWorkaround
When set to 1, deactivates the workaround for a bug in the PslExecute() PSL
function.
If BPPM Hardware detects that the version of the PATROL Agent is affected
by the PslExecute() bug, it uses an alternate technique to create
asynchronous threads with the event_trigger() function and the RemPsl
standard event. The disablePslExecuteBugWorkaround variable disables this
workaround.
findWbemNamespaceTimeout
Number of seconds after which a remote BPPM Hardware stops trying to get a
server namespace via WBEM.
Default value: 1200.
55

Version 1.9.00
Variables
Description
forceSnmpSerialization
Maximum time in seconds the main discovery process waits for the previous
discovery to complete. When this timeout is reached, it means the previous
discovery did not complete in a timely fashion.
globalDiscoveryTimeout
Maximum time in seconds the main discovery process waits for the previous
discovery to complete. When this timeout is reached, it means the previous
discovery did not complete in a timely fashion.
hdfPath
Alternate path where the connector files (*.hdf) are stored.

Default: Not set (assumed $PATROL_HOME/lib/MS_HW_hdf).
individualDiscoveriesTimeout
Maximum time in seconds the monitor type-specific discovery processes wait

for the previous discovery to complete. When this timeout is reached, it means
the previous discovery did not complete in a timely fashion.
intrusionDetectionAlert
Alert settings for enclosure intrusion detection. Possible values are:

Never: No alert will ever be triggered even if the enclosure is opened
Always: An alert will be always triggered when the enclosure is opened
Default: An alert will be triggered only if a previously closed enclosure is
detected open
ipmiTimeout
Time in seconds after which IPMI queries are considered as failed.

Default value: Not set (assumed 300 seconds).
ipmitoolPath
Indicates the path to the ipmitool utility on Linux and Solaris systems. This can
be used if BPPM Hardware cannot find the location of the ipmitool utility
automatically.
Default: Not set.
javaPassword
Password associated to the javaUsername variable. Default: Not set (BPPM

Hardware will search for a suitable JRE automatically).
javaPath
Path to the folder containing the Java executable used by the Collection Hub.
javaUsername
Username used to launch the Java Collection Hub.

Default: Not set.
maxConcurrentCollectThreads
Maximum number of concurrent collection threads.

Default: 50.
maxConcurrentDiscoveryThreads
Maximum number of concurrent discovery threads.

Default: 10.
noMissingDeviceDetectionClasses
List of monitor types that will not trigger "missing device" alerts. Typically, the
related monitor types are:
Hardware Logical Disk
Hardware Voltage
Hardware Enclosure
Hardware LED.
pathToAWK
Path to the nawk or awk executable.
pathToAWKUnix
Same as pathToAWK, but only applicable to UNIX agents.
pathToAWKWindows
Same as pathToAWK, but only applicable to Windows agents.
pausedObjectList
Lists the PATROL object path of paused objects.
56

Version 1.9.00
Variables
Description
pemMessages
How much internal information should be sent as PATROL events.

When set to all, all internal BMC ProactiveNet Performance Management Hardware messages (problems and informational messages).
When set to problems, only errors and problems.
When set to none, no internal message at all.
Note: This doesnt affect the reporting of actual hardware problems.
Default: all.
remoteCommandMaxConnectionsPerHos Maximum number of Telnet or SSH sessions opened at once for a single host.
t
Default: Not set (assumed 5).
remoteCommandTimeout
Number of seconds after which a remoteOS command execution will be killed.

snmpTimeout
Timeout in seconds when performing SNMP queries. Only applicable when

forced SNMP serialization has been enabled (/SENTRY/HARDWARE/
forceSnmpSerialization)
snmpWalkMaxItems
Maximum number of variables that can be processed by a single SNMP walk

operation.
Default: Not set.
sshClientJarPath
Path to the SSH client JAR file.

Default: Not set.
This variable should only be set if instructed by Sentry Support.
sshCommandJarPath
Path to the SSH command JAR file.

Default: Not set.
startupDelay
Allows the administrator to specify the number of seconds that BPPM Hardware
will wait before starting its platform detection and discovery. This variable may
be useful on fast booting computers where the PATROL Agent starts before
other important instrumentation services, which causes false alerts.
Default: Not set (zero).
tableJoinTimeout
Timeout in seconds when performing a Table Join.

Default: 60.
telnetClientJarPath
Path to the Telnet client JAR file.

Default: Not set.
telnetCommandJarPath
Path to the Telnet command JAR file.

Default: Not set.
telnetConnectionMethod
Default (Windows): Java (if configured in the KM)

Note: If the PATROL Agent version is 3.6.011 or later the connection method
used by BPPM Hardware is 'sopen'; otherwise it is left blank.
Default (UNIX): Telnet.
ThresholdManagementMode
Specifies how BPPM Hardware should manage the alert thresholds on

attributes. Possible values:
as (through PATROL for Event Management)
tuning (through the standard "Override attribute" mechanism)
none (No threshold is set by BPPM Hardware)
Default: Tuning.
57

Version 1.9.00
Variables
Description
ucsJarPath
Path to the Cisco UCS client JAR file.

Default: Not set.
ucsTimeout
Timeout in seconds when performing a UCS queries.

ucsVbsPath
Path to the Cisco UCS Windows client.

Default: Not set.
UNIXConsoleMode
When set to 1, makes BPPM Hardware use short display name for the icons in
the PATROL Consoles. This can be useful for UNIX PATROL Classic Consoles
but this flags affects every console connected to the agent.
Default: Not set.
wbemTimeout
Timeout in seconds for a WBEM query to complete.

wmiScriptPath
Path to the script used to perform WMI queries on Windows.

Default: Not set (use the default WMI client provided with the KM).
4. Click Add to List

You can easily modify or remove a variable by selecting it in the list and clicking either the Modify
Selection or the Remove from List buttons.
58

Version 1.9.00
Scheduling Automatic Reports

BMC ProactiveNet Performance Management - Hardware can automatically produce text reports about
the monitored systems.
To schedule automatic reports

2. In the Reporting section, click Schedule.
Sche duling a utom a tic re ports
3. In the Schedule section, specify the time at which the report(s) must be generated.
4. Check the:
Energy Usage report type to automatically generate an Energy Usage report that will be saved
by default as MS_HW_energyUsage*.csv in the %PATROL_HOME%\log folder
Ethernet/Fiber Port Activity report type to automatically generate an Ethernet/Fiber Port
Activity report that will be saved by default as MS_HW_networkActivity*.csv in the %
PATROL_HOME%\log folder
Hardware Inventory report type to automatically generate a Hardware Inventory report that
will be saved by default as MS_HW_hardwareInventory*.csv in the %PATROL_HOME%\log folder
Updating a policy that sets the scheduling options of a report purges the report configuration v ariables and stops the
report process
The history retention period can be set from the PA TROL Console or from the PA TROL A gent using a configuration
v ariable. The default collection (retention) period is one day . W henev er a stored parameter v alue ex ceeds its
retention period, it is automatically deleted from the parameter history file. Refer to BMC documentation for details.
59

Version 1.9.00
When you are creating or editing a policy, you can add and configure monitor thresholds. The Add
Thresholds dialog box presents threshold configuration fields for BMC ProactiveNet monitors that are
configured through Central Monitoring Administration.
For details about baselines and Key Performance Indicators (KPI), see BMC ProactiveNet Central
Monitoring Administration or BMC ProactiveNet documentation or refer to the Managing Baselines and
Key Performance Indicators section. For details about the monitored attributes, refer to the specific
monitor type in the Reference Guide section.
Before you begin

Ensure that your monitor configuration is complete before thresholds are applied. Thresholds cannot be
applied to monitors that are not configured through Central Monitoring Administration. If you have not
done so already, please refer to the section Configuring Monitor S ettings.
Recommended Thresholds
Thresholds define acceptable high and/or low values for the data collected. Thresholds can be created
as part of a policy that can be applied to multiple monitor types on multiple BMC PATROL Agents.
The Reference Guide provides a list of monitor types with their respective attributes and, when
meaningful, a recommended threshold.
Configuring Monitor Thresholds

To configure monitor thresholds:
1. Create a new policy or edit an existing one.
2. Select the Threshold Configuration tab and click Add .
3. In the Add Thresholds dialog box, select the relevant Solution, Version, and Monitor Type.
4. In the Instance Name field, specify the instance to which the threshold configuration will be
applied. You can either use a string or the following regular expression patterns: ?, +, *, ( ), |, [ ],
{ }, ^, $,
5. Select Match Device Name if you want the entire <deviceName>\<instanceName> string to be
considered.
6. From the Attribute list, select a monitor attribute.
7. In the Threshold section:
Select the threshold type.
Set the threshold parameters values.
Click Add.
60

Version 1.9.00
8. Resume the procedure to configure all the monitor thresholds required.

9. Click Close. The configuration details are displayed in the table on the Threshold Configuration
tab.
10. Click Save at the bottom of the Add Policy dialog box, or Update at the bottom of the Edit Policy
dialog box.
After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agents
with matching Central Monitoring Configuration tags.
Editing a Threshold Configuration

To edit a threshold configuration:
1.
2.
3.
4.
5.
Edit an existing policy

On the Threshold Configuration tab, select a threshold definition, and click Edit.
Edit the configuration values and click Update.
When you finish editing the threshold configuration, click Close.
To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.
After you update the policy, updated threshold configurations are pushed to BMC PATROL Agents with
matching Central Monitoring Configuration tags.
Deleting a Threshold Configuration

To delete a threshold configuration:
1. Edit an existing policy
2. On the Threshold Configuration tab, select attributes, monitor types, versions, or
solutions.
3. Click Delete.
4. After you delete one or more threshold configurations, click Close.
5. To save changes to the policy, click Update at the bottom of the Edit Policy dialog box.
After you update the policy, deleted threshold configurations are removed from BMC PATROL Agents
with matching Central Monitoring Configuration tags.
61
Reference Guide

Version 1.9.00
Monitor Types and Attributes

Introduction
This chapter lists all the monitor types and attributes provided by BMC ProactiveNet Performance
Management - Hardware to monitor your systems.
Please note that depending on the type of managed systems, some attributes may not be available.
Monitor Types
Hardware Battery
Hardware Blade
Hardware Capacity Report
Hardware CPU Core
Hardware Enclosure
Hardware Fan
Hardware LED
Hardware LUN
Hardware Memory Module
Hardware Network Interface
Hardware Other Device
Hardware Physical Disk
Hardware Power Supply
Hardware Processor
Hardware Robotics
Hardware Sentry Connector
Hardware Tape Drive
Hardware Voltage
Baselines and Key Performance Indicators

Some attributes are identified by default as Key Performance Indicators (KPIs) and therefore
automatically included in the base lining calculation. To learn more about auto baselining and KPIs,
please refer to the Managing Baselines and Key Performance Indicators chapter.
In this guide, attributes flagged as KPIs and included by default in the baseline calculation process are
respectively identified by the following icon: KPI
63

Version 1.9.00
Managing Baselines and Key Performance

Indicators
In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet
calculates baselines per attributes based on values collected over a specified period of time to
determine a normal operating range. When the collected values for these attributes are out of range, an
alert is triggered.
Some attributes are identified by default as Key Performance Indicators (identitied with the
therefore automatically included in the base lining calculation.
icon) and
Managing baselines
The baseline is the expected normal operating range for a metric or attribute of a monitor.
The baseline is calculated by collecting the values for a monitors attributes and metrics over a specified
time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a
given time period) and a high baseline value (consisting of the 90th percentile of all the values for a
given time period), taking a weighted average of these values over time. A higher weight is given to the
latest data being factored into the baseline average. The accuracy of the baseline improves over time.
Requirements for baseline generation

For baselines to be generated for an attribute, that abnormality threshold means that the threshold
exists and is not suppressed.
Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an
active abnormality threshold and are also KPI attributes will have baselines generated for them.
A bsolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.
Managing Key Performance Indicators

The KPI attribute of an attribute can be activated or deactivated manually through the BMC ProactiveNet
Administration Console. In this KM, some attributes have been designated as important indicators of
performance (KPIs). We do not recommend that these default settings are modified.
However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration
Console.
To add or remove Key Performance Indicator (KPI) attributes for a

monitor type
1. In the Administration Console, from the menu bar, choose Tools > KPI Administration. The
64

Version 1.9.00
KPI Administration dialog box is displayed.

2. From the Monitor Type list, choose the monitor type for which you want to add or remove KPI
attributes. A list of attributes for the selected monitor type is displayed.
3. In the KPI column for the attributes that you want to add or remove as Key Performance Indicators:
select the KPI check box to add the corresponding attribute as a KPI
deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor
type
For complete and detailed information on this procedure, please refer to the BMC Proactiv eNet documentation av ailable
from BMC W eb site.
Hardware Battery
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Charge*
Percentage of the battery charge.
Warning 50
Alarm 30
Statistics
Present
When the battery is no longer discovered,

the attribute goes into alarm.
{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Status*
Battery Status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
* These attributes are used by default when v isualizing the corresponding monitor instance in BPPM.
65

Version 1.9.00
Hardware Blade
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Power State
Indicates whether the blade is currently on or {0 = Off

off
;2=
On}
None
Availability
Present
When the blade is no longer discovered, the

attribute goes into alarm.
{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Status*
Blade Status.
{0 = OK; 1 = Warning
1=
2 = Alarm
Degrade
d; 2 =
Failed}
Availability
* This attribute is used by default when v isualizing the corresponding monitor instance in BPPM.

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
CPU Count
Host total number of physical processors

(CPU).
CPUs
None
Statistics
Connected Ports
Number of connected ports.
ports
None
Statistics
Degrees Below Warning*
Number of degrees before reaching the

closest warning threshold.
degrees
Celsius
None
Statistics
Logical Disk Size
Host total logical disk size.
Gigabyte None
s (GB)
Statistics
Memory Size
Host total memory (RAM).
Gigabyte None
s (GB)
Statistics
Physical Disk Size
Host total physical disk size.
Gigabyte None
s (GB)
Statistics
Power Consumption*
Power consumed by the host.
Watts
None
Statistics
Unallocated Disk Space
Host Total available disk space that is not

allocated to any volume.
Gigabyte None
(GB)
Statistics
66

Version 1.9.00
For detailed information about
K P I, see Managing Baselines and Key Performance Indicators.
Hardware CPU Core

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Present
When the CPU Core is no longer discovered,

the attribute goes into alarm.
{0 =
Missing;
1=
Present}
0 = Alarm
Status*
CPU Core Status.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
Availability
Used Time Percent
Percentage of the CPU Core usage.

The "Used Time Percent" attribute is
calculated as: (UsedTime - LastUsedTime) /
(currentTime - lastTime) *100
Percenta None
ge (%)
Statistics
Availability

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Battery Status*
This attribute triggers an alert to predict that

the disk controller battery will be unable to
support the controller in the event of a
power failure.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Controller Status*
This attribute displays the status of the disk

controller.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Present
When the disk controller is no longer

discovered, the attribute goes into alarm.
{0 =
Missing;
1=
Present}
0 = Alarm
Availability
67

Version 1.9.00
Depending on y our sy stem, all attributes may not be used. Only one of the attributes may be v isible. This will not
affect the proper monitoring of the dev ice.
68

Version 1.9.00

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Intrusion Status
This attribute will trigger an alarm if the

enclosure is open or not properly closed.
2=
2 = Alarm
Intrusion
Detected
}
Availability
Present
When the disk enclosure is no longer

{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Status*
Enclosure Status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
69

Version 1.9.00
Hardware Enclosure
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Intrusion Status
This attribute will trigger an alarm if the

enclosure is open or not properly closed.
{0 = OK; 2 = Alarm
2=
Intrusion
Detecte
d}
Availability
Power Consumption*
This attribute reports the electricity

consumption.
Watts
Statistics
Status
Enclosure Status.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
None
Availability
Hardware Fan
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Present
When the fan is no longer discovered, the

attribute goes into alarm.
{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Speed*
Fan Speed.
Revoluti
ons per
minutes
(RPM)
Automatic
Statistics
Speed Percent
Fan Speed as a percentage of its maximal

speed.
% of
Automatic
maximum
speed
Statistics
Status*
Fan Status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
Availability
70
1 = Warning
2 = Alarm

Version 1.9.00
Hardware LED
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Color
Color of the LED.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Status*
Led Status.
{0 =
Off; 1 =
Blinking;
2 = On}
1 = Warning
2 = Alarm
Availability

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Error Count
Number of errors encountered by the

physical disk.
Errors
None
Statistics
Status*
Logical Disk status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Unallocated Space
Amount of unused disk space in the logical

disk (i.e. not allocated to the higher layer or
the operating system).
Gigabyte
s (GB)
None
Statistics
71

Version 1.9.00
Hardware LUN
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Available Path Count*
Number of distinct paths available to the

remote volume.
Paths
Warning
Statistics
when
downgrades
or fewer than
expected.
Alarm when 0
Present
When the remote volume is no longer

{0 =
Missing;
1=
Present}
0 = Alarm
Status*
Availability of the remote volume.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
72
Availability
Availability

Version 1.9.00

Attributes
Attribute
Description
Unit
Default Alert
Thresholds
Type
Error Count
Number of detected (and possibly,

corrected) errors.
Errors
1 = Warning
Statistics
Error Status
This attribute will trigger an alert if the

number of memory errors reaches a
threshold set by the manufacturers agent.
{0 = No
Errors; 1 =
Detected
Errors; 2 =
Too Many
Errors}
1 = Warning
2 = Alarm
Availability
Predicted Failure This attribute will trigger a warning if a

memory failure is predicted to happen.
{0 = OK; 1
= Failure
Predicted}
1 = Alarm
Availability
Present
When the memory module is no longer

{0 =
Missing; 1 =
Present}
0 = Alarm
Availability
Status*
Memory Status.
{0 = OK; 1
=
Degraded; 2
= Failed}
1 = Warning
2 = Alarm
Availability

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Bandwidth Utilization
Percentage used of the available bandwidth.
Percenta
ge (%)
Automatic
Statistics
Duplex Mode
Whether the port is configured to operate in

half-duplex or full-duplex mode.
{0 =
Halfduplex;
1 = Full
duplex}
Automatic
Availability
73

Version 1.9.00
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Error Percent
Transmitted and received packets in error as

a percentage of all processed packets.
Percenta
ge (%)
Automatic
Statistics
Link Speed
Negotiated or configured link speed.
Megabits
per
seconds
(Mbits/s)
Automatic
Statistics
Link Status
This attribute will trigger a warning if the

network interface is not connected (i.e. no
wire plugged-in).
{0 =
Plugged;
1=
Unplugg
ed}
1 = Alarm
Availability
Present
When the network adapters are no longer

{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Received Bytes Rate*
Received network traffic in megabytes per

second.
Megabyt
es per
seconds
(MB/s)
None
Statistics
Received Packets Rate
Received network traffic in packets per

second.
Packets
per
second
None
Statistics
Status
Network interface Status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Transmitted Bytes Rate*
Emitted network traffic in megabytes per

second.
Megabyt
es per
seconds
(MB/s)
None
Statistics
Transmitted Packets Rate
Emitted network traffic in packets per

second.
Packets
per
second
(packets
/s)
None
Statistics
Zero Buffer Credit Percent
Percentage of zero buffer credits that

occurred over the last polling interval.
Percenta
ge (%)
None
Statistics
74

Version 1.9.00

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Present
When the device is no longer discovered, the

attribute goes into alarm
{0 =
Missing;
1=
Present}
0 = Alarm
Status*
Device Status.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
Availability
Usage Count
Number of times the device has been used.
Times
Automatic
Statistics
Value
Device value.
n/a
Automatic
Statistics
Availability
Hardware Physical Disk

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Device Not Ready Error

Count
Number of not ready device errors that the

disk has encountered since the last
reinitialization, or since the last manual reset.
Errors
Alarm 1
Statistics
Error Count
Number of errors that the disk has

encountered since the last reinitialization, or
since the last manual reset.
Errors
Automatic
Statistics
Hard Error Count
Number of hard errors that the disk has

Errors
Alarm 1
Statistics
Illegal Request Error Count
Number of illegal request errors that the disk

has encountered since the last reinitialization,
or since the last manual reset.
Errors
None
Statistics
Media Error Count
Number of media errors that the disk has

Errors
Alarm 1
Statistics
No Device Error Count
Number of no device errors that the disk has

Errors
Alarm 1
Statistics
75

Version 1.9.00
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Predicted Failure
Informs if a failure is predicted.
{0 = OK;
1=
Failure
Predicte
d}
1 = Alarm
Availability
Present
When the physical disk is no longer

discovered, the attribute goes into alarm
{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Recoverable Error Count
Number of recoverable errors that the disk

has encountered since the last reinitialization,
or since the last manual reset.
Errors
None
Statistics
Status*
Physical Disk status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Transport Error Count
Number of transport errors that the disk has

Errors
Alarm 1
Statistics
76

Version 1.9.00
Hardware Power Supply

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Present
When the power supply is no longer

{0 =
Missing;
1=
Present}
0 = Alarm
Status*
Power Supply status.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
Availability
Used Capacity
Percentage of the Power Supply power

currently in use if available.
Percenta Automatic
ge (%)
Statistics
Availability
Hardware Processor
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Corrected Error Count
Number of detected and corrected errors.
Errors
None
Statistics
Current Speed
CPU speed.
MHz
None
Statistics
Predicted Failure
This attribute will trigger a warning if a CPU

failure is predicted to happen.
{0 = OK;
1=
Failure
Predicte
d}
1 = Warning
Availability
Present
When the physical processor is no longer

{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Status*
CPU Status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
77

Version 1.9.00
Hardware Robotics
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Error Count*
Number of moves in failure.
Errors
Automatic
Statistics
Move Count
Number of moves performed by the robot.
Moves
None
Statistics
Present
When the robotics is no longer discovered,

the attribute goes into alarm
{0 =
Missing;
1=
Present}
0 = Alarm
Availability
Status*
Device Status
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Hardware Sentry Connector

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Status*
Connector Status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
78
Collection
Status

Version 1.9.00
Hardware Tape Drive

Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Error Count
Number of tape drive failures.
Errors
Automatic
Statistics
Mount Count
Number of mount operations that happened

during the last collect interval. The attribute
remains to zero when no mount operation
occurs.
Mounts
None
Statistics
Needs Cleaning*
Indicates whether the tapedrive needs

cleaning.
1=
2 = Alarm
Cleaning
Needed;
2=
Cleaning
Needed
Immedia
tely}
Statistics
Present
When the tape drive is no longer discovered,

the attribute goes into alarm
{0 =
Missing;
1=
Present}
Availability
Status*
Device status.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
Availability
Unmount Count
Number of unmount operations that

happened during the last collect interval. The
attribute remains to zero when no unmount
operation occurs.
Unmount
s
Statistics
0 = Alarm
None
79

Version 1.9.00
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Status
Temperature status.
{0 = OK;
1=
Degrade
d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Temperature*
Temperature reading.
Degrees
Celsius
(C)
Automatic
Statistics
For detailed information about
K P I, see Managing Baselines and Key Performance Indicators.
Hardware Voltage
Attributes
Attribute
Description
Unit
Default
Type
Alert
Thresholds
Status
Voltage status.
1=
2 = Alarm
Degrade
d; 2 =
Failed}
Availability
Voltage*
Voltage reading.
Millivolt
(mV)
Statistics
Automatic
80

Version 1.9.00
Device Additional Configuration

Variables
The following table contains the list of the device additional configuration variables which can be added
in the Device Advanced Settings section when configuring monitor settings. These variables will be
applied to a single supervised host or device.
These variables should only be set when instructed so by Sentry Software Support.
Variables
Description
defaultWattage
Assumed power consumption in Watts of the monitored server. This value will be
used instead of the measured or estimated value. Use this variable to override a
Power Consumption attribute value that seems unlikely.
forceWmiNamespace
Forces the use of a specific WMI namespace instead of letting BPPM Hardware
decide the suitable namespace.
Default: Not set
ipmitoolCommand
To override the command line used by BPPM Hardware to perform IPMI requests on
Linux and Solaris systems. The specified command needs to provide the exact
command to be executed with the following macros:
%{IPMICOMMAND} (will be replaced with mc info, sdr, fru, etc. at run time)
%{USERNAME}
%{PASSWORD}
Example: /usr/bin/ipmitool %{COMMAND} u %{USERNAME} p %
{PASSWORD}.
Default: Not set (BPPM Hardware will find the suitable ipmitool command to run
automatically).
networkLinkAlarmType
Type of alert for the Link Status attribute of the Hardware Sentry Network monitor
type. Possible values are:
OK
WARN
ALARM
Default: Not set (assumed WARN)
networkLinkDuplexAlarmType
Type of alert for the Duplex Mode attribute of the Hardware Sentry Network monitor
type. Possible values are:
OK
WARN
ALARM
Default: Not set (assumed WARN).
networkLinkDuplexSetting
Indicates when BPPM Hardware needs to trigger an alert on the Duplex Mode
attribute of the Hardware Sentry Network monitor type:
NEVER (will never trigger an alert on Duplex Mode)
DEFAULT (will trigger an alert only when Link Status downgrades from Plugged to
Unplugged)
ALWAYS (will trigger an alert for all interfaces that are unplugged)
Default: Not set (assumed DEFAULT).
Device Additional Configuration Variables
81

Version 1.9.00
Variables
Description
networkLinkSetting
Indicates when BPPM Hardware needs to trigger an alert on the Link Status attribute
of the Hardware Sentry Network monitor type:
NEVER (will never trigger an alert on LinkStatus)
DEFAULT (will trigger an alert only when a full-duplex running adapter
downgrades to half-duplex)
ALWAYS (will trigger an alert for all adapters not operating in full-duplex mode)
networkLinkSpeedAlarmType
Type of the alert for the Link Speed attribute of the Hardware Sentry Network
monitor type. Possible values are:
OK
WARN
ALARM
Default: Not set (assumed WARN).
networkLinkSpeedMinimum
Minimum accepted Link Speed value when networkLinkSpeedSetting is configured to

ALWAYS.
networkLinkSpeedSetting
Indicates when BPPM Hardware needs to trigger an alert on the Link Speed attribute
of the Hardware Sentry Network monitor type:
NEVER (will never trigger an alert on Link Speed)
DEFAULT (will trigger an alert only when Link Speed downgrades from a higher
speed to a slower speed)
ALWAYS (will trigger an alert for all interfaces that are slower than the value
indicated by the networkLinkSpeedMinimum configuration variable)
wmiUsePatrolDefaultAccount
When set to 1, tells BPPM Hardware to use the security token of the PATROL
Agents default account to connect to remote systems with WMI when the
wmiUsername variable is empty.
Default: Not set (assumed 0, where BPPM Hardware does not perform any WMI
query if wmiUsername is empty).
Device Additional Configuration Variables
82

Version 1.9.00
Index
-A Abnormalities
Adapter 22
34, 64
Add 24, 30
Create
24
Update
30
Add Monitor Types
39
additional variables
51
Advanced Configuration Variables
Agent
15
Alert Actions
48
Alert Delay 49
Attributes
63
54
Available Path Count

72
Bandwidth Utilization 73
Battery Status
67
Charge
65
Color 71
Connected Ports
66
Controller Status
67
Corrected Error Count
77
CPU Count
66
Current Speed 77
Degrees Below Warning 66
Device Not Ready Error Count
75
Duplex Mode
73
Error Count
71, 73, 75, 78, 79
Error Percent
73
Error Status
73
Hard Error Count
75
Illegal Request Error Count
75
Intrusion Status
69, 70
Link Speed 73
Link Status
73
Logical Disk Size
66
Media Error Count
75
Memory Size
66
Mount Count
79
Move Count
78
Needs Cleaning 79
No Device Error Count
75
Physical Disk Size
66
Index
power Consumption 66, 70

Power State
66
Predicted Failure
73, 75, 77
Present
65, 66, 67, 69, 70, 72, 73, 75, 77,
78, 79
Received Byte Rate
73
Received Packets Rate
73
Recoverable Error Count
75
Speed 70, 77
Speed Percent
70
Status
65, 66, 67, 69, 70, 71, 72, 73, 75,
77, 78, 79, 80
Technology 75
Temperature
80
Test Report
78
Transmitted Byte Rate
73
Transmitted Packet Rate
73
Transport Error Count
75
Unallocated Disk Space
66
Unallocated Space
71
Unmount Count
79
Usage Count
75
Used Capacity 77
Used Time Percent
67
Value
75
Voltage
80
Zero Buffer Credit Percent
73
Auto Reset
50
Automatic Reporting 59
-BBaselines
BMC ProactiveNet Performance Management
34, 64
Generation 34, 64
Manage
34, 64
Requirements
34, 64
BMC
BMC Software Installation Utility 15
Abnormalities
34, 64
Baselines
34, 64
Key Performance Indicators
KPI 34, 64
BPPM
Data Collection
83
33
34, 64

Version 1.9.00
Discrete parameters
Downloading 20
-C-
-E-
Cisco
12
Cisco UCS Interconnect Chassis
12
Cisco Fabric Interconnect Switch 46
Cisco UCS
39
Cisco UCS Blade Chassis
46
Cisco UCS Manager 46
Component
15
Component Installation package
creating 19
downloading 20
Configuring
Editing a policy 38
Editing a Threshold Configuration
EMC
EMC Clariion 12
EMC SMI-S Provider (ECOM)
EMC Symmetrix 12
EMC Symmetrix V-Max 12
Emulex
discovery interval 52
Local Commands
51
monitor settings
39
Configuring Monitor Thresholds
60
Configuring thresholds
60
Connection to a Device
39
Connector 39
Connector Status Parameters
49
Console Server 15
Creating a policy 37
Features
Files
11
Mshw_ntx86_1300.exe
15
Mshw_unix_1300.tar 15
mshw_unix_1400.tar 15
mshw_WINDOWS_1400.exe
Fujitsu
15
Fujitsu Eternus
12
Fujitsu-Siemens BX Blade Chassis
12
12
Data Collection
BPPM 33
Verify 33
Debug 53
Debug Mode
51
-GGenerate
Baselines
34, 64
Global Advanced Settings
Global Alert Settings
47
Goals
11
61
Dell EquaLogic PS Series

12
Dell Modular Chassis (blades)
12
Dell PowerEdge
12
Device Advanced Settings
39
Device Information 39
Disabling a policy 39
discovery and polling intervals
51
Discovery Interval
Index
12
-F-
-D-
configuring
61
Emulex HBA
12
Enabling a policy 39
Error Count
47, 50
ErrorCount
50
39, 54
enabling 53
Deleting a policy 38
Deleting a Threshold Configuration
Dell
49
12
-HHardware
15
Hardware Sentry
Installation
Hitachi
Hitachi AMS
52
84
15
12
51
12

Version 1.9.00
Hitachi
Hitachi BladeSymphony
Hitachi USP-V
12
12
12
Installing the Monitoring Solution 18

Integrating the Monitoring Solution 22
Integration Service Agent
24
IPMI-Over-LAN 47
HP
HP 9000 12
HP AlphaServer 12
HP c-Class BladeSystem 12
HP CommandView EVA
12
HP CommandView XP (or Hitachi Device
Manager)
12
12
HP Integrity 12
HP NetServer 12
HP p-Class BladeSystem 12
HP ProLiant
12
HP StorageWorks EVA
12
HP StorageWorks XP 12
12
HP SuperDome (PA-RISC)
12
-IIBM 3584 Tape Library 12

IBM BladeCenter 12
IBM Director Agent
12
IBM DS 3000, 4000, 5000 Series
12
IBM DS 6000, 8000 Series
12
IBM DS Storage Manager (SMcli)
12
IBM pSeries, IBM eServer p5, p6 12
IBM Storwize V7000 12
IBM Storwize V7000 CIM Agent
12
IBM SVC
12
IBM SVC CIM Agent
12
IBM VIO Server 12
IBM XiV
12
IBM XIV Storage System SMI-S Agent
12
IBM XIV Storage System SMI-S AgentIBM
Storwize V7000 CIM Agent
12
IBM xSeries, IBM Netfinity 12
Importing the Monitoring Solution 18
Install / Un-install
Hardware Sentry
Packages
15
Installation
Index

34, 64
Manage
34, 64
KPI
34, 64
Manage
34, 64
-LLocal Commands
configuring
Localhost Sudo
51
51
51
-M-
IBM
configuring
Installing 20
-K-
Manage
Baselines
34, 64
KPI 34, 64
Managing Policies
37
McData SAN Switch 12
Monitor Settings
34, 64
configuring 39
Monitor thresholds
60
Monitor Type
24
Monitor Types
63
Hardware Battery 65
Hardware Blade
66
66
Hardware CPU Core
67
Hardware Disk Controller 67
69, 70
Hardware Fan 70
Hardware LED 71
Hardware Logical Disk 71
Hardware LUN 72
73
73
75
15
37
85

Version 1.9.00
Monitor Types
63
Hardware Physical Disk 75

Hardware Power Supply 77
Hardware Processor 77
Hardware Robotics
78
Hardware Sentry Connector 78
Hardware Tape Drive
79
80
Hardware Voltage
80
Multi-Tier 45
Multi-Tier Authentication 45
Product
protocol
11
IPMI-Over-LAN 39
SNMP 39
SSH/Telnet
39
WBEM 39
WMI 39
PW Commands
31
-QQLogic
-N-
QLogic HBA
12
Quantum Tape Library
12
NEC
NEC Express5800 12
NetApp 12
number of consecutive times
Numeric parameters
49
-R47
Reference Guide
Reports
scheduling
Requirements
Root Privileges
-OOpenSSH 43
Operating Systems
Scheduling
Reports
59
SNMP 42
SNMP Community String 42
SNMP port
42
specific action 47
Specific PATROL Event
48
SSH 43
SSH/Telnet
43
Status attribute
49
STD 41 PATROL Event
48
StorageTek
-P19, 20
PATROL component
15
PATROL Configuration Manager
Platforms
Supported 12
Policies
37
Policy 37, 38, 39
Present Parameters
49
ProactiveNet
22, 24
Index
59
12
43, 51
-S-
HP-UX
12
Linux 12, 15
OpenVMS
12
Solaris
12
Tru64
12
UNIX
15
VMware ESX4
12
Windows
12, 15
out-of-band interface
47
Overview
11
Package
PATROL
63
37
StorageTek LSeries
12
StorageTek StreamLine (SL)
Sudo
51
Sudo Command 43
Sudo Command Line
51
Sun
12
Sun Advanced Lights-Out Management

(ALOM)
12
Sun Blade Modular Chassis
12
Sun Fire (SPARC T1, T2) 2009 and newer
firmware
12
86

Version 1.9.00
Sun
Sun Fire (SPARC T1, T2) pre-2009
firmware
12
Sun Fire (SPARC)
12
Sun Fire (X64)
12
Sun Fire F12K, F15K, F20K, F25K 12
Sun Fire Mx000 12
-TTags
37
Technology
Command lines
HTTP 12
IPMI 12
SNMP 12
SSH 12
Telnet
12
WBEM 12
WMI 12
XML API 12
Telnet
43
Thorium 15
Thresholds
60
12
Customize
31
Import
31
-UUnknown Status
47, 49
-V Variables
Verify
54
Data Collection
VMware
VMware ESX4
VMware ESXi
33
12
12
-W WBEM 45
Web 15
Windows Management Instrumentation
WMI 46
Index
46
87
About BMC Software

BMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management
solutions that empower companies to manage their IT infrastructure from a
business perspective. Delivering Business Service Management, BMC Software
solutions span enterprise systems, applications, databases, and service
management. Founded in 1980, BMC Software has offices worldwide and fiscal
2004 revenues of more than $1.4 billion. For more information about BMC
Software, visit www.bmc.com.
About Sentry Software

Sentry Software, a strategic Technology Alliance Partner of BMC Software,
provides comprehensive multi-platform monitoring solutions that enable
management of the hardware and software aspects of all servers and SANs and
covering up to 100 % of custom applications within the BMC ProactiveNet
Performance Management environment. Sentry Software also develops adapters
for BMC Atrium Orchestrator that enables IT administrators to automate the
execution of common requests and tasks that occur in the daily course of IT
operations. Combined with BMCs servers and network automation tools, the
adapters allow IT administrators to implement provisioning and

BBPM Perfmon MGMT

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BBPM Perfmon MGMT

Hochgeladen von

Copyright:

Verfügbare Formate

BMC ProactiveNet Performance

BMC ProactiveNet Performance Management - Hardware

Contacting BMC Software

United States and Canada

BMC Software, Inc.

1 (713) 918 8800 or

Restricted Rights Legend

BMC ProactiveNet Performance Management - Hardware

Support Web Site

Support by Telephone or E-mail

Before Contacting BMC Software

BMC ProactiveNet Performance Management - Hardware

BMC ProactiveNet Performance Management - Hardware

BMC ProactiveNet Performance Management - Hardware

BMC ProactiveNet Performance Management - Hardware

Copyright 2011 BMC Software, Inc.

BMC ProactiveNet Performance Management - Hardware

The pages in this section provide a high-level overview of the product.

User Goals and Features

BMC ProactiveNet Performance Management - Hardware

Cisco UCS B-Series, C-Series

Cisco UCS B-Series, C-Series

IPMI, command lines

Dell OpenManage Server

Dell OpenManage Server

Fujitsu Serverview WBEM agent

Fujitsu-Siemens Serveview WBEM

Fujitsu-Siemens Serveview WBEM

HP-UX Support Tools Manager (STM)

Command lines, Telnet/

HP Insight Management Agent

HP Insight Management Agent

HP Insight Management Agent

HP Insight Management Agent

BMC ProactiveNet Performance Management - Hardware

HP-UX Support Tools Manager (STM)

Command lines, Telnet/

HP Insight Management Agent

HP Insight Management Agent

HP Insight Management Agent

HP Insight Management Agent

HP Insight Management Agent

Command lines, Telnet/

Command lines, Telnet/

IBM pSeries, IBM eServer

IBM v7000 Disk Arrays

IBM VIO Server

IBM xSeries, IBM Netfinity

IBM Director Agent

IBM xSeries, IBM Netfinity

IBM Director Agent

WBEM, command lines

NEC ESMPRO Agent

NEC ESMPRO Agent

Sun Fire (SPARC T1, T2)

Sun Fire (SPARC T1, T2)

Access to the Sun Advanced LightsOut Management (ALOM) card over

Command lines, SSH to

Sun Fire (SPARC)

Sun Fire (X64)

Sun Fire (X64)

Sun Fire (X64)

IPMI (WMI), command