truesight operations management - hardware sentry 1.9 · 9 truesight operations management -...

TrueSight Operations Management -Hardware

USER DOCUMENTATION

Version 1.9.50

October 2015

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

.50

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 the Web,call 800 537 1813. Outside the United States and Canada, please contact your local support centerfor assistance. To find telephone and email contact information for the BMC Software supportcenter that services your location, refer to the Contact Customer Support section of the Supportpage 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

.50

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

.50

Table of Contents.....................................................................................................................................................................................17Overview

.....................................................................................................................................................................................18Monitored Components

.....................................................................................................................................................................................20Product at a Glance

.....................................................................................................................................................................................21Platforms & Requirements

.....................................................................................................................................................................................26Solution Packages

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

.....................................................................................................................................................................................31Creating the Installation Package

.....................................................................................................................................................................................32Downloading the Installation Package

.....................................................................................................................................................................................32Installing the Package

.....................................................................................................................................................................................35Configuring Monitor Settings

.......................................................................................................................................................................................35Configuring Devices to Monitor

......................................................................................................................................................................38Using the SNMP Protocol

......................................................................................................................................................................41Using the SSH/Telnet Protocol

......................................................................................................................................................................43Using the WBEM Protocol

......................................................................................................................................................................45Using the WMI Protocol

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

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

.......................................................................................................................................................................................48Configuring Global Alert Settings

......................................................................................................................................................................49Configuring Alert Actions

......................................................................................................................................................................51Configuring Alert Delay

......................................................................................................................................................................52Automatically Resetting Error Count Parameters

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

......................................................................................................................................................................55Configuring the Unknown Status

.......................................................................................................................................................................................56Configuring Global Advanced Settings

......................................................................................................................................................................57Configuring Local Commands

......................................................................................................................................................................58Configuring Intervals

......................................................................................................................................................................59Enabling the Debug Mode

.......................................................................................................................................................................................60Scheduling Automatic Reports

.....................................................................................................................................................................................63Monitor Types and Attributes

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

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

.......................................................................................................................................................................................67Hardware Capacity Report

5

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

.......................................................................................................................................................................................68Hardware CPU Core

.......................................................................................................................................................................................69Hardware Disk Controller

.......................................................................................................................................................................................70Hardware Disk Enclosure

.......................................................................................................................................................................................71Hardware Enclosure

.......................................................................................................................................................................................72Hardware Fan

.......................................................................................................................................................................................73Hardware LED

.......................................................................................................................................................................................73Hardware Logical Disk

.......................................................................................................................................................................................74Hardware LUN

.......................................................................................................................................................................................75Hardware Memory Module

.......................................................................................................................................................................................75Hardware Network Interface

.......................................................................................................................................................................................77Hardware Other Device

.......................................................................................................................................................................................78Hardware Physical Disk

.......................................................................................................................................................................................80Hardware Power Supply

.......................................................................................................................................................................................81Hardware Processor

.......................................................................................................................................................................................82Hardware Robotics

.......................................................................................................................................................................................83Hardware Sentry Connector

.......................................................................................................................................................................................84Hardware Tape Drive

.......................................................................................................................................................................................85Hardware Temperature

.......................................................................................................................................................................................86Hardware Voltage

.....................................................................................................................................................................................87Managing Baselines and Key Performance Indicators

.....................................................................................................................................................................................89Device Additional Configuration Variables

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

Release Notes for v1.9.50

7

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

In this section:What's New

Functionality

Supported Platforms

Monitored Components

Changes and Improvements

Functionality

Supported Platforms


Fixed Issues

Functionality

Supported Platforms


8

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

What's New

Functionality

TrueSight OM - Hardware fully supports SNMP v2c and SNMP v3.

Two new configuration variables, removeAllThresholds and trimFromDisplayName, areavailable to respectively delete all existing thresholds from the configuration and specify thecharacters to be removed from the object display names.

Supported Platforms

New Supported Platforms

EMC CLARiiON and VNX systems (monitored through Navisphere CLI).

EMC Isilon Clusters (monitored via SSH).

