bmc® performance manager express for hardware x.x 1.9.60... · user documentation january 2015 bmc...

User Documentation January 2015

BMC Performance ManagerExpress for Hardware

Version 2.9.25

Table of Contents 2

Version 2.9.25

BMC Performance Manager Express for Hardware

Table of Contents...........................................................................................................................21Targeted Computers

...........................................................................................................................21Package

...........................................................................................................................22Note on RSMs

...........................................................................................................................22Installing Appropriate Hardware Agents

...........................................................................................................................23Installing BPM Express for Hardware

...........................................................................................................................24Installation Procedure

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

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

...........................................................................................................................32Requirements for monitoring Storage systems

...........................................................................................................................35Requirements for monitoring Windows systems

...........................................................................................................................37Requirements for monitoring Other platforms

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

...........................................................................................................................41Installing a Patch

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

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

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

...........................................................................................................................45Integrating with BMC ProactiveNet Performance Management

...........................................................................................................................46Automatically Enabling the Application Classes

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

...........................................................................................................................53Managing Baselines and Key Performance Indicators

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

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

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

...........................................................................................................................62Monitoring with BPM Express for Hardware

...........................................................................................................................63Inside BPM Express for Hardware

...........................................................................................................................64The Detection Process

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

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

...........................................................................................................................65The Connectors

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

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

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

Table of Contents 3

Version 2.9.25


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

...........................................................................................................................73Disks: Physical Disks, Logical Disks and Disk Controllers

...........................................................................................................................76Devices: Processors, Memory modules and Network interfaces

...........................................................................................................................79Missing Device Detection

...........................................................................................................................79Connector Monitoring

...........................................................................................................................81Reporting

...........................................................................................................................81Ethernet/Fiber Port Traffic Report

...........................................................................................................................81Energy Usage Report

...........................................................................................................................83Thresholds

...........................................................................................................................83Configuring Alert Conditions

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

...........................................................................................................................86Troubleshooting

...........................................................................................................................86Enabling the Debug Mode

...........................................................................................................................87BPM Express for Hardware Shows Nothing

...........................................................................................................................88Monitors Nothing but Network Interfaces

...........................................................................................................................90Reinitializing Certain Parameters

...........................................................................................................................91Reinitializing the PM

...........................................................................................................................91Troubleshooting Connectivity Issues

...........................................................................................................................92Unable to See Disk Controller

...........................................................................................................................92Unable to connect to WMI

...........................................................................................................................94Application Classes

...........................................................................................................................94Battery

...........................................................................................................................95Blade

...........................................................................................................................96Capacity Report

...........................................................................................................................97Connector

...........................................................................................................................98CPU

...........................................................................................................................99CPU Core

...........................................................................................................................99Disk Controller

...........................................................................................................................100Enclosure

...........................................................................................................................100Fan

...........................................................................................................................102LED

...........................................................................................................................102Logical Disk

...........................................................................................................................103LUN

...........................................................................................................................104Main

...........................................................................................................................105Memory

...........................................................................................................................106Network

Table of Contents 4

Version 2.9.25


...........................................................................................................................108Other Device

...........................................................................................................................109Physical Disk

...........................................................................................................................110Power Supply

...........................................................................................................................111Robotics

...........................................................................................................................112Tape Drive

...........................................................................................................................112Temperature

...........................................................................................................................113Voltage

...........................................................................................................................114Special Note on Application Collection Status

...........................................................................................................................114Thresholds

...........................................................................................................................115Additional Configuration Properties

...........................................................................................................................121Connectors

...........................................................................................................................121Connector and Platform Reference Table

...........................................................................................................................129Adaptec IOManager

...........................................................................................................................130Adaptec StorMan (RAID)

...........................................................................................................................131Adaptec Storage Manager (DPT)

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

...........................................................................................................................132Brocade SAN Switch

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

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

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

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

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

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

...........................................................................................................................140Dell EqualLogic PS Series

...........................................................................................................................141Dell iDRAC - Server

...........................................................................................................................143Dell iDRAC - Storage

...........................................................................................................................144Dell OpenManage Array Manager

...........................................................................................................................145Dell OpenManage Server Administrator

...........................................................................................................................146Dell OpenManage Storage Manager

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

...........................................................................................................................148EMC Disk Arrays

...........................................................................................................................149EMC Isilon

...........................................................................................................................150Emulex HBAs (hbacmd)

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

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

...........................................................................................................................153Fujitsu-Siemens Serverview - WBEM

Table of Contents 5

Version 2.9.25


...........................................................................................................................154Fujitsu-Siemens Serverview - WMI

...........................................................................................................................155Fujitsu-Siemens ServerView RAID Agent

...........................................................................................................................156Fujitsu-Siemens Serverview

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

...........................................................................................................................158Hitachi BladeSymphony Chassis

...........................................................................................................................159Hitachi HDS Disk Arrays

...........................................................................................................................160Hitachi HDS USP/VSP Storage Systems

...........................................................................................................................162HP BladeSystem

...........................................................................................................................163HP BladeSystem - Telnet/SSH

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

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

...........................................................................................................................165HP Insight Management Agent - HBA

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

...........................................................................................................................167HP Insight Management Agent - iLO

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

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

...........................................................................................................................169HP Insight Management Agent - Network

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

...........................................................................................................................170HP Insight Management Agent - Server

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

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

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

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

...........................................................................................................................175HP MSA 2000 & P2000

...........................................................................................................................177HP StorageWorks EVA - SSSU - PM

...........................................................................................................................178HP TopTools Agent

...........................................................................................................................179HP TopTools NetRaid Agent

...........................................................................................................................180HP-UX - Common

...........................................................................................................................181HP-UX - Disks

...........................................................................................................................182HP-UX-HBA

...........................................................................................................................183HP-UX - Network

...........................................................................................................................183HP-UX - SASMGR Managed Disks

...........................................................................................................................184HP-UX - Smart Array RAID

...........................................................................................................................185HP-UX-STM

...........................................................................................................................186HP-UX - WBEM

...........................................................................................................................187HP-UX - WBEM Network

Table of Contents 6

Version 2.9.25


...........................................................................................................................188IBM AIX - CHRP Environment

...........................................................................................................................189IBM AIX - Common

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

...........................................................................................................................191IBM AIX - HBA

...........................................................................................................................192IBM AIX - SCSI disks

...........................................................................................................................193IBM AIX - LUN

...........................................................................................................................193IBM AIX - usysfault

...........................................................................................................................194IBM BladeCenter Management Module

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

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


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

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

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

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

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

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

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


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

...........................................................................................................................207IBM DS6000/8000 Disk Arrays

...........................................................................................................................208IBM Hardware Management Console (HMC)

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

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

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

...........................................................................................................................211IBM TS3100 Tape Libraries

...........................................................................................................................212IBM TS3200 Tape Libraries

...........................................................................................................................213IBM Storwize Disk Arrays - SSH

...........................................................................................................................214IBM VIO Server

...........................................................................................................................215Intel Base Board 5 Motherboards

...........................................................................................................................216Intel Modular Server

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

...........................................................................................................................218Localhost Monitoring Disabled

...........................................................................................................................219LSI 1030-based GAM Server

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

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

Table of Contents 7

Version 2.9.25


...........................................................................................................................221LSI Logic - LsiUtil - RAID

...........................................................................................................................222LSI Logic MegaRAID PowerConsole

...........................................................................................................................223LsiLogic MegaRAID SAS

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

...........................................................................................................................224LSI MegaCli

...........................................................................................................................225LSI/Mylex GAM Server

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

...........................................................................................................................226Linux - Network

...........................................................................................................................227Linux - Multipath

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

...........................................................................................................................229McData Fibre Switch

...........................................................................................................................230MegaCLI Managed Raid Controllers

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

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

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

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

...........................................................................................................................235Motherboard Monitor

...........................................................................................................................236NetApp Filer - SNMP Agent

...........................................................................................................................237NEC ESMPRO Agent

...........................................................................................................................238Promise FastTrack

...........................................................................................................................239Pure Storage FA Series (SSH)

...........................................................................................................................240QLogic HBAs - ESX

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

...........................................................................................................................242Quantum (ADIC) Enterprise Level Tape Libraries

...........................................................................................................................243SmartMonTools

...........................................................................................................................244SMI-S Compliant Disk Arrays

...........................................................................................................................245SMI-S Compliant HBAs

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

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

...........................................................................................................................247SMI-S Compliant Storage Libraries

...........................................................................................................................248SMI-S Compliant SAN Switches

...........................................................................................................................249SNIA Compliant Tape Libraries

...........................................................................................................................250SPARC Enterprise Mx000 (XSCF)

...........................................................................................................................251StorageTek LSeries Tape Library

...........................................................................................................................252StorageTek StreamLine Tape Library

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

Table of Contents 8

Version 2.9.25


...........................................................................................................................254SUN Blade Chassis

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

...........................................................................................................................256SUN ILOM (SNMP)

...........................................................................................................................257SUN ILOM (SSH)

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

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

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

...........................................................................................................................261Sun Solaris - Fault Manager (Memory and CPU)

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

...........................................................................................................................263Sun Solaris - Processor

...........................................................................................................................264Sun Solaris - Network

...........................................................................................................................265Sun Solaris - Non-Sun Disks

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

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

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

...........................................................................................................................268Sun Solaris - Sun Disks

...........................................................................................................................269Sun Solaris - Tape Drives

...........................................................................................................................269Windows - DiskPart

...........................................................................................................................270VMware ESXi 3.x

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

...........................................................................................................................272VMware ESX4i - Disks (VMware)

...........................................................................................................................273VMware ESXi 4.x

...........................................................................................................................274WMI - Battery

...........................................................................................................................274WMI - Disks

...........................................................................................................................275WMI - HBA

...........................................................................................................................276WMI - Network

Release Notes for v2.9.25

10


Version 2.9.25

What's NewBMC Performance Manager Express for Hardware now monitors the overall CPU and memorystatus of Oracle/Sun Solaris 11 servers.

A new configuration property (IPMI Timeout) is now available to allow users to override thedefault timeout value for executing a single IPMI command.

New Connectors

Several connectors were added to the current version of BMC Performance Manager Express forHardware. They enable the product to fully monitor the following systems:

Pure Storage FA Series (SSH) to monitor Pure Storage FA Series via SSH.

QLogic HBAs - ESX to monitor QLogic HBA adapters on ESX servers.

EMC Isilon to monitor EMC Isilon systems.

Changes and ImprovementsDell CMC: The blade's hostname was added to each blade display ID.

EMC Disk Arrays: The connector no longer verifies the presence of disk. This reduces theworkload on the EMC SMI-S Provider and reduces the risk of the connector failing to query theEMC SMI-S Provider.

IBM BladeCenter Chassis: Embedded switches, passthroughs, and management modules arenow monitored. The IBM Storwize (SSH) connector supports IBM Storwize v3700 systems. SPARC Enterprise Mx000 (XSCF): Negative voltage sensors, such as -12V, are discovered.WMI - HBA Connector:

The connector now uses the LUN's naa.ID to identify LUNs. Using the naa.ID helps link LUNsto the Storage System's volume as they share this unique identifier code.

The connector displays the disk's Windows MPIO ID as well as the drive letters and partitionnames of any volumes on that LUN. A typical LUN ID will therefore read:naa.60616043312F05A4308DC65F111 (MPIO Disk0 - C:(OS) D:(Data))

Fixed IssuesAdaptec Storman Connector: The connector supports a new Physical Disks command outputto prevent some physical disks to be missing.

Hardware WMI Exceptions in RSM Log: The Network card (iLO management cards) Statusis now properly monitored and the error message "The Specified datatype is invalid" will nolonger be appearing in the RSM log file.

HP Insight Management Agent - Server - WBEM: The connector removes all temperaturethresholds of zero to avoid unwanted temperature alerts.

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

HP-UX System: On some cases, the value of the Error Percent parameter of the Network classwas not reported correctly.

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

IBM ServeRAID Disks Monitoring:

To prevent battery-controller association issues, a more reliable method has beenimplemented to associate batteries to their related disk controllers. Successful activation of thisconnector will automatically disable the previous monitoring method (SMI-S based).

11


Version 2.9.25

The status code returned by the IBM Director Agent for the controller’s battery wasoccasionally misinterpreted as degraded.

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

Sun SPARC servers running Solaris :

False alarms were triggered on LED instances.

Invalid values were reported or false alarms were triggered for temperature and voltagesensors.

Windows MPIO LUNs Monitoring: Because Windows regularly changes the unique identifiersof LUNs and physical disks, false missing/present alerts could occur for LUNs and duplicateinstances could appear. To solve this issue, the WMI - HBA connector now uses the LUN'snaa.ID, which is unique and does not change.

VMWare ESX: Individual memory sensors listed under "Other" sensors in the vCenter/vSphereconfiguration tab are now monitored by BMC Performance Manager Express for Hardware.

Windows - DiskPart: On Windows systems, the DiskPart connector was causing a thread/handle leak in the VDS.EXE process (Virtual Disk Service).

Supported Platforms/Requirements

13


Version 2.9.25

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

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

ServersTypical Platform Operating System Instrumentation

PrerequisitesTechnology Used

Cisco UCS B-Series, C-Series

Windows None IPMI, WMI


Linux ipmitool IPMI, command lines


ESX None WBEM

Dell PowerEdge Windows Dell OpenManage ServerAdministrator

SNMP

Dell PowerEdge Linux Dell OpenManage ServerAdministrator

SNMP

Dell PowerEdge ESX None WBEM

Fujitsu PRIMEPOWERServers (sun4us) -

Solaris None Command lines

Fujitsu-SiemensPRIMERGY

VMware Fujitsu Serverview WBEM agent WBEM


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

SNMP


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

SNMP


Linux Fujitsu-Siemens Serveview WBEMAgent

WBEM


Windows Fujitsu-Siemens Serveview WBEMAgent

WMI


ESX None WBEM

14


Version 2.9.25

Typical Platform Operating System InstrumentationPrerequisites

Technology Used

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

Command lines or WBEM

HP AlphaServer Tru64 HP Insight Management Agent SNMP

HP AlphaServer OpenVMS HP Insight Management Agent SNMP

HP Integrity Windows HP Insight Management Agent SNMP

HP Integrity Linux HP Insight Management Agent SNMP

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

Command lines or WBEM

HP NetServer Windows HP TopTools SNMP, WMI

HP ProLiant Windows HP Insight Management Agent SNMP or WMI

HP ProLiant Linux HP Insight Management Agent SNMP

HP ProLiant Solaris HP Insight Management Agent SNMP

HP ProLiant ESX HP Insight Management Agent WBEM

HP SuperDome (Itanium) Windows HP Insight Management Agent SNMP

HP SuperDome (Itanium) Linux HP Insight Management Agent SNMP

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

HP SuperDome (PA-RISC)

HP-UX GSP card Command lines

IBM pSeries, IBM eServer IBM AIX None Command lines

IBM VIO Server IBM AIX None SSH

IBM xSeries, IBMNetfinity

Windows IBM Director Agent WMI


ESX None WBEM


Linux IBM Director Agent WBEM, command lines

NEC Express5800 Windows NEC ESMPRO Agent SNMP

NEC Express5800 ESX None WBEM

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-Out Management (ALOM) card overthe network

Command lines, SSH tothe ALOM card

Sun Fire (SPARC) Solaris None Command lines

Sun Fire (X64) Solaris ipmitool, lsiutil Command lines

Sun Fire (X64) Linux ipmitool, lsiutil Command lines

15


Version 2.9.25

Typical Platform Operating System InstrumentationPrerequisites

Technology Used

Sun Fire (X64) Windows lsiutil IPMI (WMI), commandlines

Sun Fire F12K, F15K,F20K, F25K

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

SSH to the SystemController

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

SSH to the XSCF

Cross-Platform Technology

Technology OperatingSystem

Instrumentation Prerequisites Technology Used

Emulex HBA Windows None WMI

Emulex HBA Linux hbacmd Command lines

Emulex HBA Solaris hbacmd Command lines

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

Brocade SAN Switch SNMP Enabled SNMP

Cisco MDS, Nexus* None Telnet/SSH

16


Version 2.9.25

Typical Platform Instrumentation Prerequisites Technology Used

Dell EquaLogic PS Series None SNMP

Dell PowerVault TL2000 TapeLibraries

Dell OpenManager Server Administrator SNMP

Dell PowerVault TL4000 TapeLibraries

Dell OpenManager Server Administrator SNMP

Dell TL2000/4000 TapeLibraries

None SNMP

EMC CLARiiON EMC SMI-S Provider WBEM

EMC Isilon EMC Isilon SSH interface Command lines

EMC Symmetrix EMC SMI-S Provider WBEM

IBM v7000 Disk Arrays Storage Device Telnet/SSH

IBM TS3100 Tape Libraries None SNMP

IBM TS3200 Tape Libraries None SNMP

Fujitsu Eternus ETERNUS SMI-S Agent WBEM

Hitachi AMS/HUS Hitachi Device Manager WBEM

Hitachi USP-V Hitachi Device Manager WBEM

Hitachi VSP Hitachi Device Manager WBEM

HP StorageWorks P6000 HP CommandView EVA Command lines

HP StorageWorks XP / P9000Series

Hitachi Device Manager or HP P9000CommandView Advanced Edition

WBEM

IBM 3584 Tape Libraries 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 TapeLibraries

None SNMP

IBM XiV IBM XIV Storage System SMI-S Agent WBEM

McData SAN Switch None SNMP

NetApp None SNMP

Pure Storage FA Series None SSH

Quantum Tape Libraries None SNMP

