bmc® performance manager express for hardware … of contents 2 version 2.9.10 bmc performance...

User Documentation October 2013

BMC Performance ManagerExpress for Hardware

Version 2.9.10

Table of Contents 2

Version 2.9.10

BMC Performance Manager Express for Hardware

Table of Contents...........................................................................................................................22Targeted Computers

...........................................................................................................................22Package

...........................................................................................................................23Note on RSMs

...........................................................................................................................23Installing Appropriate Hardware Agents

...........................................................................................................................24Migration

...........................................................................................................................24Installing BPM Express for Hardware

...........................................................................................................................25Installation Procedure

...........................................................................................................................28Adding BPM Express for Hardware to an Element Profile

...........................................................................................................................32Requirements for monitoring AIX, HP-UX, Linux, Solaris and Tru64 systems

...........................................................................................................................34Requirements for monitoring Storage systems

...........................................................................................................................37Requirements for monitoring Windows systems

...........................................................................................................................39Requirements for monitoring Other platforms

...........................................................................................................................42Adding the Hardware Application class to an Existing Element

...........................................................................................................................43Un-installing BPM Express for Hardware

...........................................................................................................................43Removing BPM Express for Hardware from Managed Elements

...........................................................................................................................44Uninstalling BPM Express for Hardware from the Portal

...........................................................................................................................46Integrating with BMC ProactiveNet Performance Management

...........................................................................................................................47Automatically Enabling the Application Classes

...........................................................................................................................48Creating and Importing an Adapter for a BMC Portal Solution

...........................................................................................................................54Managing Baselines and Key Performance Indicators

...........................................................................................................................58How it Works

...........................................................................................................................60Understanding BPM Express for Hardware within the Portal environment

...........................................................................................................................61Integrating BPM Express for Hardware

...........................................................................................................................62The Need for Vendor-specific Hardware Agents

...........................................................................................................................63Monitoring with BPM Express for Hardware

...........................................................................................................................64Inside BPM Express for Hardware

...........................................................................................................................65The Detection Process

...........................................................................................................................65The Discovery Process

...........................................................................................................................65The Collection Process

...........................................................................................................................66The Connectors

...........................................................................................................................66Monitoring

...........................................................................................................................66The Basics

Table of Contents 3

Version 2.9.10


...........................................................................................................................68Monitoring the Enclosure

...........................................................................................................................69Environment: Fans, Temperatures, Power_Supplies and Voltages

...........................................................................................................................7 1Disks: Physical Disks, Logical Disks and Disk Controllers

...........................................................................................................................7 5Devices: Processors, Memory modules and Network interfaces

...........................................................................................................................7 7Missing Device Detection

...........................................................................................................................7 8Connector Monitoring

...........................................................................................................................7 9Reporting

...........................................................................................................................7 9Ethernet/Fiber Port Traffic Report

...........................................................................................................................80Energy Usage Report

...........................................................................................................................81Thresholds

...........................................................................................................................82Configuring Alert Conditions

...........................................................................................................................84Modifying Parameter Thresholds

...........................................................................................................................85Troubleshooting

...........................................................................................................................85Enabling the Debug Mode

...........................................................................................................................86BPM Express for Hardware Shows Nothing

...........................................................................................................................87Monitors Nothing but Network Interfaces

...........................................................................................................................89Reinitializing Certain Parameters

...........................................................................................................................90Unable to See Disk Controller

...........................................................................................................................90Unable to connect to WMI

...........................................................................................................................92Application Classes

...........................................................................................................................92Battery

...........................................................................................................................93Blade

...........................................................................................................................93Capacity Report

...........................................................................................................................95Connector

...........................................................................................................................95CPU

...........................................................................................................................97CPU Core

...........................................................................................................................97Disk Controller

...........................................................................................................................98Enclosure

...........................................................................................................................98Fan

...........................................................................................................................100LED

...........................................................................................................................100Logical Disk

...........................................................................................................................101LUN

...........................................................................................................................102Main

...........................................................................................................................103Memory

...........................................................................................................................104Network

...........................................................................................................................106Other Device

Table of Contents 4

Version 2.9.10


...........................................................................................................................107Physical Disk

...........................................................................................................................108Power Supply

...........................................................................................................................109Robotics

...........................................................................................................................109Tape Drive

...........................................................................................................................110Temperature

...........................................................................................................................111Voltage

...........................................................................................................................112Special Note on Application Collection Status

...........................................................................................................................112Thresholds

...........................................................................................................................112Additional Configuration Properties

...........................................................................................................................117Connectors

...........................................................................................................................117Connector and Platform Reference Table

...........................................................................................................................125Adaptec IOManager

...........................................................................................................................125Adaptec StorMan (RAID)

...........................................................................................................................126Adaptec Storage Manager (DPT)

...........................................................................................................................127Adaptec Storage Manager Web Edition (AAC)

...........................................................................................................................128Brocade SAN Switch

...........................................................................................................................129Cisco MDS9000 Series - SSH/Telnet

...........................................................................................................................130Cisco UCS Manager (Blade, Fabric Interconnect Switch)

...........................................................................................................................131DataDirect Networks (DDN) Disk Array - SNMP Agent

...........................................................................................................................132Data Domain Storage Appliance - SNMP Agent

...........................................................................................................................133Dell CMC (Dell Chassis Management Controller)

...........................................................................................................................134Dell DRAC/MC (Dell Remote Access Controller/Modular Chassis)

...........................................................................................................................135Dell EqualLogic PS Series

...........................................................................................................................136Dell iDRAC - Server

...........................................................................................................................138Dell iDRAC - Storage

...........................................................................................................................139Dell OpenManage Array Manager

...........................................................................................................................140Dell OpenManage Server Administrator

...........................................................................................................................141Dell OpenManage Storage Manager

...........................................................................................................................142Dell PowerVault TL2000/4000 Tape Libraries

...........................................................................................................................143EMC Disk Arrays

...........................................................................................................................144Emulex HBAs (hbacmd)

...........................................................................................................................145Fibre Alliance SNMP Agent (Switches)

...........................................................................................................................146Fujitsu-Siemens Management Blade (FSC BX Blade Servers)

...........................................................................................................................147Fujitsu-Siemens Serverview - WBEM

...........................................................................................................................148Fujitsu-Siemens Serverview - WMI

...........................................................................................................................149Fujitsu-Siemens ServerView RAID Agent

Table of Contents 5

Version 2.9.10


...........................................................................................................................150Fujitsu-Siemens Serverview

...........................................................................................................................151Fusion ioDrive (fio-status)

...........................................................................................................................152Hitachi BladeSymphony Chassis

...........................................................................................................................153Hitachi HDS Disk Arrays

...........................................................................................................................154HP BladeSystem

...........................................................................................................................155HP BladeSystem - Telnet/SSH

...........................................................................................................................156HP Insight Management Agent - Drive Array

...........................................................................................................................157HP Insight Management Agent- Fiber Array

...........................................................................................................................158HP Insight Management Agent - HBA

...........................................................................................................................159HP Insight Managerment Agent - IDE Storage

...........................................................................................................................159HP Insight Management Agent - iLO

...........................................................................................................................160HP Insight Management Agent (v8.25 or higher) - Memory

...........................................................................................................................161HP Insight Management Agent (v8.20 or lower) - Memory

...........................................................................................................................161HP Insight Management Agent - Network

...........................................................................................................................162HP Insight Management Agent - SCSI Storage

...........................................................................................................................163HP Insight Management Agent - Server

...........................................................................................................................164HP Insight Management Agent - Server (Alpha)

...........................................................................................................................165HP Insight Management Agent - Server - WBEM

...........................................................................................................................167HP Insight Management Agent - Server - WMI

...........................................................................................................................168HP MP/GSP card (iLO)

...........................................................................................................................168HP MSA 2000 & P2000

...........................................................................................................................17 0HP StorageWorks EVA - SSSU - PM

...........................................................................................................................17 1HP TopTools Agent

...........................................................................................................................17 2HP TopTools NetRaid Agent

...........................................................................................................................17 3HP-UX - Common

...........................................................................................................................17 4HP-UX - Disks

...........................................................................................................................17 5HP-UX-HBA

...........................................................................................................................17 6IBM AIX - LUN

...........................................................................................................................17 6HP-UX - Network

...........................................................................................................................17 7HP-UX - SASMGR Managed Disks

...........................................................................................................................17 8HP-UX - Smart Array RAID

...........................................................................................................................17 9HP-UX-STM

...........................................................................................................................180HP-UX - WBEM

...........................................................................................................................181HP-UX - WBEM Network

...........................................................................................................................182IBM BladeCenter Management Module

...........................................................................................................................183IBM AIX - CHRP Environment

Table of Contents 6

Version 2.9.10


...........................................................................................................................184IBM AIX - Common

...........................................................................................................................185IBM AIX - Environment (uesensor)

...........................................................................................................................186IBM AIX - HBA

...........................................................................................................................187IBM AIX - SCSI disks

...........................................................................................................................188IBM Director Agent 3.x - Windows

...........................................................................................................................189IBM Director Agent 4.x - Linux


...........................................................................................................................191IBM Director Agent 5.10x - Linux

...........................................................................................................................192IBM Director Agent 5.10x - Windows

...........................................................................................................................193IBM Director Agent 5.20.x - Linux

...........................................................................................................................194IBM Director Agent 5.20.x - ServeRAID - Linux

...........................................................................................................................195IBM Director Agent 5.20.x - Windows

...........................................................................................................................196IBM Director Agent 5.20.x - ServeRAID - Windows

...........................................................................................................................197IBM Director Agent 6.x - Linux


...........................................................................................................................199IBM DS (LSI) Disk Arrays (smcli)

...........................................................................................................................200IBM DS6000/8000 Disk Arrays

...........................................................................................................................201IBM Netfinity Manager 5.20.x - Basic

...........................................................................................................................202IBM Netfinity Manager 5.20.x - Disks

...........................................................................................................................203IBM Netfinity Manager 5.20.x - Normal

...........................................................................................................................203IBM TS3100 Tape Libraries

...........................................................................................................................204IBM TS3200 Tape Libraries_2

...........................................................................................................................205IBM v7000 Disk Arrays - SSH

...........................................................................................................................206IBM v7000 Disk Arrays

...........................................................................................................................207IBM VIO Server

...........................................................................................................................208Intel Base Board 5 Motherboards

...........................................................................................................................209Intel Modular Server

...........................................................................................................................210IPMI - In-band (IpmiTool)

...........................................................................................................................211Localhost Monitoring Disabled

...........................................................................................................................212LSI 1030-based GAM Server

...........................................................................................................................213LSI 1030-based GAM Server (Alternate MIB)

...........................................................................................................................213LSI Logic - LsiUtil - RAID (Windows)

...........................................................................................................................214LSI Logic - LsiUtil - RAID

...........................................................................................................................215LSI Logic MegaRAID PowerConsole

...........................................................................................................................216LsiLogic MegaRAID SAS

...........................................................................................................................216LsiLogic MegaRAID SAS (Newer Controllers)

Table of Contents 7

Version 2.9.10


...........................................................................................................................217LSI MegaCli

...........................................................................................................................218LSI/Mylex GAM Server

...........................................................................................................................218Linux - Emulex HBAs (hbacmd)

...........................................................................................................................219Linux - Network

...........................................................................................................................220Linux - Multipath

...........................................................................................................................221Linux - QLogic HBAs (scli)

...........................................................................................................................222McData Fibre Switch

...........................................................................................................................223MegaCLI Managed Raid Controllers

...........................................................................................................................224MIB-2 Standard SNMP Agent - Network Interfaces

...........................................................................................................................225MIB-2 Standard SNMP Agent - Network Interfaces - Linux

...........................................................................................................................226MIB-2 Standard SNMP Agent - Network Interfaces - Windows

...........................................................................................................................227MIB-2 Standard SNMP Agent - Network Interfaces - Solaris

...........................................................................................................................228Motherboard Monitor

...........................................................................................................................229NetApp Filer - SNMP Agent

...........................................................................................................................230NEC ESMPRO Agent

...........................................................................................................................231Promise FastTrack

...........................................................................................................................232Quantum (ADIC) Based Tape Libraries

...........................................................................................................................233SmartMonTools

...........................................................................................................................234SMI-S Compliant Disk Arrays

...........................................................................................................................235SMI-S Compliant HBAs

...........................................................................................................................236SMI-S Compliant RAID Controller - Linux

...........................................................................................................................237SMI-S Compliant RAID Controller - Windows

...........................................................................................................................237SMI-S Compliant Storage Libraries

...........................................................................................................................238SMI-S Compliant SAN Switches

...........................................................................................................................239SNIA Compliant Tape Libraries

...........................................................................................................................240SPARC Enterprise Mx000 (XSCF)

...........................................................................................................................241StorageTek LSeries Tape Library

...........................................................................................................................242StorageTek StreamLine Tape Library

...........................................................................................................................243Sun Advanced Lights-Out Management (ALOM) card

...........................................................................................................................244SUN Blade Chassis

...........................................................................................................................245Sun Fire F12K/F15K/F20K/F25K (SMS)

...........................................................................................................................246SUN ILOM (SNMP)

...........................................................................................................................247SUN ILOM (SSH)

...........................................................................................................................248Sun Solaris - Environment (ALOM-CMT snapshot)

...........................................................................................................................249Sun Solaris - Environment (prtpicl)

...........................................................................................................................250Sun Solaris - Environment (prtdiag, lom)

Table of Contents 8

Version 2.9.10


...........................................................................................................................251Sun Solaris - Fault Manager (Memory)

...........................................................................................................................252Sun Solaris - Memory modules (cediag)

...........................................................................................................................253Sun Solaris - Processor

...........................................................................................................................254Sun Solaris - Network

...........................................................................................................................255Sun Solaris - Non-Sun Disks

...........................................................................................................................256Sun Solaris - Multi-core Processors (psrinfo)

...........................................................................................................................256Sun Solaris - RAID Disks (Raidctl)

...........................................................................................................................257Sun Solaris - Multi Processors (psrinfo)

...........................................................................................................................258Sun Solaris - Sun Disks

...........................................................................................................................259Sun Solaris - Tape Drives

...........................................................................................................................259Windows - DiskPart

...........................................................................................................................260VMware ESXi 3.x

...........................................................................................................................261VMware ESX4i - Disks (IPMI)

...........................................................................................................................262VMware ESX4i - Disks (VMware)

...........................................................................................................................263VMware ESXi 4.x

...........................................................................................................................264WMI - Battery

...........................................................................................................................264WMI - Disks

...........................................................................................................................265WMI - HBA

...........................................................................................................................266WMI - Network

Release Notes for v2.9.10

10


Version 2.7.28

What's New

New Supported Platforms

Brocade SAN Switch

DataDirect Networks (DDN)

Dell PowerVault TL2000 and TL4000 tape libraries

Hitachi HDS Disk Arrays

IBM DS6000, DS8000 Disk Arrays

IBM TS3100 tape libraries

IBM TS3200 tape libraries

IBM v7000 Disk Arrays

Fujitsu-Siemens PRIMERGY servers running VMware

Fujitsy-Siemens Serverview

Miscellaneous

A new additional configuration property is available to disable a specific connector for a managedelement in rsm.properties:

Disable Connectors(net.sentrysoftware.bpm.hardware.disabledConnectors.<hostname>=connector1.hdf,connector2.hdf,connector3.hdf).

11


Version 2.7.28

On HP Blade Chassis monitored using SNMP, the product now excludes temperature sensors that donot have a valid temperature value (and thus also an invalid threshold) or a valid status.

The product now supports multi-tier authentication schemes for WBEM connections, and notablyconnections to VMware ESXi hosts that require an authentication through VMware vCenter.

A temperature sensor with the status of "N/A" (i.e. one that only has a numeric value) was notbeing interpreted correctly, leading to the entire sensor's status being reported as "unknown" ratherthan a status based on the numeric temperature.

Changes and Improvements

Improved Platforms Support

Dell servers with iDRAC7 or later: The KM now supports Dell's new iDRAC7 management card,which provides full hardware information about Dell server.

Dell PowerEdge M1000e Chassis: The MS_HW_DellCMC.hdf connector now monitors the overallstatus of each blade installed in the chassis and makes possible the collect of the ambienttemperature sensor in most recent versions of the Dell CMC firmware.

Fujitsu PRIMEPOWER: The product provides enhanced support for Fujitsu PRIMEPOWER serversrunning Solaris. The “sun4us” hardware class is now supported as the “sun4u” class.

Hitachi HDS Disk Arrays: This version of the KM provides a new connector specifically designed andoptimized for Hitachi HDS Disk Arrays. It adds new parameters and significantly reduces resourcesneeded to monitor a Hitachi Disk Array. This connector replaces the SMI-S Compliant Disk Arraysconnector which is therefore withdrawn from the productwhich no longer needs to be used forHitachi storage systems.

IBM Blade Chassis - The connector for IBM Blade Chassis has been improved to:

add a status parameter for Fan Modules

collects an accurate Power Consumption

add monitoring of 3rd and 4th Fan Modules in chassis with 4 Fan modules

Monitor second temperature sensor for BladeCenter HT chassis

IBM DS6000/DS8000 Disk Arrays: The product provides improved monitoring for IBM DS6000/DS8000 Disk Arrays. It adds new parameters, provides more details, better identifies the differentcomponents in the system and significantly reduces resources needed to monitor an IBM DS6000/DS8000.

Oracle servers: The KM now provides support for Oracle servers (formerly known as Sun servers)through their ILOM card.

Miscellaneous

The product provides improved monitoring for network ports on a server running Solaris 11 andwhere the network port's Device Instance ID is not the same as its Link Assigned Name.(e.g. the physical port device ID is e1000g0 and the ifconfig name is net0).

On HP ProLiant, the monitoring of the physical cards in a NIC teaming configuration is nowperformed by the regular connectors (MIB2, WMI, etc.). The “HP Insight Management Agent –Network” connector now monitors the status of the logical interface only.

StorageTek StreamLine Tape Library: The status of the tape drives is now properly interpreted.

Dell PowerEdge: The product will now use Dell's Location codes (Nexus) to identify disks. ThisNexus identifier better represents the true location of the disk.

The monitoring IBM VIO Servers has been significantly improved. The product:

better recognizes and adapts to restricted and unrestricted shell interfaces when connecting to anIBM VIO Server. In an unrestricted shell interface, the standard IBM AIX connectors will be usedinstead of the specific IBM VIO Server connector

12


Version 2.7.28

monitors Disk Controllers and LUNs (AvailablePathcount)

provides an ErrorCount parameter for Physical Disks. Also, the Status parameter has beenremoved (No reliable physical disk status is available)

The monitoring of recent versions of Linux (RedHat Enterprise Linux 6 a.k.a. RHEL6, SuSe LinuxEnterprise Server 11 SP2 a.k.a. SLES 11 SP2, etc.) has been improved to allow support of the newoutput format used by the latest version of the multipath utility.

BPM Express for Hardware now monitors HBAs in HP 9000 (PA-RISC) servers running HP-UX (linkspeed, link status and port status). Using the MS_HW_HPUXHBA.hdf connector requires rootprivileges.

The PM provides enhanced support for Fujitsu PRIMEPOWER servers running Solaris. The “sun4us”hardware class is now supported as the “sun4u” class.

The product now monitors Brocade SAN switches via Brocade's SMI Agent which providesinformation not available using SNMP, notably:

Ports in Virtual Fabrics

FCoE Ethernet Ports

Fixed IssuesUpgrading from version 2.7.27 to higher versions is now possible.

In Cisco UCS blade chassis, the status of the blade servers was not properly reported when theblade had a specific user label configured.

The following issues on HP ProLiant servers running VMware or Linux have been fixed:

parameters for the network interfaces are now collected

the LinkStatus of the network cards is now properly collected

all network cards are now properly discovered

13


Version 2.7.28

On IBM xSeries, the 6.3.2 version of the IBM Director agent reports voltage and temperature alertthresholds in a way that is inconsistent with the previous versions. The new connector takes intoaccount this variation and support older and newer versions of the IBM Director Agent.

CIn Cisco MDS and Nexus Switches, ports that were "Administratively Down" or "Out of Service"were previously reported as having a status of "Unknown". These ports will now report a status of"OK".

The VMWare ESX Disks (Storage) and VMware ESX Disks (IPMI) connectors are now automaticallydeactivated if the SMI-S Compliant RAID Controller connector applies to the monitored system.

Monitoring Sun/Oracle servers: when monitored through their ILOM card, voltage sensors no longertrigger false alarms. Also, when monitored through their ILOM card, the PredictedFailure parameteris now properly collected.

The "Linux - Multipath" connector was wrongly activated on all Linux systems even though thesystem did not have any MPIO configuration and the multipath command line utility couldn't befound.

The PM was unable to transfer and execute the embedded files, therefore connectors using theembedded files would not be used even though they pass the platform detection test.

On IBM DS3000, DS4000 and DS5000 Series storage systems, physical disks with the status of "By-passed" are now discovered and an appropriate alarm is generated.

The HP Insight Management Agent–Server connector (MS_HW_CpMgServNT.hdf) triggeredtemperature alerts due to invalid thresholds.

Some Sun SPARC systems do not report the color of the LED. Without the LED color, the productwas unable to set the appropriate alert thresholds. BPM Express for Hardware now looks at thedescription of the LED to determine proper thresholds if the color is not available.

On EMC Clariion and VNX storage systems, failed (or disabled, or removed) storage processors andcontrollers are now properly reported as such.

On HP BladeSystem c7000 chassis, some temperature sensors were not properly discovered.

IBM DS3000, DS4000, DS5000 Series Storage Systems: The name of the temporary file to store theoutput of the SMCLI command on the RSM was not generated properly. As a result, the monitoringfailed with an “index out of range” exception.

An issue leading to an infinite loop when trying to discover the Emulex HBA cards on serversrunning UNIX or Linux, prevented the product to collect hardware information and displayed thefollowing message in the Application Collection Status parameter: "SentrySoftware-HardwareSentry-solution.Javaheapspace:SentrySoftware-SEN_HW_MAIN".

The connector for Dell EqualLogic PS Series (MS_HW_Equallogic.hdf) no longer collectstemperature values of zero, preventing alerts of type "Temperature: WARNING! (Problem: Althoughnot yet critical, the temperature is abnormally high (0 degrees C))" from being generated.

Supported Platforms/Requirements

15


Version 2.7.28

Requirements for Managed ElementsFor BMC Performance Manager Express for Hardware to collect information from a managed element, itrequires specific instrumentation agents or system management tools to be present on the managedelement.

A specific hardware agent is often required on each managed element depending on its underlyingcomponents.

ServersTypical Platform Operating

SystemInstrumentation Prerequisites Technology Used

Cisco UCS B-Series, C-Series

Windows None IPMI, WMI

Cisco UCS B-Series, C-Series

Linux ipmitool IPMI, command lines

Dell PowerEdge Windows Dell OpenManage Server Administrator SNMP

Dell PowerEdge Linux Dell OpenManage Server Administrator SNMP

Dell PowerVault TL2000tape libraries

Windows Dell SNMP Agent (DELL-SHADOW-MIB) SNMP

Dell PowerVault TL4000tape libraries

Windows Dell SNMP Agent (DELL-SHADOW-MIB) SNMP

Fujitsu PRIMEPOWERServers (sun4us) -

Solaris None Command lines

Fujitsu-SiemensPRIMERGY - VMware

Fujitsu ServerviewWBEM agent

None WBEM

Fujitsu-SiemensPRIMERGY

Windows Fujitsu-Siemens ServerviewFujitsu-Siemens ServerView RAIDAgent / Promise FastTrack SNMP Agent /LSI GAM Server / LSI MegaRAID SASSNMP Agent / LSI MegaRAIDPowerConsole / Mylex GAM Server(depending on the server, follow Fujitsu-Siemens recommendations)

SNMP


Linux Fujitsu-Siemens ServerviewFujitsu-Siemens ServerView RAIDAgent / Promise FastTrack SNMP Agent /LSI GAM Server / LSI MegaRAID SASSNMP Agent / LSI MegaRAIDPowerConsole / Mylex GAM Server(depending on the server, follow Fujitsu-Siemens recommendations)

SNMP


Linux Fujitsu-Siemens Serveview WBEM Agent WBEM


Windows Fujitsu-Siemens Serveview WBEM Agent WMI

HP 9000 HP-UX GSP card Command lines, Telnet/SSH

HP AlphaServer Tru64 HP Insight Management Agent SNMP

HP AlphaServer OpenVMS HP Insight Management Agent SNMP

16


Version 2.7.28

Typical Platform OperatingSystem

Instrumentation Prerequisites Technology Used

HP Integrity Windows HP Insight Management Agent SNMP

HP Integrity Linux HP Insight Management Agent SNMP

HP Integrity HP-UX MP card Command lines, Telnet/SSH

HP NetServer Windows HP TopTools SNMP, WMI

HP ProLiant Windows HP Insight Management Agent SNMP or WMI

HP ProLiant Linux HP Insight Management Agent SNMP

HP ProLiant Solaris HP Insight Management Agent SNMP

HP SuperDome (Itanium) Windows HP Insight Management Agent SNMP

HP SuperDome (Itanium) Linux HP Insight Management Agent SNMP

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

HP SuperDome (PA-RISC)

HP-UX GSP card Command lines, Telnet/SSH

IBM pSeries, IBM eServer IBM AIX None Command lines

IBM TS3100 TapeLibraries

Storage Device IBM SNMP Agent SNMP Agent (IBM-3100-MIB)

SNMP

IBM TS3200 tape libraries Storage Device IBM SNMP Agent SNMP Agent (IBM-3200-MIB)

SNMP

IBM v7000 Disk Arrays Storage Device -- Telnet/SSH, WBEM

IBM VIO Server IBM AIX None SSH

IBM xSeries, IBMNetfinity

Windows IBM Director Agent WMI


Linux IBM Director Agent WBEM, command lines

NEC Express5800 Windows NEC ESMPRO Agent SNMP

NEC Express5800 Linux NEC ESMPRO Agent SNMP

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

Solaris None Command lines

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

Solaris Access to the Sun Advanced Lights-OutManagement (ALOM) card over thenetwork

Command lines, SSH to theALOM card

Sun Fire (SPARC) Solaris None Command lines

Sun Fire (X64) Solaris ipmitool, lsiutil Command lines

Sun Fire (X64) Linux ipmitool, lsiutil Command lines

Sun Fire (X64) Windows lsiutil IPMI (WMI), command lines

Sun Fire F12K, F15K,F20K, F25K

Solaris Access to the SMS utilities installed onthe System Controller (SC)

SSH to the SystemController

Sun Fire Mx000 Solaris Access to the eXtended System ControlFacility (XSCF)

SSH to the XSCF

17


Version 2.7.28

Cross-Platform Technology

Technology OperatingSystem

Instrumentation Prerequisites Technology Used

Emulex HBA Windows None WMI

Emulex HBA Linux hbacmd Command lines

Emulex HBA Solaris hbacmd Command lines

QLogic HBA Windows None WMI

QLogic HBA Linux scli Command lines

QLogic HBA Solaris scli Command lines

VMware ESX/ESXi VMware ESX/ESXi Access to the CIM server WBEM

Blade Chassis

Chassis Instrumentation Prerequisites Technology Used

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

XML API (HTTP)

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

Fujitsu-Siemens BX BladeChassis

Fujitsu-Siemens Management Blade SNMP

Hitachi BladeSymphony Hitachi BladeSymphony Management Module SNMP

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

HP p-Class BladeSystem HP Insight Management Agent SNMP

IBM BladeCenter IBM BladeCenter Management Module SNMP

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

Storage Devices

Typical Platform Instrumentation Prerequisites Technology Used

3PAR InServ 3PAR SMI-S Provider WBEM

Brocade SAN Switch SNMP Enabled SNMP

Cisco SAN Switch1 None Telnet/SSH

Compellent Compellent Enterprise Manager WBEM

Dell EquaLogic PS Series None SNMP

Dell TL2000/4000 Tape library None SNMP

EMC Clariion EMC SMI-S Provider WBEM

EMC Symmetrix EMC SMI-S Provider WBEM

EMC VNX series EMC SMI-S Provider WBEM

18


Version 2.7.28

Typical Platform Instrumentation Prerequisites Technology Used

Fujitsu Eternus ETERNUS SMI-S Agent WBEM

Hitachi AMS Hitachi Device Manager WBEM

Hitachi USP-V Hitachi Device Manager WBEM

Hitachi VSP Hitachi Device Manager WBEM

HP StorageWorks EVA HP CommandView EVA Command lines

HP StorageWorks P9000 Series HP CommandView WBEM

HP StorageWorks XP HP CommandView XP (or Hitachi Device Manager) WBEM

IBM 3584 Tape Library None SNMP

IBM DS 3000, 4000, 5000Series

IBM DS Storage Manager (SMcli) Command lines

IBM DS 6000, 8000 Series IBM DS Storage Manager WBEM

IBM TS3100/3200 Tape library None SNMP

IBM XiV IBM XIV Storage System SMI-S Agent WBEM

McData SAN Switch None SNMP

NetApp None SNMP

Quantum Tape Library None SNMP

StorageTek LSeries None SNMP

StorageTek StreamLine (SL) None SNMP

* Cisco network switches are not supported by BMC Performance Manager Express for Hardware.

The vendor-specific instrumentation agents and system tools are generally provided with theservers and are available on the manufacturer website. Unless mentioned otherwise, these“agents” must be installed on the managed server for BMC Performance Manager Express forHardware to function properly. Please refer to the platform-specific guides available on the BMCPerformance Manager Express for Hardware page of the Sentry Software website.

Please check our web site www.sentrysoftware.com to find the latest updates. Updates are in the formof patches for BMC Performance Manager Express for Hardware. They are for free and do not need anupgrade of the PM itself, unless there are structural changes.

http://www.sentrysoftware.net/downloadBpmeHardware.asp

http://www.sentrysoftware.com

Getting Started

20


Version 2.7.28

BMC Performance Manager Express for Hardware enables administrators to monitor the hardware of alltheir diverse servers on BMC© Portal. This is a single performance manager (PM) that is able to monitorthe hardware of different server brands: IBM®, HP®, DELL®, Sun Microsystems®, NEC®, Fujitsu-Siemens® and many others.

As this PM is specifically designed for the BMC Portal environment, it uses the Portal’s web-basedinterface and features for installing, managing and monitoring your Information Technology (IT)infrastructure. The full integration with BMC Performance Manager Portal provides a single customizableentry point for data from multiple sources and a single view that enables you to monitor the health andperformance of your infrastructure

Once installed, BMC Performance Manager Express for Hardware requires no configuration andautomatically detects the environment and starts monitoring the hardware: status of the disks and theRAID controllers, temperature of the system, speed of the fans, power supplies, network interfaces etc.

For convenience, BMC Performance Manager Express for Hardware is called BPM Express for Hardware within theproduct documentation (online and PDF formats)

Installation Guide

22


Version 2.7.28

This chapter explains how to install and run BMC Performance Manager Express for Hardware forBMC® Portal.

As BMC Performance Manager Express for Hardware is a performance manager specifically designedfor the BMC© Portal environment, it uses the Portal’s web-based interface and features for installing,managing and monitoring your Information Technology (IT) infrastructure. The full integration withBMC® Portal provides a single customizable entry point for data from multiple sources and a single viewthat enables you to monitor the health and performance of your infrastructure.

Once installed on one system in the Portal environment, you can add as many elements as you wish andBMC Performance Manager Express for Hardware starts monitoring the hardware of all the connectedsystems within your BMC© Portal environment: status of the disks and the RAID controllers, temperatureof the system, speed of the fans, etc.

Targeted Computers

BMC Performance Manager Express for Hardware (called BPM Express for Hardware for short) is to beinstalled on the web-based BMC© Portal v2.5.00.

Install on just one element within the BMC© Performance Manager Portal environment

Ensure access to the Remote Service Monitor (RSM) program installed on a Windows system. TheRSM program can be installed on the same system as the Portal if it is a Windows system.

Once you install BPM Express for Hardware on one machine, you can then add as many elements(computers, servers, systems) as you require to your monitoring environment irrespective of whetherthey Windows, UNIX or Linux systems.

Please note that BPM Express for Hardware v2.9.10 is not compatible with any version of BMC©Portal prior to v2.5.00..

Package

The package for BPM Express for Hardware consists of just one PAR file. It is available on the BMCSoftware EPD site, as well as on the Sentry Software Website:

BPM-Express-for-Hardware-<version>.par

This file is valid for installation on Windows and UNIX/Linux systems.

Product updates and documentation in PDF and online formats are available on the Sentry SoftwareWebsite.

http://www.sentrysoftware.com/Products/HardwareExpress_Downloads.asp

http://www.sentrysoftware.com/Products/HardwareExpress_Documentation.asp

http://www.sentrysoftware.com/Products/HardwareExpress_Documentation.asp

23Note on RSM


Version 2.7.28

Note on RSM

In general, an RSM is said to support the monitoring of 100,000 parameters. In the case of BPM Expressfor Hardware, it is difficult to calculate a precise number of parameters collected since this dependsentirely on the element itself and the number of hardware objects: disks, fans, memory modules etc.discovered.