Hitachi (HDS) AMS, HUS Storage Systems (monitored through the Hitachi Storage NavigatorModular 2 CLI).

HP P2000 G3 systems (monitored via WBEM).

Huawei Storage Systems (OceanStor) (monitored via SNMP)

Huawei Servers (monitored via their management cards).

IBM DataPower Appliances (monitored via SNMP)

IBM PureFlex Chassis (monitored via SNMP)

IBM Storwize v3700 systems (monitored via SSH)

Lenovo servers (via their IMM)

MacroSan Storage Systems (monitored via SNMP)

Oracle/Sun InfiniBand DCS Switches (monitored via SNMP)

Oracle/Sun servers (monitored through the Oracle Hardware Management Agent -Recommended method)

Oracle/Sun ZFS Storage Appliances (monitored via SSH)

Pure Storage FA Series (monitored via SSH)

QLogic HBA adapters on ESX servers (monitored via WBEM)

VMware ESX6 (monitored via WBEM)

9

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Improved Platforms

Cisco

• Non-port components for Cisco Ethernet Switches (power supplies, fans, temperaturesensors, and voltages) are supported. They are monitored via SNMP.

IBM AIX servers

TrueSight OM - Hardware reports the status of the System Attention LED and triggers an alertif a hardware problem has been reported on each system since 0:00am.

Logical disks (hdisks), physical disks (pdisks) and batteries managed by sissasraidmgr aresupported.

Oracle/Sun

Hardware monitoring is available for any Oracle/Sun system with an ILOM.

MPIO LUNs managed with the mpathadm utility are supported.

Oracle/Sun Xsigo switches are supported (monitored via SNMP).

The overall CPU and memory status are supported for Oracle/Sun Solaris 11 servers.

Network port statistics are now available for Oracle/Sun - Xsigo Switches.

SPARC Enterprise Mx000 (XSCF): Negative voltage sensors, such as -12V, are discovered.

VMware

The pathcount of LUNs is monitored for VMware ESX5i / vSphere 5 host servers.

Individual memory sensors listed under "Other" sensors in the vCenter/vSphereconfiguration tab are supported.


The Power State attribute is available to indicate whether the blade is currently on or off forDell Blade Servers, Hitachi BladeSymphony Chassis, HP BladeSystem rack, and IBMBladeCenter chassis.

10

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Changes and Improvements

Functionality

Improved scalability: The product better handles large number of hosts to monitor.

Improved stability: The product better handles error conditions on a large number of hosts.

On Windows systems, the monitoring solution could take a very long time to initialize uponstartup and after a reinitialize.

When the PATROL Agent is managed from CMA, the default thresholds mechanism is nowset to "tuning" to automatically generate alarms/events.

TrueSight OM - Hardware can be configured to automatically delete missing instances after acertain time.

Additional information (BIOS Version, Driver Version, Manufacturer, etc.) is provided in the Hardware Health Report and in events triggered by the Alert Actions.

Specific PATROL Events triggered upon Hardware and Connector failures also indicate thealert origin (monitor type name).

By default, TrueSight OM - Hardware will no longer trigger an event when an internal issueoccurs.

TrueSight OM - Hardware debug output file now includes a full hardware inventory.

The debug file and the Hardware Inventory now report the total number of instances foreach host for every monitor types.

The maximum number of concurrent collection threads is now set per host through the maxConcurrentCollectThreadsPerHost global configuration variable. ThemaxConcurrentCollectThreads variable is therefore no longer supported.

Supported Platforms

The monitoring of the Cisco UCS Interconnect Switches has been improved.

Dell Blade Servers:

The blade's hostname was added to each blade display ID.

Timeouts for all commands have been increased.

Fujitsu Eternus: TrueSight OM - Hardware provides more detailed information about FujitsuEternus systems and uses significantly less resources.

The Status of the Hitachi HDS USP/VSP Storage Systems is more accurately reported.

HP ProLiant Servers running VMware ESX:

TrueSight OM - Hardware collects a real time power consumption value from either theVMware ESX CIM agent or HP Insight Management Agent for VMware ESX.

