TrueSight Operations Management - Hardware v1.9 · Configuring Monitor Settings ... Both UemCli and Navisphere ... TrueSight Operations Management - Hardware Version 1.9.60 Overview

TrueSight Operations Management -Hardware

USER DOCUMENTATION

Version 1.9.60

December 2016

HARDWARE MONITORING

http://www.sentrysoftware.com

http://sentrysoftware.com/Solutions/Hardware_solution.asp

Contacting BMC Software

You can access the BMC Software Web site at http://www.bmc.com. From this Web site, you canobtain information about the company, its products, corporate offices, special events, and careeropportunities.

United States and Canada

Address BMC Software, Inc.2101 CityWest Blvd. Houston TX77042-2827

Telephone 1 (713) 918 8800 or 1 (800) 841 2031 (Toll Free)

Copyright 2015 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 andconfidential. Your use of this information is subject to the terms and conditions of the applicableEnd User License Agreement for the product and the proprietary and restricted rights noticesincluded in this documentation.

Restricted Rights Legend

U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVEDUNDER THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any dataand computer software by the U.S. Government is subject to restrictions, as applicable, set forthin FAR Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, andDFARS 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 thisaddress.

2

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Customer Support

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.

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

You can also access product documents and search the Knowledge Base for help with an issue at http://www.sentrysoftware.com

Support by Telephone or E-mail

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

3

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

http://www.bmc.com/support_home


http://www.sentrysoftware.com


4

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Table of Contents.....................................................................................................................................................................................13Overview

.....................................................................................................................................................................................14Monitored Components

.....................................................................................................................................................................................16Product at a Glance

.....................................................................................................................................................................................17Platforms & Requirements

.....................................................................................................................................................................................22Solution Packages

.....................................................................................................................................................................................22Upgrading from Previous Versions

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

.....................................................................................................................................................................................29Creating the Installation Package

.....................................................................................................................................................................................30Downloading the Installation Package

.....................................................................................................................................................................................30Installing the Package

.....................................................................................................................................................................................33Configuring Monitor Settings

.......................................................................................................................................................................................33Configuring Devices to Monitor

......................................................................................................................................................................36Using the SNMP Protocol

......................................................................................................................................................................39Using the SSH/Telnet Protocol

......................................................................................................................................................................41Using the WBEM Protocol

......................................................................................................................................................................43Using the WMI Protocol

......................................................................................................................................................................44Using the Cisco UCS Manager

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

.......................................................................................................................................................................................46Configuring Global Alert Settings

......................................................................................................................................................................47Configuring Alert Actions

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

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

......................................................................................................................................................................51Enabling/Disabling the Missing Device Detection

......................................................................................................................................................................53Configuring the Unknown Status

.......................................................................................................................................................................................54Configuring Global Advanced Settings

......................................................................................................................................................................55Configuring Local Commands

......................................................................................................................................................................56Configuring Intervals

......................................................................................................................................................................57Enabling the Debug Mode

.......................................................................................................................................................................................58Scheduling Automatic Reports

.....................................................................................................................................................................................62Getting Additional Product Information

.....................................................................................................................................................................................63Troubleshooting Connectivity Issues

.....................................................................................................................................................................................67Monitor Types and Attributes

5

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

.......................................................................................................................................................................................69Hardware Battery

.......................................................................................................................................................................................70Hardware Blade

.......................................................................................................................................................................................71Hardware Capacity Report

.......................................................................................................................................................................................72Hardware CPU Core

.......................................................................................................................................................................................73Hardware Disk Controller

.......................................................................................................................................................................................74Hardware Disk Enclosure

.......................................................................................................................................................................................75Hardware Enclosure

.......................................................................................................................................................................................76Hardware Fan

.......................................................................................................................................................................................77Hardware LED

.......................................................................................................................................................................................77Hardware Logical Disk

.......................................................................................................................................................................................78Hardware LUN

.......................................................................................................................................................................................79Hardware Memory Module

.......................................................................................................................................................................................79Hardware Network Interface

.......................................................................................................................................................................................81Hardware Other Device

.......................................................................................................................................................................................82Hardware Physical Disk

.......................................................................................................................................................................................84Hardware Power Supply

.......................................................................................................................................................................................85Hardware Processor

.......................................................................................................................................................................................86Hardware Robotics

.......................................................................................................................................................................................87Hardware Sentry Connector

.......................................................................................................................................................................................88Hardware Tape Drive

.......................................................................................................................................................................................89Hardware Temperature

.......................................................................................................................................................................................90Hardware Voltage

.....................................................................................................................................................................................91Global Advanced Additional Configuration Variables

.....................................................................................................................................................................................97Device Additional Configuration Variables

.....................................................................................................................................................................................100Managing Baselines and Key Performance Indicators

Release Notes for v1.9.60

7

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

What's New

Functionality

MSHW-4299 - Configuration variables: The rediscoverHosts variable is now available to forcethe discovery of specific hosts.

MSHW-4375 - TrueSight Operations Management - Hardware has been updated to becompatible with the latest versions of PATROL Agent's AES256-bit security encryptionalgorithm (for example, PATROL Agent version 10.0.00).

Supported Platforms

TrueSight OM - Hardware now monitors the following platforms:

HC-1 - Hitachi Compute Blade Chassis Management Module (monitored via SNMP).

HC-7 - Cisco UCS C-Series (via CIMC card).

HC-273 - Hitachi HNAS Systems (monitored via SNMP).

MSHW-3859 - EMC VNXe Storage Systems.

MSHW-4023 - Quantum DXi Deduplication / NAS / Backup Systems (monitored via SSH).

Monitored Components

The product now monitors the following components:

8

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

HC-335 - VMware ESX5i LUNs: TrueSight OM - Hardware now supports the monitoring ofESX5i LUNs booting with USB Stick/SD Card. The ESX Disks - IPMI connector is automaticallydisabled if no local disks are detected.

HC-365 - Ports with name beginning with en[ospx] (CentOS / Redhat 7).

MSHW-4201 - Oracle Logical RAID disks/volumes.

MSHW-4234 - Dell PowerEdge SD Cards.

MSHW-4284 - Components of external disk shelves attached to a Dell PowerEdge Server,such as power supplies and fans.

MSHW-4311 - The underlying physical network ports of virtual network ports in Solaris 11.

MSHW-4491 - VMware ESXi 6.0 disks.

Changes and Improvements

Functionality

MSHW-4581 - A report providing detailed information about TrueSight OM - Hardware is nowautomatically generated when the monitoring solution is started or reinitialized.

Supported Platforms

HC-13 - Fujitsu Eternus DX Disk Arrays monitoring: Logical Disks are now better identified bytype (Volume, RAID Storage Pool, Thin Pool, etc.).

HC-29 - IBM AIX - sissasraidmgr commends with sudo enabled: The sissasraidmgr commandsometimes only runs from a specific directory when executed through sudo. This mayprevent the connector to be used when sudo is enabled. The connector now changes thecurrent directory to that specific directory before running the sissasraidmgr command.

HC-253 - EMC PowerPath monitoring: PowerPath Logical Device IDs containing spaces werenot handled properly. The product now supports and reports PowerPath Logical Devicewhich IDs contain spaces.

HC-254 - Sun Solaris - RAID Disks: The serialization of the command execution has been fixedto avoid connector failure (“raidctl:enter_filelock:filelock is owned by 'process xxxx'”).

HC-283 - SPARC Systems monitoring: CPUs on SPARC systems listed as "host processors"instead of "processors" were erroneously placed under Other Devices. "Host processors" arenow properly listed under CPUs.

MSHW-4241 - HP ProLiant Servers: The display name of NIC teams (network interfaces) hasbeen improved.

MSHW-4305 - Dell Blade servers (through CMC): Display name has been modified to betteridentify the monitored blades. It now consists of the model and a unique identifier.

Fixed Issues

Functionality

9

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

MSHW-4201 - Oracle/Sun Disk Controllers monitoring: The IDs assigned by the Oracle agentto identify Disk Controllers were not stable in the Oracle/Sun Hardware Agent. This couldprevent the product to accurately associate an event with the right disk controller. To avoidthis problem, the product has been modified to use the name of the controller as the uniqueID (and display ID).

MSHW-4419 - SNMP v3: SNMP connections failed when the authentication protocol was setto "None".

MSHW-4512 - Debug Log File: When monitoring through Telnet or SSH, TrueSight OM -Hardware could needlessly create two debug log files for the same device or system (oneidentified with the device/system hostname and another with its IP address). A single debugfile is now created and labeled with the device/system's hostname.

MSHW-4564 - WBEM queries to CIM Agents failed when using Java 1.8.

Supported Platforms

HC-252 - Hitachi HDS USP/VSP Storage Systems:

Multiple instances of Hitachi VSP enclosures could be displayed

Environment alerts were not received

HC-282 - Dell PowerEdge Servers: Some disks could be missing when monitoring servers withexternal disk shelves when the disks inside the server shared IDs with disks in the diskshelf.

HC-284 - HP Servers Running Windows: All temperature thresholds of zero are now removedto avoid unwanted temperature alerts.

MSHW-4155/MSHW-4241 - HP ProLiant Servers:

Network interfaces were not properly discovered.

WAN interfaces were detected as physical network cards.

10

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

MSHW-4221 - VMWare ESX: Only one memory module was detected when the componentID was the same for all. To solve this issue, the solution now uses the device ID to identifymemory modules.

MSHW-4458 - EMC CLARiiON, VNX and VNXe storage systems: Both UemCli and Navispherewould activate when installed on the same server.

Monitored Components

HC-281 - SMI-S Raid Controllers monitoring: The connector now verifies that each controllerhas associated physical disks to prevent non-controllers devices from being falsely reportedas controllers.

HC-316 - Cisco UCS with Fabric Extenders: Physical components were not attached to theproper enclosure instance.