On an average, between 2-5 parameters are collected for each object discovered. The number ofhardware objects discovered, and the hence number of parameters collected, greatly varies from onemanaged element to another. The total number of parameters collected directly depends on the numberof objects discovered on each element.

The number of RSMs required would also depend on whether an RSM is dedicated to BPM Express forHardware alone, or whether there are other PMs on the same RSM. It should be safe to assume that anRSM dedicated entirely to BPM Express for Hardware would be able to support approximately 150elements, and an RSM shared by two or more PMs should on an average be able to support themonitoring of 80 to 100 elements.

Installing Appropriate HardwareAgentsIn most cases, BPM Express for Hardware requires a third-party hardware instrumentation agent tocollect information from the monitored computer. Each manufacturer develops platform-specific systemmanagement tools that collect hardware data and these tools are generally provided along with theserver and are also generally available on the manufacturer website.

Unless mentioned otherwise, the platform-specific instrumentation layer or system management toolmust be installed on the managed systems for BPM Express for Hardware to function properly. Certainservers or systems could have more than one applicable “hardware agent”. You can refer to the Connector and Platform Reference Table to see which system tools/agents are required for yourservers.

The installation of the platform-specific “hardware agents” is to be done prior to the installation ofBPM Express for Hardware. Additional information on the instrumentation agents for certainplatforms may be found in platform-specific guides on the Sentry Software Website .


24Migration


Version 2.7.28

Migration

As part of the process of migrating to PM 2.7 from version 2.5.xx or 2.6.xx, all parameters will beremoved and recreated for each element. Only those parameters that are used will then berecreated (Unused, previously grayed out parameters will not be shown.) Previous history for allparameters will be lost during this recreation process, however any previous events generated bythose parameters will remain.

BMC Performance Manager Express for Hardware Version 2.9.10 requires BMC© Portal v2.5.00(minimum). It is fully compatible with the Portal v2.5.00 and upwards.

Owing to structural changes from version 2.5.00, an automatic migration from previous versions(2.3.xx) of BPM Express for Hardware is not possible. Users of previous versions should remove the PMfrom all elements and completely uninstall the PM (v2.3.xx) before uploading and installing Version2.9.10.

If the previous version is not removed from the Portal and Version 2.9.10 is loaded, the two PMs willappear separately in the list of application classes, and the older version will continue to monitorelements.

BPM Express for Hardware Version 2.9.10 is integrated with the new WMI collector patch of BMC Portal sdk.Installation of BMC’s WMI patch 2.5.00.033.zip (for Portal 2.5) or 2.6.00.004.zip (for Portal 2.6) is required beforemigration or installing Version 2.9.10.

Installing BPM Express forHardwareGetting the BPM Express for Hardware PackageTo install BPM

Express for Hardware on your Portal environment, you need:

BPM-Express-for-Hardware-<version>.par

You can get this installation file by contacting BMC Software or by downloading it from the SentrySoftware Website

Prerequisites1. BMC© Portal minimum version 2.5.00

2. At least one Remote Service Monitor program (RSM). See BPM Portal Management and MonitoringGuide for more details.

3. An account for BMC© Portal account with sufficient credentials

Uninstall the previous version of the PMOwing to structural changes in the PM, no migration is possible from previous versions (2.3.xx) tov2.5.00 or higher. Once you install Version 2.9.10, the BPM Express for Hardware application class will

http://www.sentrysoftware.net

http://www.sentrysoftware.net

25Installing BPM Express for Hardware


Version 2.7.28

not overwrite or merge with its previous versions (2.3.xx), but will instead appear in the list in additionto it, just like any other PM, and the previous version will continue to function. If you wish to use onlyVersion 2.9.10 on all your elements, you need to completely uninstall and remove the previous version(2.3.xx) before installing Version 2.9.10.

As part of the process of migrating to PM 2.7 from version 2.5.xx or 2.6.xx, all parameters will beremoved and recreated for each element. Only those parameters that are used will then berecreated (Unused, previously grayed out parameters will not be shown.) Previous history for allparameters will be lost during this recreation process, however any previous events generated bythose parameters will remain.

Installation Procedure1. Place BPM-Express-for-Hardware-<version>.par file in a known location on your file system.

No migration is possible from previous versions (2.3.xx) to v2.9.10 owing to structural changes. It isessential to uninstall the previous version (2.3.xx) from all elements before installing v2.9.10 as itwill not overwrite or merge with the old version, but will instead just appear as an additional PM, andthe old version will continue the monitoring.

Logging on to Portal

2. Log on to BMC Portal with super-administrator credentials.

3. Click the Portal tab. Under Tasks in the left pane, select Performance Managers to open thePerformance Managers page and then click Upload.

Uploading Perform ance Managers



Version 2.7.28

4. Click Browse to open a file selection dialog box, select the file BPM-Express-for-Hardware-<version>.par and click Open.

Locating the .par file

5. Click Upload. The Portal uploads the PAR file to the database, and you should see BPM Express forHardware in the list of Performance Managers as Published, which means it is installed.

BPM Express for Hardware appears as Published



Version 2.7.28

6. The “+” symbol next to BPM Express for Hardware indicates that there are several application classeswithin the main PM (Performance Manager). Expand the tree to see the platform-specific applicationclasses of BPM Express for Hardware:

Viewing platform -specific Hardware classes

7. Hardware (Solaris); Hardware (Linux); Hardware (Linux); Hardware (Storage); Hardware (Other);Hardware (OpenVMS); Hardware (HP-US); Hardware (AIX); Hardware (Switch); Hardware(Windows); Hardware (Tru64)

The PM is built with separate platform-specific classes since the input properties required to activate theclass vary from one platform to another. For details, see: Adding BPM Express for Hardware to anElement Profile.

Please note that although the expanded list shows Hardware (Switch) and Hardware (Storage)amongst other classes - these two classes are meant for monitoring storage devices, but will notfunction unless the Storage Add-on for BPM Express for Hardware is installed. This is a separateproduct for monitoring storage devices, and it is built as an add-on component for BPM Express forHardware.

The installation of BPM Express for Hardware is now complete. To begin using the performancemanager, log out and then log in again, this time, with user credentials. You are now ready to beginusing the PM.



Version 2.7.28

Adding BPM Express for Hardware to an ElementProfile

1. Click Configure tab > Element Profiles. The Available Profiles page appears. Select theProfile to which you wish to add the Hardware class > Edit.

Selecting a Profile

2. The selected Element Profile’s Properties page appears. Go to Application Classes > Add.



Version 2.7.28

A dding A pplication Classes

3. The Element Profile Properties – Add Application Classes page appears. Choose Hardwarefrom the Select Category drop-down list.



Version 2.7.28

Selecting the Hardware A pplicable Class



Version 2.7.28

4. On selection of Hardware in the list, the Available Classes section displays all the differentplatform-specific BPM Express for Hardware application classes: Hardware (Solaris), Hardware(Linux), Hardware (AIX), etc.

5. Select the application class applicable to your system and click Next.

6. On the Properties and Credentials page, enter the information required for monitoring withHardware (Windows/ Aix,HP-UX, Linux, Solaris and Tru64 systems/Other:Blade chassis,management cards etc.)

7. After entering the element properties and credentials, you arrive at the final step for adding theBPM Express for Hardware application class: Thresholds, Properties and Credentials.

8. Thresholds are automatically set by BPM Express for Hardware. It is recommended to keep thedefault thresholds (or see Modifying Parameter Thresholds. Click Finish.

9. Hardware (<platform type>) appears in the list of Application Classes for the profile.

Elem ent Profile Properties

1. Click Done to save the changes made. The BPM Express for Hardware application class is nowadded to all the elements in the selected Element Profile.



Version 2.7.28

Requirements for monitoring AIX, HP-UX, Linux,Solaris and Tru64 systemsInformation required to monitor AIX, HP-UX, Linux,Solaris and Tru64 systems

Name Description

Collection interval Select the polling interval from the drop-down list. Default: 5. Unit: Minutes

Connection Credentials[Telnet/SSH] Username[Telnet/SSH] PasswordOrShared Credentials

Enter the credentials used to connect to the element through Telnet or SSH. OrSelect shared credentials from the drop down list if you wish to use pre-definedcredentials.

[Execution] Credentials[Execution] Username[Execution] PasswordOrShared Credentials

Optional: Execution credentials used to execute commands through Telnet or SSH.Enter the execution username and password only if you need to use a logindifferent from the connection login above.OrSelect shared credentials from the drop down list if you wish to use pre-definedcredentials.

[Root] Credentials[Root] Username[Root] PasswordOrShared Credentials

Optional: Enter the root login. These credentials will only be used to executecommands requiring root privileges. OrSelect shared credentials from the drop down list if you wish to use pre-definedcredentials.

[WBEM] Credentials[WBEM] Username[WBEM] PasswordOrShared Credentials

Optional: Enter the WBEM credentials if required for connection to the element. OrSelect shared credentials from the drop down list if you wish to use pre-defined loginand password.

[SSH] Private Key Specify the path of the private key used for SSH authentication.

[SSH] Passphrase Specify the passphrase for the above imported private key.

[WBEM] Multi-Tier AuthenticationServer

Enter the IP address/Host name of the multi-tier authentication server. This option ismostly used for VMware ESXi host with an authentication through vCenter servers).

[WBEM] Transport Protocol Select the transport protocol: HTTP or HTTPS to be used for connecting to the CIMserver.

[WBEM] Port Enter the WBEM port number on which runs the CIM server.

[WBEM] Namespace Optional: Enter the WBEM namespace used to connect to the CIM server.

Hostname Enter the hostname or IP address of the element to be monitored.

Credential Options Selection of type of credentials: root or sudo, from the drop-down list determineswhether BPM Express for Hardware will use the root credentials specified above orthe sudo utility for commands requiring root privileges.

SNMP version Specify the SNMP version to be used by BPM Express for Hardware to retrieveinformation from the elements: SNMP v1; SNMP v2c; SNMP v3.

SNMP Community Enter the SNMP community string required for SNMP v1/SNMP v2c.



Version 2.7.28

Name Description

[SNMP v3] Username Enter the username required for SNMP v3.

[SNMP v3] Authentication Protocol Enter the protocol required for SNMP v3 authentication.

[SNMP v3] AuthenticationPassword

Enter the password required for SNMP v3 authentication.

[SNMP v3] Privacy Protocol Enter the privacy protocol required for SNMP v3.

[SNMP v3] Privacy Password Enter the privacy password required for SNMP v3.

Error Count auto-reset after Specify the interval in hours for a reset of the Error Count parameter.Certain devices are monitored by counting the number of encountered errors. TheError Count parameter triggers an alert as soon as an error is detected. The ErrorCount parameter and its alerts are automatically reset at the specified interval toprevent a single error from continuously raising alerts.

Missing Device Detection By default, the missing device(s) will be detected and monitored. Setting the optionto Disable will deactivate the detection and the monitoring of the missing device(s).

In case of Status parameter valueis UNKNOWN

Select the action to be performed when Hardware Express is unable to interpret thevalue of the Staus parameter if it is UNKNOWN.

Default system wattage Constant value (in Watts) to be used for the "Power Consumption" parameter andthe "Energy Usage" report when the system is not able to report its actual energyusage. Use this setting if you know approximately the normal power consumption ofthis managed element and would like to compare it with other better instrumentedsystems and report on the global electricity consumption of your servers.

Debug Mode Select Yes to enable the debug mode or No disable it. Default: NoThe debug output is stored in a file on the RSM server. The debug file is located at:%RSM_HOME%/RSMxx/SEN_HW/sen_hw_debug_hostname.log

Sudo Configuration and Execution Methods

The BMC Performance Manager Express for Hardware can be configured to use different Credentials /the sudo utility in three different ways:

1st method: Sudo

The software logs into the server using the credentials Credentials: [Telnet/SSH], it then runs thecommand using sudo.

To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the section Credentials: [Execution] and Credentials: [Root] needs to be blank (no usercredentials), and the option Use Sudo Utility selected. The sudo utility would need to be configured forall commands that need root and the sudo utility would also need to be in the path of the Patrol User.Select the option Use Sudo Utility.



Version 2.7.28

i.e.

login patrol

sudo command

2nd method: Ultra Secure Sudo

The software logs into the server using the credentials Credentials: [Telnet/SSH], then does an su toCredentials: [Execution], then runs the command using sudo.

This method is a slight modification of the 1st method, which is rarely used outside ultra secureenvironments. This is used when the first username does not have the rights to run the sudo.

To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the second, non-root user, but able to run the sudo command to be entered in Credentials:[Execution], and Credentials: [Root] to be left blank. The option Use Sudo Utility needs to be selected.The sudo utility would need to be configured for all commands that need root and the sudo utility wouldalso need to be in the path of the Patrol User. Then select the option Use Sudo Utility.

i.e.

login patrol

su - secure-user

sudo command

3rd method: Root

The software logs into the server using credentials Credentials: [Telnet/SSH], then su to Credentials:[Root] and runs the command directly.

To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], section Credentials: [Execution] left blank, and the root credentials section Credentials: [Root].The select the option Use above Execution/Root credentials.

i.e.

login patrol

su - root

command

Requirements for monitoring storage systemsInformation required to monitor storage systems

Name Description


Connection CredentialsTelnet/SSH UsernameTelnet/SSH PasswordOrShared Credentials

Enter the credentials used to connect to the element through Telnet or SSH. Or



Version 2.7.28

Name Description

Select shared credentials from the drop down list if you wish to use pre-definedcredentials.

WBEM CredentialsWBEM UsernameWBEM PasswordOrShared Credentials

Optional: Enter the WBEM credentials if required for connection to the element. OrSelect shared credentials from the drop down list if you wish to use pre-defined loginand password.








SNMP Port Port number on which the SNMP agent is running.








Error Count Auto-reset After Specify the interval in hours for a reset of the Error Count parameter.Certain devices are monitored by counting the number of encountered errors. TheError Count parameter triggers an alert as soon as an error is detected. The ErrorCount parameter and its alerts are automatically reset at the specified interval toprevent a single error from continuously raising alerts.

Link Status auto-reset after The Link Status parameter triggers an alert as soon as a link fails. The Link failurealarm is automatically cleared at specified interval. Unit: hours.









Version 2.7.28


1st method: Sudo


To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the section Credentials: [Execution] and Credentials: [Root] needs to be blank (no usercredentials), and the option Use Sudo Utility selected. The sudo utility would need to be configured forall commands that need root and the sudo utility would also need to be in the path of the Patrol User.Select the option Use Sudo Utility.

i.e.

login patrol

sudo command





i.e.

login patrol

su - secure-user

sudo command

3rd method: Root





Version 2.7.28

i.e.

login patrol

su - root

command

Requirements for monitoring Windows systemsInformation required to monitor Windows systems

Input Properties Description


Connection Credentials[WMI] Username[WMI] PasswordOrShared Credentials

Enter the credentials used to connect to the element using WMI. OrSelect shared credentials from the drop down list if you wish to use pre-definedcredentials.

WBEM CredentialsWBEM UsernameWBEM PasswordOrShared Credentials

Optional: Enter the WBEM credentials if required for connection to the element.OrSelect shared credentials from the drop down list if you wish to use pre-definedcredentials.






SNMP Port Default : 161. Port number on which the SNMP agent is running.









Link Status auto-reset after Specify the interval in hours for a reset of the Link Status parameter.The Link Status parameter triggers an alert as soon as a link fails. The Link failurealarm is automatically cleared at specified interval.




Version 2.7.28

Input Properties Description

In case of Status parameter valueis UNKNOWN...

Select the action to be performed when Hardware Express is unable to interpret thevalue of the Status parameter if it is UNKNOWN.





1st method: Sudo


To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the section Credentials: [Execution] and Credentials: [Root] needs to be blank (no usercredentials), and the option Use Sudo Utility selected. The sudo utility would need to be configured forall commands that need root and the sudo utility would also need to be in the path of the Patrol User.Select the option "Use Sudo Utility".

i.e.

login patrol

sudo command







Version 2.7.28

i.e.

login patrol

su - secure-user

sudo command

3rd method: Root



i.e.

login patrol

su - root

command

Requirements for monitoring Other platformsInformation required for monitoring “Other” platformsi.e. Blade chassis, management cards etc.

Name Description


Connection Credentials[Telnet/SSH/IPMI] Username[Telnet/SSH/IPMI] Password

OrShared Credentials

Enter the credentials used to connect to the element through Telnet or SSH or IPMI. OrSelect shared credentials from the drop down list if you wish to use pre-definedcredentials.

[UCS] Username[UCS] PasswordOrShared Credentials

Login used to connect to Cisco's Unified Computing Systems.

Shared credentials used for authentication.

[WBEM] Username[WBEM] PasswordOrShared Credentials

Optional: Login used to connect to the remote element through WBEM).



[UCS] SSL Encryption "Yes" enables the SSL encryption for UCS login while "No" disables it.

[WBEM] Multi-Tier AuthenticationServer

Enter the IP address/Host name of the multi-tier authentication server. This option ismostly used for VMware ESXi host with an authentication through vCenter servers).




Version 2.7.28





SNMP Port Port number on which the SNMP agent is running.









Link Status auto-reset after The Link Status parameter triggers an alert as soon as a link fails. The Link failurealarm is automatically cleared at specified interval. Unit: hours.





Debug Mode Select Yes to enable the debug mode or No to disable it. Default: NoThe debug output is stored in a file on the RSM server. The debug file is located at:%RSM_HOME%/RSMxx/SEN_HW/sen_hw_debug_hostname.log

Sudo Configuration and Execution MethodsThe BMC Performance Manager Express for Hardware can be configured to use different Credentials /the sudo utility in three different ways:

1st method: Sudo


To use this method, we would need the patrol user credentials to be entered in Credentials: [Telnet/SSH], the section Credentials: [Execution] and Credentials: [Root] needs to be blank (no usercredentials), and the option Use Sudo Utility selected. The sudo utility would need to be configured forall commands that need root and the sudo utility would also need to be in the path of the Patrol User.



Version 2.7.28

Select the option Use Sudo Utility.

i.e.

login patrol

sudo command





i.e.

login patrol

su - secure-user

sudo command

3rd method: Root



i.e.

login patrol

su - root

command



Version 2.7.28

Adding the Hardware Application Class to anExisting Element1. In the Configure tab: Click the Element to which you wish to add the hardware solution and the

Element Properties page appears. Scroll down to Application Classes > Add.

A dding a Hardware A pplication Class

2. On the Properties – <Element> – Add Application Classes page > Select Category >Hardware.

3. In the Available Application Classes, the BPM Express for Hardware application class applicable tothe element appears automatically. Select and click Next.

Hardware A pplication Class Properties

4. The Properties and Credentials page appears asking for the information required for monitoring forHardware (<platform>). Enter the required information.

Click the link for information required to monitor Windows systems.

Click the link for information required to monitor AIX, HP-UX, Linux, Solaris and Tru64 systems.

Click the link for information required for monitoring “Other” platforms i.e. Blade chassis,management cards etc.

5. After entering the element properties and credentials, you arrive at the final step for adding theHardware application class: Thresholds.

6. Thresholds are automatically set by BPM Express for Hardware. It is recommended that you leavethe default thresholds as they are. Click Finish. Details on how to modify thresholds are given in theUser Guide.

7. The message: “Success! Changed have been saved” appears and Hardware (<platform>) appearsin list of Application Classes for the element.

You can now return to the Status tab to view the monitoring of the element by BPM Express for



Version 2.7.28

Hardware.

Un-installing BPM Express forHardwareThis chapter describes the procedure to remove or permanently delete BPM Express for Hardware fromyour Portal environment. You cannot delete the hardware solution (or any other) if any of its applicationclasses are currently monitoring infrastructure elements.

Removing BPM Express for Hardware fromManaged ElementsUn-installation of BPM Express for Hardware is not possible if any infrastructure elements continue to bemonitored by the Hardware application class. It is essential that all users remove the Hardwareapplication class from their monitored elements, only then can it be properly uninstalled and removedfrom the Portal.

Deleting the Hardware Application Class from ManagedElementsTo remove an application class from an Element Profile1. In the Configure tab, click Element Profile > Available Profiles > select the Profile from which

you wish to delete the application class > Edit.

2. The Element Profile Properties page appears. Scroll to Application Classes > Delete.

3. The next page displays the Application Classes Available for Removal. Select Hardware(<platform>) and click Next.

4. The next page asks for confirmation of the deletion requested. Click Delete.

5. The message: “Success! Changes have been saved” indicates that the deletion is now complete.The BPM Express for Hardware application class has been successfully removed from all theelements in the selected element profile.

To remove an application class from an Element1. In the Configure tab, click the Element > Properties page > Application Classes > Delete.

2. The next page displays the application classes available for removal. Select Hardware (<platform>)and click Next.

3. Confirm the deletion on the following page by clicking Delete.

4. The message “Success! Changes have been saved” indicates that the deletion is complete and theelement is no longer monitored by BPM Express for Hardware.

Once the application class is removed from all elements/element profiles; the super-administrator canproceed to completely remove the PM from the Portal environment.

44Un-installing BPM Express for Hardware


Version 2.7.28

Uninstalling BPM Express for Hardware from thePortalJust as for installation, to uninstall BPM Express for Hardware from the Portal environment, you need touse super-administrator credentials:

The PM can be uninstalled from the Portal only once it is deleted from all managed elements.

1. In the Portal tab, expand Tasks > and click Performance Managers.

2. In the Performance Managers list, scroll down to BMC PM Express for Hardware.

3. Ensure that it shows “0” for the number of elements monitored. The PM that you wish to deleteshould not have any elements assigned to it.

4. Select BMC PM Express for Hardware and click Delete.

5. On the next Performance Managers - Delete page, click Delete to confirm.

The “Success” message that appears indicates that BMC© PM Express for Hardware is now removedfrom the Portal.

For a complete un-installation, it is recommended to remove all traces of the performance managerfrom the Portal. Delete the BPM Express for Hardware PAR file from each RSM used by the solution. Todo so:

1. Stop the RSM service

2. Go to %RSM_HOME%\RSMxx\server\rsm\solutions

3. Delete the file: SentrySoftware-HardwareSentry-solution-<version>.par

4. Restart the RSM service

BMC Performance Manager Express for Hardware is now completely removed from your BMC© Portalenvironment.

Integration Guide

46Integrating with BMC ProactiveNet PerformanceManagement


Version 2.7.28

Integrating with BMC ProactiveNetPerformance ManagementOverview

To integrate a Performance Manager into BMC ProactiveNet, you need to first install and configure thesolution in BMC Portal, automatically enable the application classes and create a specific adapter. Anadapter for BMC Portal facilitates pulling of performance data from existing BMC Portal solutions intoBMC ProactiveNet. Using an Adapter, you can import BMC Portal application classes (provided in aPerformance Manager – PM) into BMC ProactiveNet. The Adapter periodically synchronizes theperformance data collected by these application classes into BMC ProactiveNet.

A dapter for BMC PA TROL A rchitecture



Version 2.7.28

Automatically Enabling the Application ClassesTo automatically enable application classes:

1. Uncompress the BPM-Express-for-Hardware-<version>-PM2BPPM.zip file

2. Copy all the BPM_SENTRYSOFTWARE_HARDWARESENTRY_SOLUTIONSENTRYSOFTWARE_HARDWARESENTRY_MAIN_AIX xml files into: <BPPM install dir>\ProactiveNet\pw\pronto\systdata\adapter-defaults

3. Restart the BMC ProactiveNet server

You will then have to create and import an adapter for a BMC Portal PM



Version 2.7.28

Creating and Importing an Adapter for a BMCPortal Solution

Creating an Adapter for a BMC Portal Solution1. Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console

is displayed as shown in the following figure:

A ccessing the A dm inistration tab in the A dm inistration Console



Version 2.7.28

2. Right-click the Adapters folder and select Import Monitor Types and Add Adapter > BMCPortal.

Im porting Monitor Ty pes and A dding A dapter



Version 2.7.28

3. In the Configuration tab, enter the required information:

Setting the connection param eters

In the Instance Name field, enter a name for this instance of the Adapter that will perform theintegration of the ‘targeted PM’ into BMC ProactiveNet.

Select the Agent where this instance of the Adapter will be executed

Enter the required information to connect to BMC Portal: BMC Portal Host Name or IPaddress, Port, BMC Portal User Name and Password

To successfully integrate the PM with BMC ProactiveNet, the BMC Portal User Account specified musthave at least been used once to log in to BMC Portal and have the Hardware Application Class addedto an existing element.

Enter the required information to connect to BMC Portal Datastore: BMC Portal Datastore HostName or IP address, Port, and credentials



Version 2.7.28

4. Click Next to continue

Selecting the A pplication Classes to im port



Version 2.7.28

5. Select the application class(es) to import and click Next

6. Set the Filter details if needed.

Setting filter details



Version 2.7.28

7. Click Next to Continue.

8. Set the Auto-sync poll scheduling, if needed.

Scheduling A uto-sy nc polls



Version 2.7.28

9. Click Next to continue. The system displays a summary of your settings, click Finish to confirm. TheAdapter has been added to the Adapters folder of the Administration Console.

A dapter added to the A dapters folder

10. To see the class instances that have been imported by the Adapter, expand the Adapters folder,right-click the Adapter and select Details.

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

Once created and imported, the Adapter will be displayed in the Devices folder of the BMC ProactiveNetOperations Console.

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

Some parameters are identified by default as Key Performance Indicators and therefore automaticallyincluded in the base lining calculation.



Version 2.7.28

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 a specifiedtime period and establishing a low baseline value (consisting of the 10th percentile of all the values for agiven time period) and a high baseline value (consisting of the 90th percentile of all the values for agiven time period), taking a weighted average of these values over time. A higher weight is given to thelatest data being factored into the baseline average. The accuracy of the baseline improves over time.

Requirements for baseline generation

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

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

Managing Key Performance Indicators

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

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

To add or remove Key Performance Indicator (KPI) attributes for amonitor 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 remove KPIattributes. A list of attributes for the selected monitor type is displayed.

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

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

deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitortype

For complete and detailed information on this procedure, please refer to the BMC ProactiveNet documentation availablefrom BMC Web site.

Parameters for which the system by default calculates baselines as well as parameters considered as



Version 2.7.28

KPIs are respectively identified by the following icons:

Baselining

KPI

User Guide

58


Version 2.7.28

Prerequisites�

1. BPM Express for Hardware is a PM for the Portal and therefore needs to be installed within theBMC© Portal environment.

2. As this is an agent-less performance manager for the web-based BMC© Performance ManagerPortal, it can be installed on just one managed element equipped with the Portal.

3. Minimum version of BMC© Portal should be 2.5.00.

4. The RSM program should be installed on a Windows system (it can be the same as the Portal)

5. Install the vendor-specific instrumentation agents or system management tools on the managedelements to be monitored prior to installing the PM. See the platform-specific guides for details.

6. Download the product package i.e. a PAR file from BMC EPD or the Sentry Software Web site.

How it Works

BMC Performance Manager Express for Hardware is a PM that enables BMC Portal to monitor computerhardware (disk status, temperatures, CPU, power supplies etc).

It gathers hardware information from different sources such as manufacturer-specific agents, standardmanagement technologies, SNMP, WBEM, etc., and displays this information within the Portalenvironment.

In order to work properly, BPM Express for Hardware needs certain hardware information sources to beavailable. Depending on the platform, it relies on the manufacturer-specific instrumentation layer and/oron standard management technology such as WBEM or SNMP. On startup, BPM Express for Hardwareautomatically detects which hardware information source is available and then uses this to poll data onthe hardware health of the computer. BPM Express for Hardware collects such data from each serverand reports it in your Portal console.



59How it Works


Version 2.7.28

Monitoring hardware with BPM Express for Hardware

Overview of the mechanism of BPM Express forHardware

60How it Works


Version 2.7.28

The Siemens® ServerView® agent shows the temperatures, the fans, the power supplies and thevoltages of the Siemens computer through SNMP

The Mylex® GAM Server shows the status of the physical and logical disks of the Mylex RAIDController through SNMP

The Windows WMI provider shows the status of the physical disks attached to the standard SCSIcontroller through WBEM

BPM Express for Hardware detects and automatically connects to all three information sources(Siemens ServerView, Mylex GAM Server and Windows WMI provider).

BPM Express for Hardware gathers only useful hardware information from these sources anddisplays it within the Portal framework

This is just an example of the basic mechanism of BPM Express for Hardware and is applicable to IBM, NEC, HP and allother supported computers as well.

Understanding BPM Express forHardware within the PortalenvironmentHere’s an overview of the basic outline of BPM Express for Hardware within BMC© PerformanceManager Portal.

The environment

The BMC© Portal, is composed of a database, an application server, and a web server, andprovides the access point for its utilities and modules.

The BMC© Performance Manager Portal extends the features in the Portal, enabling you to leverageboth agent-less technologies and the PATROL agent to monitor the availability and performance ofyour business infrastructure.

BPM Express for Hardware is a based on agent-less technology, is designed for the Portal and usesthe same web-based interface and Portal features common to all modules.

� The interactionBPM Express for Hardware is leveraged by the BPM Portal module that uses Remote ServiceMonitors (RSMs) to collect metrics about your infrastructure.

An RSM is a computer on which you have installed the RSM program. Depending on the size of yourenvironment, you can implement one or many RSMs. To know what to monitor on the specifiedinfrastructure elements, the RSM uses PMs and therefore for hardware monitoring, it banks on theBPM Express for Hardware.

All Performance Managers, and the application classes that they contain, are installed on the Portal,and saved in the Portal database when you select them from an installation CD or when you importthem via the Portal user interface. Performance Managers that are installed on the Portal areavailable to all users on the Portal who have the appropriate user permissions.

The figure below shows the interaction between BPM Express for Hardware and the Portal:

61Understanding BPM Express for Hardware withinthe Portal environment


Version 2.7.28

Understanding BPM Express for Hardware within the Portal env ironm ent

Interaction between the PM and the PortalThe above given data and diagram show you how remote monitoring of your hardware is possible onthe Portal. Installation of BPM Express for Hardware on just one computer is sufficient for monitoring aheterogeneous infrastructure, as long as the vendor-specific hardware agents are installed on everymanaged element.

Integrating BPM Express forHardwareBPM Express for Hardware is specifically designed for BMC© Portal and does not require any specialintegration process.

Once properly installed within the BMC© Performance Manager Portal environment, the hardwareinformation and status of the monitored elements should be available via the web browser used toaccess the Portal. Please refer to the Installation Guide for further details on the installation procedure.


62The Need for Vendor-specific Hardware Agents


Version 2.7.28

The Need for Vendor-specificHardware AgentsOften, the standard operating system layer is not a sufficient hardware information source and mostcomputers require an additional manufacturer-specific agent for BPM Express for Hardware to functionproperly. In most cases, server vendors provide the required hardware monitoring agent for their servermodels.

Depending on the platform, a single agent could monitor the temperatures, fans, voltages, powersupplies and RAID systems, or, the platform may require separate agents for environment and diskmonitoring.

For example: The IBM Director Agent monitors and provides information about temperatures, fans,voltages, power supplies and the ServeRAID disks for IBM xSeries servers. On the other hand, theSiemens ServerView Agent only monitors the sensors on the motherboard of the server (temperatures,voltages, fans and power supplies) and so the Mylex GAM Server is required to monitor the Mylex RAIDcontroller of the server.

Please refer to the Connector and Platform Reference Table and the platform-specific guides for furtherdetails on vendor-specific agents required by BPM Express for Hardware.


63Monitoring with BPM Express for Hardware


Version 2.7.28

Monitoring with BPM Express forHardwareOnce BPM Express for Hardware is installed on the elements, after having ensured that all pre-requisitesare met, the hardware information is displayed automatically in Portal interface under: Element >Hardware (<platform-type>) as shown below.

View of objects discov ered by BPM Express for Hardware

Monitored componentsDepending on the managed system, BPM Express for Hardware monitors:

Disks (RAID and non-RAID disks)

Disk enclosures

Fans

Memory modules

Network interfaces

Power supplies

Processors

Temperature

Voltage

For details on which hardware components are detected on each system, please see the Connectors & PlatformsReference Table in the Reference Guide and click on the Connector Name applicable to your system/typical platform.

64Inside BPM Express for Hardware


Version 2.7.28

Inside BPM Express for Hardware

Architecture

BPM Express for Hardware is principally composed of a common hardware monitoring engine: BPM-Express-for-Hardware-<version>.par containing the following files:

SEN_HW_bcel-5.2-2.5.00_Build_214.jar

SEN_HW_Hardware_2600-2.5.00_Build_214.jar.

DetectionUpon startup, BPM Express for Hardware tests each connector in order to detect which hardwareinformation sources are available (vendor-specific hardware agents, standards instrumentation layers,etc.) This is called the detection process.

DiscoveryOnce BPM Express for Hardware knows which hardware information sources are available and can beconnected to, it tries to discover the hardware environment by querying these selected hardwareinformation sources, as described in the corresponding *.hdf files. This is called the discovery process.

CollectionFinally, when the detection and discovery processes are complete, BPM Express for Hardware startscollecting data about the discovered hardware environment (status, temperatures, voltages, etc.) byquerying the detected hardware information sources as described in the corresponding *.hdf files. Thisis called the collection process.