All temperature thresholds of zero have been removed to avoid unwanted temperaturealerts.

11

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

When HP servers did not return an overall power consumption, the monitoring solutiondisabled the corresponding attribute and made an estimate in the capacity report. When thisinformation is not available, the monitoring solution will now try to sum up the powerconsumption of all power supplies before falling back on the estimate.

IBM BladeCenter Chassis: Embedded switches, passthroughs, and management modules arenow monitored.

IBM AIX Servers:

Additional information is available fo LUNs (WWN, Array Name, Hardware Location Code,and Expected Number of Paths).

The Status of the System Attention LED is now reported and an alert is triggered when thisLED is turned on.

On IBM AIX and VIO servers, the system is now fully identified with its hardware ID, LPAR ID,system ID and model name. More details have also been added to several components(disks, network cards, FC ports, and CPUs) to facilitat their identification in case of a failure.

IBM VIO Server systems are better identified with their model name, code, IDs, etc.

IBM Storwize (SSH):

Additional information is available for physical disks (vendor, model, serial number,firmware, etc.).

The instance name has been changed to "IBM Storwize (SSH)".

Quantum Scalar i2000 and i6000: The components visible identifiers are now based on sensornames / locations /etc.

SUN SPARC Enterprise Mx000 (XSCF): False voltage alerts were triggered due to incorrectthresholds.

SUN SPARC Servers (Prtpicl): A smaller version of the device ID is used for the display ID toenable easier sensor identification.

VMware ESX: The monitoring of power supplies has been improved. Both VMware ESXhealth and availability status are used to determine the health of the power supply.

Disk Monitoring on WMware ESX servers (IPMI): Because some servers use the same IPMIMonitored Device ID for all physical disks, the monitoring solution uses the IPMI Device ID togroup sensors for each physical disk. The physical disk's caption is now used as the Display ID.


Logical Disks, Temperature, Voltage and LED instances will be automatically deleted in theBMC TrueSight OM Console as soon as they are detected as "missing".

A more reliable method is being used to associate batteries to their related disk controllers.

Harware Sentry now uses Counter64 OIDs for Ethernet switches equipped with a MIB-2standard SNMP Agent.

HBA Cards Monitoring on all Windows-based systems : The LUN's naa.ID is now used toidentify LUNs. Using this naa.ID helps link LUNs to the Storage System's volume as they sharethis unique identifier code. The cdisk's Windows MPIO ID as well as the drive letters andpartition names of any volumes on that LUN are now also provided. A typical LUN ID willtherefore read: naa.60616043312F05A4308DC65F111 (MPIO Disk0 - C:(OS) D:(Data))

12

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

LUNs:

A warning is triggered when the number of available paths is one path lower than theinitial number of available paths.

The Present attribute is no more available.

The problem type, consequences, and recommended actions are provided when an alert istriggered on the Status and Available Path Count attributes.

Windows MPIO LUNs Monitoring: Because Windows regularly changes the uniqueidentifiers of LUNs and physical disks, false missing/present alerts could occur for LUNs andduplicate instances could appear. To solve this issue, the monitoring solution now uses theLUN's naa.ID, which is unique and does not change.

Network Links:

Improved network monitoring through SNMP MIB-2 for Windows and network switches.

Default thresholds are set on the Error Percent attribute of the Hardware NetworkInterface monitor type (≥ 10% = warning, ≥ 30% = alarm).

Fixed Issues

Functionality

The product could freeze or stop working in case of repeated discovery timeouts, whenreinitializing the KM on large environments or when too many connectors failed at the sametime.

In some situations, TrueSight OM - Hardware would not activate the Bandwidth Utilizationattribute even if it could collect the network’s bandwidth utilization.

When using a version of the PATROL Agent older than 9.0, the Monitor Type for the HardwareLUNs was missing.

Supported Platforms

The ports link speed was not available for Cisco MDS9000 Series FC switches.

Data Domain Storage Systems: Due to the structure of the Data Domain MIB, specific stringsin a Physical Hard Drive's serial number could cause a disk to report an unknown status.