StorageTek LSeries None SNMP

StorageTek StreamLine (SL) None SNMP

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

17


Version 2.9.25

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

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

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

http://www.sentrysoftware.com

Getting Started

19


Version 2.9.25

BMC Performance Manager Express for Hardware enables administrators to monitor the hardware ofall their diverse servers on BMC© Portal. This is a single performance manager (PM) that is able tomonitor the 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 singlecustomizable entry point for data from multiple sources and a single view that enables you tomonitor the health and performance 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 andthe RAID controllers, temperature of the system, speed of the fans, power supplies, networkinterfaces etc.

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

Installation Guide

21


Version 2.9.25

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 singleview that 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 wishand BMC Performance Manager Express for Hardware starts monitoring the hardware of all theconnected systems within your BMC© Portal environment: status of the disks and the RAIDcontrollers, temperature of the system, speed of the fans, etc.

Targeted Computers

BMC Performance Manager Express for Hardware (called BPM Express for Hardware for short) is tobe installed on the web-based BMC© Portal.

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.The RSM 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..

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

22Note on RSM


Version 2.9.25

Note on RSM

In general, an RSM is said to support the monitoring of 100,000 parameters. In the case of BPMExpress for Hardware, it is difficult to calculate a precise number of parameters collected since thisdepends entirely on the element itself and the number of hardware objects: disks, fans, memorymodules 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 thenumber of objects discovered on each element.

The number of RSMs required would also depend on whether an RSM is dedicated to BPM Expressfor Hardware alone, or whether there are other PMs on the same RSM. It should be safe to assumethat an RSM dedicated entirely to BPM Express for Hardware would be able to support approximately150 elements, 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-specificsystem management tools that collect hardware data and these tools are generally provided alongwith the server 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.Certain servers or systems could have more than one applicable “hardware agent”. You can refer tothe 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 of BPMExpress for Hardware. Additional information on the instrumentation agents for certain platforms maybe found in platform-specific guides on the Sentry Software Website.


23Installing BPM Express for Hardware


Version 2.9.25

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 andMonitoring Guide 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.25, the BPM Express for Hardware application classwill not overwrite or merge with its previous versions (2.3.xx), but will instead appear in the list inaddition to it, just like any other PM, and the previous version will continue to function. If you wish touse only Version 2.9.25 on all your elements, you need to completely uninstall and remove theprevious version (2.3.xx) before installing Version 2.9.25.

http://www.sentrysoftware.net

http://www.sentrysoftware.net



Version 2.9.25

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

system.

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

Logging on to Portal

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

Uploading Performance Managers

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



Version 2.9.25

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

BPM Express for Hardw are appears as Published

6. The “+” symbol next to BPM Express for Hardware indicates that there are several applicationclasses within the main PM (Performance Manager). Expand the tree to see the platform-specificapplication classes of BPM Express for Hardware: Hardware (OpenVMS); Hardware (Switch);Hardware (Windows); Hardware (Other); Hardware (HP-UX); Hardware (AIX); Hardware (Tru64);Hardware (Storage); Hardware (Solaris); Hardware (Linux).

The PM is built with separate platform-specific classes since the input properties required to activatethe class 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) amongstother classes - these two classes are meant for monitoring storage devices, but will not function unlessthe Storage Add-on for BPM Express for Hardware is installed. This is a separate product for monitoringstorage devices, and it is built as an add-on component for BPM Express for Hardware.

The installation of BPM Express for Hardware is now complete. If a previous version was alreadyinstalled, the PM is automatically upgraded.

To begin using the performance manager, log out and then log in again, this time, with usercredentials. You are now ready to begin using the PM.



Version 2.9.25

Adding BPM Express for Hardware to an ElementProfile1. Log on to BMC Portal with administrator credentials.

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



Version 2.9.25

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

Adding Application Classes

4. The Element Profile Properties – Add Application Classes page appears. ChooseHardware from the Select Category drop-down list.

Selecting the Storage Applicable Class



Version 2.9.25

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

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

Entering Properties and Credentials



Version 2.9.25

7. Click Next. You arrive at the final step for adding the BMC Performance Manager Express forHardware application class: Thresholds, Properties and Credentials.

8. Thresholds are automatically set by BMC Performance Manager Express for Hardware. It isrecommended to keep the default thresholds (or see the Modifying Parameter Thresholdssection). Click Finish.

Configuring Thresholds

9. Click Done to save the changes made. The Hardware application class is now added to all theelements in the selected Element Profile.



Version 2.9.25

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 login differentfrom 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] 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 Port Port number on which the SNMP Agent is running.

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

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



Version 2.9.25

Name Description

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

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.

Missing Device Detection By default, the missing device(s) will be detected and monitored. Setting the option toDisable 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 Status parameter if it is UNKNOWN.

Default system wattage Constant value (in Watts) to be used for the "Power Consumption" parameter and the"Energy Usage" report when the system is not able to report its actual energy usage.Use this setting if you know approximately the normal power consumption of thismanaged 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 differentCredentials / 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 configuredfor all commands that need root and the sudo utility would also need to be in the path of the PatrolUser. Select the option Use Sudo Utility.



Version 2.9.25

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 beselected. The sudo utility would need to be configured for all commands that need root and the sudoutility would also 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.9.25

Name Description

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

WBEM/SSSU CredentialsWBEM/SSSU UsernameWBEM/SSSU PasswordOrShared Credentials

Optional: Enter the WBEM or SSSU credentials if required for connection to theelement. 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.









Version 2.9.25

Sudo Configuration and Execution MethodsThe BMC Performance Manager Express for Hardware can be configured to use differentCredentials / 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 configuredfor all commands that need root and the sudo utility would also need to be in the path of the PatrolUser. 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.9.25

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

Input Properties Description

In case of Status parameter valueis UNKNOWN...




Sudo Configuration and Execution Methods

The BMC Performance Manager Express for Hardware can be configured to use differentCredentials / 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 configuredfor all commands that need root and the sudo utility would also need to be in the path of the PatrolUser. Select the option "Use Sudo Utility".

i.e.

login patrol

sudo command







Version 2.9.25

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

Name Description





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












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


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 differentCredentials / 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 user



Version 2.9.25

credentials), and the option Use Sudo Utility selected. The sudo utility would need to be configuredfor all commands that need root and the sudo utility would also need to be in the path of the PatrolUser. 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.9.25

Adding the Hardware Application Class to anExisting Element1. Log on to BMC Portal with administrator credentials.

2. In the Configure tab: Click the Element to which you wish to add the hardware solution andthe Element Properties page appears. Scroll down to Application Classes > Add.

Adding a Hardw are Application Class



Version 2.9.25

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

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

Hardw are Application Class Properties

5. The Properties and Credentials page appears asking for the information required formonitoring for Hardware (<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 youleave the default thresholds as they are. Click Finish. Details on how to modify thresholds aregiven in the User Guide.

7. The message: “Success! Changed have been saved” appears and Hardware (<platform>)appears in 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 forHardware.

Installing a PatchPatches for BMC Performance Manager Express for Hardware are available for download on the Sentry Software's Website. They can be applied by simply copying the hdf file(s) to the %RSM_HOME%\RSMxx\SEN_HW\hdf_2xxx\ directory on each RSM. No further actions arerequired. The new component monitoring will be added at the next discovery.

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

42Un-installing BPM Express for Hardware


Version 2.9.25

Un-installing BPM Express forHardwareThis chapter describes the procedure to remove or permanently delete BPM Express for Hardwarefrom your Portal environment. You cannot delete the hardware solution (or any other) if any of itsapplication classes 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 tobe monitored 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 andthe element 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.

43Un-installing BPM Express for Hardware


Version 2.9.25

Uninstalling BPM Express for Hardware from thePortalJust as for installation, to uninstall BPM Express for Hardware from the Portal environment, you needto use 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.To do 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

45Integrating with BMC ProactiveNetPerformance Management


Version 2.9.25

Integrating with BMC ProactiveNetPerformance ManagementOverview

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

Adapter for BMC Portal



Version 2.9.25

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

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:

Accessing the Administration tab in the Administration Console



Version 2.9.25

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

Importing Monitor Types and Adding Adapter



Version 2.9.25

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

Setting the connection parameters

In the Instance Name field, enter a name for this instance of the Adapter that will performthe integration 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 added toan existing element.

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



Version 2.9.25

4. Click Next to continue

Selecting the Application Classes to import



Version 2.9.25

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

6. Set the Filter details if needed.

Setting filter details



Version 2.9.25

7. Click Next to Continue.

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

Scheduling Auto-sync polls



Version 2.9.25

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

Adapter added to the Adapters 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 into BMCProactiveNet to enable the update of a single PM independently.

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



Version 2.9.25

Managing Baselines and Key PerformanceIndicatorsIn order to facilitate the detection of abnormalities on your monitored environment, BMCProactiveNet calculates baselines per parameter (metrics or attributes) based on values collectedover a specified period of time to determine a normal operating range. When the collected values forthese parameters are out of range, an alert is triggered.

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

Managing baselines

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

The baseline is calculated by collecting the values for a monitor’s attributes and metrics over aspecified time period and establishing a low baseline value (consisting of the 10th percentile of all thevalues for a given time period) and a high baseline value (consisting of the 90th percentile of all thevalues for a given time period), taking a weighted average of these values over time. A higher weightis given to the latest data being factored into the baseline average. The accuracy of the baselineimproves 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 BMCProactiveNet Administration Console. In this PM, some parameters or attributes have beendesignated as important indicators of performance (KPIs). We do not recommend that these defaultsettings are modified.

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



Version 2.9.25

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.The KPI Administration dialog box is displayed.

2. From the Monitor Type list, choose the monitor type for which you want to add or remove 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 PerformanceIndicators:

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

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

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

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

Baselining

KPI

Integrating the PM

56


Version 2.9.25

BPM 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 installationprocedure.


User Guide

58


Version 2.9.25

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 systemhardware (disk status, temperatures, CPU, power supplies etc). It gathers hardware information fromdifferent sources such as manufacturer-specific agents, standard management technologies, SNMP,WBEM, etc., and displays this information within the Portal environment.

In order to work properly, BPM Express for Hardware needs certain hardware information sources tobe available. Depending on the platform, it relies on the manufacturer-specific instrumentation layerand/or on standard management technology such as WBEM or SNMP. On startup, BPM Express forHardware automatically detects which hardware information source is available and then uses this topoll data on the hardware health of the computer. BPM Express for Hardware collects such data fromeach server and reports it in your Portal console.

In the example below, BPM Express for Hardware leverages the IBM Director and MIB-2 StandardSNMP Agents to monitor an IBM Server running on Windows. While the IBM Director Agent showsthe enclosure model, processors, memory modules, fans, power supplies, voltage sensors, temperature sensors, disk controllers, and physical and logical disks; the MIB-2 Standard SNMPAgent provides information about the network cards.



59How it Works


Version 2.9.25

Monitoring an IBM Server running W indow s

60How it Works


Version 2.9.25

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 toleverage both agent-less technologies and the PATROL agent to monitor the availability andperformance of your business infrastructure.

BPM Express for Hardware is a based on agent-less technology, is designed for the Portal anduses the 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 ofyour environment, you can implement one or many RSMs. To know what to monitor on thespecified infrastructure elements, the RSM uses PMs and therefore for hardware monitoring, itbanks on the BPM Express for Hardware.

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

61Understanding BPM Express for Hardwarewithin the Portal environment


Version 2.9.25

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

Understanding BPM Express for Hardw are w ithin the Portal environment

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 monitoringa heterogeneous infrastructure, as long as the vendor-specific hardware agents are installed on everymanaged element.

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 tofunction properly. In most cases, server vendors provide the required hardware monitoring agent fortheir server models.

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.

62The Need for Vendor-specific Hardware Agents


Version 2.9.25

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 tomonitor the Mylex RAID controller of the server.

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

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

View of objects discovered by BPM Express for Hardw are

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


63Monitoring with BPM Express for Hardware


Version 2.9.25

Batteries

Blades

Capacity

Disk controllers

Enclosure

Logical Disks

Fans

LED

LUN

Memory modules

Network interfaces

Physical Disks

Power supplies

Processors

Robotics

Tape drives

Temperature

Voltage

Other devices

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.

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_2920-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 instrumentationlayers, 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 discoveryprocess.

Collection

64Inside BPM Express for Hardware


Version 2.9.25

Finally, 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.This is 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 information sourcesCreates 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 hardware environmentPolling is carried out every 5 minutes.

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\SentrySoftware-HardwareSentry-solution-<version>.par-native.

You can force BPM Express for Hardware to perform or ignore the detection process on specific connector files (seethe Pre-selected Connectors, Disable Connectors, and Force Detection sections) .

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. Theremay be 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".



Version 2.9.25

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).Most of 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 ofeach detected “.hdf” file and creates the Disk Controller icons.

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

With a view to optimization, the discovery process is as parallelled as possible. All independent objects are

processed at the same time.

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

Based on the collection interval configured, the BPM Express for Hardware spawns severalparamlets that are responsible for 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 notto the corresponding classes and instances.

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

The ConnectorsEach connector is an “.hdf” file that is dedicated to one source of hardware information. Eachconnector file describes how BPM Express for Hardware connects to the available hardwareinformation source and what information is available through this source. For example,SEN_HW_EMCDiskArray.hdf describes how to get information from the EMC Disk Arrays and thenmonitor the array.

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.



Version 2.9.25

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

Monitoring

Monitoring the hardware components with the BPM Express for Hardware is very simple. Onceinstalled, as per the instructions given in the Installation Guide chapter, BPM Express for Hardwareautomatically detects all the various hardware components and displays them in the web-basedinterface.

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 hardwarecomponents within your BMC© Performance Manager Portal environment.

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

The discovered hardware components of the monitoring element are grouped under certain containericons. Here is a the structure of how the monitored elements are displayed in the Portal interface:


67Monitoring


Version 2.9.25

Hardw are Components Structure

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

EnvironmentBattery

Fans - FAN

Power Supply - PS

Temperature - TEMP

Voltage - VOLT

68Monitoring


Version 2.9.25

� DisksDisk Controller - CTRL

LUN

Logical disk - LD

Physical disk - HD

Tape Drive

� DevicesBlade - BL

Enclosure

Fiber Channel - FC

LED

Memory Module - MEM

Network Interface - NET

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

Processors - CPU

Robotics

System Chassis

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,as well 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.

69Monitoring


Version 2.9.25

Monitoring the enclosure

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

The Locator parameter to physically locate a component.

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

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

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. Itis the 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.For each monitored element, graphs & text reports are built by polling the parameter instances everyfive minutes. To view these graphs or text reports from the Status tab:

70Monitoring


Version 2.9.25

Monitoring the Environment: fans, temperatures and voltages

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 Table view (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,that triggers 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 are

71Monitoring


Version 2.9.25

breached: 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 havebeen breached, the Status parameter will report for example: “WARNING! The fan speed is toolow” or, “ALARM! This fan has stopped working” etc. The history graph shows the exact details ofthe 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 Locator parameter helps to physically locate a component.

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

The Speed Percent parameter represents the speed of the corresponding fan in percentage ofits maximal 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 recommendedactions. The alert conditions for Status are: “!”=WARNING; “!!”=ALARM . Example: “OK”, or,“ALARM!! This fan is 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 notworking properly or when the ambient temperature is too hot. Monitoring the temperatures of criticaldevices of your system allows you to take action before a crash occurs.

Depending on the available information, the Temperature and/or Status parameters will bedisplayed for 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 ifthe temperature rises to high, or i.e. if any of the other parameters breach their respectivethresholds. 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!!. The temperature iscritically high”.

72Monitoring


Version 2.9.25

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. TheStatus parameter 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 tofail or “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 ofthe computer. 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 helpin detecting unstable system instability.

Depending on the available information, the Voltage and/or Status parameters are displayed foreach voltage 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 thevoltage output is too low for proper functioning or if it goes out of the proper range. It is only Status that will trigger and display the alerts. When all is fine, Status shows “OK”, and whenthere is 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 voltage sensor is no longer detected".

73Monitoring


Version 2.9.25

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. Inthe left pane, click on an Element > Hardware (<platform>) > Device Type > Disks and seethe discovered components in detail in the right pane. An icon is created for each storage-relateddevice discovered: physical disks, logical disks and disk controllers. Each icon is labeled with adescription of the device: ID, size, vendor, role, etc. By clicking on the disk in the left pane, you cansee its details in the right pane.

Monitoring disks: disk controller, physical 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 "Attached 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 alertswhen any of the other parameters for the device breach their thresholds. Alert conditions for Statusdescribe in symbolic terms what occurs in the parameter when thresholds are breached: one

74Monitoring


Version 2.9.25

exclamation mark triggers a warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds have been breached,the Status parameter will report, for example: “WARNING! This disk is about to fail” or, “ALARM!!This logical disk is no longer detected” or as may be the case. The history graph shows the exactdetails of the 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 following parameters will be displayed for eachdiscovered physical disk:

The Predicted Failure parameter uses the S.M.A.R.T. technology to predict physical diskfailures. An alert will be triggered by the Status parameter if it is predicted that the PhysicalDisk will soon break 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 isnot 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 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 nolonger detected."

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 Status parameterwill automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal to report pureevent-driven alerts with no need for manual acknowledgment from the operators.

75Monitoring


Version 2.9.25

Logical DisksRAID or advanced disk controllers expose several physical disks as a single logical disk to theoperating system. 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 sincethe last counter reset. The error count is automatically reset every 24th hour (by default; thissetting is configurable).

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 whenthere is 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."


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

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 Status parameterwill automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal to report pureevent-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 disksas a single logical disk which is the only disk exposed to the operating system. Monitoring bothphysical and logical disks is essential to ensure that storage is available.

Depending on the system and the information available, the Battery Status, the ControllerStatus and the Locator parameters 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.

All systems may not be able to provide this information.

76Monitoring


Version 2.9.25

Monitoring Devices: Processors, Memory Modulesand 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 > Devicesand see the discovered components in detail in the right panel. An icon is created for each detecteddevice. 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 bemissing, the Status parameter will trigger an alert if necessary.

Monitoring devices: CPUs, memory modules, netw ork interfaces and other devices

Status is a text parameter that describes the overall status of the corresponding device or sensor. It

77Monitoring


Version 2.9.25

is the Status parameter that raises alerts when any of the other parameters for the device breachtheir thresholds. Alert conditions for Status describe in symbolic terms what occurs in the parameterwhen thresholds are breached: one exclamation mark triggers a warning; two exclamation marksraise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the device havebeen breached, the status parameter will report for example: “WARNING! This network adapterhas degraded” or, “ALARM! This network adapter is not detected anymore” or as may be the case.The history graph shows the exact details of the problem, its consequences and recommendedactions.

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 from theoperators.

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 amonitoring tool 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 rebootis either 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 operatingsystem starts 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 BPMExpress for Hardware and reported in the Portal interface.

Depending on the information available, the following parameters will be displayed for eachdiscovered processor (CPU):

78Monitoring


Version 2.9.25

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 POSTerror, 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 failurein the near future.

The Current Speed parameter displays the current clock speed of the processor in megahertz.


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 reportstatistics on 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 thememory modules, the Error Count and/or Predicted Failure and/or Status parameters will bedisplayed for each discovered memory module:

The Error Count parameter reports the number of errors that have been detected by thememory module and then corrected. A steadily growing value means that the memory module isnot reliable and that it could encounter errors that it is unable to correct and that will then crashthe 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 theECC technology). If this parameter goes into alarm, you should remove the faulty memorymodule and replace it with a new one.