Here's a synopsis of the actions performed by BPM Express for Hardware:

Action Description

Activation Activates the main class

Detection Tests each connector in order to detect which hardware information sources are available on themonitored element and can be connected toDetection is carried out when the Hardware class is added to an element and each time the RSM isrestarted.

Discovery Discovers the hardware environment by querying the previously detected hardware informationsourcesCreates the other class instances (Temperature, Physical Disk, etc.)Discovery is carried out every hour.

CollectionProcess

Polls previously detected hardware information sources to gather data about the hardwareenvironmentPolling is carried out every 5 minutes.



Version 2.7.28

The Detection ProcessOnce the BPM Express for Hardware class is added to an element, BPM Express for Hardware:

1. Gets the list of available connectors “*.hdf” files from %RSM_HOME%\RSMxx\server\rsm\tmp\deploy\tmpxxxxxSentrySoftware-HardwareSentry-solution-<version>.par-native.

2. For each “.hdf” file found, BPM Express for Hardware tests the detection criteria (OS type, NTservice, processes, SNMP request, etc.)

3. Marks the “.hdf” files as "detected" once all its detection criteria is successfully passed. There maybe several connectors detected at one time (typically: one connector for the temperatures,voltages, etc., one for the RAID disk controller and one for the non-RAID disk controller)

4. Launches the discovery process

Only one “.hdf” file can describe the computer model and manufacturer and only one icon for the computer will becreated. The BPM Express for Hardware engine will ensure that only one “.hdf” describing the computer model will bemarked as "detected".

The Discovery ProcessThe discovery process is launched just after the end of the detection process. It takes the followingactions:

Processes the "Enclosure.Discovery" section of the detected connectors (“.hdf”) that describe thecomputer model and create the main Hardware Sentry and computer icon (class: Enclosure). Mostof other icons (environment, disks, devices etc) will be created under this computer icon.

Launches the disk controller discovery that processes the "Disk Controller Discovery" section of eachdetected “.hdf” file and creates the Disk Controller icons.

Launches the other discoveries (fans, temperatures, voltages, power supplies, logical disks, physicaldisks and other devices) that will process the corresponding sections of each detected “.hdf” fileand create the corresponding icons.

With a v iew to optimization, the discovery process is as parallelled as possible. A ll independent objects are processed

at the same time.

The Collection ProcessOnce the discovery process is complete, the collection process starts:

Every five minutes, the BPM Express for Hardware spawns several paramlets that are responsiblefor the collection of information about a given device type.

For example, the Fan paramlet will gather fan information from the different detected hardwareinformation sources, as described in the corresponding “.hdf” Fan.Collect section.

These paramlets are "attached" to the main BPM Express for Hardware icon (main class) and not tothe corresponding classes and instances.

When a device is marked as "missing" by the discovery process (i.e. had been discovered but is nolonger discovered), the collection process no longer queries the hardware information source andsimply sets the status of the object to alarm.



Version 2.7.28

The ConnectorsEach connector is an “.hdf” file that is dedicated to one source of hardware information. Each connectorfile describes how BPM Express for Hardware connects to the available hardware information sourceand what information is available through this source. For example, SEN_HW_Director41NT.hdf describes how to get information from the IBM Director 4.1 Agent and then monitor an IBM xSeriesserver.

An “.hdf” file can tell the BPM Express for Hardware engine to do the following actions:

Query a SNMP agent (get, get next, and tables)

Execute a WBEM query (using WMI for Windows and the Pegasus implementation of WBEM forLinux)

Execute an OS command (using TELNET and SSH)

Each “.hdf” file uses a mix of these possible actions with some computing capabilities to make BPMExpress for Hardware gather useful data in a given hardware information source.

The “.hdf” files are deployed on the RSM at %RSM_HOME%\RSMxx\server\rsm\tmp\deploy\tmpxxxxxSentrySoftware-HardwareSentry -solution-<version>.par-native. These files released by Sentry Softwareare encrypted and therefore cannot be updated or modified by the end-user.

Monitoring

Monitoring the hardware components with the BPM Express for Hardware is very simple. Once installed,as per the instructions given in the Installation Guide chapter, BPM Express for Hardware automaticallydetects all the various hardware components and displays them in the web-based interface.

There is no configuration or setup to be done in order to monitor the hardware of your infrastructure.All you have to do is set/modify thresholds (if required) as per your specific requirements.

This section gives details about all the components monitored by BPM Express for Hardware.

The BasicsBPM Express for Hardware requires no configuration to discover and monitor the hardware componentswithin your BMC© Performance Manager Portal environment.

Once the PM is installed after ensuring that all prerequisites have been as described in the InstallationGuide (such as installing the manufacturer-specific hardware agents etc.), and the class is added to anelement or Element Profile, an icon labeled Hardware (<platform>) appears in the Portal interface andthe PM discovers all the hardware components of the managed element.

The discovered hardware components of the monitoring element are grouped under certain container


67Monitoring


Version 2.7.28

icons. Here is a the structure of how the monitored elements are displayed in the Portal interface:

Hardware Com ponents Structure

In the left pane of the Status tab, the hardware component icons are shortened as follows:

EnvironmentFans - FAN

Temperature - TEMP

Power Supply - PS

Voltage - VOLT

� DisksLogical disk - LD

Physical disk - HD

Disk Controller - CTRL

� Devices

68Monitoring


Version 2.7.28

Blade - BL

Processors - CPU

Memory Module - MEM

Other Device - name of the actual "other device" as reported by the underlying instrumentationagent

Network Interface - NET

BPM Express for Hardware sets thresholds by default on all parameters, but you can modify thethresholds as per your specific requirements.

The Reference Guide gives details for each application class and their parameters.

Monitoring the EnclosureOn certain platforms, like DELL PowerEdge computers and IBM xSeries computers running Windows orLinux, BPM Express for Hardware can detect if the enclosure of the machine is open.

This intrusion that is detected could mean that somebody has gained physical access to the machine, aswell as its internal components, especially the physical disks with all the data. It is therefore quitehelpful to monitor the enclosure status of servers. Depending on the platform, for each enclosurediscovered, the Status, Power Consumption and Intrusion Status parameters are displayed.

Monitoring the enclosure

Basically, the enclosure instance represents the computer's main chassis of the element.

The Intrusion Status parameter, when available, raises an alert when the enclosure is opened.

The Power Consumption parameter when available, displays the power consumed by theelement in Watts.

The Status parameter, if collected, represents the overall status of all the classes of monitoredelement.

69Monitoring


Version 2.7.28

Monitoring the Environment: Fans,Temperatures, Power-Supplies and VoltagesBPM Express for Hardware automatically detects the information sources available on the monitoredcomputer and displays the hardware information provided by those sources in the Portal interface. It isthe Environment icon that regroups the icons created for each sensor found for Fans, Temperature,Power Supplies and Voltages. The icons are created automatically.

In the left pane, click on an Element > Hardware (<platform>) > Computer Type >Environment to see the discovered hardware components in detail in the right pane. Similarly byclicking on any hardware component in the left pane, you can see details about it in the right pane. Foreach monitored element, graphs & text reports are built by polling the parameter instances every fiveminutes. To view these graphs or text reports from the Status tab:

Monitoring the Env ironm ent: fans, tem peratures and v oltages

1. Click the parameter > click the corresponding History icon that appears in the right pane.

2. For parameters with numeric values or Boolean values such as: Temperature, Voltage, Speed,Speed Percent and Used Capacity, you can see the results either in Chart view (graph) or Tableview (for parameters with text values)

Alert Thresholds: Depending on the type of platform and sensors, and whenever possible, alertthresholds are automatically set by BPM Express for Hardware. When the parameter value breachesthese thresholds, it is Status - a text parameter that displays the overall status for every instance, thattriggers alerts, and a notification is sent out according to the options configured in the Portal.

If a device appears to be missing, the Status parameter will trigger an alert. Alert conditions forStatus describe in symbolic terms what occurs in the Status parameter when thresholds arebreached: one exclamation mark triggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the device have beenbreached, the Status parameter will report for example: “WARNING! The fan speed is too low” or,

70Monitoring


Version 2.7.28

“ALARM! This fan has stopped working” etc. The history graph shows the exact details of the problem,its consequences and recommended actions.

FansTo avoid temperatures that are too high, system manufacturers install fans on critical devices(processors, power supplies, etc.). Monitoring fans is important as they ensure a proper temperaturefor the system to work efficiently. Depending on the available information, the Speed and/or SpeedPercent and/or Status parameters will be displayed for each detected fan device:

The Speed parameter represents the speed of the corresponding fan in rotations/minute. An alertis triggered if the fan speed is too low for proper functioning.

The Speed Percent parameter represents the speed of the corresponding fan in percentage of itsmaximal speed.

The Status parameter represents the overall status of the fan. An alert is triggered if any of theparameters breach their respective thresholds. It is only Status that will trigger and display thealerts. When all is fine, Status shows “OK”, and when there is problem, it shows “WARNING!” or“ALARM!!” with a detailed description of the issue, its consequences and recommended actions. Thealert conditions for Status are: “!”=WARNING; “!!”=ALARM . Example: “OK”, or, “ALARM!! This fanis not detected anymore”.

TemperaturesAs with any electronic device, chips and other components of a computer stop working when thetemperature rises too high (many unrecoverable errors, crashes and even hardware damage).Temperatures may rise too high when the device is abnormally overloaded, when a fan is not workingproperly or when the ambient temperature is too hot. Monitoring the temperatures of critical devices ofyour system allows you to take action before a crash occurs.

Depending on the available information, the Temperature and/or Status parameters will be displayedfor each detected temperature sensor:

The Temperature parameter represents the current temperature reading in degrees Celsius (°C).

The Status parameter represents the overall status of the temperature. An alert is triggered if thetemperature rises to high, or i.e. if any of the other parameters breach their respective thresholds.It is only Status that will trigger and display the alerts. When all is fine, Status shows “OK”, andwhen there is problem, it shows “WARNING!” or “ALARM!!” with a detailed description of the issue,its consequences and recommended actions. The alert conditions for Status are: “!”=WARNING;“!!”=ALARM. Example: “OK”, or, “ALARM!!. The temperature is critically high”.

71Monitoring


Version 2.7.28

Power SuppliesThe power supply is the component that transforms the AC Line into electric power needed by thecomputer. Therefore the power supply is a highly critical device of a computer that should never fail.Due to this, many vendors build servers with redundant power supplies. Monitoring power suppliesallows the operators to be alerted when a power supply fails, or even in some cases when a powersupply is overloaded.

Depending on the available information, the Used Capacity and/ or Status parameters will bedisplayed for each power supply or power unit device:

The Used Capacity parameter represents the current power usage as a percentage. The Statusparameter triggers an alert when the power supply’s maximum power output is reached.

The Status parameter represents the overall status of the power supply. An alert is triggered ifpower output goes out of range, or i.e. if the parameter for breaches its thresholds. It is Statusthat will trigger and display the alerts. When all is fine, Status shows “OK”, and when there isproblem, it shows “WARNING!” or “ALARM!!” with a detailed description of the issue, itsconsequences and recommended actions. The alert conditions for Status are: “!”=WARNING;“!!”=ALARM. Example: “WARNING! Problem: This power supply is in degraded state, or about to failor “ALARM!! The power consumed by the system is out of the supported range".

VoltagesPower supplies convert the AC line power into voltages and currents needed by the motherboard of thecomputer. The stability of the motherboard (and therefore that of the overall computer) stronglydepends on this power converter. Voltages that are too low or too high may lead to unpredictablesystem crashes. Monitoring the value of the different voltages needed by the motherboard will help indetecting unstable system instability.

Depending on the available information, the Voltage and/or Status parameters are displayed for eachvoltage sensor on the motherboard:

The Voltage parameter represents the voltage output in milliVolts (mV). An alert is triggered bythe Status parameter if the voltage goes out of the proper range.

The Status parameter represents the overall status of the voltage. It triggers an alert if the voltageoutput is too low for proper functioning or if it goes out of the proper range. It is only Status thatwill trigger and display the alerts. When all is fine, Status shows “OK”, and when there is problem,it shows “WARNING!” or “ALARM!!” with a detailed description of the issue, its consequences andrecommended actions. The alert conditions for Status are: “!”=WARNING; “!!”=ALARM. Example:“OK” or “ALARM!! This voltage sensor is no longer detected".

Monitoring Disks: Physical Disks, Logical Disksand Disk ControllersBPM Express for Hardware automatically detects the information sources available on the monitoredcomputer and displays the hardware information provided by those sources in the Portal interface.

It is the Disks icon that regroups the icons created for each sensor found for logical disks, physicaldisks, and disk controllers. If the components are detected, the icons are created automatically. In the

72Monitoring


Version 2.7.28

left pane, click on an Element > Hardware (<platform>) > Computer Type > Disks and see thediscovered components in detail in the right pane. An icon is created for each storage-related devicediscovered: physical disks, logical disks and disk controllers. Each icon is labeled with a description ofthe device: ID, size, vendor, role, etc. By clicking on the disk in the left pane, you can see its details inthe right pane.

Monitoring disks: disk controller, phy sical disks, logical disks

An icon will be created for a disk controller only if its parameters discover some values. If not, then the disk controllerdetails will be mentioned in the "A ttached to" parameter of the logical/physical disk.

Each of these disks also display which disk controller they are attached to. If a device appears to bemissing, the Status parameter will trigger an alert. Status is a text parameter that describes theoverall status of the corresponding device or sensor. It is the Status parameter that raises alerts whenany of the other parameters for the device breach their thresholds. Alert conditions for Status describein symbolic terms what occurs in the parameter when thresholds are breached: one exclamation marktriggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds have been breached, theStatus parameter will report, for example: “WARNING! This disk is about to fail” or, “ALARM!! Thislogical disk is no longer detected” or as may be the case. The history graph shows the exact details ofthe problem, its consequences and recommended actions.

Physical DisksPhysical disks must be monitored to avoid loss of data, unavailability and performance degradation.When available, the S.M.A.R.T. technology is used to warn of a disk failure before it occurs.

Depending on the available information, the Predicted Failure, Error Count and Status parameterswill be displayed for each discovered physical disk:

73Monitoring


Version 2.7.28

The Predicted Failure parameter uses the S.M.A.R.T. technology to predict physical disk failures.An alert will be triggered by the Status parameter if it is predicted that the Physical Disk will soonbreak down.

The Error Count parameter is incremented each time an error occurs on this physical disk. Analert is raised by the Status parameter from the first detected error. The Status parameterrepresents the overall status of the physical disk and an alert is triggered if the physical disk is notavailable for proper operation or if any of the other parameters breach their thresholds.

The Status parameter represents the overall status of the physical disk. It triggers an alert if thephysical disk is missing or not fully operational or if any of the other parameters have breachedtheir thresholds. It is only Status that will trigger and display the alerts. When all is fine, Statusshows “OK”, and when there is problem, it shows “WARNING!” or “ALARM!!” with a detaileddescription of the issue, its consequences and recommended actions. The alert conditions forStatus are: “!”=WARNING; “!!”=ALARM. Example: “OK” or “ALARM!! This physical disk is no longerdetected."

The Attached to parameter states which disk controller the physical disk is attached to.

The "Status" parameter reports an “ALARM!!” if the "Error Count" parameter is greater than zero (that is: the diskencountered some errors). Since the counter is reset every 24th hour, the corresponding alert on the Statusparameter will automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal toreport pure event-driven alerts with no need for manual acknowledgment from the operators.

74Monitoring


Version 2.7.28

Logical DisksRAID or advanced disk controllers expose several physical disks as a single logical disk to the operatingsystem. The status of a logical disk typically corresponds to the status of a RAID array (on-line,degraded, rebuilding, etc.). For each logical disk discovered, the parameters displayed are:

The Error Count parameter represents number of errors encountered by the Logical disk since thelast counter reset. The error count is automatically reset every 24th hour (by default; this setting isconfigurable).

The Status parameter represents the overall status of the logical disk. It triggers an alert if thelogical disk is missing or if any of the other parameters have breached their thresholds. It is only Status that will trigger and display the alerts. When all is fine, Status shows “OK”, and when thereis problem, it shows “WARNING!” or “ALARM!!” with a detailed description of the issue, itsconsequences and recommended actions. The alert conditions for Status are: “!”=WARNING;“!!”=ALARM. Example: “OK” or “ALARM!! This logical disk is no longer detected."

The Attached to parameter states which disk controller the logical disk is attached to.

For non-RAID disk controllers (as most of IDE controllers, for example), no logical disk will bedisplayed.

The "Status" parameter reports an “ALARM!!” if the Error Count parameter is greater than zero (that is: the diskencountered some errors). Since the counter is reset every 24th hour, the corresponding alert on the Statusparameter will automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal toreport pure event-driven alerts with no need for manual acknowledgment from the operators.

Disk Controller

A disk controller is a card inside a computer that connects one or several physical disk drives to thiscomputer. Some intelligent disk controllers (such as RAID controllers) manage several physical disks asa single logical disk which is the only disk exposed to the operating system. Monitoring both physical andlogical disks is essential to ensure that storage is available.

Depending on the system and the information available, the Battery Status and Controller Statusparameters are displayed.

The Battery Status parameter triggers an alert to predict that the disk controller battery will beunable to support the controller in the event of a power failure.

The Controller Status parameter displays the status of the disk controller.

The disk controller icon is displayed only if either/both of the parameters collect some values. If novalues are collected, there will be no separate icon for the disk controller, but the logical disk andphysical disk instances display the details of the disk controller the disks are attached to.

A ll sy stems may not be able to prov ide this information.

75Monitoring


Version 2.7.28

Monitoring Devices: Processors, MemoryModules and Network interfacesBPM Express for Hardware automatically detects the information sources available on the monitoredcomputer and displays the hardware information provided by those sources in the Portal interface.

It is the Devices icon that regroups the icons created for each sensor found for the processors,memory modules, network interfaces. If the components are detected, the icons are createdautomatically.

In the left pane, click on an Element > Hardware (<platform>) > Computer Type > Devices andsee the discovered components in detail in the right panel. An icon is created for each detected device.Each icon is labeled with a description of the device: ID, size, vendor, role, etc.

Clicking the icon in the left pane, displays its details in the right pane. If a device appears to be missing,the Status parameter will trigger an alert if necessary.

Monitoring dev ices: CPUs, m em ory m odules, network interfaces and other dev ices

Status is a text parameter that describes the overall status of the corresponding device or sensor. It isthe Status parameter that raises alerts when any of the other parameters for the device breach theirthresholds. Alert conditions for Status describe in symbolic terms what occurs in the parameter whenthresholds are breached: one exclamation mark triggers a warning; two exclamation marks raise analarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the device have beenbreached, the status parameter will report for example: “WARNING! This network adapter hasdegraded” or, “ALARM! This network adapter is not detected anymore” or as may be the case. Thehistory graph shows the exact details of the problem, its consequences and recommended actions.

76Monitoring


Version 2.7.28

The "Status" parameter reports an ALARM if the "Error Count" and "Corrected Error Count" parameters report valuesgreater than zero (that is: the disk encountered some errors). Since the counter is reset every 24th hour, thecorresponding alert on the "Status" parameter will automatically be cleared after 24 hours. This mechanism enablesBPM Express for Hardware/Portal to report pure event-driven alerts with no need for manual acknowledgment fromthe operators.

ProcessorsProcessors (also called CPU, Central Processing Unit) are obviously the most critical devices within acomputer. While a processor fault may often lead to a system crash without a chance for a monitoringtool to catch the error, it can still be useful to monitor a server’s processors.

In the case of a system crash due to a processor fault, the system reboots automatically. The reboot iseither triggered by the operating system or by the motherboard itself. If a processor is no longerworking, it is automatically disabled by the BIOS and, if there is one processor left, the operating systemstarts with one processor less.

BPM Express for Hardware monitors each processor and checks that it is present and running. If aprocessor is missing upon reboot, BPM Express for Hardware will trigger an alert. On some recent orhigh-end servers, processors are able to correct some operation errors by themselves (like the ECCmemory). If this information is available, it is displayed in the Portal by BPM Express for Hardware. Inaddition, if the processor is able to predict a failure, this information will be monitored by BPM Expressfor Hardware and reported in the Portal interface.

Depending on the information available, the Status and/or Corrected Error Count and/or PredictedFailure parameters will be displayed for each discovered processor (CPU):

The Status parameter represents the overall status of the processor. An alert is triggered if theprocessor is not available for proper operation (missing, disable by the BIOS due to a POST error,etc.) or if any if the other parameters breach their thresholds.

The Predicted Failure parameter reports the predictive failure analysis, performed by theprocessor itself. This information is based on the rate of corrected errors.

The Corrected Error Count parameter represents the number of errors that have beenautomatically corrected by the processor. This information can be very useful to predict a failure inthe near future.

77Monitoring


Version 2.7.28

Memory ModulesThe main memory of a computer is actually as critical as the processors since almost all processoroperations deal with the memory. A single memory fault will lead to severe computer crash with,potentially, data corruption. On servers, the memory modules (the devices where the memory data isactually stored) often include auto-correction features (ECC), and sometimes even better: RAID5-likememory configuration. These features and configurations allow the memory modules to report statisticson failures, to predict failures, to hot-replace a memory module upon failure, etc.

Depending on the available information and the features provided by the motherboard and the memorymodules, the Error Count and/or Predicted Failure and/or Status parameters will be displayed foreach discovered memory module:

The Error Count parameter reports the number of errors that have been detected by the memorymodule and then corrected. A steadily growing value means that the memory module is not reliableand that it could encounter errors that it is unable to correct and that will then crash the system.

The Predicted Failure parameter is reported by the memory modules which try to predict if it isgoing to fail by analyzing the trend of the number of detected/corrected errors (thanks to the ECCtechnology). If this parameter goes into alarm, you should remove the faulty memory module andreplace it with a new one.

The Status parameter represents the overall status of the memory module. An alert is triggered ifthe memory module reports a failure (in a RAID5-like configuration), if it is missing after acomputer reboot or if any of the other parameters breach their thresholds.

Network InterfacesNetwork interfaces are devices that serve as a common interface for various other devices within a localarea network (LAN), or as an interface to allow networked computers to connect to an outside network.It is therefore essential to make sure these devices are properly running and linked to the network. Foreach network interface discovered, the Status, Error Percent and/or Link Status parameters aredisplayed:

The Status parameter represents the overall status of the network interface. An alert is triggeredwhen the network interface is not responding, or any of the other parameters’ thresholds arebreached.

The Link Status parameter reports whether or not the adapter is properly linked to the networkfrom a pure hardware cable perspective (it will not report a bad IP configuration for example). Bydefault, the Link Status parameter raises an alert (through Status) only for previously connectednetwork adapters that are no longer linked to the network.

The Error Percent parameter represents the percentage of sent and received network packetsthat were in error. A high percentage of errors often means that the network link is improperlyconfigured or that the network card is functioning poorly and thus needs to be replaced.

Missing Device DetectionThe missing device detection mechanism of BPM Express for Hardware alerts operators when a devicethat was previously detected in the system is no longer found.

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

78Monitoring


Version 2.7.28

software. When a device is no longer discovered, its Status parameter goes into alarm and its labeldirectly shows that it is missing.

Monitoring ConnectorsWhen a BPM Express for Hardware connector has been detected as applicable to the current platform, acorresponding instance is created under Infrastructure > Element > Hardware (<platform>) >Detected Connectors and its status is monitored regularly to ensure that the underlying technology isstill available.

Example

BPM Express for Hardware is running on a Dell PowerEdge server with Dell OpenManage ServerAdministrator.

Upon startup, BMC Performance Manager Express for Hardware detects Dell OpenManage ServerAdministrator and starts using the corresponding connector to discover the server hardwareconfiguration and monitor the discovered devices.

BPM Express for Hardware creates an icon representing the Dell OpenManage Server Administratorconnector.

Every 5 minutes, its Status parameter is updated.

If, for some reason, the Dell agent stops working, an alarm is raised on the Status parameter andall the components discovered and monitored through this connector go off-line.

Monitoring connectors

This connector monitoring mechanism helps administrators detect hardware agent failures. It provides ahigher monitoring accuracy by not confusing errors encountered by devices with errors caused due tofailure of the monitoring tool. The parameters for the connector monitoring class are:

79Monitoring


Version 2.7.28

Test Report: This parameter describes the tests run to evaluate the availability of the technologiesused by this connector to monitor the system.

Status: This parameter displays the overall status of the connector and it is this parameter thattriggers the alerts if any of the parameters of the class breach their thresholds.

Reporting

Ethernet/Fiber Port Traffic ReportBMC Performance Manager Express for Hardware enables you to generate a report showing usagestatistics returned by a specific Ethernet/fiber port. The report shows the total number of received andtransmitted bytes for the selected port. It can easily be customized to show the data that administratorscan use to optimize network traffic.

To generate an Ethernet/Fiber Port Traffic Report, click on the discovered Network / FC instance >“Reports” tab

Select the data you wish to generate a report for: Received or Transmitted byte traffic

Select the period that you wish the report to cover: number of days or hours

Select the interval to apply to the report data: hourly or daily

Report – Ethernet/Fiber Port Traffic Report

So from the above report you can see that 0.4759 GB were received and 0.5274 GB were transmitted onthe 22nd. Whereas on the 23rd, 1.65 GB were received and 41 GB were transmitted.

80Reporting


Version 2.7.28

Energy Usage ReportEnergy consumption has emerged as important concerns in systems and services management. In orderto provide accurate and helpful information on the energy consumed by hardware components, BPMExpress for Hardware provides an energy usage report that can be customized to show how the poweris being consumed.

To generate an Energy Usage Report, click the container Capacity Report > “Reports” tab.

Select the data you wish to generate a report for: Energy Usage (kWh) or Power Consumption (watts)

Select the period that you wish the report to cover: number of days or hours

Select the interval to apply to the report data: hourly or daily

Report – Energy Usage Report

From the above report you can see that the server have consumed 4 kWh of energy and 175 watts ofPower on the 22nd.

So calculating for a period of one week:

Energy used: 27 to 28 kWh

Power Consumed: 1225 watts

81Reporting


Version 2.7.28

Thresholds

By default, BPM Express for Hardware automatically sets alert thresholds on the parameters ofmonitored elements. Depending on the computer it is running on - BPM Express for Hardware setsdifferent thresholds for the different parameters (temperature, voltage etc.).

How thresholds are set by BPM Express for Hardware

BPM Express for Hardware dynamically sets the thresholds on all of its parameters, depending on theplatform it runs on. It receives the threshold values from the underlying instrumentation layer of theelement. This is why a summary table of alert thresholds cannot be provided - they differ from systemto system.

The alerts, i.e. the warnings and alarms are configured to be automatically raised via the Statusparameter of each class. For example, a voltage instance has two parameters: Status and Voltage.When thresholds on the Voltage parameter are breached - by default the alert is displayed by theStatus parameter icon, and not the Voltage parameter icon.

The Status param eter display s the alert

When default thresholds are modified, the alerts are displayed by the icon of the parameter whose thresholds havebeen modified. See Modify ing Parameter Thresholds

Parameters configured to trigger alertsIt is only Status, the text parameter that shows the overall status of each monitored element anddisplays the alert conditions of warnings and alarms. For example, let's take the case of a networkinterface, which has the following instances under it:

Link Status: Indicates whether or not the card is pluggedValues: Plugged = OK; Unplugged (if previously plugged in) = Alarm

Error Percent: Displays the percentage of errors detectedUnit: %10-30 = Warning; 30-100 = Alarm

Status: Displays the overall status of the instanceValues: OK; Unplugged = Warning; Critical/Missing = Alarm

If the network interface is unplugged, this information will be displayed by Link Status parameter iconin the History icon with all the details. However, only the Status icon will go into Warning. Similarly, if

82Thresholds


Version 2.7.28

the Error Percent parameter thresholds breach alarm levels, it is the Status icon that will trigger anddisplay the alarm and not the Error Percent icon.

Configuring Alert ConditionsBPM Express for Hardware detects manufacturer-set thresholds for each element and assigns thesepre-set thresholds to its symbolic conditions of exclamation marks. BPM Express for Hardware translates theregex of one exclamation mark "!" into a warning, and two exclamation marks into an alarm. By default,the alerts are triggered on the Status parameter. You can see these threshold symbols for anymonitored element in the Configure tab, under Thresholds.

Nevertheless, it is possible to modify these pre-set thresholds via the Configure tab in the Portal. Youmust however remember that you have to disable the thresholds for the Status parameter (which willotherwise continue to consider pre-set thresholds), and instead directly assign custom threshold valueson individual parameters of the class.

Starting with version 2.7.17, BPM Express for Hardware manages the display of parametersdynamically. This was rendered possible by creating separated parameter definition files for eachparameter of an application class. Therefore, for application class that has more than one parameter, acombination of different parameters was created. This may result in the display of several occurrencesof the same application class. For example, the Application class: Physical Disk has 3 parameters:

Status

Predicted Failure

Error Count

Therefore, 7 parameter definition files were created in order to define each parameter and the possiblecombination of all the parameters. That is:

83Thresholds


Version 2.7.28

Status

Predicted Failure

Error Count

Status, Predicted Failure

Status, Error Count

Error Count, Predicted Failure

Status, Error Count, Predicted Failure

Configuring alert conditions

Consequently, we strongly recommend that you wait for all the hardware components to be discoveredbefore setting threshold values for a hardware instance to avoid having to enter thresholds for eachoccurrence of the application class.

84Thresholds


Version 2.7.28

Setting threshold v alues

Modifying Parameter ThresholdsWhenever possible, BPM Express for Hardware automatically sets thresholds for parameters. Thesethresholds are retrieved from the element's instrumentation agents and in most cases they are apt forthe system.

Generally, there is no need to modify these thresholds but in case BPM Express for Hardware cannotobtain them, or if you prefer a more fault-tolerant monitoring, you can modify the thresholds of eachparameter through the Configure tab > Edit Thresholds.

1. To modify the parameter thresholds of several hardware objects of an element, click on theHardware (<platform>) icon in the Configure tab > Thresholds, Properties andCredentials > Edit.

or

To modify the thresholds of a particular instance, click on the instance icon > Thresholds,Properties and Credentials > Edit.

Thresholds, Properties and Credentials

Click Edit to modify the thresholds

Any modification to the thresholds or any other properties of elements created using the

Element Profile mode is to be done using the Element Profile route or by clicking Override Profile

2. Disable the alert conditions in the Status parameter, i.e. un-check the boxes for Warning andAlarm.

Disabling the default alert thresholds on Status

85Thresholds


Version 2.7.28

Disable the alerts on the Status parameter by un-checking the boxes

3. Enable the alert conditions on the parameter (Temperature in the image below) by checking theboxes, and manually enter the threshold values and then click on Save.

Modify ing threshold v alues

Manually modify the thresholds on the parameter and activate the alerts

4. The "Success, changes have been saved" message indicates that the modifications have beenregistered.

Alerts, if any, will be henceforth be displayed by the Temperature parameter icon, and not theStatus icon as is the case when default thresholds are maintained.

Alerts are displayed by the parameter whose thresholds are modified.

Troubleshooting

This section lists the most frequently asked questions:

Enabling the Debug Mode

BPM Express for Hardware Shows No Monitored Components

Monitors Nothing other than Network Interfaces

Note on RSMs

Unable to See Any Disk Information

Unable to Connect to WMI

Enabling the Debug ModeBy default, BPM Express for Hardware sends only the most critical information, warning and errormessages to the Status parameter report. Most often, this information is accurate enough to ensurethat BPM Express for Hardware is functioning properly. If you encounter an issue and wish to report it tocustomer support, you will be asked to enable the Debug Mode and provide the debug output to thesupport team.

86Troubleshooting


Version 2.7.28

1. In the Configure tab > click the Element whose debug output you require.

2. Scroll down to Application Classes > click Edit.

3. Select Yes from the drop-down Debug Mode list > Save.

4. Once the debug mode is enabled, delete the files sen_hw_database_hostname_*.dat stored at %RSM_HOME%\RSMxx\server\rsm\tmp\deploy\ or restart the RSM service (restarting the RSM willaffect other PMs too).

5. Deletion of the files or an RSM restart will allow BPM Express for Hardware to perform freshdetection, discovery and collection processes.

6. By default, BPM Express for Hardware sends its debug output to: %RSM_HOME%/RSMxx/SEN_HW/sen_hw_debug_hostname.log

7. Wait for 30 minutes and then disable the debug mode by selecting No.

8. Send the debug file to the support team.

Pay attention to the file size -the debug output of BPM Express for Hardware could be very large ifenabled for several days.

BPM Express for Hardware Shows NothingEven if BPM Express for Hardware is unable to detect any available hardware information source, itshould create an icon labeled Hardware under the main computer icon.

Checking the Application Collection Status

This parameter has Boolean values: True or False

True indicates that BPM Express for Hardware is functioning

False indicates that it is not

You first need to check whether the Application Collection Status has been set to true which meansthat at least one collect has been performed. As long as this parameter is not set to true, it means thatBPM Express for Hardware has not finished (successfully or not) its collection for this server. You needto wait until Application Collection Status is set to true before investigating further.