Dell PowerEdge Servers: the physical disk instances were not attached to the proper diskcontroller instance.

Dell Servers with non-RAID disks could appear twice in BMC TrueSight OM.

Dell TL2000/4000 and IBM TS3100/3200 Tape Libraries: Tape drive mounts were incorrectlyreported as errors, which resulted in false alerts to be triggered on the Error Countattributes.

EMC Isilon Systems monitoring: Time stamped log files would fill up the filesystem. Theselog files will now be sent to /tmp/MS_HW_isi_hw_check without a timestamp to solve thisissue.

13

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Hitachi HDS AMS/HUS Storage Systems:

Authentication issues were encountered.

The execution of all commands is fully serialized to prevent conflicts. All temporary filesused by the batch files/shell scripts use randomized file names to prevent file locks andmissing files.

Logical disk information was missing.

Logical Disk Status was not collected for some systems when the command outputformat was not supported by the monitoring solution.

The Linux connector did not work properly.

HP Servers Running VMware:

Disk controllers and their batteries are now properly discovered even when noinformation on their model or serial number is available.

Thresholds labeled as "Critical" were often only “Warning” temperatures in HP's InsightManager Agent. The monitoring solution now detects this problem and sets the rightthresholds.

Display IDs have been improved to facilitate the identification of components.

HP Servers Running Windows: Disk controllers and their batteries are now properlydiscovered even when no information on their model or serial number is available.

HP-UX System: In some cases, the value of the Error Percent attribute of the Networkmonitor type was not reported correctly.

IBM AIX Servers:

Network statistics were not collected for physical ports that were part of SEA VirtualAdapters.

Power failures were not detected.

Network delays had been observed when the enstat command used to collect Ethernetports statistics on IBM AIX servers was run on disabled ports.

HBA ports were only considered active if a tape drive or hard disk was attached to them.HBA ports will now be considered active if an enabled path is associated to them.

Ports that were used as failover ports by MPIO were considered disabled. This caused falselink down alerts and stopped the monitoring of ports that were in fact active.

Child devices attached to FC ports were not monitored.

IBM Storwize (SSH): LEDs were not reporting all faults on both v3700 and v7000 systems.

IBM x Series Servers: On rare occasions, duplicate processor instances could appear in yourmonitoring environment because the IBM Director Agent reported each processor twice.

IPMI Monitoring:

Oracle specific SPARC power supply sensors is now recognized.

The SEL Fullness sensor is now excluded to avoid getting SEL Fullness alerts whenmonitoring an IBM server using IPMI.

The BIST_FAIL sensor is now excluded to avoid getting false CPU alerts when monitoring aCisco UCS Blade.

Oracle/Sun Solaris:

Disks branded as Sun and larger than 1TB were excluded from the discovery because theexpected product tag was "SUNxxxG".

Due to a recent modification in the psrinfo command output, cores were reported as full

14

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

processors. They are now grouped under a single physical CPU.

Too many CPU cores were detected for Sun Solaris MultiCore Processors.

SUN SPARC Servers

(Prtpicl): No thresholds appeared for fan sensors when LowWarningThreshold did not existfor fan instances. LowPowerOffThreshold will now be used whenever this situation occurs.

Sun SPARC servers (Running Solaris): False alarms were triggered on LED instances.

Sun SPARC servers (Running Solaris): Invalid values were reported or false alarms weretriggered for temperature and voltage sensors.

VMware:

Authentication failures for some ESXi servers could occur when monitoring VMware ESXiservers using vCenter as a multi-tier authentication server.

The port status for link down ports had been modified in VMware ESX 5.5, which causedthe VMware ESXi 4.x connector to falsely report port failures.


Devices classified as “Other Devices” (CP Modules, etc.) are now attached to their respectiveenclosures.

Emulex HBA monitoring failed when hbacmd was not installed in /usr/sbin/hbanyware/hbacmd. The monitoring solution will now run the command without the full path. Pleasenote that this modification requires hbacmd to be added to the PATH environment variableof the user used to monitor the server.

The link status for the HP-UX network cards was always "Unknown".