The Status parameter represents the overall status of the memory module. An alert is triggeredif the 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 alocal area network (LAN), or as an interface to allow networked computers to connect to an outsidenetwork. It is therefore essential to make sure these devices are properly running and linked to thenetwork. For each network interface discovered, the Status, Error Percent and/or Link Statusparameters are displayed:

The Status parameter represents the overall status of the network interface. An alert istriggered when the network interface is not responding, or any of the other parameters’thresholds are breached.

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).By default, the Link Status parameter raises an alert (through Status) only for previouslyconnected network 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.

79Monitoring


Version 2.9.25

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

This mechanism is especially useful when, for example, a non-redundant physical disk does notrestart during a system reboot and therefore is no longer seen by the operating system and themonitoring software. When a device is no longer discovered, its Status parameter goes into alarmand its label directly shows that it is missing.

Monitoring ConnectorsWhen a BPM Express for Hardware connector has been detected as applicable to the currentplatform, a corresponding instance is created under Infrastructure > Element > Hardware(<platform>) > Detected Connectors and its status is monitored regularly to ensure that theunderlying technology is still 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 ServerAdministrator connector.

Based on the collection interval configured, its Status parameter is updated.

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

80Monitoring


Version 2.9.25

Monitoring connectors

This connector monitoring mechanism helps administrators detect hardware agent failures. Itprovides a higher monitoring accuracy by not confusing errors encountered by devices with errorscaused due to failure of the monitoring tool. The parameters for the connector monitoring class are:

Test Report: This parameter describes the tests run to evaluate the availability of thetechnologies used 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.

81Monitoring


Version 2.9.25

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 receivedand transmitted bytes for the selected port. It can easily be customized to show the data thatadministrators can 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 transmittedon the 22nd. Whereas on the 23rd, 1.65 GB were received and 41 GB were transmitted.

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

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

82Reporting


Version 2.9.25

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 wattsof Power on the 22nd.

So calculating for a period of one week:

Energy used: 27 to 28 kWh

Power Consumed: 1225 watts

83Reporting


Version 2.9.25

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 fromsystem to 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.

When default thresholds are modified, the alerts are displayed by the icon of the parameter whose thresholds havebeen modified. See Modifying 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 parametericon in the History icon with all the details. However, only the Status icon will go into Warning.Similarly, if the Error Percent parameter thresholds breach alarm levels, it is the Status icon thatwill trigger and display 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 translatesthe regex of one exclamation mark "!" into a warning, and two exclamation marks into an alarm. Bydefault, the alerts are triggered on the Status parameter. You can see these threshold symbols for

84Thresholds


Version 2.9.25

any monitored element in the Configure tab, under Thresholds.

Nevertheless, it is possible to modify these pre-set thresholds via the Configure tab in the Portal.You must however remember that you have to disable the thresholds for the Status parameter(which will otherwise continue to consider pre-set thresholds), and instead directly assign customthreshold values on 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,a combination of different parameters was created. This may result in the display of severaloccurrences of the same application class. For example, the Application class: Physical Disk has 3parameters:

Status

Predicted Failure

Error Count

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

Status

Predicted Failure

Error Count

Status, Predicted Failure

Status, Error Count

Error Count, Predicted Failure

Status, Error Count, Predicted Failure

Consequently, we strongly recommend that you wait for all the hardware components to bediscovered before setting threshold values for a hardware instance to avoid having to enterthresholds for each occurrence of the application class.

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 aptfor the 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.

85Thresholds


Version 2.9.25

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

86Thresholds


Version 2.9.25

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.

Modifying threshold values

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 reportit to customer support, you will be asked to enable the Debug Mode and provide the debug output tothe support team.

87Troubleshooting


Version 2.9.25

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 RSMwill affect 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 whichmeans that at least one collect has been performed. As long as this parameter is not set to true, itmeans that BPM Express for Hardware has not finished (successfully or not) its collection for thisserver. You need to wait until Application Collection Status is set to true before investigatingfurther.

This parameter is created by default by the Portal for every application class that is added. Hencewhen you 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 forHardware on the RSM was able to communicate with the targeted server with the credentialsprovided by the user. If so, the Machine Status parameter is set to “<hostname> is alive. Detectedas a <OS> system”. Otherwise, this parameter will report that BPM Express for Hardware cannotcommunicate with this host. This can be due to several reasons:

88Troubleshooting


Version 2.9.25

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

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. Thefollowing reasons 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 SNMPtechnology (DELL OpenManage, HP Insight Management, and Fujitsu-Siemens ServerView forexample). Since BPM Express for Hardware gathers hardware information from these agents, youneed to enable and properly configure the SNMP layer on the managed servers if an SNMP-basedagent 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 forHardware – simply because it cannot communicate with the managed element. So enabling andauthorizing the managed server to communicate through the SNMP protocol is essential.

Configuring SNMP on Windows servers 2003, 2008,2012Starting with Windows Server 2003, the SNMP service is not configured to allow the "public"community by default. As a consequence, even if the SNMP service is properly installed and thehardware agent properly running, BPM Express for Hardware is not able to gather any hardwareinformation from the SNMP agent. Therefore, on Windows Server computers that run an SNMP-basedhardware agent (DELL OpenManage, HP Insight Management or Fujitsu-Siemens ServerView), youfirst need to install the SNMP service (not installed by default) and then configure it to allow acommunity to access the SNMP agent.

89Troubleshooting


Version 2.9.25

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

Troubleshooting: SNMP Service - Properties

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

Troubleshooting: SNMP Service 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 >Configure tab > 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 Windows or Linux, BPM Express for Hardware will still be able to monitornetwork cards and internal non-RAID disks.

90Troubleshooting


Version 2.9.25

Reinitializing Certain ParametersDue to the inner mechanism of servers, and that of BPM Express for Hardware, certain parametershave a 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 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 ErrorCount to be re-initialized every 24hrs by default. This time-frame is customizable. Basically, here’swhat happens:

When BPM Express for Hardware detects the parameter Error Count for the first time, it notesthe number 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 lastrecorded Error Count/Corrected Error Count as the new “base-count or threshold” for thefresh round after reset. This is the inner mechanism, the display shows that on reset the count iszero, and if it increases 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 itmeets an Error Count of any value greater than 40, the Status parameter of that instancewill trigger an 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 forError Count will be 48, and so on and so forth.

91Troubleshooting


Version 2.9.25

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

Logical Disk

Memory

Network

Physical Disk

Robotics

Tape Drives

Corrected Error Count applies to:

CPU

Reinitializing the PMTo reinitialize the PM, you can:

either restart the RSM. All the elements monitored by the RSM will then be automaticallyreinitialized

or manually delete the file sen_hw_database_<hostname>_*.dat that corresponds to theelement you wish to renitialize. This file is stored in %RSM_HOME%\RSMxx\server\rsm\tmp\deploy.

Troubleshooting Connectivity IssuesBMC Performance Manager Express for Hardware leverages specific instrumentation agents orsystem management tools to collect hardware information. Because some connectivity issues mayexist and cause BMC Performance Manager Express for Hardware to fail, it is highly recommended totest the connection to the specific agent before contacting the Sentry Support Team.

To troubleshoot connectivity issues:

1. Download the connection tool required from the Sentry Software Web site. Please note that theconnection tool requires Java v1.6 or higher.

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

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

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

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

4. Wait for the test to complete. If a connectivity issue is detected, an error message will appear. Inthis case, the issue encountered does not concern BMC Performance Manager Express forHardware. Check your configuration to diagnose the source of the issue.

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

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

92Troubleshooting


Version 2.9.25

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 mustbe used with your disk controller.

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

1. A firewall blocks the WMI 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,so enabling the DCPM across the firewall should allow it to work. When WMI connects to a remotemachine it uses port 135 for the initial negotiation, and then a random port is allocated for furtherconnection. Stated below are two links that will help in setting a range of ports for the RPC/DCOMconnection. Once you have set a range for RPC/DCOM communication, you can then configure thefirewall to allow traffic through 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 since 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 theGuest account 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

94


Version 2.9.25

This chapter provides the following detailed chapters:

Classes and Parameters: Parameters, info boxes and menu commands for each applicationclass

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 ManagerExpress for Hardware on the Portal. It gives a detailed view of each application class describing itsfunction and parameters.

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 processare respectively 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 The charge level of the cache card battery as a percentage. Percentage(%)

Warning ≤ 50%Alarm ≤ 30 %

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

Status Status of the battery. Values:OK;Warning;Alarm

Warning = “!”Alarm = “!!”

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

95Application Classes


Version 2.9.25

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 Status of the blade. Values:OK;Warning;Alarm


Power State Indicates whether the blade is currently on or off Values:Off; On

None

"Status" is a text parameter that gives the overall status of the corresponding device 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.



Version 2.9.25

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

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

Total PhysicalDisk Size

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

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 connectorwill no longer be monitored. Check the Test Report parameter to have more details about theconnector failure.

Parameters


Status Status of the connector. Values:OK;Warning;Alarm


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

n/a n/a

"Status" is a text parameter that gives the overall status of the corresponding device or sensor. An alert conditiondescribes in symbolic terms what occurs in the Status 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 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.