This parameter is created by default by the Portal for every application class that is added. Hence whenyou add BPM Express for Hardware on an element, this parameter should appear.

Checking the Machine Status

The second step is to check the Machine parameter which reports whether BPM Express for Hardwareon the RSM was able to communicate with the targeted server with the credentials provided by theuser. If so, the Machine Status parameter is set to “<hostname> is alive. Detected as a <OS>system”. Otherwise, this parameter will report that BPM Express for Hardware cannot communicate withthis host. This can be due to several reasons:

87Troubleshooting


Version 2.7.28

A firewall prevents communication between the RSM and the managed server

The WMI layer has not been installed or is disabled (Windows only)

Neither SSH nor Telnet connections are allowed on the managed server (UNIX and Linux only)

The supplied credentials are incorrect

The SNMP community string is wrong

If the Machine Status is OK, you need to check which connectors are detected as valid for thetargeted server, and compare them to the expected list of connectors (as described in the InstallationGuide).

Checking Connector Detection

If one or several connectors are not detected as valid for the targeted server, you should enable thedebug mode of BPM Express for Hardware, and send Sentry Software the debug output. The followingreasons could cause BPM Express for Hardware to exclude connectors.

Several reasons may prevent a connector from being used:

The SNMP community string is wrong (only for SNMP-based connectors)

The administrative/root credentials are missing or incorrect (only for connectors which need suchroot/administrative privileges)

The corresponding hardware agent is not installed or running

Some instrumentation drivers required by the hardware agent are missing

Monitors Nothing Other than Network InterfacesThis is typically an SNMP issue. Many manufacturer-provided hardware agents use the SNMP technology(DELL OpenManage, HP Insight Management, and Fujitsu-Siemens ServerView for example). Since BPMExpress for Hardware gathers hardware information from these agents, you need to enable andproperly configure the SNMP layer on the managed servers if an SNMP-based agent is running on them.

However sometimes, like in the case of HP® (Compaq®) ProLiant® servers, the network interface isdetected and displayed whilst no other hardware component is detected by BPM Express for Hardware –simply because it cannot communicate with the managed element. So enabling and authorizing themanaged server to communicate through the SNMP protocol is essential.

Configuring SNMP on Windows servers 2003, 2008Starting with Windows Server 2003, the SNMP service is not configured to allow the "public" communityby default. As a consequence, even if the SNMP service is properly installed and the hardware agentproperly running, BPM Express for Hardware is not able to gather any hardware information from theSNMP agent. Therefore, on Windows Server computers that run an SNMP-based hardware agent (DELLOpenManage, HP Insight Management or Fujitsu-Siemens ServerView), you first need to install theSNMP service (not installed by default) and then configure it to allow a community to access the SNMPagent.

88Troubleshooting


Version 2.7.28

1. In the Services administrative tool, right-click SNMP service > Properties. Click Security:

Troubleshooting: SNMP Serv ice - Properties

2. Click on the first Add button and enter a community name that will allow access to the SNMP agent(READ ONLY):

Troubleshooting: SNMP Serv ice Configuration

3. Click OK. The new settings are taken into account immediately.

4. Next, you enter the community string for this server on the Portal: Log on as a user > Configuretab > Elements

5. Expand your infrastructure tree and select the element for which you need to enter the SNMPcommunity string > Edit.

6. Scroll down to Application Classes section > Hardware (<platform>) > Edit > Propertiesand Credentials.

7. Enter the SNMP community string in order to enable BPM Express for Hardware to monitor allhardware components of the element and not just network interfaces.

On officially un-supported servers running W indows or Linux , BPM Express for Hardware will still be able to monitornetwork cards and internal non-RA ID disks.

89Troubleshooting


Version 2.7.28

Reinitializing Certain ParametersDue to the inner mechanism of servers, and that of BPM Express for Hardware, certain parameters havea tendency to trigger alerts far too frequently.

Generally, these alerts do not indicate a grave problem, and are more of a nuisance to administratorswho have to deal with them all the time. Error Count and Corrected Error Count are two suchparameters. Reinitializing these parameters automatically reduces the triggering of such “ignorable”alerts.

For this reason, BPM Express for Hardware has configured Error Count and Corrected Error Countto be re-initialized every 24hrs by default. This time-frame is customizable. Basically, here’s whathappens:

When BPM Express for Hardware detects the parameter Error Count for the first time, it notes thenumber of errors encountered, and keeps that “1st discovered” number as a base–count.

