Bbpm Perfmon Mgmt

8/9/2019 Bbpm Perfmon Mgmt

1/88

User Documentation January 2014

BMC ProactiveNet Performance

Management - HardwareVersion 1.9.00


2/88

Contacting BMC SoftwareYou can access the BMC Software Web site at http://www.bmc.com. From this Web site, you can obtaininformation 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 77042-

2827

Telephone 1 (713) 918 8800 or1 (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 areregistered 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 thisdocumentation.

Restricted Rights Legend

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

2

Version 1.9.00

BMC ProactiveNet Performance Management - Hardware


3/88

You can obtain technical support by using the Support page on the BMC Software Web site or bycontacting 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-mailaddresses, 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, call800 537 1813. Outside the United States and Canada, please contact your local support center forassistance. To find telephone and email contact information for the BMC Software support center thatservices 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 canbegin 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, andservice 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"

3

Version 1.9.00

http://www.bmc.com/support_homehttp://www.bmc.com/support_homehttp://www.bmc.com/support_home


4/88

Table of Contents 4

Version 1.9.00


Table of Contents...........................................................................................................................11User Goals and Features

...........................................................................................................................11Product at a Glance

...........................................................................................................................12Supported Platforms

...........................................................................................................................15Solution Packages

...........................................................................................................................18Importing the Monitoring Solution into Central Administration

...........................................................................................................................19Creating the Installation Package

...........................................................................................................................20Downloading the Installation Package

...........................................................................................................................20Installing the Package

...........................................................................................................................24Creating and Importing an Adapter for a BMC PATROL KM

...........................................................................................................................30Updating an Adapter for a BMC PATROL KM

...........................................................................................................................31Importing and Customizing Thresholds

...........................................................................................................................33Verifying the Data Collection

...........................................................................................................................34Managing Baselines and Key Performance Indicators

...........................................................................................................................37Adding Tags to PATROL Agents

...........................................................................................................................37Managing Policies

...........................................................................................................................37Creating a policy

...........................................................................................................................38Editing an existing policy

...........................................................................................................................38Deleting a policy

...........................................................................................................................39Enabling/disabling a policy

...........................................................................................................................39Configuring Monitor Settings

...........................................................................................................................39Creating a Connection to a Device

..................................................................................................................42Using the SNMP Protocol

..................................................................................................................43Using the SSH/Telnet Protocol

..................................................................................................................45Using the WBEM Protocol

..................................................................................................................46Using the WMI Protocol

..................................................................................................................46Using the Cisco UCS Manager

..................................................................................................................47Using the IPMI-Over-LAN Protocol

...........................................................................................................................47Configuring Global Alert Settings

..................................................................................................................48Configuring Alert Actions

..................................................................................................................49Configuring Alert Delay

..................................................................................................................49Configuring the Unknown Status

..................................................................................................................50Automatically Resetting Error Count Parameters


5/88

Table of Contents 5

Version 1.9.00


...........................................................................................................................51Configuring Global Advanced Settings

..................................................................................................................51Configuring Local Commands

..................................................................................................................52Configuring Intervals

..................................................................................................................53Enabling the Debug Mode

..................................................................................................................54Setting Additional Configuration Variables

...........................................................................................................................59Scheduling Automatic Reports

...........................................................................................................................60Configuring Thresholds

...........................................................................................................................60Configuring Monitor Thresholds

...........................................................................................................................61Editing a Threshold Configuration

...........................................................................................................................61Deleting a Threshold Configuration

...........................................................................................................................63Monitor Types and Attributes...........................................................................................................................64Managing Baselines and Key Performance Indicators

...........................................................................................................................65Hardware Battery

...........................................................................................................................66Hardware Blade

...........................................................................................................................66Hardware Capacity Report

...........................................................................................................................67Hardware CPU Core

...........................................................................................................................67Hardware Disk Controller

...........................................................................................................................69Hardware Disk Enclosure

...........................................................................................................................7 0Hardware Enclosure

...........................................................................................................................7 0Hardware Fan

...........................................................................................................................7 1Hardware LED

...........................................................................................................................7 1Hardware Logical Disk

...........................................................................................................................7 2Hardware LUN

...........................................................................................................................7 3Hardware Memory Module

...........................................................................................................................7 3Hardware Network Interface

...........................................................................................................................7 5Hardware Other Device

...........................................................................................................................7 5Hardware Physical Disk

...........................................................................................................................7 7Hardware Power Supply

...........................................................................................................................7 7Hardware Processor

...........................................................................................................................7 8Hardware Robotics

...........................................................................................................................7 8Hardware Sentry Connector

...........................................................................................................................7 9Hardware Tape Drive

...........................................................................................................................80Hardware Temperature

...........................................................................................................................80Hardware Voltage

...........................................................................................................................81Device Additional Configuration Variables


6/88

Support Information


7/88

7

Version 1.9.00


This section contains information about how to contact Customer Support and the levels of supportoffered for this and other releases.

If you have problems with or questions about a BMC product, or for the latest support policies, see theCustomer Support website at http://www.bmc.com/support. You can also access product documentsand search the Knowledge Base for help with an issue at http://www.sentrySoftware.com. If you do nothave access to the web and you are in the United States or Canada, contact Customer Support at 800537 1813. Outside the United States or Canada, contact your local BMC office or agent.
http://www.sentrysoftware.com/http://www.bmc.com/support


8/88

Legal Notices


9/88

9

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., areregistered with the U.S. Patent and Trademark Office, and may be registered or pending registration inother countries. All other BMC trademarks, service marks, and logos may be registered or pendingregistration in the U.S. or in other countries. All other trademarks or registered trademarks are theproperty 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 betrademarks 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 andconditions of the applicable End User License agreement for the product and to the proprietary andrestricted rights notices included in the product documentation.

BMC Software Inc.2101 CityWe st Blvd, Houston TX 77042-282 7, USA713 918 8800Custom er Support: 800 537 1813 (United State s and Canada) or conta ct your local support center


10/88

Overview


11/88

11

Version 1.9.00


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

User Goals and FeaturesProduct at a Glance

Supported Platforms

Note that for conve nience and brev ity, reference to BMC Proact iveNet Pe rformance Management - Hardware, mayalso be made as BPPM Hardware.

User Goals and Features

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 informationthrough a centralized console so you can easily view and manage your entire IT infrastructure. Theproduct collects and brings critical performance data and useful metrics into the BMC ProactiveNetPerformance Management environment and enables administrators to be warned whenever Hardwareproblem 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.


12/88

12Supported Platforms

Version 1.9.00


Supported Platforms

BMC ProactiveNet Performance Management - Hardware requires specific instrumentation agents orsystem management tools to be present on the managed system to collect hardware information.

Servers

Typical Platform Operat ing System Instrumentat ionPrerequisites

Technology Used

Cisco UCS B-Series, C-Series Windows None IPMI, WMI

Cisco UCS B-Series, C-Series Linux ipmitool IPMI, command lines

Dell PowerEdge Windows Dell OpenManage ServerAdministrator

SNMP

Dell PowerEdge Linux Dell OpenManage ServerAdministrator

SNMP

Fujitsu PRIMEPOWERServers (sun4us) -

Solaris None Command lines

Fujitsu-Siemens PRIMERGY VMware Fujitsu Serverview WBEM agent WBEM

Fujitsu-Siemens PRIMERGY Windows Fujitsu-Siemens ServerviewFujitsu-Siemens ServerView RAID

Agent / Promise FastTrack SNMP

Agent / LSI GAM Server / LSIMegaRAID SAS SNMP Agent / LSIMegaRAID PowerConsole / MylexGAM Server (depending on theserver, follow Fujitsu-Siemensrecommendations)

SNMP

Fujitsu-Siemens PRIMERGY Linux Fujitsu-Siemens ServerviewFujitsu-Siemens ServerView RAID

Agent / Promise FastTrack SNMPAgent / LSI GAM Server / LSIMegaRAID SAS SNMP Agent / LSIMegaRAID PowerConsole / MylexGAM Server (depending on theserver, follow Fujitsu-Siemensrecommendations)

SNMP

Fujitsu-Siemens PRIMERGY Linux Fujitsu-Siemens Serveview WBEMAgent

WBEM

Fujitsu-Siemens PRIMERGY Windows Fujitsu-Siemens Serveview WBEMAgent

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 HP Insight Management Agent SNMP

HP Integrity Windows HP Insight Management Agent SNMP

HP Integrity Linux HP Insight Management Agent SNMP


13/88


Version 1.9.00


Typical Platform Operat ing System Instrumentat ionPrerequisites

Technology Used

HP Integrity HP-UX HP-UX Support Tools Manager (STM)or HP-UX WBEM Provider

Command lines, Telnet/SSH, or WBEM

HP NetServer Windows HP TopTools SNMP, WMI

HP ProLiant Windows HP Insight Management Agent SNMP or WMI

HP ProLiant Linux HP Insight Management Agent SNMP

HP ProLiant Solaris HP Insight Management Agent SNMP

HP SuperDome (Itanium) Windows HP Insight Management Agent SNMP

HP SuperDome (Itanium) Linux HP Insight Management Agent SNMP

HP SuperDome (Itanium) HP-UX MP/GSP card Command lines, Telnet/SSH

HP SuperDome (PA-RISC) HP-UX GSP card Command lines, Telnet/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 Lights-Out Management (ALOM) card overthe network

Command lines, SSH tothe 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), commandlines