Version 2.9.25

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 Hardwarebecause the processor is "missing".

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 Alarm if the "Corrected Error Count" parameter is greater than zero (that is: thedisk 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 BPM Express forHardware/Portal report pure event-driven alerts with no need for manual acknowledgment from the operators.

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 Status of the overall CPU. Values:OK;Warning;Alarm



"Status" is a text parameter that describes the overall status of the corresponding device or sensor. Alert conditionsdescribe in symbolic terms what occurs in the "Status" 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 breachedfor a CPU, the Status parameter will report “Warning! Problem: This processor is degraded orabout to fail." Or “Alarm!! This processor is not detected anymore", or as may be the case. On



Version 2.9.25

clicking the history graph, you can see the exact details of the problem, its consequences and therecommended actions.


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

Parameters



Status Status of the CPU Core. 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(%)

Warning ≥ 50% Alarm ≥ 100 %

Disk ControllerThe purpose of the Disk Controller instance is to display the status of the disk controller batteryand the status of the disk controller. In addition, some information regarding the disk controllers, likeits brand, 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

Status of the disk controller. Values: OK;Warning;Alarm




Version 2.9.25




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

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 opened.Example: "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 text parameter that describes the overall status of the corresponding device or sensor.


FanThis class creates monitoring objects for each cooling sensor it discovers. Depending on the systemand the data available, one or more parameters will be associated to the fan monitoring. Criticaldevices like processors, power supplies etc, have fans to avoid over-heating. Monitoring fans isimportant because they ensure a proper temperature for the system to work efficiently.



Version 2.9.25

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

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 ofits maximal speed.

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

Parameters



Speed Speed of the fan. Rotation PerMinute(RPM)

n/a

Speed

Percent

Speed of the fan as a percentage of its maximal speed. Percent(%) ofmaximal speed

n/a

Status Status of the fan.Example: “OK” or “Alarm!! This fan is not detected anymore”




"Status" is a text parameter that describes the overall status of the corresponding device or sensor. Alert conditionsdescribe in symbolic terms what occurs in the parameter when thresholds are breached: one exclamation mark triggersa warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that a fan has breached manufacturer-specified thresholds,the Status parameter will report “Warning! This fan is degraded/is about to fail” or “Alarm!! Thisfan is not detected anymore", as may be the case. The history graph shows the exact details of theproblem, its consequences and recommended actions.




Version 2.9.25

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 ofphysical disks, configured as an array (RAID 0, 1, 5, etc.) and exposed to the operating system as asingle physical 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 sincethe last counter reset. The error count is automatically reset every 24th hour (by default; thissetting is configurable).

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. Ittriggers an alert if the logical disk missing or if any of the other parameters have breached theirthresholds. It is only Status that will trigger and display the alerts. When all is fine, Status shows“OK”, and when there is a problem, it shows “Warning!” or “Alarm!!” with a detailed descriptionof 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-RAID disk controllers (as most of IDE controllers, for example), no logical disk will be displayed.

The "Status" parameter will report 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 "Status"parameter will be automatically cleared after 24 hours. This mechanism has been implemented to let the system reportpure event-driven alerts with no need for manual acknowledgment from the operators.

Parameters


Error Count Displays the number of errors encountered by the logical disksince the last counter reset (every 24hrs by default).

Errors n/a



Version 2.9.25



Status Displays the overall status of the logical disk.Example: “OK” or “Alarm!! This logical disk is no longerdetected”.





Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the logical diskhave been breached, the Status parameter will report “Warning! This logical disk is degraded/isabout to fail” or “Alarm!! This logical disk is not detected anymore", or as may be the case. Thehistory graph shows 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 Warning = When downgrades orfewer than expectedAlarm = 0


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



Version 2.9.25

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 theRSM is able to communicate with the targeted remote element. It detects whether or not the remoteelement is accessible for monitoring i.e. whether or not the remote element is up & running and canbe 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 toany of 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 thefirewall is 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.9.25

“<hostname> is alive. Problem: Host platform cannot be detected.”

On clicking on the History icon, you can see the details about the problem, its consequencesand the recommended actions.

The warning "Machine Status" triggers in case of a problem, is not related to any hardware issue; all itindicates is that the BPM Express for Hardware cannot perform the detection, discovery or collectionprocesses on this remote element.

If one or several connectors are not detected as valid for the targeted server, you need to enable the debug mode ofBPM 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 handlefailed memory modules or, most often, for modules that have been disabled by the BIOS uponreboot (the module is then flagged as "missing").

The Error Count parameter represents the number of errors that have been fixed by ECC-enabled memory 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 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 Status parameterwill automatically be cleared after 24 hours. This mechanism enables BPM Express for Hardware/Portal to report pureevent-driven alerts with no need for manual acknowledgment from the operators.

Parameters


Error Count

Displays the number of errors encountered since last counterreset (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 Status of the memory. Values: n/a



Version 2.9.25


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 memorymodule have been breached, the Status parameter will report “Warning! This memory moduleencountered an abnormal number of internal errors” or “Alarm!! An imminent failure is predictedon this memory module”, or as may be the case. The history graph shows the exact details of theproblem, its consequences 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 apure 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 previouslyconnected network 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 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 Statusparameter.

Parameters


Bandwidth

Utilization

Percentage used of the available bandwidth. Percentage(%)

n/a

Connected toPhysicalAddress

Port number to which the network card is connected. Portnumber

n/a



Version 2.9.25


ConnectionType

Type of the network connection. ethernet/FC

n/a

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 received packetsin error between collects.

Percentage(%)

Warning ≥ 10Alarm ≥ 30

Link Speed

Negotiated or configured link speed. Megabits/seconds(MB/Bits)

Warning ≥ 10Alarm ≥ 100

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 Status of the network interface.Example: “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 Baselining and KPI, see Managing Baselines and Key Performance Indicators.

"Status" is a text parameter that describes the overall status of the corresponding device or sensor. Alert conditionsdescribe in symbolic terms what occurs in the parameter when thresholds are breached: one exclamation mark triggersa warning; two exclamation marks raise an alarm.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the network



Version 2.9.25

interface have been breached, the Status parameter will report “Warning! This network adapterhas degraded”,or, “Alarm!! This network adapter is not detected anymore” or as may be the case.The history graph shows the exact details of the problem, its consequences and recommendedactions.


Other DeviceThis class is typically used to monitor devices that do not relate to the other classes and can rarelybe monitored on servers. The device definition is given by the connector file and the device ismonitored just 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 Status of the "other device".Example: “OK” or “Alarm!! This device is no longer detected”.


Warning = “!”Alarm = “


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 theexact details of the problem, its consequences and recommended actions.




Version 2.9.25

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 performancedegradation. When available, S.M.A.R.T technology will be used to predict a disk failure before itoccurs. Depending on the available information, the Predicted Failure and/or Status parameterswill be displayed for each 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 physicaldisk is 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 theirthresholds.

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 isonly 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 theissue, its consequences and recommended actions. The alert conditions for Status are:“!”=Warning; “!!”=Alarm

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 "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 Status of the physical disk.Example: “OK” or “Alarm!! This disk is not detectedanymore”.






Version 2.9.25


Example

If BPM Express for Hardware detects that manufacturer-specified thresholds for the physical diskhave been breached, the Status parameter will report “Warning! This physical disk is degraded/isabout to fail” or “Alarm! This disk is not detected anymore", or as the case may be. The historygraph shows the 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, orin some 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 ifan error occurs with the power supply.

Parameters



Status Status of the power supply.Example: “OK” or “Alarm!! The power consumed by thesystem is out of the supported range".



Used

Capacity

Displays the percentage of the power supply currently in use. Percentage(%)

n/a




Version 2.9.25


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 theproblem, 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 Status of the device. Values: OK;Warning;Alarm





Version 2.9.25

Tape DriveThe Tape Drive application class can be a child of the Enclosure and Disk Controller applicationclasses.

Parameters


Error Count

Displays the number of errors encountered. Errors n/a


Mount Count Number of mount operations that happened during the lastcollect interval. The parameter remains to zero when nomount operation occurs.

Mounts n/a

Needs

Cleaning

No / Yes Values:No;Yes

n/a

Status Status of the tape drive. Values: OK;Warning;Alarm


UnmountCount

Number of unmount operations that happened during thelast collect interval. The parameter remains to zero when nounmount operation occurs.

Unmounts

n/a


TemperatureBPM Express for Hardware detects the temperature probes on the motherboard or devices andcreates an instance of this class for each of them. Their location in the platform is described in theinstance’s label 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 Status of the temperature sensor.Example: “OK” or “Alarm!! The temperature is critically high”.





Version 2.9.25


Temperature

Displays the temperature reading. Celsiusdegrees(C°)

n/a


"Status" is a text parameter which describes the overall status of the corresponding device or sensor. An alertcondition describes in symbolic terms what occurs when thresholds are breached.

Example

If BPM Express for Hardware detects that manufacturer-specified thresholds have been breachedfor temperature, 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 completehardware health report for this temperature sensor. The actual temperature value (when available)is reported by the Temperature parameter but alert thresholds are not directly set on thisparameter. The history graph will display details about the problem, its consequences and therecommended 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 setthresholds. Otherwise, the Status parameter will inform you if a problem occurs with one of thevoltages.

Parameters



Status Status of the voltage sensor.Example: “OK” or “Alarm!! This voltage sensor is no longerdetected".



Voltage Displays the voltage reading. megavolt (mV)

n/a




Version 2.9.25


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 isout of the normal range." or “Alarm!! This voltage sensor is no longer detected", or as may be thecase. The history graph shows the exact details of the problem, its consequences andrecommended actions.


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 classon the 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 alertconditions. BPM Express for Hardware assigns the pre-set thresholds to its symbolic conditions ofexclamation marks.

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;and for an alarm-level breach, the Status parameter is set to “Alarm!!” with two exclamation marks,which triggers an Alarm alert in the Portal. When a problem occurs, it is the Status parameter thatreports “WARNING!” or “ALARM!!” followed by a full description of the encountered problem, thepossible consequences and the recommended action. Nevertheless, it is possible to modify these pre-set thresholds via the Configure tab.

115Thresholds


Version 2.9.25

If you wish to modify pre-set thresholds of individual parameters, you must deactivate the thresholdsfor the Status parameter (which will otherwise continue to consider pre-set thresholds and trigger alertsaccordingly), and instead, directly assign threshold values against individual parameters 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.

SSH Timeout

This property allows you to override the default timeout value or the default connector specifiedtimeout value 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

116Additional Configuration Properties


Version 2.9.25

Telnet timeout

This property allows you to override the default timeout value or the default connector specifiedtimeout value 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

UCS timeout

This property allows you to override the default timeout value for executing a request to a Cisco UCSBlade Chassis. The default value is 60 seconds.

Property: net.sentrysoftware.bpm.hardware.ucsTimeout.default=60000

WMI timeout

This property allows you to override the default timeout value for executing a single WMI query. Thedefault value is 45 seconds.

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.The default 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 exclude namespace

This property allows you to specify a list of namespaces that are to be excluded while executing theWMI query.



Version 2.9.25

Property:net.sentrysoftware.bpm.hardware.wmiExcludeNamespaceList=namespace1,namespace2,namespace3,...

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

WBEM namespace

This property allows you to specify a list of namespaces that are to be excluded while executing theWBEM query. .

Property: net.sentrysoftware.bpm.hardware.wbemExcludeNamespaceList=namespace1,namespace2,namespace3,...

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

Property: net.sentrysoftware.bpm.hardware.forceWMIScript=true

Force nAwk

By default BPM Express for Hardware uses the java native awk method to parse the result. Settingthis 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 Activation

This property forces the activation of the SNMP protocol.

Property: net.sentrysoftware.bpm.hardware.snmpActivation=true

Reflect Fan Speed value

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

By default in the class Power Supply, BPM Express for Hardware sets the parameter “Status” inalert if the parameter “UsedCapacity” 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.powersupply.usedcapacity=false

Reflect Voltage value

By default in the class Voltage, BPM Express for Hardware sets the parameter “Status” in alert ifthe parameter “Voltage” exceeds the threshold value. Setting this property value to “false” will forceBPM Express for Hardware not to reflect the threshold values on parameter “Status”.

Property: net.sentrysoftware.bpm.hardware.volt.voltage=false

Reflect Temperature value

By default in the class Temperature, BPM Express for Hardware sets the parameter “Status” inalert if the 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”.



Version 2.9.25

Property: net.sentrysoftware.bpm.hardware.temp.temperature=false

Reflect Available Path Count value

By 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"will force BPM Express for Hardware not to reflect the threshold values on parameter "Status".

Property: net.sentrysoftware.bpm.hardware.lun.availablePathCount=false

SNMP Port

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

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 specifiedconnector files for a specified element.

Property:net.sentrysoftware.bpm.hardware.preSelectedConnectors.hostname=connector1.hdf,connector2.hdf,connector3.hdf



Version 2.9.25

Perform Garbage Collect

By 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 forHardware. 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.

Property:net.sentrysoftware.bpm.hardware.disabledConnectors=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.

Example

To set the value for all hosts:net.sentrysoftware.bpm.hardware.disabledConnectors=connector1.hdf,connector2.hdf,connector3.hdf

To set the value for a specific host: net.sentrysoftware.bpm.hardware.disabledConnectors.<hostname>=connector1.hdf,connector2.hdf,connector3.hdf

Force detection

By default, the detection process is performed if any one of the protocols (SNMP, WMI, SSH, Telnet,WBEM) is detected. This property can however be set to "true" to force BPM Express for Hardwarewhatever the protocols detected on the element.

Property: net.sentrysoftware.bpm.hardware.forceDetection=true

IPMI TimeoutThis property allows you to override the default timeout value for executing a single IPMI command.The default value is 360 seconds.

Property: net.sentrysoftware.bpm.hardware.ipmiTimeout.default=360000

121Connectors


Version 2.9.25

Connectors

This section provides detailed information on each connectors - stating the target, typical platforms,the pre-requisites for BPM Express for Hardware to function optimally, technology used, and what itwill discover (stating precise application class names) and then, most importantly, what it willmonitor.

In order to know all about the connectors for your systems, first identify your platforms/environments in the 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 PerformanceManager Express for Hardware. Each connector is a file with the .hdf extension and they are storedin: %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

122Connectors


Version 2.9.25


Operating System

Dell EqualLogic PS Series MS_HW_Equallogic.hdf Dell EqualLogic PSSeries Disk Systems

Storage Device

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

EMC Isilon MS_HW_EMCIsilon.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

Hitachi HDS USP/VSPStorage Systems

MS_HW_HitachiVSPSNMP.hdf Storage Systems SNMP

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

123Connectors


Version 2.9.25


Operating System

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

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

124Connectors


Version 2.9.25


Operating System

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

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 AIX - usysfault MS_HW_IBMAIXusysfault.hdf IBM AIX servers 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

125Connectors


Version 2.9.25


Operating System

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

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 Hardware ManagementConsole (HMC)

MS_HW_IBMHMC.hdf IBM AIX servers IBM AIX

IBM Netfinity Manager 5.20.x- Basic

MS_HW_IbmNetfinityManagerBASIC.hdf

IBM Netfinity Microsoft Windows

IBM Netfinity Manager 5.20.x- Disks

MS_HW_IbmNetfinityManagerRAID.hdf

IBM Netfinity Microsoft Windows

IBM Netfinity Manager 5.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 Storwize Disk Arrays -SSH

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

126Connectors


Version 2.9.25


Operating System

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


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

Linux

MIB-2 Standard SNMP Agent- Network Interfaces -Solaris

MS_HW_MIB2Solaris.hdf Any SNMP-instrumented device

Sun Solaris, Sun Solaris

MIB-2 Standard SNMP Agent- Network Interfaces -Windows

MS_HW_MIB2NT.hdf Any SNMP-instrumented device

Microsoft Windows

MIB-2 Standard SNMP Agent- Network Interfaces

MS_HW_MIB2.hdf Any SNMP-instrumented device

Network, HP-UX, StorageDevice, HP OpenVMS, HPTru64

Motherboard Monitor MS_HW_MBMNT.hdf No-name PC Microsoft Windows

127Connectors


Version 2.9.25


Operating System

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


Pure Storage FA Series(SSH)

MS_HW_PureStorage.hdf Disk Array Storage Device

QLogic HBAs - ESX MS_HW_QlogicHBA.hdf Servers with QLogicHBAs

Linux

Quantum (ADIC) based TapeLibraries

MS_HW_QuantumTapeLibrary.hdf Quantum (ADIC)Tape Library

Storage Device

Quantum (ADIC) EnterpriseLevel Tape Libraries

MS_HW_QuantumTapeLibraryi6000.hdf

Quantum (ADIC)Tape Library i2000i6000

Storage Device

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

128Connectors


Version 2.9.25


Operating System

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

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

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.hdfMS_HW_VMwareESX5iLUNesxcli.hdfMS_HW_VMwareESX5iLUNSSH.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

129Connectors


Version 2.9.25


Operating System

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

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

130Connectors


Version 2.9.25

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 thearcconf utility.

Target

Typical platform(s): Sun Fire (x64)

Operating system(s): Sun Solaris, Linux

Instrumentation layer: arcconf

Technology used: System commands

Discovered objects





SEN_HW_DISKCONTROLLER / Controller Status

SEN_HW_DISKCONTROLLER / Battery Status



This connector is able to monitor the local host and/or a remote system.

131Connectors


Version 2.9.25

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-agentwhich supports all DPT-based Adaptec RAID controllers.

Target



Instrumentation layer: Adaptec Storage Manager


Discovered objects









Adaptec Storage Manager Web Edition (AAC)This connector provides disk monitoring through the Adaptec Storage Manager Web Edition SNMPsub-agent which supports all AAC-based Adaptec RAID controllers.

Target


132Connectors


Version 2.9.25

Operating system: Microsoft Windows, Linux

Instrumentation layer: Adaptec Storage Manager Web Edition


Discovered objects









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)


133Connectors


Version 2.9.25

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 / Link Status

SEN_HW_NETWORK / Link Speed

SEN_HW_NETWORK / Error Count

SEN_HW_NETWORK / Transmitted Packets Rate

SEN_HW_NETWORK / Received Packets Rate

SEN_HW_NETWORK / Transmitted Bytes Rate

SEN_HW_NETWORK / Received Bytes Rate

SEN_HW_NETWORK / Zero Buffer Credit Percent


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

134Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status




SEN_HW_BLADE / Status









SEN_HW_NETWORK / Duplex Mode

SEN_HW_ENCLOSURE / Power Consumption

This connector targets remote devices 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

135Connectors


Version 2.9.25

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



DataDirect Networks (DDN) Disk Array - SNMPAgentThis connector discovers the enclosure and the disks of DDN (DataDirect Networks) disk arrays aswell as the various environment sensors (temperatures, fans, power supplies). It relies on the SNMPprotocol

Target

Typical platform(s): DDN Disk Array

136Connectors


Version 2.9.25


Instrumentation layer: DDN SNMP Agent


Discovered objects


Fans (SEN_HW_FAN)





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


137Connectors


Version 2.9.25

Discovered objects



Fans (SEN_HW_FAN)





SEN_HW_LOGICALDISK / Unallocated Space


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)


138Connectors


Version 2.9.25

Discovered objects




Fans (SEN_HW_FAN)






Batteries (SEN_HW_BATTERY)



SEN_HW_DISKCONTROLLER / Status Information






SEN_HW_FAN / Speed

SEN_HW_FAN / Status

SEN_HW_FAN / Status Information



SEN_HW_TEMPERATURE / Status Information


SEN_HW_POWERSUPPLY / Status Information


SEN_HW_BLADE / Status Information


SEN_HW_OTHERDEVICE / Status Information


SEN_HW_ENCLOSURE / Status Information


SEN_HW_BATTERY / Status

SEN_HW_BATTERY / Status Information


139Connectors


Version 2.9.25

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)


Discovered objects



Fans (SEN_HW_FAN)








SEN_HW_FAN / Speed

SEN_HW_FAN / Status






140Connectors


Version 2.9.25

Dell EqualLogic PS SeriesThere can be multiple PS Systems controlled by the same controller. Thus multiple enclosures arelikely.

Target

Typical platform(s): Dell EqualLogic PS Series Disk Systems


Instrumentation layer: Dell EqualLogic MIBs / SNMP Agent (EQLGROUP-MIB)


Discovered objects



Fans (SEN_HW_FAN)








SEN_HW_PHYSICALDISK / Error Count

SEN_HW_FAN / Status

SEN_HW_FAN / Speed






141Connectors


Version 2.9.25

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)


142Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)

Voltage sensors (SEN_HW_VOLTAGE)



Memory modules (SEN_HW_MEMORY)

Processors (SEN_HW_CPU)





SEN_HW_FAN / Status


SEN_HW_VOLTAGE / Status

SEN_HW_VOLTAGE / Status Information






SEN_HW_MEMORY / Status

SEN_HW_MEMORY / Status Information

SEN_HW_CPU / Status

SEN_HW_CPU / Status Information


SEN_HW_NETWORK / Status Information








143Connectors


Version 2.9.25

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)


144Connectors


Version 2.9.25

Discovered objects




Fans (SEN_HW_FAN)












SEN_HW_FAN / Status











Dell OpenManage Array ManagerThis connector provides disks monitoring through the Dell OpenManage Array Manager SNMP agent(not to be confused with Storage Manager).

Target


Operating system(s): Microsoft Windows, Linux

Instrumentation layer: Dell OpenManage Server Administrator

145Connectors


Version 2.9.25


Discovered objects








Dell OpenManage Server AdministratorThis connector provides hardware monitoring through the Dell OpenManage Server AdministratorSNMP agent which supports almost all DELL PowerEdge servers.

Target





146Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)










SEN_HW_FAN / Status

SEN_HW_FAN / Speed

SEN_HW_VOLTAGE / Voltage







SEN_HW_MEMORY / ErrorCount

SEN_HW_CPU / Status

SEN_HW_CPU / CurrentSpeed


SEN_HW_ENCLOSURE / Intrusion Status




Dell OpenManage Storage ManagerThis connector provides DELL disk array monitoring through the Dell Storage Manager Agent whichsupports almost all DELL disk arrays.

Target



147Connectors


Version 2.9.25



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)


148Connectors


Version 2.9.25

Discovered objects


Tape drives (SEN_HW_TAPEDRIVE)

Robotics (SEN_HW_ROBOTICS)




SEN_HW_TAPEDRIVE / Error Count

SEN_HW_TAPEDRIVE / Mount Count

SEN_HW_ROBOTICS / Status

SEN_HW_ROBOTICS / Status Information


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 discover and monitor the FC ports of the array and the variousenvironment sensors when available (temperatures, fans, power supplies, etc.). It relies on theWBEM technology and supports SMI-S compliant disk arrays only.

Target

Typical platform(s): Disk Array


Instrumentation layer: EMC SMI-S Agent (ECOM)

Technology used: WBEM

149Connectors


Version 2.9.25

Discovered objects


Fans (SEN_HW_FAN)









SEN_HW_FAN / Status














EMC IsilonThis connector discovers the status of EMC Isilon systems.

Target



Instrumentation layer: EMC Isilon SSH interface


150Connectors


Version 2.9.25

Discovered objects



Fans (SEN_HW_FAN)













SEN_HW_FAN / Speed





SEN_HW_CPU / Status










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

151Connectors


Version 2.9.25

Operating system(s): Linux, Sun Solaris

Instrumentation layer: Emulex's hbacmd utility


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)

152Connectors


Version 2.9.25


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

Target

Typical platform: Fujitsu-Siemens BX Blade Servers

Operating systems: N/A

Instrumentation layer: Fujitsu-Siemens Management Blade


153Connectors


Version 2.9.25

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 Serverview WBEM Agent


154Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status










SEN_HW_CPU / Current Speed

SEN_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 Serverview WBEM Agent

Technology used: WMI

155Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status











SEN_HW_CPU / Status



Fujitsu-Siemens ServerView RAID AgentThis connector provides disk monitoring through the Fujitsu-Siemens ServerView RAID SNMP sub-agent which supports many RAID controllers in Primergy servers.