After which, each time it discovers an Error Count greater than this recorded base-count (whichbecomes its “threshold”, it triggers an alert through the Status parameter of that class. This, asyou can tell, happens far too often. It is the same with Corrected Error Count.

Now, configured by default to “re-initialize” every 24hrs, it is programmed to take the last recorded Error Count/Corrected Error Count as the new “base-count or threshold” for the fresh roundafter reset. This is the inner mechanism, the display shows that on reset the count is zero, and if itincreases to one, an alarm is triggered.

Example

Let’s say the very first discovered Error Count for Logical Disk is 40.

Now onwards, every time, BPM Express for Hardware “discovers” the Logical disk, and it meetsan Error Count of any value greater than 40, the Status parameter of that instance will triggeran alert.

Remember it is programmed for reintialization every 24hrs. So, suppose during the last“collect” just before the reset takes place, the Error Count is ‘48’, BPM Express for Hardwarewill record ‘48’ as the “base-count” for the next round after re-initialization.

Hence after 24hrs (or the time you set: 6hrs, or 1hour etc), the base-count/threshold for ErrorCount will be 48, and so on and so forth.

Classes that contain “reinitializable” parameters:Error Count applies to:

90Troubleshooting


Version 2.7.28

Logical Disk

Memory

Physical Disk

Corrected Error Count applies to:

CPU

Unable to See Disk ControllerOn some computers, the vendor-specific hardware monitoring agent is only responsible for themonitoring of the baseboard: temperatures, fans, voltages and power supplies. In this case, the diskmonitoring is handled by the disk controller manufacturer. Therefore, you need to install additionalsoftware for your disk monitoring. Please contact your server vendor to know which software must beused with your disk controller.

Unable to connect to WMIAt times BPM Express for Hardware is unable to connect to WBEM. There could be two reasons for this:

1. A firewall blocks the WBEM protocol

2. The user does not have sufficient connection rights

Firewall is blocking the WMI protocolIn such a case, you are required to set the port for RPC/DCOM connections. WMI uses RPC/DCOM, soenabling the DCPM across the firewall should allow it to work. When WMI connects to a remote machineit uses port 135 for the initial negotiation, and then a random port is allocated for further connection.Stated below are two links that will help in setting a range of ports for the RPC/DCOM connection. Onceyou have set a range for RPC/DCOM communication, you can then configure the firewall to allow trafficthrough this range of ports.

http://support.microsoft.com/default.aspx?scid=kb;en-us;154596

http://msdn.microsoft.com/en-us/library/aa389286(VS.85).aspx

Insufficient connection rightsThis means that the user credentials provided are insufficient to access WMI. This error occurs when

the connected user is not recognized or is restricted in some fashion by the remote server (forexample, the user might be locked out). The reasons may be the following:

Accounts are in different domains

Recent changes made to WMI security:

Blank passwords, formerly permitted, are not allowed in Windows XP and Windows Server 2003

The DCOM configuration access setting might have been changed

If the target computer is running Windows XP, the Force guest value under the registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa might be set to force the Guestaccount off (value is zero)

Request your network administrator to accord sufficient rights to the user credentials.



http://msdn.microsoft.com/en-us/library/aa389286(VS.85).aspx

Reference Guide

92


Version 2.7.28

This chapter provides the following detailed chapters:

Classes and Parameters: Parameters, info boxes and menu commands for each application class

Connectors and Platforms: supported platforms, instrumentation agents or system tools theyrequire as well as the connectors that are used to monitor them. Details are given for eachconnector and show all the components discovered and monitored through them.

Application Classes

This section familiarizes you with all the Application classes used by BMC Performance Manager Expressfor Hardware on the Portal. It gives a detailed view of each application class describing its function andparameters.

Baselines and Key Performance Indicators

Some parameters are identified by default as Key Performance Indicators (KPIs) and thereforeautomatically included in the base lining calculation. To learn more about auto baselining and KPIs,please refer to the Managing Baselines and Key Performance Indicators chapter.

In this guide, parameters flagged as KPIs and included by default in the baseline calculation process arerespectively identified by the following icons:

Baselining

KPI

BatteryThe Battery class can be a child of the Enclosure and Disk Controller classes.

Parameters

Name Description Unit Alert Conditions

Charge Displays the percentage of the battery charge. Percentage(%)

≤ 50% Warning ≤ 30 % Alarm

Locator Helps to physically locate a component. n/a n/a

Status Displays the battery status. Values:OK;Warning;Alarm

“!” = Warning“!!” = Alarm

For detailed information about B a se lining, see Managing Baselines and Key Performance Indicators.

93Application Classes


Version 2.7.28

BladeEach instance of the Blade class represents a blade server inside a blade enclosure. The Statusparameter represents the global status of the blade.

Parameters



Status Displays the overall blade status. Values:OK;Warning;Alarm


"Status" is a tex t parameter that gives the overall status of the corresponding dev ice or sensor. An alert conditiondescribes in symbolic terms what occurs in the parameter when thresholds are breached: one exclamation marktriggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that a blade has exceeded manufacturer-specified thresholds,the Status parameter will report “Warning! or Alarm!! The blade is missing”, or as the case may be.On clicking the history graph, you can see the exact problem details, the consequences and therecommended actions.

Depending on your system, all parameters may not be used.

Capacity ReportParameters


ConnectedEthernet/Fiber Ports

Total number of connected Ethernet/Fiber Ports ConnectedEthernet/FiberPorts

n/a

DegradedDevice Count

Total number of degraded devices Device(s)

Warning ≥ 1

DegreesBelow

Warning

Degrees left before reaching the defined threshold Celsiusdegrees (C°)

n/a



Version 2.7.28

EnergyUsage

Energy usage of the system Kilowatthour(kWh)

n/a

Failed DeviceCount

Total number of failed devices Device(s)

Alarm ≥ 1

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

n/a

MissingDevice Count

Total number of missing devices Device(s)

Alarm ≥ 1

Physical CPUCount

Host total number of physical processors (CPU) Physicalprocessors(CPU)

None

PowerConsumption

Power consumed by the host Watts(W)

n/a

Total LogicalDisk Size

Host total logical disk size Terabytes (TB)

n/a

TotalPhysical DiskSize

Host total physical disk size Terabytes (TB)

n/a

TotalUnallocatedSpace

Host Total available disk space that is not allocated to anyvolume.

Gigabytes (GB)

n/a




Version 2.7.28

ConnectorEach instance of the Connector class represents a connector currently used by BPM Express forHardware in order to discover and monitor the hardware components of the server.

Connectors are continuously monitored to ensure that the underlying technology used by BPMExpress for Hardware to discover and monitor the hardware functions properly.

If something goes wrong with the hardware instrumentation layer (but not with the hardwareitself), an alert is raised by the Status parameter of the corresponding Connector instance.

In this case, hardware components that were discovered and monitored through this connector willno longer be monitored. Check the Test Report parameter to have more details about theconnector failure.

Parameters


Status Displays the overall connector status Values:OK;Warning;Alarm


Test Report Describes the tests performed to evaluate the status of theconnector

n/a n/a

"Status" is a tex t parameter that gives the overall status of the corresponding dev ice or sensor. An alert conditiondescribes in symbolic terms what occurs in the Status parameter when thresholds are breached: one exclamationmark triggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that a connector has exceeded a manufacturer-specifiedthreshold, the Status parameter will report "Alarm!!. This connector is not working anymore". Onclicking the history graph, you can see the exact details of the problem, its consequences and therecommended actions.


CPUEach instance of the CPU class represents a physical processor of the server. On high-range servers,the Status parameter will raise an alert "on the fly" as soon as a processor fails. On most servershowever, a failed processor causes a server crash. Upon reboot, the processor is likely to beautomatically disabled by the BIOS which will then raise an alert in BPM Express for Hardware becausethe processor is "missing".



Version 2.7.28

The Corrected Error Count and Predicted Failure parameters (available only for a few high-end processors) help administrators intervene before such a crash occurs.

The "Status" parameter will report an A larm if the "Corrected Error Count" parameter is greater than zero (that is:the disk encountered some errors). Since the counter is reset every 24th hour, the corresponding alert on the"Status" parameter will be automatically cleared after 24 hours. This mechanism has been implemented to let BPMExpress for Hardware/Portal report pure event-driven alerts with no need for manual acknowledgment from theoperators.

Parameters


CorrectedError Count

Displays the number of detected and corrected errors Errors n/a

CurrentSpeed

Displays the current clock speed of the processor inmegahertz

Megahertz(Mhz)

n/a


PredictedFailure

Triggers an alert through the Status parameter if a CPUfailure is expected

Values :OK;PredictedFailure

n/a

Status Displays the overall CPU status. Values:OK;Warning;Alarm



"Status" is a tex t parameter that describes the overall status of the corresponding dev ice or sensor. A lert conditionsdescribe in symbolic terms what occurs in the "Status" parameter when thresholds are breached: one exclamationmark triggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds have been breached for aCPU, the Status parameter will report “Warning! Problem: This processor is degraded or about tofail." Or “Alarm!! This processor is not detected anymore", or as may be the case. On clicking thehistory graph, you can see the exact details of the problem, its consequences and the recommendedactions.




Version 2.7.28

CPU CoreThe CPU Core class can only be a child of the CPU class.

Parameters



Status Displays the CPU Core status. Values: OK;Warning;Alarm


Used TimePercent

Displays the percentage of the CPU core usage.The "Used Time Percent" parameter is calculated as:(UsedTime - LastUsedTime) / (currentTime - lastTime) *100

Percentage(%)

≥ 50% Warning ≥ 100 % Alarm

Disk ControllerThe purpose of the Disk Controller instance is to display the status of the disk controller battery andthe status of the disk controller. In addition, some information regarding the disk controllers, like itsbrand, model or driver version, may be displayed.

The Battery Status parameter triggers an alert to predict that the disk controller battery will beunable to support the controller in the event of a power failure.

The Controller Status parameter displays the status of the disk controller.

Parameters


BatteryStatus

Triggers an alert to predict that the disk controller batterywill be unable to support the controller in the event of apower failure.

Values: OK;Warning;Alarm


ControllerStatus

Displays the status of the disk controller Values: OK;Warning;Alarm






Version 2.7.28

EnclosureBasically, each Enclosure instance represents a box with some hardware components inside. This classis used to represents the computer's main chassis, but also external disk array enclosures or bladeenclosures.

The Intrusion Status parameter, when available, raises an alert when the chassis is opened.

The Status parameter, if collected, represents the overall status.

Parameters


IntrusionStatus

Triggers an alert if the enclosure is openedExample: "Alarm!! Problem: The enclosure is open or hasbeen removed"

Values: OK ;IntrusionDetected

“!!” = Alarm


Status Displays the overall status of the enclosure Values:OK;Warning;Alarm


"Status" is a tex t parameter that describes the overall status of the corresponding dev ice or sensor.


FanThis class creates monitoring objects for each cooling sensor it discovers. Depending on the system andthe data available, one or more parameters will be associated to the fan monitoring. Critical devices likeprocessors, power supplies etc, have fans to avoid over-heating. Monitoring fans is important becausethey ensure a proper temperature for the system to work efficiently.

Depending on the available information, the Speed and/or Status parameters will be displayed foreach detected fan device:



Version 2.7.28

The Speed parameter represents the speed of the corresponding fan (in rotations/minute). Analert is raised through Status if the fan speed is too low for proper functioning.

The Speed Percent parameter represents the speed of the corresponding fan in percentage of itsmaximal speed.

The Status parameter represents the overall status of the fan. An alert is triggered if the fan stopsspinning or does not spin fast enough.

Parameters



Speed Displays the speed of the fan Rotation PerMinute(RPM)

n/a

Speed

Percent

Displays the speed of the fan as a percentage of its maximalspeed

Percent(%) ofmaximalspeed

n/a

Status Displays the overall fan statusExample: “OK” or “Alarm!! This fan is not detected anymore”




"Status" is a tex t parameter that describes the overall status of the corresponding dev ice or sensor. A lert conditionsdescribe in symbolic terms what occurs in the parameter when thresholds are breached: one exclamation marktriggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that a fan has breached manufacturer-specified thresholds, theStatus parameter will report “Warning! This fan is degraded/is about to fail” or “Alarm!! This fan isnot detected anymore", as may be the case. The history graph shows the exact details of theproblem, its consequences and recommended actions.




Version 2.7.28

LEDThe LED instances can only be children of the Enclosure class.

Parameters


Color Color of the LED. n/a n/a


Status Led Status. Depending on the LED, On, Off or Blinking maymean OK, WARNING or ALARM. So, if "On" means OK,Status will be "On". But if "On" means "Degraded", Statuswill be "On!". And if "On" means "Critical", Status will be"On!!". Same for "Off" and "Blinking".

Values:OK;Warning;Alarm


Logical DiskThis class creates instances for each logical disk discovered. Logical disks are often a group of physicaldisks, configured as an array (RAID 0, 1, 5, etc.) and exposed to the operating system as a singlephysical volume.

The status of a logical disk typically corresponds to the status of a RAID array (on-line, degraded,rebuilding, etc.). For each logical disk discovered, the Status parameter is displayed.

The Error Count parameter represents number of errors encountered by the logical disk since thelast counter reset. The error count is automatically reset every 24th hour (by default; this setting isconfigurable).

The Status parameter represents the overall status of the logical disk. An alert is triggered whenthe logical disk is not fully operational (degraded, rebuilding, etc.) or not available at all. It triggersan alert if the logical disk missing or if any of the other parameters have breached their thresholds.It is only Status that will trigger and display the alerts. When all is fine, Status shows “OK”, andwhen there is a problem, it shows “Warning!” or “Alarm!!” with a detailed description of the issue,its consequences and recommended actions. The alert conditions for Status are: “!”=Warning;“!!”=Alarm. Example: “OK” or “Alarm!!” This logical disk is no longer detected."

For non-RA ID disk controllers (as most of IDE controllers, for example), no logical disk will be displayed.

The "Status" parameter will report an A larm if the "Error Count" parameter is greater than zero (that is: the diskencountered some errors). Since the counter is reset every 24th hour, the corresponding alert on the "Status"parameter will be automatically cleared after 24 hours. This mechanism has been implemented to let the systemreport pure event-driven alerts with no need for manual acknowledgment from the operators.

Parameters




Version 2.7.28

Error Count

Displays the number of errors encountered by the logicaldisk since the last counter reset (every 24hrs by default)

Errors n/a


Status Displays the overall status of the logical diskExample: “OK” or “Alarm!! This logical disk is no longerdetected”


“!” = Warning “!!” = Alarm



Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the logical disk havebeen breached, the Status parameter will report “Warning! This logical disk is degraded/is about tofail” or “Alarm!! This logical disk is not detected anymore", or as may be the case. The history graphshows the exact details of the problem, its consequences and recommended actions.


LUNThe LUN class can be a child of the Enclosure class.

Parameters


Status Indicates the availability of the remote volume. Values:OK;Warning;Alarm


AvailablePath Count

Number of distinct paths available to the remote volume Paths When downgrades or fewer thanexpected = Warning0 = Alarm


For detailed information about B a se lining and KP I, see Managing Baselines and Key Performance Indicators.



Version 2.7.28

MainThe Main class is responsible for the initialization of all the subclasses (i.e Fan, Logical Disk, CPU, etc).This class has just one parameter called Machine Status.

Machine Status is a text parameter that reports whether the BPM Express for Hardware on the RSM isable to communicate with the targeted remote element. It detects whether or not the remote element isaccessible for monitoring i.e. whether or not the remote element is up & running and can be monitored.Values for this parameter are: “OK” and “WARNING”.

Example for OK

“<hostname> is alive. Detected as <OS>. Protocols used: (SNMP/WBEM/ Telnet/SSH)

If this parameter reports that the application cannot communicate with this host, it could be due to anyof the following reasons:

A firewall prevents communication between the RSM and the managed server

The WMI layer has not been installed or is disabled (Windows only)

Neither SSH nor telnet connections are allowed on the managed server (UNIX and Linux only)

The supplied credentials are incorrect

The SNMP community string is wrong

None of the connectors match the platform of the remote element

Some examples of possible “Warning!” alerts:

The remote element is down.

Example

“<hostname> is down. Problem: Either the remote element is not currently running or the firewallis preventing access to the element.”

The remote element is up and running, but none of the connectors match the platform of theremote element.

Example

“<hostname> is alive. Problem: None of the connectors match this platform.”

The remote element is up and running, but the host platform cannot be detected.

Example



Version 2.7.28

“<hostname> is alive. Problem: Host platform cannot be detected.”

On clicking on the History icon, you can see the details about the problem, its consequences andthe recommended actions.

The warning "Machine Status" triggers in case of a problem, is not related to any hardware issue; allit indicates is that the BPM Express for Hardware cannot perform the detection, discovery orcollection processes on this remote element.

If one or several connectors are not detected as valid for the targeted server, you need to enable the debug modeof BPM Express for Hardware and check the debug output for the reason that led it to exclude those connectors.

MemoryEach instance of the Memory module represents a memory module in the server.

The Status parameter will raise an "on the fly" alert on servers that can dynamically handle failedmemory modules or, most often, for modules that have been disabled by the BIOS upon reboot (themodule is then flagged as "missing").

The Error Count parameter represents the number of errors that have been fixed by ECC-enabledmemory modules.

In some case, the Predicted Failure parameter is used to alert administrators that the memorymodule is about to fail.

The use of the Error Count, or Predicted Failure parameter depends on the technology beingused to report the health of memory modules.

The "Status" parameter reports an A larm if the "Error Count" parameter is greater than zero (that is: the diskencountered some errors). Since the counter is reset every 24th hour, the corresponding alert on the Statusparameter will automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal toreport pure event-driven alerts with no need for manual acknowledgment from the operators.

Parameters


Error Count

Displays the number of errors encountered since lastcounter reset (every 24hrs by default)

Errors “!” = Warning“!!” = Alarm

Error Status This parameter will trigger an alert if the number of memoryerrors reaches a threshold set by the manufacturer’s agent.Value set by memoryColl every 2 minutes.




PredictedFailure

Raises an alert through the Status parameter if a memoryfailure is expected

n/a n/a

Status Displays the overall memory status. Values: n/a



Version 2.7.28

Example: “OK” or “Warning! This memory moduleencountered an abnormal number of internal errors”

OK;Warning;Alarm



Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the memory modulehave been breached, the Status parameter will report “Warning! This memory module encounteredan abnormal number of internal errors” or “Alarm!! An imminent failure is predicted on this memorymodule”, or as may be the case. The history graph shows the exact details of the problem, itsconsequences and recommended actions.


NetworkEach Network instance represents a network adapter in the server.

The Link Status reports whether or not the adapter is properly linked to the network from a purehardware cable perspective (it will not report a bad IP configuration for example). By default, the Link Status parameter raises an alert (through Status) only for previously connected networkadapters that are no longer linked to the network.

The Error Percent parameter represents the percentage of sent and received network packetsthat were in error. A high percentage of errors often means that the network link is improperlyconfigured or that the network card is functioning erratically and thus needs to be replaced.

The Status parameter displays the overall status of the instance. It raises an alert if any of theother parameters breach their thresholds. Alerts are triggered only through the Status parameter.

Parameters


Bandwidth

Utilization

Percentage used of the available bandwidth. Percentage(%)

n/a

Connectedto PhysicalAddress

Port number to which the network card is connected. Portnumber

n/a

ConnectionType

Type of the network connection ethernet/FC

n/a



Version 2.7.28

Duplex Mode Whether the port is configured to operate in half-duplex orfull-duplex mode.

Values:Half;Full

n/a

Error

Percent

Displays the percentage of transmitted and receivedpackets in error between collects.

Percentage(%)

≥ 10 = Warning≥ 30 = Alarm

Link Speed

Negotiated or configured link speed Megabits/seconds (MB/Bitss)

≥ 10 = Warning≥ 100 = Alarm

Link Status Triggers a warning if the network interface is not connected(i.e. cable unplugged)

Values:Plugged;Unplugged



PhysicalAddress

The physical address of the network component Physicaladdress

n/a

ReceivedBytes Rate

Received network traffic in bytes per second. Bytes/seconds (B/s)

n/a

ReceivedBytes

Number of received bytes Gigabytes (GB)

n/a

Status Displays the overall status of the network interfaceExample: “OK” or “Alarm!! This network adapter is notdetected anymore”



TransmittedByte Rate

Emitted network traffic. Megabytes/seconds (MB/s)

n/a

TransmittedBytes

Number of transmitted bytes Gigabytes (GB)

n/a

For detailed information about B a se lining and KP I, see Managing Baselines and Key Performance Indicators.

"Status" is a tex t parameter that describes the overall status of the corresponding dev ice or sensor. A lert conditionsdescribe in symbolic terms what occurs in the parameter when thresholds are breached: one exclamation marktriggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the network interfacehave been breached, the Status parameter will report “Warning! This network adapter hasdegraded”,or, “Alarm!! This network adapter is not detected anymore” or as may be the case. Thehistory graph shows the exact details of the problem, its consequences and recommended actions.



Version 2.7.28


Other DeviceThis class is typically used to monitor devices that do not relate to the other classes and can rarely bemonitored on servers. The device definition is given by the connector file and the device is monitoredjust as any other in any other class.

This represents hardware components that do not fall into other predefined categories i.e. other thanprocessors, memory modules, temperature sensors, fans, voltage sensors, power supplies, networkcards, disk controllers, physical disks and logical disks.

Parameters


Status Displays the overall status of the "other device"Example: “OK” or “Alarm!! This device is no longer detected”




Usage Count Number of times the device has been used. n/a n/a


Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the “other device”have been breached, the Status parameter will report “Alarm! This device has degraded.” or “Alarm!!This device is no longer detected”, or as may be the case. The history graph shows the exact detailsof the problem, its consequences and recommended actions.




Version 2.7.28

Physical DiskEach instance of this class represents a hard drive detected on the platform by BPM Express forHardware. Its purpose is to monitor the status of each hard drive and possibly detect an incomingfailure.

Physical disks must be monitored to avoid loss of data, un-availabilities and performance degradation.When available, S.M.A.R.T technology will be used to predict a disk failure before it occurs. Dependingon the available information, the Predicted Failure and/or Status parameters will be displayed foreach discovered physical disk:

The Predicted Failure parameter uses S.M.A.R.T technology to predict physical disk failures. Analert will be triggered if it is predicted that the physical disk will soon break down. The Statusparameter represents the current status of the physical disk. An alert is triggered if the physical diskis not available for proper operation.

The Error Count parameter is incremented each time an error occurs on this physical disk. Analert is raised by the Status parameter from the first detected error. The Status parameterrepresents the overall status of the physical disk and triggers an alert is triggered if the physicaldisk is not available for proper operation or if any of the other parameters breach their thresholds.

The Status parameter represents the overall status of the physical disk. It triggers an alert if thephysical disk is missing or if any of the other parameters have breached their thresholds. It is only Status that will trigger and display the alerts. When all is fine, Status shows “OK”, and whenthere is a problem, it shows “Warning!” or “Alarm!!” with a detailed description of the issue, itsconsequences and recommended actions. The alert conditions for Status are: “!”=Warning;“!!”=Alarm

The "Status" parameter reports an A larm if the "Error Count" parameter is greater than zero (that is: the diskencountered some errors). Since the counter is reset every 24th hour, the corresponding alert on the "Status"parameter will automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal toreport pure event-driven alerts with no need for manual acknowledgement from the operators.

Parameters


Error Count

Displays the number of errors encountered by the physicaldisk.

Errors n/a


PredictedFailure

Triggers information if a failure is expected n/a n/a

Status Displays the overall status of the physical diskExample: “OK” or “Alarm!! This disk is not detectedanymore”






Version 2.7.28


Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the physical disk havebeen breached, the Status parameter will report “Warning! This physical disk is degraded/is about tofail” or “Alarm! This disk is not detected anymore", or as the case may be. The history graph showsthe exact details of the problem, its consequences and recommended actions.


Power SupplyEach instance of this class represents a power supply in the system. It is used to monitor their statusand to indicate when a power supply is malfunctioning and needs attention.

Power supply is critical and should never fail, which is why servers often have redundant powersupplies. Monitoring power supplies allows the operators to be alerted when a power supply fails, or insome cases when a power supply is overloaded. Depending on the information available, the UsedCapacity and/or Status parameters will be displayed for each power supply or power unit device:

The Used Capacity parameter represents the power supply’s power currently in use inpercentage. An alert is triggered if the computer uses too much power than it can be supplied.

The Status parameter represents the current status of the power supply. An alert is triggered if anerror occurs with the power supply.

Parameters



Status Displays the overall status of the power supplyExample: “OK” or “Alarm!! The power consumed by thesystem is out of the supported range"



UsedCapacity

Displays the percentage of the power supply currently in use Percentage(%)

n/a




Version 2.7.28


Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for power supply havebeen breached, the Status parameter will report “Warning! Problem: This power supply is indegraded state, or about to fail” or “Alarm!! The power consumed by the system is out of thesupported range", or as may be the case. The history graph shows the exact details of the problem,its consequences and recommended actions.


RoboticsThe Robotics class can only be a child of the Enclosure class.

Parameters


Error Count

Displays the number of errors encountered. Errors n/a


Move Count(Cumulative)

Number of moves performed by the robot. Moves n/a

Status Device status. Values: OK;Warning;Alarm



Tape DriveThe Tape Drive application class can be a child of the Enclosure and Disk Controller applicationclasses.

Parameters




Version 2.7.28

Error Count

Displays the number of errors encountered. Errors n/a


Mount Count Number of mounts Mounts n/a

Needs

Cleaning

No / Yes Values:No;Yes

n/a

Status Device status. Values: OK;Warning;Alarm


UnmountCount

Number of unmounts Unmounts

n/a


TemperatureBPM Express for Hardware detects the temperature probes on the motherboard or devices and createsan instance of this class for each of them. Their location in the platform is described in the instance’slabel if it is available.

When a temperature reading can be performed, temperature thresholds are automatically set and analert will be triggered if the temperature rises to a dangerous level. Even in the case that no readingcan made, the Status parameter will display the condition of the temperature in the system.

Parameters



Status Displays the overall temperature statusExample: “OK” or “Alarm!! The temperature is critically high”



Temperature

Displays the temperature reading Celsiusdegrees(C°)

n/a


"Status" is a tex t parameter which describes the overall status of the corresponding dev ice or sensor. An alertcondition describes in symbolic terms what occurs when thresholds are breached.

Example



Version 2.7.28

If BPM Express for Hardware detects that manufacturer-specified thresholds have been breached fortemperature, the Status parameter will report “Warning! The temperature is too high (67°C)” or,“Alarm!! The temperature is critically high” or, as may be the case. There is a complete hardwarehealth report for this temperature sensor. The actual temperature value (when available) is reportedby the Temperature parameter but alert thresholds are not directly set on this parameter. The historygraph will display details about the problem, its consequences and the recommended actions.


VoltageThe purpose of this class is to monitor power supply voltages. For each voltage sensor (+5V, +12V, -5V,etc.), an instance is created in a container with a label describing its type.

If the computer’s configuration allows a reading of the voltages, the values will be available in the Voltage parameter and an alert will be triggered if they do not meet the automatically set thresholds.Otherwise, the Status parameter will inform you if a problem occurs with one of the voltages.

Parameters



Status Displays the overall status of the voltageExample: “OK” or “Alarm!! This voltage sensor is no longerdetected"



Voltage Displays the voltage reading megavolt (mV)

n/a



Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for voltage have beenbreached, the Status parameter will report “Warning! Although still not critical, the voltage level is outof the normal range." or “Alarm!! This voltage sensor is no longer detected", or as may be the case.The history graph shows the exact details of the problem, its consequences and recommendedactions.



Version 2.7.28


Special Note on Application Collection StatusThis Boolean parameter shows the status of the application and its ability to collect data. A value ofFalse means that the RSM cannot communicate with or collect information for the application class onthe element.

Thresholds

BPM Express for Hardware dynamically sets the thresholds on all of its parameters depending on theplatform it is running on. This is why a summary table of the alert thresholds of BPM Express forHardware cannot be provided. It takes the manufacturer-set thresholds for each component and setsalert rules accordingly.

As you have seen in the previous section, it is Status, the text parameter that displays alert conditions.BPM Express for Hardware assigns the pre-set thresholds to its symbolic conditions of exclamationmarks.

For instance, when a manufacturer-set threshold reaches warning levels, BPM Express for Hardwaretranslates it to “Warning!” with one exclamation mark, which triggers a Warning alert in the Portal; andfor an alarm-level breach, the Status parameter is set to “Alarm!!” with two exclamation marks, whichtriggers an Alarm alert in the Portal. When a problem occurs, it is the Status parameter that reports“WARNING!” or “ALARM!!” followed by a full description of the encountered problem, the possibleconsequences and the recommended action. Nevertheless, it is possible to modify these pre-setthresholds via the Configure tab.

If you wish to modify pre-set thresholds of individual parameters, you must deactivate thethresholds for the Status parameter (which will otherwise continue to consider pre-set thresholdsand trigger alerts accordingly), and instead, directly assign threshold values against individualparameters of the class. See the User Guide for details.

Additional Configuration Properties

This section provides detailed information on how to override the default property values used withinBPM Express for Hardware. These values have to be defined in the rsmcfg.properties (%RSM_HOME%\ RSMxx\server\rsm\conf\properties\rsm\ rsmcfg.properties) file.

The following properties may be set to override the default values for a specific element or for allelements at once.

113Additional Configuration Properties


Version 2.7.28

SSH Timeout

This property allows you to override the default timeout value or the default connector specified timeoutvalue for executing a single command using SSH. The default value is 45 seconds.

Property: net.sentrysoftware.bpm.hardware.sshTimeout.default=45000

Example

To set the value for all hosts: net.sentrysoftware.bpm.hardware.sshTimeout.default=45000

To set the value for a specific host: net.sentrysoftware.bpm.hardware.sshTimeout.default.<hostname>=45000

To override the connector specified timeout value:

Property: net.sentrysoftware.bpm.hardware.sshTimeout.hdf=60000

Example

To set the value for all hosts: net.sentrysoftware.bpm.hardware.sshTimeout.hdf=60000

To set the value for a specific host: net.sentrysoftware.bpm.hardware.sshTimeout.hdf.<hostname>=60000

The <hostname> tag must be replaced with EXACTLY the hostname or IP address entered when adding the element

Telnet timeout

This property allows you to override the default timeout value or the default connector specified timeoutvalue for executing a single command using Telnet. The default value is 45 seconds.

Property: net.sentrysoftware.bpm.hardware.telnetTimeout.default=45000*

To override the connector specified timeout value:

Property: net.sentrysoftware.bpm.hardware.telnetTimeout.hdf=60000

WMI timeout

This property allows you to override the default timeout value for executing a single WMI query. Thedefault value is 45 seconds.



Version 2.7.28

Property: net.sentrysoftware.bpm.hardware.wmiTimeout.default=45000

WBEM timeout

This property allows you to override the default timeout value for executing a single WBEM query. Thedefault value is 45 seconds.

Property: net.sentrysoftware.bpm.hardware.wbemTimeout.default=45000

AWK timeout

This property allows you to override the default timeout value for executing a single AWK command.The default value is 180 seconds.

Property: net.sentrysoftware.bpm.hardware.awkTimeout.default=180000

WMI namespace

This property allows you to specify the namespace that is to be used for executing the WMI query.

Property: net.sentrysoftware.bpm.hardware.wmiNamespace=root\cimv2

WBEM namespace

This property allows you to specify the namespace that is to be used for executing the WBEM query.

Property: net.sentrysoftware.bpm.hardware.wbemNamespace=root

Force Telnet

If an element responds to both Telnet and SSH, by default BPM Express for Hardware uses SSH. Thisproperty can be set to “true” in order to force Telnet over SSH.

Property: net.sentrysoftware.bpm.hardware.forceTelnet=true

Force SSH

This property is used to specify BPM Express for Hardware to use SSH.

Property: net.sentrysoftware.bpm.hardware.forceSSH=true

Force WMI Script

By default BPM Express for Hardware uses the WMI class of BMC portal sdk to perform wmi requests.Setting this property value to “true” will force BPM Express for Hardware to use WMI Script to perform

wmi requests.



Version 2.7.28

Property: net.sentrysoftware.bpm.hardware.forceWMIScript=true

Force nAwkBy default BPM Express for Hardware uses the java native awk method to parse the result. Setting this

property value to “true” will force BPM Express for Hardware to use nAwk to parse the result. Property: net.sentrysoftware.bpm.hardware.forcenawk=true

Force SNMP Protocol ActivationThis property forces the activation of the SNMP protocol.

Property: net.sentrysoftware.bpm.hardware.snmpActivation=true

Reflect Fan Speed valueBy default in the class Fan, BPM Express for Hardware sets the parameter “Status” in alert if theparameter “Speed” exceeds the threshold value. Setting this property value to “false” will force BPM

Express for Hardware not to reflect the threshold values on parameter “Status”. Property: net.sentrysoftware.bpm.hardware.fan.speed=false

Reflect PowerSupply UsedCapacity valueBy default in the class Power Supply, BPM Express for Hardware sets the parameter “Status” in alertif the parameter “UsedCapacity” exceeds the threshold value. Setting this property value to “false” willforce BPM Express for Hardware not to reflect the threshold values on parameter “Status”.

Property: net.sentrysoftware.bpm.hardware.powersupply.usedcapacity=false

Reflect Voltage valueBy default in the class Voltage, BPM Express for Hardware sets the parameter “Status” in alert if theparameter “Voltage” exceeds the threshold value. Setting this property value to “false” will force BPMExpress for Hardware not to reflect the threshold values on parameter “Status”.

Property: net.sentrysoftware.bpm.hardware.volt.voltage=false

Reflect Temperature valueBy default in the class Temperature, BPM Express for Hardware sets the parameter “Status” in alert ifthe parameter “Temperature” exceeds the threshold value. Setting this property value to “false” will

force BPM Express for Hardware not to reflect the threshold values on parameter “Status”. Property: net.sentrysoftware.bpm.hardware.temp.temperature=false

Reflect Available Path Count valueBy default in the class LUN, BPM Express for Hardware sets the parameter "Status" in alert if theparameter "Available Path Count" exceeds the threshold value. Setting this property value to "false" willforce BPM Express for Hardware not to reflect the threshold values on parameter "Status".

Property: net.sentrysoftware.bpm.hardware.lun.availablePathCount=false

SNMP PortBPM Express for Hardware uses the default Port 161 for SNMP requests. This port number can beoverriden by setting this property value in the rsmcfg.properties file.



Version 2.7.28

Property: net.sentrysoftware.bpm.hardware.snmp.port=161

SSH PortBPM Express for Hardware uses the default Port 22 for SSH requests. This port number can beoverriden by setting this property value in the rsmcfg.properties file.

Property: net.sentrysoftware.bpm.hardware.ssh.port=22

Telnet PortBPM Express for Hardware uses the default Port 23 for Telnet requests. This port number can beoverriden by setting this property value in the rsmcfg.properties file.

Property: net.sentrysoftware.bpm.hardware.telnet.port=23

WBEM ActivationOption to activate the WBEM protocol is added by setting a value in the rsmcfg.properties file.

Properties: net.sentrysoftware.bpm.hardware.wbemActivation=true;true

Pre-Selected ConnectorsThis property will force Hardware Express to perform detection process only on the specified connectorfiles for a specified element.

Property:net.sentrysoftware.bpm.hardware.preSelectedConnectors.hostname=connector1.hdf,connector2.hdf,connector3.hdf

Perform Garbage CollectBy default, the RSM will perform garbage collect (GC) when it needs memory. This property canhowever be set to "true" to force the GC of all the elements that are using BPM Express for Hardware.GC will then be performed after each collect.

Property: net.sentrysoftware.bpm.hardware.garbagecollect=true

Disable Connectors

This property will force BPM Express for Hardware to ignore/disable the detection process of thespecified connector files for a specified element.

Property:net.sentrysoftware.bpm.hardware.disabledConnectors.<hostname>=connector1.hdf,connector2.hdf,connector3.hdf

Forcing the GC of all the elements that are using BPM Express for Hardware may have a significantimpact on performance.

117Connectors


Version 2.7.28

Connectors

This section provides detailed information on each connectors - stating the target, typical platforms, thepre-requisites for BPM Express for Hardware to function optimally, technology used, and what it willdiscover (stating precise application class names) and then, most importantly, what it will monitor.

In order to know all about the connectors for your systems, first identify your platforms/environments inthe reference table, and then read the corresponding details.

Connector and Platform Reference TableThe following table shows all the connectors provided with this versions of BMC Performance ManagerExpress for Hardware. Each connector is a file with the .hdf extension and they are stored in: %RSM_HOME%\RSMxx\server\rsm\tmp\deploy directory.

Connector Name Connector File Typicalplatform

Operating System

Adaptec - StorMan - RAID MS_HW_AdptStorManUnix.hdf Sun Fire (x64) Sun Solaris, Linux

Adaptec IOManager MS_HW_IOManager.hdf Fujitsu-SiemensPRIMERGY

Microsoft Windows, Linux

Adaptec Storage Manager(DPT)

MS_HW_DptStorageManager.hdf Fujitsu-SiemensPRIMERGY


Adaptec Storage ManagerWeb Edition (AAC)

MS_HW_AAC.hdf Fujitsu-SiemensPRIMERGY


Brocade SAN Switch SMIAgent

MS_HW_BrocadeSwitchWBEM.hdf SAN Switches Storage Device

Brocade SAN Switch MS_HW_BrocadeSwitch.hdf SAN Switches Storage Device

Cisco MDS9000 Series - SSH/Telnet

MS_HW_CiscoTelnet.hdf Cisco MDS9000Series FC switches

Storage Device

Cisco UCS Manager (Blade,Fabric Interconnect Switch)

MS_HW_CiscoUCSBlade.hdf Cisco UCS N/A

Data Domain StorageAppliance - SNMP Agent

MS_HW_DataDomain.hdf Data DomainStorage Appliance

Storage Device

DataDirect Networks (DDN)Disk Array - SNMP Agent

MS_HW_DDN.hdf DDN Disk Array Storage Device

DataDirect Networks (DDN)Storage Appliance - SNMPAgent

MS_HW_DDNSA.hdf DDN StorageAppliance

Storage Device

Dell CMC (Dell ChassisManagement Controller)

MS_HW_DellCMC.hdf Dell M1000EChassis

N/A

Dell DRAC/MC (Dell RemoteAccess Controller/ModularChassis)

MS_HW_DellDRACMC.hdf Dell PowerEdge N/A

Dell EqualLogic PS Series MS_HW_Equallogic.hdf Dell EqualLogic PSSeries Disk Systems

Storage Device

118Connectors


Version 2.7.28


Operating System

Dell iDRAC - Server MS_HW_DelliDRACServer.hdf Dell PowerEdge N/A

Dell iDRAC - Storage MS_HW_DelliDRACStorage.hdf Dell PowerEdge N/A

Dell OpenManage ArrayManager

MS_HW_DellArrayManager.hdf Dell PowerEdge Microsoft Windows, Linux

Dell OpenManage ServerAdministrator

MS_HW_DellOpenManage.hdf Dell PowerEdge Microsoft Windows, Linux

Dell OpenManage StorageManager

MS_HW_DellStorageManager.hdf Dell PowerEdge Microsoft Windows, Linux

Dell PowerVaultTL2000/4000 Tape Libraries

MS_HW_DellTL2000.hdfDell TL2000/4000Tape Library

Storage Device

EMC Disk Arrays MS_HW_EMCDiskArray.hdf Disk Array Storage Device

Emulex HBAs (hbacmd) MS_HW_EmulexHbacmd.hdf Server with EmulexHBAs

Linux, Sun Solaris

Fibre Alliance SNMP Agent(Switches)

MS_HW_FibreAllianceSwitch.hdf SAN Switches Storage Device

Fujitsu-SiemensManagement Blade (FSC BXBlade Servers)

MS_HW_FujitsuSiemensBlade.hdf Fujitsu-Siemens BXBlade Servers

N/A

Fujitsu-Siemens Serverview- WBEM

MS_HW_ServerviewWBEM.hdf Fujitsu-SiemensPRIMERGY

Linux

Fujitsu-Siemens Serverview- WMI

MS_HW_ServerviewWMI.hdf Fujitsu-SiemensPRIMERGY

Microsoft Windows

Fujitsu-Siemens ServerViewRAID Agent

MS_HW_FscRaid.hdf Fujitsu-SiemensPRIMERGY


Fujitsu-Siemens Serverview MS_HW_ServerviewNT.hdf Fujitsu-SiemensPRIMERGY


Fusion ioDrive (fio-status) MS_HW_FusionIO.hdf All x86 basedservers

Microsoft Windows, Linux, SunSolaris

Hitachi BladeSymphonyChassis

MS_HW_HitachiBladeSymphony.hdf HitachiBladeSymphonyChassis

N/A

Hitachi HDS Disk Arrays MS_HW_HitachiDiskArray.hdf Disk Array Storage Device

HP BladeSystem - Telnet/SSH

MS_HW_HPBladeTelnet.hdf HP BladeSystem N/A

HP BladeSystem MS_HW_HPBladeSystem.hdf HP BladeSystem Microsoft Windows, Linux, SunSolaris

HP Insight ManagementAgent - Drive Array

MS_HW_CpqDriveArrayNT.hdf HP ProLiant Microsoft Windows, Linux, HPOpenVMS, HP Tru64, SunSolaris

HP Insight ManagementAgent - Fiber Array

MS_HW_CpqFCADriveArray.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP Insight ManagementAgent - HBA

MS_HW_CpqHBA.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

119Connectors


Version 2.7.28


Operating System

HP Insight ManagementAgent - IDE Storage

MS_HW_CpqIDEDriveArray.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP Insight ManagementAgent - iLO

MS_HW_CpMgSm2.hdf HP ProLiant Microsoft Windows, Linux, HPOpenVMS, HP Tru64, SunSolaris

HP Insight ManagementAgent - Network

MS_HW_CpqNIC.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP Insight ManagementAgent - SCSI Storage

MS_HW_CpqSCSIDriveArray.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP Insight ManagementAgent - Server - WBEM

MS_HW_HPInsightwbem.hdf HP ProLiant Linux

HP Insight ManagementAgent - Server - WMI

MS_HW_HPInsightwmi.hdf HP ProLiant Microsoft Windows

HP Insight ManagementAgent - Server (Alpha)

MS_HW_CpMgServTru64.hdf HP ProLiant HP Tru64, HP OpenVMS

HP Insight ManagementAgent - Server

MS_HW_CpMgServNT.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP Insight ManagementAgent (v8.20 or lower) -Memory

MS_HW_CpqSiMem.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP Insight ManagementAgent (v8.25 or higher) -Memory

MS_HW_CpqHeResMem2.hdf HP ProLiant Microsoft Windows, Linux, HPTru64, HP OpenVMS, SunSolaris

HP MP/GSP card MS_HW_HPiLO.hdf HP 9000, Integrity,SuperDome

N/A

HP MSA 2000 & P2000 MS_HW_HPDotHill.hdf HP StorageWorksMSA P2000

Storage Device

HP StorageWorks EVA -SSSU

MS_HW_HPSSSU.hdf HP StorageWorksEVA

Storage Device

HP TopTools Agent MS_HW_HPTopToolsNT.hdf HP NetServer Microsoft Windows

HP TopTools NetRaid Agent MS_HW_HpNetRaidController.hdf HP NetServer Linux, Microsoft Windows

HP-UX - Common MS_HW_HPUX.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX - Disks MS_HW_HPUXDisk.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX - HBA MS_HW_HPUXHBA.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX - Network MS_HW_HPUXNetwork.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

120Connectors


Version 2.7.28


Operating System

HP-UX - SASMGR ManagedDisks

MS_HW_HPUXSasMgr.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX - Smart Array RAID MS_HW_HPUXSAUtil.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX - STM MS_HW_HPUXStm.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX - WBEM Network MS_HW_HPUXWBEMNetwork.hdf HP 9000, HPIntegrity, HPSuperDome

HP-UX

HP-UX WBEM MS_HW_HPUXWBEM.hdf HP-UX - WBEM HP-UX

IBM AIX - CHRP Environment MS_HW_IBMAIXChrpMachstat.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

IBM AIX - Common MS_HW_IBMAIX.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

IBM AIX - Environment(uesensor)

MS_HW_IBMAIXUeSensor.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

IBM AIX - HBA MS_HW_IBMAIXHBA.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

IBM AIX - LUN MS_HW_IBMAIXLUN.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

IBM AIX - SCSI disks MS_HW_IBMAIXDisk.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

IBM BladeCenterManagement Module

MS_HW_IBMBlade.hdf IBM BladeCenter N/A

IBM Director Agent 3.x -Windows

MS_HW_Director3NT.hdf IBM xSeries, IBMNetfinity

Microsoft Windows

IBM Director Agent 4.x -Linux

MS_HW_Director4Linux.hdf IBM xSeries, IBMNetfinity

Linux



Microsoft Windows

IBM Director Agent 5.10.x -Linux


Linux

IBM Director Agent 5.10.x -Windows


Microsoft Windows

IBM Director Agent 5.20.x -Linux


Linux

IBM Director Agent 5.20.x -Windows


Microsoft Windows

121Connectors


Version 2.7.28


Operating System

IBM Director Agent 6.x -Linux


Linux



Microsoft Windows

IBM DS (LSI) Disk Arrays(smcli)

MS_HW_smcli.hdf IBM DSxxxx DiskArrays

Storage Device

IBM DS6000/8000 DiskArrays

MS_HW_IBMDS68DiskArray.hdf Disk Array Storage Device

IBM Netfinity Manager5.20.x - Basic

MS_HW_IbmNetfinityManagerBASIC.hdf

IBM Netfinity Microsoft Windows

IBM Netfinity Manager5.20.x - Disks

MS_HW_IbmNetfinityManagerRAID.hdf

IBM Netfinity Microsoft Windows

IBM Netfinity Manager5.20.x - Normal

MS_HW_IbmNetfinityManager.hdf IBM Netfinity Microsoft Windows

IBM TS3100 Tape Libraries MS_HW_IBMTS3100.hdf IBM TS3100 TapeLibrary

Storage Device

IBM TS3200 Tape Libraries MS_HW_IBMTS3200.hdf IBM TS3200 TapeLibrary

Storage Device

IBM v7000 Disk Arrays - SSH MS_HW_IBMv7000SSH.hdf Disk Array Storage Device

IBM v7000 Disk Arrays MS_HW_IBMv7000.hdf Disk Array Storage Device

IBM VIO Server MS_HW_IBMVIOS.hdf IBM RS/6000, IBMpSeries, IBMeServer p5

IBM AIX

Intel Base Board 5Motherboards

MS_HW_IntelBaseBrd5.hdf Generic Servers Microsoft Windows, Linux

Intel Modular Server MS_HW_IntelModularServer.hdf Generic Servers N/A

IPMI MS_HW_IpmiTool.hdf Intel and AMD-based servers

Linux, Sun Solaris, MicrosoftWindows

Linux - Multipath MS_HW_LinuxMultipath.hdf Dell PowerEdge,Fujitsu-SiemensPRIMERGY, HPProLiant, IBMxSeries, NECExpress5800, SunFire (x64)

Linux

Linux - Network MS_HW_LinuxNetwork.hdf Dell PowerEdge, HPProLiant, Fujitsu-SiemensPRIMERGY, IBMxSeries, Sun Fire

Linux

Linux - QLogic HBAs (scli) MS_HW_QlogicSCLI.hdf Linux Server withHBAs

Linux

Localhost MonitoringDisabled

MS_HW_DisableLocalHost.hdf All Microsoft Windows, Linux, SunSolaris

LSI 1030-based GAM Server(Alternate MIB)

MS_HW_LSI1030Alt.hdf Fujitsu-SiemensPRIMERGY


122Connectors


Version 2.7.28


Operating System

LSI 1030-based GAM Server MS_HW_LSI1030.hdf Fujitsu-SiemensPRIMERGY


LSI Logic - LsiUtil - RAID(Windows)

MS_HW_LSIUtilWindows.hdf Windows serversequipped with anLSI RAID controller

Microsoft Windows

LSI Logic - LsiUtil - RAID MS_HW_LSIUtilUNIX.hdf Sun Fire (x64) Linux, Sun Solaris

LSI MegaCli MS_HW_LSIMegaCliWindows.hdf Any System with anLSI controllermanaged byMegaCli / CmdTool2

Microsoft Windows

LSI/Mylex GAM Server MS_HW_MylexController.hdf Fujitsu-SiemensPRIMERGY


LsiLogic MegaRAIDPowerConsole

MS_HW_MegaRaidPowerConsole.hdf



LsiLogic MegaRAID SAS(Newer Controllers)

MS_HW_LSIMegaRaidSAS5.hdf Fujitsu-SiemensPRIMERGY


LsiLogic MegaRAID SAS MS_HW_LSIMegaRaidSAS.hdf Fujitsu-SiemensPRIMERGY


McData Fibre Switch MS_HW_McData.hdf SAN Switches Storage Device

MegaCLI Managed RaidControllers

MS_HW_SunMegaCli.hdf All Solaris Machineswith LSI controllersand IBM Serverswith EXP3000External Bays

Sun Solaris, Linux

MIB-2 Standard SNMP Agent- Network Interfaces - Linux

MS_HW_MIB2Linux.hdf Any SNMP-instrumenteddevice

Linux

MIB-2 Standard SNMP Agent- Network Interfaces -Solaris

MS_HW_MIB2Solaris.hdf Any SNMP-instrumenteddevice

Sun Solaris, Sun Solaris

MIB-2 Standard SNMP Agent- Network Interfaces -Windows

MS_HW_MIB2NT.hdf Any SNMP-instrumenteddevice

Microsoft Windows

MIB-2 Standard SNMP Agent- Network Interfaces

MS_HW_MIB2.hdf Any SNMP-instrumenteddevice

Network, HP-UX, StorageDevice, HP OpenVMS, HPTru64

Motherboard Monitor MS_HW_MBMNT.hdf No-name PC Microsoft Windows

NEC ESMPRO Agent MS_HW_NECEsmPro.hdf NEC Express5800 Microsoft Windows, Linux

NetApp Filer - SNMP Agent MS_HW_NetApp.hdf Disk Array Storage Device

Promise FastTrack MS_HW_PromiseFSC.hdf Fujitsu-SiemensPRIMERGY


Quantum (ADIC) basedTape Libraries

MS_HW_QuantumTapeLibrary.hdf Quantum (ADIC)Tape Library

Storage Device

123Connectors


Version 2.7.28


Operating System

SmartMon Tools MS_HW_SmartMonLinux.hdf Dell PowerEdge,Fujitsu-SiemensPRIMERGY, HPProLiant, IBMxSeries, Sun Fire(x64)

Linux

SMI-S Compliant Disk Arrays MS_HW_SMISDiskArray.hdf Disk Array Storage Device

SMI-S Compliant HBAs MS_HW_SMISHBA.hdf Server with HBAs Microsoft Windows, Linux, IBMAIX, HP-UX, Tru64, HPOpenVMS, Sun Solaris

SMI-S Compliant RAIDController - Linux

MS_HW_Director52ServeRAIDLinux.hdf


Linux

SMI-S Compliant RAIDController - Windows

MS_HW_Director52ServeRAIDNT.hdf


Microsoft Windows

SMI-S Compliant SANSwitches

MS_HW_SMISSwitch.hdf SAN Switches Storage Device

SMI-S Compliant StorageLibraries

MS_HW_SMISLibrary.hdf Storage Libraries Storage Device

SNIA Compliant TapeLibraries

MS_HW_SNIALibrary.hdf IBM Tape Library3584 / VariousTS3xxx librariesfrom IBM based onthe SNIA mib

Storage Device

SPARC Enterprise Mx000(XSCF)

MS_HW_SunXscf.hdf SPARC EnterpriseMx000

Sun Solaris

StorageTek LSeries TapeLibrary

MS_HW_StorageTekLSeries.hdf StorageTek LSeries Storage Device

StorageTek StreamLine TapeLibrary

MS_HW_StorageTekStreamLine.hdf StorageTekStreamLine

Storage Device

Sun Advanced Lights-OutManagement (ALOM) card

MS_HW_SunAlom.hdf Sun Fire (SPARC) N/A

Sun Blade Chassis MS_HW_SunBladeChassis.hdf Sun Blade Chassis N/A

Sun Fire F12K/F15K/F20K/F25K (SMS)

MS_HW_SunF15K.hdf Sun Fire (SPARC) Sun Solaris

Sun/Oracle ILOM (SNMP) MS_HW_SunILOMSNMP.hdf Sun Blade withILOM cards

N/A

Sun/Oracle ILOM (SSH) MS_HW_SunILOMSSH.hdf Sun Blade withILOM cards

N/A

Sun Solaris - Environment(ALOM-CMT snapshot)

MS_HW_SunScSnapshot.hdf Sun Fire (SPARCT1/T2)

Sun Solaris

Sun Solaris - Environment(prtdiag, lom)

MS_HW_SunPrtdiag.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - Environment(prtpicl)

MS_HW_SunPrtpicl.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - Fault Manager(Memory and CPU)

MS_HW_SunFmadm.hdf Sun Fire (SPARC) Sun Solaris

124Connectors


Version 2.7.28


Operating System

Sun Solaris - MemoryModules (cediag)

MS_HW_SunCediag.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - Multi-coreProcessors (psrinfo)

MS_HW_SunPsrinfoT1.hdf Sun Fire Sun Solaris

Sun Solaris - Network MS_HW_SunNetwork.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - Non-Sun Disks MS_HW_SunIostatNonSun.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - Processors(psrinfo)

MS_HW_SunPsrinfo.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - RAID Disks(raidctl)

MS_HW_SunRaidctl.hdf All Sun Platformswith hardwareRAID Controllers

Sun Solaris

Sun Solaris - Sun Disks MS_HW_SunIostat.hdf Sun Fire (SPARC) Sun Solaris

Sun Solaris - Tape Drives MS_HW_SunTapeDrives.hdf Sun Fire (SPARC) Sun Solaris

VMware ESXi - Disks (IPMI) MS_HW_VMwareESXiDisksIPMI.hdf VMware ESXi Linux

VMware ESXi - Disks(VMware)

MS_HW_VMwareESXiDisksStorage.hdf

VMware ESXi Linux

VMware ESXi 3.x MS_HW_VMwareESXi.hdfMS_HW_VMwareESXiDisksIPMI.hdfMS_HW_VMwareESXiDisksStorage.hdf

VMware ESXi Linux

VMware ESXi 4.xVMware ESXi 5.x

MS_HW_VMwareESX4i.hdfMS_HW_VMwareESXiDisksIPMI.hdfMS_HW_VMwareESXiDisksStorage.hdf

VMware ESXi Linux

Windows - DiskPart MS_HW_DiskPart.hdf Windows Microsoft Windows

WMI - Battery MS_HW_GenBatteryNT.hdf Any Windowsplatform

Microsoft Windows

WMI - Disks MS_HW_WBEMGenDiskNT.hdf Dell PowerEdge,Fujitsu-SiemensPRIMERGY, HPProLiant, IBMxSeries, NECExpress5800, SunFire (x64)

Microsoft Windows

WMI - HBA MS_HW_WBEMGenHBA.hdf Dell PowerEdge,Fujitsu-SiemensPRIMERGY, HPProLiant, IBMxSeries, NECExpress5800, SunFire (x64)

Microsoft Windows

WMI - Network MS_HW_WBEMGenNetwork.hdf Dell PowerEdge,Fujitsu-SiemensPRIMERGY, HPProLiant, IBMxSeries, NECExpress5800, SunFire (x64)

Microsoft Windows

125Connectors


Version 2.7.28

Adaptec IOManagerThis connector provides disk monitoring through the Adaptec IO Manager SNMP sub-agent whichsupports a few AAC-based Adaptec RAID controllers.

Target

Typical platform: Fujitsu-Siemens PRIMERGY

Operating systems: Microsoft Windows, Linux

Instrumentation layer: Adaptec IOManager

Technology used: SNMP

Discovered objects

Disk controllers (SEN_HW_DISKCONTROLLER)

Logical disks, RAIDs (SEN_HW_LOGICALDISK)

Physical disks (SEN_HW_PHYSICALDISK)

Collected Parameters

SEN_HW_LOGICALDISK / Status

SEN_HW_LOGICALDISK / Status information

SEN_HW_PHYSICALDISK / Status

SEN_HW_PHYSICALDISK / Status information

SEN_HW_PHYSICALDISK / Predicted Failure

Adaptec StorMan (RAID)Gives information about physical disks and volumes of Adaptec SAS RAID controllers through the arcconfutility.

Target

Typical platform(s): Sun Fire (x64)

Operating system(s): Sun Solaris, Linux

Instrumentation layer: arcconf

126Connectors


Version 2.7.28

Technology used: System commands

Discovered objects





SEN_HW_DISKCONTROLLER / ControllerStatus

SEN_HW_DISKCONTROLLER / BatteryStatus



This connector is able to monitor the local host and/or a remote system.

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the 'sudo' utility for the following commands:

/[opt|usr]/StorMan/arcconf

Adaptec Storage Manager (DPT)This connector provides disk monitoring through the Adaptec Storage Manager SNMP sub-agent whichsupports all DPT-based Adaptec RAID controllers.

Target



Instrumentation layer: Adaptec Storage Manager


127Connectors


Version 2.7.28

Discovered objects







SEN_HW_PHYSICALDISK / PredictedFailure


Adaptec Storage Manager Web Edition (AAC)This connector provides disk monitoring through the Adaptec Storage Manager Web Edition SNMP sub-agent which supports all AAC-based Adaptec RAID controllers.

Target


Operating system: Microsoft Windows, Linux

Instrumentation layer: Adaptec Storage Manager Web Edition


Discovered objects









128Connectors


Version 2.7.28

Brocade SAN SwitchThis connector discovers the enclosure and fiber-channel ports of SAN switches as well as the variousenvironment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol andsupports the Brocade MIB (fcSwitch-MIB).

Target

Typical platform(s): SAN Switches

Operating system(s): Storage Device

Instrumentation layer: Brocade SNMP Agent (fcSwitch)


129Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)

Temperature sensors (SEN_HW_TEMPERATURE)

Power supplies (SEN_HW_POWERSUPPLY)

Blades (SEN_HW_BLADE)

Other devices (SEN_HW_OTHERDEVICE)

Network cards (SEN_HW_NETWORK)

Enclosure model (SEN_HW_ENCLOSURE)


SEN_HW_FAN / Status

SEN_HW_FAN / Speed

SEN_HW_TEMPERATURE / Status

SEN_HW_TEMPERATURE / Temperature

SEN_HW_OTHERDEVICE / Status

SEN_HW_POWERSUPPLY / Status

SEN_HW_NETWORK / Status

SEN_HW_NETWORK / LinkStatus

SEN_HW_NETWORK / LinkSpeed

SEN_HW_NETWORK / ErrorCount

SEN_HW_NETWORK / TransmittedPacketsRate

SEN_HW_NETWORK / ReceivedPacketsRate

SEN_HW_NETWORK / TransmittedBytesRate

SEN_HW_NETWORK / ReceivedBytesRate

SEN_HW_NETWORK / ZeroBufferCreditPrecent


Cisco MDS9000 Series - SSH/TelnetThis connector discovers the enclosure and fiber-channel ports of SAN switches as well as the variousenvironment sensors (temperatures, fans, power supplies, etc.).

Target

Typical platform(s): Cisco MDS9000 Series FC switches


Instrumentation layer: Commands on the Cisco Bay Controller

Technology used: Telnet/SSH

130Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status




SEN_HW_BLADE / Status









SEN_HW_NETWORK / DuplexMode

SEN_HW_ENCLOSURE / Powerconsumption

This connector targets remote dev ices only .

Cisco UCS Manager (Blade, Fabric InterconnectSwitch)This connector provides hardware monitoring for Cisco UCS Blade chassis (as well as the Cisco FabricInterconnect Switch) through the UCS Manager (running on the Fabric Interconnect Switch).

Target

Typical platform(s): Cisco UCS

Operating system(s): N/A

131Connectors


Version 2.7.28

Instrumentation layer: Cisco UCS Manager (XML API)

Technology used: Cisco UCS XML API

Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status

SEN_HW_FAN / Speed











SEN_HW_ENCLOSURE / Status

SEN_HW_ENCLOSURE / PowerConsumption


DataDirect Networks (DDN) Disk Array - SNMPAgentThis connector monitors the HBA cards present in an HP Proliant system by connecting to the HP InsightManagement agent.

Target

Typical platform(s): HP Proliant

132Connectors


Version 2.7.28

Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS

Instrumentation layer: HP Insight Management Agents


Discovered objects


Fans (SEN_HW_OTHERDEVICEFAN)





SEN_HW_FAN / Status




Data Domain Storage Appliance - SNMP AgentThis connector discovers the enclosure and the disks of Data Domain disk arrays as well as the variousenvironment sensors (temperatures, fans, power supplies). It relies on the SNMP protocol.

Target

Typical platform(s): Data Domain Storage Appliance


Instrumentation layer: Data Domain SNMP Agent


133Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)





SEN_HW_LOGICALDISK / UnallocatedSpace


SEN_HW_FAN / Status




Dell CMC (Dell Chassis Management Controller)Provides environmental information (temperatures, fans and power supplies) on Dell Blade serversthrough the Dell Chassis Management Controller (CMC).

Target

Typical platform(s): Dell M1000E Chassis


Instrumentation layer: Dell Chassis Management Controller (CMC)


134Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






SEN_HW_FAN / Speed

SEN_HW_FAN / Status








Dell DRAC/MC (Dell Remote AccessController/Modular Chassis)This connector provides environmental information (temperatures, fans and power supplies) on DellBlade servers through the Dell Remote Access Controller/Modular Chassis (DRAC/MC)

Target