HC-336 - No CPUs were discovered on Oracle Netra T4 systems.

HC-347 - Linux Multipath monitoring: The number of paths was not calculated correctly whenthe mpath listed more than only policy line.

HC-408 - Statistics, link status, and link speed were not available on SAN Switches FC ports.

HC-460 - Multiple cards with the same Mac address appeared in the monitoring console. Tosolve this issue, CompositeBus virtual cards have been excluded from the monitoringprocess.

MSHW-237 - EMC PowerPath LUNs: The monitoring of EMC PowerPath LUNs has beenimproved to fix an issue where the Available Path Count attribute was set to zero andtriggered an alarm.

MSHW-4117 - Fujitsu Servers Running ESX: Environment sensors were missing when themain identifier (caption) was blank. To solve this issue, the solution now uses the deviceIDfield to identify sensors.

MSHW-4385 - IBM AIX Servers: The monitoring of SEA Virtual Adapters has been improved toinclude statistics and link status for virtual ports.

MSHW-4407 - Hardware Sentry discovered and monitored dormant CPUs on HP-UX systems.Dormant HP-UX CPUs have been excluded from the monitoring process.

MSHW-4458 - Hardware Sentry now recognizes the unbound status of the Navispherephysical disks.

11

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Getting Started

13 Overview

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

OverviewTrueSight Operations Management - Hardware monitors the hardware of almost any server(physical, virtual, and blade servers) and external storage device (disk arrays, fiber switches, andtape libraries) available in datacenters. Once TrueSight OM - Hardware is installed andconfigured for monitoring, all the hardware components are automatically detected and broughtinto BMC TrueSight Operations Management.

Contrary to manufacturers’ monitoring tools, TrueSight OM - Hardware allows IT administratorsto monitor their heterogeneous infrastructure into one single console. Because thresholds areautomatically set according to the manufacturers' recommendations and alarms triggered assoon as these thresholds are breached, hardware failures can be detected at an early stage, longbefore they impact business.

Several reports can also be easily be generated to be informed about the energy usage, the portactivity or to obtain a detailed hardware inventory.

To learn more about TrueSight OM - Hardware, watch this 2-minute video: Monitoring Multi-Vendor Hardwarewith Sentry Software .

http://www.youtube.com/v/iHFCE8H6KSI

http://www.youtube.com/v/iHFCE8H6KSI

14Overview

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Monitored ComponentsTrueSight OM - Hardware monitors the following components:

Hardware Components Information Collected

BatteriesAvailability and statusCharge percentage

BladesAvailability and statusPower state

CPU CoreAvailability and statusSpeedPercentage of the CPU Core usage speed

Disk ControllersAvailabilityStatus of the disk controller and of its battery

Disk EnclosuresAvailability and statusIntrusion detection

EnclosuresStatusIntrusion detectionPower consumption

FansAvailability and statusFan Speed (in rotations/minute)

TrueSight OM - HardwareConnector

Status

LEDs Status

Color

Logical DisksStatusAmount of unused disk spaceNumber of encountered errors

LUNsStatusNumber of available paths

15 Monitored Components

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Components Information Collected

Memory ModulesAvailability and StatusNumber of errors detected and correctedPredicted failures

Network InterfaceAvailabilityLink speedPercentage of sent and received packets that were in errorStatus (Network Interface and status of the network interface to thenetwork)Percentage of transmitted and received packages

Other DevicesAvailability and StatusNumber of times the device has been used. Device value

Physical DisksAvailability and statusNumber of errors (on the physical disk, not ready device errors, harderrors, etc.)Predicted failures

Power SuppliesAvailability and statusPower currently in use (in percentage)

Processors (CPU) Availability and statusCurrent speed (in megahertz)Number of errors automatically correctedPredicted failures

Robotics Availability and statusNumber of moves and number of moves in failure

Tape DriveAvailability and statusNumber of mount and unmount operationsNumber of tape drive failures

Temperature Sensors Current temperatureStatus

Voltage SensorsStatusVoltage output in milliVolts

16Monitored Components

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Product at a GlanceTrueSight Operations Management - Hardware leverages one or several sources (manufacturer-specific hardware agents, standard management technologies, SSH, SNMP, WBEM, WMI, etc.) togather hardware information and display it in the BMC TrueSight Operations ManagementConsole.

17 Product at a Glance

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Platforms & RequirementsTrueSight Operations Management - Hardware requires specific instrumentation agents orsystem management tools to be present on the managed system to collect hardwareinformation.

Servers

Typical Platform Operating System Instrumentation Prerequisites Technology Used

Cisco UCS B-Series, C-Series

Windows None IPMI, WMI


Linux ipmitool IPMI, command lines


ESX None WBEM

Dell PowerEdge Windows Dell OpenManage ServerAdministrator

SNMP

Dell PowerEdge Linux Dell OpenManage ServerAdministrator

SNMP

Dell PowerEdge ESX None WBEM

Fujitsu PRIMEPOWERServers (sun4us) -

Solaris None Command lines

Fujitsu-SiemensPRIMERGY

ESX Fujitsu Serverview WBEM agent WBEM


Windows Fujitsu-Siemens ServerviewFujitsu-Siemens ServerView RAIDAgent / Promise FastTrack SNMPAgent / LSI GAM Server / LSIMegaRAID SAS SNMP Agent / LSIMegaRAID PowerConsole /Mylex GAM Server (dependingon the server, follow Fujitsu-Siemens recommendations)

SNMP


Linux Fujitsu-Siemens ServerviewFujitsu-Siemens ServerView RAIDAgent / Promise FastTrack SNMPAgent / LSI GAM Server / LSIMegaRAID SAS SNMP Agent / LSIMegaRAID PowerConsole /Mylex GAM Server (dependingon the server, follow Fujitsu-Siemens recommendations)

SNMP


Linux Fujitsu-Siemens ServeviewWBEM Agent

WBEM

18Platforms & Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60



Windows Fujitsu-Siemens ServeviewWBEM Agent

WMI


ESX None WBEM

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

Command lines orWBEM

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

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

Command lines orWBEM

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 ProLiant ESX HP Insight Management Agent WBEM

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

HP SuperDome (PA-RISC) HP-UX GSP card Command lines

Huawei Servers All Management Card SNMP

IBM pSeries, IBM eServer IBM AIX None Command lines

IBM xSeries, IBMNetfinity

Windows IBM Director Agent WMI


Linux IBM Director Agent WBEM, commandlines


ESX None WBEM

IBM VIO Server IBM AIX None SSH

Lenovo IMM Windows Integrated Management Module SNMP

NEC Express5800 Windows NEC ESMPRO Agent SNMP

NEC Express5800 Linux NEC ESMPRO Agent SNMP

Oracle (Sun) SPARC/x86 TSeries, X Series

Solaris Oracle Hardware ManagementAgent

SNMP

Sun Fire (X64) Solaris ipmitool, lsiutil Command lines

19 Platforms & Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


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 utilitiesinstalled on the SystemController (SC)

SSH to the SystemController

Sun Fire Mx000 Solaris Access to the eXtended SystemControl 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

QLogic HBA Windows None WMI

QLogic HBA Linux scli Command lines

QLogic HBA Solaris scli Command lines

Blade Chassis

Chassis Instrumentation Prerequisites Technology Used

Cisco UCS InterconnectChassis

Cisco UCS Manager on the Cisco UCSInterconnect Switch

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 ManagementModule

SNMP

IBM BladeCenter IBM BladeCenter Management Module SNMP

IBM PureFlex Chassis IBM BladeCenter Management Module SNMP

Sun Blade Modular Chassis Access to the Chassis Management Module(CMM)

SNMP


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Storage Devices and Other Devices

Typical Platform Instrumentation Prerequisites Technology Used

3PAR InServ 3PAR SMI-S Provider WBEM

Brocade SAN Switch SNMP Enabled SNMP

Cisco Ethernet Switch None SNMP

Cisco MDS, Nexus None Telnet/SSH

Compellent Compellent Enterprise Manager WBEM

Dell EquaLogic PS Series None SNMP

Dell TL2000/4000 TapeLibraries

Dell OpenManage Server Administrator SNMP

EMC CLARiiON EMC SMI-S Provider WBEM

EMC CLARiiON EMC Navisphere CLI System Commands

EMC Isilon EMC Isilon SSH interface SSH

EMC Symmetrix EMC SMI-S Provider WBEM

EMC VNX series EMC SMI-S Provider WBEM

EMC VNX series EMC Navisphere CLI System Commands

EMC VNXe uemcli System Commands

Fujitsu Eternus ETERNUS SMI-S Agent WBEM

Fusion ioDrive fio-status cli utility Command lines

Hitachi AMS/HUS HSNM2 CLI Command lines

Hitachi HNAS Hitachi SNMP Agent SNMP

Hitachi USP/USP-V Hitachi SNMP Agent SNMP

Hitachi VSP Hitachi SNMP Agent SNMP

HP P2000 G3 MSA Arrays HP P2000 Management Card WBEM

HP StorageWorks P6000 HP CommandView EVA Command lines

HP StorageWorks XP /P9000 Series

Hitachi Device Manager or HP P9000CommandView Advanced Edition

WBEM

Huawei Storage Systems(OceanStor)

Huawei Storage System SNMP Agent SNMP

IBM DataPower Data Domain SNMP Agent SNMP

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 Libraries None SNMP

IBM v3700 Disk Arrays None Telnet/SSH

21 Platforms & Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60



IBM TS3100 Tape Libraries None SNMP

IBM TS3200 Tape Libraries None SNMP

IBM XiV IBM XIV Storage System SMI-S Agent WBEM

MacroSan Storage Systems MacroSan SNMP Agent SNMP

McData SAN Switch None SNMP

NetApp None SNMP

Oracle/Sun InfiniBand DCSSwitches

Oracle/Sun ILOM SNMP Agent.SNMP v1 enabled on the switch.