Target



Instrumentation layer: Fujitsu-Siemens ServerView RAID Agent


156Connectors


Version 2.9.25

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


157Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status

SEN_HW_FAN / Speed





SEN_HW_MEMORY / Error Count

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,

158Connectors


Version 2.9.25

Discovered objects














fio-status

Hitachi BladeSymphony ChassisThis connector provides hardware monitoring for the Hitachi BladeSymphony Chassis racks throughthe Hitachi BladeSymphony Chassis Management Module

Target

Typical platform(s): Hitachi BladeSymphony Chassis


Instrumentation layer: Hitachi BladeSymphony Chassis Management Module


159Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)






LEDs (SEN_HW_LED)


SEN_HW_FAN / Speed

SEN_HW_FAN / Status








SEN_HW_LED / Status


Hitachi HDS Disk ArraysThis connector discovers the enclosure and the disks of Hitachi SAN disk arrays, as well as thestorage pools and storage volumes. It will also discover and monitor the FC ports of the array andthe various environment sensors when available (temperatures, fans, power supplies, etc.). It relieson the WBEM technology and supports SMI-S compliant disk arrays only.

Target



Instrumentation layer: Hitachi SMI-S Agent (Hitachi Storage Command Suite)


160Connectors


Version 2.9.25

Discovered objects



Fans (SEN_HW_FAN)












SEN_HW_FAN / Status
















Hitachi HDS USP/VSP Storage SystemsThis connector discovers the overall (global) status of a USP/VSP's Processors, CSW, Cache, SM,Power Supplies, Batteries, Fans, Physical Disks and Environment.

Target


161Connectors


Version 2.9.25


Instrumentation layer: Hitachi SNMP Agent


Discovered objects


Fans (SEN_HW_FAN)











SEN_HW_FAN / Status










SEN_HW_CPU / Status





162Connectors


Version 2.9.25

HP BladeSystemThis connector provides hardware monitoring for the HP BladeSystem racks through the HP InsightManagement Agents.

Target

Typical platform: HP BladeSystem


Instrumentation layer: HP iLO / HP Insight Management Agents


Discovered objects

Blades (SEN_HW_BLADES)

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status








163Connectors


Version 2.9.25

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


Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status

SEN_HW_FAN / Speed Percent




SEN_HW_POWERSUPPLY / Used Watts






164Connectors


Version 2.9.25

HP Insight Management Agent–Drive ArrayThis connector monitors the HP/Compaq Drive Arrays by connecting to the Storage ManagementSNMP sub-agent of the HP Insight Manager agent.

Target

Typical platform: HP ProLiant

Operating system(s): Microsoft Windows, Linux, HP OpenVMS, HP Tru64, Sun Solaris

Instrumentation layer: HP Insight Management Agents


Discovered objects














SEN_HW_FAN / Status





165Connectors


Version 2.9.25

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



Discovered objects















HP Insight Management Agent - HBAThis connector monitors the HBA cards present in an HP ProLiant system by connecting to the HPInsight Management agent.

Target

Typical platform(s): HP ProLiant

166Connectors


Version 2.9.25

Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris



Discovered objects






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





167Connectors


Version 2.9.25

Discovered objects









HP Insight Management Agent–iLOThis connector provides hardware monitoring of the HP iLO card in HP ProLiant servers through theHP Insight Manager (Server Agent) which supports almost all HP Proliant and Integrity servers underWindows and Linux, as well as Tru64 servers.

Target


Operating systems: Microsoft Windows, Linux, HP OpenVMS, HP Tru64, Sun Solaris



Discovered objects







168Connectors


Version 2.9.25

HP Insight Management Agent (v8.25 or higher) -MemoryThis connector provides Memory Information through the HP Insight Manager (Newer ServerAgents).

Target





Discovered objects





HP Insight Management Agent (v8.20 or lower) -MemoryThis connector provides Memory Information through the HP Insight Manager (Older Server Agents).

Target





169Connectors


Version 2.9.25

Discovered objects





HP Insight Management Agent - NetworkThis connector discovers enclosures, Ethernet ports and aggregations through the HP InsightManager Agent.

Target


Operating system(s): Microsoft Windows, Linux, SUN, HP



Discovered objects













170Connectors


Version 2.9.25

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





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



171Connectors


Version 2.9.25



Discovered objects

Fans (SEN_HW_FAN)







SEN_HW_FAN / Status



SEN_HW_POWERSUPPLY / Used Watts


SEN_HW_CPU / Status

SEN_HW_CPU / Predicted Failure



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



172Connectors


Version 2.9.25

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


173Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / Status












SEN_HW_CPU / Status












174Connectors


Version 2.9.25

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




175Connectors


Version 2.9.25

HP MP/GSP card (iLO)This connector provides environmental information (temperatures, fans, etc.) on HP 9000 andIntegrity servers 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 Cardsand Fibre Ports on P2000 / MSA Series Filers.

Target

Typical platform(s): HP StorageWorks MSA P2000


176Connectors


Version 2.9.25

Instrumentation layer: HP MSA Management Card


Discovered objects



Fans (SEN_HW_FAN)














SEN_HW_FAN / Status












W e recommend setting the collection interval for all MSA Disk arrays to at least 15 minutes to preventthe management card from being overloaded.


177Connectors


Version 2.9.25

HP StorageWorks EVA - SSSU - PMThis connector monitors the environmental sensors located in Disk Shelves. Sensors and physicaldisks are 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

178Connectors


Version 2.9.25

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

179Connectors


Version 2.9.25

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


180Connectors


Version 2.9.25

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





181Connectors


Version 2.9.25

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,you can 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

182Connectors


Version 2.9.25

HP-UX-HBAThis connector provides hardware status information for the fiber channel HBA cards on HP UXsystems.

Target



Instrumentation layer: HP-UX system commands (ioscan, fcmsutil)


Discovered objects










/usr/sbin/ioscan

/opt/fcms/bin/fcmsutil

183Connectors


Version 2.9.25

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


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

184Connectors


Version 2.9.25


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 commands: * /opt/sas/bin/sasmgr


HP-UX - Smart Array RAIDDisplay the physical disks connected to a Smart Array Controller and any configured logical drivesand spare drives.

Target



Instrumentation layer: HP-UX Smart Array Configuration Utility


185Connectors


Version 2.9.25

Discovered objects












/opt/raidsa/bin/sautil

HP-UX-STMThis connector enables monitoring physical disks and memory modules on HP-UX systems throughthe Support Tools Manager utilities (STM).

Target



Instrumentation layer: HP-UX Support Tools Manager (STM)


186Connectors


Version 2.9.25

Discovered objects



Fans (SEN_HW_FAN)








SEN_HW_FAN / Status



HP-UX-WBEM

Target



Instrumentation layer: HP-UX WBEM Provider


187Connectors


Version 2.9.25

Discovered objects


Logical disks (SEN_HW_LOGICALDISK)

RAIDs (SEN_HW_LOGICALDISK)


Fans (SEN_HW_FAN)














SEN_HW_FAN / Status











SEN_HW_CPU / Status




HP-UX - WBEM Network

Target


188Connectors


Version 2.9.25


Instrumentation layer: HP-UX WBEM Provider


Discovered objects






SEN_HW_NETWORK / Speed


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)


189Connectors


Version 2.9.25

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


190Connectors


Version 2.9.25

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)


191Connectors


Version 2.9.25

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

Typical platform(s): IBM RS/6000, IBM pSeries, IBM eServer p5

Operating system(s): IBM AIX

Instrumentation layer: IBM AIX system commands (lsdev, lsattr, fcstat, etc.)


192Connectors


Version 2.9.25

Discovered objects


Parameters collected









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







193Connectors


Version 2.9.25

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/bin/dd

IBM AIX - LUNProvides LUN MPIO status information on IBM AIX systems.

Target



Instrumentation layer: IBM AIX lspath system command


Discovered objects

LUN (SEN_HW_LUN)


SEN_HW_LUN / Available Path Count


IBM AIX - usysfaultThis connector reports the status of the System Attention LED and triggers an alert when this LED isturned on. The alert remains until an administrator manually acknowledges the status of the SystemAttention LED.

This connector should be installed on all IBM AIX servers that are not connected to a HardwareManagement Console (HMC).

194Connectors


Version 2.9.25

Target

Typical platforms: IBM AIX servers


Instrumentation layer: IBM AIX usysfault command


Discovered objects

LEDs (SEN_HW_LED)


SEN_HW_LED / Status

This connector is able to monitor the local host and/or a remote system. This connector probably requires rootprivileges for its proper operation. You therefore will need to configure the product to use the root login/password toexecute external commands. Alternatively, you can configure the product to use the 'sudo' utility for the followingcommands: /usr/lpp/diagnostics/bin/usysfault

IBM BladeCenter Management ModuleThis connector provides hardware monitoring of the IBM BladeCenter chassis through the IBMBladeCenter Management Module (SNMP-based). It also monitors embedded switches, passthroughs,and management modules. It needs to run remotely.

Target

Typical platform: IBM BladeCenter

Operating system: Not applicable

Instrumentation layer: IBM BladeCenter Management Module


195Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)













IBM Director Agent 3.x–WindowsThis connector provides hardware monitoring through the IBM Director Agent version 3.x whichsupports almost 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


196Connectors


Version 2.9.25

Discovered objects




Fans (SEN_HW_FAN)







SEN_HW_FAN / Speed




IBM Director Agent 4.x–LinuxThis connector provides hardware monitoring through the IBM Director Agent version 4.x whichsupports some (not all) xSeries servers.

Target


Operating system: Linux



197Connectors


Version 2.9.25

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/cimcli.

IBM Director Agent 4.x–WindowsThis connector provides hardware monitoring through the IBM Director Agent version 4.x whichsupports almost all IBM Netfinity and xSeries servers.

Target



198Connectors


Version 2.9.25



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 whichsupports some (not all) xSeries servers.

Target



Instrumentation layer: IBM Director Agent 5.10.x

199Connectors


Version 2.9.25


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 whichsupports almost all IBM Netfinity and xSeries servers.

Target


200Connectors


Version 2.9.25




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



201Connectors


Version 2.9.25



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 command: /opt/ibm/icc/cimom/bin/CLI.

202Connectors


Version 2.9.25

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 andxSeries servers.

Target





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




203Connectors


Version 2.9.25


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 andxSeries servers.

Target

Typical platform(s): IBM xSeries, IBM Netfinity




204Connectors


Version 2.9.25

Discovered objects









IBM Director Agent 6.x - LinuxThis connector provides hardware monitoring through the IBM Director Agent version 6.x.

Target





205Connectors


Version 2.9.25

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





206Connectors


Version 2.9.25

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


207Connectors


Version 2.9.25

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,you can 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 discover and monitor the FC ports, physical and logical disksof the array. It relies on the WBEM technology and supports SMI-S compliant disk arrays only.

Target



208Connectors


Version 2.9.25

Instrumentation layer: IBM SMI-S Agent (IBM System Storage DS6000/DS8000 Storage Manager)


Discovered objects


















IBM Hardware Management Console (HMC)This connector monitors the overall health of IBM AIX servers through the Hardware ManagementConsole (HMC). It reports the status of the System Attention LED and triggers an alert if a hardwareproblem has been reported on each system since 0:00am.

This connector should be installed on a separate system to monitor the IBM AIX systems connectedto a Hardware Management Console (HMC) by connecting to the HMC system. Please note that thisconnector requires root privileges and that the monitoring of the HMC itself needs to be configuredwith this connector.

Target

Typical platform(s): IBM AIX servers


209Connectors


Version 2.9.25

Instrumentation layer: IBM Hardware Management Console (HMC)


Discovered objects


LEDs (SEN_HW_LED)




SEN_HW_LED / Status


IBM Netfinity Manager 5.20.x–BasicThis connector provides basic environment monitoring through the IBM Netfinity Manager ServicesSNMP sub-agent which supports almost all old IBM servers (Netfinity) under Windows.

Target

Typical platform: IBM Netfinity


Instrumentation layer: IBM Netfinity Manager 5.20.x


210Connectors


Version 2.9.25

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 ServicesSNMP sub-agent which supports almost all old IBM servers (Netfinity) under Windows.

Target





Discovered objects








211Connectors


Version 2.9.25

IBM Netfinity Manager 5.20.x–NormalThis connector provides environment monitoring through the IBM Netfinity Manager Services SNMPsub-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)


212Connectors


Version 2.9.25

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)


213Connectors


Version 2.9.25

Discovered objects












IBM Storwize 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 discover and monitor the FC ports, physical and logical disksof the array. It logs in directly to the v3700 and v7000 cluster's management interface.

Target



Instrumentation layer:


214Connectors


Version 2.9.25

Discovered objects






LEDs (SEN_HW_LED)








SEN_HW_LED / Status

SEN_HW_LED / Status Information




IBM VIO ServerProvides hardware status information (processors, memory modules, network interfaces, HBAs,physical disks) on IBM VIO systems.

Target



Instrumentation layer: IBM AIX system commands through the IOS interface (lsdev, entstat, etc.)


215Connectors


Version 2.9.25

Discovered objects







Collected parameters






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 Agentsunder Windows and Linux.

Target

Typical platform(s): Generic Servers


Instrumentation layer: Intel Server Manager 8 SNMP Agents


216Connectors


Version 2.9.25

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


217Connectors


Version 2.9.25

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

218Connectors


Version 2.9.25

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 privileges for its proper operation. You therefore will need to configure theproduct 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: * 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

219Connectors


Version 2.9.25

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








220Connectors


Version 2.9.25

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 thelsiutil utility.

Target

Typical platform(s): Windows servers equipped with an LSI RAID controller


Instrumentation layer: lsiutil


221Connectors


Version 2.9.25

Discovered objects








LSI Logic - LsiUtil - RAIDGives information about physical disks and volumes of LSI Logic SAS RAID controllers through thelsiutil utility.

Target

Typical platform(s): Sun Fire (x64)

Operating system(s): Linux, Sun Solaris

Instrumentation layer: lsiutil


Discovered objects








222Connectors


Version 2.9.25

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-agent which supports all MegaRAID-based RAID controllers.

Target



Instrumentation layer: LSI MegaRAID PowerConsole


Discovered objects








223Connectors


Version 2.9.25

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

224Connectors


Version 2.9.25


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









225Connectors


Version 2.9.25

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 providedwith the Emulex Drivers.

Target

Typical platform(s): Linux Server with HBAs


Instrumentation layer: Emulex's hbacmd utility


Discovered objects


226Connectors


Version 2.9.25












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


227Connectors


Version 2.9.25











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

Target

Typical platform(s): Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NECExpress5800, Sun Fire (x64)


Instrumentation layer: Linux multipath utility


228Connectors


Version 2.9.25

Discovered objects

LUN (SEN_HW_LUN)



SEN_HW_LUN / Available Path Information


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


229Connectors


Version 2.9.25

Discovered objects







Credentials


scli

McData Fibre Switch

Target

Typical platform(s): McData San Switches

Operating system(s): Storage

Instrumentation layer: SNMP


230Connectors


Version 2.9.25

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

Operating system(s): Sun Solaris, Linux

Instrumentation layer: MegaCli (LSI) managed RAID card


231Connectors


Version 2.9.25

Discovered objects









Credentials


MegaCli

MIB-2 Standard SNMP Agent - Network InterfacesThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with aMIB-2 standard 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


232Connectors


Version 2.9.25

Discovered objects












MIB-2 Standard SNMP Agent - Network Interfaces- LinuxThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with aMIB-2 standard SNMP Agent.

Target





Discovered objects


233Connectors


Version 2.9.25











MIB-2 Standard SNMP Agent - Network Interfaces- WindowsThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with aMIB-2 standard SNMP Agent.

Target





234Connectors


Version 2.9.25

Discovered objects












MIB-2 Standard SNMP Agent - Network Interfaces- SolarisThis connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with aMIB-2 standard SNMP Agent.

Target


Operating system(s): Sun Solaris



235Connectors


Version 2.9.25

Discovered objects












Motherboard MonitorThis connector provides hardware monitoring through Motherboard Monitor version 5.x whichsupports almost all non-branded PCs under Windows.

Target

Typical platform: Unbranded PC


Instrumentation layer: Motherboard Monitor


236Connectors


Version 2.9.25

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 thevarious environment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMPprotocol.

Target



Instrumentation layer: NetApp SNMP Agent


237Connectors


Version 2.9.25

Discovered objects



Fans (SEN_HW_FAN)










SEN_HW_FAN / Status






NEC ESMPRO AgentThis connector provides hardware monitoring through the NEC ESMPRO Agent which supports almostall NEC Express5800 and some BULL NovaScale servers running Windows and Linux.

Target

Typical platform: NEC Express5800


Instrumentation layer: NEC ESMPRO Agent


238Connectors


Version 2.9.25

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


239Connectors


Version 2.9.25

Discovered objects










Pure Storage FA Series (SSH)This connector discovers the Environmental, Physical Disk, Logical Disk, Management Network Cardsand Fiber Ports on Pure Storage FA Series arrays.

Target

Typical platform: Pure Storage FA Series

Operating systems: Storage Device

Instrumentation layer: Pure Storage Management Card


240Connectors


Version 2.9.25

Discovered objects


Fans (SEN_HW_FAN)








SEN_HW_FAN / Status













QLogic HBAs - ESXThis connector discovers the QLogic HBAs of a server. It relies on the WBEM technology.

Target

Typical platform: Server with QLogic HBAs

Operating systems: Linux

Instrumentation layer: QLogic Cim Agent for ESX


241Connectors