Typical platform: Dell PowerEdge

Operating system: N/A

Instrumentation layer: Dell Remote Access Controller/Modular Chassis (DRAC/MC)


135Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)








SEN_HW_FAN / Speed

SEN_HW_FAN / Status






Dell EqualLogic PS SeriesThere can be multiple PS Systems controlled by the same controller. Thus multiple enclosures are likely.

Target

Typical platform(s): Dell EqualLogic PS Series Disk Systems


Instrumentation layer: Dell EqualLogic MIBs / SNMP Agent (EQLGROUP-MIB)


136Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)




Batteries (SEN_HW_BATTERY)




SEN_HW_PHYSICALDISK / ErrorCount

SEN_HW_FAN / Status

SEN_HW_FAN / Speed




SEN_HW_BATTERY / Status


Dell iDRAC - ServerThis connector provides hardware monitoring through Dell's iDRAC Management Card for Dell serverswith iDRAC7 or later.

Target

Typical platform(s): Dell PowerEdge


Instrumentation layer: Dell iDRAC Management Card (iDRAC7 or Later)


137Connectors


Version 2.7.28

Discovered objects

Fans (MS_HW_FAN)

Voltage sensors (MS_HW_VOLTAGE)

Temperature sensors (MS_HW_TEMPERATURE)

Power supplies (MS_HW_POWERSUPPLY)

Memory modules (MS_HW_MEMORY)

Processors (MS_HW_CPU)

Network cards (MS_HW_NETWORK)

Enclosure model (MS_HW_ENCLOSURE)

Batteries (MS_HW_BATTERY)

Collected parameters

MS_HW_FAN / Status

MS_HW_FAN / StatusInformation

MS_HW_VOLTAGE / Status

MS_HW_VOLTAGE / StatusInformation

MS_HW_TEMPERATURE / Status

MS_HW_TEMPERATURE / StatusInformation

MS_HW_TEMPERATURE / Temperature

MS_HW_POWERSUPPLY / Status

MS_HW_POWERSUPPLY / StatusInformation

MS_HW_MEMORY / Status

MS_HW_MEMORY / StatusInformation

MS_HW_CPU / Status

MS_HW_CPU / StatusInformation

MS_HW_NETWORK / Status

MS_HW_NETWORK / StatusInformation

MS_HW_NETWORK / LinkStatus

MS_HW_ENCLOSURE / Status

MS_HW_ENCLOSURE / StatusInformation

MS_HW_ENCLOSURE / PowerConsumption

MS_HW_BATTERY / Status

MS_HW_BATTERY / StatusInformation


138Connectors


Version 2.7.28

Dell iDRAC - StorageThis connector provides hardware monitoring through Dell's iDRAC Management Card for Dell serverswith iDRAC7 or later.

Target

Typical platform(s): Dell PowerEdge


Instrumentation layer: Dell iDRAC Management Card (iDRAC7 or Later)


139Connectors


Version 2.7.28

Discovered objects

Disk controllers (MS_HW_DISKCONTROLLER)

Logical disks, RAIDs (MS_HW_LOGICALDISK)

Physical disks (MS_HW_PHYSICALDISK)

Fans (MS_HW_FAN)


Other devices (MS_HW_OTHERDEVICE)




MS_HW_DISKCONTROLLER / ControllerStatus

MS_HW_DISKCONTROLLER / StatusInformation

MS_HW_LOGICALDISK / Status

MS_HW_LOGICALDISK / StatusInformation

MS_HW_PHYSICALDISK / Status

MS_HW_PHYSICALDISK / StatusInformation

MS_HW_FAN / Status




MS_HW_OTHERDEVICE / Status

MS_HW_OTHERDEVICE / StatusInformation






Dell OpenManage Array ManagerThis connector provides disks monitoring through the Dell OpenManage Array Manager SNMP agent (notto be confused with Storage Manager).

Target


Operating system(s): Microsoft Windows, Linux

Instrumentation layer: Dell OpenManage Server Administrator

140Connectors


Version 2.7.28


Discovered objects








Dell OpenManage Server AdministratorThis connector provides hardware monitoring through the Dell OpenManage Server Administrator SNMPagent which supports almost all DELL PowerEdge servers.

Target





141Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)

Voltage sensors (SEN_HW_VOLTAGE)




Memory modules (SEN_HW_MEMORY)

Processors (SEN_HW_CPU)


Batteries (SEN_HW_BATTERT)


SEN_HW_FAN / Status

SEN_HW_FAN / Speed

SEN_HW_VOLTAGE / Voltage

SEN_HW_VOLTAGE / Status





SEN_HW_MEMORY / Status

SEN_HW_MEMORY / ErrorCount

SEN_HW_CPU / Status

SEN_HW_CPU / CurrentSpeed


SEN_HW_ENCLOSURE / IntrusionStatus




Dell OpenManage Storage ManagerThis connector provides DELL disk array monitoring through the Dell Storage Manager Agent whichsupports almost all DELL disk arrays.

Target



142Connectors


Version 2.7.28



Discovered objects













Dell PowerVault TL2000/4000 Tape LibrariesThis connector monitors Dell PowerVault TL2000 and TL4000 tape libraries through SNMP.

Target

Typical platform(s): Dell TL2000/4000 Tape Library


Instrumentation layer: Dell SNMP Agent (DELL-SHADOW-MIB)


143Connectors


Version 2.7.28

Discovered objects


Tape drives (MS_HW_TAPEDRIVE)

Robotics (MS_HW_ROBOTICS)

Parameters collected



MS_HW_TAPEDRIVE / ErrorCount

MS_HW_TAPEDRIVE / MountCount

MS_HW_ROBOTICS / Status

MS_HW_ROBOTICS / StatusInformation


EMC Disk ArraysThis connector discovers the enclosure and the disks of EMC SAN disk arrays, as well as the storagepools and storage volumes. It will also discovery and monitor the FC ports of the array and the variousenvironment sensors when available (temperatures, fans, power supplies, etc.). It relies on the WBEMtechnology and supports SMI-S compliant disk arrays only.

Target

Typical platform(s): Disk Array


Instrumentation layer: EMC SMI-S Agent (ECOM)

Technology used: WBEM

144Connectors


Version 2.7.28

Discovered objects


Fans (SEN_HW_FAN)








SEN_HW_PHYSICALDISK / StatusInformation

SEN_HW_FAN / Status

SEN_HW_FAN / StatusInformation


SEN_HW_POWERSUPPLY / StatusInformation


SEN_HW_OTHERDEVICE / StatusInformation


SEN_HW_NETWORK / StatusInformation



SEN_HW_ENCLOSURE / StatusInformation


SEN_HW_BATTERY / StatusInformation


Emulex HBAs (hbacmd)This connector discovers Emulex HBAs of servers running UNIX or Linux using the hbacmd utilityprovided with the Emulex Drivers.

Target

Typical platform(s): UNIX/Linux Server with Emulex HBAs

Operating system(s): Linux, Sun Solaris

Instrumentation layer: Emulex's hbacmd utility


145Connectors


Version 2.7.28

Discovered objects














/usr/sbin/hbanyware/hbacmd

Fibre Alliance SNMP Agent (Switches)This connector discovers the enclosure and fiber-channel ports of SAN switches as well as the variousenvironment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol andsupports the Fibre Alliance MIB (FCMGMT-MIB).

Target



Instrumentation layer: Fibre Alliance SNMP Agent (FCMGMT-MIB)


146Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






SEN_HW_FAN / Status












Fujitsu-Siemens Management Blade (FSC BXBlade Servers)This connector provides hardware monitoring through the Fujitsu-Siemens Management Blade SNMPAgent which supports the Fujitsu-Siemens Blade servers (BX300, BX600, etc.). Needs to run remotely.

Target

Typical platform: Fujitsu-Siemens BX Blade Servers

Operating systems: N/A

Instrumentation layer: Fujitsu-Siemens Management Blade


147Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






SEN_HW_FAN / Status

SEN_HW_FAN / Speed





Fujitsu-Siemens Serverview - WBEMThis connector provides hardware monitoring through the -Siemens Serverview WBEM Agent (ESX)which supports almost all Fujitsu-Siemens PRIMERGY servers.

Target

Typical platform(s): Fujitsu-Siemens PRIMERGY

Operating system(s): Linux

Instrumentation layer: Fujitsu-Siemens Serveview WBEM Agent


148Connectors


Version 2.7.28

Discovered objects

Fans (MS_HW_FAN)








MS_HW_FAN / Status


MS_HW_VOLTAGE / Voltage








MS_HW_CPU / CurrentSpeed

MS_HW_CPU / Status



Fujitsu-Siemens Serverview - WMIThis connector provides hardware monitoring through the Fujitsu-Siemens Serverview Agent forWindows which supports almost all Fujitsu-Siemens PRIMERGY servers.

Target


Operating systems: Microsoft Windows

Instrumentation layer: Fujitsu-Siemens Serveview WBEM Agent

Technology used: WMI

149Connectors


Version 2.7.28

Discovered objects

Fans (MS_HW_FAN)








MS_HW_FAN / Status











MS_HW_CPU / Status



Fujitsu-Siemens ServerView RAID AgentThis connector provides disk monitoring through the Fujitsu-Siemens ServerView RAID SNMP sub-agentwhich supports many RAID controllers in Primergy servers.

Target



Instrumentation layer: Fujitsu-Siemens ServeView RAID Agent


150Connectors


Version 2.7.28

Discovered objects











Fujitsu-Siemens ServerviewThis connector provides hardware monitoring through the Fujitsu-Siemens Serverview Agent whichsupports almost all Fujitsu-Siemens PRIMERGY servers.

Target



Instrumentation layer: Fujitsu-Siemens Serverview Agent


151Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status

SEN_HW_FAN / Speed






SEN_HW_CPU / Status



Fusion ioDrive (fio-status)This connector monitors the Fusion ioDrive accelerator card.

Target

Typical platform(s): All x86 based servers

Operating system(s): Microsoft Windows, Linux, Sun Solaris

Instrumentation layer: fio-status cli utility

Technology used: System commands,

152Connectors


Version 2.7.28

Discovered objects














fio-status

Hitachi BladeSymphony ChassisThis connector provides hardware monitoring for the Hitachi BladeSymphony Chassis racks through theHitachi BladeSymphony Chassis Management Module

Target

Typical platform(s): Hitachi BladeSymphony Chassis


Instrumentation layer: Hitachi BladeSymphony Chassis Management Module


153Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






LEDs (SEN_HW_LED)


SEN_HW_FAN / Speed

SEN_HW_FAN / Status


SEN_HW_TEMPERATURE / StatusInformation






SEN_HW_LED / Status


Hitachi HDS Disk ArraysThis connector discovers the enclosure and the disks of Hitachi SAN disk arrays, as well as the storagepools and storage volumes. It will also discovery and monitor the FC ports of the array and the variousenvironment sensors when available (temperatures, fans, power supplies, etc.). It relies on the WBEMtechnology and supports SMI-S compliant disk arrays only.

Target



Instrumentation layer: Hitachi SMI-S Agent (Hitachi Storage Command Suite)


154Connectors


Version 2.7.28

Discovered objects



Fans (MS_HW_FAN)












MS_HW_FAN / Status








MS_HW_NETWORK / LinkSpeed








HP BladeSystemThis connector provides hardware monitoring for the HP BladeSystem racks through the HP InsightManagement Agents.

Target

Typical platform: HP BladeSystem

155Connectors


Version 2.7.28


Instrumentation layer: HP iLO / HP Insight Management Agents


Discovered objects

Blades (SEN_HW_BLADES)

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status








HP BladeSystem - Telnet/SSHThis connector provides hardware monitoring for the HP BladeSystem racks through the OnboardAdministrator.

Target

Typical platform(s): HP BladeSystem


Instrumentation layer: HP BladeSystem Onboard Administrator


156Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status

SEN_HW_FAN / SpeedPercent




SEN_HW_POWERSUPPLY / UsedWatts




SEN_HW_ENCLOSURE / powerconsumption


HP Insight Management Agent–Drive ArrayThis connector monitors the HP/Compaq Drive Arrays by connecting to the Storage Management SNMPsub-agent of the HP Insight Manager agent.

Target

Typical platform: HP ProLiant

Operating system(s): Microsoft Windows, Linux, HP OpenVMS, HP Tru64, Sun Solaris



157Connectors


Version 2.7.28

Discovered objects














SEN_HW_FAN / Status





HP Insight Management Agent–Fiber ArrayThis connector monitors the fiber-connected HP/Compaq StorageWorks Arrays by connecting to theFiber Array Management SNMP sub-agent of the HP Insight Manager agent.

Target


Operating systems: Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris



158Connectors


Version 2.7.28

Discovered objects















HP Insight Management Agent - HBAThis connector monitors the HBA cards present in an HP ProLiant system by connecting to the HP InsightManagement agent.

Target

Typical platform(s): HP ProLiant

Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris



Discovered objects





159Connectors


Version 2.7.28


HP Insight Management Agent–IDE StorageThis connector monitors the HP/Compaq IDE Drive Arrays by connecting to the Storage ManagementSNMP sub-agent of the HP Insight Manager agent.

Target





Discovered objects









HP Insight Management Agent–iLOThis connector provides hardware monitoring of the HP iLO card in HP ProLiant servers through the HPInsight Manager (Server Agent) which supports almost all HP Proliant and Integrity servers underWindows and Linux, as well as Tru64 servers.

Target


160Connectors


Version 2.7.28

Operating systems: Microsoft Windows, Linux, HP OpenVMS, HP Tru64, Sun Solaris



Discovered objects







HP Insight Management Agent (v8.25 or higher) -MemoryThis connector provides Memory Information through the HP Insight Manager (Newer Server Agents).

Target





Discovered objects





161Connectors


Version 2.7.28

HP Insight Management Agent (v8.20 or lower) -MemoryThis connector provides Memory Information through the HP Insight Manager (Older Server Agents).

Target





Discovered objects





HP Insight Management Agent - NetworkThis connector discovers enclosures, Ethernet ports and aggregations through the HP Insight ManagerAgent.

Target


Operating system(s): Microsoft Windows, Linux, SUN, HP



162Connectors


Version 2.7.28

Discovered objects













HP Insight Management Agent–SCSI StorageThis connector monitors the HP/Compaq SCSI disk by connecting to the Storage Management SNMPsub-agent of the HP Insight Manager agent.

Target





163Connectors


Version 2.7.28

Discovered objects










HP Insight Management Agent–ServerThis connector provides hardware monitoring through the HP Insight Manager (Server Agent) whichsupports almost all HP Proliant and Integrity servers under Windows and Linux, as well as Tru64servers.

Target





164Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status



SEN_HW_POWERSUPPLY / UsedWatts


SEN_HW_CPU / Status

SEN_HW_CPU / PredictedFailure



HP Insight Management Agent–Server (Alpha)This connector adds HP Tru64-specific hardware monitoring through the HP Insight Manager (ServerAgent).

Target


Operating systems: HP Tru64, HP OpenVMS



165Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)



SEN_HW_FAN / Status



HP Insight Management Agent - Server - WBEMThis connector provides hardware monitoring through the HP Insight Manager (Server Agent) whichsupports almost all HP Proliant and Integrity servers under Windows and Linux, as well as Tru64servers.

Target



Instrumentation layer: HP Insight Management Agents - WBEM


166Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / Status

SEN_HW_FAN / StatusInformation



SEN_HW_TEMPERATURE / StatusInformation






SEN_HW_MEMORY / StatusInformation


SEN_HW_CPU / Status

SEN_HW_CPU / StatusInformation











167Connectors


Version 2.7.28

HP Insight Management Agent - Server - WMIThis connector provides hardware monitoring through the HP Insight Manager (Server Agent) whichsupports almost all HP Proliant and Integrity servers under Windows and Linux, as well as Tru64servers.

Target


Operating system(s): Microsoft Windows

Instrumentation layer: HP Insight Management Agents - WMI


Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / Status







SEN_HW_CPU / Status




168Connectors


Version 2.7.28

HP MP/GSP card (iLO)This connector provides environmental information (temperatures, fans, etc.) on HP 9000 and Integrityservers through HP Integrated Lights-Out Management Card

Target

Typical platforms: HP 9000, Integrity, SuperDome


Instrumentation layer: HP MP/GSP card (iLO)


Discovered objects

Fans (SEN_HW_FAN)





SEN_HW_FAN / Status





HP MSA 2000 & P2000This connector discovers the Environmental, Physical Disk, Logical Disk, Management Network Cards andFibre Ports on P2000 / MSA Series Filers.

Target

Typical platform(s): HP StorageWorks MSA P2000


169Connectors


Version 2.7.28

Instrumentation layer: HP MSA Management Card


Discovered objects



Fans (SEN_HW_FAN)










SEN_HW_LOGICALDISK / StatusInformation




SEN_HW_FAN / Status












We recom m end setting the collection interv al for all MSA Disk array s to at least 15 m inutes toprev ent the m anagem ent card from being ov erloaded.


170Connectors


Version 2.7.28

HP StorageWorks EVA - SSSU - PMThis connector monitors the environmental sensors located in Disk Shelves. Sensors and physical disksare grouped into "Blades", one blade for each controller/disk shelf.

Target

Typical platform(s): HP EVA Storage Systems

Operating system(s): Storage

Instrumentation layer: Command Line

Technology used: SSSU

171Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)














SEN_HW_FAN / Status

SEN_HW_FAN / Speed










HP TopTools AgentThis connector provides hardware monitoring through the HP TopTools Agent version 5.x whichsupports almost all HP NetServer servers under Windows.

Target

Typical platform: HP NetServer

Operating system: Microsoft Windows

Instrumentation layer: HP TopTools Agent

172Connectors


Version 2.7.28

Technology used: System commands, WMI

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Speed

SEN_HW_FAN / Status






SEN_HW_CPU / Status

This connector is available for use to monitor the local host only .

HP TopTools NetRaid AgentThis connector monitors the RAID disks (physical and logical) attached to a HP NetRAID controller. Ituses the information provided by the HP NetRAID SNMP Sub-Agent, installed with the HP TopToolsServer Agent.

Target

Typical platform: HP NetServer

Operating systems: Linux, Microsoft Windows

Instrumentation layer: HP TopTools NetRaid Agent


173Connectors


Version 2.7.28

Discovered objects








HP-UX–CommonThis connector provides hardware status information (processors, network interfaces) on HP-UXsystems. Requires root privileges for disk monitoring.

Target

Typical platforms: HP 9000, HP Integrity, HP SuperDome

Operating system: HP-UX

Instrumentation layer: HP-UX system commands (ioscan, lanscan, etc.)


Discovered objects





SEN_HW_CPU / Status





174Connectors


Version 2.7.28

Credentials required

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the sudo utility for the following command: /usr/bin/adb.

HP-UX–DisksThis connector provides hardware SCSI disks status information on HP-UX systems. Requires rootprivileges.

Target



Instrumentation layer: HP-UX system commands (pvdisplay, ioscan, etc.)


Discovered objects







This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the following command: /usr/sbin/diskinfo

175Connectors


Version 2.7.28

HP-UX-HBAThis connector provides hardware status information for the fiber channel HBA cards on HP UX systems.

Target



Instrumentation layer: HP-UX system commands (ioscan, fcmsutil)


Discovered objects




MS_HW_NETWORK / LinkSpeed






/usr/sbin/ioscan

/opt/fcms/bin/fcmsutil

176Connectors


Version 2.7.28

IBM AIX - LUNProvides LUN MPIO status information on IBM AIX systems.

Target

Typical platform(s): IBM RS/6000, IBM pSeries, IBM eServer p5

Operating system(s): IBM AIX

Instrumentation layer: IBM AIX lspath system command


Discovered objects

LUN (MS_HW_LUN)


MS_HW_LUN / AvailablePathCount


HP-UX - NetworkDiscovers and monitors Ethernet adapters.

Target

Typical platform(s): HP 9000, HP Integrity, HP SuperDome

Operating system(s): HP-UX

Instrumentation layer: HP-UX system commands (lanscan, etc.)


177Connectors


Version 2.7.28

Discovered objects












HP-UX - SASMGR Managed DisksProvides hardware SAS Raid disks status information on HP-UX systems. Requires root privileges.

Target



Instrumentation layer: HP-UX system commands (sasmgr, ioscan etc.)


178Connectors


Version 2.7.28

Discovered objects









This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the 'sudo' utility for the following commands: * /opt/sas/bin/sasmgr


HP-UX - Smart Array RAIDDisplay the physical disks connected to a Smart Array Controller and any configured logical drives andspare drives.

Target



Instrumentation layer: HP-UX Smart Array Configuration Utility


179Connectors


Version 2.7.28

Discovered objects












/opt/raidsa/bin/sautil

HP-UX-STMThis connector enables monitoring physical disks and memory modules on HP-UX systems through theSupport Tools Manager utilities (STM).

Target



Instrumentation layer: HP-UX Support Tools Manager (STM)


180Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)








SEN_HW_FAN / Status



HP-UX-WBEM

Target



Instrumentation layer: HP-UX WBEM Provider


181Connectors


Version 2.7.28

Discovered objects


Logical disks (MS_HW_LOGICALDISK)

RAIDs (MS_HW_LOGICALDISK)


Fans (MS_HW_FAN)














MS_HW_FAN / Status





MS_HW_TEMPERATURE / Status

MS_HW_TEMPERATURE / StatusInformation





MS_HW_CPU / Status




HP-UX - WBEM Network

Target


182Connectors


Version 2.7.28


Instrumentation layer: HP-UX WBEM Provider


Discovered objects






MS_HW_NETWORK / Speed


IBM BladeCenter Management ModuleThis connector provides hardware monitoring of the IBM BladeCenter chassis through the IBMBladeCenter Management Module (SNMP-based). Needs to run remotely.

Target

Typical platform: IBM BladeCenter

Operating system: Not applicable

Instrumentation layer: IBM BladeCenter Management Module


183Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)













IBM AIX–CHRP EnvironmentThis connector provides hardware environment information (temperatures, voltages, fans, powersupplies) on IBM CHRP-based AIX systems.

Target

Typical platforms: IBM RS/6000, IBM pSeries, IBM eServer p5

Operating system: IBM AIX

Instrumentation layer: IBM AIX system commands (machstat)


184Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)



SEN_HW_FAN / Status




This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the following commands:

/usr/sbin/bootinfo

/usr/sbin/machstat

IBM AIX–CommonThis connector provides hardware status information (processors, network interfaces) on IBM AIXsystems

Target



Instrumentation layer: IBM AIX system commands (lsdev, entstat, etc.)


185Connectors


Version 2.7.28

Discovered objects






SEN_HW_CPU / Status













IBM AIX–Environment (ue sensor)This connector provides hardware environment information: temperatures, voltages, fans, powersupplies on IBM AIX systems

Target



Instrumentation layer: IBM AIX system commands (uesensor)


186Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)





SEN_HW_FAN / Speed






IBM AIX - HBAProvides hardware status information for the fiber channel HBA cards on IBM AIX systems.

Target



Instrumentation layer: IBM AIX system commands (lsdev, lsattr, fcstat, etc.)


187Connectors


Version 2.7.28

Discovered objects











IBM AIX–SCSI disksThis connector provides hardware status information of the non-RAID SCSI physical disks on IBM AIXsystems

Target


Operating systems: IBM AIX

Instrumentation layer: IBM AIX system commands (lsdev, pvdisplay, etc.)


Discovered objects







188Connectors


Version 2.7.28

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the 'sudo' utility for the following commands:

/usr/bin/dd

IBM Director Agent 3.x–WindowsThis connector provides hardware monitoring through the IBM Director Agent version 3.x which supportsalmost all IBM Netfinity and xSeries servers. This connector is WBEM-based.

Target

Typical platforms: IBM xSeries, IBM Netfinity


Instrumentation layer: IBM Director Agent 3.x


Discovered objects




Fans (SEN_HW_FAN)







SEN_HW_FAN / Speed




189Connectors


Version 2.7.28

IBM Director Agent 4.x–LinuxThis connector provides hardware monitoring through the IBM Director Agent version 4.x which supportssome (not all) xSeries servers.

Target


Operating system: Linux



Discovered objects




Fans (SEN_HW_FAN)










SEN_HW_FAN / Speed





SEN_HW_CPU / Status



190Connectors


Version 2.7.28


This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the following command: /opt/IBM/director/CIMOM/bin/cimcli.

IBM Director Agent 4.x–LinuxThis connector provides hardware monitoring through the IBM Director Agent version 4.x which supportsalmost all IBM Netfinity and xSeries servers.

Target





191Connectors


Version 2.7.28

Discovered objects




Fans (SEN_HW_FAN)










SEN_HW_FAN / Speed





SEN_HW_CPU / Status



IBM Director Agent 5.10.x–LinuxThis connector provides hardware monitoring through the IBM Director Agent version 5.x which supportssome (not all) xSeries servers.

Target



Instrumentation layer: IBM Director Agent 5.10.x


192Connectors


Version 2.7.28

Discovered objects




Fans (SEN_HW_FAN)










SEN_HW_FAN / Speed





SEN_HW_CPU / Status




This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the following command: /opt/ibm/director/cimom/bin/CLI.

IBM Director Agent 5.10.x–WindowsThis connector provides hardware monitoring through the IBM Director Agent version 5.x which supportsalmost all IBM Netfinity and xSeries servers.

Target



193Connectors


Version 2.7.28



Discovered objects




Fans (SEN_HW_FAN)










SEN_HW_FAN / Speed





SEN_HW_CPU / Status



IBM Director Agent 5.20.x–LinuxThis connector provides hardware monitoring through the IBM Director Agent version 5.20.x whichsupports some (not all) xSeries servers.

Target




194Connectors


Version 2.7.28


Discovered objects




Fans (SEN_HW_FAN)










SEN_HW_FAN / Speed





SEN_HW_CPU / Status




This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the sudo utility for the command: /opt/ibm/icc/cimom/bin/CLI.

IBM Director Agent 5.20.x–ServeRAID - LinuxThis connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agentcomponent of the IBM Director Agent version 5.20.x which supports almost all IBM Netfinity and xSeriesservers.

Target


195Connectors


Version 2.7.28




Discovered objects








This connector is able to monitor the local host and/or a remote system

IBM Director Agent 5.20.x–WindowsThis connector provides hardware monitoring through the IBM Director Agent version 5.20.x whichsupports almost all IBM Netfinity and xSeries servers.

Target





196Connectors


Version 2.7.28

Discovered objects




Fans (SEN_HW_FAN)










SEN_HW_FAN / Speed





SEN_HW_CPU / Status



IBM Director Agent 5.20.x–ServeRAID -WindowsThis connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agentcomponent of the IBM Director Agent version 5.20.x which supports almost all IBM Netfinity and xSeriesservers.

Target

Typical platform(s): IBM xSeries, IBM Netfinity




197Connectors


Version 2.7.28

Discovered objects









IBM Director Agent 6.x - LinuxThis connector provides hardware monitoring through the IBM Director Agent version 6.x.

Target





198Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Speed






SEN_HW_CPU / Status



IBM Director Agent 6.x - WindowsThis connector provides hardware monitoring through the IBM Director Agent version 6.x.

Target





199Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Speed






SEN_HW_CPU / Status



IBM DS (LSI) Disk Arrays (smcli)This connector provides hardware monitoring for IBM DS Storage Systems through the SMCli utility.

Target

Typical platform(s): IBM DSxxxx Disk Array


Instrumentation layer: SMCLI


200Connectors


Version 2.7.28

Discovered objects




Fans (SEN_HW_FAN)











SEN_HW_FAN / Status








This connector is able to monitor remote system only .

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the 'sudo' utility for the following commands: Second_Address

IBM DS6000/8000 Disk ArraysThis connector discovers the enclosure and the disks of IBM SAN disk arrays, as well as the storagepools and storage volumes. It will also discovery and monitor the FC ports, physical and logical disks ofthe array. It relies on the WBEM technology and supports SMI-S compliant disk arrays only.

Target



201Connectors


Version 2.7.28

Instrumentation layer: IBM SMI-S Agent (IBM System Storage DS6000/DS8000 Storage Manager)


Discovered objects


















IBM Netfinity Manager 5.20.x–BasicThis connector provides basic environment monitoring through the IBM Netfinity Manager Services SNMPsub-agent which supports almost all old IBM servers (Netfinity) under Windows.

Target

Typical platform: IBM Netfinity


Instrumentation layer: IBM Netfinity Manager 5.20.x


202Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)




SEN_HW_FAN / Status




IBM Netfinity Manager 5.20.x–DisksThis connector provides IBM ServeRAID monitoring through the IBM Netfinity Manager Services SNMPsub-agent which supports almost all old IBM servers (Netfinity) under Windows.

Target





Discovered objects








203Connectors


Version 2.7.28

IBM Netfinity Manager 5.20.x–NormalThis connector provides environment monitoring through the IBM Netfinity Manager Services SNMP sub-agent which supports almost all old IBM servers (Netfinity) under Windows.

Target


Operating systems: Microsoft Windows



Discovered objects








IBM TS3100 Tape LibrariesThis connector monitors IBM TS3100 tape libraries through SNMP.

Target

Typical platform(s): IBM TS3100 Tape Library


Instrumentation layer: IBM SNMP Agent SNMP Agent (IBM-3100-MIB)


204Connectors


Version 2.7.28

Discovered objects












IBM TS3200 Tape LibrariesThis connector monitors IBM TS3200 tape libraries through SNMP.

Target

Typical platform(s): IBM TS3200 Tape Library


Instrumentation layer: IBM SNMP Agent SNMP Agent (IBM-3200-MIB)


205Connectors


Version 2.7.28

Discovered objects












IBM v7000 Disk Arrays - SSHThis connector discovers the enclosure and the disks of IBM SAN disk arrays, as well as the storagepools and storage volumes. It will also discovery and monitor the FC ports, physical and logical disks ofthe array. It logs in directly to the v7000 custer's management interface.

Target



Instrumentation layer:


206Connectors


Version 2.7.28

Discovered objects






LEDs (MS_HW_LED)








MS_HW_LED / Status

MS_HW_LED / StatusInformation




IBM v7000 Disk ArraysThis connector discovers the enclosure and the disks of IBM SAN disk arrays, as well as the storagepools and storage volumes. It will also discovery and monitor the FC ports, physical and logical disks ofthe array. It relies on the WBEM technology and supports SMI-S compliant disk arrays only.

Target



Instrumentation layer:


207Connectors


Version 2.7.28

Discovered objects












IBM VIO ServerProvides hardware status information (processors, memory modules, network interfaces, HBAs, physicaldisks) on IBM VIO systems.

Target



Instrumentation layer: IBM AIX system commands through the IOS interface (lsdev, entstat, etc.)


208Connectors


Version 2.7.28

Discovered objects











SEN_HW_MEMORY / StatusInformation


SEN_HW_CPU / Status










This connector is able to monitor remote systems only .

Intel Base Board 5 MotherboardsThis connector provides hardware monitoring through the Intel Server Manager 8 SNMP Agents underWindows and Linux.

Target

Typical platform(s): Generic Servers


Instrumentation layer: Intel Server Manager 8 SNMP Agents


209Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status

SEN_HW_FAN / Speed






SEN_HW_CPU / Status


Intel Modular ServerThis connector provides hardware monitoring through the Intel Modular Server Chassis ManagementModule's SNMP Agents.

Target

Typical platform(s): Generic Servers


Instrumentation layer: Intel Server Manager 8 SNMP Agents


210Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)










SEN_HW_FAN / Status

SEN_HW_FAN / Speed











IPMI–In-band(IpmiTool)Gives environmental information (temperatures, fans, etc.) on several IPMI-enabled servers in-band andout-of-band.

Target

Typical platform(s): Intel and AMD-based servers

Operating system(s): Linux, Sun Solaris, Microsoft Windows

Instrumentation layer: IPMI

Technology used: IPMI

211Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)








LEDs (SEN_HW_LED)




SEN_HW_FAN / Speed

SEN_HW_FAN / Status






SEN_HW_CPU / Status



SEN_HW_LED / Status

This connector is able to monitor the local host and/or a remote system.This connector probably requires root priv ileges for its proper operation. You therefore will need to configure theproduct to use the root login/password to execute ex ternal commands.A lternatively , you can configure the product to use the 'sudo' utility for the following commands: * ipmitool

Localhost Monitoring DisabledA manually selectable connector that collects nothing but activates the localhost.

Target

Typical platform(s): All

Operating system(s): Microsoft Windows, Linux, Sun Solaris

212Connectors


Version 2.7.28

Instrumentation layer: Nothing

Technology used: N/A

Discovered objects




LSI 1030-based GAM ServerThis connector provides disk monitoring for LSI c1030-based disk controllers (also known as LSIIntegrated Mirroring) through the LSI1030 SNMP sub-agent.

Target

Typical platforms: Fujitsu-Siemens PRIMERGY


Instrumentation layer: LSI GAM Server


Discovered objects








213Connectors


Version 2.7.28

LSI 1030-based GAM Server (Alternate MIB)This connector provides disk monitoring for LSI c1030-based disk controllers (also known as LSIIntegrated Mirroring) through the LSI1030 SNMP sub-agent (based on the 1.3.6.1.4.1.3582.2 MIB).

Target



Instrumentation layer: LSI GAM Server