Sun Fire F12K, F15K, F20K,F25K

Solaris Access to the SMS utilities installedon the System Controller (SC)

SSH to the SystemController

Sun Fire Mx000 Solaris Access to the eXtended SystemControl Facility (XSCF)

SSH to the XSCF

Cross-Platform Technology

Technology OperatingSystem

Instrumentation Prerequisites Technology Used

Emulex HBA Windows None WMI

Emulex HBA Linux hbacmd Command lines

Emulex HBA Solaris hbacmd Command lines


14/88


Version 1.9.00


Technology OperatingSystem

Instrumentation Prerequisites 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 Instrumentation Prerequisites Technology Used

Cisco UCS Interconnect Chassis Cisco UCS Manager on the Cisco UCS InterconnectSwitch

XML API (HTTP)

Dell Modular Chassis (blades) DRAC/MC Telnet/SSH

Fujitsu-Siemens BX BladeChassis

Fujitsu-Siemens Management Blade SNMP

HP c-Class BladeSystem HP BladeSystem On-Board Administrator SNMP

HP p-Class BladeSystem HP Insight Management Agent 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

Storage Devices

Typical Platform Instrumentation Prerequisites 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 tapelibraries

Dell OpenManage Server Administrator SNMP

Dell PowerVault TL4000 tapelibraries

Dell OpenManage Server Administrator 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


15/88


Version 1.9.00


Typical Platform Instrumentation Prerequisites Technology Used

Fujitsu Eternus ETERNUS SMI-S Agent WBEM

Hitachi AMS/HUS Hitachi Device Manager WBEM

Hitachi USP-V Hitachi Device Manager WBEM

Hitachi VSP Hitachi Device Manager WBEM