Version 2.9.25

Discovered objects






Quantum (ADIC) Based Tape Libraries

Target

Typical platform(s): Quantum (ADIC) Tape Library


Instrumentation layer: Quantum SNMP Agent (ADIC-TAPE-LIBRARY-MIB)


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 / Needs Cleaning


SEN_HW_ROBOTIC / Status


242Connectors


Version 2.9.25

Quantum (ADIC) Enterprise Level Tape LibrariesThis connector provides hardware monitoring through the Quantum Scalar's SNMP interface. It isprimarily designed for the i2000 and i6000 libraries.

Target

Typical platform(s): Quantum (ADIC) Tape Library i2000 i6000


Instrumentation layer: Quantum SNMP Agent (ADIC-MANAGEMENT-MIB)


243Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / Speed

SEN_HW_FAN / Status














SEN_HW__TAPEDRIVE / Status

SEN_HW_TAPEDRIVE / Status Information






SmartMonToolsThis connector provides S.M.A.R.T.-enabled physical disk information through the smartd/smartctlutility under Linux

Target

Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, Sun Fire(x64)

244Connectors


Version 2.9.25


Instrumentation layer: SmartMonTools


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 discover and monitor the FC ports of the array and the variousenvironment sensors when available (temperatures, fans, power supplies, etc.). It relies on theWBEM technology and supports SMI-S compliant disk arrays only.

Target



Instrumentation layer: SMI-S Agent provided by the array vendor

245Connectors


Version 2.9.25


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


246Connectors


Version 2.9.25

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 Netfinityand xSeries servers.

Target



Instrumentation layer: IBM Director Agent 5.20.x / 6.10.x


Discovered objects









247Connectors


Version 2.9.25

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 discover and monitor the FC ports of the arrayand the various environment sensors when available (temperatures, fans, power supplies, etc.). Itrelies on the 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

248Connectors


Version 2.9.25


Discovered objects

Fans (SEN_HW_FAN)









SEN_HW_FAN / 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 technologyand supports SMI-S compliant switches only.

Target



Instrumentation layer: SMI-S Agent provided by the switch vendor

249Connectors


Version 2.9.25


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)


250Connectors


Version 2.9.25

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


251Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)








SEN_HW_FAN / Status




SEN_HW_OTHERDEVICE / Power Consumption


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


252Connectors


Version 2.9.25

Discovered objects

Fans (SEN_HW_FAN)






Robotic (SEN_HW_ROBOTIC)


SEN_HW_FAN / Status




SEN_HW_OTHERDEVICE / Usage Count

SEN_HW_OTHERDEVICE / Usage Count





SEN_HW_ROBOTICS / Move Count

SEN_HW_ROBOTICS / Error Count


StorageTek StreamLine Tape LibraryThis connector provides basic hardware monitoring of the StorageTek StreamLine tape librariesthrough their built-in SNMP agent. Needs to run remotely.

Target

Typical platform(s): StorageTek StreamLine


Instrumentation layer: StorageTek StreamLine SNMP Agent


253Connectors


Version 2.9.25

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


254Connectors


Version 2.9.25

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 SNMPAgent / SSH (optional).

Target

Typical platform(s): SUN Blade Chassis


Instrumentation layer: SUN Blade Chassis CMM SNMP Agent


255Connectors


Version 2.9.25

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


256Connectors


Version 2.9.25

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


257Connectors


Version 2.9.25

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


258Connectors


Version 2.9.25

Discovered objects













SEN_HW_CPU / Status



Sun Solaris–Environment (ALOM-CMT snapshot)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 cardin-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


259Connectors


Version 2.9.25

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 Sunplatforms through the prtpicl utility. This connector is to be used mainly on Solaris 10 systems.

Target



Instrumentation layer: Sun Solaris system commands (prtpicl, etc.)

260Connectors


Version 2.9.25


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 Sunplatforms through the prtdiag or lom utility.

Target



Instrumentation layer: Sun Solaris system commands (prtdiag, lom, psrinfo, etc.)


261Connectors


Version 2.9.25

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,you can configure the product to use the 'sudo' utility for the following command: /usr/sbin/lom.

Sun Solaris - Fault Manager (Memory and CPU)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)


262Connectors


Version 2.9.25

Discovered objects









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.Requires root privileges

Target



Instrumentation layer: Sun Solaris system commands (cediag, cestat)


263Connectors


Version 2.9.25

Discovered objects



SEN_HW_MEMORY / Predicted Failure



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 machinethrough the psrinfo system command.

Target



Instrumentation layer: Sun Solaris system commands (psrinfo, etc.)


Discovered objects



SEN_HW_CPU / Status

264Connectors


Version 2.9.25


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 can configure the product to use the sudo utility for the following commands:

265Connectors


Version 2.9.25

/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 tobe manually 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 / Hard Error Count

SEN_HW_PHYSICALDISK / Media Error Count

SEN_HW_PHYSICALDISK / Device Not Ready Error Count

SEN_HW_PHYSICALDISK / No Device Error Count

SEN_HW_PHYSICALDISK / Transport Error Count

SEN_HW_PHYSICALDISK / Recoverable Error Count

SEN_HW_PHYSICALDISK / Illegal Request Error Count




Credentials


266Connectors


Version 2.9.25

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


Instrumentation layer: Sun Solaris system commands (raidctl)

267Connectors


Version 2.9.25


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




268Connectors


Version 2.9.25

Discovered objects


CPU Cores (SEN_HW_CPUCORE)


SEN_HW_CPUCORE / Status

SEN_HW_CPUCORE / Status Information


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


269Connectors


Version 2.9.25

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





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

270Connectors


Version 2.9.25


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


271Connectors


Version 2.9.25

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




272Connectors


Version 2.9.25

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









273Connectors


Version 2.9.25

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





274Connectors


Version 2.9.25

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 / Time Left


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 (LUNMulti-Path Disk Device) are found.

Target

Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NECExpress5800, Sun Fire (x64)




275Connectors


Version 2.9.25

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


276Connectors


Version 2.9.25

Discovered objects


LUN (SEN_HW_LUN)











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)




277Connectors


Version 2.9.25

Discovered objects










Index 278


Version 2.9.25

Index

- A -Abnormalities 53

Actions

Collection 63

Detection 63

Discovery 63Adaptec

AAC 131

Adaptec AAC-based RAID 131

Adaptec DPT-based RAID 131

Adaptec IOManager 129

Adaptec Storage Manager 131

Adaptec Storage Manager DPT 131

Adaptec Storage Manager Web Edition 131

Adaptec Storage Manager Web Edition AAC 131

Adaptec StorMan (RAID) 130

Adaptec U320 HostRAID 129Adapter

Add 46

Create 46Adding the Hardware Application Class to anExisting Element 40

Agent 153, 211, 212

Dell iDRAC Management 141, 143

Fujitsu-Siemens Serveview WBEM 154

HP Insight Management Agents 172

Quantum (ADIC) Enterprise Level TapeLibraries 242

Agents 152

Brocade SNMP 132

EQLGROUP-MIB 140

fcSwitch 132

Fujitsu-Siemens Serveview 156

Fusion ioDrive (fio-status) 157

Hardware 22, 61

Hitachi SNMP Agent 160

HP iLO / HP Insight Management 162

HP Insight Management 164, 165, 166,168, 169, 170, 171, 174

IBM Director Agent 5.20.x / 6.10.x 246,247

Intel Server Manager 8 SNMP 215, 216

LSI MegaRAID SAS SNMP 223

NetApp SNMP 236

Promise FastTrack SNMP Agent 238

Quantum SNMP Agent 241

SNMP 136, 140

SNMP Agent 65, 135

SUN Blade Chassis CMM SNMP Agent 254

SUN Blade SP SNMP Agent 256

Vendor-specific 61AIX

Requirements 30Alerts

Conditions 83

Configuration 83ALOM

ALOM-CMT snapshot 258Application Classes 218, 242

Battery 94

Blade 95

Capacity Report 96

Connector 97

CPU 90, 98, 99, 104

CPU Core 99

Disk Controller 99, 112

Enclosure 100, 111, 112

Fan 100, 104

LED 102

Logical Disk 90, 102, 104

LUN 103

Main 63, 65, 104

Memory 90, 105

Network 90, 106

Other Device 108

Physical Disk 63, 83, 90, 109

Power Supply 110

Robotics 90, 111

SEN_HW_BATTERY 137, 140, 141, 143,145, 148, 149, 159, 160, 164, 177, 184, 206,213, 274

SEN_HW_BLADE 133, 134, 137, 139, 152,158, 163, 177, 194, 216, 229

SEN_HW_CPU 141, 145, 149, 153, 154,156, 160, 170, 172, 174, 178, 180, 186, 189,196, 197, 198, 199, 200, 202, 204, 205, 214,215, 237, 250, 256, 257, 263, 266, 267, 270,273

SEN_HW_CPUCORE 267

Index 279


Version 2.9.25

Application Classes 218, 242

SEN_HW_DISKCONTROLLER 129, 130,131, 137, 143, 144, 146, 155, 157, 164, 165,166, 170, 179, 181, 183, 184, 185, 186, 192,195, 196, 197, 198, 199, 200, 202, 203, 206,210, 214, 216, 219, 220, 221, 222, 223, 224,225, 230, 238, 241, 246, 247, 265, 266, 268,272, 274

SEN_HW_ENCLOSURE 132, 133, 134,135, 136, 137, 139, 140, 141, 143, 145, 147,148, 149, 151, 152, 156, 158, 159, 160, 162,163, 165, 170, 172, 174, 175, 177, 178, 180,186, 189, 194, 196, 197, 198, 199, 200, 202,204, 205, 206, 207, 208, 211, 212, 214, 215,216, 217, 229, 235, 236, 237, 239, 241, 244,247, 248, 249, 250, 251, 252, 253, 254, 255,256, 257, 258, 260, 270, 273

SEN_HW_FAN 132, 133, 134, 135, 136,137, 139, 140, 141, 143, 145, 148, 149, 151,152, 153, 154, 156, 158, 159, 160, 162, 163,170, 171, 172, 174, 175, 177, 178, 186, 188,190, 194, 195, 196, 197, 198, 199, 200, 202,204, 205, 206, 209, 215, 216, 217, 229, 235,236, 237, 239, 241, 244, 247, 248, 250, 251,253, 254, 255, 258, 259, 260, 270, 273

SEN_HW_LED 158, 193, 208, 213

SEN_HW_LOGICALDISK 129, 130, 131,136, 137, 140, 143, 144, 146, 149, 155, 159,164, 165, 166, 170, 175, 177, 179, 183, 184,186, 195, 196, 197, 198, 199, 200, 202, 203,206, 207, 210, 219, 220, 221, 222, 223, 224,225, 230, 236, 238, 244, 245, 246, 247, 266,269, 272

SEN_HW_LUN 193, 227, 275

SEN_HW_MEMORY 141, 145, 153, 154,156, 159, 160, 168, 170, 172, 174, 177, 178,185, 186, 189, 196, 197, 198, 199, 200, 202,204, 205, 214, 215, 237, 250, 256, 257, 260,261, 262, 270, 273

SEN_HW_NETWORK 132, 133, 134, 141,148, 149, 150, 151, 159, 165, 167, 169, 172,174, 175, 180, 182, 183, 187, 189, 191, 206,207, 214, 216, 225, 226, 228, 229, 231, 232,233, 234, 236, 239, 240, 244, 245, 247, 248,264, 270, 273, 275, 276

SEN_HW_NETWORKCARD 177

SEN_HW_OTHERDEVICE 133, 137, 139,143, 145, 148, 158, 159, 160, 162, 163, 165,167, 172, 174, 175, 177, 206, 207, 213, 216,229, 244, 247, 248, 250, 251, 253, 255, 258,261

SEN_HW_PHYSICALDISK 129, 130, 131,135, 136, 137, 140, 143, 144, 146, 148, 149,155, 157, 159, 160, 164, 165, 166, 170, 175,177, 179, 181, 183, 184, 185, 186, 192, 195,196, 197, 198, 199, 200, 202, 203, 206, 207,210, 213, 214, 216, 219, 220, 221, 222, 223,224, 225, 230, 236, 238, 239, 243, 244, 246,247, 253, 256, 257, 258, 265, 266, 268, 271,272, 274

SEN_HW_POWERSUPPLY 132, 133, 134,135, 136, 137, 139, 140, 141, 143, 145, 148,149, 151, 152, 153, 154, 156, 158, 159, 160,162, 163, 170, 171, 172, 174, 175, 177, 178,186, 188, 190, 194, 195, 196, 197, 198, 199,200, 202, 204, 205, 206, 213, 216, 217, 229,235, 236, 237, 239, 241, 244, 247, 248, 250,251, 253, 254, 255, 258, 260, 270, 273

SEN_HW_ROBOTIC 241, 247, 249, 251

SEN_HW_ROBOTICS 147, 211, 212

SEN_HW_TAPEDRIVE 147, 211, 212, 241,247, 249, 251, 252, 269

SEN_HW_TEMPERATURE 132, 133, 134,135, 136, 137, 139, 140, 141, 145, 149, 151,152, 153, 154, 156, 157, 158, 160, 162, 163,170, 172, 174, 175, 177, 178, 186, 190, 194,195, 196, 197, 198, 199, 200, 202, 204, 205,206, 209, 211, 213, 215, 217, 229, 235, 236,237, 239, 243, 244, 247, 248, 251, 253, 254,255, 256, 257, 258, 259, 260, 270, 273

SEN_HW_VOLTAGE 141, 145, 149, 153,154, 156, 157, 175, 178, 186, 190, 194, 195,196, 197, 198, 199, 200, 202, 204, 205, 209,211, 215, 217, 235, 237, 250, 253, 254, 255,256, 257, 258, 259, 260, 270, 273

Tape Drive 112

Tape Drives 90

Temperature 63, 112

Voltage 113Architecture 58, 60, 63

- B -Baselines

BMC ProactiveNet Performance Management 53

Generation 53

Manage 53

Requirements 53BMC

ProactiveNet Performance Management 46

Index 280


Version 2.9.25

BMC ProactiveNet Performance Management

Abnormalities 53

Baselines 53

Key Performance Indicators 53

KPI 53Brocade SAN Switch 132

- C -Cisco

Cisco UCS 134

Cisco UCS Manager (Blade, FabricInterconnect Switch) 134

Cisco UCS Manager (XML API) 134

Cisco UCS XML API 134Collection

Process 65Commands 218

arcconf 130

cediag 262

cestat 262

CmdTool2 224

dd 265, 268, 269

HP-UX system 180, 181, 182, 183

IBM AIX system 188, 189, 190, 191, 192,193, 214

ifconfig 264

iostat 265, 268, 269

kstat 264

Linux system 226

lsiutil 220, 221

MegaCli 224

ndd 264

psrinfo 266, 267

Raidctl 266

System 130, 178, 180, 181, 182, 183,184, 185, 188, 189, 190, 191, 192, 193, 206,207, 214, 217, 220, 221, 224, 225, 226, 227,228, 230, 235, 243, 250, 255, 258, 259, 260,261, 262, 264, 265, 266, 267, 268, 269

Windows system 224Configuration 115

Alerts 83

Sudo 30, 32, 35, 37

Connector 65, 121, 129, 130, 131, 132, 133,134, 135, 136, 137, 139, 140, 141, 143, 145,146, 147, 151, 152, 153, 154, 156, 157, 158,159, 162, 163, 164, 165, 166, 167, 168, 169,170, 171, 174, 175, 177, 178, 179, 180, 181,182, 183, 184, 185, 186, 187, 188, 189, 190,191, 192, 193, 195, 196, 197, 198, 199, 200,202, 203, 204, 205, 206, 207, 209, 210, 211,212, 213, 214, 215, 216, 217, 219, 220, 221,222, 223, 224, 225, 226, 227, 230, 231, 232,233, 234, 235, 236, 237, 238, 241, 243, 244,245, 246, 247, 248, 249, 250, 251, 252, 253,254, 255, 256, 257, 258, 259, 261, 264, 265,266, 267, 268, 270, 271, 272, 273, 274, 275,276

MS_HW_HitachiVSPSNMP.hdf 160

Quantum (ADIC) Enterprise Level TapeLibraries 242

Connectors 269

MS_HW_McData.hdf 229

MS_HW_SunPsrinfo.hdf 263Controller

LSI RAID 220, 221Credentials 180, 181, 182, 183, 184, 188,196, 198, 200, 217, 221, 225, 226, 227, 228,243, 258, 260, 261, 264, 265, 266, 268, 269

Custer's management interface 213

- D -Data Domain Storage Appliance 136

DataDirect Networks (DDN) Disk Array 135

Debug Mode 37

Enabling 86Default system wattage 37

Dell

Dell CMC (Dell Chassis ManagementController) 137

Dell DRAC Dell Remote Access Card 139

Dell EqualLogic MIBs 140

Dell EqualLogic PS Series 140

Dell EqualLogic PS Series Disk Systems 140

Dell OpenManage Array Manager 144

Dell OpenManage Server 144, 145, 146

Dell OpenManage Server Administrator 144, 145, 146

Dell OpenManage Storage Manager 146

DELL PERC RAID 144, 146

Dell PowerEdge 141, 143, 144, 145, 146

Index 281


Version 2.9.25

Dell

Dell PowerVault TL2000 147

Dell PowerVault TL4000 147

Dell SNMP Agent 147

Dell's iDRAC Management Card 141, 143

DELL-SHADOW-MIB 147Detection

Process 64Devices 266

Batteries 137, 141, 143, 148, 149, 159,160, 177, 213

Battery 94, 140, 164, 184, 206, 274