The solution monitors LSI sas2ircu-Managed RAID Controllers even though themanufacturer's agent does not report its status or the agent is not installed.

Multiple instances of the same LSI RAID Controller could appear in the monitoringenvironment.

The current speed of the CPU core is reported through the Current Speed attribute.

Disks:

TrueSight OM - Hardware rounded logical disks size for disks bigger than 1 TB (e.g.: the sizeof a 1.4 TB logical disk was displayed as 1 TB). The size of disks bigger than 1 TB is nowrounded to one decimal place.

A thread/handle leak could occur in the VDS.EXE process (Virtual Disk Service) whenmonitoring logical disks in a Microsoft Windows system and could cause the correspondingservice to crash.

When servers (typically HP ProLiant) do not report sizes of physical disks, the monitoringsolution queries the associated storage extents to find the actual disk size.

The monitoring solution failed to interpret the status of Non-RAID disks (reported asUnknown instead of OK)

The availability of the enclosure is reported through the Present attribute.

Redundant fans sometimes reported a speed/speed percent reading of zero, which triggeredan alert even if no thresholds were set. The monitoring solution now disables the speed/speed percent attributes if a valid status is collected to avoid this issue while maintaining fullmonitoring.

The units for the LED Status attribute have been changed to be more meaningful.

15

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Windows MPIO LUNs Monitoring: Because Windows regularly changes the unique identifiersof LUNs and physical disks, false missing/present alerts could occur for LUNs and duplicateinstances could appear.

LUNs Monitoring on WMI Disks:

If a Windows server had both LUNs and local non-RAID physical disks, then TrueSight OM -Hardware monitored both as local physical disks. LUNs will now be excluded from themonitoring.

EMC PowerPath LUNs were monitored when local physical disks were missing.

Because the monitoring solution was unable to report problems on logical disks in Windowsenvironments, logical volumes are no longer displayed for non-English versions of Windows.

Some physical disks were missing when monitoring Linux / Solaris servers with AdaptecStorMan managed RAID cards.

Getting Started

17 Overview

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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 as soonas 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

18Overview

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

19 Monitored Components

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

20Monitored Components

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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.

21 Product at a Glance

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

22Platforms & Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50



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

23 Platforms & Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50


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

.50

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

Fujitsu Eternus ETERNUS SMI-S Agent WBEM

Fusion ioDrive fio-status cli utility Command lines

Hitachi AMS/HUS HSNM2 CLI Command lines

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



25 Platforms & Requirements

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

.50

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.

http://www.sentrysoftware.net/link.asp?topic=58

http://www.sentrysoftware.com/link.asp?topic=58

Installing the Monitoring Solution

29

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

30

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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 TrueSight Operations Management.

2. Click the Repository drawer and select Manage Repository.

3. Check that the version of the BMC component available is actually the latest one. If not,download the latest version corresponding to your operating system (Windows or UNIX/Linux) available on the Sentry Software Website.

4. From TrueSight Operations Management, click Import .

5. Select Single solution.

6. Browse to the .zip source file.

7. Click Import.

The selected archive file is imported to the repository.

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

31 Importing the Monitoring Solution into CentralAdministration

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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.

32Creating the Installation Package

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

35 Configuring Monitor Settings

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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.

36Configuring Monitor Settings

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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 used bythe 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

.50

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 device oralso 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

.50

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

.50

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

.50

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

.50

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

.50

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 order toexecute 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

.50

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 using theWBEM 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

.50

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

.50

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

.50

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

.50

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

.50

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

.50

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 Actions whenan 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

.50

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.

5. Click Close to save your settings.



True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

.50

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

.50

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

.50

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

.50

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

.50

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

.50

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 to executeexternal 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

.50

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 collect hardwarehealth 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

.50

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

.50

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 variables andstops the report process.

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.

Reference Guide

63 Monitor Types and Attributes

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

64Monitor Types and Attributes

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

.50

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

.50

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 longer discovered,the attribute goes into alarm.



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

.50

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

.50

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

.50

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

.50

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

.50

Hardware EnclosureAttributes


Type