Discovered objects








LSI Logic - LsiUtil - RAID (Windows)Gives information about physical disks and volumes of LSI Logic SAS RAID controllers through the lsiutilutility.

Target

Typical platform(s): Windows servers equipped with an LSI RAID controller


Instrumentation layer: lsiutil


214Connectors


Version 2.7.28

Discovered objects








LSI Logic - LsiUtil - RAIDGives information about physical disks and volumes of LSI Logic SAS RAID controllers through the lsiutilutility.

Target

Typical platform(s): Sun Fire (x64)

Operating system(s): Linux, Sun Solaris

Instrumentation layer: lsiutil


Discovered objects








215Connectors


Version 2.7.28

Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.

Alternatively, you can configure the product to use the 'sudo' utility for the following commands:

lsiutil

LSI Logic MegaRAID PowerConsoleThis connector provides disk monitoring through the LsiLogic MegaRAID PowerConsole SNMP sub-agentwhich supports all MegaRAID-based RAID controllers.

Target



Instrumentation layer: LSI MegaRAID PowerConsole


Discovered objects








216Connectors


Version 2.7.28

LsiLogic MegaRAID SASThis connector provides disk monitoring through the LsiLogic MegaRAID SAS SNMP sub-agent whichsupports all LSI MegaRaid SAS RAID controllers.

Target



Instrumentation layer: LSI MegaRAID SAS SNMP Agent


Discovered objects









LsiLogic MegaRAID SAS (Newer Controllers)This connector provides disk monitoring through the LsiLogic MegaRAID SAS SNMP sub-agent whichsupports newer LSI MegaRaid SAS RAID controllers.

Target

Typical platform(s): Fujitsu-Siemens PRIMERGY


Instrumentation layer: LSI MegaRAID SAS SNMP Agent

217Connectors


Version 2.7.28


Discovered objects









LSI MegaCliGives physical disk and array status.

Target

Typical platform(s): Any System with an LSI controller managed by MegaCli / CmdTool2


Instrumentation layer: Windows system commands (MegaCli / CmdTool2)


Discovered objects









218Connectors


Version 2.7.28

LSI/Mylex GAM ServerThis connector provides disk monitoring through the Mylex SNMP sub-agent which supports all Mylexdisk controllers.

Target


Instrumentation layer: Mylex GAM Servers


Discovered objects







Linux - Emulex HBAs (hbacmd)This connector discovers Emulex HBAs of servers running Linux using the hbacmd utility provided withthe Emulex Drivers.

Target

Typical platform(s): Linux Server with HBAs


Instrumentation layer: Emulex's hbacmd utility


Discovered objects


219Connectors


Version 2.7.28












Credentials


/usr/sbin/hbanyware/hbacmd

Linux–NetworkThis connector provides the monitoring of network cards on all Linux systems.

Target

Typical platforms: Dell PowerEdge, HP ProLiant, Fujitsu-Siemens PRIMERGY, IBM xSeries, Sun Fire


Instrumentation layer: Linux system commands (ethtool, mii-tool)


Discovered objects


220Connectors


Version 2.7.28











Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the commands:

ethtool

mii-tool

Linux - MultipathThis connector provides the monitoring of HBA cards on all Linux systems through the multipath utility.

Target

Typical platform(s): Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NECExpress5800, Sun Fire (x64)


Instrumentation layer: Linux multipath utility


221Connectors


Version 2.7.28

Discovered objects

LUN (SEN_HW_LUN)


SEN_HW_LUN / AvailablePathCount

SEN_HW_LUN / AvailablePathInformation


Credentials


multipath

Linux - QLogic HBAs (scli)This connector discovers QLogic HBAs of servers running Linux using the scli utility provided with theQLogic Drivers.

Target

Typical platform(s): Linux Server with HBAs


Instrumentation layer: QLogic's SCLI utility


222Connectors


Version 2.7.28

Discovered objects







Credentials


scli

McData Fibre Switch

Target

Typical platform(s): McData San Switches

Operating system(s): Storage

Instrumentation layer: SNMP


223Connectors


Version 2.7.28

Discovered objectsFans (SEN_HW_FAN)







Parameters collectedSEN_HW_FAN / Status













MegaCLI Managed Raid ControllersGives physical disk and array status.

Target

Typical platform(s): All Solaris Machines with LSI controllers and IBM Servers with EXP3000 ExternalBays

Operating system(s): Sun Solaris, Linux

Instrumentation layer: MegaCli (LSI) managed RAID card


224Connectors


Version 2.7.28

Discovered objects









Credentials


MegaCli

MIB-2 Standard SNMP Agent - NetworkInterfacesThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2standard SNMP Agent.

Target

Typical platform(s): Any SNMP-instrumented device

Operating system(s): Network, HP-UX, Storage Device, HP OpenVMS, HP Tru64

Instrumentation layer: MIB-2 Standard SNMP Agent


225Connectors


Version 2.7.28

Discovered objects












MIB-2 Standard SNMP Agent - NetworkInterfaces - LinuxThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2standard SNMP Agent.

Target





Discovered objects


226Connectors


Version 2.7.28











MIB-2 Standard SNMP Agent - NetworkInterfaces - WindowsThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2standard SNMP Agent.

Target





227Connectors


Version 2.7.28

Discovered objects












MIB-2 Standard SNMP Agent - NetworkInterfaces - SolarisThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2standard SNMP Agent.

Target


Operating system(s): Sun Solaris



228Connectors


Version 2.7.28

Discovered objects












Motherboard MonitorThis connector provides hardware monitoring through Motherboard Monitor version 5.x which supportsalmost all non-branded PCs under Windows.

Target

Typical platform: Unbranded PC


Instrumentation layer: Motherboard Monitor


229Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






SEN_HW_FAN / Speed




NetApp Filer - SNMP AgentThis connector discovers the enclosure and the disks of NetApp disk arrays (filer) as well as the variousenvironment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol.

Target



Instrumentation layer: NetApp SNMP Agent


230Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)










SEN_HW_FAN / Status






NEC ESMPRO AgentThis connector provides hardware monitoring through the NEC ESMPRO Agent which supports almost allNEC Express5800 and some BULL NovaScale servers running Windows and Linux.

Target

Typical platform: NEC Express5800


Instrumentation layer: NEC ESMPRO Agent


231Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status





SEN_HW_CPU / Status


Promise FastTrackThis connector provides disk monitoring through the Promise FastTrack SNMP agent.

Target



Instrumentation layer: Promise FastTrack SNMP Agent


232Connectors


Version 2.7.28

Discovered objects








MS_HW_PHYSICALDISK / PredictedFailure


Quantum (ADIC) Based Tape Libraries

Target

Typical platform(s): Quantum (ADIC) Tape Library


Instrumentation layer: Quantum SNMP Agent (ADIC-TAPE-LIBRARY-MIB)


233Connectors


Version 2.7.28

Discovered objects


Fans (SEN_HW_FAN)



Tape drive (SEN_HW_TAPEDRIVE)

Robotics (SEN_HW_ROBOTIC)



SEN_HW_FAN / Status



SEN_HW_TAPEDRIVE / Status

SEN_HW_TAPEDRIVE / NeedsCleaning

SEN_HW_TAPEDRIVE / MountCount

SEN_HW_ROBOTIC / Status


SmartMonToolsThis connector provides S.M.A.R.T.-enabled physical disk information through the smartd/smartctl utilityunder Linux

Target

Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, Sun Fire(x64)


Instrumentation layer: SmartMonTools


234Connectors


Version 2.7.28

Discovered objects








Credentials


Alternatively, you can configure the product to use the sudo utility for the command:/usr/sbin/smartctl/bin/dd.

SMI-S Compliant Disk ArraysThis connector discovers the enclosure and the disks of SAN disk arrays, as well as the storage poolsand storage volumes. It will also discovery and monitor the FC ports of the array and the variousenvironment sensors when available (temperatures, fans, power supplies, etc.). It relies on the WBEMtechnology and supports SMI-S compliant disk arrays only.

Target



Instrumentation layer: SMI-S Agent provided by the array vendor


235Connectors


Version 2.7.28

Discovered objects



Fans (SEN_HW_FAN)










SEN_HW_FAN / Status









SMI-S Compliant HBAsThis connector discovers the HBAs of a server. It relies on the WBEM technology and supports SMI-Scompliant HBAs only.

Target

Typical platform(s): Server with HBAs

Operating system(s): Microsoft Windows, Linux, IBM AIX, HP-UX, Tru64, HP OpenVMS, Sun Solaris

Instrumentation layer: SMI-S Agent provided by the HBA vendor


236Connectors


Version 2.7.28

Discovered objects








SMI-S Compliant RAID Controller - LinuxThis connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agentcomponent of the IBM Director Agent version 5.20.x / 6.10.x which supports almost all IBM Netfinity andxSeries servers.

Target



Instrumentation layer: IBM Director Agent 5.20.x / 6.10.x


Discovered objects









237Connectors


Version 2.7.28

SMI-S Compliant RAID Controller - WindowsThis connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agentcomponent of the IBM Director Agent version 5.20.x (or the 6.10.x common agent) which supportsalmost all IBM Netfinity and xSeries servers.

Target



Instrumentation layer: IBM Director Agent 5.20.x / 6.10.x


Discovered objects









SMI-S Compliant Storage LibrariesThis connector discovers the enclosure of a storage library as well as its specialized devices: tapedrives, cartridges, media changers, etc.. It will also discovery and monitor the FC ports of the array andthe various environment sensors when available (temperatures, fans, power supplies, etc.). It relies onthe WBEM technology and supports SMI-S compliant tape libraries only.

Target

Typical platform(s): Storage Libraries


Instrumentation layer: SMI-S Agent provided by the library vendor

238Connectors


Version 2.7.28


Discovered objects

Fans (SEN_HW_FAN)






Tape drives (SEN_HW_TAPEDRIVE)



SEN_HW_FAN / Status











SEN_HW_ROBOTICS / Status


SMI-S Compliant SAN SwitchesThis connector discovers the enclosure and fiber-channel ports of SAN switches as well as the variousenvironment sensors (temperatures, fans, power supplies, etc.). It relies on the WBEM technology andsupports SMI-S compliant switches only.

Target



Instrumentation layer: SMI-S Agent provided by the switch vendor

239Connectors


Version 2.7.28


Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status









SNIA Compliant Tape Libraries

Target

Typical platform(s): IBM Tape Library 3584 / Various TS3xxx libraries from IBM based on the SNIAmib


Instrumentation layer: SNIA Compliant SNMP Agent (SNIA-SML-MIB)


240Connectors


Version 2.7.28

Discovered objects








SEN_HW_ROBOTIC / Status


SPARC Enterprise Mx000 (XSCF)Gives environmental information (temperatures, fans, etc.) and boards status on SPARC EnterpriseM4000, M5000, M8000 and M9000 servers.

Target

Typical platform(s): SPARC Enterprise Mx000


Instrumentation layer: Sun XSCF utilities installed on the System Controller


241Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status




SEN_HW_OTHERDEVICE / PowerConsumption


SEN_HW_CPU / Status



StorageTek LSeries Tape LibraryThis connector provides basic hardware monitoring of the StorageTek LSeries tape libraries throughtheir built-in SNMP agent. Needs to run remotely.

Target

Typical platform(s): StorageTek LSeries


Instrumentation layer: StorageTek LSeries SNMP Agent


242Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






Robotic (SEN_HW_ROBOTIC)


SEN_HW_FAN / Status




SEN_HW_OTHERDEVICE / usagecount

SEN_HW_OTHERDEVICE / UsageCount




SEN_HW_ROBOTICS / Status

SEN_HW_ROBOTICS / MoveCount

SEN_HW_ROBOTICS / ErrorCount


StorageTek StreamLine Tape LibraryThis connector provides basic hardware monitoring of the StorageTek StreamLine tape libraries throughtheir built-in SNMP agent. Needs to run remotely.

Target

Typical platform(s): StorageTek StreamLine


Instrumentation layer: StorageTek StreamLine SNMP Agent


243Connectors


Version 2.7.28

Discovered objects








Sun Advanced Lights–Out Management (ALOM)cardThis connector provides environmental and disk information (temperatures, fans, etc.) on Sun SPARCservers equipped with an ALOM card. Telnet must be enabled on the ALOM card.

Target

Typical platform: Sun Fire (SPARC)


Instrumentation layer: Sun Advanced Lights-Out Management (ALOM) card


244Connectors


Version 2.7.28

Discovered objects


Fans (SEN_HW_FAN)








SEN_HW_FAN / Status

SEN_HW_FAN / Speed








SUN Blade ChassisThis connector provides hardware monitoring for the SUN Blade Chassis through the CMM SNMP Agent /SSH (optional).

Target

Typical platform(s): SUN Blade Chassis


Instrumentation layer: SUN Blade Chassis CMM SNMP Agent


245Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)






SEN_HW_FAN / Speed

SEN_HW_FAN / Status






Sun Fire F12K/F15K/F20K/F25K (SMS)This connector provides environmental information (temperatures, fans, etc.) and boards status on SunFire F12K, F15K, F20K and F25K servers.

Target


Operating system: Sun Solaris

Instrumentation layer: Sun SMS utilities installed on the System Controller (SC on F15K, etc.)


246Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status









SUN ILOM (SNMP)This connector provides hardware monitoring for the SUN Blades with ILOM cards via SNMP.

Target

Typical platform(s): SUN Blade with ILOM cards


Instrumentation layer: SUN Blade SP SNMP Agent


247Connectors


Version 2.7.28

Discovered objects














SEN_HW_CPU / Status


SUN ILOM (SSH)This connector provides hardware monitoring for the SUN Blades with ILOM cards via SSHP.

Target

Typical platform(s): SUN Blade with ILOM cards


Instrumentation layer: SUN Blade SP


248Connectors


Version 2.7.28

Discovered objects













SEN_HW_CPU / Status



Sun Solaris–Environment (ALOM-CMTsnapshot)This connector provides environmental and disk information (temperatures, fans, etc.) on Sun SPARCT1/T2 servers equipped with an ALOM card. Gathers the hardware information from the ALOM card in-band (no telnet or SSH connection over the network). Requires the SUNWexplo (Sun Explorer) package.

Target

Typical platform: Sun Fire (SPARC T1/T2)


Instrumentation layer: Sun Explorer and the ALOM-CMT card


249Connectors


Version 2.7.28

Discovered objects


Fans (SEN_HW_FAN)








SEN_HW_FAN / Status

SEN_HW_FAN / Speed








Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the 'sudo' utility for the following commands: /opt/SUNWexplo/bin/snapshot.

Sun Solaris–Environment (prtpicl)This connector provides environmental information (temperatures, fans, etc.) on several Sun platformsthrough the prtpicl utility. This connector is to be used mainly on Solaris 10 systems.

Target



Instrumentation layer: Sun Solaris system commands (prtpicl, etc.)

250Connectors


Version 2.7.28


Discovered objects

Fans (SEN_HW_FAN)





SEN_HW_FAN / Speed


SEN_HW_FAN / Status





SEN_HW_LED / Status


Sun Solaris–Environment (prtdiag, lom)This connector provides environmental information (temperatures, fans, etc.) on several Sun platformsthrough the prtdiag or lom utility.

Target



Instrumentation layer: Sun Solaris system commands (prtdiag, lom, psrinfo, etc.)


251Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status








Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the 'sudo' utility for the following command: /usr/sbin/lom.

Sun Solaris - Fault Manager (Memory)This connector parses fmadm faulty command looking for faulty memory modules

Target

Typical platform(s): Sun Fire (SPARC)


Instrumentation layer: Sun Solaris system commands (fmadm)


252Connectors


Version 2.7.28

Discovered objects



SEN_HW_OTHERDIVICE / Status



Credentials


Alternatively, you can configure the product to use the 'sudo' utility for the following commands:

* /usr/sbin/fmadm

Sun Solaris–Memory modules (cediag)This connector provides memory modules monitoring on Sun Solaris 8 and 9 SPARC systems. Requiresroot privileges

Target



Instrumentation layer: Sun Solaris system commands (cediag, cestat)


253Connectors


Version 2.7.28

Discovered objects



SEN_HW_MEMORY / PredictedFailure



Credentials

This connector probably requires root privileges for proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the command: /opt/SUNWcest/bin/cediag.

Both cediag and cestat need to be added to the sudoers file.

Sun Solaris - ProcessorThis connector discovers and monitors the processor in any Sun SPARC-based Solaris machine throughthe psrinfo system command.

Target



Instrumentation layer: Sun Solaris system commands (psrinfo, etc.)


Discovered objects



SEN_HW_CPU / Status

254Connectors


Version 2.7.28


See Also

Platforms & Connectors

Sun Solaris–NetworkThis connector provides the monitoring of network cards on all Sun Solaris systems.

Target



Instrumentation layer: Sun Solaris system commands (kstat, ndd, ifconfig, etc.)


Discovered objects













Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, you

255Connectors


Version 2.7.28

can configure the product to use the sudo utility for the following commands:

/usr/bin/kstat

/usr/sbin/ndd

Sun Solaris–Non-Sun DisksThis connector provides physical disk information (status and error count) on Sun Solaris platformsthrough the iostat -En utility. Supports only non-Sun disks in Sun systems. This connector needs to bemanually activated and will never be picked up automatically during the platform detection andcomponents discovery.

Target



Instrumentation layer: Sun Solaris system commands (iostat, dd)


Discovered objects





SEN_HW_PHYSICALDISK / HardErrorCount

SEN_HW_PHYSICALDISK / MediaErrorCount

SEN_HW_PHYSICALDISK / DeviceNotReadyErrorCount

SEN_HW_PHYSICALDISK / NoDeviceErrorCount

SEN_HW_PHYSICALDISK / TransportErrorCount

SEN_HW_PHYSICALDISK / RecoverableErrorCount

SEN_HW_PHYSICALDISK / IllegalRequestErrorCount




256Connectors


Version 2.7.28

Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the 'sudo' utility for the following command: /usr/bin/dd.

Sun Solaris–Multi-core Processors (psrinfo)This connector discovers and monitors the processor in any Sun SPARC-based Solaris machine throughthe psrinfo system command.

Target

Typical platform: Sun Fire




Discovered objects

Processors (SEN_HW_CPU)CPU Cores (SEN_HW_CPUCORE)


SEN_HW_CPUCORE / Status


Sun Solaris - RAID Disks (Raidctl)Gives physical disk and array status.

Target

Typical platform(s): All Sun Platforms with Hardware Raid Controllers

257Connectors


Version 2.7.28


Instrumentation layer: Sun Solaris system commands (raidctl)


Discovered objects








Credentials

This connector probably requires root privileges for its proper operation. You therefore will need toconfigure the product to use the root login/password to execute external commands. Alternatively, youcan configure the product to use the 'sudo' utility for the following commands:* /usr/sbin/raidctl

Sun Solaris - Multi Processors (psrinfo)This connector discovers and monitors the multi-core processors (SPARC T1, T2, T2+ and Intel Xeon)through the psrinfo system command.

Target

Typical platform(s): Sun Fire




258Connectors


Version 2.7.28

Discovered objects


CPU Cores (SEN_HW_CPUCORE)


SEN_HW_CPUCORE / Status

SEN_HW_CPUCORE / StatusInformation


Sun Solaris–Sun DisksThis connector provides physical disk information (status and error count) on Sun Solaris systemsthrough the iostat -En utility. Supports only official Sun disks.

Target





Discovered objects







Credentials

This connector probably requires root privileges for its proper operation. You therefore will need to

259Connectors


Version 2.7.28

configure the product to use the root login/password to execute external commands.Alternatively, you can configure the product to use the sudo utility for the command: /usr/sbin/dd.

Sun Solaris - Tape DrivesGives physical disk information (status and error count) on Sun Solaris systems through the iostat -Enutility. Supports only official Sun disks.

Target

Typical platform(s): Sun Fire (SPARC)




Discovered objects

Tape drives (SEN_HW_TAPEDRIVE)


SEN_HW_TAPEDRIVE / ErrorCount


Credentials


Windows - DiskPartDiscovers and monitors the logical disks in a Microsoft Windows system through the DISKPART.EXEutility, notably the software RAID volumes.

Target

Typical platform(s): Windows

260Connectors


Version 2.7.28


Instrumentation layer: The DISKPART.EXE command-line utility


Discovered objects


Credentials




VMware ESXi 3.xThis connector provides hardware monitoring through the VMware ESXi implementation of SMASH,through the WBEM protocol.

Target

Typical platform(s): VMware ESXi


Instrumentation layer: WBEM


261Connectors


Version 2.7.28

Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / Status

SEN_HW_FAN / Speed








SEN_HW_CPU / Status





VMware ESX4i - Disks (IPMI)This connector provides disk monitoring through the VMware ESX4i agent's discrete IPMI Sensors

Target

Typical platform(s): VMware ESX4i




262Connectors


Version 2.7.28

Discovered objects





VMware ESX4i - Disks (VMware)This connector provides disk monitoring through the VMware ESX4i agent's VMware classes.

Target

Typical platform(s): VMware ESX4i




Discovered objects









263Connectors


Version 2.7.28

VMware ESXi 4.x / 5.xThis connector provides hardware monitoring through the VMware ESXi implementation of SMASH,through the WBEM protocol.

Target

Typical platform(s): VMware ESXi




Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / Status

SEN_HW_FAN / Speed








SEN_HW_CPU / Status





264Connectors


Version 2.7.28

WMI - BatteryThis connector provides battery monitoring for Windows computers.

Target

Typical platform(s): Any Windows platform


Instrumentation layer: WMI


Discovered objects




SEN_HW_BATTERY / Charge

SEN_HW_BATTERY / TimeLeft


WMI–DisksThis connector provides monitoring of the S.M.A.R.T.-enabled disks that are directly handled byWindows (and WBEM through the WMI service). Deactivates the connector if only MPIO disks (LUN Multi-Path Disk Device) are found.

Target

Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NECExpress5800, Sun Fire (x64)




265Connectors


Version 2.7.28

Discovered objects







WMI - HBAThis connector provides the monitoring of HBA cards on all Windows-based systems through the WMIlayer (root/WMI namespace).

Target

Typical platform(s): Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NECExpress5800, Sun Fire (x64)


Instrumentation layer: WMI and Microsoft Fibre Channel Information tool


266Connectors


Version 2.7.28

Discovered objects


LUN (SEN_HW_LUN)









SEN_HW_LUN / AvailablePathCount


WMI–NetworkThis connector provides the monitoring of network cards on all Windows-based systems through theWMI layer (root/WMI namespace).

Target

Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NECExpress5800, Sun Fire (x64)




267Connectors


Version 2.7.28

Discovered objects










Index 268


Version 2.9.10

Index

- A -Abnormalities 54

Actions

Collection 64

Detection 64

Discovery 64Adaptec

AAC 127

Adaptec AAC-based RAID 127

Adaptec DPT-based RAID 126

Adaptec IOManager 125

Adaptec Storage Manager 126, 127

Adaptec Storage Manager DPT 126

Adaptec Storage Manager Web Edition 127

Adaptec Storage Manager Web Edition AAC 127

Adaptec StorMan (RAID) 125

Adaptec U320 HostRAID 125Adapter

Add 48

Create 48Adding the Hardware Application Class to anExisting Element 42

Agent 147, 203, 204

Dell iDRAC Management 136, 138

Fujitsu-Siemens Serveview WBEM 148

HP Insight Management Agents 165Agents 146

Brocade SNMP 128

EQLGROUP-MIB 135

fcSwitch 128

Fujitsu-Siemens Serveview 150

Hardware 23, 62

HP iLO / HP Insight Management 154

HP Insight Management 156, 157, 158,159, 160, 161, 162, 163, 164, 167

IBM Director Agent 5.20.x / 6.10.x 236, 237

Intel Server Manager 8 SNMP 208, 209

LSI MegaRAID SAS SNMP 216

NetApp SNMP 229

Promise FastTrack SNMP Agent 231

Quantum SNMP Agent 232

SNMP 132, 135

SNMP Agent 66, 131

SUN Blade Chassis CMM SNMP Agent 244

SUN Blade SP SNMP Agent 246

Vendor-specific 62AIX

Requirements 32Alerts

Conditions 82

Configuration 82ALOM

ALOM-CMT snapshot 248Application Classes 211

Battery 92

Blade 93

Capacity Report 93

Connector 95

CPU 89, 95, 97, 102

CPU Core 97

Disk Controller 92, 97, 109

Enclosure 92, 98, 100, 109

Fan 98, 102, 112

LED 100

Logical Disk 89, 100, 102

LUN 101

Main 64, 65, 102

Memory 89, 103

MS_HW_BATTERY 136, 138, 143, 153,170, 205

MS_HW_BLADE 170

MS_HW_CPU 136, 147, 148, 165

MS_HW_DISKCONTROLLER 138

MS_HW_ENCLOSURE 138, 142, 143, 153,165, 170, 200, 203, 204, 206

MS_HW_FAN 136, 138, 143, 147, 148, 153,165, 170

MS_HW_LED 205

MS_HW_LOGICALDISK 138, 153, 170, 200,206

MS_HW_LUN 176

MS_HW_MEMORY 136, 147, 148, 153, 165,170

MS_HW_NETWORK 136, 143, 144, 153,165, 175, 181, 200

MS_HW_NETWORKCARD 170

MS_HW_OTHERDEVICE 138, 143, 153,165, 170, 200, 205

MS_HW_PHYSICALDISK 138, 143, 153,170, 200, 205, 206

MS_HW_POWERSUPPLY 136, 138, 143,147, 148, 153, 165, 170, 205

Index 269


Version 2.9.10

Application Classes 211

MS_HW_ROBOTICS 142, 203, 204

MS_HW_TAPEDRIVE 142, 203, 204

MS_HW_TEMPERATURE 136, 147, 148,165, 170, 205

MS_HW_VOLTAGE 136, 147, 148

Network 104

Other Device 106

Physical Disk 64, 82, 89, 107

Power Supply 108, 112

Robotics 109

S_HW_ENCLOSURE 136

SEN_HW_BATTERY 135, 156, 178, 199,264

SEN_HW_BLADE 129, 130, 134, 146, 152,155, 182, 209

SEN_HW_CPU 140, 150, 163, 167, 171,173, 184, 189, 190, 191, 192, 193, 195, 197,198, 207, 208, 230, 240, 246, 247, 256, 257,260, 263

SEN_HW_CPUCORE 257

SEN_HW_DISKCONTROLLER 125, 126, 127,139, 141, 149, 156, 157, 159, 162, 172, 174,177, 178, 179, 187, 188, 189, 190, 191, 192,193, 194, 195, 196, 199, 202, 207, 209, 212,213, 214, 215, 216, 217, 218, 223, 231, 232,236, 237, 255, 256, 258, 262, 264

SEN_HW_ENCLOSURE 128, 129, 130, 132,133, 134, 135, 140, 145, 146, 150, 152, 154,155, 157, 163, 167, 168, 171, 173, 182, 184,189, 190, 191, 192, 193, 195, 197, 198, 199,203, 207, 208, 209, 210, 228, 229, 230, 232,234, 237, 238, 239, 240, 241, 242, 243, 244,245, 246, 247, 248, 250, 260, 263

SEN_HW_FAN 128, 129, 130, 132, 133,134, 135, 140, 145, 146, 150, 152, 154, 155,163, 164, 167, 168, 171, 182, 183, 185, 188,189, 190, 191, 192, 193, 195, 197, 198, 199,201, 208, 209, 210, 228, 229, 230, 232, 234,237, 238, 240, 241, 243, 244, 245, 248, 249,250, 260, 263

SEN_HW_LED 152

SEN_HW_LOGICALDISK 125, 126, 127, 132,135, 139, 141, 149, 156, 157, 159, 162, 168,172, 177, 178, 188, 189, 190, 191, 192, 193,194, 195, 196, 199, 202, 212, 213, 214, 215,216, 217, 218, 223, 229, 231, 234, 235, 236,237, 256, 262

SEN_HW_LUN 220, 265

SEN_HW_MEMORY 140, 150, 160, 161,163, 167, 171, 179, 189, 190, 191, 192, 193,195, 197, 198, 207, 208, 230, 240, 246, 247,250, 251, 252, 260, 263

SEN_HW_NETWORK 128, 129, 130, 145,158, 159, 161, 167, 168, 173, 176, 184, 186,199, 207, 209, 218, 219, 221, 224, 225, 226,227, 229, 234, 235, 237, 238, 254, 260, 263,265, 266

SEN_HW_OTHERDEVICE 129, 131, 133,134, 140, 152, 154, 155, 157, 159, 167, 168,199, 209, 234, 237, 238, 240, 241, 243, 245,248

SEN_HW_PHYSICALDISK 125, 126, 127,132, 135, 139, 141, 149, 156, 157, 159, 162,168, 172, 174, 177, 178, 179, 187, 188, 189,190, 191, 192, 193, 194, 195, 196, 199, 202,207, 209, 212, 213, 214, 215, 216, 217, 218,223, 229, 231, 233, 234, 236, 237, 243, 246,247, 248, 255, 256, 258, 261, 262, 264

SEN_HW_POWERSUPPLY 128, 129, 130,132, 133, 134, 135, 140, 145, 146, 150, 152,154, 155, 163, 164, 167, 168, 171, 182, 183,185, 188, 189, 190, 191, 192, 193, 195, 197,198, 199, 209, 210, 228, 229, 230, 232, 234,237, 238, 240, 241, 243, 244, 245, 248, 250,260, 263

SEN_HW_ROBOTIC 232, 237, 239, 241

SEN_HW_TAPEDRIVE 232, 237, 239, 241,242, 259

SEN_HW_TEMPERATURE 128, 129, 130,132, 133, 134, 135, 140, 145, 146, 150, 152,154, 155, 163, 167, 168, 171, 182, 185, 188,189, 190, 191, 192, 193, 195, 197, 198, 199,201, 203, 208, 210, 228, 229, 230, 233, 234,237, 238, 241, 243, 244, 245, 246, 247, 248,249, 250, 260, 263

SEN_HW_VOLTAGE 140, 150, 168, 171,182, 185, 188, 189, 190, 191, 192, 193, 195,197, 198, 201, 203, 208, 210, 228, 230, 240,243, 244, 245, 246, 247, 248, 249, 250, 260,263

Tape Drive 109

Temperature 64, 110, 112

Voltage 111, 112Architecture 58, 60, 64

- B -Baselines

BMC ProactiveNet Performance Management 54

Index 270


Version 2.9.10

Baselines

Generation 54

Manage 54

Requirements 54BMC

ProactiveNet Performance Management 48BMC ProactiveNet Performance Management

Abnormalities 54

Baselines 54

Key Performance Indicators 54

KPI 54Brocade SAN Switch 128

- C -Cisco

Cisco UCS 130

Cisco UCS Manager (Blade, FabricInterconnect Switch) 130

Cisco UCS Manager (XML API) 130

Cisco UCS XML API 130Collection

Process 65Commands 211

arcconf 125

cediag 252

cestat 252

CmdTool2 217

dd 255, 258, 259

HP-UX system 173, 174, 175, 176, 177

IBM AIX system 176, 183, 184, 185, 186,187, 207

ifconfig 254

iostat 255, 258, 259

kstat 254

Linux system 219

lsiutil 213, 214

MegaCli 217

ndd 254

psrinfo 256, 257

Raidctl 256

System 125, 171, 173, 174, 175, 176, 177,178, 179, 183, 184, 185, 186, 187, 199, 200,207, 210, 213, 214, 217, 218, 219, 220, 221,223, 228, 233, 240, 245, 248, 249, 250, 251,252, 254, 255, 256, 257, 258, 259

Windows system 217Configuration 112

Alerts 82

Sudo 32, 34, 37, 39Connector 66, 117, 125, 127, 128, 129, 130,131, 132, 133, 134, 135, 136, 138, 140, 141,142, 145, 146, 147, 148, 150, 152, 153, 154,155, 156, 157, 158, 159, 160, 161, 162, 163,164, 167, 168, 170, 171, 172, 173, 174, 175,176, 178, 179, 181, 183, 184, 185, 186, 187,188, 189, 190, 191, 192, 193, 194, 195, 196,197, 198, 199, 200, 201, 202, 203, 204, 205,206, 207, 208, 209, 210, 212, 213, 214, 215,216, 217, 218, 219, 220, 223, 224, 225, 226,227, 228, 229, 230, 231, 232, 233, 234, 235,236, 237, 238, 239, 240, 241, 242, 243, 244,245, 246, 247, 248, 249, 251, 254, 255, 256,257, 258, 260, 261, 262, 263, 264, 265, 266

Controller

LSI RAID 213, 214Credentials 173, 174, 175, 177, 178, 183, 189,191, 193, 210, 214, 218, 219, 220, 221, 233,248, 250, 251, 254, 255, 256, 258, 259

Custer's management interface 205

- D -Data Domain Storage Appliance 132

DataDirect Networks (DDN) Disk Array 131

Debug Mode 39

Enabling 85Default system wattage 39

Dell

Dell CMC (Dell Chassis ManagementController) 133

Dell DRAC Dell Remote Access Card 134

Dell EqualLogic MIBs 135

Dell EqualLogic PS Series 135

Dell EqualLogic PS Series Disk Systems 135