Blade 95, 133, 134, 139, 152, 158, 194,216

Blades 137, 229

Cache Memory 177

Controller 129, 131, 144, 146

Controllers 177

CPU Cores 267

Disk 62

Disk controller 99, 108, 130, 143, 155,164, 165, 166, 170, 179, 181, 183, 184, 185,192, 195, 196, 197, 198, 199, 200, 202, 203,206, 210, 214, 216, 219, 220, 221, 222, 223,224, 225, 230, 238, 241, 246, 247, 265, 266,268, 272, 274

Disk controllers 137, 157, 186

Disk enclosure 62

Disk Shelves 177

Disk Systems 177

EMU 177

Enclosure 152

Enclosure model 132, 133, 134, 135, 136,137, 139, 140, 141, 143, 145, 147, 148, 149,151, 153, 154, 156, 158, 159, 160, 162, 163,165, 170, 174, 175, 178, 180, 186, 189, 194,196, 197, 198, 199, 200, 202, 204, 205, 206,207, 208, 211, 212, 213, 214, 215, 216, 217,218, 229, 235, 236, 237, 239, 241, 242, 244,247, 248, 249, 250, 251, 252, 253, 254, 255,256, 257, 258, 260, 270, 273

Environment 152

Ethernet Ports 177

Fan 62, 100, 108, 132, 133, 134, 136,139, 140, 145, 151, 152, 156, 158, 162, 163,170, 171, 174, 175, 178, 188, 190, 194, 195,196, 197, 198, 199, 200, 202, 204, 205, 206,209, 215, 216, 217, 235, 236, 237, 241, 244,247, 248, 250, 251, 253, 254, 255, 258, 259,260, 270, 273

Fans 135, 137, 141, 143, 148, 149, 153,154, 159, 160, 175, 177, 186, 229, 239, 242

Fiber Ports 177

HP 177

IO Module 177

LED 158

LEDs 193, 208, 213

Logical disk 102, 108, 129, 130, 131, 136,140, 144, 146, 155, 164, 165, 166, 170, 175,179, 183, 184, 195, 196, 197, 198, 199, 200,202, 203, 206, 210, 219, 220, 221, 222, 223,224, 225, 230, 236, 238, 244, 245, 246, 247,266, 272

Logical disks 137, 149, 159, 186, 207, 269

Logical disks, RAIDs 143

LUN 193, 227, 275

Management Blade 152

Memory module 62, 108, 145, 156, 168,170, 174, 178, 185, 196, 197, 198, 199, 200,202, 204, 205, 214, 215, 237, 250, 256, 257,260, 261, 262, 270, 273

Memory modules 141, 153, 154, 159,160, 186, 189

Network cards 108, 132, 133, 134, 141,148, 149, 150, 151, 159, 165, 167, 169, 174,175, 180, 182, 183, 189, 191, 206, 207, 214,216, 225, 226, 228, 229, 231, 232, 233, 234,236, 239, 240, 244, 245, 247, 248, 264, 270,273, 275, 276

Network interface 62

Non-RAID Disk 62

Other devices 137, 143, 148, 159, 160,207, 213, 229, 261

Others 133, 139, 145, 158, 162, 163, 165,167, 174, 175, 206, 216, 244, 247, 248, 250,251, 253, 255, 258

Physical disk 108, 129, 130, 131, 136,140, 144, 146, 155, 164, 165, 166, 170, 175,179, 181, 183, 184, 185, 192, 195, 196, 197,198, 199, 200, 202, 203, 206, 210, 214, 216,219, 220, 221, 222, 223, 224, 225, 230, 236,238, 243, 244, 246, 247, 253, 256, 257, 258,265, 266, 268, 271, 272, 274

Physical disks 135, 137, 143, 148, 149,157, 159, 160, 177, 186, 207, 213, 239

Index 282


Version 2.9.25

Devices 266

Power supplies 62, 108, 132, 133, 134,135, 136, 137, 139, 140, 141, 143, 145, 148,149, 151, 152, 153, 154, 156, 158, 159, 160,162, 163, 170, 171, 174, 175, 177, 178, 186,188, 190, 194, 195, 196, 197, 198, 199, 200,202, 204, 205, 206, 213, 216, 217, 229, 235,236, 237, 239, 241, 242, 244, 247, 248, 250,251, 253, 254, 255, 258, 260, 270, 273

Processor 62, 108, 145, 156, 170, 174,178, 180, 196, 197, 198, 199, 200, 202, 204,205, 214, 215, 237, 250, 256, 257, 266, 267,270, 273

Processors 141, 149, 153, 154, 160, 186,189, 263

RAID Disk 62, 266

Raid Groups 177

RAIDs 130, 136, 137, 140, 149, 155, 159,164, 165, 166, 170, 175, 179, 183, 184, 186,195, 196, 197, 198, 199, 200, 202, 203, 206,207, 210, 219, 220, 221, 222, 223, 224, 225,230, 236, 238, 244, 245, 246, 247, 266, 269,272

Robotics 147, 211, 212, 241, 242, 247,249, 251

RS232 Bus 177

Tape drive 241, 247, 249, 251, 252, 269

Tape Drives 147, 211, 212, 242

Temperature 62

Temperature sensor 108, 132, 133, 134,136, 139, 140, 145, 151, 156, 158, 163, 170,174, 175, 178, 190, 194, 195, 196, 199, 200,202, 206, 209, 211, 215, 217, 235, 236, 237,243, 244, 247, 248, 251, 253, 254, 255, 256,257, 258, 259, 260, 270, 273

Temperature Sensors 135, 137, 141, 149,153, 154, 157, 160, 186, 213, 229, 239, 242

Temperatures 177

Voltage 62

Voltage sensor 108, 145, 156, 175, 178,190, 194, 195, 196, 199, 200, 202, 209, 211,215, 217, 235, 237, 250, 253, 254, 255, 256,257, 258, 259, 260, 270, 273

Voltage Sensors 141, 149, 153, 154, 157,186, 242

Discovered objectsENDIFsentrywebsiteDiscovered objectsEND 189

Discovery

Process 65

Disk 129, 130, 131, 136, 144, 146, 155, 164,166, 170, 179, 183, 184, 185, 192, 195, 196,197, 198, 199, 200, 202, 203, 206, 214, 216,220, 221, 223, 225, 238, 244, 245, 247, 253,265, 266, 268, 271, 272

Physical 258, 274DPT 131

DuplexMode 169

- E -ECOM 148

EMC

Isilon Systems 149EMC SMI-S Agent 148

Emulex HBAs 150

Environment 60

lom 260

Monitoring 69

prtdiag 260Error Count Auto-reset After 37

- F -Fan

Monitoring 69FAQ 86

FC ports 213

Fibre Alliance SNMP Agent (Switches) 151

Files

.hdf 64, 65, 121

rsmcfg.properties 115Firewall 92

Fujitsu 154

BX Blade Servers 152

FSC BX Blade Servers 152

Fujitsu-Siemens 152

Fujitsu-Siemens Blade 152

Fujitsu-Siemens PRIMERGY 153, 219,220, 222, 223

Fujitsu-Siemens Serverview 156

Fujitsu-Siemens ServerView RAID Agent 155

Fujitsu-Siemens Serveview 153

- G -Generate

Index 283


Version 2.9.25

Generate

Baselines 53Getting Started 19

- H -HBA 275

hbacmd 150

hdf 41

Hitachi 159

Hitachi BladeSymphony Chassis 158

Hitachi BladeSymphony ChassisManagement Module 158

Hostname 37

HP 187

HP 9000 175, 180, 181, 182, 183, 184

HP BladeSystem 162

HP BladeSystem - Telnet/SSH 163

HP BladeSystem Onboard Administrator 163

HP EVA Storage Systems 177

HP Insight Management Agent - HBA 165

HP Insight Management Agent - Network 169

HP Insight Management Agent - Server -WMI 174

HP Insight Management Agent (v8.20 orlower) - Memory 168

HP Insight Management Agent (v8.25 orhigher) - Memory 168

HP Insight Management Agent–Drive Array 164

HP Insight Management Agent–Fiber Array 165

HP Insight Management Agent–IDE Storage 166

HP Insight Management Agent–iLO 167

HP Insight Management Agents 165, 166,167, 168, 169, 170, 171, 174

HP Insight Management Agent–SCSI Storage 170

HP Insight Management Agent–Server 170

HP Insight Management Agent–Server(Alpha) 171

HP Integrity 180, 181, 182, 183, 184

HP MP/GSP card (iLO) 175

HP MSA 2000 & P2000 175

HP MSA Management Card 175

HP NetServer 178, 179

HP OpenVMS 165, 166, 167, 168, 169,170, 171

HP ProLiant 164, 165, 167, 168, 169, 170,171, 174

HP StorageWorks EVA - SSSU - PM 177

HP StorageWorks MSA P2000 175

HP SuperDome 180, 181, 182, 183, 184

HP TopTools Agent 178

HP TopTools NetRaid Agent 179

HP Tru64 165, 166, 167, 168, 169, 170,171

HP-UX 181, 182, 183, 184, 185

HP-UX - Network 183

HP-UX - SASMGR Managed Disks 183

HP-UX - Smart Array RAID 184

HP-UX Smart Array Configuration Utility 184

HP-UX Support Tools Manager (STM) 185

HP-UX system commands 183

HP-UX–Disks 181

HP-UX-STM 185HP-UX 186

Requirements 30

- I -IBM

BM-3100-MIB 211, 212

IBM AIX 188, 190, 191, 192, 193, 214

IBM AIX - HBA 191

IBM AIX lspath 193

IBM AIX system commands 188, 189,190, 191, 192, 193, 214

IBM AIX–CHRP Environment 188

IBM AIX–Common 189

IBM AIX–Environment (ue sensor) 190

IBM AIX–SCSI disks 192

IBM BladeCenter 194

IBM BladeCenter Management Module 194

IBM Director Agent 3.x 195

IBM Director Agent 3.x–Windows 195

IBM Director Agent 4.x 196, 197

IBM Director Agent 4.x–Linux 196, 197

IBM Director Agent 5.10.x 198, 199

IBM Director Agent 5.10.x–Linux 198

IBM Director Agent 5.10.x–Windows 199

IBM Director Agent 5.20.x / 6.10.x 246,247

Index 284


Version 2.9.25

IBM

IBM Director Agent 5.20.x–Linux 200

IBM Director Agent 5.20.x–ServeRAID -Linux 202

IBM Director Agent 5.20.x–ServeRAID -Windows 203

IBM Director Agent 5.20.x–Windows 202

IBM Director Agent 6 205

IBM Director Agent 6 - Linux 204

IBM Director Agent 6 - Windows 205

IBM Director Agent 6.1.x 204

IBM DS (LSI) Disk Arrays (smcli) 206, 207

IBM eServer p5 188, 189, 190, 191, 192,193, 214

IBM Netfinity 195, 196, 197, 198, 199,202, 203, 204, 205, 246, 247

IBM Netfinity Manager 5.20.x–Basic 209

IBM Netfinity Manager 5.20.x–Disks 210

IBM Netfinity Manager 5.20.x–Normal 211

IBM pSeries 188, 189, 190, 191, 192, 193,214

IBM RS/6000 188, 189, 190, 191, 192,193, 214

IBM SAN disk arrays 213

IBM SNMP Agent SNMP 211, 212

IBM TS3100 211, 212

IBM TS3100 Tape Libraries 211, 212

IBM v7000 213

IBM VIO Server 214

IBM xSeries 195, 196, 197, 198, 199, 202,203, 204, 205, 246, 247

IBM AIX 193, 208

IBM AIX - usysfault 193

IBM AIX usysfault command 193

In case of Status parameter value is UNKNOWN 37

Install

Patch 41Install / Un-install

Adding BPM Express for Hardware to anElement Profile 26

BMC® Performance Manager Express forHardware for BMC® Portal 21

BPM Express for Hardware 23

Hardware Agents 22

Package 21, 23

Prerequisites 23

Procedure 24

Removing BPM Express for Hardware fromManaged Elements 42

Targeted Computers 21

Uninstall 23

Un-installing BPM Express for Hardware 42

Uninstalling BPM Express for Hardware fromthe Portal 43

Integration

BPM Express for Hardware 56Integration Service Agent 46

Intel

Intel Base Board 5 215

Intel Modular Server 216

Intel Server Manager 8 SNMP Agents 215,216

Interaction 60

Introduction 19

IntrusionStatus 156

IPMI 271

IPMI–In-band(IpmiTool) 217

ipmitool 217Isilon 149

- K -Key Performance Indicators


Manage 53KPI


Manage 53

- L -LinkStatus auto-reset after 37

Linux 218, 240

Linux - Emulex HBAs (hbacmd) 225

Linux - Multipath 227

Linux - QLogic HBAs (scli) 228

Linux–Network 226

Requirements 30localhost 218

LSI

LSI 1030-based GAM Server 219

LSI 1030-based GAM Server (Alternate MIB) 220

LSI GAM Server 220

Index 285


Version 2.9.25

LSI

LSI Logic - LsiUtil - RAID (Windows) 220,221

LSI Logic MegaRAID PowerConsole 222

LSI MegaCli 224

LSI MegaRAID PowerConsole 222

LSI MegaRAID SAS SNMP Agent 223

LSI RAID controller 220, 221

LSI/Mylex GAM Server 225

LsiLogic MegaRAID SAS 223

LsiLogic MegaRAID SAS (Newer Controllers) 223

- M -Manage

Baselines 53

Key Performance Indicators 53

KPI 53Mechanism 58

MegaCli (LSI) managed RAID card 230

MegaCLI Managed Raid Controllers 230

MIB-2 Standard SNMP Agent

MIB-2 Standard SNMP Agent - NetworkInterfaces 231

MIB-2 Standard SNMP Agent - NetworkInterfaces - Linux 232

MIB-2 Standard SNMP Agent - NetworkInterfaces - Solaris 234

MIB-2 Standard SNMP Agent - NetworkInterfaces - Windows 233

Microsoft Fibre Channel Information tool 275

Missing Device Detection 37

Monitor Type 46

Monitoring 66

Basics 66


Connector 79

CPU 76

Devices 66, 76

Disk Controllers 73

Disks 66, 73

Enclosure 68

Environment 66, 69

Fans 69

Memory Modules 76

Missing Device 79

Network Interfaces 76

Physical Disks 73

Power Supplies 69

Processors 76

Structure 66

Temperatures 69

Voltages 69Motherboard Monitor 235

Mylex GAM Servers 225

- N -NEC

NEC ESMPRO Agent 237NetApp

NetApp Filer - SNMP Agent 236

- O -Operating System

HP-UX 187Operating Systems 13, 132, 141, 143, 185,243

HP OpenVMS 164, 165, 166, 167, 168,169, 170, 171, 231, 245

HP Tru64 164, 165, 166, 167, 168, 169,170, 171, 231

HP-UX 180, 181, 182, 183, 184, 231, 245

IBM AIX 188, 189, 190, 191, 192, 193,214, 245

Linux 129, 130, 131, 144, 145, 146, 150,155, 156, 162, 164, 165, 166, 167, 168, 169,170, 172, 179, 196, 198, 200, 202, 204, 215,217, 219, 220, 222, 223, 225, 226, 227, 228,230, 232, 237, 238, 245, 246, 270, 271, 272,273

Microsoft Windows 146, 155, 156, 162,164, 165, 166, 167, 168, 169, 170, 174, 178,179, 195, 197, 199, 202, 203, 205, 209, 210,211, 215, 218, 219, 220, 221, 222, 223, 224,225, 233, 235, 237, 238, 245, 247, 274, 275,276

Network 231

Storage Device 133, 136, 140, 147, 151,175, 177, 206, 207, 211, 212, 213, 231, 236,241, 242, 244, 247, 248, 249, 251, 252

SUN 169

Sun Solaris 130, 150, 164, 165, 166, 167,168, 169, 170, 217, 218, 230, 234, 245, 250,255, 258, 259, 260, 261, 262, 264, 265, 266,267, 268, 269

Tru64 245

Index 286


Version 2.9.25

Operating Systems 13, 132, 141, 143, 185,243

Windows 129, 131, 144, 145OS command 65

Overview 58, 60

- P -Parameters 218, 271

Application Collection Status 87, 114

Available Path Count 103, 193, 227, 275

Available Path Information 227

Bandwidth Utilization 106

Battery Status 73, 99, 130, 155, 165, 224,230, 238

Charge 94, 274

Color 102

Connected Ethernet/Fiber Ports 96

Connected to Physical Address 106

Connection Type 106

connector 194, 262, 269

Controller Status 73, 99, 130, 137, 143,157, 164, 165, 170, 183, 186, 202, 203, 206,216, 241, 246, 247, 272

Corrected Error Count 76, 90

CorrectedErrorCount 98

Credentials 262

Current Speed 153, 154, 172, 174, 186

CurrentSpeed 98

Degrees Below Warning 96

Duplex Mode 106, 133, 189, 214

Energy Usage 96

Erro rCount 191

Error Count 73, 76, 83, 90, 102, 105, 109,111, 112, 132, 133, 140, 147, 150, 151, 155,156, 165, 169, 172, 183, 185, 189, 192, 211,212, 214, 216, 223, 225, 226, 229, 231, 232,233, 234, 242, 251, 264, 265, 268, 269, 275,276

Error Percent 76, 83, 106

Error Status 105

ErrorCount 180

Failure 131

Intrusion Status 68, 100, 145, 196, 197,198, 199, 200, 202

Link Speed 106, 132, 133, 134, 150, 151,159, 169, 172, 175, 177, 182, 183, 189, 214,216, 225, 228, 229, 231, 232, 233, 234, 240,275