Intrusion Status This attribute will trigger an alarm if theenclosure 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

.50

Hardware FanAttributes


Type

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



Speed* Speed of the corresponding fan (inrotations/minute). An alert is triggeredif the fan speed is too low for properfunctioning.

Revolutionsperminutes(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

.50

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

.50

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

.50

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 if amemory failure is predicted to happen.

{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

.50


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

.50


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

.50

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 the diskhas 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

.50


Type

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

1 =Warning2 = Alarm

Availability

Transport Error Count Number of transport errors that the diskhas 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

.50

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

.50

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

.50

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

.50

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

.50

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

.50

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

.50

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

.50

Managing Baselines and KeyPerformance IndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, TrueSightOperations Management calculates baselines per attributes based on values collected over aspecified period of time to determine a normal operating range. When the collected values forthese attributes are out of range, an alert is triggered.

Some attributes are identified by default as Key Performance Indicators (with the icon) andtherefore automatically included in the base lining calculation.

Managing baselines

The baseline is the expected normal operating range for a metric or attribute of a monitor.

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile ofall the values for a given time period) and a high baseline value (consisting of the 90th percentileof all the values for a given time period), taking a weighted average of these values over time. Ahigher weight is given to the latest data being factored into the baseline average. The accuracy ofthe baseline improves over time.

Requirements for baseline generation

For baselines to be generated for an attribute, that abnormality threshold means that thethreshold exists and is not suppressed. Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes thathave an active abnormality threshold and are also KPI attributes will have baselines generatedfor them.

Absolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.

88Managing Baselines and Key PerformanceIndicators

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Managing Key Performance Indicators

The KPI attribute of an attribute can be activated or deactivated manually through TrueSightOperations Management. In this monitoring solution, some attributes have been designated asimportant indicators of performance (KPIs). We do not recommend that these default settingsare modified.

However, advanced users may activate or deactivate KPIs from TrueSight OperationsManagement.

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

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

2. From the Monitor Type list, choose the monitor type for which you want to add or removeKPI attributes. A list of attributes for the selected monitor type is displayed.

3. In the KPI column for the attributes that you want to add or remove as Key PerformanceIndicators:

select the KPI check box to add the corresponding attribute as a KPI

deselect the KPI check box to remove the corresponding attribute from the KPIs for thatmonitor type

For complete and detailed information on this procedure, please refer to TrueSight OperationsManagement documentation available f rom BMC Web site.

89 Managing Baselines and Key PerformanceIndicators

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Device Additional ConfigurationVariablesThe following table contains the list of the device additional configuration variables which can beadded 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.

Variables Description

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 - HardwareNetwork monitor type. Possible values are:

OK

WARN

ALARM

Default: Not set (assumed WARN).

90Device Additional Configuration Variables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50


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)


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

91 Device Additional Configuration Variables

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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.


automaticReinitialization If set to 1, triggers a re-initialization of TrueSight OM - Hardware. Thediscovery checks this variable every hour (by default) and deletes itbefore performing 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

.50


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

.50


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

.50


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


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50


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

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


True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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

.50

Troubleshooting ConnectivityIssues

99

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

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/Products/index.asp

101

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Index

- A -Add Monitor Types 35

additional variables 56

Advanced Configuration Variables 91

Agent 26

Alert Actions 49

Alert Delay 51

Attributes 63

Available Path Count 74

Bandwidth Utilization 75

Battery Status 69

Charge 65

Color 73

Connected Ports 67

Controller Status 69

Corrected Error Count 81

CPU Count 67

Current Speed 68, 81

Degrees Below Warning 67

Device Not Ready Error Count 78

Duplex Mode 75

Error Count 73, 75, 78, 82, 84

Error Percent 75

Error Status 75

Hard Error Count 78

Illegal Request Error Count 78

Intrusion Status 70, 71

Link Speed 75

Link Status 75

Logical Disk Size 67

Media Error Count 78

Memory Size 67

Mount Count 84

Move Count 82

Needs Cleaning 84

No Device Error Count 78

Physical Disk Size 67

Power Consumption 67, 71