Dell OpenManage Array Manager 139

Dell OpenManage Server 139, 140, 141

Dell OpenManage Server Administrator 139, 140, 141

Dell OpenManage Storage Manager 141

DELL PERC RAID 139, 141

Dell PowerEdge 136, 138, 139, 140, 141

Dell PowerVault TL2000 142

Dell PowerVault TL4000 142

Dell SNMP Agent 142

Dell's iDRAC Management Card 136, 138

DELL-SHADOW-MIB 142Detection

Process 65

Index 271


Version 2.9.10

Devices 256

Batteries 136, 138, 143, 153, 170, 205

Battery 92, 135, 156, 178, 199, 264

Blade 93, 129, 130, 134, 146, 152, 182,209

Cache Memory 170

Controller 125, 126, 127, 139, 141

Controllers 170

CPU Cores 257

Disk 63

Disk controller 97, 106, 125, 138, 149, 156,157, 159, 162, 172, 174, 177, 178, 179, 187,188, 189, 190, 191, 192, 193, 194, 195, 196,199, 202, 207, 209, 212, 213, 214, 215, 216,217, 218, 223, 231, 232, 236, 237, 255, 256,258, 262, 264

Disk enclosure 63

Disk Shelves 170

Disk Systems 170

EMU 170

Enclosure 146

Enclosure model 128, 129, 130, 132, 133,134, 135, 136, 138, 140, 142, 143, 145, 147,148, 150, 152, 153, 154, 155, 157, 163, 167,168, 171, 173, 182, 184, 189, 190, 191, 192,193, 195, 197, 198, 199, 200, 203, 204, 205,206, 207, 208, 209, 210, 211, 228, 229, 230,232, 234, 237, 238, 239, 240, 241, 242, 243,244, 245, 246, 247, 248, 250, 260, 263

Environment 146

Ethernet Ports 170

Fan 63, 98, 106, 128, 129, 130, 132, 133,134, 135, 140, 145, 146, 150, 152, 154, 155,163, 164, 167, 168, 171, 182, 183, 185, 188,189, 190, 191, 192, 193, 195, 197, 198, 199,201, 208, 209, 210, 228, 229, 230, 232, 234,237, 238, 240, 241, 243, 244, 245, 248, 249,250, 260, 263

Fans 136, 138, 143, 147, 148, 153, 168,170

Fiber Ports 170

HP 170

IO Module 170

LED 152

LEDs 205

Logical disk 100, 106, 125, 126, 127, 132,135, 139, 141, 149, 156, 157, 159, 162, 168,172, 177, 178, 188, 189, 190, 191, 192, 193,194, 195, 196, 199, 202, 212, 213, 214, 215,216, 217, 218, 223, 229, 231, 234, 235, 236,237, 256, 262

Logical disks 153, 200, 206

Logical disks, RAIDs 138

LUN 176, 220, 265

Management Blade 146

Memory module 63, 106, 140, 150, 160,161, 163, 167, 171, 179, 189, 190, 191, 192,193, 195, 197, 198, 207, 208, 230, 240, 246,247, 250, 251, 252, 260, 263

Memory modules 136, 147, 148, 153

Network cards 106, 128, 129, 130, 136,143, 144, 145, 153, 158, 159, 161, 167, 168,173, 175, 176, 184, 186, 199, 200, 207, 209,218, 219, 221, 224, 225, 226, 227, 229, 234,235, 237, 238, 254, 260, 263, 265, 266

Network interface 63

Non-RAID Disk 63

Other devices 138, 143, 153, 200, 205

Others 129, 133, 134, 140, 152, 154, 155,157, 159, 167, 168, 199, 209, 234, 237, 238,240, 241, 243, 245, 248

Physical disk 106, 125, 126, 127, 132, 135,139, 141, 149, 156, 157, 159, 162, 168, 172,174, 177, 178, 179, 187, 188, 189, 190, 191,192, 193, 194, 195, 196, 199, 202, 207, 209,212, 213, 214, 215, 216, 217, 218, 223, 229,231, 233, 234, 236, 237, 243, 246, 247, 248,255, 256, 258, 261, 262, 264

Physical disks 138, 143, 153, 170, 200,205, 206

Power supplies 63, 106, 128, 129, 130,132, 133, 134, 135, 136, 138, 140, 143, 145,146, 147, 148, 150, 152, 153, 154, 155, 163,164, 167, 168, 170, 171, 182, 183, 185, 188,189, 190, 191, 192, 193, 195, 197, 198, 199,205, 209, 210, 228, 229, 230, 232, 234, 237,238, 240, 241, 243, 244, 245, 248, 250, 260,263

Processor 63, 106, 140, 150, 163, 167,171, 173, 184, 189, 190, 191, 192, 193, 195,197, 198, 207, 208, 230, 240, 246, 247, 256,257, 260, 263

Processors 136, 147, 148

RAID 206

RAID Disk 63, 256

Raid Groups 170

RAIDs 125, 132, 135, 149, 153, 156, 157,159, 162, 168, 172, 177, 178, 188, 189, 190,191, 192, 193, 194, 195, 196, 199, 200, 202,212, 213, 214, 215, 216, 217, 218, 223, 229,231, 234, 235, 236, 237, 256, 262

Robotics 142, 203, 204, 232, 237, 239, 241

RS232 Bus 170

Index 272


Version 2.9.10

Devices 256

Tape drive 232, 237, 239, 241, 242, 259

Tape drives 142, 203, 204

Temperature 63

Temperature sensor 106, 128, 129, 130,132, 133, 134, 135, 140, 145, 150, 152, 155,163, 167, 168, 171, 182, 185, 188, 189, 192,193, 195, 199, 201, 203, 208, 210, 228, 229,230, 233, 234, 237, 238, 241, 243, 244, 245,246, 247, 248, 249, 250, 260, 263

Temperature sensors 136, 147, 148, 205

Temperatures 170

Voltage 63

Voltage sensor 106, 140, 150, 168, 171,182, 185, 188, 189, 192, 193, 195, 201, 203,208, 210, 228, 230, 240, 243, 244, 245, 246,247, 248, 249, 250, 260, 263

Voltage sensors 136, 147, 148Discovery

Process 65Disk 125, 126, 127, 132, 139, 141, 149, 156,159, 162, 172, 177, 178, 179, 187, 188, 189,190, 191, 192, 193, 194, 195, 196, 199, 207,209, 213, 214, 216, 218, 231, 234, 235, 237,243, 255, 256, 258, 261, 262

Physical 248, 264DPT 126

DuplexMode 161

- E -ECOM 143

EMC SMI-S Agent 143

Emulex HBAs 144

Environment 60

lom 250

Monitoring 69

prtdiag 250Error Count Auto-reset After 39

- F -Fan

Monitoring 69FAQ 85

FC ports 205, 206

Fibre Alliance SNMP Agent (Switches) 145

Files

.hdf 65, 66, 117

rsmcfg.properties 112Firewall 90

Fujitsu 148

BX Blade Servers 146

FSC BX Blade Servers 146

Fujitsu-Siemens 146

Fujitsu-Siemens Blade 146

Fujitsu-Siemens PRIMERGY 147, 212, 213,215, 216

Fujitsu-Siemens Serverview 150

Fujitsu-Siemens ServerView RAID Agent 149

Fujitsu-Siemens Serveview 147

- G -Generate

Baselines 54Getting Started 20

- H -HBA 265

hbacmd 144

Hitachi 153

Hitachi BladeSymphony Chassis 152

Hitachi BladeSymphony Chassis ManagementModule 152

Hostname 39

HP 181

HP 9000 168, 173, 174, 175, 176, 178

HP BladeSystem 154

HP BladeSystem - Telnet/SSH 155

HP BladeSystem Onboard Administrator 155

HP EVA Storage Systems 170

HP Insight Management Agent - HBA 158

HP Insight Management Agent - Network 161

HP Insight Management Agent - Server - WMI 167

HP Insight Management Agent (v8.20 orlower) - Memory 161

HP Insight Management Agent (v8.25 orhigher) - Memory 160

HP Insight Management Agent–Drive Array 156

HP Insight Management Agent–Fiber Array 157

Index 273


Version 2.9.10

HP 181

HP Insight Management Agent–IDE Storage 159

HP Insight Management Agent–iLO 159

HP Insight Management Agents 157, 158,159, 160, 161, 162, 163, 164, 167

HP Insight Management Agent–SCSI Storage 162

HP Insight Management Agent–Server 163

HP Insight Management Agent–Server (Alpha) 164

HP Integrity 173, 174, 175, 176, 178

HP MP/GSP card (iLO) 168

HP MSA 2000 & P2000 168

HP MSA Management Card 168

HP NetServer 171, 172

HP OpenVMS 158, 159, 160, 161, 162, 163,164

HP ProLiant 156, 157, 158, 159, 160, 161,162, 163, 164, 167

HP StorageWorks EVA - SSSU - PM 170

HP StorageWorks MSA P2000 168

HP SuperDome 173, 174, 175, 176, 178

HP TopTools Agent 171

HP TopTools NetRaid Agent 172

HP Tru64 158, 159, 160, 161, 162, 163,164

HP-UX 174, 175, 177, 178, 179

HP-UX - Network 176

HP-UX - SASMGR Managed Disks 177

HP-UX - Smart Array RAID 178

HP-UX Smart Array Configuration Utility 178

HP-UX Support Tools Manager (STM) 179

HP-UX system commands 176, 177

HP-UX–Disks 174

HP-UX-STM 179HP-UX

Requirements 32

- I -IBM

BM-3100-MIB 203, 204

IBM AIX 176, 183, 185, 186, 187, 207

IBM AIX - HBA 186

IBM AIX lspath 176

IBM AIX system commands 176, 183, 184,185, 186, 187, 207

IBM AIX–CHRP Environment 183

IBM AIX–Common 184

IBM AIX–Environment (ue sensor) 185

IBM AIX–SCSI disks 187

IBM BladeCenter 182

IBM BladeCenter Management Module 182

IBM Director Agent 3.x 188

IBM Director Agent 3.x–Windows 188

IBM Director Agent 4.x 189, 190

IBM Director Agent 4.x–Linux 189, 190

IBM Director Agent 5.10.x 191, 192

IBM Director Agent 5.10.x–Linux 191

IBM Director Agent 5.10.x–Windows 192

IBM Director Agent 5.20.x / 6.10.x 236, 237

IBM Director Agent 5.20.x–Linux 193

IBM Director Agent 5.20.x–ServeRAID - Linux 194

IBM Director Agent 5.20.x–ServeRAID -Windows 196

IBM Director Agent 5.20.x–Windows 195

IBM Director Agent 6 198

IBM Director Agent 6 - Linux 197

IBM Director Agent 6 - Windows 198

IBM Director Agent 6.1.x 197

IBM DS (LSI) Disk Arrays (smcli) 199, 200

IBM eServer p5 176, 183, 184, 185, 186,187, 207

IBM Netfinity 188, 189, 190, 191, 192, 195,196, 197, 198, 236, 237

IBM Netfinity Manager 5.20.x–Basic 201

IBM Netfinity Manager 5.20.x–Disks 202

IBM Netfinity Manager 5.20.x–Normal 203

IBM pSeries 176, 183, 184, 185, 186, 187,207

IBM RS/6000 176, 183, 184, 185, 186, 187,207

IBM SAN disk arrays 205, 206

IBM SNMP Agent SNMP 203, 204

IBM TS3100 203, 204

IBM TS3100 Tape Libraries 203, 204

IBM v7000 205, 206

IBM v7000 Disk Arrays 206

IBM VIO Server 207

IBM xSeries 188, 189, 190, 191, 192, 195,196, 197, 198, 236, 237

In case of Status parameter value is UNKNOWN 39

Install / Un-install

Adding BPM Express for Hardware to anElement Profile 28

Index 274


Version 2.9.10

Install / Un-install

BMC® Performance Manager Express forHardware for BMC® Portal 22

BPM Express for Hardware 24

Hardware Agents 23

Migration 24

Package 22, 24

Prerequisites 24

Procedure 25

Removing BPM Express for Hardware fromManaged Elements 43

Targeted Computers 22

Uninstall 24

Un-installing BPM Express for Hardware 43

Uninstalling BPM Express for Hardware fromthe Portal 44

Integration

BPM Express for Hardware 61Integration Service Agent 48

Intel

Intel Base Board 5 208

Intel Modular Server 209

Intel Server Manager 8 SNMP Agents 208,209

Interaction 60

Introduction 20

IntrusionStatus 150

IPMI 261

IPMI–In-band(IpmiTool) 210

ipmitool 210

- K -Key Performance Indicators


Manage 54KPI


Manage 54

- L -LinkStatus auto-reset after 39

Linux 211

Linux - Emulex HBAs (hbacmd) 218

Linux - Multipath 220

Linux - QLogic HBAs (scli) 221

Linux–Network 219

Requirements 32localhost 211

LSI

LSI 1030-based GAM Server 212

LSI 1030-based GAM Server (Alternate MIB) 213

LSI GAM Server 213

LSI Logic - LsiUtil - RAID (Windows) 213,214

LSI Logic MegaRAID PowerConsole 215

LSI MegaCli 217

LSI MegaRAID PowerConsole 215

LSI MegaRAID SAS SNMP Agent 216

LSI RAID controller 213, 214

LSI/Mylex GAM Server 218

LsiLogic MegaRAID SAS 216

LsiLogic MegaRAID SAS (Newer Controllers) 216

- M -Manage

Baselines 54

Key Performance Indicators 54

KPI 54Mechanism 58

MegaCli (LSI) managed RAID card 223

MegaCLI Managed Raid Controllers 223

Metrics

Fan Speed 112

Power Supply Used Capacity 112

Temperature 112

Voltage 112MIB-2 Standard SNMP Agent

MIB-2 Standard SNMP Agent - NetworkInterfaces 224

MIB-2 Standard SNMP Agent - NetworkInterfaces - Linux 225

MIB-2 Standard SNMP Agent - NetworkInterfaces - Solaris 227

MIB-2 Standard SNMP Agent - NetworkInterfaces - Windows 226

Microsoft Fibre Channel Information tool 265

Missing Device Detection 39

Monitor Type 48

Monitoring 66

Basics 66


Index 275


Version 2.9.10

Monitoring 66

Connector 78

CPU 75

Devices 66, 75

Disk Controllers 71

Disks 66, 71

Enclosure 68

Environment 66, 69

Fans 69

Memory Modules 75

Missing Device 77

Network Interfaces 75

Physical Disks 71

Power Supplies 69

Processors 75

Structure 66

Temperatures 69

Voltages 69Motherboard Monitor 228

Mylex GAM Servers 218

- N -NEC

NEC ESMPRO Agent 230NetApp

NetApp Filer - SNMP Agent 229

- O -Operating System

HP-UX 181Operating Systems 15, 128, 136, 138, 179,233

HP OpenVMS 131, 156, 157, 158, 159, 160,161, 162, 163, 164, 224, 235

HP Tru64 131, 156, 157, 158, 159, 160,161, 162, 163, 164, 224

HP-UX 173, 174, 175, 176, 177, 178, 224,235

IBM AIX 176, 183, 184, 185, 186, 187, 207,235

Linux 125, 126, 127, 131, 139, 140, 141,144, 149, 150, 154, 156, 157, 158, 159, 160,161, 162, 163, 165, 172, 189, 191, 193, 194,197, 208, 210, 212, 213, 215, 216, 218, 219,220, 221, 223, 225, 230, 231, 235, 236, 260,261, 262, 263

Microsoft Windows 141, 149, 150, 154,156, 157, 158, 159, 160, 161, 162, 163, 167,171, 172, 188, 190, 192, 195, 196, 198, 201,202, 203, 208, 211, 212, 213, 214, 215, 216,217, 218, 226, 228, 230, 231, 235, 237, 264,265, 266

Network 224

Storage Device 129, 132, 135, 142, 145,168, 170, 199, 200, 203, 204, 205, 206, 224,229, 232, 234, 237, 238, 239, 241, 242

SUN 161

Sun Solaris 125, 144, 156, 157, 158, 159,160, 161, 162, 163, 210, 211, 223, 227, 235,240, 245, 248, 249, 250, 251, 252, 254, 255,256, 257, 258, 259

Tru64 235

Windows 125, 126, 127, 131, 139, 140OS command 66

Overview 58, 60

- P -Parameters 211, 261

Application Collection Status 86, 112

Available Path Count 101

AvailablePathCount 176, 220, 265

AvailablePathInformation 220

Bandwidth Utilization 104

Battery Status 71, 97

BatteryStatus 125, 149, 157, 217, 223, 231

Charge 92, 264

Color 100

Connected Ethernet/Fiber Ports 93

Connected To Physical Address 104

Connection Type 104

connector 182, 252, 259

Controller Status 71, 97

ControllerStatus 125, 138, 156, 157, 162,177, 194, 196, 199, 209, 232, 236, 237, 262

Corrected Error Count 75, 89

CorrectedErrorCount 95

Credentials 252

CurrentSpeed 95, 147, 148, 165, 167

Degrees Below Warning 93

Duplex Mode 104

DuplexMode 129, 207

Energy Usage 93

Error Count 71, 75, 82, 89, 103, 107

Error Percent 75, 81, 104

Index 276


Version 2.9.10

Parameters 211, 261

ErrorCount 100, 128, 129, 135, 142, 144,145, 149, 150, 157, 161, 165, 173, 176, 179,184, 186, 187, 203, 204, 207, 209, 216, 218,219, 224, 225, 226, 227, 241, 251, 254, 255,258, 259, 265, 266

Failure 127

Intrusion Status 68

IntrusionStatus 98, 140, 189, 190, 191,192, 193, 195

Link Speed 104

Link Status 75, 81, 104

LinkSpeed 128, 129, 130, 144, 145, 153,161, 165, 168, 170, 175, 176, 207, 209, 218,221, 224, 225, 226, 227, 265

LinkStatus 128, 129, 130, 136, 144, 145,158, 161, 165, 167, 168, 170, 173, 175, 176,181, 184, 186, 207, 209, 218, 221, 224, 225,226, 227, 229, 234, 235, 237, 238, 254, 260,263, 265, 266

Locator 92, 93, 95, 97, 98, 100, 101, 104,106, 107, 108, 109, 110, 111

Machine Status 86, 102

Memory Size 93

Modification 84

Mount Count 109

MountCount 142, 232, 237, 241, 242

MoveCount 241

MoveCount (Cumulative) 109

Needs Cleaning 109

NeedsCleaning 232, 237, 239

Percent 97

Physical Address 104

Physical CPU Count 93

Power Consumption 68, 93

PowerConsumption 129, 130, 136, 152,155, 240, 260

Predicted Failure 71, 75, 82, 103, 107

PredictedFailure 95, 125, 126, 127, 149,156, 157, 159, 162, 163, 170, 209, 231, 233,246, 247, 252, 264

Received Bytes 104

Received Bytes Rate 104

ReceivedBytesRate 128, 129, 130, 144,145, 161, 165, 176, 207, 209, 218, 224, 225,226, 227

ReceivedPacketsRate 128, 129, 130, 144,145, 161, 165, 176, 207, 218, 224, 225, 226,227, 265

Reinitialization 89

Speed 69, 98, 128, 130, 135, 140, 146,150, 152, 170, 171, 181, 188, 189, 190, 191,192, 193, 195, 197, 198, 208, 209, 210, 228,243, 244, 248, 249, 260, 263

Speed Percent 69

SpeedPercent 98, 155, 182, 249, 260, 263

Statis 126

Status 68, 69, 71, 75, 77, 78, 81, 82, 92,93, 95, 97, 98, 100, 101, 103, 104, 106, 107,108, 109, 110, 111, 112, 125, 127, 128, 129,130, 131, 132, 135, 136, 138, 139, 140, 141,142, 143, 144, 145, 146, 147, 148, 149, 150,152, 153, 154, 155, 156, 157, 158, 159, 160,161, 162, 163, 164, 165, 167, 168, 170, 171,172, 173, 174, 175, 176, 177, 178, 179, 181,182, 183, 184, 187, 188, 189, 190, 191, 192,193, 194, 195, 196, 197, 198, 199, 200, 201,202, 203, 204, 205, 206, 207, 208, 209, 210,212, 213, 214, 215, 216, 217, 218, 221, 223,224, 225, 226, 227, 229, 230, 231, 232, 233,234, 235, 236, 237, 238, 239, 240, 241, 242,243, 244, 245, 246, 247, 248, 249, 250, 251,252, 254, 255, 256, 257, 258, 260, 262, 263,264, 265, 266

StatusInformation 136, 138, 142, 143, 144,147, 148, 152, 153, 165, 168, 175, 181, 197,198, 200, 203, 204, 205, 206, 207, 218, 221,236, 237, 265

Temperature 69, 110, 128, 129, 130, 132,135, 136, 140, 146, 147, 148, 150, 152, 154,155, 163, 165, 168, 170, 171, 182, 188, 189,190, 191, 192, 193, 195, 197, 198, 203, 205,208, 210, 228, 229, 230, 233, 234, 237, 238,241, 243, 244, 245, 246, 247, 248, 249, 250,260, 263

Temperature sensors 154, 190, 191, 197,198

Test Report 78, 95

Threshold 84

TimeLeft 264

Total Logical Disk Size 93

Total Physical Disk Size 93

Total Unallocated Space 93

Transmitted Byte Rate 104

Transmitted Bytes 104

TransmittedBytesRate 128, 129, 130, 144,145, 161, 165, 176, 207, 209, 218, 224, 225,226, 227

TransmittedPacketsRate 128, 129, 130,144, 145, 161, 165, 176, 207, 218, 224, 225,226, 227, 265

UnallocatedSpace 132, 168, 170

Index 277


Version 2.9.10

Parameters 211, 261

Unmount Count 109

usagecount 241

Used Capacity 69

UsedCapacity 108

UsedTime 97

UsedWatts 155, 163

Voltage 69, 81, 111, 140, 147, 148, 150,168, 171, 182, 185, 188, 189, 190, 191, 192,193, 195, 197, 198, 203, 208, 210, 228, 230,240, 243, 244, 245, 246, 247, 248, 249, 250,260, 263

Voltage sensors 190, 191, 197, 198Performance manager 25

Platforms 154, 206, 211

Cisco MDS9000 Series FC switches 129

Cisco UCS 130

Data Domain Storage Appliance 132

Dell 4000 Tape Library 142

Dell EqualLogic PS Series Disk Systems 135

Dell M1000E Chassis 133

Dell PowerEdge 134, 136, 138, 140, 141,219, 220, 233, 264, 265

Dell TL2000 Tape Library 142

Dell TL2000/4000 Tape Library 142

Disk Array 153, 200, 205, 229, 234

Fujitsu-Siemens BX Blade Servers 146

Fujitsu-Siemens PRIMERGY 125, 126, 127,147, 148, 149, 150, 212, 213, 215, 216, 219,220, 231, 233, 264, 265

Generic Servers 208, 209

Hitachi BladeSymphony Chassis ManagementModule 152

HP 9000 168, 173, 174, 175, 176, 177,178, 179, 181

HP BladeSystem - Telnet/SSH 155

HP EVA Storage Systems 170

HP Integrity 173, 174, 175, 176, 177, 178,179, 181

HP NetServer 171, 172

HP ProLiant 131, 156, 157, 158, 159, 160,161, 162, 163, 164, 165, 167, 219, 220, 233,264, 265

HP StorageWorks EVA - SSSU 170

HP StorageWorks MSA P2000 168

HP SuperDome 173, 174, 175, 176, 177,178, 179, 181

IBM BladeCenter 182

IBM DSxxxx Disk Array 199

IBM eServer p5 176, 183, 184, 185, 186,187, 207

IBM Netfinity 188, 189, 190, 191, 192, 193,194, 195, 196, 197, 198, 201, 202, 203, 236,237

IBM pSeries 176, 183, 184, 185, 186, 187,207

IBM RS/6000 176, 183, 184, 185, 186, 187,207

IBM Tape Library 3584 239

IBM TS3100 Tape Library 203, 204

IBM xSeries 188, 189, 190, 191, 192, 193,194, 195, 196, 197, 198, 219, 220, 233, 236,237, 264, 265

Integrity 168

Linux Server with HBAs 218, 221

NEC Express5800 220, 230, 264, 265

Reference table 117

SAN Switches 128, 145, 238

SPARC Enterprise Mx000 240

Storage Libraries 237

StorageTek LSeries 241

StorageTek StreamLine 242

SUN Blade Chassis 244

SUN Blade with ILOM cards 246, 247

Sun Fire 219

Sun Fire (SPARC T1, T2) 257

Sun Fire (SPARC T1/T2) 248

Sun Fire (SPARC) 243, 245, 249, 250, 251,252, 254, 255, 256, 258, 259

Sun Fire (x64) 125, 210, 220, 233, 264,265

SuperDome 168

Supported 15

VMware ESX4i 261, 262

VMware ESXi 260, 263

WBEM 200

Windows 264

Windows servers 213, 214PM 25

Polling interval 32, 34, 37, 39

Power Supplies

Monitoring 69Prerequisites 58

Process

Collection 65

Detection 65

Discovery 65Promise FastTrack 231

Properties 39

Index 278


Version 2.9.10

Properties 39

[Execution] Credentials 32

[Execution] Password 32

[Execution] Username 32

[Root] Credentials 32

[Root] Password 32

[Root] Username 32

[SNMP v3] Authentication Password 32, 34,37, 39

[SNMP v3] Authentication Protocol 32, 34,37, 39

[SNMP v3] Privacy Password 32, 34, 37, 39

[SNMP v3] Privacy Protocol 32, 34, 37, 39

[SNMP v3] Username 32, 34, 37, 39

[SSH] Passphrase 32, 34, 39

[SSH] Private Key 32, 34, 39

[Telnet/SSH/IPMI] Password 39

[Telnet/SSH/IPMI] Username 39

[Telnet/SSH] Password 32

[Telnet/SSH] Username 32

[UCS] Password 39

[UCS] SSL Encryption 39

[UCS] Username 39

[WBEM] Credentials 32

[WBEM] Multi-Tier Authentication Server 32, 39

[WBEM] Namespace 32, 34, 39

[WBEM] Password 32, 39

[WBEM] Port 32, 34, 39

[WBEM] Transport Protocol 32, 34, 39

[WBEM] Username 32, 39

[WMI] Password 37

[WMI] Username 37

AWK timeout 112

Collection interval 32, 34, 37, 39

Credential Options 32

Debug Mode 32, 34, 37

Default system wattage 32, 34, 37

Disable Connectors 112

Error Count Auto-reset After 32, 34, 37

Force nAwk 112

Force SNMP Protocol Activation 112

Force SSH 112

Force Telnet 112

Force WMI Script 112

Hostname 32, 34, 37

In case of Status parameter value isUNKNOWN 32, 34

In case of Status parameter value isUNKNOWN... 37

LinkStatus auto-reset after 34, 37

Missing Device Detection 32, 34, 37

net.sentrysoftware.bpm.hardware.fan.speed 112

net.sentrysoftware.bpm.hardware.forcenawk 112

net.sentrysoftware.bpm.hardware.forceSSH 112

net.sentrysoftware.bpm.hardware.forceTelnet 112

net.sentrysoftware.bpm.hardware.forceWMIScript 112

net.sentrysoftware.bpm.hardware.powersupply.usedcapacity 112

net.sentrysoftware.bpm.hardware.preSelectedConnectors.hostname 112

net.sentrysoftware.bpm.hardware.ssh.port 112

net.sentrysoftware.bpm.hardware.sshTimeout.default 112

net.sentrysoftware.bpm.hardware.sshTimeout.hdf 112

net.sentrysoftware.bpm.hardware.telnet.port 112

net.sentrysoftware.bpm.hardware.telnetTimeout.default 112

net.sentrysoftware.bpm.hardware.telnetTimeout.hdf 112

net.sentrysoftware.bpm.hardware.temp.temperature 112

net.sentrysoftware.bpm.hardware.volt.voltage 112

net.sentrysoftware.bpm.hardware.wbemActivation 112

net.sentrysoftware.bpm.hardware.wbemNamespace 112

net.sentrysoftware.bpm.hardware.wbemTimeout.default 112

net.sentrysoftware.bpm.hardware.wmiNamespace 112

net.sentrysoftware.bpm.hardware.wmiTimeout.default 112

Perform Garbage Collector 112

Pre-Selected Connectors 112

Reflect Fan Speed value 112

Reflect PowerSupply UsedCapacity value 112

Reflect Temperature value 112

Reflect Voltage value 112

Index 279


Version 2.9.10

Properties 39

Reflect AvailablePathCount value 112

SNMP Community 32, 34, 37

SNMP Port 34, 37, 112

SNMP version 32, 34, 37

SSH Port 112

SSH Timeout 112

Telnet Port 112

Telnet timeout 112

Telnet/SSH Password 34

Telnet/SSH Username 34

WBEM Activation 112

WBEM Credentials 34, 37

WBEM namespace 112

WBEM Password 34, 37

WBEM timeout 112

WBEM Username 34, 37

WMI namespace 112

WMI Script 112

WMI timeout 112

- Q -Quantum (ADIC) Based Tape Libraries 232

- R -RAID 126, 127, 139, 141

Reference guide 92

Remote Service Monitor 22, 23

Remote Service Monitor program 24

Report 140

Reporting

Energy Usage 80

Ethernet/Fiber Port Traffic 79Requirements 62

Hardware Agent 15

Management Elements 15

Operating System 15RSM 22, 23, 24

- S -S.M.A.R.T. technology 71

Siemens 146, 147, 148

SmartMonTools 233

SMCLI 199

SMI-S 206

SMI-S Compliant Disk Arrays 234

SMI-S Compliant HBAs 235

SMI-S Compliant RAID Controller - Windows 237

SMI-S Compliant SAN Switches 238

SMI-S Compliant Storage Libraries 237SNIA

SNIA Compliant Tape Libraries 239SNMP 125, 126, 127, 128, 132, 138, 139, 140,141, 142, 145, 146, 149, 150, 152, 154, 156,157, 158, 159, 160, 161, 162, 163, 164, 172,182, 201, 202, 203, 204, 208, 209, 212, 213,215, 216, 224, 225, 226, 227, 229, 230, 231,232, 239, 241, 242, 244

SNMP Community 39

SNMP Port 39

SNMP version 39

Solaris 243, 245, 248, 249, 250, 251, 252,254, 255, 256, 257, 258, 259

Requirements 32SPARC

SPARC Enterprise Mx000 (XSCF) 240SSSU 170

Status

PowerConsumption 134

Speed 134

Temperature 134Storage 126, 127

Requirements 34StorageTek

StorageTek LSeries Tape Library 241

StorageTek StreamLine Tape Library 242Sudo 173

Configuration 32, 34, 37, 39

Requirements 37SUN

Sun Advanced Lights–Out Management(ALOM) card 243

Sun Advanced Lights-Out Management ALOMcard 243

SUN Blade Chassis 244

SUN Blade Chassis CMM SNMP Agent 244

SUN Blade SP SNMP Agent 246

Sun Explorer 248

Sun Fire (SPARC T1/T2) 248

Sun Fire (SPARC) 243

Sun Fire F12K/F15K/F20K/F25K SMS 245

SUN ILOM (SNMP) 246

SUN ILOM (SSH) 247

Index 280


Version 2.9.10

SUN

Sun Solaris 243, 245, 248, 249, 250, 251,252, 254, 255, 256, 257, 258, 259

Sun Solaris - Disks 258

Sun Solaris - Environment prtpicl 249

Sun Solaris - Fault Manager (Memory) 251

Sun Solaris - Network 254

Sun Solaris - Non-Sun Disks 255

Sun Solaris - Processors psrinfo 256System commands 144

Systems

AIX 32

HP-UX 32

Linux 22, 32

Solaris 32

Storage 34

Tru64 32

UNIX 22

Windows 22, 37

- T -Telnet/SSH 129, 133, 134, 155, 168, 205, 243,247

Temperature 167

Monitoring 69Threshold 28, 42, 69, 81, 82, 112

Modification 84Troubleshooting 85, 87, 89


Disk Controller 90

No information displayed 86

VMI connection 90Tru64

Requirements 32

- U -UCS 28

Utility

Emulex's hbacmd 218

Linux multipath 220

QLogic's SCLI 221

Sudo 220, 250, 251, 252, 254, 255, 256,258, 259

- V -VMware

VMware ESX4i 261, 262

VMware ESXi 3.x 260

VMware ESXi 4.x 263Voltage

Monitoring 69

- W -WBEM 143, 147, 153, 165, 189, 191, 193, 194,197, 206, 234, 235, 236, 237, 238, 260, 261,262, 263

WBEM query 66

Web 127

Windows 37

WMI 148, 167, 171, 188, 190, 192, 195, 196,198, 237, 264, 265

Dell PowerEdge 266

Fujitsu-Siemens PRIMERGY 266

HP ProLiant 266

IBM xSeries 266

NEC Express5800 266

Platforms 266

Sun Fire (x64) 266WMI protocol 90

Snippet source Back_Cover_BMC.xml not found!

Snippet source Back_Cover_Sentry.xml not found!

bmc® performance manager express for hardware … of contents 2 version 2.9.10 bmc performance...

Documents