Link Status 76, 83, 106, 132, 133, 134,141, 149, 150, 151, 165, 169, 172, 174, 175,177, 182, 183, 187, 189, 191, 214, 216, 225,228, 229, 231, 232, 233, 234, 236, 239, 240,244, 245, 247, 248, 264, 270, 273, 275, 276

LinkStatus 180

Locator 94, 95, 98, 99, 100, 102, 103,105, 106, 108, 109, 110, 111, 112, 113

Machine Status 87, 104

Memory Size 96

Modification 84

Mount Count 112, 147, 241, 242, 247,251, 252

Move Count 251

Move Count (Cumulative) 111

Needs Cleaning 112, 241, 242, 247

NeedsCleaning 249

Physical Address 106

Physical CPU Count 96

Power Consumption 68, 96, 133, 134,137, 141, 158, 163, 250, 270

Power State 95

Predicted Failure 73, 76, 83, 105, 109,129, 131, 137, 155, 164, 165, 166, 170, 177,216, 238, 243, 257, 262, 274

PredictedFailure 98, 256

Received Byte sRate 183

Received Bytes 106

Received Bytes Rate 106, 132, 133, 134,150, 151, 169, 172, 189, 214, 216, 225, 229,231, 232, 233, 234

Received Packet sRate 183

Received Packets Rate 132, 133, 134,150, 151, 169, 172, 189, 214, 225, 229, 231,232, 233, 234, 275

Reinitialization 90

Speed 69, 100, 132, 134, 137, 140, 145,149, 152, 156, 158, 177, 178, 187, 195, 196,197, 198, 199, 200, 202, 204, 205, 215, 216,217, 235, 242, 253, 254, 258, 259, 270, 273

Speed Percent 69, 100, 163, 194, 259,270, 273

Statis 131

Index 287


Version 2.9.25

Parameters 218, 271

Status 68, 69, 73, 76, 79, 83, 94, 95, 97,98, 99, 100, 102, 103, 105, 106, 108, 109,110, 111, 112, 113, 114, 129, 130, 131, 132,133, 134, 135, 136, 137, 140, 141, 143, 144,145, 146, 147, 148, 149, 150, 151, 152, 153,154, 155, 156, 157, 158, 159, 160, 162, 163,164, 165, 166, 167, 168, 169, 170, 171, 172,174, 175, 177, 178, 179, 180, 181, 182, 183,184, 185, 186, 187, 188, 189, 192, 193, 194,195, 196, 197, 198, 199, 200, 202, 203, 204,205, 206, 207, 208, 209, 210, 211, 212, 213,214, 215, 216, 217, 219, 220, 221, 222, 223,224, 225, 228, 229, 230, 231, 232, 233, 234,236, 237, 238, 239, 241, 242, 243, 244, 245,246, 247, 248, 249, 250, 251, 252, 253, 254,255, 256, 257, 258, 259, 260, 261, 262, 263,264, 265, 266, 267, 268, 269, 270, 272, 273,274, 275, 276

Status Information 137, 141, 143, 147,148, 149, 150, 153, 154, 157, 158, 159, 160,172, 175, 182, 186, 187, 189, 204, 205, 207,208, 211, 212, 213, 214, 225, 228, 239, 242,246, 247, 261, 269, 275

Temperature 69, 112, 132, 133, 134, 136,137, 140, 141, 145, 149, 152, 153, 154, 156,157, 158, 162, 163, 170, 172, 175, 177, 178,186, 194, 195, 196, 197, 198, 199, 200, 202,204, 205, 211, 213, 215, 217, 235, 236, 237,239, 242, 243, 244, 247, 248, 251, 253, 254,255, 256, 257, 258, 259, 260, 270, 273

Temperature Sensors 162, 197, 198, 204,205

Test Report 79, 97

Threshold 84

Time Left 274

Total Logical Disk Size 96

Total Physical Disk Size 96

Total Unallocated Space 96

Transmitted Byte Rate 106

Transmitted Bytes 106

Transmitted Bytes Rate 132, 133, 134,150, 151, 169, 172, 183, 189, 214, 216, 225,229, 231, 232, 233, 234

Transmitted Packet Rate 234

Transmitted Packets Rate 132, 133, 134,150, 151, 169, 172, 183, 189, 214, 225, 229,231, 232, 233, 275

Unallocated Space 136, 175, 177

Unmount Count 112

Usage Count 108, 251

Used Capacity 69, 110

Used Watts 163, 170

UsedTime 99

Voltage 69, 83, 113, 145, 149, 153, 154,156, 157, 175, 178, 190, 194, 195, 196, 197,198, 199, 200, 202, 204, 205, 211, 215, 217,235, 237, 242, 250, 253, 254, 255, 256, 257,258, 259, 260, 270, 273

Voltage Sensors 197, 198, 204, 205Patch

Install 41Performance manager 24

Platforms 162, 218

Cisco MDS9000 Series FC switches 133

Cisco UCS 134

Data Domain Storage Appliance 136

Dell 4000 Tape Library 147

Dell EqualLogic PS Series Disk Systems 140

Dell M1000E Chassis 137

Dell PowerEdge 139, 141, 143, 145, 146,226, 227, 243, 274, 275

Dell TL2000 Tape Library 147

Dell TL2000/4000 Tape Library 147

Disk Array 159, 207, 213, 236, 244

Fujitsu-Siemens BX Blade Servers 152

Fujitsu-Siemens PRIMERGY 129, 131,153, 154, 155, 156, 219, 220, 222, 223, 226,227, 238, 243, 274, 275

Generic Servers 215, 216

Hitachi BladeSymphony ChassisManagement Module 158

Hitachi HDS USP/VSP Storage Systems 160

HP 9000 175, 180, 181, 182, 183, 184,185, 187

HP BladeSystem - Telnet/SSH 163

HP EVA Storage Systems 177

HP Integrity 180, 181, 182, 183, 184,185, 187

HP NetServer 178, 179

HP ProLiant 164, 165, 166, 167, 168, 169,170, 171, 172, 174, 226, 227, 243, 274, 275

HP StorageWorks EVA - SSSU 177

HP StorageWorks MSA P2000 175

HP SuperDome 180, 181, 182, 183, 184,185, 187

IBM BladeCenter 194

IBM DSxxxx Disk Array 206

IBM eServer p5 188, 189, 190, 191, 192,193, 214

Index 288


Version 2.9.25

Platforms 162, 218

IBM Netfinity 195, 196, 197, 198, 199,200, 202, 203, 204, 205, 209, 210, 211, 246,247

IBM pSeries 188, 189, 190, 191, 192, 193,214

IBM RS/6000 188, 189, 190, 191, 192,193, 214

IBM Tape Library 3584 249

IBM TS3100 Tape Library 211, 212

IBM xSeries 195, 196, 197, 198, 199, 200,202, 203, 204, 205, 226, 227, 243, 246, 247,274, 275

Integrity 175

Linux Server with HBAs 225, 228

NEC Express5800 227, 237, 274, 275

Pure Storage FA Series 239

QLogic HBAs - ESX 240

Reference table 121

SAN Switches 132, 151, 248

SPARC Enterprise Mx000 250

Storage Libraries 247

StorageTek LSeries 251

StorageTek StreamLine 252

SUN Blade Chassis 254

SUN Blade with ILOM cards 256, 257

Sun Fire 226

Sun Fire (SPARC T1, T2) 267

Sun Fire (SPARC T1/T2) 258

Sun Fire (SPARC) 253, 255, 259, 260,261, 262, 264, 265, 266, 268, 269

Sun Fire (x64) 130, 217, 227, 243, 274,275

SuperDome 175

Supported 13

VMware ESX4i 271, 272

VMware ESXi 270, 273

WBEM 207

Windows 274

Windows servers 220, 221PM 24

Reinitialize 91Polling interval 30, 32, 35, 37

Power Supplies

Monitoring 69Prerequisites 58

Process

Collection 65

Detection 64

Discovery 65

Promise FastTrack 238

Properties 37

[Execution] Credentials 30

[Execution] Password 30

[Execution] Username 30

[Root] Credentials 30

[Root] Password 30

[Root] Username 30

[SNMP v3] Authentication Password 30,32, 35, 37

[SNMP v3] Authentication Protocol 30, 32,35, 37

[SNMP v3] Privacy Password 30, 32, 35,37

[SNMP v3] Privacy Protocol 30, 32, 35, 37

[SNMP v3] Username 30, 32, 35, 37

[SSH] Passphrase 30, 32, 37

[SSH] Private Key 30, 32, 37

[Telnet/SSH/IPMI] Password 37

[Telnet/SSH/IPMI] Username 37

[Telnet/SSH] Password 30

[Telnet/SSH] Username 30

[UCS] Password 37

[UCS] SSL Encryption 37

[UCS] Username 37

[WBEM] Credentials 30

[WBEM] Multi-Tier Authentication Server 30, 37

[WBEM] Namespace 30, 32, 37

[WBEM] Password 30, 37

[WBEM] Port 30, 32, 37

[WBEM] Transport Protocol 30, 32, 37

[WBEM] Username 30, 37

[WMI] Password 35

[WMI] Username 35

AWK timeout 115

Collection interval 30, 32, 35, 37

Credential Options 30

Debug Mode 30, 32, 35

Default system wattage 30, 32, 35

Disable Connectors 115

Error Count Auto-reset After 30, 32, 35

Force nAwk 115

Force SNMP Protocol Activation 115

Force SSH 115

Force Telnet 115

Force WMI Script 115

Hostname 30, 32, 35

Index 289


Version 2.9.25

Properties 37

In case of Status parameter value isUNKNOWN 30, 32

In case of Status parameter value isUNKNOWN... 35

IPMI Tiemout 115

LinkStatus auto-reset after 32, 35

Missing Device Detection 30, 32, 35

net.sentrysoftware.bpm.hardware.fan.speed 115

net.sentrysoftware.bpm.hardware.forcenawk 115

net.sentrysoftware.bpm.hardware.forceSSH 115

net.sentrysoftware.bpm.hardware.forceTelnet 115

net.sentrysoftware.bpm.hardware.forceWMIScript 115

net.sentrysoftware.bpm.hardware.ipmiTimeout.default 115

net.sentrysoftware.bpm.hardware.powersupply.usedcapacity 115

net.sentrysoftware.bpm.hardware.preSelectedConnectors.hostname 115

net.sentrysoftware.bpm.hardware.ssh.port 115

net.sentrysoftware.bpm.hardware.sshTimeout.default 115

net.sentrysoftware.bpm.hardware.sshTimeout.hdf 115

net.sentrysoftware.bpm.hardware.telnet.port 115

net.sentrysoftware.bpm.hardware.telnetTimeout.default 115

net.sentrysoftware.bpm.hardware.telnetTimeout.hdf 115

net.sentrysoftware.bpm.hardware.temp.temperature 115

net.sentrysoftware.bpm.hardware.volt.voltage 115

net.sentrysoftware.bpm.hardware.wbemActivation 115

net.sentrysoftware.bpm.hardware.wbemNamespace 115

net.sentrysoftware.bpm.hardware.wbemTimeout.default 115

net.sentrysoftware.bpm.hardware.wmiNamespace 115

net.sentrysoftware.bpm.hardware.wmiTimeout.default 115

Perform Garbage Collector 115

Pre-Selected Connectors 115

Reflect Fan Speed value 115

Reflect PowerSupply UsedCapacity value 115

Reflect Temperature value 115

Reflect Voltage value 115

Reflect AvailablePathCount value 115

SNMP Community 30, 32, 35

SNMP Port 32, 35, 115

SNMP version 30, 32, 35

SSH Port 115

SSH Timeout 115

Telnet Port 115

Telnet timeout 115

Telnet/SSH Password 32

Telnet/SSH Username 32

UCS timeout 115

WBEM Activation 115

WBEM Credentials 32, 35

WBEM namespace 115

WBEM Password 32, 35

WBEM timeout 115

WBEM Username 32, 35

WMI namespace 115

WMI Script 115

WMI timeout 115

- Q -Quantum (ADIC) Based Tape Libraries 241

Quantum (ADIC) Enterprise Level Tape Libraries 242

- R -RAID 131, 144, 146

Reference guide 94

Reinitialize

PM 91Remote Service Monitor 21, 22

Remote Service Monitor program 23

Report 145

Reporting

Energy Usage 81

Ethernet/Fiber Port Traffic 81Requirements 61

Hardware Agent 13

Management Elements 13

Index 290


Version 2.9.25

Requirements 61

Operating System 13RSM 21, 22, 23

- S -S.M.A.R.T. technology 73

Siemens 152, 153, 154

SmartMonTools 243

SMCLI 206

SMI-S

SMI-S Compliant Disk Arrays 244

SMI-S Compliant HBAs 245

SMI-S Compliant RAID Controller - Windows 247

SMI-S Compliant SAN Switches 248

SMI-S Compliant Storage Libraries 247SNIA

SNIA Compliant Tape Libraries 249SNMP 129, 131, 132, 136, 143, 144, 145,146, 147, 151, 152, 155, 156, 158, 160, 162,164, 165, 166, 167, 168, 169, 170, 171, 179,194, 209, 210, 211, 212, 215, 216, 219, 220,222, 223, 231, 232, 233, 234, 236, 237, 238,241, 249, 251, 252, 254

SNMP Community 37

SNMP Port 37

SNMP version 37

Solaris 253, 255, 258, 259, 260, 261, 262,264, 265, 266, 267, 268, 269

Requirements 30SPARC

SPARC Enterprise Mx000 (XSCF) 250SSH 239

SSSU 177

Status

Power Consumption 139

Speed 139

Temperature 139Storage 131

Requirements 32StorageTek

StorageTek LSeries Tape Library 251

StorageTek StreamLine Tape Library 252Sudo 180

Configuration 30, 32, 35, 37

Requirements 35SUN

Sun Advanced Lights–Out Management(ALOM) card 253

Sun Advanced Lights-Out ManagementALOM card 253

SUN Blade Chassis 254

SUN Blade Chassis CMM SNMP Agent 254

SUN Blade SP SNMP Agent 256

Sun Explorer 258

Sun Fire (SPARC T1/T2) 258

Sun Fire (SPARC) 253

Sun Fire F12K/F15K/F20K/F25K SMS 255

SUN ILOM (SNMP) 256

SUN ILOM (SSH) 257

Sun Solaris 253, 255, 258, 259, 260, 261,262, 264, 265, 266, 267, 268, 269

Sun Solaris - Disks 268

Sun Solaris - Environment prtpicl 259

Sun Solaris - Fault Manager (Memory) 261

Sun Solaris - Network 264

Sun Solaris - Non-Sun Disks 265

Sun Solaris - Processors psrinfo 266Sun Solaris 263

System commands 150

Systems

AIX 30

HP-UX 30

Linux 21, 30

Solaris 30

Storage 32

Tru64 30

UNIX 21

Windows 21, 35

- T -Telnet/SSH 133, 137, 139, 163, 175, 213,253, 257

Temperature 174

Monitoring 69Threshold 26, 40, 69, 83, 114

Modification 84Troubleshooting 86, 88, 90


Disk Controller 92

No information displayed 87

VMI connection 92Tru64

Requirements 30

Index 291


Version 2.9.25

- U -UCS 26

Utility

Emulex's hbacmd 225

Linux multipath 227

QLogic's SCLI 228

Sudo 227, 260, 261, 262, 264, 265, 266,268, 269

- V -VMware

VMware ESX4i 271, 272

VMware ESXi 3.x 270

VMware ESXi 4.x 273Voltage

Monitoring 69

- W -WBEM 148, 153, 159, 172, 196, 198, 200,202, 204, 240, 244, 245, 246, 247, 248, 270,271, 272, 273

WBEM query 65

Web 131

Windows 35

WMI 154, 174, 178, 195, 197, 199, 202, 203,205, 247, 274, 275

Dell PowerEdge 276

Fujitsu-Siemens PRIMERGY 276

HP ProLiant 276

IBM xSeries 276

NEC Express5800 276

Platforms 276

Sun Fire (x64) 276WMI protocol 92

About BMC® SoftwareBMC Software helps leading companies around the world put technology at theforefront of business transformation, improving the delivery and consumption of digitalservices. From mainframe to cloud to mobile, BMC delivers innovative IT managementsolutions that have enabled more than 20,000 customers to leverage complextechnology into extraordinary business performance—increasing their agility andexceeding anything they previously thought possible. For more information about BMC

Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software, providescomprehensive multi-platform monitoring solutions that enable management of thehardware and software aspects of all servers and SANs and covering up to 100 % ofcustom applications within the BMC ProactiveNet Performance Managementenvironment. Sentry Software also develops adapters for BMC Atrium Orchestrator thatenables IT administrators to automate the execution of common requests and tasksthat occur in the daily course of IT operations. Combined with BMC’s servers andnetwork automation tools, the adapters allow IT administrators to implementprovisioning and decommissioning workflows that cover all layers of their ITinfrastructure. Finally, Sentry Software designs connectors that bring storage capacitymetrics into BMC Capacity Optimization to ensure IT administrators that their storageinfrastructure is properly sized for their current and future needs.The combination of its monitoring, automation, and capacity optimization capabilitiesfor IT infrastructures, makes Sentry Software a key-partner in the storage managementmarketplace. For more information about Sentry Software, please visitwww.sentrysoftware.com.

http://www.sentrysoftware.com

isabelle

Text Box

462784

isabelle

Text Box

bmc® performance manager express for hardware x.x 1.9.60... · user documentation january 2015 bmc...

Documents