Power State 66, 67

Predicted Failure 75, 78, 81

Present 65, 66, 67, 68, 70, 71, 72, 75, 77,80, 82, 84

Received Byte Rate 75

Received Packets Rate 75

Recoverable Error Count 78

Speed 72, 81

Speed Percent 72

Status 65, 66, 67, 68, 70, 71, 72, 73, 74,75, 77, 78, 80, 81, 82, 83, 84, 85, 86

Technology 78

Temperature 85

Test Report 83

Transmitted Byte Rate 75

Transmitted Packet Rate 75

Transport Error Count 78

Unallocated Disk Space 67

Unallocated Space 73

Unmount Count 84

Usage Count 77

Used Capacity 80

Used Time Percent 68

Value 77

Voltage 86

Zero Buffer Credit Percent 75Authentication password 38

Authentication Protocol 38

Auto Reset 52

Automatic Reporting 60

- B -Baselines 87

BMC

BMC Software Installation Utility 26

- C -Changes 7

Cisco

Cisco Ethernet Switches 21

Cisco UCS B-Series, C-Series 21

Cisco UCS Interconnect Chassis 21Cisco Fabric Interconnect Switch 46

Cisco UCS 35

Cisco UCS Blade Chassis 46

Cisco UCS Manager 46

Component 26

Component Installation package

creating 31

downloading 32

102

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Components 18

Configuration Variables 35, 91

Configuring

discovery interval 58

Local Commands 57

monitor settings 35Connectivity

Issues 99Connector 7, 35

Connector Status Parameters 51

Console Server 26

Context name 38

- D -Debug 59

Debug Mode 56

enabling 59Dell

Dell EquaLogic PS Series 21

Dell Modular Chassis (blades) 21

Dell OpenManage Server Administrator 21

Dell PowerEdge 21Detection

Missing Device 53Device

Detection 53

Missing 53Device Advanced Settings 35

Device Information 35

Disable

Missing Device Detection 53discovery and polling intervals 56

Discovery Interval

configuring 58Discrete parameters 51

Downloading 32

- E -EMC

EMC Clariion 21

EMC SMI-S Provider (ECOM) 21

EMC Symmetrix 21

EMC Symmetrix V-Max 21Emulex

Emulex HBA 21Error Count 48, 52

ErrorCount 52

- F -Features 17

Files

Mshw_ntx86_1300.exe 26

Mshw_unix_1300.tar 26

mshw_unix_1400.tar 26

mshw_WINDOWS_1400.exe 26Fujitsu

Fujitsu Eternus 21

Fujitsu-Siemens BX Blade Chassis 21

Fujitsu-Siemens PRIMERGY 21

Fujitsu-Siemens Serverview 21

- G -Global Advanced Settings 56

Global Alert Settings 48

Goals 17

- H -Hardware 26

Hardware Sentry

Installation 26Hitachi

Hitachi AMS 21

Hitachi BladeSymphony 21

Hitachi Device Manager 21

Hitachi USP-V 21HP

HP 9000 21

HP AlphaServer 21

HP c-Class BladeSystem 21

HP CommandView EVA 21

HP CommandView XP (or Hitachi DeviceManager) 21

HP Insight Management Agent 21

HP Integrity 21

HP NetServer 21

HP p-Class BladeSystem 21

HP ProLiant 21

HP StorageWorks EVA 21

HP StorageWorks XP 21

HP SuperDome (Itanium) 21

103

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

HP

HP SuperDome (PA-RISC) 21Huawei

Huawei Servers 21

Huawei Storage Systems (OceanStor) 21

- I -IBM

IBM 3584 Tape Library 21

IBM BladeCenter 21

IBM DataPower 21

IBM Director Agent 21

IBM DS 3000, 4000, 5000 Series 21

IBM DS 6000, 8000 Series 21

IBM DS Storage Manager (SMcli) 21

IBM pSeries, IBM eServer p5, p6 21

IBM Storwize V7000 21

IBM Storwize V7000 CIM Agent 21

IBM SVC 21

IBM SVC CIM Agent 21

IBM VIO Server 21