SNMP

Oracle/Sun Xsigo Switches Sun Xsigo SNMP Agent SNMP

Oracle/Sun ZFS StorageAppliances

Oracle ZFS Command Line (SSH SSH

Pure Storage FA Series Pure Storage Management Card SSH

Quantum DXiDeduplication / NAS /Backup Systems

Commands on the Quantum DXi controller SSH

Quantum Tape Libraries None SNMP

StorageTek LSeries None SNMP

StorageTek StreamLine (SL) None SNMP

Generally, manufacturers provide instrumentation agents and system tools for free and these areeither found on the CD-ROM provided with the server or, on the manufacturer’s web site. Unlessmentioned otherwise, the manufacturer’s instrumentation agent must be installed on the monitoredserver for TrueSight OM - 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 the Sentry Software website.

Java Runtime Environment

Java Runtime Environment version 1.6.00 or higher is required in some cases for the solution tooperate properly (notably when the solution needs to make WBEM or SSH connections).

Apache JRE is not supported.

http://www.sentrysoftware.com/


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Solution PackagesTrueSight OM - Hardware Packages

Packages are available on the Sentry Software Web site.

There are three packages, each of which can be used to install the product on every TrueSightcomponent (Agent, Repository, 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

Java Runtime Environment Package

A package of a suitable Java Runtime Environment, designed for use with the BMC SoftwareInstallation Utility, is made available to download on the Sentry Software Web site.

Upgrading from Previous VersionsAfter installing the latest version of TrueSight Operations Management - Hardware, themonitoring solution must be reinitialized. TrueSight OM - Hardware will then run a fulldiscovery, set the appropriate connectors, and restart the monitoring of existing and newdevices.

To reinitialize the monitoring solution:

1. In the Navigation pane of Central Monitoring Administration, click the Policies drawer andselect a policy view (e.g. All).

2. Select a policy and click Edit .

3. Click the Configuration Variables tab.

4. Click Add to set the required configuration variable. The Add Configuration Variable paneis displayed.

Upgrading from Previous Versions - Adding Configuration Variable

5. Provide the following information:

Variable: type "/SENTRY/HARDWARE/automaticReinitialization"

http://www.sentrysoftware.com/products/km-hardware-sentry.asp

http://www.sentrysoftware.com/products/km-hardware-sentry.asp

23 Upgrading from Previous Versions

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Operation: select "REPLACE" from the drop-down list

Value: type "1"

6. Click Add.

7. Click Close to save your settings.

8. Click Finish.

A reinitialization of TrueSight OM - Hardware is performed. The discovery checks the automaticReinitialization variable every minute and deletes it in the PATROL agent configurationbefore performing the re-initialization.

To prevent further unexpected reinitializations, it is recommended to later remove the automaticReinitialization variable from the policy.

24Upgrading from Previous Versions

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Installing the Monitoring Solution

27

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Once the latest version of the solution has been loaded into Central Monitoring Administration,administrators can create all the installation packages required for their different operatingsystems 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 toconnect to TrueSight Operations Management 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 TrueSight OM - Hardware:

Importing TrueSight OM - Hardware into Central Monitoring Administration

Creating the Installation Package

Downloading the Installation Package

Installing the Package

28

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Importing the Monitoring Solutioninto Central AdministrationThe TrueSight Central Monitoring Repository includes the current versions of TrueSightOperations Management - Hardware that you can use with BMC TrueSight. If the versionavailable in the Repository does not correspond to the latest one, you will have to manuallyimport it:

1. Log on to the BMC TrueSight Operations Management Console.

2. Launch Central Monitoring Administration.

3. Click the Repository drawer and select Manage Repository.

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

5. From TrueSight Operations Management, click Import .

6. Select Single solution.

7. Browse to the .zip source file.

8. Click Import.

The selected archive file is imported to the repository.

http://www.sentrysoftware.net/Products/index.asp

29 Importing the Monitoring Solution into CentralAdministration

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Creating the Installation PackageThe installation package to deploy to managed systems can be created directly from TrueSightOperations Management:

1. Log on to TrueSight Operations Management

2. Click the Repository drawer and select Deployable Package Repository.

3. Click Add .

4. Select the operating system and platform for which you want to create a package. Thecomponents available in the repository for the selected operating system and platform aredisplayed.

5. Select the Installation Package Component:

From the Available components list, select the relevant component.

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 PATROL Agent for the operating system and platform thatyou chose is included in the Selected components list.

Click Next. The Add Component Installation Package wizard are displayed.

6. Go through the wizard and specify the required PATROL information. The InstallationPackage Details is displayed.

7. Verify that:

the operating system and platform are correct

the components that you want to include are listed in the Included Components list.

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 inthe Monitoring 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 Packages list.

30Creating the Installation Package

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

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.

RecommendationIf you defined the BMC TrueSight Integration Service variable for PATROL Agents in theinstallation package, ensure the agents are started in phases. Do not start newly deployedagents all at once. Start and configure monitoring for the agents in planned phases to reducethe performance impact on the Integration Service nodes and on the BMC TrueSight Serverassociated with the automatic workflow process.

1. Log on to TrueSight Operations Management from the computer on which the PATROL Agentis installed or to be installed.

2. Click the Repository drawer and select Deployable Package 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.

Installing the PackageThis chapter provides a step by step procedure to install a monitoring solution package:

1. From the computer on which you want to install the package, log on to TrueSight OperationsManagement.

2. (Optional) To filter the list of installation packages, select an operating system from the Filter by Operating System list.

3. Click the link for the installation package that you want to download.

4. Through the browser's download dialog box, save the installation package in a temporaryfile.

5. Extract the installation package that is appropriate for your operating system. The package isextracted to the bmc_products directory on the current host.

6. 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, theagent sends a configuration request by passing its tags to Central Monitoring Administration, viathe Integration Service. Central Monitoring Administration evaluates policies that match thetags, determines the final configuration to be applied, and sends the configuration informationback to the agent. Monitoring is based on the configuration information received by the agent.

Configuring After Installation

33 Configuring Monitor Settings

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring Monitor SettingsWhen you create or edit a policy, you can add and configure monitor types. The Add MonitorTypes dialog box presents configuration fields for compatible BMC PATROL monitoring solutionsthat are located in the Central Monitoring Repository.

To configure the Monitor Type settings1. 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. Click Add .

5. From the Solution menu, select Hardware.

6. From the Version menu, select the required version.

Configuring Devices to MonitorYou can configure TrueSight OM - Hardware to monitor devices. The procedure is as follows:

1. Create a new policy or edit an existing one

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 previouslyspecified will be used.

(Optional for localhost) Select the Device Type.

34Configuring Monitor Settings

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

3. Configure the protocol(s) to be used to monitor the 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 thesolution.

Use Specified Connectors (Advanced Users Only): to list the connectors to be usedby the solution.

If you selected the Exclude Specified Connectors or Use Specified Connectors option,enter in the Connector File Names field the name of the connectors that will be used ornot by the solution. Connector names must be separated by a comma (,).

Click Close to validate.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

5. (Optional) In the Device Advanced Settings section, click Additional 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. Multiplevalues 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 existing device and click Modify Selection to edit the settings of the selected deviceor also Remove from List to delete the selected device.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Using the SNMP ProtocolTrueSight OM - Hardware can leverage the SNMP protocol to collect hardware information. Inthat case, an SNMP agent must be installed on the monitored host and the SNMP connectionconfigured. The information required by TrueSight OM - Hardware will vary according to theversion used:

SNMPVersion

Description Information Required

SNMP v1 Supports 32-bitcounters.

Community.

Port Number (Default: 161).

Timeout is set through the PATROL Agent Conf iguration variable /snmp/default_timeout.

SNMP v2c Supports both 32 and64-bit counters.

CommunityPort NumberTimeout (Default: 120 seconds).

SNMP v3 Encryption andauthentication addedto the 64-bit counters.

Authentication information (username, protocol, and password)Encryption information (privacy protocol and password)Context namePort NumberTimeout (Default: 120 seconds)

To monitor a server using the SNMP protocol:

1. First, configure the device to monitor to be monitored.

2. Click SNMP.

3. Define the SNMP Information:

Select the version of the SNMP protocol used by the device to be monitored. Possiblevalues are 1, 2c, or 3.

Use the spin button to indicate the SNMP port number you wish to use to perform SNMPqueries. By default the SNMP queries are performed through port 161.

Using the SNMP Protocol - SNMP Information


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

4. If you selected SNMP Version 1, indicate the SNMP Community string to use to performSNMP v1 queries:

Using the SNMP Protocol - SNMP v1 Connection Settings

5. If you selected SNMP Version 2c, indicate:

the SNMP Community string to use to perform SNMP v2c queries.

the number of seconds TrueSight OM - Hardware will wait for an SNMP response. Bydefault, the timeout is set to 120 seconds to cover all the sub-queries that compose the'parent' queries.

Using the SNMP Protocol - SNMP v2c Connection Settings

6. If you selected SNMP Version 3, indicate:

The Username to be used to perform the SNMP v3 queries.

The Authentication Protocol to be used to authenticate the SNMP v3 messages. Possiblevalues are: None, MD5, SHA.

The Authentication password to be used to authenticate the SNMP v3 messages.

The Privacy protocol to be used to authenticate SNMP v3 messages. Possible values are:None, AES, DES.

The Privacy password associated with the privacy protocol.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

The Context name accessible to the SNMP entity.

The Port number (default: 161).

The number of seconds TrueSight OM - Hardware will wait for an SNMP response. Bydefault, the timeout is set to 120 seconds to cover all the sub-queries that compose the'parent' queries.

Using the SNMP Protocol - SNMP v3 Connection Settings

7. Click Close to validate.

8. In the Hardware Configuration section, click the Add to List button to validate yourconfiguration.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Using the SSH/Telnet ProtocolSSH/Telnet (Secure Shell/Terminal Network) can for example be used to monitor Linux/UNIXservers or to communicate remotely with systems and devices that have an SSH/Telnet interfaceon their management card. Once the SSH/Telnet options are configured, TrueSight OM -Hardware will run commands to determine the status, performance or capacity of these systems.

To monitor a server using the SSH/Telnet protocol:


2. Click SSH/Telnet.

SSH/Telnet Credentials

3. In the SSH/Telnet section, select the Authentication Mode to use to establish a connectionwith the device. Possible values are SSH, SSH with Authentication Key, and Telnet.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

4. If you have previously selected:

SSH or Telnet, enter the credentials required to connect to the host through the selectedprotocol.

SSH with Authentication Key, specific credentials will be required and more especially theUsername, Passphrase (if required), and the OpenSSH Private Key.

The key file must be accessible to the PATROL Agent that will make the connection to the host throughthe SSH/Telnet protocol.

5. (UNIX/Linux) In the Sudo Options section: Check the Use When root Privileges are Needed option to use the "sudo" utility in orderto execute external commands as "root" on UNIX/Linux platforms.Enter the Sudo Command Line to execute.





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Using the WBEM ProtocolYou can use the WBEM (Web-Based Enterprise Management) protocol to communicate directlywith a SMI-S Provider and collect information.

To monitor a server using the WBEM protocol:


2. Click WBEM.

WBEM Credentials

3. Enter the Username and Password to use to establish the connection with the device usingthe WBEM protocol.

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

5. For encrypted connections, check the Encryption option.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

6. In the Advanced 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 theWBEM credentials.

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





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Using the WMI ProtocolYou can use the WMI (Windows Management Instrumentation) protocol to monitor systems ordevices:


2. Click WMI.

WMI Credentials

3. Enter the Username and Password to use to establish the connection with the device usingthe WMI protocol.





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

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


2. Click Cisco UCS.

Cisco UCS Credentials

3. Enter the Username and Password to use to establish the connection with the Cisco UnifiedComputing System.

4. Uncheck the Encryption option to disable the SSL Encryption for UCS login (HTTPS). Bydefault, the encryption is enabled.





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Using the IPMI-Over-LAN ProtocolIPMI-Over-LAN is the out-of-band interface used by TrueSight OM - Hardware to bypass the usualhardware agents and communicate directly with the motherboard’s BMC chip.

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


2. Click IPMI-Over-LAN.

IPMI-over-LAN Credentials

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





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring Global Alert SettingsConfiguring 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 foran alert to be triggered.

the delay after which Error Count attributes should be reset.

when missing devices should be deleted.

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


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring Alert ActionsAlert Actions enable the administrator to choose specific actions to be executed when ahardware failure is detected. With Alert Actions, it is possible to customize the way a hardwareproblem notification is performed.

TrueSight OM - Hardware can be configured to run one, several, or all types of Alert Actionswhen 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 Alert Actions


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

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

A STD 41 PATROL Event

A Specific PATROL Event

No Event

These events are generated every time a threshold is exceeded. They contain a full Hardware Health Reportdetailing the fault that has occurred.

4. Check the Enable Annotations option to make the solution annotate the parameter’s graphwith a comprehensive report of the problem.




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring Alert DelayConfiguring the alert delay consists in indicating the number of consecutive times an attributehas to stay above (or below) the threshold for an alert to be triggered. This setting will preventfalse 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 Alert Delay

3. Use the spin button to indicate the number of consecutive times parameters have to stayabove (or below) the threshold of an alert to be triggered.




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Automatically Resetting Error Count ParametersError Count parameters keep increasing as new errors are encountered. To reset theseparameters, you can configure TrueSight OM - Hardware to automatically acknowledge an alerton the Error Count parameters and reset it to zero after a certain period of time.

To automatically reset the Error Count Parameters:1. Configure the Monitor Settings.

2. In the Global Alert Settings section, click Auto Reset.

Automatically Resetting Error Count Parameters

3. From the Error Count Parameters list, select the period of time after which you want thesolution to automatically reset the Error Count parameters.




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Enabling/Disabling the Missing Device DetectionEnabled by default, the missing device detection mechanism alerts operators when a device thatwas previously detected in the system is no longer found. If a device is no longer discovered, itsPresent attribute goes into alarm.

This mechanism is very useful when, for example, a non-redundant physical disk does not restartduring a system reboot and is therefore no longer seen by the operating system and themonitoring software.

The missing device detection feature does not apply to logical disks, voltages, temperature sensors, LEDs,and LUNs.

To disable the missing device detection:1. Configure the Monitor Settings.

2. In the Global Alert Settings section, click Missing Device Detection.

Missing Device Detection

2. Disable Missing Device Detection:

Check this box if you no longer want to be alerted when a device goes missing.Deactivating this feature when some missing devices have already been detected willtrigger a removal of these devices from the monitoring environment.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

3. Remove missing devices: if the "Disable Missing Device Detection" box is unchecked, specifywhen the missing devices should be deleted:

After the number of hours specified below: devices will be removed when the specifiedtime is reached. Enter the desired time in the text field (default: 72).

Never: devices will continue to appear in the console even when they are detected asmissing.

Immediately: devices will be removed from the console as soon as they are detected asmissing. An alert will however be triggered before deletion.

The history of devices that have been removed will be lost.




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring the Unknown StatusTrueSight OM - Hardware returns an Unknown Status when it is unable to detect the status of amonitored 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, youneed to tell TrueSight OM - Hardware how you want the Unknown Status to be interpreted byusing the Unknown Status setting.

To configure the Unknown Status:1. Configure the Monitor Settings.

2. In the Global Alert Settings section, click Unknown Status.

Configuring the Unknown Status

3. From the drop-down list, select:

Nothing to not 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

4. Click Close to save your settings.5. In the Add Monitor Types dialog box, click Add.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring Global Advanced SettingsConfiguring Global Advanced Settings consists in:

indicating the credentials to be used to perform local commands.

specifying the discovery and polling intervals.

enabling the debug mode.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring Local CommandsTo collect hardware information about the localhost where the PATROL Agent is installed, youmay have to specify the credentials that will be used by TrueSight OM - Hardware to run therequired commands.

To specify these credentials:1. Configure the Monitor Settings.

2. In the Global Advanced Settings section, click Local Commands.

Configuring the Local Commands

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 toexecute external commands as "root”

Enter the Sudo Command Line to execute




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Configuring IntervalsTrueSight Operations Management - Hardware periodically performs discoveries to detect newcomponents in your monitored environment. By default, the solution runs a discovery everyhour, but you can customize this interval to match your specific needs.

TrueSight OM - Hardware also polls the managed systems to collect hardware health data. Bydefault, the polling interval for this "data-collect" is set to every 2 minutes.

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

2. In the Global Advanced Settings section, click Intervals.

Configuring the Discovery Interval

3. Use the spin buttons to:

Enter the frequency (in minutes) of the discovery process. By default, the discoveryinterval is set to 60 minutes

Enter the interval at which the solution must poll the managed systems to collecthardware health data. By default, the polling interval is set to 2 minutes




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Enabling the Debug ModeWhen you encounter an issue and wish to report it to Sentry Software, you will be asked toenable the Debug 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 Settings section, click Debug.

Enabling the Debug 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 or $PATROL_HOME/log folder.

4. In the Debug End Time field, 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 End Timemust be properly set to a date and time in the future.




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Scheduling Automatic ReportsTrueSight Operations Management - Hardware can automatically produce text reports about themonitored systems.

To schedule automatic reports


2. In the Reporting section, click Schedule.

Scheduling automatic reports

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 besaved as MS_HW_energyUsage*.csv in the %PATROL_HOME%\log or $PATROL_HOME/logfolder

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

Hardware Inventory report type to automatically generate a Hardware Inventory reportthat will be saved as MS_HW_hardwareInventory*.csv in the %PATROL_HOME%\log or$PATROL_HOME/log folder



Updating a policy that sets the scheduling options of a report purges the report conf iguration variablesand stops the report process.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

The history retention period can be set using a conf iguration variable. The default collection (retention)period is one day. Whenever a stored parameter value exceeds its retention period, it is automaticallydeleted from the parameter history f ile. Refer to BMC documentation for details.

Troubleshooting the MonitoringSolution

61

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

If you encounter issues while using TrueSight OM - Hardware, please complete the followingsteps:

1. Verify if a patch has been published on the Sentry Software Website that could solve yourissue. If a patch exists, please download the patch and follow the installation procedure.

2. Search Sentry Software’s knowledge base for solutions for this specific issue.

3. Verify that you are not experiencing connectivity issues.

If none of the above resolves the issue, please contact Customer Support for assistance. Beforecontacting our Customer Support, make sure that you have the latest Debug log available.

http://www.sentrysoftware.com/Support/Patches/index.asp?productID=mshw

http://www.sentrysoftware.com/kb/index.asp

http://sentrysoftware.com/Support/register_Case.asp

62

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Getting Additional ProductInformationWhen TrueSight OM - Hardware starts or after a reinitialization, a report providing the followinginformation is automatically generated:

Product information (version, build number, release date and release type)

Product KM list, including version number

Product PSL Libraries, including file date and size

Product Binaries, including file date and size

Connectors, including version number and build date

These information may become very convenient when you encounter an issue and need toprovide detailed information on your TrueSight OM - Hardware configuration to the SentrySoftware support team.

Example of a Product Information Report forWindows

Example of a Product Information Report for Linux

By default, only the latest generated report is stored in %PATROL_HOME%\log\ and namedMS_HW_product_information_<PATROL Agent port number>.log.

63 Getting Additional Product Information

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Troubleshooting Connectivity IssuesTrueSight Operations Management - Hardware leverages specific instrumentation agents orsystem management tools to collect hardware information. Because some connectivity issuesmay exist and cause TrueSight Operations Management - Hardware to fail, it is highlyrecommended to test the connection to the specific agent before contacting the Sentry SupportTeam.

To troubleshoot connectivity issues:1. Download the connection tool required from the Sentry Software Web site. Please note that

the connection tool requires Java v1.6 or higher.

A Java security restriction, introduced in versions higher than 1.6, prevents connections to web serversif the RSA key size is less than 1024 bits. The VCenter RSA key size being 512 bits, the VMwareconnection tool will not work with a version higher than 1.6 unless you modify the java.security filestored in %JAVA_HOME%\jre1.7.0_51\lib\security\java.security by either commenting the line

jdk.certpath.disabledAlgorithms=MD2, RSA keySize < 1024 or changing its value to 512.

2. Run the command java -jar <Troubleshooting_Tool_Name.jar> to launch the connection tool.

3. Enter the information required to connect to the system and click Test Connection.

4. Wait for the test to complete. If a connectivity issue is detected, an error message willappear. In this case, the issue encountered does not concern TrueSight OperationsManagement - Hardware. Check your configuration to diagnose the source of the issue.

5. Click Save As to export the connection test results into a txt file. You can then send thisinformation to the Sentry Support Team.

http://www.sentrysoftware.com/support/troubleshooting-tools.asp

64Troubleshooting Connectivity Issues

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Reference Guide

67 Monitor Types and Attributes

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Monitor Types and AttributesIntroduction

This chapter lists all the monitor types and attributes provided by TrueSight OperationsManagement - Hardware to monitor your systems.

Please note that depending on the type of managed systems, some attributes may not beavailable.

Monitor Types

Hardware Battery

Hardware Blade

Hardware Capacity Report

Hardware CPU Core

Hardware Disk Controller

Hardware Disk Enclosure

Hardware Enclosure

Hardware Fan

Hardware LED

Hardware Logical Disk

Hardware LUN

Hardware Memory Module

Hardware Network Interface

Hardware Other Device

Hardware Physical Disk

Hardware Power Supply

Hardware Processor

Hardware Robotics

TrueSight OM - Hardware Connector

Hardware Tape Drive

Hardware Temperature

Hardware Voltage

68Monitor Types and Attributes

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Baselines and Key Performance Indicators

Some attributes are identified by default as Key Performance Indicators (KPIs) and thereforeautomatically included in the base lining calculation. To learn more about auto baselining andKPIs, 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 calculationprocess are respectively identified by the following icon: KPI


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware BatteryAttributes

Attribute Description Unit Default AlertThresholds

Type

Charge* Percentage of the battery charge. Percentage (%)

Warning ≤50Alarm ≤ 30

Statistics

Present When the battery is no longerdiscovered, the attribute goes intoalarm.

{0 =Missing; 1 =Present}

0 = Alarm Availability

Status* Battery Status. {0 = OK;1 =Degraded; 2 =Failed}

1 = Warning2 = Alarm

Availability

* These attributes are used by default when visualizing the corresponding monitor instance in TrueSight OM.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware BladeAttributes


Type

Power State Indicates whether the blade is currentlyon or off

{0 = Off; 2 =On}

None Availability

Present When the blade is no longerdiscovered, the attribute goes intoalarm.



Status* Blade Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

* This attribute is used by default when visualizing the corresponding monitor instance in TrueSight OM.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Capacity ReportAttributes


Type

CPU Count Host total number of physicalprocessors (CPU).

CPUs None Statistics

Connected Ports Number of connected ports. ports None Statistics

Degrees Below Warning* Number of degrees before reaching theclosest warning threshold.

degreesCelsius

None Statistics

Logical Disk Size Host total logical disk size. Gigabytes (GB)

None Statistics

Memory Size Host total memory (RAM). Gigabytes (GB)

None Statistics

Physical Disk Size Host total physical disk size. Gigabytes (GB)

None Statistics

Power Consumption* Power consumed by the host. Watts None Statistics

Unallocated Disk Space Host total available disk space that isnot allocated to any volume.

Gigabytes (GB)

None Statistics


For detailed information about KPI, see Managing Baselines and Key Performance Indicators.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware CPU CoreAttributes


Type

Current Speed Current speed of the CPU core inmegahertz.

Megahertz(MHz)

None Statistics

Present When the CPU Core is no longerdiscovered, the attribute goes intoalarm.



Status* CPU Core Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Used Time Percent Percentage of the CPU Core usage.The "Used Time Percent" attribute iscalculated as: (UsedTime -LastUsedTime) / (currentTime -lastTime) *100

Percentage (%)

None Statistics



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Disk ControllerAttributes


Type

Battery Status* This attribute triggers an alert topredict that the disk controller batterywill be unable to support the controllerin the event of a power failure.

{0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Controller Status* This attribute displays the status of thedisk controller.


1 =Warning2 = Alarm

Availability

Present When the disk controller is no longerdiscovered, the attribute goes intoalarm.




Depending on your system, all attributes may not be used. Only one of the attributes may be visible. Thiswill not af fect the proper monitoring of the device.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Disk EnclosureAttributes


Type

Intrusion Status This attribute will trigger an alarm ifthe enclosure is open or not properlyclosed.

{0 = OK;2 =IntrusionDetected}

1 =Warning2 = Alarm

Availability

Present When the disk enclosure is no longerdiscovered, the attribute goes intoalarm.



Status* Enclosure Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware EnclosureAttributes


Type

Intrusion Status This attribute will trigger an alarm ifthe enclosure is open or not properlyclosed.

{0 = OK;2 =IntrusionDetected}


Power Consumption* This attribute reports the electricityconsumption.

Watts None Statistics

Present Availability of the enclosure. An alert istriggered when the enclosure is nolonger discovered.



Status Enclosure Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware FanAttributes


Type

Present When the fan is no longer discovered, the attribute goes into alarm.



Speed* Speed of the corresponding fan (inrevolutions/minute). An alert istriggered if the fan speed is too low forproper functioning.

Revolutionsperminute(RPM)

Automatic

Automaticthresholdsset byTrueSightOM -Hardwareshould notbecustomizedor modified.

Statistics

Speed Percent Speed of the corresponding fan inpercentage of its maximal speed.

% ofmaximumspeed

Automatic


Statistics

Status* Current status of the fan. An alert istriggered if the fan stops spinning ordoes not spin fast enough.



Availability




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware LEDAttributes


Type

Color State of the LED depending on its color. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Status* LED Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning 2 = Alarm

Availability


Hardware Logical DiskAttributes


Type

Error Count Number of errors encountered by thelogical disk.

Errors None Statistics

Status* Logical Disk status. {0 = OK;1 =Degraded; 2 =Failed}


Availability

Unallocated Space Amount of unused disk space in thelogical disk (i.e. not allocated to thehigher layer or the operating system).

Gigabytes (GB)

None Statistics




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware LUNAttributes


Type

Available Path Count* Number of distinct paths available tothe remote volume.

Paths Warningwhendowngrades or fewerthanexpected.Alarm when0

Statistics

Status* Availability of the remote volume. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Memory ModuleAttributes


Type

Error Count Number of detected (and possibly,corrected) errors.

Errors 1 = Warning Statistics

Error Status This attribute will trigger an alert if thenumber of memory errors reaches athreshold set by the manufacturer’sagent.

{0 = NoErrors; 1 =DetectedErrors; 2 =Too ManyErrors}


Availability

PredictedFailure

This attribute will trigger a warning ifa memory failure is predicted tohappen.

{0 = OK; 1 =FailurePredicted}


Present When the memory module is no longerdiscovered, the attribute goes intoalarm.

{0 =Missing; 1= Present}


Status* Memory Status. {0 = OK; 1 =Degraded;2 = Failed}


Availability



Hardware Network InterfaceAttributes


Type

Bandwidth Utilization Percentage used of the availablebandwidth. This parameter is ONLYcollected if Link Speed, Duplex Mode,Received Bytes Rate and TransmittedBytes Rate are all properly collected

Percentage (%)

Automatic Statistics


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


Type

Duplex Mode Whether the port is configured tooperate in half-duplex or full-duplexmode.

{0 =Half-duplex;1 = Fullduplex}

Automatic Availability

Error Percent Transmitted and received packets inerror as a percentage of all processedpackets.

A warning is raised when thispercentage goes above 10% and analarm when above 30%.

A high percentage of errors oftenmeans that the network link isimproperly configured or that thenetwork card is behaving badly andthus needs to be replaced.

Percentage (%)

≥ 10% =Warning

≥ 30% =Alarm

Statistics

Link Speed Negotiated or configured link speed. Megabits perseconds(Mbits/s)


Link Status This attribute will trigger a warning ifthe network interface is not connected(i.e. no wire plugged-in).

{0 =Plugged; 1 =Unplugged}


Present When the network adapters are nolonger discovered, the attribute goesinto alarm.



Received Bytes Rate* Received network traffic in megabytesper second.

Megabytes perseconds (MB/s)

None Statistics

Received Packets Rate Received network traffic in packets persecond.

Packetspersecond

None Statistics

Status Network interface Status. {0 = OK;1 =Degraded; 2 =Failed}


Availability


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


Type

Transmitted Bytes Rate* Emitted network traffic in megabytesper second.

Megabytes perseconds (MB/s)

None Statistics

Transmitted Packets Rate Emitted network traffic in packets persecond.

Packetspersecond(packets/s)

None Statistics

Zero Buffer Credit Percent Percentage of zero buffer credits thatoccurred over the last polling interval.

Percentage (%)

None Statistics



Hardware Other DeviceAttributes


Type

Present When the device is no longer discovered,the attribute goes into alarm



Status* Device Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Usage Count Number of times the device has been used. Times Automatic Statistics

Value Device value. n/a Automatic Statistics



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Physical DiskAttributes


Type

Device Not Ready ErrorCount

Number of not ready device errors thatthe disk has encountered since the lastreinitialization, or since the lastmanual reset.

Errors Alarm ≥ 1 Statistics

Error Count Number of errors that the disk hasencountered since the lastreinitialization, or since the lastmanual reset.

Errors Automatic Statistics

Hard Error Count Number of hard errors that the disk hasencountered since the lastreinitialization, or since the lastmanual reset.


Illegal Request ErrorCount

Number of illegal request errors thatthe disk has encountered since the lastreinitialization, or since the lastmanual reset.


Media Error Count Number of media errors that the diskhas encountered since the lastreinitialization, or since the lastmanual reset.


No Device Error Count Number of no device errors that thedisk has encountered since the lastreinitialization, or since the lastmanual reset.


Predicted Failure Informs if a failure is predicted. {0 = OK;1 =FailurePredicted}


Present When the physical disk is no longerdiscovered, the attribute goes intoalarm



Recoverable Error Count Number of recoverable errors that thedisk has encountered since the lastreinitialization, or since the lastmanual reset.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


Type

Status* Physical Disk status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Transport Error Count Number of transport errors that thedisk has encountered since the lastreinitialization, or since the lastmanual reset.





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Power SupplyAttributes


Type

Present When the power supply is no longerdiscovered, the attribute goes intoalarm



Status* Power Supply status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Used Capacity Percentage of the Power Supply powercurrently in use if available.

Percentage (%)





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware ProcessorAttributes


Type

Corrected Error Count Number of detected and correctederrors.


Current Speed CPU speed. Megahertz(MHz)

None Statistics

Predicted Failure This attribute will trigger a warning if aCPU failure is predicted to happen.

{0 = OK;1 =FailurePredicted}

1 =Warning

Availability

Present When the physical processor is nolonger discovered, the attribute goesinto alarm



Status* CPU Status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware RoboticsAttributes


Type

Error Count* Number of moves in failure. Errors Automatic Statistics

Move Count Number of moves performed by therobot.

Moves None Statistics

Present When the robotics is no longerdiscovered, the attribute goes intoalarm



Status* Device Status {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

TrueSight OM - Hardware ConnectorAttributes


Type

Status* Connector Status. {0 = OK;1 =Degraded; 2 =Failed}


CollectionStatus



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware Tape DriveAttributes


Type

Error Count Number of tape drive failures. Errors Automatic Statistics

Mount Count Number of mount operations thathappened during the last collectinterval. The attribute remains to zerowhen no mount operation occurs.

Mounts None Statistics

Needs Cleaning* Indicates whether the tape drive needscleaning.

{0 = OK;1 =CleaningNeeded;2 =CleaningNeededImmediately}

1 =Warning2 = Alarm

Statistics

Present When the tape drive is no longerdiscovered, the attribute goes intoalarm.



Status* Device status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Unmount Count Number of unmount operations thathappened during the last collectinterval. The attribute remains to zerowhen no unmount operation occurs.

Unmounts

None Statistics



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware TemperatureAttributes


Type

Status Temperature status. {0 = OK;1 =Degraded; 2 =Failed}

1 =Warning2 = Alarm

Availability

Temperature* Temperature reading. DegreesCelsius

(C°)

Automatic


Statistics


For detailed information about KPI, see Managing Baselines and Key Performance Indicators.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Hardware VoltageAttributes


Type

Status Current status of the voltage. An alert istriggered if the voltage output is too lowfor proper functioning.


1 =Warning2 = Alarm

Availability

Voltage* Voltage output in millivolts (mV). Analert is triggered if the voltage goes outof the proper range.

Millivolt (mV)





True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Global Configuration VariablesThis section lists the configuration variables used by TrueSight Operations Management -Hardware globally, i.e that apply to all of the monitored hosts. These configuration variables arestored under /SENTRY/HARDWARE in the PATROL Agent’s configuration and can be managedthrough the Configuration Variables pane.

To manage configuration variables: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 Configuration Variables tab.

4. Click Add to define Configuration Variables. The Add Configuration Variable pane isdisplayed.

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

Variables Description

automaticReinitialization If set to 1, triggers a re-initialization of TrueSight OM - Hardware. Thediscovery checks this variable every minute and deletes it beforeperforming the re-initialization.

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

collectionHubHeapSizeMin Minimum heap size in megabytes allocated to Java Collection Hub.Default: Not set (assumed 128 MB).

collectionHubOverrideJavaCommandLine

Command line used by TrueSight OM - Hardware to launch the JavaCollection Hub. This variable should only be set if instructed bySentry Support.

collectTimeout Maximum time in seconds the collectors wait for the previouscollection to complete. When this timeout is reached, it means theprevious collection did not complete in a timely fashion.Default: Not set (assumed 300 seconds).

92Global Advanced Additional ConfigurationVariables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


currentVersion Indicates the version level of the configuration. This should alwaysmatch with the version of TrueSight OM - Hardware. TrueSight OM -Hardware uses this variable to perform migration operations on theconfiguration variables. The variable is automatically set during itsinitialization.

deactivatedDeviceClassList List of monitor types that are deactivated, for which no discovery andno collection will be performed. Use this variable to completelydisable the monitoring of a specific type of objects.

defaultCommandTimeout Timeout in seconds used when TrueSight OM - Hardware executes anOS Command. Default: 30. Unit: seconds

dirCommand OS Command used to list the files in a directory. This command isused 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 TrueSight OM - Hardware from performing anSNMP dump of the monitored systems in debug mode.Default: Not set.

disableForcedDefaultAccount When set to 1, prevents TrueSight OM - Hardware from explicitlyusing the /AgentSetup/defaultAccount credentials when runningexternal commands.Default: Not set.

disableI2D If set to 1, no MetaTokenID and no MetaFQDN information will be setin the PATROL namespace for any host.

disableJRECheck When set to 1, disables the validation tests of the JRE used byTrueSight OM - Hardware to run Java code. This can be used to forceTrueSight OM - Hardware to use a non-Sun or non-Oracle JRE.

disableMissingDeviceDetection When set to ‘1’, disables the missing device detection mechanism ofTrueSight OM - Hardware. By default, TrueSight OM - Hardware raisesan alarm for devices that were discovered and that are no longerdiscovered.Default: Not set

disablePslExecuteBugWorkaround When set to ‘1’, deactivates the workaround for a bug in thePslExecute() PSL function. If TrueSight OM - Hardware detects that the version of the PATROLAgent is affected by the PslExecute() bug, it uses an alternatetechnique to create asynchronous threads with the event_trigger()function and the RemPsl standard event. ThedisablePslExecuteBugWorkaround variable disables thisworkaround.

findWbemNamespaceTimeout Number of seconds after which a TrueSight OM - Hardware stopstrying to get a server namespace via WBEM.Default value: 1200.

93 Global Advanced Additional ConfigurationVariables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


forceClassicConfigMode When set to 1, TrueSight OM - Hardware switches to Classic Mode,which means that it can only be operated from a PATROL Console. Allthe configured policies will then be ignored. Default: 0.

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

globalDiscoveryTimeout Maximum time in seconds the main discovery process waits for theprevious discovery to complete. When this timeout is reached, itmeans the previous discovery 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 discoveryprocesses wait for the previous discovery to complete. When thistimeout is reached, it means the previous discovery did not completein a timely fashion.Default: Not set (assumed 300 seconds).

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 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 Solarissystems. This can be used if TrueSight OM - Hardware cannot find thelocation of the ipmitool utility automatically.Default: Not set.

javaPassword Password associated to the javaUsername variable. Default: Not set(TrueSight OM - Hardware will search for a suitable JREautomatically).

javaPath Path to the folder containing the Java executable used by theCollection Hub.

javaUsername Username used to launch the Java Collection Hub.Default: Not set.

maxConcurrentCollectThreadsPerHost

Maximum number of collect threads that can run concurrently foreach monitored host.Default: 15.

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:


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


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.

pemMessages How much internal information should be sent as PATROL events.When set to ‘all’, all internal TrueSight Operations Management - Hardwaremessages (problems and informational messages).

When set to ‘problems’, only errors and problems.

When set to ‘nothing’, no internal message at all.

Note: This doesn’t affect the reporting of actual hardware problems.

Default: all.

remoteCommandMaxConnectionsPerHost

Maximum number of Telnet or SSH sessions opened at once for asingle 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).

removeAllThresholds When set to ‘1’, deletes all thresholds from the configuration at thenext discovery (every hour by default).Note: Default thresholds will then be re-added (except if the"ThresholdsManagementMode" variable is set to "none").

removeMissingDevices Number of seconds after which the missing device should beremoved. An empty value means the device will never be deleted. A '0'value means the device will be deleted right away.Default: empty

snmpTimeout Timeout in seconds when performing SNMP queries. Only applicablewhen forced SNMP serialization has been enabled (/SENTRY/HARDWARE/forceSnmpSerialization)Default: 60 seconds.

snmpWalkMaxItems Maximum number of variables that can be processed by a singleSNMP 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.


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


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

startupDelay Allows the administrator to specify the number of seconds thatTrueSight OM - Hardware will wait before starting its platformdetection and discovery. This variable may be useful on fast bootingcomputers where the PATROL Agent starts before other importantinstrumentation 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 configured in the KM)Note: If the PATROL Agent version is 3.6.011 or later the connectionmethod used by TrueSight OM - Hardware is 'sopen'; otherwise it isleft blank.Default (UNIX): Telnet.

ThresholdsManagementMode Specifies how TrueSight OM - Hardware should manage the alertthresholds on attributes. Possible values:

‘as’ (through PATROL for Event Management)

‘tuning’ (through the standard "Override attribute" mechanism)

‘none’ (No threshold is set by TrueSight OM - Hardware)

Default: ‘Tuning’.

trimFromDisplayName Lists all characters that will be removed from object display names.Example: :(-_Default: "," (comma)

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 TrueSight OM - Hardware use short displayname for the icons in the PATROL Consoles. This can be useful forUNIX PATROL Classic Consoles but this flags affects every consoleconnected to the agent.Default: Not set.

wbemTimeout Timeout in seconds for a WBEM query to complete.Default: Not set (assumed 60 seconds).


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


wmiScriptPath Path to the script used to perform WMI queries on Windows. Default: Not set (use the default WMI client provided with the KM).

5. Click Add to List .

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




True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Device Additional ConfigurationVariablesThe following table contains the list of the device additional configuration variables which canbe added in the Device Advanced Settings section when configuring monitor settings. Thesevariables will be applied to a single supervised host or device.

These configuration variables are stored under /SENTRY/HARDWARE/<hostID> in the PATROLAgent’s configuration.

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


defaultWattage Assumed power consumption in Watts of the monitored server. This valuewill be used instead of the measured or estimated value. Use this variableto override a Power Consumption attribute value that seems unlikely.

forceWmiNamespace Forces the use of a specific WMI namespace instead of letting TrueSightOM - Hardware decide the suitable namespace.Default: Not set

ipmitoolCommand To override the command line used by TrueSight OM - Hardware toperform IPMI requests on Linux and Solaris systems. The specifiedcommand needs to provide the exact command to be executed with thefollowing 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 (TrueSight OM - Hardware will find the suitable ipmitoolcommand to run automatically).

networkLinkAlarmType Type of alert for the Link Status attribute of the TrueSight OM - HardwareNetwork monitor type. Possible values are:

OK

WARN

ALARM

Default: Not set (assumed WARN)

networkLinkDuplexAlarmType Type of alert for the Duplex Mode attribute of the TrueSight OM -Hardware Network monitor type. Possible values are:

OK

98Device Additional Configuration Variables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


WARN

ALARM

Default: Not set (assumed WARN).

networkLinkDuplexSetting Indicates when TrueSight OM - Hardware needs to trigger an alert on theDuplex Mode attribute of the TrueSight OM - Hardware Network monitortype:

NEVER (will never trigger an alert on Duplex Mode)

DEFAULT (will trigger an alert only when Link Status downgrades from Plugged toUnplugged)

ALWAYS (will trigger an alert for all interfaces that are unplugged)

Default: Not set (assumed DEFAULT).

networkLinkSetting Indicates when TrueSight OM - Hardware needs to trigger an alert on theLink Status attribute of the TrueSight OM - Hardware Network monitortype:

NEVER (will never trigger an alert on LinkStatus)

DEFAULT (will trigger an alert only when a full-duplex running adapter downgrades tohalf-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 TrueSight OM -Hardware Network monitor type. Possible values are:

OK

WARN

ALARM

Default: Not set (assumed WARN).

networkLinkSpeedMinimum Minimum accepted Link Speed value when networkLinkSpeedSetting isconfigured to “ALWAYS”.

networkLinkSpeedSetting Indicates when TrueSight OM - Hardware needs to trigger an alert on theLink Speed attribute of the TrueSight OM - Hardware 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 speedto a slower speed)

ALWAYS (will trigger an alert for all interfaces that are slower than the valueindicated by the networkLinkSpeedMinimum configuration variable)


rediscoverHosts Forces a discovery for each specified host. Hosts must be identified withtheir PATROL IDs and separated by commas.Default: Not set.Note: this variable deletes the list of current devices (including the missingones) for the provided hosts, removes the host instances and triggers adiscovery. If the automaticReinitialization conf iguration variable is set to '1',the rediscoverHosts variable will be ignored and removed from theconf iguration.

99 Device Additional Configuration Variables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60


wmiUsePatrolDefaultAccount When set to 1, tells TrueSight OM - Hardware to use the security token ofthe PATROL Agent’s default account to connect to remote systems withWMI when the wmiUsername variable is empty.Default: Not set (assumed 0, where TrueSight OM - Hardware does notperform any WMI query if wmiUsername is empty).

100Device Additional Configuration Variables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Managing Baselines and KeyPerformance IndicatorsTo detect abnormalities on the monitored environment, BMC TrueSight Operations Managementcalculates baselines per attribute based on values collected over a specified period of time todetermine a normal operating range. When the collected values for these parameters are out ofrange, an alert is triggered. Some attributes are identified by default as Key PerformanceIndicators (identified with the icon) and automatically included in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for an attribute of a monitor. There are twobaselines: Baseline High and Baseline Low. Baseline High represents the point at which 95% ofthe weighted average of the historical values fall below this value for the selected time period; Baseline Low represents the point at which 90% of the weighted average of historical values forthe selected time period fall above this line.

Baselines are generated for KPI attributes that have an active abnormality thresholds.

Managing Key Performance Indicators

Starting from v9.5 of BPPM, attributes that have not been initially designated in the KM as KeyPerformance Indicators (KPIs) cannot be flagged as KPIs from BPPM/TrueSight. Althoughenabling baseline is possible through the Options > Administration > Intelligent EventThresholds feature available in the Infrastructure Management Server operator console, BMCdoes not recommend doing it.

For more information, refer to the BMC TrueSight Operations Management documentation available f romdocs.bmc.com.

https://docs.bmc.com/docs/dashboard.action

101 Managing Baselines and Key PerformanceIndicators

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Troubleshooting ConnectivityIssues

103

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

TrueSight OM - Hardware leverages different instrumentation layers to collect hardwareinformation. Because some connectivity issues may exist and cause TrueSight OM - Hardware tofail, it is highly recommended to test the connection to this instrumentation layer beforecontacting the Sentry Support Team.

To troubleshoot connectivity issues:

1. Download the connection tool required from the Sentry Software Website (Downloadssection of your product). Please note that the connection tool requires Java v1.6 or higher.

2. Run the command java -jar VMWare-Connection-Tool_V1.0.00.jar to launch the connectiontool.

3. Enter the information required to connect to the system and click Test Connection.

4. Wait for the test to complete. If a connectivity issue is detected, an error message willappear. In this case, the issue encountered has nothing to do with TrueSight OM - Hardware.Check your configuration to diagnose the source of the issue.

5. Click Save As to export the connection test results into a txt file. You can then send thisinformation to the Sentry Support Team.

http://www.sentrysoftware.com/support/troubleshooting-tools.asp

105

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Index

- A -Add Monitor Types 33

additional variables 54

Agent 22

Alert Actions 47

Alert Delay 49

Attributes 67

Available Path Count 78

Bandwidth Utilization 79

Battery Status 73

Charge 69

Color 77

Connected Ports 71

Controller Status 73

Corrected Error Count 85

CPU Count 71

Current Speed 72, 85

Degrees Below Warning 71

Device Not Ready Error Count 82

Duplex Mode 79

Error Count 77, 79, 82, 86, 88

Error Percent 79

Error Status 79

Hard Error Count 82

Illegal Request Error Count 82

Intrusion Status 74, 75

Link Speed 79

Link Status 79

Logical Disk Size 71

Media Error Count 82

Memory Size 71

Mount Count 88

Move Count 86

Needs Cleaning 88

No Device Error Count 82

Physical Disk Size 71

Power Consumption 71, 75

Power State 70, 71

Predicted Failure 79, 82, 85

Present 69, 70, 71, 72, 74, 75, 76, 79, 81,84, 86, 88

Received Byte Rate 79

Received Packets Rate 79

Recoverable Error Count 82

Speed 76, 85

Speed Percent 76

Status 69, 70, 71, 72, 74, 75, 76, 77, 78,79, 81, 82, 84, 85, 86, 87, 88, 89, 90

Technology 82

Temperature 89

Test Report 87

Transmitted Byte Rate 79

Transmitted Packet Rate 79

Transport Error Count 82

Unallocated Disk Space 71

Unallocated Space 77

Unmount Count 88

Usage Count 81

Used Capacity 84

Used Time Percent 72

Value 81

Voltage 90

Zero Buffer Credit Percent 79Authentication password 36

Authentication Protocol 36

Auto Reset 50

Automatic Reporting 58

- B -Baselines 100

BMC

BMC Software Installation Utility 22

- C -Changes 7

Cisco

Cisco Ethernet Switches 17

Cisco UCS B-Series, C-Series 17

Cisco UCS Interconnect Chassis 17Cisco Fabric Interconnect Switch 44

Cisco UCS 33

Cisco UCS Blade Chassis 44

Cisco UCS Manager 44

Component 22

Component Installation package

creating 29

downloading 30Components 14

106

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

configuration variables 33

Configuration Variables (Advanced)

automaticReinitialization 91

collectionHubHeapSizeMax 91

collectionHubHeapSizeMin 91

collectionHubOverrideJavaCommandLine 91

collectTimeout 91

currentVersion 91

deactivatedDeviceClassList 91

defaultCommandTimeout 91

dirCommand 91

disableDebugSNMPWalk 91

disableForcedDefaultAccount 91

disableI2D 91

disableJRECheck 91

disableMissingDeviceDetection 91

disablePslExecuteBugWorkaround 91

findWbemNamespaceTimeout 91

forceClassicConfigMode 91

forceSnmpSerialization 91

globalDiscoveryTimeout 91

hdfPath 91

individualDiscoveriesTimeout 91

intrusionDetectionAlert 91

ipmiTimeout 91

ipmitoolPath 91

javaPassword 91

javaPath 91

javaUsername 91

maxConcurrentCollectThreadsPerHost 91

maxConcurrentDiscoveryThreads 91

noMissingDeviceDetectionClasses 91

pathToAWK 91

pathToAWKUnix 91

pathToAWKWindows 91

pausedObjectList 91

pemMessages 91

remoteCommandMaxConnectionsPerHost 91

remoteCommandTimeout 91

removeAllThresholds 91

removeMissingDevices 91

snmpTimeout 91

snmpWalkMaxItems 91

sshClientJarPath 91

sshCommandJarPath 91

startupDelay 91

tableJoinTimeout 91

telnetClientJarPath 91

telnetCommandJarPath 91

telnetConnectionMethod 91

ThresholdsManagementMode 91

trimFromDisplayName 91

ucsJarPath 91

ucsTimeout 91

ucsVbsPath 91

UNIXConsoleMode 91

wbemTimeout 91

wmiScriptPath 91Configuration variables (Device)

defaultWattage 97

forceWmiNamespace 97

ipmitoolCommand 97

networkLinkAlarmType 97

networkLinkDuplexAlarmType 97

networkLinkDuplexSetting 97

networkLinkSetting 97

networkLinkSpeedAlarmType 97

networkLinkSpeedMinimum 97

networkLinkSpeedSetting 97

rediscoverHosts 97

wmiUsePatrolDefaultAccount 97Configuring

discovery interval 56

Local Commands 55

monitor settings 33Connectivity

Issues 103Connector 7, 33

Connector Status Parameters 49

Console Server 22

Context name 36

- D -Debug 57

Debug Mode 54

enabling 57Dell

Dell EquaLogic PS Series 17

Dell Modular Chassis (blades) 17

Dell OpenManage Server Administrator 17

Dell PowerEdge 17Detection

Missing Device 51Device

Detection 51

107

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Device

Missing 51Device Advanced Settings 33

Device Information 33

Disable

Missing Device Detection 51discovery and polling intervals 54

Discovery Interval

configuring 56Discrete parameters 49

Downloading 30

- E -EMC

EMC Clariion 17

EMC SMI-S Provider (ECOM) 17

EMC Symmetrix 17

EMC Symmetrix V-Max 17Emulex

Emulex HBA 17Error Count 46, 50

ErrorCount 50

- F -Features 13

Files

Mshw_ntx86_1300.exe 22

Mshw_unix_1300.tar 22

mshw_unix_1400.tar 22

mshw_WINDOWS_1400.exe 22Fujitsu

Fujitsu Eternus 17

Fujitsu-Siemens BX Blade Chassis 17

Fujitsu-Siemens PRIMERGY 17

Fujitsu-Siemens Serverview 17

- G -Global Advanced Settings 54

Global Alert Settings 46

Goals 13

- H -Hardware 22

Hardware Sentry 22

Installation 22

Migrate 22

Upgrade 22Hitachi

Hitachi AMS 17

Hitachi BladeSymphony 17

Hitachi Device Manager 17

Hitachi HNAS 17

Hitachi USP-V 17HP

HP 9000 17

HP AlphaServer 17

HP c-Class BladeSystem 17

HP CommandView EVA 17

HP CommandView XP (or Hitachi DeviceManager) 17

HP Insight Management Agent 17

HP Integrity 17

HP NetServer 17

HP p-Class BladeSystem 17

HP ProLiant 17

HP StorageWorks EVA 17

HP StorageWorks XP 17

HP SuperDome (Itanium) 17

HP SuperDome (PA-RISC) 17Huawei

Huawei Servers 17

Huawei Storage Systems (OceanStor) 17

- I -IBM

IBM 3584 Tape Library 17

IBM BladeCenter 17

IBM DataPower 17

IBM Director Agent 17

IBM DS 3000, 4000, 5000 Series 17

IBM DS 6000, 8000 Series 17

IBM DS Storage Manager (SMcli) 17

IBM pSeries, IBM eServer p5, p6 17

IBM Storwize V7000 17

IBM Storwize V7000 CIM Agent 17

IBM SVC 17

IBM SVC CIM Agent 17

IBM VIO Server 17

IBM XiV 17

IBM XIV Storage System SMI-S Agent 17

108

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

IBM

IBM XIV Storage System SMI-S AgentIBMStorwize V7000 CIM Agent 17

IBM xSeries, IBM Netfinity 17Importing the Monitoring Solution 28

Improvement 7

Install / Un-install

Hardware Sentry 22

Packages 22

Upgrade 22Installing 30

Installing the Monitoring Solution 27

IPMI-Over-LAN 45

Issues

Connectivity 103

Fixed 7

Troubleshooting 103

- K -Key Performance Indicators 100

KPI 100

- L -Lenovo

Lenovo IMM - SNMP 17Local Commands 54

configuring 55Localhost Sudo 55

- M -McData SAN Switch 17

Migrate

Hardware Sentry 22Monitor Settings

configuring 33Monitor Types 67

Hardware Battery 69

Hardware Blade 70

Hardware Capacity Report 71

Hardware CPU Core 72

Hardware Disk Controller 73

Hardware Disk Enclosure 74, 75

Hardware Fan 76

Hardware LED 77

Hardware Logical Disk 77

Hardware LUN 78

Hardware Memory Module 79

Hardware Network Interface 79

Hardware Other Device 81

Hardware Physical Disk 82

Hardware Power Supply 84

Hardware Processor 85

Hardware Robotics 86

Hardware Sentry Connector 87

Hardware Tape Drive 88

Hardware Temperature 89

Hardware Voltage 90Multi-Tier 41

Multi-Tier Authentication 41

- N -NEC

NEC Express5800 17NetApp 17

New features 7

number of consecutive times 46

Numeric parameters 49

- O -OpenSSH 39

Operating Systems

HP-UX 17

Linux 17, 22

OpenVMS 17

Solaris 17

Tru64 17

UNIX 22

VMware ESX4 17

Windows 17, 22out-of-band interface 45

Overview 16

- P -Package 29, 30

PATROL

PATROL component 22Platforms

Supported 17

109

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

Port 36

Present Parameters 49

Privacy password 36

Privacy protocol 36

Product 16

Product information

Build number 62

Connectors 62

Product Binaries 62

Product KM list 62

Product PSL Libraries 62

Release date 62

Release type 62

Version 62protocol

IPMI-Over-LAN 33

SNMP 33

SSH/Telnet 33

WBEM 33

WMI 33

- Q -QLogic

QLogic HBA 17Quantum Tape Library 17

- R -Reference Guide 67

Reports

scheduling 58Requirements 17

Root Privileges 39, 55

- S -Scheduling

Reports 58SNMP

v1 36

v2c 36

v3 36SNMP Community String 36

SNMP port 36

specific action 46

Specific PATROL Event 47

SSH 39

SSH/Telnet 39

Status attribute 53

STD 41 PATROL Event 47

StorageTek

StorageTek LSeries 17

StorageTek StreamLine (SL) 17Sudo 55

Sudo Command 39

Sudo Command Line 55

Sun

Sun Advanced Lights-Out Management(ALOM) 17

Sun Blade Modular Chassis 17

Sun Fire (SPARC T1, T2) – 2009 and newerfirmware 17

Sun Fire (SPARC T1, T2) – pre-2009firmware 17

Sun Fire (SPARC) 17

Sun Fire (X64) 17

Sun Fire F12K, F15K, F20K, F25K 17

Sun Fire Mx000 17

- T -Technology

Command lines 17

HTTP 17

IPMI 17

SNMP 17

SSH 17

Telnet 17

WBEM 17

WMI 17

XML API 17Telnet 39

Thorium 22

Timeout 36

Troubleshooting 63

Connectivity Issues 103

- U -Unknown Status 46, 53

Upgrade

Hardware Sentry 22Username 36

110

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.60

- V -VMware

VMware ESX4 17

VMware ESXi 17

- W -WBEM 41

Web 22

What's new 7

Windows Management Instrumentation 43

WMI 43

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC TrueSight environment. Sentry Software alsodevelops adapters for BMC Atrium Orchestrator that enables IT administrators toautomate the execution of common requests and tasks that occur in the daily course ofIT operations. Combined with BMC’s servers and network automation tools, theadapters allow IT administrators to implement provisioning and decommissioningworkflows that cover all layers of their IT infrastructure. Finally, Sentry Software designsconnectors that bring storage capacity metrics into BMC TrueSight Capacity Optimizationto ensure IT administrators that their storage infrastructure is properly sized for theircurrent and future needs.

Like us on Facebook:facebook.com/sentrysoftware

Follow us on Twitter:

twitter.com/sentrysoftware

LEARN MORE

To learn more about our solutions, please visit :www.sentrysoftware.com/solutions

© BMC Software, Inc. All rights reserved.

ABOUT MARKETZONE DIRECT PRODUCTS

The BMC MarketZone Directprogram sells and supportsthird-party products thatcomplement and/or augment BMCsolutions. MarketZone Directproducts are available under BMClicense and support terms.

About BMC Software™BMC Software helps leading companies around the world put technology at the forefrontof business transformation, improving the delivery and consumption of digital services.From mainframe to cloud to mobile, BMC delivers innovative IT management solutionsthat have enabled more than 20,000 customers to leverage complex technology intoextraordinary business performance—increasing their agility and exceeding anythingthey previously thought possible. For more information about BMC Software, visit

www.bmc.com.

Bus ines s thrives when IT runs s marter,fas ter and s tronger. That’s why the mos tdemanding IT organizations in the worldrely on BMC Software acros s dis tributed,mainframe, virtual and cloudenvironments . Recognized as the leader inBus ines s Service Management, BMC offersa comprehens ive approach and unifiedplatform that helps IT organizations cutcos t , reduce ris k and drive bus ines sprofit . For the four fis cal quarters endedSeptember 30,2011, BMC revenue wasapproximately $2.2 billion.

BUSINESS RUNS ON I.T .

I.T . RUNS ON BMC SOFT WARE

http://facebook.com/sentrysoftware

http://twitter.com/sentrysoftware

http://twitter.com/sentrysoftware

http://facebook.com/sentrysoftware

Documents

TrueSight Operations Management - Hardware v1.9 · Configuring Monitor Settings ... Both UemCli and Navisphere ... TrueSight Operations Management - Hardware Version 1.9.60 Overview