HP StorageWorks P6000 HP CommandView EVA Command lines

HP StorageWorks XP HP CommandView XP (or Hitachi Dev ice Manager) WBEM

HP StorageWorks P9000 Series HP CommandView WBEM

IBM DS 3000, 4000, 5000Series

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

1 C isco network switches are not supported by BMC Proact iveNet Performance Management - Hardware.

Generally server manufacturers furnish instrumentation agents and system tools for free and theseare e ither found on the CD-ROM provided with the server or, on the manufacturers web site. Unlessmentioned otherwise, the manufacturers instrumentation agent must be installed on themonitored server for BPPM Hardware to function properly. For details on how to install the requiredinstrumentation agent on the systems, please refer to the platform-specific guides available on theHardware Sentry pageof 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_.zip

For UNIX and Linux systems: mshw_ALL_.tar

For OpenVMS systems: mshw_VMS_.tar
http://www.sentrysoftware.net/link.asp?topic=58http://www.sentrysoftware.net/Support/user_documentation.asp


16/88

16Solution Packages

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 operateproperly (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 InstallationUtility, is made available to download on the Sentry Software Web site.

A pa che JRE is no t supp ort e d.
http://www.sentrysoftware.net/link.asp?topic=58


17/88

Installing the Monitoring Solution


18/88

18

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 differentoperating 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 toBMC ProactiveNet Central Monitoring Administration from the server where they want to install thepackage, download it and launch the installation.

This section describes the different steps to follow to install BPPM Hardware:Importing BPPM Hardware into Central AdministrationCreating the Installation PackageDownloading the Installation PackageInstalling the Package

Importing the Monitoring Solutioninto Central AdministrationThe BMC ProactiveNet Central Monitoring Repository includes the current versions of the BMC PATROLAgent and BMC PATROL Monitoring Solutions that you can use with BMC ProactiveNet. If the versionavailable 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 Repositorydrawer and select Manage Repository.

3. Check that the version of the BMC component available is actually the latest one. If not, downloadthe latest version corresponding to your operating system (Windows or UNIX/Linux) available onthe Sentry Software Websiteand save it on the local computer from which you are running theCentral Monitoring Administration web-based console.

4. From the BMC ProactiveNet Central Monitoring Administration, click Import .

5. Select Single solution.

6. Browse to the .zip source file.

7. Click Import.

The selected archive file is imported to the repository.
http://www.sentrysoftware.net/Products/index.asp


19/88

19Importing the Monitoring Solution into CentralAdministration

Version 1.9.00


Creating the Installation Package

The installation package to deploy to managed systems can be created directly from BMC ProactiveNetCentral Monitoring Administration:

1. Log on to BMC ProactiveNet Central Monitoring Administration

2. Click the Repositorydrawer and select Monitoring Repository.

3. ClickAdd .

4. Select the operating system and platform for which you want to create a package. The componentsavailable in the repository for the selected operating system and platform are displayed.

5. Select the Installation Package Component:

From theAvailablecomponents list, select Hardware.From theVersionlist, select the latest version.

Click the right arrow button to move the component into the Selected Componentslist

By default, the appropriate BMC PA TROL Agent for the operat ing system and platform that you chose is

included in the Selected components list.

Click Next. TheAdd Component Installation Packagewizard is displayed.

6. Go through the wizard and specify the required PATROL information. The Installation PackageDetailsis displayed:

7. Verify that:

the operating system and platform are correct

the components that you want to include are listed in the Included Componentslist.8. 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 theMonitoring Installation Packages list on the Monitoring Repository window.

Format: Select a file compression format for the package.

9. Click Save Installation Package.

10. Click Close. The package is now available in the Monitoring Installation Packageslist.


20/88

20Creating the Installation Package

Version 1.9.00


Downloading the Installation

PackageYou can download an installation package and install the components on one or more hosts. Theinstallation runs silently with the information entered during package creation.

Recommendation

If you defined the BMC ProactiveNet Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployed agents allat once. Start and configure monitoring for the agents in planned phases to reduce the performanceimpact on the Integration Service nodes and on the BMC ProactiveNet Server associated with theautomatic workflow process.

1. Log on to BMC ProactiveNet Central Monitoring Administration from the computer on whichthe PATROL Agent is installed.

2. Click the Repositorydrawer and select Monitoring Repository.

3. (Optional) To filter the list of installation packages, select an operating system from the Filter byOperating Systemlist.

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.

Installing the Package1. 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 extractedto thebmc_productsdirectory 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 agentsends 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 theagent. 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 configurationinformation. The agent does not begin monitoring until a matching policy is created.


21/88

Integrating the Monitoring Solution


22/88

22

Version 1.9.00


To integrate a BMC PATROL KM intoBMC ProactiveNet Performance Management 8.5or8.6, youneed to install the KM on top of a PATROL Agent, then add a connection to the system to be monitoredand finally create a specific adapter.

An adapter for BMC PATROL is a software component designed to facilitate the integration of metricscollected by a BMC PATROL KM into BMC ProactiveNet. The adapter allows you to import applicationclasses from a BMC PATROL KM into BMC ProactiveNet and displays the performance metrics into yourBMC ProactiveNet Performance Management environment. It also ensures a periodical synchronizationwith the KM in order to provide updated and accurate data.

A dapter fo r BM C P A TROL A rc hite 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, registeritself, 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 theSAdapter (Staging Adapter) to accept inbound connections from the PATROL Agents. The SAdapter isa 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.


23/88

23

Version 1.9.00


A utom a ted W ork flo w - The PA TROL A ge nt conne cts to the In te gra tio n Serv ice

The manual method:This method relies on the p3Adapter profile. Each p3adapter is responsible for querying a set ofPATROL Agents in a single security domain and retrieves data. This method is not documented in thisguide.

Manua l Met hod - Integration Service connects to PATROL Agent

You can also use the following methods to send events directly to the BPPM cell but you would lose thebenefit 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 re fer to the knowledge article:Integrat ing the Events Generated by the KMs into BMC Ev ent Manager.
http://www.sentrysoftware.com/kb/KB1104.asp


24/88

24Creating and Importing a BPPM Adapter for aBMC PATROL KM

Version 1.9.00


Creating and Importing a BPPM

Adapter for a BMC PATROL KMCreating 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::3183.

the /AgentSetup/prealoadedKMs variable contains MS_HARDWARE_SENTRY1.km

2. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Consoleis displayed as shown in the following figure:

A cce ssing the A dm inis tra tio n ta b in the A dm inis trat io n Co nsole

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:


25/88


Version 1.9.00


Setting the connection param eters

In the Instance Namefield, enter a name for this instance of the Adapter that will perform theintegration of the targeted KM into BMC ProactiveNet (e.g. Adapter for Hardware).

From the Source Agentlist, select the BPPM remote agent to which your PATROL agents aresending data to

Enter the Integration Service Agent hostnameorIP address

Enter the Integration Service Agent Port. The default port is 3182.

Enter the required credentials to connect to the Integration Service Agent


26/88


Version 1.9.00


5. Click Nextto continue. If you have correctly set the integrationServicesvariable as explainedabove, your PATROL Agents will be listed:

Reviewing the Integration Service configuration

6. Click Next.


27/88


Version 1.9.00


Selecting A pplication Classe s t o impo rt

7. Select the application classes to import.

Unselecting will delete the application classes that have already been imported during a previousoperation. Application classes ready to be deleted are marked with a red x.

8. Click Nextto start the import process. The system displays a summary of the application classimport, click Nextto continue.

9. Select the application classes you wish to auto-synchronize with the Integration Service Agent.


28/88


Version 1.9.00


Selecting A pplication Classe s for Auto-sy nc

10. Click Nextto continue

11. If needed, set the Filterdetails.


29/88


Version 1.9.00


Sett ing filter det ails

12. Click Nextto continue.

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


30/88


Version 1.9.00


Scheduling Auto-sync polls

14. Click Finish. The system displays a summary of your settings, click Finishto confirm. The Adapterhas 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 theAdapterand select Details.

We strongly recommend that you create a specific adapter for each KM you need to integrate intoBMC ProactiveNet to enable the update of a single KM independently.

Updating an Adapter for a BMCPATROL KM1. Delete the Adapter instance.

2. Go through theAdd an Adapterwizard to actually delete the monitor types that had been createdbased on the previous version of the KM.

3. Close.

4. Resume the entire Creating an Adapter for a BMC PATROL KMprocedure.


31/88

31Updating an Adapter for a BMC PATROL KM

Version 1.9.00


For complete a nd detailed information on these procedure s, please ref er to the BMC Proa ctiveNet documentation

ava ilable from BMC Web site.

Importing and CustomizingThresholds1. Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW

Commandsas Administrator.

Launching BMC ProactiveNet PW Com ma nds

2. Execute the following command line:pw adapter -type patrol -get_thresholds -pproxy_host

[-pproxy_port ] [-pproxy_user ] [-pproxy_passwd ] -i -v

where

-get_thresholds = File name with absolute path at which thresholds will be imported

-pproxy_host = Host name or IP Address of Patrol Proxy Server

-pproxy_port = Port at which Patrol Proxy Agent communicates with Patrol

Proxy Server

-pproxy_user = User name of Patrol Proxy user

-pproxy_passwd = Password to authenticate Patrol Proxy user-i = import Instance level thresholds


32/88

32Importing and Customizing Thresholds

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 properlyconverted by the PATROL Adapter.

The import proced ure fails to interpret p roperly the Voltage a lert thresholds. If you wa nt to activate alert thresholds

in BMC ProactiveNe t for Voltage pa rameters, you w ill need to manually de scribe them in the te xt f ile, a s in theexample below.

6. Save the fi le.

7. Execute the following command:pw threshold loadpatrolthreshold [ [-v]]

where:

is a thresholds file name. If no file path is specified then the default

'/pw/tmp/' is used

-v enables the Verbose mode

8. Check the result in the BMC ProactiveNet Operations Console. Class-level thresholdscan bedisplayed using theAbsolute Global Thresholdspanel in the BMC ProactiveNet Operator Console,while instance-level thresholdsare displayed in theAbsolute Instance Thresholdspanel:


33/88

33Importing and Customizing Thresholds

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

Or through the Operations console.

Method 1: Running a Command1. On the BPPM Remote Agent machine where the Integration Service is running, launch the commandprompt

2. Go to BPPMAgent\Agent\pproxy\PNS\bin

3. Run the following command:pproxcli >c:\pprox.txt

/connect -host -port -username -password

Example: /connect -host carnap -port 3182 -username admin -password ******

4. Run the following command:/PATROL/query/getInstanceData -agent :

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: -appl -inst -param

Get instance data for given agent. Application name,instance name and parameter name are optional

Method 2: Through the BMC ProactiveNet OperationsConsole

1. In the Mainnavigation pane, click Devices.


34/88

34Verifying the Data Collection

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 Export to Excelto get the list of all the data collection points between a selected timeframe.

Managing Baselines and KeyPerformance IndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNetcalculates baselines per parameter (metrics or attributes) based on values collected over a specifiedperiod of time to determine a normal operating range. When the collected values for these parametersare out of range, an alert is triggered.

Some parameters are identified by default as Key Performance Indicators and therefore automaticallyincluded 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 specifiedtime period and establishing a low baseline value (consisting of the 10th percentile of all the values for agiven time period) and a high baseline value (consisting of the 90th percentile of all the values for agiven time period), taking a weighted average of these values over time. A higher weight is given to thelatest 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 thresholdexists and is not suppressed.

Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have anactive abnormality threshold and are also KPI attributes will have baselines generated for them.

Abs olu te th re sh old s (wit h "ou ts ide ba se line ") o r s ign a tu re th re sh old s d o n ot sa tis fy th ese re qu ire ment s.

Managing Key Performance Indicators

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


35/88

35Managing Baselines and Key PerformanceIndicators

Version 1.9.00


However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet AdministrationConsole.

To add or remove Key Performance Indicator (KPI) attributes for amonitor type

1. In theAdministration Console, from the menu bar, choose Tools > KPI Administration. TheKPI Administrationdialog box is displayed.

2. From the Monitor Typelist, choose the monitor type for which you want to add or remove KPIattributes. 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 det ailed information on this procedure , please re fer to the BMC Proa ctiveNet documenta tion availablefrom BMC Web site.

Parameters for which the system by default calculates baselines as well as parameters considered asKPIs are respectively identified by the following icons:

Baselining

KPI


36/88

Configuring After Installation


37/88

37

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

Adding Tags to PATROL Agents

Tags must be set for all your PATROL Agents before creating a policy. If you have not already set yourtags during the installation, you can still manually add them by using wpconfigor PATROLConfiguration Manager.

The variable to add tags to PATROL Agents is:

/AgentSetup/Identification/Tags/TAG/tagName

where tagNamemust 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 alsospecify threshold creation and the setting of baselines. A policy can also include intelligent server-sidethresholds 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 policyEnabling/disabling a policy

Creating a policyA 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 Navigationpane, click the Policiesdrawer and select a policy view (e.g.All).

3. ClickAdd to open theAdd Policydialog box.

4. Enter a unique policy Name. In an environment with tenants, policy names must be unique for asingle tenant.


38/88

38Managing Policies

Version 1.9.00


5. (For environments with tenants) Select a Tenantname.

6. Use the up and down arrows to indicate the Precedencenumber from 0 to 999.

7. (Optional) Enter a policy Description.

8. Enter a Central Monitoring Administration Tag.

Tags are case sensitive and cannot contain spaces or any of the following characters: /, \, {, }, ,, , &.

9. Click the:

Monitor Configurationtab to configure monitor types

Threshold Configurationtab 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 policiesconfigure 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 valuedetermines the order the policies are applied. The policy with the lower number value forprecedence is the policy from which the final configuration is applied.

Policies with different tags: If conflicting policies have different tags, then the policies areapplied according to the order they are listed on the BMC PATROL Agent. The policy listed last onthe agent is the policy from which the final configuration is applied.

Editing an existing policyAn existing policy can be edited as follows:

1. In the Navigationpane of Central Monitoring Administration, click the Policiesdrawer and select apolicy view (e.g.All).

2. Select a policy and click Edit .

3. Click the:

Generaltab to edit the policy general settings.

Monitor configurationtab to edit the monitor settings.

Threshold settingstab 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:



39/88

39Managing Policies

Version 1.9.00


2. Select one or more policies and click Delete .

3. ClickYesto confirm deletion.

Enabling/disabling a policyFor maintenance and troubleshooting it can be useful to enable or disable policies. When a policy isdisabled, the policy and its associations remain intact, but the policy configuration is not applied until thepolicy 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. TheAdd Monitor Types

dialog box presents configuration fields for compatible BMC PATROL monitoring solutions that arelocated in the Central Monitoring Repository.

To configure the Monitor Type settings1. Log on to Central Monitoring Administration.

2. In the Navigationpane, click the Policiesdrawer and select a policy view (e.g.All).

3. Create a new policy or edit an existing one. Click the Monitor Configurationtab.

4. ClickAdd .

5. From the Solutionmenu, select Hardware.

6. From theVersionmenu, select the required version.

7. From the Monitor Typemenu, select the Monitor Typefor which you want to add a policy, thatis Hardware.

Creating a Connection to a DeviceYou can configure BPPM Hardware to monitor devices remotely. To remotely monitor devices, you needto create a connection to this specific device.

To create a connection to a device:

1. Create a new policy or edit an existing one


40/88


41/88

41Configuring Monitor Settings

Version 1.9.00


2. In the Device Informationsection:

Indicate the name of the device that you wish to monitor.

Enter theIP addressof the device. If no IP address is provided, the device name previouslyspecified 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 Settingssection, click Connectorsto choose the mode to be

used:Select an option from the Connector Selectionlist:

Automatic(Recommended): to let the solution select the most relevant connectors.

Exclude Specified Connectors: to list the connectors that will not be used by thesolution.

Use Specified Connectors:to list the connectors to be used by the solution. This optionshould only be selected and set if instructed by Sentry Support.

If you selected the Exclude Specified Connectorsor Use Specified Connectorsoption, enterthe name of the connectors that will be used or not by the solution. Connector names must beseparated by a comma (,).

Click Closeto validate.

5. (Optional) In the Device Advanced Settingssection, clickAdv. Variablesto configure the device

additional configuration variableswhich will be applied to a single supervised host or device:

Enter the NameandValueof the configuration variable you need to configure. Multiple valuesmust be separated by a semi-colon (;).

ClickAdd to List

You can easily modify or remove a variable by selecting it in the list and clicking either theModify Selectionor the Remove from Listbuttons.

Click Closeto validate.

6. When all the required information is filled, click theAdd to List buttonto validate and add the

defined device to the list below.

7. In theAdd Monitor Typesdialog box, clickAdd.

You can then s elect an ex isting dev ice and click Modify Selection to edit the sett ings of the selected dev ice or alsoRemov e from L ist to delete the selected de vice.


42/88


Version 1.9.00


Using the SNMP Protocol

You can use the SNMP protocol to monitor the hardware of servers and storage devices which areinstrumented through SNMP.

To monitor a server using the SNMP protocol:

1. First, create a connection to the deviceto be monitored.

2. Click SNMP.

SNMP Cred entials

3. Enter the SNMP Community Stringto use to perform SNMP v1 queries.

4. Use the spin button to indicate the SNMP portnumber you wish to use to perform SNMP queries.

By default the SNMP queries are performed through port 161.5. Click Closeto validate your creation.

6. In the Hardware Configurationsection, click theAdd to Listbutton to validate yourconfiguration.

7. In theAdd Monitor Types dialog box, clickAdd.


43/88


Version 1.9.00


Using the SSH/Telnet Protocol

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


44/88


Version 1.9.00


To monitor a server using the SSH/Telnet protocol:

1. First, create a connection to the deviceto be monitored.2. Click SSH/Telnet.

SSH/Telnet Credentials

3. In the SSH/Telnetsection:

Select theAuthentication Modeto use to establish a connection with the remote device.

Enter theUsernameto use to establish the connection with the remote device.

Enter the Passwordto use to establish the connection with the remote device. A Passphrasemay be required to establish a connection through SSH with Authentication Key.

Enter the OpenSSH Private Key Filerequired for establishing connection through SSH withAuthentication Key. The key file must be accessible by the PATROL Agent that will make theconnection to the remote host through the SSH/Telnet protocol.

4. In theSudo Optionssection:Check the Use When root Privileges are Needed option to use the "sudo" utility in order toexecute external commands as "root" on UNIX/Linux platforms.

Enter theSudo Command Lineto execute.5. Click Close to validate your creation.




45/88


Version 1.9.00


Using the WBEM Protocol

You can use the WBEM (Web-Based Enterprise Management) protocol to communicate directly with aSMI-S Provider/storage system and collect information.

To monitor a server using the WBEM protocol:


2. Click WBEM.

WBEM Credentials

3. Enter the Username, Password and Port Numberto use to establish the connection with theremote device using the WBEM protocol.

4. Specify the port number. By default port 5989 is used for encrypted connections and 5988 for non-encrypted connections.

5. Check the Encryptionoption if the port used is 5989.

6. In theAdvanced Options section:

Enter the IP address/device name of the Multi-Tier Authentication Server. This option ismostly used for VMware servers. If left blank, the solution will automatically use the WBEMcredentials.

Enter the WBEM Namespace. Leave blank to let the solution detect the proper name(recommended).

5. Click Closeto validate your creation.




46/88


Version 1.9.00


Using the WMI Protocol

You can use the WMI (Windows Management Instrumentation) protocol to remotely monitor systems ordevices:


2. Click WMI.

WMI Credentials

3. Enter the Usernameand Passwordto use to establish the connection with the remote deviceusing the WMI protocol.


5. In the Hardware Configurationsection, click theAdd to Listbutton to validate your

configuration.6. In theAdd Monitor Types dialog box, clickAdd.

Using the Cisco UCS ManagerTo collect information about Cisco UCS Blade Chassis and Cisco Fabric Interconnect Switch:


2. Click Cisco UCS.

Cisco UCS Credentials


47/88


Version 1.9.00


3. Enter the Usernameand Passwordto use to establish the connection with the Cisco UnifiedComputing System.

4. Uncheck the Encryptionoption to disable the SSL Encryption for UCS login (HTTPS). By default,

the encryption is always enabled.




Using the IPMI-Over-LAN ProtocolIPMI-Over-LAN is the out-of-band interface used by BPPM Hardware to bypass the usual hardwareagents and communicate directly with the motherboards BMC chip.

To monitor a server using the IPMI-Over-LAN protocol:


2. Click IPMI-Over-LAN.

IPMI-over-LAN Credentials

3. Enter the Usernameand Password to use to establish the connection with the IPMI chip out-of-band (IPMI-over-LAN).




Configuring Global Alert SettingsConfiguring Global Alert Settingsconsists in indicating:

the specific actionsto be executed when a hardware failure is detected.

the number of consecutive timesan attribute has to stay above (or below) the threshold for an alertto be triggered.

the action to perform when the solution returns an Unknown Status on a device.

the delay after which Error Countattributes should be reset.


48/88


Version 1.9.00


Configuring Alert Actions

Alert Actions enable the administrator to choose specific actions to be executed when a hardwarefailure is detected. With Alert Actions, it is possible to customize the way a hardware problemnotification is performed.

BPPM Hardware can be configured to run one, several, or all types of Alert Actions when an alert istriggered 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 Settingssection, clickAlert Actions.

Configuring Alert Ac tions

3. Select the type of event you want the solution to perform Upon a Hardware Problem Triggerfield and Upon a Connector Failure Trigger:

A STD 41 PATROL Event

A Specific PATROL Event

No Event

These events a re generated every t ime a threshold is exceeded. They contain a full Hardware Health Reportdeta iling the fault that has occurred.

4. (BPPM 9.5 only) Check theEnable Annotationsoption to make the solution annotate theparameters graph with a comprehensive report of the problem.

5. Click Closeto save your settings.



49/88


Version 1.9.00


Configuring Alert Delay

Configuring the alert delay consists in indicating the number of consecutive times an attribute has tostay above (or below) the threshold for an alert to be triggered. This setting will prevent false alerts tobe 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:

1. Configure the Monitor Settings.2. In the Global Alert Settingssection, click theAlert Delaybutton.

Configuring Alert Delay

3. Use the spin button to indicate the number of consecutive times parameters have to stay above (orbelow) the threshold of an alert to be triggered.

4. Click Close to save your settings.


Configuring the Unknown StatusBPPM Hardware returns an Unknown Statuswhen it is unable to detect the status of a monitoreddevice. Even though this situation is rare, you may want to get notified of this Unknown Statusin aparticular way such as a warning or an alarm. To get this specific notice, you need to tell BPPMHardware how you want the Unknown Status to be interpreted by using the Unkn Statussetting.

To configure the Unknown Status:


2. In theGlobal Alert Settingssection, click Unkn Status.


50/88


Version 1.9.00


Configuring the Unknown Sta tus

3. From the drop-down list, select:

Nothingnot to feed theStatusattribute0 (OK)to set theStatus attribute to OK (default)

1 (Warning)to trigger a WARNING on the Statusattribute

2 (Alarm)to trigger an ALARM on the Statusattribute

4. Click Close to save your settings.5. In theAdd Monitor Types dialog box, clickAdd.

Automatically Resetting Error Count ParametersError 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 CountParameters:


2. In the Global Alert Settingssection, clickAuto Reset .

A utom a t ica lly Re se tt ing Erro rC ount Pa ra m e ters

3. From the Error Count Parameterslist, select the period of time after which you want the solutionto automatically reset the Error Count parameters.




51/88


Version 1.9.00


Configuring Global Advanced SettingsConfiguring Global Alert Settingsconsists 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 CommandsTo collect hardware information about the local host where the PATROL Agent is installed, you mayhave 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 Settingssection, click Local Cmd.

Configuring the Local Comm ands

3. Enter the UsernameandPasswordto 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 Neededoption to use the "sudo" utility to executeexternal commands as "root

Enter the Sudo Command Lineto execute




52/88


Version 1.9.00


Configuring Intervals

BMC ProactiveNet Performance Management - Hardware periodically performs discoveries to detect newcomponents in your monitored environment. By default, the solution runs a discovery every hour, butyou can customize this interval to match your specific needs.

To configure the discovery and polling interval1. Configure the Monitor Settings.

2. In the Global Advanced Settingssection, click Intervals.

Configuring the Discove ry Interv al

3. Use the spin buttons to:

Enter the frequency (in minutes) of the discovery process. By default, the discovery interval is setto 60 minutes

Enter the interval at which the solution must poll the managed systems to collect hardware healthdata. By default, the polling interval is set to 2 minutes

4. Click Close to save your settings.



53/88


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 theDebug Mode and provide the debug output to the Sentry Software support team.

To enable the debug mode1. Configure the Monitor Settings.

2. In the Global Advanced Settingssection, click Debug.

Enabling the Debug Mode

3. Check the Enable Debug Modeoption. The solution will store debug information in a log file. Bydefault debug files are stored in the %PATROL_HOME%\log folder

4. In the Debug End Timefield, enter the date and time at which the system must stop loggingdebug 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 EndTime must be properly set to a date and time in the future.




54/88


Version 1.9.00


Setting Additional Configuration Variables

Advanced configuration variables can be used to manually set variables that cannot be configuredthrough the CMA interface.

These variables should only be set when instructed by Sentry Software Support.

To set configuration variables1. Configure the Monitor Settings.

2. In the Global Advanced Settingssection, clickAdd Variables.

Sett ing Configurat ion Variables

3. Enter the NameandValue of the configuration variable you need to configure. Multiple values mustbe separated by a semi-colon (;).

Variables Description

automaticReinitialization If set to 1, triggers a re-initialization of BPPM Hardware. The discovery checksthis variable every hour (by default) and deletes it before performing the re-initialization.

collectionHubHeapSizeMax Maximum heap size in megabytes allocated to the Java Collection Hub.Default: Not set (assumed 128 MB).


55/88


Version 1.9.00



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. Thisvariable should only be set if instructed by Sentry Support.

collectTimeout Maximum time in seconds the collectors wait for the previous collection tocomplete. When this t imeout is reached, it means the prev ious collection didnot complete in a timely fashion.Default: Not set (assumed 300 seconds).

currentVersion Indicates the version level of the configuration. This should always match withthe version of BPPM Hardware. BPPM Hardware uses this variable to performmigration operations on the configuration variables. The variable isautomatically set during its initialization.Default: 1.9.00.

deactivatedDeviceClassList List of monitor types that are deactivated, for which no discovery and nocollection will be performed. Use this variable to completely disable themonitoring 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 findthe 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 thePATROL namespace for any host.

disableJRECheck When set to 1, disable the validation tests of the JRE used by BPPM Hardwareto run Java code. This can be used to force BPPM Hardware to use a non-Sunor non-Oracle JRE.

disableMissingDeviceDetection When set to 1, disables the missing device detection mechanism of BPPMHardware. By default, BPPM Hardware raises an alarm for devices that werediscovered and that are no longer discovered.Default: Not set

disablePslExecuteBugWorkaround When set to 1, deactivates the workaround for a bug in the PslExecute() PSLfunction.If BPPM Hardware detects that the version of the PATROL Agent is affectedby the PslExecute() bug, it uses an alternate technique to createasynchronous threads with the event_trigger() function and the RemPslstandard event. The disablePslExecuteBugWorkaround variable disables thisworkaround.

findWbemNamespaceTimeout Number of seconds after which a remote BPPM Hardware stops trying to get aserver namespace v ia WBEM.Default value: 1200.


56/88


Version 1.9.00



forceSnmpSerialization Maximum time in seconds the main discovery process waits for the previousdiscovery to complete. When this timeout is reached, it means the previousdiscovery did not complete in a timely fashion.Default: Not set (assumed 600 seconds).

globalDiscoveryTimeout Maximum time in seconds the main discovery process waits for the previousdiscovery to complete. When this timeout is reached, it means the previousdiscovery did not complete in a timely fashion.Default: Not set (assumed 600 seconds).

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 waitfor the previous discovery to complete. When this timeout is reached, it meansthe previous discovery did not complete in a timely fashion.Default: Not set (assumed 300 seconds).

intrusionDetectionAlert Alert sett ings 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 isdetected 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 canbe used if BPPM Hardware cannot find the location of the ipmitool utilityautomatically.Default: Not set.

javaPassword Password associated to the javaUsername variable. Default: Not set (BPPMHardware 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, therelated monitor types are:

Hardware Logical Disk

Hardware Voltage

Hardware Temperature

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.


57/88


Version 1.9.00



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.

remoteCommandMaxConnectionsPerHost

Maximum number of Telnet or SSH sessions opened at once for a single host.Default: Not set (assumed 5).

remoteCommandTimeout Number of seconds after which a remote OS command execution will be killed.Default: Not set (assumed 60 seconds).

snmpTimeout Timeout in seconds when performing SNMP queries. Only applicable whenforced SNMP serialization has been enabled (/SENTRY/HARDWARE/forceSnmpSerialization)Default: Not set (assumed 60 seconds).

snmpWalkMaxItems Max imum 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.

This variable should only be set if instructed by Sentry Support.

startupDelay Allows the administrator to specify the number of seconds that BPPM Hardwarewill wait before starting its platform detection and discovery. This variable maybe useful on fast booting computers where the PATROL Agent starts beforeother 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.This variable should only be set if instructed by Sentry Support.

telnetCommandJarPath Path to the Telnet command JAR file.

Default: Not set.This variable should only be set if instructed by Sentry Support.

telnetConnectionMethod Default (Windows): Java (if conf igured in the KM)Note: If the PATROL Agent version is 3.6.011 or later the connection methodused by BPPM Hardware is 'sopen'; otherwise it is left blank.Default (UNIX): Telnet.

ThresholdManagementMode Specifies how BPPM Hardware should manage the alert thresholds onattributes. 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.


58/88


Version 1.9.00



ucsJarPath Path to the Cisco UCS client JAR file.Default: Not set.This variable should only be set if instructed by Sentry Support.

ucsTimeout Timeout in seconds when performing a UCS queries.Default: Not set (assumed 60 seconds).

ucsVbsPath Path to the Cisco UCS Windows client.Default: Not set.This variable should only be set if instructed by Sentry Support.

UNIXConsoleMode When set to 1, makes BPPM Hardware use short display name for the icons inthe PATROL Consoles. This can be useful for UNIX PATROL Classic Consolesbut this flags affects every console connected to the agent.Default: Not set.

wbemTimeout Timeout in seconds for a WBEM query to complete.

Default: Not set (assumed 60 seconds).

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. ClickAdd to List

You can easily modify or remove a variable by selecting it in the list and clicking either the ModifySelectionor the Remove from Listbuttons.




59/88


Version 1.9.00


Scheduling Automatic ReportsBMC ProactiveNet Performance Management - Hardware can automatically produce text reports aboutthe monitored systems.

To schedule automatic reports1. Configure the Monitor Settings.

2. In the Reportingsection, click Schedule.

Scheduling autom atic reports

3. In the Schedulesection, specify the time at which the report(s) must be generated.

4. Check the:

Energy Usagereport type to automatically generate an Energy Usage report that will be savedby default as MS_HW_energyUsage*.csv in the %PATROL_HOME%\log folder

Ethernet/Fiber Port Activityreport type to automatically generate an Ethernet/Fiber PortActivity report that will be saved by default as MS_HW_networkActivity*.csv in the %PATROL_HOME%\log folder

Hardware Inventoryreport type to automatically generate a Hardware Inventory report thatwill be saved by default as MS_HW_hardwareInventory*.csv in the %PATROL_HOME%\log folder



Updat ing a policy that sets the sche duling options of a report purges the re port configuration variables and stops thereport process

The history retention period can be set from the PATRO L Console or from the PA TROL Ag ent using a configurationvariable. The default collection (retention) period is one day. Whenever a stored parameter value exceeds itsretention period, it is automatically de leted from the para meter history file. R efe r to BMC documentat ion for details.


60/88


61/88

61Configuring Thresholds

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

10. Click Saveat the bottom of theAdd Policydialog box, or Updateat the bottom of the Edit Policydialog box.

After you save or update the policy, new threshold configurations are pushed to BMC PATROL Agentswith matching Central Monitoring Configuration tags.

Editing a Threshold ConfigurationTo edit a threshold configuration:

1. Edit an existing policy

2. On the Threshold Configurationtab, select a threshold definition, and click Edit.

3. Edit the configuration values and click Update.

4. When you finish editing the threshold configuration, click Close.

5. To save changes to the policy, click Updateat the bottom of the Edit Policydialog box.

After you update the policy, updated threshold configurations are pushed to BMC PATROL Agents withmatching Central Monitoring Configuration tags.

Deleting a Threshold Configuration

To delete a threshold configuration:

1. Edit an existing pol

Bbpm Perfmon Mgmt

Documents