IBM XiV 21

IBM XIV Storage System SMI-S Agent 21

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

IBM xSeries, IBM Netfinity 21Importing the Monitoring Solution 30

Improvement 7

Install / Un-install

Hardware Sentry 26

Packages 26Installing 32

Installing the Monitoring Solution 29

IPMI-Over-LAN 47

Issues

Connectivity 99

Fixed 7

Troubleshooting 99

- K -Key Performance Indicators 87

KPI 87

- L -Lenovo

Lenovo IMM - SNMP 21Local Commands 56

configuring 57Localhost Sudo 57

- M -McData SAN Switch 21

Monitor Settings

configuring 35Monitor Types 63

Hardware Battery 65

Hardware Blade 66

Hardware Capacity Report 67

Hardware CPU Core 68

Hardware Disk Controller 69

Hardware Disk Enclosure 70, 71

Hardware Fan 72

Hardware LED 73

Hardware Logical Disk 73

Hardware LUN 74

Hardware Memory Module 75

Hardware Network Interface 75

Hardware Other Device 77

Hardware Physical Disk 78

Hardware Power Supply 80

Hardware Processor 81

Hardware Robotics 82

Hardware Sentry Connector 83

Hardware Tape Drive 84

Hardware Temperature 85

Hardware Voltage 86Multi-Tier 43

Multi-Tier Authentication 43

- N -NEC

NEC Express5800 21NetApp 21

New features 7

number of consecutive times 48

Numeric parameters 51

104

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

- O -OpenSSH 41

Operating Systems

HP-UX 21

Linux 21, 26

OpenVMS 21

Solaris 21

Tru64 21

UNIX 26

VMware ESX4 21

Windows 21, 26out-of-band interface 47

Overview 20

- P -Package 31, 32

PATROL

PATROL component 26Platforms

Supported 21Port 38

Present Parameters 51

Privacy password 38

Privacy protocol 38

Product 20

protocol

IPMI-Over-LAN 35

SNMP 35

SSH/Telnet 35

WBEM 35

WMI 35

- Q -QLogic

QLogic HBA 21Quantum Tape Library 21

- R -Reference Guide 63

Reports

scheduling 60Requirements 21

Root Privileges 41, 57

- S -Scheduling

Reports 60SNMP

v1 38

v2c 38

v3 38SNMP Community String 38

SNMP port 38

specific action 48

Specific PATROL Event 49

SSH 41

SSH/Telnet 41

Status attribute 55

STD 41 PATROL Event 49

StorageTek

StorageTek LSeries 21

StorageTek StreamLine (SL) 21Sudo 57

Sudo Command 41

Sudo Command Line 57

Sun

Sun Advanced Lights-Out Management(ALOM) 21

Sun Blade Modular Chassis 21

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

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

Sun Fire (SPARC) 21

Sun Fire (X64) 21

Sun Fire F12K, F15K, F20K, F25K 21

Sun Fire Mx000 21

- T -Technology

Command lines 21

HTTP 21

IPMI 21

SNMP 21

SSH 21

Telnet 21

WBEM 21

WMI 21

105

True

Sigh

t O

pera

tion

s M

anag

em

ent

- H

ardw

are

Ver

sion

1.9

.50

Technology

XML API 21Telnet 41

Thorium 26

Timeout 38

Troubleshooting

Connectivity Issues 99

- U -Unknown Status 48, 55

Username 38

- V -Variables 91

VMware

VMware ESX4 21

VMware ESXi 21

- W -WBEM 43

Web 26

What's new 7

Windows Management Instrumentation 45

WMI 45

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 ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasks thatoccur in the daily course of IT operations. Combined with BMC’s servers and networkautomation tools, the adapters allow IT administrators to implement provisioning anddecommissioning workflows that cover all layers of their IT infrastructure. Finally, SentrySoftware designs connectors that bring storage capacity metrics into BMC TrueSightCapacity Optimization to ensure IT administrators that their storage infrastructure isproperly sized for their current 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

truesight operations management - hardware sentry 1.9 · 9 truesight operations management -...

Documents