Sentry Software KM for PATROL Hardware Sentry User documentation
Mainos
Mainos
Hardware Sentry KM for
PATROL
Version 1.8.01
User Documentation
January 2013
Hardware Sentry KM for PATROL
Version 1.8.01
Contacting BMC Software
You can access the BMC Software Web site at http://www.bmc.com/. From this Web site, you can obtain information about the company, its products, corporate offices, special events, and career opportunities.
United States and Canada Outside United States and Canada
Address
BMC Software, Inc.
2101 CityWest Blvd. Houston TX 77042-
2827
Telephone
713 918 8800 or
800 841 2031
Fax
713 918 8000
Telephone
(01) 713 918 8800
Fax
(01) 713 918 8000
Copyright 2006 BMC Software, Inc. or licensors, as an unpublished work. All rights reserved.
BMC Software, the BMC Software logos, and all other BMC Software product or service names are registered trademarks or trademarks of BMC Software, Inc.
IBM is a registered trademark of International Business Machines Corporation.
DB2 is a registered trademark of International Business Machines Corporation.
Oracle is a registered trademark, and the Oracle product names are registered trademarks or trademarks of Oracle Corporation.
All other trademarks belong to their respective companies.
BMC Software considers information included in this documentation to be proprietary and confidential.
Your use of this information is subject to the terms and conditions of the applicable End User License
Agreement for the product and the proprietary and restricted rights notices included in this documentation.
Restricted Rights Legend
U.S. Government Restricted Rights to Computer Software. UNPUBLISHED -- RIGHTS RESERVED UNDER
THE COPYRIGHT LAWS OF THE UNITED STATES. Use, duplication, or disclosure of any data and computer software by the U.S. Government is subject to restrictions, as applicable, set forth in FAR
Section 52.227-14, DFARS 252.227-7013, DFARS 252.227-7014, DFARS 252.227-7015, and DFARS
252.227-7025, as amended from time to time. Contractor/Manufacturer is BMC Software, Inc., 2101
CityWest Blvd., Houston, TX 77042-2827, USA. Any contract notices should be sent to this address.
2
Hardware Sentry KM for PATROL
Version 1.8.01
You can obtain technical support by using the Support page on the BMC Software Web site or by contacting Customer Support by telephone or e-mail. To expedite your inquiry, please see "Before
Contacting BMC Software."
Support Web Site
You can obtain technical support from BMC Software 24 hours a day, 7 days a week at http:// www.bmc.com/support_home . From this Web site, you can
Read overviews about support services and programs that BMC Software offers:
Find the most current information about BMC Software products
Search a database for problems similar to yours and possible solutions
Order or download product documentation
Report a problem or ask a question
Subscribe to receive e-mail notices when new product versions are released
Find worldwide BMC Software support center locations and contact information, including e-mail addresses, fax numbers, and telephone numbers
Support by Telephone or E-mail
In the United States and Canada, if you need technical support and do not have access to the Web, call
800 537 1813. Outside the United States and Canada, please contact your local support center for assistance. To find telephone and email contact information for the BMC Software support center that services your location, refer to the Contact Customer Support section of the Support page on the BMC
Software Web site at http://www.bmc.com/support_home .
Before Contacting BMC Software
Before you contact BMC Software, have the following information available so that Customer Support can begin working on your problem immediately:
3
Hardware Sentry KM for PATROL
Hardware Sentry KM for PATROL
Version 1.8.01
Release Notes for v1.8.01
What's New
Hardware Sentry KM for PATROL is now officially supported on Windows Server 2012.
The KM now supports multi-tier authentication schemes for WBEM connections, that is connections to a VMware ESXi host with an authentication through VMware vCenter, for example.
It is now possible to disable the validation tests of the JRE used by the KM to run Java code and therefore force the KM to use a non-Sun or non-Oracle JRE. To disable the validation test, you need to set the /SENTRY/MATSYA/disableJRECheck variable in the PATROL Agent's configuration accordingly. This is notably useful on IBM AIX and HP-UX systems where Sun/Oracle’s JRE is not available. Warning: Apache JRE is not supported. Note: A valid JRE is required by the KM only to perform certain tasks, like WBEM queries and remote SSH connections.
Missing Parameters: It is now possible to modify the number of times Missing parameters thresholds can be breached before an alert is triggered. The default N times value for the “Missing” parameter can be customized by setting the related configuration varialble, that is missingMaxOCC.
The ZeroBufferCreditPercent parameter was added to the
MS_HW_NETWORK application class
to report the percentage of zero buffer credits over the last polling interval for FC ports.
New Configuration Variable: findW bemNamespaceT imeout defines the number of seconds after which a remote Hardware Sentry KM for PATROL stops trying to get a server namespace via WBEM.
Default value is set to 1200s.
Dell Servers with iDRAC7 Management Cards: The KM is now able to monitor Dell PowerEdge
Servers out of band via its iDRAC management card.
Brocade SAN Switches: The connector now supports the monitoring of WWN Cards.
HP-UX Servers via WBEM: The connector now enables the monitoring of newer HP Integrity i2 servers running HP-UX: HP Integrity BL860c i2, BL870c i2 & BL890c i2 Server Blades, rx2800 i2 and
HP Integrity Superdome 2).
Sun ILOM SSH Connector for Blades: The connector now supports the monitoring of Discrete
T emperature and V oltage sensors.
Changes and Enhancements
It is now possible to fully manage Hardware Sentry alert thresholds through BMC PATROL standard administration tools (Event Management KM, PCM, etc.). Hardware Sentry KM for PATROL no longer resets the alert thresholds automatically for all application classes at each discovery. The default alert thresholds are now set only once when the KM first runs.
The overall performance and scalability of the KM has been dramatically improved so that the product is now able to monitor several hundreds remote VMware ESX hosts from one Agent.
The overall performance of the KM discovery process has been greatly improved. The number
PATROL Agent configuration changes has been drastically reduced leading to lesser I/O resource consumption.
The KM no longer automatically switches from one threshold mechanism to another. Threshold
mechanism can be selected through the Selecting the Threshold Mechanism KM Command.
Data Domain Storage Systems Monitoring: Temperature thresholds are now set for Ambient and CPU sensors.
Monitoring IBM DS3000, DS4000, DS5000 Series: Disk Drawers are now fully monitored.
The default threshold for the DegreesBelowWarning parameter has been removed to avoid duplicate notification with the T emperature parameter threshold.
5
Release Notes for v1.8.01
Hardware Sentry KM for PATROL
Version 1.8.01
The Debug mode was modified to ensure full compatibility with BPPM 9.x.
EMC Storage Systems:
Controllers and storage processors are now reported as Controllers under the Other Devices category.
The ID of the storage processors and controllers is no longer displayed twice in the label of the corresponding instance.
The speed of each port is now monitored with the
LinkS peed parameter of the
For all fiber-connector systems (storage systems, FC ports, HBAs and SAN switches), the connection type of the port is no longer detailed in the instance name. Only the main acronym is being used: "FC Port N", "FC Port E", etc.
NetApp Filers - NVRam Battery Monitoring: The NVRam Battery Status is now supported by the connector.
Hardware Sentry MIB-2 connector now supports 10 G port speed.
On Windows systems, the discovery of
Physical Disks has been improved to reduce the number of
WMI queries.
On Windows systems, the number displayed in the icon label to identify the physical disk now matches with Windows' administration tools.
Release Notes for v1.8.01
6
Hardware Sentry KM for PATROL
Version 1.8.01
Fixed Issues
Version 1.8.01 of Hardware Sentry KM for PATROL fixes issues relating to the monitoring of:
Sun Sparc Servers: The connector now takes into consideration the Exponent of a T emperature sensor.
IBM DS Storage Systems I345 Battery: The battery status of Battery maintenance charging was not recognized as an OK status.
NetApp Filers: The identifier of the Physical Disk ID/ Disk S helf W W N was changed to prevent false missing alerts to be generated for Physical Disks, T emperature, Fans and Pow er S upplies. The original identifier can now be found in the Infobox under Identifying Information.
IBM Director 6.2.1 Monitoring: The detection criteria query "SELECT Name FROM
__NAMESPACE" has been removed to prevent the connector to fail unnecessarily.
IBM Director 6.3 or later: Since temperature and voltage thresholds are stored in a different property depending on the version of the IBM Director Agent used, temperature and voltage thresholds were missing. This version of the KM takes into consideration both pre 6.3 and 6.3
threshold properties.
Sun Servers running Solaris: When a Physical Disk failed or was removed and reported a size of zero bytes, the monitoring of all the Physical Disks failed.
Cisco Telnet Switches:
The connector will no longer add a unique identifier to Chassis Fans if they already have one.
The connector adds the hostname or the hostname information to the Connected to Physical
A ddress property of the FC Port.
Data Domain Storage Systems: Devices with blank IDs were being created causing false missing alerts.
IBM DS3000, DS4000, DS5000 Storage Systems:
The Physical Disk status of Replaced was not interpreted correctly.
Pow er S upply Fan failures were reported as unknown failures and did not generate alarms. The connector will now alarm on Pow er S upply Fan failures and warn on any unknown failures.
VIO servers:
'$' characters were not protected when running OS commands in a Telnet or SSH session, preventing the monitoring of VIO servers from a UNIX server.
The connector has been modified to test for an unrestricted shell and if found run all commands with their full path. If a restricted shell is found, commands will continue to be run with no path specified. AIX Connectors not designed for VIO Servers will also now be deactivated.
Servers equipped with HBA Cards: Hardware Sentry KM for PATROL has been modified to prevent the creation of duplicate instances of the same HBA card when the KM is in automatic detection mode.
Recent Oracle (SUN) x86 Servers Using IPMI:
The KM now recognizes the manufacturer identifier of Oracle and processes SUN/Oracle specific sensors properly.
Oracle/Sun specific power supply sensors (PSx/VINOK and PSx/PWROK) are now correctly interpreted.
The debugging information has been improved.
Release Notes for v1.8.01
7
Hardware Sentry KM for PATROL
Version 1.8.01
Disks on VMware ESX servers: The KM now discovers and monitors
Physical Disks even if when there is no presence sensor for the
Physical Disks.
Sun Solaris - Environment (prtdiag, lom): Pow er S upply and Memory Module failures were erroneously reported as Unknow n. The connector has been modified to report these specific failures as A larm.
HP StorageWorks MSA 2000 & P2000: Discovery stopped when the string "#" was found in the xml command output; this string was identified as the prompt, which caused the capture of the full output of the command to stop.
EMC Storage Systems: FC and Ethernet ports that were not configured or not in use were inaccurately reported as Failed (S topped) with a status in A larm. Such ports are now reported with an OK status.
HP EVA Disk Arrays: The detection criteria for the connector have been modified to recognize the output of the P6000 version of SSSU. Also, passwords with exclamation marks (!) no longer cause the batch file to fail.
Ethernet ports on Cisco Nexus switches or Cisco MDS switches embedded in a Blade
Chassis: The timeout issue occurring with SSH/Telnet connections has been fixed.
Brocade, McData and Fibre Alliance Switches monitored using SNMP: Depending on the model, firmware versions and manufacturer of SAN switches, different values have been used to convert from Kb/s to Mb/s (100, 125 or 106.25). The KM now detects which value has been used and uses it to calculate the link speed of the port and its bandwidth utilization.
Sun ILOM SSH: Physical Disks were not monitored if State sensor was not available.
HP Proliant Systems using HP's NIC Teaming: The monitoring of the physical cards in a NIC teaming configuration is now done through the operating system instrumentation. The HP Insight
Management Agent - Network Connector now monitors the status of the logical network cards only.
Miscellaneous
The KM now properly handles white spaces in the %PATROL_HOME% environment variable when executing nawk.exe on PATROL Agent version 3.9.00 and higher.
Some parameters could be activated by the discovery even though no data was available, notably the Pow er Consumption parameter.
On Windows systems, remote LUNs mounted by an HBA were incorrectly discovered as internal
Physical Disks.
Since the introduction of
thresholds in v1.8.00, devices with an identifier containing over 100 characters could have their parameters deactivated by the Event Management
KM. This problem is fixed with version 1.8.01.
Some versions of the S un Blade Chassis firmware have incomplete identifiers for Pow er S upplies that prevented these components to be properly discovered and monitored.
On older HP servers that are not on VMWare's ESX HCL, environmental sensors were not found by the HP agent for ESX, but could be found using ESX's inbuilt hardware monitoring system. From now on, if sensors are not found by the HP connector the PM will revert to using the VMWare connector.
Alert on missing parameters are now properly closed and the corresponding events are triggered accordingly.
Known Issues
The PATROL Agent must be executed on a server where the regional settings are set to 'English
(United-States)' in order to avoid collected values to be rounded up and therefore lead to inaccurate calculation or untimely alerts.
Release Notes for v1.8.01
8
Hardware Sentry KM for PATROL
Version 1.8.01
Installation Guide
This chapter describes the installation procedure for Hardware Sentry on any PATROL component
(Agents, Consoles, Console Server, etc.). As the setup is based on the BMC Software Installation Utility, this procedure applies to all operating systems supported by Hardware Sentry. Although not covered by this section, the installation through the Distribution Server is fully supported. Please refer to the
Distribution Server documentation for a detailed description of the deployment procedure.
Ensure that you have already installed the platform-specific hardware agents on the systems, before you install the KM.
Platforms & Requirements
Requirements for managed systems
The BMC Software PATROL Agent must be installed, and its version should be at least 3.4.11. For
Hardware Sentry to collect information from a managed system, it requires specific instrumentation agents or system management tools to be present on the managed system.
Servers
Typical Platform Operating
System
Windows Cisco UCS B-Series, C-
Series
Cisco UCS B-Series, C-
Series
Dell PowerEdge
Dell PowerEdge
Fujitsu-Siemens
PRIMERGY
Linux
Windows
Linux
Windows
Fujitsu-Siemens
PRIMERGY
Linux
Instrumentation Prerequisites Technology Used
None IPMI, WMI ipmitool IPMI, command lines
Dell OpenManage Server Administrator
Dell OpenManage Server Administrator
SNMP
SNMP
Fujitsu-Siemens Serverview
Fujitsu-Siemens ServerView RAID
Agent / Promise FastTrack SNMP Agent /
LSI GAM Server / LSI MegaRAID SAS
SNMP Agent / LSI MegaRAID
PowerConsole / Mylex GAM Server
(depending on the server, follow Fujitsu-
Siemens recommendations)
SNMP
Fujitsu-Siemens Serverview SNMP
9
Installation Guide
Hardware Sentry KM for PATROL
Version 1.8.01
HP 9000
HP AlphaServer
HP AlphaServer
HP Integrity
HP Integrity
HP Integrity
HP ProLiant
HP ProLiant
HP ProLiant
Linux
Solaris
HP NetServer Windows
HP SuperDome (Itanium) Windows
HP SuperDome (Itanium) Linux
HP SuperDome (Itanium) HP-UX
HP SuperDome (PA-
RISC)
HP-UX
HP-UX
Tru64
OpenVMS
Windows
Linux
HP-UX
Windows
IBM pSeries, IBM eServer IBM AIX
IBM VIO Server IBM AIX
Windows IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
Linux
NEC Express5800
NEC Express5800
Sun Fire (SPARC)
Sun Fire (SPARC T1, T2)
– pre-2009 firmware
Windows
Linux
Solaris
Solaris
Sun Fire (SPARC T1, T2)
– 2009 and newer firmware
Sun Fire F12K, F15K,
F20K, F25K
Sun Fire Mx000
Solaris
Solaris
Solaris
Sun Fire (X64) Solaris
Typical Platform Operating
System
Instrumentation Prerequisites Technology Used
Fujitsu-Siemens ServerView RAID
Agent / Promise FastTrack SNMP Agent /
LSI GAM Server / LSI MegaRAID SAS
SNMP Agent / LSI MegaRAID
PowerConsole / Mylex GAM Server
(depending on the server, follow Fujitsu-
Siemens recommendations)
GSP card
HP Insight Management Agent
Command lines, Telnet/SSH
SNMP
HP Insight Management Agent
HP Insight Management Agent
HP Insight Management Agent
MP card
HP Insight Management Agent
SNMP
SNMP
SNMP
Command lines, Telnet/SSH
SNMP or WMI
HP Insight Management Agent
HP Insight Management Agent
HP TopTools
HP Insight Management Agent
HP Insight Management Agent
MP/GSP card
GSP card
SNMP
SNMP
SNMP, WMI
SNMP
SNMP
Command lines, Telnet/SSH
Command lines, Telnet/SSH
None
None
IBM Director Agent
IBM Director Agent
Command lines
SSH
WMI
WBEM, command lines
NEC ESMPRO Agent
NEC ESMPRO Agent
None
Access to the Sun Advanced Lights-Out
Management (ALOM) card over the network
None
SNMP
SNMP
Command lines
Command lines, SSH to the
ALOM card
Command lines
Access to the SMS utilities installed on the System Controller (SC)
Access to the eXtended System Control
Facility (XSCF) ipmitool, lsiutil
SSH to the System
Controller
SSH to the XSCF
Command lines
Installation Guide
10
Hardware Sentry KM for PATROL
Version 1.8.01
Typical Platform
Sun Fire (X64)
Sun Fire (X64)
Operating
System
Linux
Windows
Instrumentation Prerequisites Technology Used
ipmitool, lsiutil lsiutil
Command lines
IPMI (WMI), command lines
Cross-Platform Technology
Technology
Emulex HBA
Emulex HBA
Emulex HBA
QLogic HBA
QLogic HBA
QLogic HBA
VMware ESX/ESXi
Operating
System
Windows
Linux
Solaris
Windows
Linux
Solaris
VMware ESX/ESXi
Instrumentation Prerequisites
None hbacmd hbacmd
None scli scli
Access to the CIM server
Technology Used
WMI
Command lines
Command lines
WMI
Command lines
Command lines
WBEM
Blade Chassis
Chassis Instrumentation Prerequisites Technology Used
Cisco UCS Interconnect Chassis Cisco UCS Manager on the Cisco UCS Interconnect
Switch
XML API (HTTP)
Dell Modular Chassis (blades)
Fujitsu-Siemens BX Blade
Chassis
DRAC/MC
Fujitsu-Siemens Management Blade
Telnet/SSH
SNMP
HP c-Class BladeSystem
HP p-Class BladeSystem
Hitachi BladeSymphony
IBM BladeCenter
Sun Blade Modular Chassis
Storage Devices
Typical Platform
3PAR InServ
Brocade SAN Switch
Cisco SAN Switch
1
Compellent
Dell EquaLogic PS Series
HP BladeSystem On-Board Administrator
HP Insight Management Agent
Hitachi BladeSymphony Management Module
IBM BladeCenter Management Module
SNMP
SNMP
SNMP
SNMP
Access to the Chassis Management Module (CMM) SNMP
Instrumentation Prerequisites
3PAR SMI-S Provider
SNMP Enabled
None
Compellent Enterprise Manager
None
Technology Used
WBEM
SNMP
Telnet/SSH
WBEM
SNMP
Installation Guide
11
Hardware Sentry KM for PATROL
Version 1.8.01
Typical Platform Instrumentation Prerequisites Technology Used
EMC Clariion
EMC Symmetrix
EMC Symmetrix V-Max
EMC VNX series
Fujitsu Eternus
Hitachi AMS
Hitachi USP-V
Hitachi VSP
HP StorageWorks EVA
EMC SMI-S Provider
EMC SMI-S Provider
EMC SMI-S Provider
EMC SMI-S Provider
ETERNUS SMI-S Agent
Hitachi Device Manager
Hitachi Device Manager
Hitachi Device Manager
HP CommandView EVA
WBEM
WBEM
WBEM
WBEM
WBEM
WBEM
WBEM
WBEM
Command lines
HP StorageWorks XP HP CommandView XP (or Hitachi Device Manager) WBEM
HP StorageWorks P9000 Series HP CommandView WBEM
IBM DS Storage Manager (SMcli) Command lines IBM DS 3000, 4000, 5000
Series
IBM DS 6000, 8000 Series
IBM 3584 Tape Library
IBM DS Storage Manager
None
WBEM
SNMP
IBM XiV
McData SAN Switch
NetApp
Quantum Tape Library
IBM XIV Storage System SMI-S Agent
None
None
None
StorageTek LSeries None
StorageTek StreamLine (SL) None
1
C isco network switches are not supported by Hardware Sentry KM for PA TROL.
WBEM
SNMP
SNMP
SNMP
SNMP
SNMP
Generally server manufacturers furnish instrumentation agents and system tools for free and these are either found on the CD-ROM provided with the server or, on the manufacturer’s web site. Unless mentioned otherwise, the manufacturer’s instrumentation agent must be installed on the monitored server for Hardware Sentry to function properly. For details on how to install the required instrumentation agent on the systems, please refer to the platform-specific guides available on the Hardware Sentry page of the Sentry Software website.
in the Reference Guide and click the "C onnector Name" applicable to y our sy stem/ty pical platform.
Requirements for console systems
The minimum version supported of the BMC Software PATROL Console is 3.4.11. It is recommended to update the other console components (Console Server, PATROL Central, etc.) with the latest version available at the BMC Software EPD site .
Installation Guide
12
Hardware Sentry KM for PATROL
Version 1.8.01
Migrating from Previous Versions
On PATROL Agents
No specific migration is required. If a previous version of Hardware Sentry has been installed, it will be overwritten by the latest version. Upon start up, Hardware Sentry will take the necessary action to complete the migration. If needed, it will migrate configuration variables.
On PATROL Consoles (Classic)
1.
Install the latest version of Hardware Sentry on the PATROL Consoles. This version will let you connect seamlessly to PATROL Agents on which a different version of Hardware Sentry is installed.
Make sure the version installed on the PATROL Console is the same or higher than the one present on the PATROL Agent.
2.
Load the MS_HARDWARE_SENTRY1.kml file in the PATROL Console to update the console profile and include the Hardware Sentry classes.
Avoid the use of the "Developer" connection type in the PATROL Console. Never use the "Commit
KMs" feature of the PATROL Console, especially when you deal with several versions of the same KM in your environment.
On Console Server, PATROL Central - Web Edition
As Console Server and PATROL Central can manage several versions of the same KM, you can install different versions of Hardware Sentry side-by-side on the same Console Server. Console Server automatically uses the appropriate version of the KM depending on what is running on the displayed agent.
After installing the latest version of Hardware Sentry, load the MS_HARDWARE_SENTRY1.kml file to update the console profile and include the Hardware Sentry classes.
Installation Guide
13
Hardware Sentry KM for PATROL
Version 1.8.01
Packages
Hardware Sentry Packages
The Hardware Sentry packages are available on: the BMC Software EPD Web site , in the folder Sentry Software Monitoring and Analytics for
BMC ProactiveNet Performance Management x.x.xx > Sentry Hardware Monitoring
version x.x.xx > Hardware Sentry KM for PATROL version x.x.xx or directly under BMC
Performance Manager for Hardware by Sentry Software according to the license you have acquired.
the Sentry Software Web site .
There are three packages, each of which can be used to install the KM on every PATROL component
(Agent, Console, etc.) according to the platform you are using.
For Windows systems: mshw_WINDOWS_<version>.zip
For UNIX and Linux systems: mshw_UNIX_<version>.tar
For OpenVMS systems: mshw_VMS_<version>.tar
Java Runtime Environment Package
Java Runtime Environment version 1.5.00 or higher is required in some cases for the KM to operate properly (notably when the KM needs to make WBEM or SSH connections).
A package of a suitable Java Runtime Environment, designed for use with the BMC Software Installation
Utility, is made available to download on: the BMC Software EPD Web site , in the folder Sentry Software Monitoring and Analytics for
BMC ProactiveNet Performance Management x.x.xx > Sentry Hardware Monitoring
version x.x.xx > Hardware Sentry KM for PATROL version x.x.xx or directly under BMC
Performance Manager for Hardware by Sentry Software according to the license you have acquired.
the Sentry Software Web site .
A pa che J RE is not supporte d.
You can optionally install this package along with the Hardware Sentry KM package. The KM will be able to lev erage either this instance of the Jav a Runtime Env ironment or another installed separately on the sy stem.
Installation Guide
14
Hardware Sentry KM for PATROL
Version 1.8.01
Extracting the Setup Files
On Windows
The packages for Windows are to be extracted in the consecutive order:
1. First, unzip the BMC Installation Utility: ins_WINDOWS_<version>.zip
2. Next, unzip the Hardware Sentry KM package in the same folder:
mshw_WINDOWS_<version>.zip
3. Then, unzip the senjre_<version>_WINDOWS.zip package if you need to install a Java Runtime
Environment program
The content of the packages merges into a subfolder named bmc_products.
A pa che J RE is not supporte d.
W indows may ask for y our confirmation to ov erwrite files and folders. This is normal behav ior and y ou can accept all ov erwrite confirmation requests.
On UNIX/Linux
The packages for UNIX/Linux are to be extracted with the tar utility:
1. First, untar the BMC Installation Utility: tar xvf ins_ALL_<version>.tar
2. Next, untar the Hardware Sentry package named: tar xvf mshw_UNIX_<version>.tar
The files are extracted into a sub-directory named bmc_products.
Installation Guide
15
Hardware Sentry KM for PATROL
Version 1.8.01
Getting the BMC Software Installation Utility
In order to install Hardware Sentry, you need the latest version of the BMC Software Installation Utility.
You can download the latest Installation Utility from the BMC Software EPD (Electronic Product download) from: https://webapps.bmc.com/signon/content/logon.jsp
on the BMC Software Website, or from the Hardware Sentry download page on the Sentry Software Website
Choose the appropriate package depending on the platform you plan to install Hardware Sentry:
For UNIX/Linux systems: ins_ALL_<version>.tar
For Windows systems: ins_WINDOWS_<version>.zip
The packages are valid for all the PATROL components: Agent, Console, Console Server, etc.
Place the Installation Utility package in the same folder as the Hardware Sentry packages.
Installation Guide
16
Hardware Sentry KM for PATROL
Version 1.8.01
Installation Procedure
Installing Hardware Sentry is an automated process managed by a wizard. The wizard goes through the necessary steps to install Hardware Sentry and all files associated with it. You are simply prompt for the product's folder location and the product/components to install. Browse to the bmc_products folder where the files have been
extracted (both Hardware Sentry and the Common Installer).
On Windows: Launch the setup.exe program.
On UNIX: Launch the setup.sh script
On some versions of Windows, you may get this security alert dialog: Windows detected that the BMC
Software Installation Utility is listening on the 50001 port.
To install Hardware Sentry KM for PATROL
1.
Allow the perl.exe program to listen on this port: Click Allow access.
Insta lla tion W iza rd - Ste p 1: W indows Se curity A le rt
Installation Guide
17
Hardware Sentry KM for PATROL
Version 1.8.01
2.
The welcome screen of the installer appears. Click Next to continue.
Insta lla tion W iza rd - Ste p 2: W e lcom e
Installation Guide
18
Hardware Sentry KM for PATROL
Version 1.8.01
3.
Read the license agreement, click the Accept option and then click Next to continue.
Insta lla tion W iza rd - Ste p 3: Re v ie wing Lice nse A gre e m e nt
Installation Guide
19
Hardware Sentry KM for PATROL
Version 1.8.01
4.
Select Install products on this computer now and click Next to continue.
Insta lla tion W iza rd - Ste p 4: Se le cting Insta lla tion Options
Installation Guide
20
Hardware Sentry KM for PATROL
Version 1.8.01
5.
Specify the BMC Software products folder. See the BMC Software documentation for more information about the BMC Software products folder. Click Next to continue.
Insta lla tion W iza rd - Ste p 5: Se le cting the Insta lla tion Dire ctory
Installation Guide
21
Hardware Sentry KM for PATROL
Version 1.8.01
6.
Select Default. Installing Hardware Sentry does not require any customization. Click Next to continue.
Insta lla tion W iza rd - Ste p 6: Se le cting a n Insta lla tion T y pe
Installation Guide
22
Hardware Sentry KM for PATROL
Version 1.8.01
7.
Select:
Managed System to install Hardware Sentry on a PATROL Agent.
Console Systems to install Hardware Sentry on a PATROL Classic Console and PATROL Central
Microsoft Windows edition.
Common services to install Hardware Sentry on the Console Server or on PATROL Central –
Web Edition.
Click Next to continue.
Insta lla tion W iza rd - Ste p 7: Se le cting Role s
Select as many options as required.
8.
Select Hardware Sentry KM for PATROL to install the KM (it should be selected by default).
Select the Java Runtime Environment program if you want to install it along with the KM (this option is only provided when you have previously
Click Next to continue.
A pa che J RE is not supporte d.
Installation Guide
23
Hardware Sentry KM for PATROL
Version 1.8.01
Insta lla tion W iza rd - Ste p 8: Se le cting Products a nd Com pone nts
Installation Guide
24
Hardware Sentry KM for PATROL
Version 1.8.01
9.
Select Yes to restart the PATROL Agent automatically
Insta lla tion W iza rd - Ste p 9: Confirm ing BMC Product Sta rtup Inform a tion
Installation Guide
25
Hardware Sentry KM for PATROL
Version 1.8.01
10. Review the installation parameters and click Start Install to launch the installation procedure.
Insta lla tion W iza rd - Ste p 10: Re v ie wing Insta lla tion Options
Installation Guide
26
Hardware Sentry KM for PATROL
Version 1.8.01
11. The setup program displays the actions performed and indicates the percentage of completion.
Once the installation is complete, click Next to view the installation results.
Insta lla tion W iza rd - Ste p 11: Insta lla tion Sta tus
Installation Guide
27
Hardware Sentry KM for PATROL
Version 1.8.01
12. Click View Log to display a detailed log of the installation procedure. Click Next.
Insta lla tion W iza rd - Ste p 12: Insta lla tion Re sults
13. Click the Finish button to complete and close the installation wizard.
Installation Guide
28
Hardware Sentry KM for PATROL
Version 1.8.01
Insta lla tion W iza rd - Ste p 13: Com ple ting a nd closing the Insta lla tion W iza rd
A Help button is av ailable at each step of the procedure. C lick to display the installation online help. The Ex it button allows y ou to stop the installation procedure.
Once Hardware Sentry is installed and integrated into the PATROL framework and the hardware information sources are available, the hardware information of the monitored computers are displayed in the PATROL Consoles (PATROL® Classic Consoles and PATROL® Central). The operators and administrators just have to look at the PATROL Consoles to see the hardware health of their monitored servers in exactly the same way they see the operating system or database health. Under each server icon, a tree represents all the monitored hardware for this server.
Installation Guide
29
Hardware Sentry KM for PATROL
Version 1.8.01
Using Ha rdwa re Se ntry to m onitor ha rdwa re
Installation Guide
30
Hardware Sentry KM for PATROL
Version 1.8.01
Preloading Hardware Sentry
For optimal operation, we recommend configuring the PATROL agent to preload Hardware Sentry upon start up. The configuration variable used to preload Hardware Sentry is /AgentSetup/preloadedKMs. It can be set with:
PATROL Configuration Manager (PCM) wpconfig.exe, which is the configuration file for Windows xpconfig, which is the configuration file for UNIX/Linux
Please refer to the BMC Software PA TROL documentation for detailed information about these tools.
To preload Hardware Sentry:
1.
Run wpconfig.exe
2.
Double-click the AgentSetup directory. The list of variables is displayed:
Pre loa ding Ha rdwa re Se ntry - wpconfig.e x e
3.
Double-click the preloadedKMs configuration variable
Installation Guide
31
Hardware Sentry KM for PATROL
Version 1.8.01
Modify ing the pre loa de dKMs v a ria ble
4.
Double-click the REPLACE line and add MS_HARDWARE_SENTRY1.km to the list of KMs that are to be loaded by the agent upon start up. Entries must be comma-delimited:
EVENT_MANAGEMENT.kml,NT_PERFMON_WIZARD.kml,NT_BASE.kml,AS_EVENTSPRING.kml,MS_HARDWARE_SENTRY1.kml
5. Click OK
6. Apply the configuration to the agent by clicking the Apply Configuration button in the toolbar.
7. Resume this procedure to set the preloadedKMs variable of each PATROL Agent where Hardware
Sentry has been installed.
Installation Guide
32
Hardware Sentry KM for PATROL
Version 1.8.01
Uninstalling Hardware Sentry
Uninstalling Hardware Sentry is an automated process managed by a wizard. The wizard goes through the necessary steps to remove Hardware Sentry and all files associated with it. You are simply prompt for the product's folder location and the product/components to uninstall.
To uninstall Hardware Sentry
1.
Locate the Uninstall folder under the BMC products directory (typically under C:\Program Files\BMC
Software, or /opt/bmc):
On Windows systems, launch uninstall.exe
On UNIX, launch uninstall.sh
Un-insta ll W iza rd — W e lcom e Ste p
Installation Guide
33
Hardware Sentry KM for PATROL
Version 1.8.01
2.
Specify the BMC Software products folder. See the BMC Software documentation for more information about the BMC Software products folder.
Un-insta ll W iza rd — Spe cify ing folde r
Installation Guide
34
Hardware Sentry KM for PATROL
Version 1.8.01
3.
To uninstall the KM, select Hardware Sentry KM for PATROL.
Un-insta ll W iza rd — Se le cting Products a nd Com pone nts
Installation Guide
35
Hardware Sentry KM for PATROL
Version 1.8.01
4.
Click Start Uninstall.
Un-insta ll W iza rd — Re v ie wing Se le cte d Products & com pone nts a nd sta rt uninsta lling
Installation Guide
36
Hardware Sentry KM for PATROL
Version 1.8.01
5.
A page displays the list of products/components processed and the percentage of completion. Click
Next to continue.
Un-insta ll W iza rd — Sta tus
Installation Guide
37
Hardware Sentry KM for PATROL
Version 1.8.01
6.
A page displaying SUCCESS indicates that Hardware Sentry KM for PATROL is now uninstalled.
Un-insta ll W iza rd — Uninsta ll Re sults
Integrating the KM into the BMC
Framework
Hardware Sentry KM for PATROL can be integrated into BMC Portal and BMC ProactiveNet Performance
Manager to proactively monitor your environments via the KM capabilities. This section will guide you through the integration steps for the two following environments:
Integrating with BMC ProactiveNet Performance Management
38
Installation Guide
Hardware Sentry KM for PATROL
Version 1.8.01
Integrating with BMC Portal
An integration component for BMC Portal is released along with the Knowledge Module (KM) in the form of a PAR file: BMC-PM-PATROL-Hardware-Sentry-<version>.par. It enables visualization of parameter data of all objects monitored by the KM, in the BMC Portal environment.
Owing to structural changes from version 1.8.00, an automatic migration from previous versions
(1.4.xx / 1.5.xx / 1.6.xx / 1.7.xx) of BMC Performance Manager Integration with Hardware Sentry
KM for PATROL is not possible. Users of previous versions should remove the PM from all elements and completely uninstall the Integration PM (v1.4.xx / v1.5.xx / v1.6.xx / v1.7.xx) before uploading and installing v1.8.00 or 1.8.01.
This integration component is v alid on BMC portal v 2.5 upwards.
To integrate Hardware Sentry with BMC Portal:
1.
be required to configure the KM
2.
In the PATROL Console, make sure the KM properly discovered your hardware and is collecting data
3.
Upload the PAR file in BMC Portal:
Place the BMC-PM-PATROL-Hardware-Sentry-<version>.par file in a known location on your file system.
Log in to BMC Portal with the superadmin credentials.
Click on Portal, then under Tasks click Performance Managers.
Click Upload and then click Browse to open a file selection dialog box.
Select BMC-PM-PATROL-Hardware-Sentry-<version>.par and click Upload.
4.
Create a new managed element:
Log in to BMC Portal with administrator credentials
Click the Configure tab > Elements > Add
Select Infrastructure Element and click Next
Select an RSM to collect data about the infrastructure element and click Next
Enter the name of the machine on which the PATROL agent is running, the Host Name and click
Next
Select the group to which your PM will belong and click Next
Select the PATROL category, the Application Classes to add and click Next
Set the Properties and Credentials that the RSM must have to access the specified elements and click Next. The list of thresholds is displayed. You can update these settings without impacting the values set in PATROL.
5.
Click Finish.
Thresholds are set in the PA TROL console. To get the last configurations made, click the Re fre sh PA T ROL
Inte gra tion button av ailable in the Ele m e nts page.
Integrating the KM into the BMC Framework
39
Hardware Sentry KM for PATROL
Version 1.8.01
Integrating with BMC ProactiveNet Performance
Management
To integrate a BMC PATROL KM into BMC ProactiveNet, you need to create a specific adapter. An adapter for BMC PATROL facilitates pulling of performance data from existing BMC PATROL solutions into BMC ProactiveNet. Using an Adapter, you can import BMC PATROL application classes (provided in a
Knowledge Module – KM) into BMC ProactiveNet. The Adapter periodically synchronizes the performance data collected by these application classes into BMC ProactiveNet.
A da pte r for BMC PA T ROL A rchite cture
Integrating the KM into the BMC Framework
40
Hardware Sentry KM for PATROL
Version 1.8.01
Creating and Importing an Adapter for a BMC PATROL KM
Creating an Adapter for a BMC PATROL KM
1.
Open the BMC ProactiveNet Administration Console. The BMC ProactiveNet Administration Console is displayed as shown in the following figure:
A cce ssing the A dm inistra tion ta b in the A dm inistra tion Console
Integrating the KM into the BMC Framework
41
Hardware Sentry KM for PATROL
Version 1.8.01
2.
Right-click the Adapters folder and select Import Monitor Type and Add Adapter > BMC
PATROL.
Im porting Monitor T y pe s a nd A dding A da pte r
Integrating the KM into the BMC Framework
42
Hardware Sentry KM for PATROL
Version 1.8.01
3.
In the Configuration tab, enter the required information:
Se tting the conne ction pa ra m e te rs
Integrating the KM into the BMC Framework
43
Hardware Sentry KM for PATROL
Version 1.8.01
In the Instance Name field, enter a name for this instance of the Adapter that will perform the integration of the ‘targeted KM’ into BMC ProactiveNet.
Select the Agent where this instance of the Adapter will be executed
Enter the Integration Service Agent hostname or IP address
Enter the Integration Service Agent Port. The default port is 3182.
Enter the required credential to connect to the Integration Service Agent
4.
Click Next to continue
Re v ie wing the Inte gra tion Se rv ice configura tion
Integrating the KM into the BMC Framework
44
Hardware Sentry KM for PATROL
Version 1.8.01
5.
Click Next to let the system load the BMC PATROL application classes.
Se le cting A pplica tion Cla sse s to im port
6.
Select the application classes to import
Unselecting will delete the application classes that have already been imported during a previous operation. Application classes ready to be deleted are marked with a red x.
Integrating the KM into the BMC Framework
45
Hardware Sentry KM for PATROL
Version 1.8.01
7.
Click Next to start the import process. The system displays a summary of the application class import, click Next to continue.
8.
Select the application classes you wish to auto-synchronize with the Integration Service Agent.
Se le cting A pplica tion Cla sse s for A uto-sy nc
Integrating the KM into the BMC Framework
46
Hardware Sentry KM for PATROL
Version 1.8.01
9.
Click Next to continue
10. Set the Filter details if need.
Se tting filte r de ta ils
Integrating the KM into the BMC Framework
47
Hardware Sentry KM for PATROL
Version 1.8.01
11. Click Next to continue.
12. Set the Auto-sync poll scheduling, if needed.
Sche duling A uto-sy nc polls
Integrating the KM into the BMC Framework
48
Hardware Sentry KM for PATROL
Version 1.8.01
13. 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.
14. To see the class instances that have been imported by the Adapter, expand the Adapters folder, right-click the Adapter and select Details.
Re v ie wing a n a da pte r de ta ils
We strongly recommend that you create a specific adapter for each KM you need to integrate into
BMC ProactiveNet to enable the update of a single KM independently.
Integrating the KM into the BMC Framework
49
Hardware Sentry KM for PATROL
Version 1.8.01
Updating an Adapter for a BMC PATROL KM
1.
Delete the Adapter instance
2.
Go through the Add an Adapter wizard to actually delete the monitor types that had been created based on the previous version of the KM
3.
Close
4.
Creating an Adapter for a BMC PATROL KM
For complete and detailed information on these procedures, please refer to the BMC Proactiv eNet documentation av ailable from BMC W eb site.
Importing and Customizing Thresholds
1.
Launch the BMC ProactiveNet PW Commands. On Windows 2008, you need to run the PW
Commands as Administrator.
La unching BMC Proa ctiv e Ne t PW Com m a nds
2. Execute the following command line:
pw adapter -type patrol -get_thresholds <file name> -pproxy_host <hostname|ipaddress>
[-pproxy_port <port_number>] [-pproxy_user <username>] [-pproxy_passwd <password>] -i -v where
-get_thresholds <file name> = File name with absolute path at which thresholds will be imported
Integrating the KM into the BMC Framework
50
Hardware Sentry KM for PATROL
Version 1.8.01
-pproxy_host <hostname|ipaddress> = Host name or IP Address of Patrol Proxy Server
-pproxy_port <port_number> = Port at which Patrol Proxy Agent communicates with Patrol Proxy Server
-pproxy_user <username> = User name of Patrol Proxy user
-pproxy_passwd <password> = Password to authenticate Patrol Proxy user
-i = import Instance level thresholds
-v = run in "verbose" mode,producing extra lines of output during extraction and conversion processes
The command has produced a text file with all the parameter threshold settings.
3.
Open the file in a text editor. Check that the global thresholds have been properly interpreted.
4.
Then go to the # INSTANCE LEVEL THRESHOLDS section of the file.
5.
Uncomment all instance level thresholds for the _PATROL__MS_HW_ prefixed instances.
Search the file for the 'NOT_IMPLEMENTED' occurrences to detect thresholds that were not properly converted by the PATROL Adapter.
The import procedure fails to interpret properly the Voltage alert thresholds. If y ou want to activ ate alert thresholds in BMC Proactiv eNet for Voltage parameters, y ou will need to manually describe them in the tex t file, as in the ex ample below.
6.
Save the file.
7.
Execute the following command: pw threshold loadpatrolthreshold [<thresholdfilename> [-v]] where:
<thresholdfilename> is a thresholds file name. If no file path is specified then the default
'<Installation Directory>/pw/tmp/' is used
-v enables the Verbose mode
Class-level thresholds can be displayed using the Absolute Global Thresholds panel in the BMC
ProactiveNet Operator Console, while instance-level thresholds are displayed in the Absolute Instance
Thresholds panel:
Integrating the KM into the BMC Framework
51
Hardware Sentry KM for PATROL
Version 1.8.01
Thresholds have been successfully imported into BMC ProactiveNet.
Managing Baselines and Key Performance Indicators
In order to facilitate the detection of abnormalities on your monitored environment, BMC ProactiveNet calculates baselines per parameter (metrics or attributes) based on values collected over a specified period of time to determine a normal operating range. When the collected values for these parameters are out of range, an alert is triggered.
Some parameters are identified by default as Key Performance Indicators and therefore automatically included in the base lining calculation.
Managing baselines
The baseline is the expected normal operating range for a metric or attribute of a monitor.
The baseline is calculated by collecting the values for a monitor’s attributes and metrics over a specified time period and establishing a low baseline value (consisting of the 10th percentile of all the values for a given time period) and a high baseline value (consisting of the 90th percentile of all the values for a given time period), taking a weighted average of these values over time. A higher weight is given to the latest data being factored into the baseline average. The accuracy of the baseline improves over time.
Requirements for baseline generation
For baselines to be generated for an attribute, that abnormality threshold means that the threshold exists and is not suppressed.
Additionally, if the Key Performance Indicator (KPI) mode is active, only those attributes that have an active abnormality threshold and are also KPI attributes will have baselines generated for them.
A bsolute thresholds (with "outside baseline") or signature thresholds do not satisfy these requirements.
Integrating the KM into the BMC Framework
52
Hardware Sentry KM for PATROL
Version 1.8.01
Managing Key Performance Indicators
The KPI attribute of a parameter can be activated or deactivated manually through the BMC ProactiveNet
Administration Console. In this KM, some parameters or attributes have been designated as important indicators of performance (KPIs). We do not recommend that these default settings are modified.
However, advanced users may activate or deactivate KPIs from the BMC ProactiveNet Administration
Console.
To add or remove Key Performance Indicator (KPI) attributes for a monitor type
1.
In the Administration Console, from the menu bar, choose Tools > KPI Administration. 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 KPI attributes. A list of attributes for the selected monitor type is displayed.
3.
In the KPI column for the attributes that you want to add or remove as Key Performance Indicators: select the KPI check box to add the corresponding attribute as a KPI deselect the KPI check box to remove the corresponding attribute from the KPIs for that monitor type
For complete and detailed information on this procedure, please refer to the BMC Proactiv eNet documentation av ailable from BMC W eb site.
Parameters for which the system by default calculates baselines as well as parameters considered as
KPIs are respectively identified by the following icons:
Baselining
KPI
User Guide
Monitoring the hardware components with Hardware Sentry is very simple. Once the KM is properly installed, as per the instructions given in the
Installation Guide , Hardware Sentry automatically detects
all the various hardware components and displays them in the PATROL interface. There is no configuration or “set–up” to be done in order to monitor the hardware of your infrastructure. All you have to do is set/modify thresholds (if required) and set alert actions as per your specific requirements in order to be notified about an error or failure. This section gives details about all the components monitored by Hardware Sentry.
Integrating the KM into the BMC Framework
53
Hardware Sentry KM for PATROL
Version 1.8.01
Getting Started
Hardware Sentry KM for PATROL® enables administrators to monitor the hardware of their diverse servers. This is a single KM that is able to monitor the hardware of different server and storage system brands: Brocade, Cisco, DELL, Fujitsu, Hitachi, HP, IBM, NEC, Oracle (Sun), etc.
Once installed, Hardware Sentry automatically detects the environment and starts monitoring the hardware: status of the disks and the RAID controllers, temperature of the system, speed of the fans, power supply, enclosure, voltage etc.
Additionally, Hardware Sentry can be configured to monitor devices remotely where a PATROL Agent cannot be installed on: blade chassis, disk arrays, fiber switches and tape libraries.
How does it work?
Hardware Sentry is a KM that allows PATROL to monitor computer hardware (disk status, temperatures, etc.). It gathers hardware information from different sources (vendor-specific agents, standard management technologies, SNMP, WBEM, etc.) and displays this information within the BPPM framework.
For optimal functioning, Hardware Sentry needs certain hardware information sources to be available.
Depending on the platform, it relies on vendor-specific agents and/or on standard management technology such as WBEM or SNMP. On start up, Hardware Sentry automatically detects which hardware information source are available and then uses these sources to monitor the hardware of the computer.
Note that he following diagram is an example and it could be applied to IBM, NEC, HP and other computers.
User Guide
54
Hardware Sentry KM for PATROL
Version 1.8.01
Ex a m ple — How Ha rdwa re Se ntry KM m onitors a DELL Powe rEdge se rv e r running W indows
The DELL OpenManager Server Administrator agent exposes the temperatures, the fans, the power supplies and the voltages of the DELL PowerEdge server through SNMP.
User Guide
55
Hardware Sentry KM for PATROL
Version 1.8.01
The DELL OpenManage Storage Manager agent exposes the status of the physical and logical disks of the DELL PERC RAID Controller through SNMP.
The Windows WMI provider shows the status of the physical disks attached to the standard SCSI
Controller.
Hardware Sentry detects and automatically connects to all three information sources (DELL
OpenManager Server Administrator, DELL OpenManage Storage Manager and Windows WMI provider).
Hardware Sentry gathers the useful hardware information from these sources and displays it within the BPPM framework.
Inside Hardware Sentry
Architecture
Hardware Sentry is principally composed of:
A common hardware monitoring engine: MS_HW_*.km KM classes and ms_hw_*.lib PSL libraries that run with the PATROL Agent of each monitored computer and,
Several connector files (MS_HW_*.hdf) that are platform-specific.
Upon start up, Hardware Sentry tests each connector in order to detect what hardware information sources are available (vendor-specific hardware agents, standards instrumentation layers, etc.). This is called the "detection process".
Once Hardware Sentry knows what hardware information sources are available and can be connected to, it tries to discover the hardware environment by querying these selected hardware information sources, as described in the corresponding *.hdf files. This is called the "discovery process".
Finally, when the detection and discovery processes are complete, Hardware Sentry starts collecting data about the discovered hardware environment (status, temperatures, voltages, etc.) by querying the detected hardware information sources. This is called the "collection process".
Here is a synopsis of the actions performed by Hardware Sentry:
User Guide
56
Hardware Sentry KM for PATROL
Version 1.8.01
Activation: Activates the MS_HW_MAIN class.
Corresponding PATROL process: PRE-DISCOVERY process of the MS_HW_MAIN class. Executed once on the PATROL Agent.
Initialization phase: Reads and interprets agent configuration, creates the main Hardware Sentry icon and activates all of the Hardware Sentry classes. When in debug mode, performs some local diagnostic tests.
: Tests each connector in order to detect which hardware information sources are available and can be connected to.
Corresponding PATROL process: DETECTION process of the MS_HW_MAIN class.
Discovery Process : Discovers the hardware environment by querying previously detected hardware
information sources. Creates the other class instances (MS_HW_TEMPERATURE, MS_HW_FAN etc.)
.
Corresponding PATROL process: DISCOVERY process of the MS_HW_MAIN class. Executed every hour (default period).
Collection Process : Polls previously detected hardware information sources to gather data about the
hardware environment.
Corresponding PATROL process: Collector parameters of the MS_HW_MAIN class: fan Col, logicalDisk Coll etc. Executed every two minutes (default period).
The Connectors
A connector is an ".hdf" file dedicated to one hardware information source. The purpose of each ".hdf" file is to describe how Hardware Sentry can connect to the hardware information source available on a platform and which information is available through this source.
For example, MS_HW_Director4NT.hdf instructs how to get information from the IBM Director 4.x Agent and then monitor an IBM xSeries server.
An ".hdf" file can tell the Hardware Sentry engine to do the following actions:
Query an SNMP agent (get, get_next, and tables)
Execute a WBEM query
Execute an OS command
Each ".hdf" file uses a mix of these possible actions with some computing capabilities to make Hardware
Sentry gather useful data in a given hardware information source.
The ".hdf" files are located under the "MS_HW _hdf" folder under "% PA TROL_HOME% \lib". A ll ".hdf" files are installed on all platforms.
The Detection Process
As Hardware Sentry is preloaded by the PATROL Agent, it begins its operations upon the agent startup.
Once the Hardware Sentry pre-discovery PSL process activates the
Agent spawns the Hardware Sentry discovery PSL process. This PSL process takes two actions: detection and environment discovery. Here is a description of this detection process.
User Guide
57
Hardware Sentry KM for PATROL
Version 1.8.01
Gets the list of available connectors ("*.hdf" files in the %PATROL_HOME%\lib\MS_HW_hdf folder).
For each ".hdf" file found, tests the detection criteria (OS type, NT service, processes, SNMP request, etc.).
Marks the ".hdf" files as "detected" once all its detection criteria is met successfully. There may be several connectors detected at one time (typically: a connector for the temperatures, voltages, etc., another for the RAID disk controller and another for the non-RAID disk controller).
Launches the discovery process.
To optimize the detection process and gain some time, the detection process is heav ily parallelized. A ll the ".hdf" files are processed simultaneously .
The Discovery Process
The discovery process is launched just after the end of the detection process. It takes the following actions:
Processes the "Enclosure.Discovery" section of the detected connectors (".hdf") that describes the computer model and creates the main Hardware Sentry and computer icon (class:
MS_HW_DISKENCLOSURE ). Most of other icons (disk controllers, fans, temperatures, etc.) are
created under this computer icon.
Launches the disk controller discovery that will process the "DiskController.Discovery" section of each detected ".hdf" file and create the
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 corresponding icons.
By default, the discovery is performed once an hour to discover and monitor any new objects added or removed. You can: customize the discovery interval by right-clicking the main Hardware icon > KM Commands >
KM Settings > Discovery interval…
force a discovery manually by right-clicking the Hardware icon > KM Commands > This
System's Settings > Trigger a KM Discovery.
W ith a v iew to optimization, the discov ery process is as paralleled as possible. A ll the independent objects are processed at the same time.
User Guide
58
Hardware Sentry KM for PATROL
Version 1.8.01
The Collection Process
Once the discovery process is complete, the collection process starts:
Every two minutes, Hardware Sentry spawns several PSL processes (fanColl, physicalDiskColl, logicalDiskColl, temperatureColl, etc.) that are responsible for the collection of information about a given device type. For example, fanColl will gather fan information from the different detected hardware information sources, as described in the corresponding ".hdf" Fan.Collect section.
These PSL processes are "attached" to the main Hardware icon ( MS_HW_MAIN class) and not to
the corresponding classes and instances.
No collection is performed on objects that have been paused.
When a device has been marked as "missing" by the discovery process (i.e. had been discovered and is no longer discovered), the collection process no longer queries the hardware information source, and simply sets the missing parameter of the object to alarm.
By default, the collection is performed every 2 minutes. You can customize the polling interval by rightclicking the main Hardware icon > KM Commands > KM Settings > Polling Interval…
Hardware Monitoring
Monitoring Critical Devices
Hardware Sentry automatically detects the information sources available on the managed system and displays the hardware information provided by these sources in the PATROL Consoles in the corresponding container.
User Guide
59
Hardware Sentry KM for PATROL
Version 1.8.01
Com pone nts Monitoring Icons
As long as at least one hardware information source provides useful data about the most critical devices in the computer, an icon will be created for each device in the PATROL Console: processors, memory modules and network interfaces.
Processors, memory modules and network interfaces icons are created under a computer icon. Each icon is labeled with a description of the device: ID, size, vendor, role, etc.
If a dev ice appears to be missing, the ""missing" parameter will trigger an alert.
Monitoring Processors
Processors (also called CPU, Central Processing Unit) are obviously the most critical devices within a computer. While a processor fault may often lead to a system crash without a chance for a monitoring tool to catch the error, it is still very useful to monitor a server’s processors.
In the case of a system crash due to a processor fault, the system reboots automatically. The reboot is either triggered by the operating system or by the motherboard itself. If a processor is no longer working, it is automatically disabled by the BIOS and, if there is one other processor left, the operating system starts with one processor less. Hardware Sentry monitors each processor and verifies if it is present and running. If a processor is missing upon a reboot, Hardware Sentry triggers an alert.
On some recent or high-end servers, processors are able to correct certain operation errors by themselves (like the ECC memory). If this information is available, it is shown in the PATROL Console by
Hardware Sentry. In addition, if the processor is able to predict failure, this information will be monitored by Hardware Sentry and shown in the PATROL Console.
Depending on the available information, the following parameters are displayed for each discovered processor (CPU):
The Missing parameter represents the availability of the processor. An alert is triggered if the processor is missing.
The Status parameter represents the current status of the processor. An alert is triggered if the processor is unavailable for proper operation (e.g.: disabled by the BIOS due to a POST error).
The StatusInformation parameter gives additional information about the current status of the processors.
The PredictedFailure parameter reports the predicted failure analysis performed by the processor itself. This information is based on the rate of corrected errors.
The CorrectedErrorCount parameter represents the number of errors that have been automatically corrected by the processor. This information can be very useful to predict a failure in the near future.
The CurrentSpeed parameter reports the current speed of the processor in megahertz. The speed of a processor can vary depending on the workload of the server.
User Guide
60
Hardware Sentry KM for PATROL
Version 1.8.01
Monitoring Memory Modules
The main memory of a computer is actually as critical as the processors since almost all processor operations deal with the memory. A single memory fault could lead to a severe computer crash potentially leading to data corruption as well. On servers, the memory modules (devices where memory data is stored) often include auto-correction features (ECC), and sometimes even better: RAID5-like memory configuration. These features and configurations allow the memory modules to report statistics 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 the memory modules, the following parameters will be displayed for each discovered memory module:
The Missing parameter reports the availability of the memory modules. An alarm is triggered if a memory module is no longer discovered.
The Status parameter represents the current status of the memory module. An alert is triggered if the memory module reports a failure (in a RAID5-like configuration).
The StatusInformation parameter gives additional information about the current status of the memory modules.
The ErrorCount parameter reports the number of errors detected by the memory module and then corrected. A steadily growing value means that the memory module is not reliable and that it could encounter errors that it is unable to correct, which mean this could lead to a system crash.
The ErrorStatus parameter deals with the same kind of error as the ErrorCount parameter but in a more accurate manner. The only difference is that, once a specified threshold is reached, an alert is triggered, so the number of errors is not actually displayed here. It is unnecessary to set an error threshold as the threshold is calculated and set by the hardware agent.
The PredictedFailure parameter reported by the memory modules predicts failure by analyzing the trend of the number of detected/corrected errors (with the ECC technology). If this parameter goes into alarm, replacement of the faulty memory module is highly recommended.
Monitoring Network Ports
Hardware Sentry automatically detects the information sources available on the monitored computer and displays the hardware information provided by those sources in the PATROL Consoles in the corresponding container. Device icons are automatically created below the main Network Interface icon they are attached too.
Hardware Sentry triggers alerts if it detects a break in the network link. By default, this alert is raised
ONLY if a previously detected network link is broken. The following parameters are monitored for each network of fiber adapter, if available:
User Guide
61
Hardware Sentry KM for PATROL
Version 1.8.01
BandwidthUtilization
DuplexMode
ErrorPercent
LinkSpeed
LinkStatus
Missing
ReceivedBytesRate
ReceivedPacketsRate
Status
StatusInformation
TransmittedBytesRate
TransmittedPacketsRate
ZeroBufferCreditPercent
Status
The Status parameter represents the current status of the network interface. An alert is triggered when the network interface does not respond.
StatusInformation
The StatusInformation parameter gives additional information about the current status of the network.
LinkStatus
The LinkStatus parameter shows the current status of the network interface to the network (i.e.
whether or nor plugged-in). By default, Hardware Sentry will trigger a warning if a network interface previously connected to the network is now unplugged. However, it will not trigger an alert for network interfaces that were never connected.
Missing
The Missing parameter shows the availability of the monitored devices. An alert is triggered if a device is no longer discovered.
ErrorPercent
The ErrorPercent parameter gives the percentage of transmitted and received packets that were in error (due to low-level protocol error or physical media problems). A warning is raised when this percentage goes above 10% and an alarm when above 30%. A frequent high error percentage implies there is a serious problem with the cable or the interface.
DuplexMode
Monitoring network cards communication performance may be critical to ensure that they run at the
User Guide
62
Hardware Sentry KM for PATROL
Version 1.8.01
expected speed in order to avoid network congestion or any other performance issues.
Most Ethernet cables allow communication in both directions between two connected cards, this feature is commonly named "full duplex". However, a defective cable or a simple internal malfunction within the cards can prevent them from communicating both ways simultaneously. In that case, once a party begins receiving a signal, it must wait for the transmitter to stop transmitting, before replying. This communication mode is typically called "half-duplex" and can generate network congestion.
The DuplexMode parameter's value is set to:
0 when the network adapter is running in "half-duplex" mode
1 when in "full-duplex" mode.
By default, the DuplexMode parameter triggers a WARNING when an adapter that was running in "fullduplex" suddenly starts communicating in "half-duplex".
LinkSpeed
The LinkSpeed parameter reports the speed that the network adapter and its remote counterpart currently use to communicate with each other. Note that the unit of this parameter is Mbits/sec.
By default, the LinkSpeed parameter triggers a WARNING when the adapter "slows down", i.e. renegotiates the link speed with its remote counterpart, and is forced (by some circumstances to figure out) to downgrade to a slower communication rate.
ReceivedBytesRate, TransmittedBytesRate, ReceivedPacketsRate,
TransmittedPacketsRate
Transmission rates monitoring provides administrators with valuable information regarding the incoming and outgoing data managed by servers and switches.
BandwidthUtilization
This parameter is ONLY collected if LinkSpeed, DuplexMode, ReceivedBytesRate and
TransmittedBytesRate are all properly collected. The bandwidth utilization (in percentage) cannot be calculated without one of the above-mentioned parameters.
Monitoring Disks
Hardware Sentry automatically detects the information sources available on the monitored computer and displays the hardware information provided by those sources in the PATROL Consoles in the corresponding container.
If at least one hardware information source provides useful data about the storage in the computer, an icon will be created for each storage-related device in the PATROL Console: disk controllers, physical
User Guide
63
Hardware Sentry KM for PATROL
Version 1.8.01
disks and logical disks.
Disk Monitoring Icons
Physical and logical disks icons are created below the disk controller icons they are attached too. Each icon is labeled with a description of the device: ID, size, vendor, role, etc.
If a dev ice appears to be missing, the ""Missing" parameter is alway s used to trigger an alert.
Monitoring Disk Controllers
A disk controller is a card inside a computer that connects one or several physical disk drives to the computer. Some intelligent disk controllers (such as RAID controllers) manage several physical disks as a single logical disk which is the only disk exposed to the operating system. Monitoring both physical and logical disks is essential to ensure that the storage is available.
The purpose of the disk controller instance is to act as a container for logical disks and physical disks monitoring, and symbolize the way hard drives are setup on the platform. In addition, some information regarding the disk controllers, like their brand, model or driver version, is displayed in the Infobox.
Depending on the information available, the following parameters will be displayed:
User Guide
64
Hardware Sentry KM for PATROL
Version 1.8.01
The BatteryStatus parameter triggers an alert to predict that the disk controller battery will be unable to support the controller in the event of a power failure.
The ControllerStatus parameter displays the status of the disk controller.
The Missing parameter reports the availability of the disk controller. An alert is triggered when the disk controller is no longer discovered.
The StatusInformation parameter gives additional information about the status of the disk controller.
If a disk controller goes missing, all its disk dependencies will be missing as well.
Monitoring Physical Disks
Physical disks must be monitored to avoid loss of data, unavailability and performance degradation.
When available, the S.M.A.R.T. technology will be used to predict a disk failure before it occurs.
Depending on the available information, the following parameters will be displayed for each discovered physical disk:
The ErrorCount parameter is incremented each time an error occurs on this physical disk. An alert is raised from the first detected error. The operator can reset the counter and clear the alert through the Acknowledge Error Count Alerts and Reset KM command in the PATROL Console.
The Missing parameter reports the availability of the physical disk. An alert is triggered when the physical disk is no longer discovered.
The PredictedFailure parameter uses the S.M.A.R.T. technology to predict physical disk failures. An alert will be triggered if it is predicted that the Physical Disk will soon break down.
The Status parameter represents the current status of the physical disk. An alert is triggered if the physical disk is not available for proper operation.
The StatusInformation parameter gives additional information about the status of the physical disk.
Monitoring Logical Disks
RAID or advanced disk controllers expose several physical disks as a single logical disk to the operating 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 following parameters are displayed:
The ErrorCount parameter represents the number of errors that the disk has encountered since the last reinitialization or since the last manual reset.
The Missing parameter reports the availability of the logical disk. An alert is triggered when the logical disk is no longer discovered.
The PredictedFailureInforms parameter reports if a failure is predicted.
The Status parameter represents the current status of the logical disk. An alert is triggered when the logical disk is not fully operational (degraded, rebuilding, etc.) or not available at all.
The StatusInformation parameter gives additional information about the current status of the physical disk.
For non-RA ID disk controllers (as most of IDE controllers, for ex ample), no logical disk will be display ed.
User Guide
65
Hardware Sentry KM for PATROL
Version 1.8.01
Monitoring LUNs
LUNs are volumes stored on a remote disk array and that are exposed to the operating system of a server as a hard disk by the HBA card (host bus adapter, typically a fiber channel card). Monitoring LUNs consists in verifying by how many paths they can be accessed.
In most redundant sy stems, a LUN can be accessed through 4 different paths, in which case the sy stem generally concludes that there 4 four disks av ailable; which is not correct. To av oid this misunderstanding, Hardware Sentry relies on another lay er, the multi-path I/O (MPIO), that will identify that there is actually only one disk av ailable. This lay er works like a driv er disk and is supplied by the operating sy stem. If there is no MPIO driv er configured, no discov ery is possible.
To monitor LUNs:
1.
In the console, double-click the Missing parameter of the MS_HW_LUN application class to verify
the remote volume is actually discovered
2.
You can then double-click the Status parameter to make sure the remote volume is not degraded or has not failed
3.
Finally, double-click the AvailablePathCount parameter to verify there are at least two paths available.
Monitoring Environment
Hardware Sentry automatically detects the information sources available on the monitored computer and displays the hardware information provided by those sources in the PATROL Consoles in the corresponding container.
If a hardware information source provides useful data about temperatures, fans, voltages or powersupplies, an icon is automatically created for each sensor found in the system as well as one or more parameters.
User Guide
66
Hardware Sentry KM for PATROL
Version 1.8.01
Env ironm e nt Monitoring Icons
For each displayed sensor, one or more graphs are built by polling the sensor every two minutes. This graphic can be viewed by double-clicking the Temperature parameter in the Console.
T e m pe ra ture history gra ph
The location or the type of the sensor may appear in the icon label if this information is available.
User Guide
67
Hardware Sentry KM for PATROL
Version 1.8.01
Depending on the platform and sensors and if possible, alert thresholds are automatically set by
Hardware Sentry KM for PATROL. When the parameter value reaches these thresholds, the parameter triggers a warning or an alarm and this alert is sent by the PATROL Console to the operators and administrators.
The parameters discov ered depend on the serv er ty pe. A ll parameters may not be discov ered on all serv ers. Please refer to the
the menu commands for each application class.
Monitoring Temperature Sensors
As with any electronic device, chips and other components of a computer stop working when they get overheated (several unrecoverable errors, crashes and even hardware damage). Temperatures may rise too high when a device is abnormally overloaded, a fan is not working properly or when the ambient temperature is too hot. Monitoring the temperatures of the critical devices of your system allows you to take preventive action and avoid a crash from overheating.
Depending on the available information, the following parameters will be displayed for each detected temperature sensor:
The Missing parameter represents the availability of the temperature sensor. An alert is triggered when a temperature sensor is no longer discovered
The Status parameter represents the current status of the temperature. An alert is triggered if the temperature gets too high.
The StatusInformation parameter gives additional information about the current status of the temperature.
The Temperature parameter represents the current temperature reading in Celsius degrees (°C).
An alert is triggered if the temperature rises too high.
Monitoring Fans
To avoid overheating, system vendors install fans on critical devices (processors, power supplies, etc.).
If a cooling system is not present, an overheated system can throttle the speed of processors and cause slow-downs or ultimately cause shut-downs. Monitoring fans is important since they ensure maintaining the right temperatures for optimal functioning of the system.
Depending on the available information, the following parameters will be displayed for each detected fan device:
The Missing parameter represents the availability of the fan. An alert is triggered if the fan is no longer discovered.
The Speed parameter represents the speed of the corresponding fan (in rotations/minute). An alert is triggered if the fan speed is to low for proper functioning.
The SpeedPercent parameter represents the speed of the corresponding fan in percentage of its maximal speed.
The Status parameter represents the current status of the fan. An alert is triggered if the fan stops spinning or does not spin fast enough.
The StatusInformation parameter gives additional information about the current status of the fan.
User Guide
68
Hardware Sentry KM for PATROL
Version 1.8.01
Monitoring Power Supplies
The power supply is the component that transforms the AC Line into electric power needed by the computer. 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 supplies allows the operators to be alerted when a power supply fails, or in some cases even when a power supply is overloaded.
Depending on the available information, the following parameters will be displayed for each power supply or power unit device:
The Missing parameter represents the availability of the power supply. An alert is triggered when the power supply is no longer discovered.
The Status parameter represents the current status of the power supply. An alert is triggered if an error occurs with the power supply.
The StatusInformation parameter gives additional information about the current status of the power supply.
The UsedCapacity parameter represents the power currently in use as a percentage. An alert is triggered when the power supply’s maximum power output is reached.
Monitoring Voltage Sensors
Power supplies convert the AC line power into voltages and currents needed by the motherboard of the computer. The stability of the motherboard (and therefore that of the overall computer) strongly depends on this power converter. Voltages that are too low or too high may lead to unpredictable system crashes. Monitoring the value of the different voltages needed by the motherboard will help in detecting system instability.
Depending on the available information, the following parameters will be displayed for each voltage sensor on the motherboard:
The Missing parameter represents the availability of the power converter. An alert is triggered when a power converter is no longer discovered.
The Status parameter represents the current status of the voltage. An alert is triggered if the voltage output is too low for proper functioning.
The StatusInformation parameter gives additional information about the current status of the voltage.
The Voltage parameter represents the voltage output in milliVolts (mV). An alert is triggered if the voltage goes out of the proper range.
Monitoring LEDs
All servers and SAN devices use LEDs to report on their essential and most critical functions: whether they are turn off or on, overheating, misconfigured, unplugged, etc. These LEDs constitute the first level of hardware monitoring in many cases.
Therefore, Hardware Sentry KM for PATROL reports the status of the LEDs in the servers that are able to provide that information. That may include front facing and internal LEDs. When possible, the KM will monitor the color/status (on, off, blinking) of each LED.
User Guide
69
Hardware Sentry KM for PATROL
Version 1.8.01
Monitoring a Remote System or an External Device
By design and by default, Hardware Sentry KM monitors the hardware of the server it is running on, excluding any external parts that the system may see (like a disk in an external disk array). However, the KM can be configured to monitor a component that needs to be accessed through the network, or an external device like a storage array.
C onfiguring Hardware Sentry to monitor another sy stem or ex ternal dev ice remotely does not prev ent it from monitoring the hardware of the local host where the KM is running. Once configured to monitor another sy stem remotely , the KM will show two icons side-by -side in the PA TROL C onsole: "Hardware on local host" and "Hardware on
<RemoteSy stem>".
Here are several typical scenarios where this mechanism will prove to be useful:
Monitor the shared chassis of a group of blade servers
Monitor the server itself through its out-of-band management card (which provides more
information than the operating system in-band)
Monitor a SAN switch , disk array or
tape library , which the PATROL Agent and KM cannot be
installed on
The licensing terms remain unchanged as to whether systems and devices are monitored locally or remotely.
Monitoring a Blade Chassis
Blade servers are small-factor servers that share the same enclosure which provides the powering and cooling for all the blade servers inside the chassis. Most popular blade systems are:
DELL Modular Chassis
Hitachi BladeSymphony
HP BladeSystem
IBM BladeCenter
Fujitsu-Siemens Blade BX
All these blade chassis are fully supported by Hardware Sentry KM.
Each blade server can be considered as a true physical server whose hardware components need to be monitored. A PATROL Agent and a Hardware Sentry KM must be installed on each blade server to monitor the various parts of the blade: processors, memory modules, internal temperature, internal disks, etc.
Additionally, it is important to monitor the different components of the shared enclosure: power supplies and fans notably. Blade enclosures are generally equipped with a management card (the name can vary depending on the manufacturer: management module for the IBM BladeCenter, management blade for the Fujitsu-Siemens Blade BX, iLO or On-board Administrator for the HP BladeSystem, DRAC-MC for the
Dell Modular Chassis).
User Guide
70
Hardware Sentry KM for PATROL
Version 1.8.01
In addition to the monitoring of the blade server it is running on, you can configure Hardware Sentry KM to connect to the management interface of the enclosure and monitor its hardware parts. Use the
Remote System or an External Device wizard to specify the name and IP address of the management
interface. Specify that the element is a “Blade Chassis or Out-of-band Management Card”. Choose the appropriate connector corresponding to the type of the chassis or let the KM automatically detect it, and then provide the wizard with the credential to connect to the management interface (SNMP community or username and password if it’s a telnet/SSH-based interface).
In the PATROL Console, you obtain two separate main Hardware icons:
Hardware on <blade chassis name>, representing the hardware components of the shared enclosure
Hardware on local host, representing the hardware components of the server (blade) the KM is running on
Under the shared chassis, an icon is also created for each blade server in the enclosure with an overall status for the blade (when available).
No additional license capacity is required to monitor the shared blade enclosure in addition to the blade serv ers present in the main chassis.
User Guide
71
Hardware Sentry KM for PATROL
Version 1.8.01
Monitoring VMware Servers
Virtualization helps IT administrators reduce capital expenses through server consolidation and improve operating expenses through automation. Because a virtualized environment faces more risks than a physical one, IT administrators must consider monitoring their virtual machines. They should always keep in mind that when an issue occurs on the physical host, it impacts all the virtual machines running on the server.
As a PATROL Agent cannot be installed on the VMware ESXi Host, the monitoring needs to be done remotely, from a PATROL Agent running on another server, physical or virtual. It is recommended that the PATROL Agent and Hardware Sentry KM run on a separate physical system (or in a virtual machine on a separate physical system) to ensure continuous monitoring even in case of hardware failures.
Hardware Sentry KM needs to be manually configured to connect to the VMware ESXi Host to discover what the physical system is made of and collect the status of all components.
For more information about the installation procedure, please refer to the KB article Monitoring VMW are ESX/ESXi .
To monitor VMware servers:
1.
Right click the local host’s Hardware icon > KM Commands > Add a Remote System or an
External Device...
User Guide
Monitor VMwa re Se rv e rs — Lice nse A gre e m e nt
72
Hardware Sentry KM for PATROL
Version 1.8.01
Read the license agreement, accept it and click Next to continue.
2.
Identify the system or device you want to monitor remotely and click Next.
Monitor VMwa re Se rv e rs — Sy ste m Ide ntifica tion
System or Device name: Enter the name of the system or device you wish to monitor
IP address or fully qualified name: Leave this field blank if you specify the host name above
System or Device type: Select Management Card/Chip, Blade Chassis, ESXi
User Guide
Monitor VMwa re Se rv e rs — Conne ctor Se le ction
73
Hardware Sentry KM for PATROL
Version 1.8.01
3.
Select WBEM and click Next
Monitor VMwa re Se rv e rs — W BEM cre de ntia ls
4.
Click on the Advanced Options button to access specific settings related to the WBEM connection:
User Guide
Monitor A nothe r Sy ste m Re m ote ly — W BEM Cre de ntia ls — A dv a nce d Options
74
Hardware Sentry KM for PATROL
Version 1.8.01
Enter the IP address/Host-name of the Multi-tier Authentication Server (This option mostly is used for VMware servers).
Enter the WBEM namespace or leave the field empty to let the KM automatically detect the proper name (recommended). If the WBEM credentials are not provided, Hardware Sentry will authenticate using the credentials provided in the previous panel (WBEM Credentials). This therefore disables multi-Tier authentication.
Click Accept to validate your changes.
5.
Enter the WBEM credentials and click Next. A new icon is then created in the PATROL Console
Monitor VMwa re Se rv e rs — Discov e re d Com pone nts
Monitoring a Server through its out-of-band management card
For most servers, Hardware Sentry KM relies on an instrumentation layer running on the operating itself
(an SNMP agent, a WBEM provider, or some system commands). However, for some types of servers
(mostly UNIX systems), the information available in-band is not sufficient and does not provide any data regarding environment sensors, power supplies, etc. For these systems, Hardware Sentry KM offers the ability to get additional information about the server through its out-of-band management card (if any).
By default, Hardware Sentry KM monitors the hardware components in-band only. Use the
Remote System or an External Device wizard to make Hardware Sentry KM connect to the out-of-band
management card and retrieve the additional information available. In the wizard, enter the name of the out-of-band management card and its IP address. Select “Management Card/Chip, Blade Chassis, ESXi” as the system type. Choose the appropriate connector corresponding to the management card in the system and then enter the credentials to connect to it.
In the PATROL Console, an additional icon is created:
User Guide
75
Hardware Sentry KM for PATROL
Version 1.8.01
Hardware on local host, corresponding to the monitoring done in-band
Hardware on <management card name>, corresponding to the monitoring done out-of-band through the management card.
No additional license capacity is required when monitoring a sy stem from both in-band and out-of-band.
Monitoring a SAN Switch
As the importance of the external storage grows with the implementation of blade servers and virtualization, monitoring the center piece of the SAN, i.e. the fiber switch, has become more critical than ever. Hardware Sentry KM is able to monitor SAN switches from Cisco, Brocade and McData: their internal hardware components, fiber ports, temperature, power supplies, fans, as well as the traffic on each port. This greatly helps SAN administrators understand the performance issues in the environment: which servers are very demanding, which array is under pressure, backups impact, etc.
As a PATROL Agent cannot be installed on a SAN switch, you will need to install the KM and the PATROL agent on a regular system and then configure Hardware Sentry KM to connect to the SAN switch and
monitor it. Use the Add a Remote System or an External Device wizard to specify the name and IP
address of the SAN switch. Select the appropriate connector or let the KM detect it automatically. Refer to the
Connectors Index chapter to get detailed information on the supported switches.
Fiber Alliance SNMP Agent, for Brocade and McData switches
Cisco MDS9000 Series, for Cisco switches
A “Hardware on <switch name>” icon is created representing all of the monitored components of the switch, such as:
User Guide
76
Hardware Sentry KM for PATROL
Version 1.8.01
Blades
Temperature sensors
Fans
Power supplies
Network cards
Enclosure model
For each port: the link status (a warning is triggered when a connected port gets disconnected), the link speed (a warning is triggered when the negotiated speed gets lower), the percentage of errors on the link, the data flow (in and out) in bytes and packets and the bandwidth utilization.
Additionally, SAN administrators can use the Ethernet/Fiber Port Traffic Report
tool in Hardware Sentry
KM to visualize the amount of data that are processed by each port of the switch on an hourly or daily basis.
The monitoring of a SA N switch requires the purchase of an additional “Sentry Software Monitoring and A naly tics for
BMC Performance Manager - Storage Monitoring” license.
Monitoring an External Disk Array
Monitoring an external disk array
SAN administrators often struggle to consolidate the monitoring and reporting of the various disk arrays from different vendors that are under their responsibility. Hardware Sentry is able to monitor a wide range of disk arrays: IBM DS, HP EVA, EMC, etc. By relying on their SMI-S standard instrumentation, or on their specific administration tools otherwise, Hardware Sentry KM monitors the health of the various internal components: the disks, the different levels of allocated volumes, the fiber ports, the environment and the controllers.
Depending on the disk array and the way it is instrumented, the configuration of Hardware Sentry KM may vary.
User Guide
77
Hardware Sentry KM for PATROL
Version 1.8.01
First case: The disk array is SMI-S compliant itself, i.e. it can be interrogated directly by using the
SMI-S protocol (WBEM-based), like the EMC Symmetrix disk arrays. Use the
appropriate connector or let Hardware Sentry KM detect it automatically, and then enter the credentials to connect to the disk array.
Second case: The disk array requires the installation of a management software tool on a separate server or workstation, like the EMC Clariion and HP EVA disk arrays. The disk array management tool acts as a “proxy” with the disk array itself. You need to install the PATROL Agent and Hardware Sentry on the server or workstation where the disk array management tool is running. By default, Hardware Sentry will monitor the hardware components of the server or workstation it is running on. Use the
Add a Remote System or an External Device wizard to make
Hardware Sentry also monitor the disk array through the management “proxy”. Enter the System or
Device name and specify “localhost” as the IP address. This will make Hardware Sentry KM send its
SMI-S/WBEM queries to the local management software tool.
Third case: IBM DS3000 and IBM DS4000 disk arrays require the installation of the SMCli tool on a server or workstation. You need to install the PATROL Agent and Hardware Sentry on the server or
workstation where SMCli has been installed. Use the Add a Remote System or an External Device
wizard to make Hardware Sentry use the SMCli tool to connect to the IBM disk array. Enter the name of the disk array and its IP address (note that you don’t specify “localhost” as in the previous case, SMICli is not a “proxy” interface). Select the appropriate connector or let Hardware Sentry KM detect it automatically, and then enter the credentials to connect to the disk array.
Fourth case: NetApp filers are monitored remotely through their native SNMP Agent. Use the
Add a Remote System or an External Device wizard to make Hardware Sentry KM monitor the internal
hardware components of the NetApp filer: enter the name and IP address of the disk array, select the appropriate connector or let Hardware Sentry KM detect it automatically, and then enter the
SNMP community string. Filers have a much broader feature set than pure disk arrays. Sentry
Software provides an additional KM that focuses on the performance and statistics metrics of the filer itself (filesystems, backups, I/O, etc.): NetApp Filers KM for PATROL. Both KMs (Hardware
Sentry KM and NetApp Filers KM) are required to obtain a full monitoring coverage of a NetApp filer.
Hardware Sentry KM shows the pure disk array part and NetApp Filers KM shows what is sometimes called the “NAS head”.
The monitoring of an ex ternal disk array requires the purchase of an additional “Sentry Software Monitoring and
A naly tics for BMC Performance Manager - Storage Monitoring” license.
Monitoring a Tape Library
As backups are now often centralized on tape libraries, it is important to ensure that these devices are available to backup software products. Hardware Sentry is able to monitor the health of the various internal components of a tape library, including the tape drives and the media changers. Please note that Hardware Sentry does not monitor the backup software products in charge of copying the data to the tapes. It will not report whether a backup operation couldn’t complete or when a backup set is not up to date.
Most tape libraries are instrumented through SNMP. While bearing different vendor names, most tape libraries are OEM’d from StorageTek or Quantum/ADIC. Use the
Add a Remote System or an External
IP address. Select the appropriate connector (most probably, simply corresponding to the real manufacturer of the library: IBM, Quantum/ADIC or StorageTek). Enter the SNMP community.
User Guide
78
Hardware Sentry KM for PATROL
Version 1.8.01
The monitoring of a tape library requires the purchase of an additional “Sentry Software Monitoring and A naly tics for
BMC Performance Manager - Storage Monitoring” license.
How to Locate a Device in a System
Depending on the monitored platform, the way the various objects are named in the PATROL Console can vary significantly. There are different IDs and names that are used by Hardware Sentry KM for each monitored object:
The internal PATROL Object ID, used to create the instance of the class; This ID is retrieved in the PATROL events that other event management systems gather (like BMC Enterprise Manager, etc.). It is a concatenation of the corresponding connector file name, the host name and the internal device ID. The internal PATROL Object ID can be seen in the Infobox of the corresponding object.
The internal Device ID, used by Hardware Sentry to uniquely identify the device in the underlying instrumentation layer. Depending on the instrumentation layer, the internal Device ID can take very different forms: a simple number, a dot-separated list of small numbers (0.0 or 1.1.2, for example), an alpha-numeric string (VCC_+12V, for example), or a complex WBEM or PnP ID
(IDE\DiskHitachi_HTS721080G9SA00_________________MC4OC10H\5&1f698b3f&0&0.0.0_0 for example). The internal Device ID is often a good way to locate the corresponding device in the real life. When it is not too long, it is displayed in the label of the icon representing that object in the
PATROL Console. Otherwise, the internal Device ID is replaced by an arbitrary number in the icon label. In any case, the internal Device ID can be seen in the Infobox of the object.
The name of the icon representing the monitored component in the PATROL Console includes the aforementioned internal Device ID (when it is not too long) as well as some additional information such as the vendor and the model of the component. In some cases, the location of the device or sensor is clearly mentioned.
Some additional “identifying information” is also provided when the instrumentation layer is able to do so. The availability of additional identifying information really depends on the type of the monitored component and the underlying instrumentation layer. For example, when monitoring a
DELL server, Hardware Sentry shows the DIMM slot location of each memory module, and their part number. In case of a memory failure, this greatly helps administrators order a new memory module with the right part number and change the faulty one with no risk of confusion with another working memory slot. Additional “identifying information” can be visualized in the Infobox. It is also reported in the
and the Hardware Health Report generated when a failure is detected.
The screenshot below clearly shows the different types of IDs and names for a monitored object in
Hardware Sentry:
User Guide
79
Hardware Sentry KM for PATROL
Version 1.8.01
Inv e ntory Re port showing diffe re nt ty pe s of m onitore d obje cts IDs a nd na m e s
The
Hardware Health Report which is generated upon the detection of a failure shows all of the
different IDs: PATROL Object ID, Internal Device ID, Serial Number, Part Number, Location, and icon name.
Insta nt Ha rdwa re He a lth Re port showing m onitore d obje ct IDs
User Guide
80
Hardware Sentry KM for PATROL
Version 1.8.01
Use Cases
Checking Disks Health
Most manufacturers typically use the “mean time to failure” or MTTF to indicate the operational reliability of their products. But the advertised MTTF of 1,000,000 hours (or even more!) is misleading.
Recent studies show that the average annual replacement rate for hard disks is typically between 3% and 15%. This means that an organization with just 100 servers and approximately 300 hard disks will experience between 9 and 45 disk failures every year, which if they don’t impact the availability of the system will surely degrade the overall performance dramatically. An organization with 1000 servers will experience almost a disk failure each day of the year. Given their relevant short lifetime and the amount of data they store, disks are one of the most critical devices to be monitored.
Monitoring disk health consists in monitoring disk controllers, physical and logical disks.
Monitoring Disk Controllers
A disk controller is a card inside a computer that connects one or several physical disk drives to the computer and write cache. To keep this write from being lost if power is interrupted, the card must be configured with a battery. It is thus recommended to closely monitor this battery.
1.
In the PATROL console, double-click the BatteryStatus parameter to verify the disk controller battery is able to support the controller in the event of a power failure
2.
You can also double-click the ControllerStatus parameter to make sure the controller is not degraded or has not failed
Monitoring Physical disks
Physical disks must be monitored to avoid loss of data, unavailability and performance degradation.
Contrary to other solutions, Hardware Sentry monitors the actual physical disks behind the controller and not only the disks as seen by the operating system. The application class used is
User Guide
81
Hardware Sentry KM for PATROL
Version 1.8.01
1.
In the PATROL Console, double-click the Status parameter to verify that it has not failed or is not degraded
2.
If available, double-click the PredictedFailure parameter to verify the physical disk is not likely to fail
3.
In case a replacement is required, in the PATROL Console, right-click the Physical Disk Icon >
InfoBox. All the information required (vendor name, model, serial number, etc.) is displayed:
Phy sica l Disks InfoBox
Monitoring Logical Disks
RAID or advanced disk controllers expose several physical disks as a single logical disk to the operating system. The information required by administrators is mainly the logical disk's status, its RAID type and size. To get that information:
User Guide
82
Hardware Sentry KM for PATROL
Version 1.8.01
1.
first, right-click the Logical Disk icon > Status. A graph is displayed in the graph pane indicating the status of the RAID array (OK, degraded, offline)
2.
right-click the Logical Disk Icon > InfoBox. A dialog box is displayed:
Logica l Disks InfoBox
It contains all the relevant information about the selected logical disk.
Monitoring Network Traffic & Preventing Bottlenecks
Today, every application relies on the network whose bandwidth and latency has a dramatic impact on the overall measured and perceived IT performance. Hardware Sentry monitors the connectivity and the quality of the connection. The incoming and outgoing traffic is also constantly measured against the available bandwidth to give system administrators the short term and long term visibility on the network capacity utilization.
User Guide
83
Hardware Sentry KM for PATROL
Version 1.8.01
Verifying the Connection
1.
In the console, double-click the LinkStatus parameter under the Network Interfaces icon
( MS_HW_NETWORK application class) to verify the interface is actually plugged to the network. By
default, a warning event is triggered when a connected network adapter is unplugged from the network. Unused adapters will not trigger useless alarms.
2.
The Status parameter only represents the status of the network adapter itself, not the connectivity
3.
The LinkSpeed parameter reports the current speed of the connection. For Ethernet or fiber adapters, any movement on this parameter means the quality of the connection is poor and needs to be fixed. By default, a warning event is triggered when the link speed downgrades from its current value to a lower value (from 1Gb/s to 100Mb/s for example).
4.
The DuplexMode parameter reports whether the Ethernet connection is working in full duplex or half-duplex mode.
5.
You can also double-click the ErrorPercent parameter to know the percentage of transmitted and received packets that were in error. A frequent high error percentage implies there is a serious problem with the cable or the interface.
Monitoring the Transmission Rates
Transmission rates monitoring provides administrators with valuable information regarding the incoming and outgoing data managed by servers and switches.
1.
In the console, double-click the parameters of the MS_HW_NETWORK application class:
ReceivedBytesRate and TransmittedBytesRate to know the data flow exchanged
ReceivedPacketsRate and TransmittedPacketsRate to know the number of received and/or transmitted packets.
Monitoring the T ra nsm ission Ra te s
The graph displayed will help you identify the traffic demands and spikes.
User Guide
84
Hardware Sentry KM for PATROL
Version 1.8.01
Understanding the Bandwidth Utilization
1.
In the console, double-click the BandwidthUtilization parameter of the
application class to know the percentage used of the available bandwidth. A graph is automatically displayed in the console's graph pane
Monitoring the Ba ndwidth Utiliza tion
The BandwidthUtilization parameter can ONLY be collected if LinkSpeed, DuplexMode,
ReceivedBytesRate and TransmittedBytesRate are all properly collected.
2.
Search for unexpected and random spikes in the network activity, which will signify either an attack or unauthorized transfer of data.
Reporting Data Traffic on a Fiber Switch in a SAN
Once Hardware Sentry KM has been configured to monitor a fiber switch in a SAN (Brocade, Cisco, or
McData), it measures the amount of ingoing and outgoing data for each fiber port in the switch. This information is stored in the PATROL Agent’s history as a data rate (in megabytes per second), and as a total amount of data (in gigabytes). The history retention period specified in the PATROL Agent’s configuration defines how much data is retained in the history file and how much can be used for the reports.
By using the Reporting > Ethernet/Fiber Port Traffic Report… KM Command, the PATROL administrator can build a report of the data traffic on a SAN switch. This tool generates a multiparameter graph in the PATROL Console with the total amount of data transmitted and received by each port in the switch, on a per-hour or per-day basis.
User Guide
85
Hardware Sentry KM for PATROL
Version 1.8.01
Ethe rne t/Fibe r Port T ra ffic Re port
The graph above shows that one device has been transmitting 25GB, while the other ports are barely active.
By choosing the “bar-style” graph (see picture above), we can identify that actually 1 port on the switch reported an activity.
Ethe rne t/Fibe r Port T ra ffic Re port - Ba r Sty le Gra ph
The statistics button of the graph window allows us to see some numerical information about each graph.
User Guide
86
Hardware Sentry KM for PATROL
Version 1.8.01
The infobox on the different ports can help us identify which devices on the SAN are the cause of an abnormal activity. The Connected to Physical Address item provides us with the WWN of the SAN device at the other end of each port.
The Ethernet/Fiber Port Traffic Report is a powerful tool to diagnose a performance issue in a
SAN: which servers are too demanding?
which disk array is under pressure?
what is the traffic caused by the backups (from the disk array to the tape library)?
are the "multi-pathing" links properly configured and the load shared among the different paths?
For the SAN administrator, it can also be a convenient way to inform one of his customers (a server administrator, or a person in charge of an application) of how much their servers are reading from or writing to a disk array, in total, per day.
This tool can be invoked from either the main hardware icon corresponding to the SAN switch, or from a group of ports (the Network Interfaces icon), or directly from a selected port instance.
Managing Data center Heating and Cooling issues
Even though data centers and servers are cooled with air conditioning and fans, computing systems may be overheated. Because overheating will lead to a general instability, Hardware Sentry monitors the fans present and all the temperature sensors. Automatic thresholds are set according to the manufacturers' recommendation and the location of temperature sensor. There is no need to customize the alert thresholds for temperature sensors and fan speeds.
The temperature thresholds set by Hardware Sentry should not be customized or modified.
Managing DataCenter Heating and Cooling issues consists in:
Monitoring the data center temperature
Monitoring the ambient temperature
Verifying the temperature of all the computing systems .
Monitoring the Data Center Temperature
You can prevent hardware overheating by properly cooling your server room. We recommend you to optimize the environmental temperature to prevent both hardware overheating and expensive energy bill.
User Guide
87
Hardware Sentry KM for PATROL
Version 1.8.01
1.
In the console, double-click the DegreesBelowWarning parameter located under the
CapacityReport icon ( MS_HW_CAPACITYREPORT application class). A graph is displayed in the
graph pane:
Monitoring the da ta ce nte r te m pe ra ture s
2.
If the number of degrees before warning threshold is: high, the temperature of your server room is too cold. You should therefore warm it to reduce your energy bill without risking hardware overheating close to zero, the temperature of your server room is probably too hot. zero, the temperature of your server room is definitively too hot. A warning will be triggered. It is then recommended to check the air-conditioning is properly working.
For more information about the Energy C ost C ontrol, please refer to this W hite Paper .
Monitoring the Cooling for the Servers
The temperature of the interior of the case of a server is controlled with fans. To prevent ambient temperature to get too high, ensure the fan is properly working:
1.
First verify the fan is available and spinning by respectively double-clicking the Missing and Status parameters of the
2.
Then double-click the:
Speed parameter to check its speed is not too fast or too low.
SpeedPercent parameter to make sure the fan has not reached its maximum speed.
Cooling might not be sufficient if the fan speed is too low or if maximum speed is reached.
User Guide
88
Hardware Sentry KM for PATROL
Version 1.8.01
A fan which is not spinning anymore or is turning too slowly should be replaced immediately.
Verifying the temperature of all your computing systems
You can create a PATROL query to verify the temperature of all your computing systems. Once executed, this query will display a list of results. Depending on your configuration, this list will either contain all the states or only the critical ones (e.g.: Warning and Critical).
1.
In the main menu bar of the PATROL Console, click Actions > New Query... to create a PATROL query
PA T ROL Que ry - Ge ne ra l ta b
User Guide
89
Hardware Sentry KM for PATROL
Version 1.8.01
2.
In the General tab:
Enter the Query name and description
In the Query Results Filter section, select Show Selected Objects and check the
Parameters box
In the Additional filtering section, select the Enable Application Class level filtering and
Enable Parameter level filtering options
3.
Open the Application Class tab
PA T ROL Que ry - A pplica tion Cla ss ta b
User Guide
90
Hardware Sentry KM for PATROL
Version 1.8.01
In the Pattern matching section, select Like and type MS_HW_TEMPERATURE
4.
Open the Parameter tab
PA T ROL Que ry - Pa ra m e te r ta b
If you only want to display the warning and critical results, choose Selected States and check the Warning and Critical boxes
In the Pattern Matching section, select Like and type Temperature
5.
Click OK.
Diagnosing Data Center Electrical Issues
Understanding the basics of the electrical distribution system will help IT administrators diagnose data center electrical issues. Power is delivered to a data center by the local utility company. Once inside the building, the utility power goes to the Automatic Transfer Switch and to the uninterruptible power supply
(UPS) units. These units clean the incoming utility system before passing it to power distribution units
(PDUs) for conversion. Power will finally be distributed to electrical outlets and servers. During the distribution, power loss or instability can occur. It can be caused by voltage or AC/DC conversion, hence the importance to monitor voltage and power supplies.
Monitoring Voltage
Monitoring voltage will help you verify the quality of your power supplies. In fact, if the power supply is weak, the voltage level on the motherboard will not be steady, which could lead to random crashes or to errors at the processor or memory levels.
User Guide
91
Hardware Sentry KM for PATROL
Version 1.8.01
1.
In the console, double-click the Voltage parameter of the MS_HW_VOLTAGE application class. A
graph is displayed in the graph pane
Monitoring Volta ge
2.
Verify the voltage is not fluctuating.
Higher voltage and fewer fluctuations in voltage will always guarantee better efficiency. If you notice voltage fluctuations, verify your electrical connections and wiring.
Monitoring Power supplies
After hard drives, the power supply is the device that is most likely to fail. The proper operation of this device highly depends on the quality of the data center electrical distribution. Indeed, voltage fluctuations are detrimental to power supplies: they can shorten their life span or impair them.
1.
In the console, double-click the Status parameter of the
MS_HW_POWERSUPPLY application class
to verify the power supply has not failed or is not degraded. Several power supply failures may reveal an issue on the data center electrical distribution
2.
You can also double-click the UsedCapacity parameter to make sure the power supply's maximum power output is not reached.
Reporting Electricity Consumption
As the energy prices go up and people realize that electricity production has also an ecological cost, IP departments recently started to look attentively to their electricity bill. In most cases, it's higher than expected and it is impossible to know which component in the IT infrastructure is consuming the most: the servers, the storage, the network, or the server room itself.
User Guide
92
Hardware Sentry KM for PATROL
Version 1.8.01
As the demand for more energy efficient servers grew up, server manufacturers started to release servers that were optimized with the electricity consumption in mind. To prove their point, server manufacturers finally instrumented their servers so that they were able to report their energy consumption “live”. Hardware Sentry leverages this information and exposes it with the
PowerConsumption parameter (in Watts) on the Enclosure class and as a total in the Capacity
Report object.
However, if most recent servers report their energy consumption, older one do not, and cannot benefit from any service pack or firmware upgrade to implement that functionality. If you want to know how much electricity is being consumed by an older server (or a really recent server, but not instrumented this way), you will need to use a physical power meter plugged between the server’s power supplies and the wall plug.
Starting with version 1.6.01 of Hardware Sentry, our product is able to estimate the power consumption of a server, based on its internal components. By knowing the characteristics of the different hardware components (processor model, maximum speed, current speed, number of memory modules, network card activity, etc.), Hardware Sentry provides you with a fairly accurate estimation of the electricity consumption (in Watts) of any monitored device (server, disk array, fiber switch, etc.).
When a server is not able to report its power consumption, the PowerConsumption parameter is not displayed under the Enclosure icon. It is only displayed under the Capacity Report icon. By visualizing the history of the PowerConsumption graph in the PATROL Console, you can observe the kind of activity that makes your server consumes more energy, if that is the case.
Ene rgy Usa ge Re port
If you know the electricity consumption for a server for which Hardware Sentry cannot automatically collect or calculate this value, you can enter this information in the system manually. Right-click the
Hardware icon > KM Commands > This System's Settings > Default Power Wattage.
The Default Power Wattage feature allows you to enter the electricity consumption for a given device.
Simply enter this value in Watts and Hardware Sentry will use this information in the
as well as for reporting the PowerConsumption parameter value.
User Guide
93
Hardware Sentry KM for PATROL
Version 1.8.01
Ma nua lly e nte r a de v ice powe r consum ption
One interesting way to exploit this information is to compare the PowerConsumption parameters of many different servers and see which ones (which brand) are the most energy wise. Knowing which type of servers consumes less energy can be an important decision factor when purchasing new servers.
W hile much attention has been paid to obtain the best accuracy possible in the power consumption estimation done by the KM, comparing an actual v alue (read from an electricity sensor) and an estimated v alue may lead to unex pected results.
In order to better understand the electricity bill, Hardware Sentry provides an Energy Usage report in kWh. Right-click the main hardware icon grouping the hardware components of a given server > KM
Commands > Reporting >
. Select a “daily” report for a several day period of time. The graph displayed in the PATROL Console shows the electricity that has been consumed by the device for each day. If you know the price of the kWh in your region, you can easily calculate the energy price for the server.
PowerC onsumption is ex pressed in W atts. It’s an instantaneous v alue, v ery much like a speed or a rate (megaby tes/ sec, e.g.). It represents how quickly the serv er is burning energy for its operation. The “Energy Usage” report is ex pressed in kW h (kilo W att hour). It represents the amount of energy consumed by the serv er in the specified interv al (hour or day ). The Energy Usage report in kW h is to the power consumption what distance is to speed:
Energy = Power x Time.
When it comes to lower the electricity bill, the very first step is to measure the current energy consumption. As Lord Kelvin put it: “If you cannot measure it, you cannot improve it." Then it is very interesting to observe what can have an impact on the power consumption of a given server. You can use the data collected by Hardware Sentry to correlate them with other KMs or external data. You may realize that the deployment of a specific application can have a significant impact of the electricity
User Guide
94
Hardware Sentry KM for PATROL
Version 1.8.01
consumption, because of its activity (an anti-virus program, for example).
Predicting Hardware Failures
Even though end-users expect the IT environment they rely on to be flawless, it is common knowledge that hardware components are inherently prone to failure. In most cases, electronic components work as expected or fail completely and it is rare to be able to observe such components degrade slowly over time. That’s why Hardware Sentry KM only reports the overall status for most object classes as simply
“okay” or “failed”.
However, some components are able to report their own degradation and warn the administrator of an imminent failure. Such components include: the processors (the more computation errors they detect and correct automatically, the more likely they will fail soon) the memory modules (an increasing number of fixed ECC errors means the module is nearing its end of life) the hard disks (many internal metrics are constantly analyzed by the disk itself to assess its own health and predict an imminent failure – this technology is standard and is called S.M.A.R.T.)
When such information is properly reported by the component, the instrumentation layer of the system itself, Hardware Sentry KM will trigger an event to warn the administrators that an imminent failure of a processor, a memory module or a physical disk is predicted.
1.
In the console, double-click the PredictedFailure parameter of the processor, memory module or physical disk you are interested in. Their application classes are respectively
Se le cting the Pre dicte dFa ilure pa ra m e te r
A graph is displayed in the graph pane. If this parameter is equal to 1 and goes into alarm, the faulty hardware should be replaced.
User Guide
95
Hardware Sentry KM for PATROL
Version 1.8.01
Recognizing Instrumentation Failures
Hardware Sentry KM does not “talk” directly to the hardware to assess its health. An instrumentation layer bridges the physical components and the software solution. The instrumentation layer can be a driver, a firmware, an API, an SNMP agent, a WBEM or WMI provider or an out-of-band management card with its own IP address. In 99% of the cases, the instrumentation layer is provided by the manufacturer along with the server.
Failures in the instrumentation layer itself do happen and it is important to discriminate these problems from actual hardware failures. System administrators will not take the same actions for an actual disk failure and for an SNMP agent crash, which in itself does not impact the availability and performance of the system.
Monitoring Connectors
The connection to each instrumentation layer is represented by an instance of the
class. The availability of the underlying technology is constantly verified and represented with the
Status parameter. When an instrumentation failure occurs, an alarm is triggered by the
MS_HW_CONNECTOR application class and all of the objects and parameters monitored through this
instrumentation layer are taken OFFLINE. This alarm reveals a monitoring issue only, which must be handled by PATROL administrators.
The TestReport parameter can give further information as it indicates whether the test completed successfully or not.
Example
User Guide
96
Hardware Sentry KM for PATROL
Version 1.8.01
Hardware Sentry is running on an HP Proliant server with HP Insight Management Agent.
Upon start up, Hardware Sentry detects the HP Insight Management Agent, and starts using the corresponding connector to discover the server hardware configuration and monitor the discovered devices.
Additionally, Hardware Sentry creates an icon in the PATROL Console representing the HP Insight
Management Agent - Server connector.
Every 2 minutes, its Status parameter is updated.
If, for some reason, the HP agent stops working, an alarm is raised on the Status parameter and the devices that were discovered through to this connector are taken offline.
Conne ctor Monitoring
This connector monitoring mechanism helps PATROL administrators detect hardware agent failures. It also provides a high monitoring accuracy by not confusing errors that are actually encountered by devices with errors stemming from a monitoring-tool failure.
When connectors are: automatically detected by Hardware Sentry, the connectors are grouped under an instance labeled
Detected Connectors.
manually selected – as for remotely monitored objects, the connectors are grouped under an instance labeled Selected Connectors.
To change the settings of connectors, right-click on Hardware > KM Commands > This System’s
Settings > Connection, Credentials and Connectors…
User Guide
97
Hardware Sentry KM for PATROL
Version 1.8.01
Reporting
This section deals with the various ways Hardware Sentry KM for PATROL enables you to create and schedule reports on the data collected from monitored devices.
Hardware Inventory Reports
IT administrators often need complete information about the hardware health of the managed system.
Hardware Sentry can generate an instant hardware inventory report that lists all the hardware components monitored on the system/remote device. This list details the monitored objects, their parameters, thresholds, etc., and describes errors or problems encountered, the possible consequences, and the actions recommended to solve the issues, if any.
Administrators can for instance:
schedule hardware inventory report
Instant Hardware Inventory Report
Because IT and virtualization technologies become more and more complex, administrators are now struggling to get a real hardware inventory and know exactly what is present on the machine they are working on. This information is however often required by the technical support of any hardware manufacturer.
User Guide
98
Hardware Sentry KM for PATROL
Version 1.8.01
To generate an hardware inventory report with Hardware Sentry:
1. right-click the Hardware icon > KM Commands > Reporting > Hardware Inventory. The following pane is displayed:
Ha rdwa re Inv e ntory Re port for a n e ntire sy ste m /de v ice
You can also generate a schedule hardware inventory report.
Scheduling Hardware Inventory Reports
Administrators can schedule automated generation of hardware inventory reports for the localhost and/ or any or all remote hosts monitored through it. The information retrieved as a text file can then be used by inventory tools. Because the information is up-to-date, administrators can easily find out if problems exist.
To schedule a hardware inventory report:.
User Guide
99
Hardware Sentry KM for PATROL
Version 1.8.01
1.
Right-click the Hardware icon > KM Commands > Reporting > Schedule Hardware
Inventory. The Hardware Inventory Scheduling wizard appears:
Sche dule Ha rdwa re Inv e ntory Re ports — W e lcom e
User Guide
100
Hardware Sentry KM for PATROL
Version 1.8.01
2.
The next panel asks you to select the hosts and to schedule the report:
Sche dule Ha rdwa re Inv e ntory Re ports — Se le ction
3.
Depending on the schedule selected, the following panels will appear:
Every hour: No additional settings required. The wizard displays the panel for macros and
destination folder (see step 4 .).
Every day at a specific time: Indicate the time at which the report is to be generated and click Next.
User Guide
101
Hardware Sentry KM for PATROL
Version 1.8.01
Sche dule Ha rdwa re Inv e ntory Re ports — Ev e ry da y
Every week at a specific time and day: Specify the time and the days you want the report generated and click Next.
Sche dule Ha rdwa re Inv e ntory Re ports — Ev e ry W e e k
Every month at a specific time and day: Indicate the day of each month and the time at which the report is to be generated and click Next.
User Guide
Sche dule Ha rdwa re Inv e ntory Re ports — Ev e ry m onth
102
Hardware Sentry KM for PATROL
Version 1.8.01
4.
Indicate where the report is to be saved and specify its filename:
Sche dule Ha rdwa re Inv e ntory Re ports — Ma cros a nd Re port de stina tion folde r
User Guide
103
Hardware Sentry KM for PATROL
Version 1.8.01
Save the Hardware Inventory in the following folder: Enter the file path
Use the following template for the Hardware Inventory filename: Indicate the path and folder where the report is to be saved and its filename. Available macros are listed in the
Actions Macro Variables section. Using the given macros will enable you to have reports that are
properly named with the hostname and time the reports are generated.
5.
A confirmation is finally displayed:
Sche dule Ha rdwa re Inv e ntory Re ports — Va lida tion
6.
Click Finish. The report will be automatically generated as per the specifications indicated.
You can also generate an
Instant Hardware Inventory report at any time for the whole managed system
or for any individual component.
Generating Capacity Reports
Administrators can create custom PATROL queries to generate detailed reports of the capacity of the monitored systems. These reports can for instance indicate the number of physical CPUs, the amount of memory, the overall size of disks and volumes, the number of connected ports, etc.
To generate these custom PATROL queries:
User Guide
104
Hardware Sentry KM for PATROL
Version 1.8.01
1.
In the main menu bar of the PATROL Console, click Actions > New Query... to create a PATROL query
PA T ROL Que ry - Ge ne ra l ta b
User Guide
105
Hardware Sentry KM for PATROL
Version 1.8.01
2.
In the General tab:
Enter the Query name and description
In the Query Results Filter section, select Show Selected Objects and check the Parameters box
In the Additional filtering section, select the Enable Parameter level filtering option
3.
Open the Parameter tab
PA T ROL Que ry - Pa ra m e te r ta b
In the Pattern Matching section, select Like and type:
CPUCount for a CPU report
MemorySize for a memory size report
ConnectedPorts for a connected ports report
PhysicalDiskSize for a physical disk size report
4.
Click OK.
Reporting Energy Usage
Energy consumption has emerged as important concerns in systems and services management. In order to provide accurate and helpful information on the energy consumed by hardware components,
Hardware Sentry provides an energy usage report that can be customized to show how the power is being consumed.
To generate an Energy Usage Report, right-click Hardware icon > KM Commands > Reporting >
Energy Usage Report.
User Guide
106
Hardware Sentry KM for PATROL
Version 1.8.01
1.
Define the report settings:
Ene rgy Usa ge Re port — Se ttings De finition
Select the data you wish to generate a report for: energy usage or power consumption 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
2.
Click the Show Reports button to display the graph.
Ene rgy Usa ge Re port — Gra ph
Reporting Ethernet/Fiber Port Traffic
Hardware Sentry enables you to generate a report showing usage statistics returned by a specific
Ethernet/fiber port. The reports shows the total number of received and transmitted bytes for the selected port. It can easily be customized to show the data that administrators can use to optimize network traffic.
User Guide
107
Hardware Sentry KM for PATROL
Version 1.8.01
To generate an Ethernet/Fiber Port Traffic Report, right-click the Hardware icon > KM Commands >
Reporting > Ethernet/Fiber Port Traffic Report.
1.
Define the report settings
Ethe rne t/Fibe r Port T ra ffic Re port — Se ttings De finition
Select the data you wish to generate a report for: bytes or packet 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
Select the Ethernet/Fiber port you wish to generate a report for: Click the Ethernet/Fiber Port
Selection button to display a list of available ports.
User Guide
108
Hardware Sentry KM for PATROL
Version 1.8.01
2.
Select an Ethernet/Fiber port
Ethe rne t/Fibe r Port T ra ffic Re port – De v ice Se le ction
Click on the port's name to select it. You can select up to 32 ports to be displayed on the same report.
Click Accept to validate you selection.
3.
Generate a usage report
User Guide
Ethe rne t/Fibe r Port T ra ffic Re port – Gra ph
Click the Show Reports button to display the graph.
109
Hardware Sentry KM for PATROL
Version 1.8.01
Administrative Tasks
This section deals with information on basic configuration and administrative tasks such as:
Set connection, credentials and connectors on the local host
Customize the polling interval
Pause / Resume the monitoring of an object
Terminate the monitoring of a device
Restore the monitoring of a device after removal
Show an instant Hardware Health report
Display labels in the UNIX Console mode
Automatically reset ErrorCount parameters
The Reference Guide has a section on C onfiguration Variables which contains list of global and host-specific configuration v ariables as well as macros. This information is also av ailable in an online format in the Hardware Sentry
Online Technical Library , as well as in the online help of the KM.
User Guide
110
Hardware Sentry KM for PATROL
Version 1.8.01
Hardware Sentry Menu Commands
Hardware is the main Hardware Sentry icon for each managed system. The menu commands available from this icon apply to the entire managed system.
Right-click the Hardware icon > KM Commands and then on one of the commands below:
KM Settings : Displays all the menu command options for different monitoring settings.
This System's Settings : Allows you to set system properties and credentials to be used for
monitoring.
Add a Remote System or an External Device : Enables you to monitor another system or an external
device remotely either SNMP, WMI, SSH/Telnet or WBEM.
Remove this system : Enables you to remove a system from the console.
Reporting : Provides various reports and enables you to schedule automated generation of hardware
health reports for all hardware components monitored.
Pause Monitoring : Enables you to pause the monitoring of the system
Resume Monitoring : Enables you to resume the monitoring that’s been paused
Reinitialize KM : Enables you to trigger a complete re-initialization of Hardware Sentry.
About: States basic product information and BMC Software support contact information
Reinitializing the KM
If ever Hardware Sentry does not function properly: displays devices as missing that you know are present, or does not detect several devices as it should etc., it is possible to reinitialize the configuration and let Hardware Sentry re-start monitoring from scratch.
The above cases of malfunction could occur after a configuration change or especially after a software/ hardware upgrade etc.
In such a case, you can reinitialize the KM, and Hardware Sentry will then run a full discovery and will re-detect the managed system, detect the appropriate connectors and re-start the monitoring of existing
& new devices. Thresholds will be set to default so all previously manually set thresholds will be lost, unless specified otherwise in the Reinitialize KM wizard shown below.
User Guide
111
Hardware Sentry KM for PATROL
Version 1.8.01
1.
To reinitialize Hardware Sentry: Right-click the Hardware icon > KM Commands > Reinitialize
KM:
User Guide
Re initia lize KM
112
Hardware Sentry KM for PATROL
Version 1.8.01
2.
Select the options as per your specific needs:
Alert thresholds and actions
Remove manually customized alert thresholds: Selection removes all customized thresholds.
Reset the threshold mechanism mode to default: Selection makes the KM revert to the default mode i.e. Hardware Sentry selects the mechanism is best suited to the system.
Reset Alert Actions: Selection removes all manually set Alert Actions and reverts to basic default actions i.e. Trigger a PATROL event and Annotate a parameter graph.
Reset other alert and threshold settings: Selection reverts any manually done configuration changes to default Hardware Sentry values.
Misc. options
Deactivate the debug mode: Selection deactivates the debug mode if manually enabled.
Restore and resume paused/removed objects: Selection restores all paused or removed objects.
Remove Hardware Health Report Schedule settings: Selection clears the report schedule.
Remove Java Settings: Selection removes the custom Java Settings (path and credentials).
The KM will try to automatically find a suitable JRE.
Monitoring settings for local host only
Force localhost monitoring: Selection restores the monitoring of the localhost when it has previously been removed with the
Remove the security settings: Selection clears all the security settings entered.
Unload connectors and perform a platform detection: Selection restarts the detection process.
Save reinitialize settings
Save reinitialize setting: Selection saves the defined settings that will then be considered as default.
In cases where configurations hav e been manually set in the PA TROL A gent, there will be an additional section called
Internal KM engine options display ing the used configuration v ariables and the option to remov e them.
3.
Click Reinitialize.
KM Commands for the Managed System's Settings
The KM commands for the managed system's settings are accessible by right-clicking the Hardware
icon > KM Commands > This System's Settings:
Connection, Credentials and Connectors to access security settings and connector selection
features.
Network Link Alerts to configure alerts that must be triggered when a break in the network link is
detected.
Default Power Wattage to provide the system with the electricity consumption for a given device.
Trigger a discovery to trigger a forced discovery and re-discover & detect the hardware
components.
User Guide
113
Hardware Sentry KM for PATROL
Version 1.8.01
Connection Credentials and Connectors on Local Host
In order to access
connector selection features, right-click the local host’s
Hardware icon > KM Commands > This System’s Settings > Connection, Credentials and
Connectors.
This wizard begins with
and is then followed by the connector selection step.
Security Settings
Conne ction Cre de ntia ls a nd Conne ctors on Loca l Host — Se curity Se ttings
User Guide
114
Hardware Sentry KM for PATROL
Version 1.8.01
SNMP Community
Hardware Sentry allows you to set or modify the SNMP community that will be used for SNMP queries.
Enter the custom SNMP community string in the first field or leave this field blank if you want Hardware
Sentry to automatically detect the SNMP community (public). Using an alternate SNMP community can be required in secured network environments where all the SNMP agents are configured in a customized community.
The KM on supports SNMP v 1.
Alternate User Account
Enter the user credentials of the alternate account to execute external commands, or leave blank to consider the default PATROL account.
Using an alternate account, i.e. an account different from the default PATROL account to execute external commands is required in some secured systems where the default PATROL account does not have all the privileges required in order to perform commands on certain hardware devices.
Restart the PA TROL agent in order to ensure that the modified settings take effect.
Sudo Options (UNIX/Linux)
Depending on the targeted platform, Hardware Sentry may use some external system utilities to gather hardware information. Sometimes the PATROL Agent default account does not have sufficient privileges to execute these commands and it is not possible in your environment to give super-user rights to the
PATROL Agent (as described above). In such case Hardware Sentry can use the "sudo" utility to execute external commands as "root". The "sudo" utility helps UNIX system administrators secure their environment by authorizing some users to execute only certain commands specified as another user account (typically root). If this applies to you, the "sudo" options feature could be a good workaround.
User Guide
115
Hardware Sentry KM for PATROL
Version 1.8.01
Conne ction Cre de ntia ls a nd Conne ctors on Loca l Host — Sudo Options
Commands: Select the commands Hardware Sentry should execute using the "sudo" utility.
Command line to execute the sudo utility: Enter the command line, or, leave the field blank to use the default /usr/local/bin/sudo path.
Ensure that the sudo utility is installed on the sy stem, and that the "/etc/sudoers" file is configured to allow the
PA TROL A gent to ex ecute the selected commands as root.
Here is the procedure to configure Hardware Sentry to use "sudo":
Identify the commands run by Hardware Sentry that require advanced privileges.
Configure "sudo" to allow the PATROL Agent default account to execute the needed commands as root (modify the /etc/sudoers file). Configuring "sudo" requires root privileges.
Check that the PATROL Agent default account is properly authorized to execute the needed commands through the "sudo" utility.
Access the Hardware Sentry Security Settings panel: Hardware icon > This Systems’s Setting
> Connection, Credentials and Connectors > Sudo options.
Check the boxes corresponding to the commands that have been configured in "sudo".
For more information about using 'sudo" in Hardware Sentry KM, please refer to the KB article #1080 av ailable on the
Sentry W eb site.
User Guide
116
Hardware Sentry KM for PATROL
Version 1.8.01
The next panel asks for WBEM credentials:
WBEM
Conne ction Cre de ntia ls a nd Conne ctors on Loca l Host — W BEM Cre de ntia ls
Enter the WBEM credentials or leave blank if using default PATROL account credentials and click Next.
The next panel allows you to decide which mode is to be used for selecting connectors.
Connector Selection
Two choices are possible:
Let Hardware Sentry detect which connectors to use: In this mode, Hardware Sentry will run tests at each discovery and select the connectors that best match the managed system.
Manually choose the connectors: Selecting this option lets you decide which connectors
Hardware Sentry should use to monitor the system Hardware.
W hen the panel comes up, the selected option is the one that is currently in use.
The first option: Let Hardware Sentry detect which connectors to use is recommended and is used by default when Hardware Sentry is loaded on a PATROL Agent.
The detection process is very efficient and accurate, and generally, does not use the computer’s
User Guide
117
Hardware Sentry KM for PATROL
Version 1.8.01
resources extensively. Clicking on the Next button will bring up a panel with a message stating that
Hardware Sentry needs to be reinitialized to run the detection process again.
If manual selection is chosen (essential for remote monitoring), the next panel displays a list of connectors to choose from. It is possible to select several connectors from the list by simply clicking on them. De-selecting a connector is also performed by clicking on the item on the list.
A t the end of the selection wizard, Hardware Sentry runs a full discov ery . A ll dev ices and sensors are re-detected. If the connector list differs from what Hardware Sentry was using prev iously , new dev ices monitored may appear in the
PA TROL C onsole and old ones may be remov ed. If this is the case, pay close attention to the PA TROL Sy stem Output
W indow for error messages. A poor selection of connectors may remov e all dev ices and sensors and may prev ent
Hardware Sentry from being able to monitor the sy stem’s hardware!
Final Step
Clicking the Next button brings up a panel with a message stating that Hardware Sentry needs to delete the host instance in the PATROL Console and perform a new discovery of the host.
Conne ction Cre de ntia ls a nd Conne ctors on Loca l Host — Pe rform a Ne w Host Discov e ry
Click Finish.
User Guide
118
Hardware Sentry KM for PATROL
Version 1.8.01
Connection, Credentials and Connectors for Remote Hosts
In order to access
connector selection features, right-click the remote system's
Hardware icon > KM Commands > This System’s Settings > Connection, Credentials and
Connectors.
1.
Right click the remote system's Hardware icon > KM Commands > Add a Remote System or
an External Device...
Monitor a Re m ote Sy ste m or a n Ex te rna l De v ice — Lice nse A gre e m e nt
User Guide
119
Hardware Sentry KM for PATROL
Version 1.8.01
Read the license agreement, accept it and click Next to continue.
2.
Identify the system or device you want to monitor remotely and click Next.
Monitor A nothe r Sy ste m Re m ote ly — Sy ste m Ide ntifica tion
User Guide
120
Hardware Sentry KM for PATROL
Version 1.8.01
System or Device name: Enter the name of the system or device you wish to monitor
IP address or fully qualified name: Leave this field blank if you specify the host name above
System or Device type: Select a platform from the drop down list to specify the system or device type.
3.
Select the Automatic option and at least one of the proposed protocols to let the KM automatically detect the suitable connectors for the monitored system/device; or select the Manual option and click Next to manually select a connector.
Based on the specified system type, the KM lists the available protocols to monitor the remote system/device.
Monitor A nothe r Sy ste m Re m ote ly — Conne ctor Se le ction Mode
User Guide
121
Hardware Sentry KM for PATROL
Version 1.8.01
4.
The KM allows you to select the connectors for Hardware Sentry to use to monitor the remote system/device. The list of displayed connectors depends on the monitored system/device. Select the appropriate connectors and click Next.
User Guide
Monitor A nothe r Sy ste m Re m ote ly — Conne ctors Se le ction
The following steps depend on the sy stem/dev ice ty pe of the remote element and the protocols used to connect to
in the Reference Guide.
122
Hardware Sentry KM for PATROL
Version 1.8.01
If the connectors selected use SNMP, this panel appears:
Monitor A nothe r Sy ste m Re m ote ly — SNMP Com m unity String
SNMP community string: Enter the SNMP community string and click Next.
The KM only supports SNMP v 1.
If the connectors selected use WMI or WBEM these panels appear asking for connection
credentials:
User Guide
123
Hardware Sentry KM for PATROL
Version 1.8.01
Monitor A nothe r Sy ste m Re m ote ly — W MI Que rie s Cre de ntia ls
Monitor A nothe r Sy ste m Re m ote ly — W BEM Que rie s Cre de ntia ls
WMI/WBEM credentials: Enter the WMI/WBEM credentials and click Next.
Click on the Advanced Options button to access specific settings related to the WBEM connection:
User Guide
124
Hardware Sentry KM for PATROL
Version 1.8.01
Monitor A nothe r Sy ste m Re m ote ly — W BEM Cre de ntia ls — A dv a nce d Options
Enter the IP address/Host-name of the Multi-tier Authentication Server (This option mostly is used for VMware servers).
Enter the WBEM namespace or leave the field empty to let the KM automatically detect the proper name (recommended). If the WBEM credentials are not provided, Hardware Sentry will authenticate using the credentials provided in the previous panel (WBEM Credentials). This therefore disables multi-Tier authentication.
Click Accept to validate your changes.
If the connectors selected require Telnet or SSH to connect to the remote element, the following panel appears:
Monitor A nothe r Sy ste m Re m ote ly — Scripts Cre de ntia ls
User Guide
125
Hardware Sentry KM for PATROL
Version 1.8.01
Connect to [System/Device] using the following protocol: Select either Telnet or SSH and enter the credentials required to execute the protocols and click Next.
Login and Password: Enter the login and password that Hardware Sentry is required to use to connect to the system/device to monitor.
Sudo options: On UNIX/Linux platforms, you have the option of permitting Hardware Sentry to use the Sudo utility to execute external commands using root.
Monitor A nothe r Sy ste m Re m ote ly — Sudo Options
User Guide
126
Hardware Sentry KM for PATROL
Version 1.8.01
If the connectors selected use the IPMI protocol, the following panel appears:
Monitor A nothe r Sy ste m Re m ote ly — IPMi Protocol
Username: credentials to connect to the IPMI chip out-of-band (IPMI-over-LAN)
Password: password associated to the specified username
If the connectors selected use the Cisco UCS XML API protocol, the following panel appears:
User Guide
127
Hardware Sentry KM for PATROL
Version 1.8.01
Monitor A nothe r Sy ste m Re m ote ly — Cisco UCS XML A PI Protocol
Encrypt data: Select this option to encrypt the communication between the KM and Cisco UCS
Manager using SSL (HTTPS)
Username: credentials valid on the specified Cisco UCS Manager
Password: password associated to the specified username
Final Step in the remote monitoring wizard is common to all platforms/systems. Click Finish and
Hardware Sentry will perform a new full discovery to detect this new remote system.
The Hardware icon for the local host will change to Hardware on localhost and an icon labeled
Hardware on <remotehostname> will appear. This represents the system/device you are now monitoring remotely, along with icons for all of the detected parameters of this remote system/device.
Triggering a Discovery
Hardware Sentry automatically executes a discovery every hour of all hardware objects for the monitored system. This enables discovering and then monitoring any new objects added or removed on the monitored environment.
You can force a discovery manually by right-clicking on the Hardware icon > KM Commands > This
System's Settings > Trigger a Discovery. This forces a discovery for the selected host only.
W ith a v iew to optimization, the discov ery process is as paralleled as possible. A ll independent objects are processed at the same time.
Disabling Localhost Monitoring
Disabling the monitoring of the localhost maybe useful when you need to monitor exclusively remote systems, such as blade chassis for example.
To disable the localhost monitoring click the localhost icon > KM Commands > Remove this
System.
To re-add the localhost monitoring, you need to perform a Reinitialize KM.. Command and select the
Force localhost monitoring option.
User Guide
128
Hardware Sentry KM for PATROL
Version 1.8.01
Re -a dding the m onitoring of the loca lhost
Localhost monitoring will be automatically re-added if there is no host to monitor.
User Guide
129
Hardware Sentry KM for PATROL
Version 1.8.01
KM Commands for KM Settings
KM Settings
Alert Actions: Enables you to select the
Alert Actions i.e. different notification methods to be
executed by Hardware Sentry when a parameter breaches its threshold.
Deactivate Device Class: Allows you to set aside
device classes from the monitoring process
and, therefore, discard the performance metrics for those specific devices to be taken into account by the KM.
Missing Device Detection: Allows you to disable the
missing device detection feature. By default,
Hardware Sentry detects "missing devices" i.e. devices previously monitored but which have disappeared during the monitoring or after a reboot or due to some other cause
Intrusion Detection Alerts: Allows you to decide when an
for the enclosure/ systems chassis should be raised
The IntrusionStatus parameter of each enclosure object discovered by Hardware Sentry reports whether or not the chassis has been opened, and triggers an alarm as per user settings.
Automatic ErrorCount Parameters Reset...: Enables you to
reset the ErrorCount parameters
of a specific device
Discovery Interval: Enables you to customize the
. By default, discovery is performed every hour
Polling Interval: Enables you to customize the polling cycle
. By default, the polling interval is done every two minutes.
Java Settings...: Defines which Java instance is to be used by Hardware Sentry.
Debug...: Activates or deactivates the
Additional Settings
Additional Settings allow you to:
Select the threshold mechanism to be used:
Automatic (by default): Hardware Sentry determines the mode of threshold management to apply to the system, that is the Event Management method will be used if the Event Management
KM is in the list of preloaded KMs on the agent, otherwise, the Tuning method will apply.
Tuning: Hardware Sentry uses the internal PATROL mechanism to set thresholds
Event Management: Hardware Sentry automatically sets thresholds through Event
Management
No Thresholds: Hardware Sentry does not set any thresholds and lets you specify them manually
Unknown Status Management: Allows you to select the actions
to be performed if Hardware
Sentry returns an "Unknown" status when it is unable to detect a device or sensor.
User Guide
130
Hardware Sentry KM for PATROL
Version 1.8.01
Restore Device or Sensor Monitoring: Brings up the Restore Device or Sensor Monitoring
wizard to restore one or several objects after their monitoring has been stopped (if removed).
Display Settings for UNIX Consoles: Gives you the option to turn on the UNIX console mode and
modify all object labels to fit the PATROL UNIX Console label size.
Enabling the Debug Mode
By default, Hardware Sentry sends only the most critical information, warning and error messages to the System Output Window of the PATROL Consoles. Most often, this information is accurate enough to ensure that Hardware Sentry is working properly.
If you encounter an issue and wish to report it to Sentry Software, you will be asked to enable the
Debug Mode and provide the debug output to the Sentry Software support team.
To enable the debug mode:
1.
Right-click the main KM icon > KM Commands > KM Settings > Debug...
Ena bling the De bug Mode
2.
Check the Enable Debug Mode option
3.
Indicate the time when the debug mode will be disabled. The required format is: mm/dd/yyyy hh: mm:ss) based on a 24 hour-day.
By default, the debug mode is set to stop automatically after one hour.
3.
Click OK. The debug files will automatically be saved in $PATROL_HOME/log.
User Guide
131
Hardware Sentry KM for PATROL
Version 1.8.01
Customizing the Discovery Cycle
Hardware Sentry performs discoveries to detect new hardware components or detect those that have gone missing.
By default, the Hardware Sentry runs a discovery every hour, but you can customize this interval by right-clicking on the Hardware icon > KM Commands > KM Settings > Discovery Interval.
Custom izing Discov e ry Cy cle
Customizing the Polling Interval
Hardware Sentry polls the managed systems to collect hardware health data. By default, the polling interval for this "data-collect" is set to every 2 minutes.
To change the polling interval for the managed system, right-click on the Hardware icon > KM
Commands > KM Settings > Polling Interval…
User Guide
132
Hardware Sentry KM for PATROL
Version 1.8.01
Custom izing Polling Inte rv a l
In addition to the polling interv al that is a global setting, i.e. it is applicable to the whole managed sy stem, y ou can also manually trigger a poll at any time on indiv idual instances to refresh parameter v alues. Right-click on the instance icon > Refresh Parameters.
Java Settings
The Java Settings wizard enables you to define which Java instance is to be used by Hardware Sentry.
You can either use the automatic detection, select a pre-detected java path or enter manually the path leading to the Java executable directory to be used.
Performing Telnet, SSH or W BEM-based collection (i.e. for most remote Linux and UNIX sy stems, and most storage sy stems) require Jav a Runtime Env ironment (JRE) v ersion 1.5 or higher.
A pa che J RE is not supporte d.
To access the Java Settings wizard, right-click the main Hardware icon > KM commands > KM
Settings > Java Settings.
User Guide
133
Hardware Sentry KM for PATROL
Version 1.8.01
J a v a Se ttings W iza rd — W e lcom e Pa ge
Select the Java executable detection method: Select one of the three following options:
: Select this option if you wish Hardware Sentry KM to try and detect the Java
executable directory by itself upon each discovery.
: Select this option if you wish to select a Java executable directory within a list of
pre-detected executables on the managed system.
: Select this option if you wish to manually enter the Java executable directory path.
Click Next to continue.
User Guide
134
Hardware Sentry KM for PATROL
Version 1.8.01
Automatic
If you have selected the automatic detection at the previous step of the wizard, Hardware Sentry KM displays the path of the Java executable directory that will be used when performing commands requiring Java features.
J a v a Se ttings W iza rd — A utom a tic De te ction
You can use a specific account to run Java on the managed system or leave the field blank for using the current valid PATROL account.
Click Finish to save your settings.
User Guide
135
Hardware Sentry KM for PATROL
Version 1.8.01
User Selection
If you have selected the user selection option at the previous step of the wizard, Hardware Sentry KM displays a list of all the Java executable directories found on your machine.
J a v a Se ttings W iza rd — Use r Se le ction
Select the Java executable directory you wish Hardware Sentry KM to use when performing commands requiring Java features. You can use a specific account to run Java on the managed system or leave the field blank for using the current valid PATROL account.
Click Finish to save your settings.
User Guide
136
Hardware Sentry KM for PATROL
Version 1.8.01
Manual
J a v a Se ttings W iza rd — Ma nua l J a v a pa th ide ntifica tion
If you have selected the Manual option at the previous step of the wizard, Hardware Sentry KM let you enter the path to the Java executable directory you wish Hardware Sentry KM to use when performing commands requiring Java features. You can use a specific account to run Java on the managed system or leave the field blank for using the current valid PATROL account.
Click Finish to save your settings.
Once you have modified the Java setting, you must restart the PATROL Agent in order to make your changes effective.
User Guide
137
Hardware Sentry KM for PATROL
Version 1.8.01
J a v a Se ttings W iza rd — Re sta rt the PA T ROL A ge nt
Click OK and restart the PATROL Agent.
User Guide
138
Hardware Sentry KM for PATROL
Version 1.8.01
Deactivating Device Class
Hardware Sentry KM for PATROL allows you to set aside device classes from the monitoring process and, therefore, discard the metrics and performance data for those specific devices to be taken into account by the KM.
The KM will not trigger any alarm if a failure on a discarded device were to occur.
To deactivate a device class:
1. Right-click Hardware Sentry KM icon > KM Commands > KM Settings > Deactivate Device
Class...
2. Select the device class(es) you wish to discard from the monitoring process:
De a ctiv a te De v ice Cla ss
3. Click OK to confirm.
To reintegrate a previously discarded device class, simply uncheck the corresponding option in the
Deactivate Device Class window.
User Guide
139
Hardware Sentry KM for PATROL
Version 1.8.01
Missing Device Detection Mechanism
The missing device detection mechanism of Hardware Sentry alerts operators when a device that was previously detected in the system is no longer found.
This mechanism is very useful when, for example, a non-redundant physical disk does not restart during a system reboot and therefore is no longer seen by the operating system and the monitoring software.
When a device is no longer discovered, its Missing parameter goes into alarm. The missing device detection feature is enabled by default. You can however deactivate the feature by right-clicking the
Hardware icon > KM Commands > KM Settings > Missing Device Detection.
Missing De v ice De te ction
Disabling this option when some missing dev ices hav e already been detected will trigger a remov al of these dev ices from the monitoring env ironment.
User Guide
140
Hardware Sentry KM for PATROL
Version 1.8.01
Automatic ErrorCount Parameters Reset
ErrorCount parameter (as in the physical disk and memory classes) keep increasing as new errors are encountered. When no error occurs, the ErrorCount parameter remains at zero. When one error occurs, the ErrorCount parameter is increased to 1 (one), and retains this value until it is acknowledged by an operator. When another error occurs, the ErrorCount parameter is automatically increased to 2 (two), and again, it retains this value until it is acknowledged by an operator.
The DeviceNotReadyErrorCount, MediaErrorCount, NoDeviceErrorCount, HardErrorCount,
IllegalRequestErrorCount, RecoverableErrorCount, and TransportErrorCount parameters provide detailed information about the type of errors encountered on the physical disks.
To reset the ErrorCount parameters of a specific device, an operator must manually activate the
Acknowledge ErrorCount Alerts and Reset command via the console menu (right-click the device icon> KM Commands > KM Settings > Acknowledge ErrorCount Alerts and Reset).This
mechanism makes sure that an operator or an administrator is aware of the encountered error.
However, since the manual acknowledgment of each error can rapidly become time consuming,
Hardware Sentry KM can be configured to automatically acknowledge an alert on the ErrorCount parameters and reset it to zero after a specified period of time.
To set the automatic ErrorCount parameters reset for a specific device, right-click the Hardware icon
> KM Commands > KM Settings > Automatic ErrorCount Reset:
A utom a tic ErrorCount Re se t
Select the period of time after which you want the KM to automatically reset the ErrorCount parameter and click OK.
User Guide
141
Hardware Sentry KM for PATROL
Version 1.8.01
In many cases, a hardware error that does not reoccur after a certain amount of time can be safely ignored.
A utomatically resetting ErrorC ount parameters to zero after a few hours is often considered as a good practice.
Restoring Device Monitoring
It is possible to restore device monitoring with Hardware Sentry after it has been removed from monitoring through the Remove option.
To see the list of the removed objects or to restore a device monitoring:
1.
Right-click the Hardware Sentry main icon > KM commands > KM Settings > Additional
settings > Restore Device or Sensor Monitoring.
Restore Dev ice Monitoring — Selecting all
2.
Select:
<All> if you want to restore the monitoring of all the devices that had been previously removed, in the PATROL Console
One or more objects if you only want to restore specific devices (press down the Ctrl-key to allow multiple selection)
3.
Click Restore.
User Guide
142
Hardware Sentry KM for PATROL
Version 1.8.01
UNIX Console Mode
The PATROL UNIX Console has a label size limitation. This could mean that at times, object labels do not display in their entirety. You can opt for turning on the UNIX Console Mode that modifies all labels to fit the PATROL UNIX Console size limitation.
To access the UNIX Console mode settings, right-click the Hardware icon > KM Commands > KM
Settings > Additional Settings > Display Settings for UNIX Console:
UNIX Console Mode Se ttings
Turning on the UNIX Console mode will affect the labels of ALL PATROL consoles including the
Windows Consoles for the given PATROL Agent. If you have a mix of UNIX and Windows, it is recommended to leave this feature disabled.
User Guide
143
Hardware Sentry KM for PATROL
Version 1.8.01
KM Commands for the Monitored Devices
The KM commands that are offered by right-clicking on a monitored hardware component/device are:
Instant Hardware Health Report
: Displays an instant report about the health of a device.
Pause Monitoring : Enables you to pause the monitoring of the hardware component
Resume Monitoring : Enables you to resume the monitoring that had previously been paused
Remove : Allows you to remove the object from the monitoring environment
Refresh Parameters : Allows you to refresh the parameters of the monitored object
Acknowledge "X" Alert/Acknowledge Error Count Alerts and Reset etc.
component/device monitored and the type of system it is monitored on, there may be certain additional commands to acknowledge alerts, or acknowledge alerts and reset the error count etc.
For instance, in the case of Network Interfaces there is an additional command: Acknowledge
LinkStatus Alert
Device-container KM commands
Hardware Sentry creates "containers" for each device. For instance, an icon is created for Network
Interfaces under which all actual network interfaces discovered will be grouped.
Each "device container" has commands such as: Pause Monitoring; Resume Monitoring; Remove;
Refresh Parameters whose actions are applicable to all objects under it.
The Reference Guide lists all the menu commands for each application class along with parameter details.
Showing Instant Hardware Health Report
The Show Instant Hardware Health Report KM command enables you to generate an instant report on the hardware health of the selected hardware component.
You can view the hardware health report of a specific monitored hardware component by right-clicking on the component icon > KM Commands > Instant Hardware Health Report.
User Guide
144
Hardware Sentry KM for PATROL
Version 1.8.01
Insta nt Ha rdwa re He a lth Re port for a spe cific ha rdwa re com pone nt
This health report gives information about the monitored object (parameters, thresholds, connectors etc.) as well as a description of the problems encountered, the possible consequences, and actions recommended to solve the issues, if any.
Refreshing Parameters
To manually refresh parameters of the Hardware Sentry KM for PATROL, without waiting for an automatic polling cycle, right-click the instance icon > Refresh Parameters.
Pausing/Resuming Monitoring
In order to perform certain tasks - maintenance for example, it is often useful to pause the monitoring of an object or even of the whole system by Hardware Sentry.
Right-click the component/system icon > Knowledge Module Commands > Pause Monitoring
When in paused state, the object/system is still displayed in the PATROL Console but in an OFFLINE status and no collect for that particular object is executed.
To restart the monitoring of the object/system click Resume Monitoring in the menu.
User Guide
145
Hardware Sentry KM for PATROL
Version 1.8.01
Terminating the Monitoring of a Device
It may happen that information about a device is received by Hardware Sentry through two different sources. In such a (rare) case, the monitoring of the device is performed twice and the icon of the device in question will also appear twice in the PATROL Console.
In order to avoid such redundancy, or, if you wish to simply stop monitoring a device, there is a simple way to terminate the monitoring of the device (or a redundant device) in the PATROL Console:
Right-click the component/device icon > KM Commands > Remove.
The device is now removed from monitoring, which means collection for this particular device will no longer be performed, and the redundant icon representing the device will disappear from the PATROL
Console.
User Guide
146
Hardware Sentry KM for PATROL
Version 1.8.01
Managing Thresholds, Alerts and Notifications
Several mechanisms exist to manage thresholds in Hardware Sentry:
The Tuning method: Hardware Sentry will manage its thresholds through the standard internal
PATROL mechanism (Override parameters). Thresholds are stored in the PATROL Agent configuration under the /___tuning___ tree.
The Event Management method: The KM will manage its thresholds through the Event
Management mechanism. Thresholds are stored in the PATROL Agent configuration under the /AS tree. This option requires that you set up the PATROL for Event Management KM on your PATROL
Agent. PATROL for Event Management has to be enabled and preloaded.
No threshold: Hardware Sentry does not set any thresholds and lets you set them manually.
Since version 1.8.01, when Hardware Sentry KM for PATROL runs for the first time, alert thresholds are automatically set according to the selected threshold mechanism. Alert thresholds can however be customized by the administrators later on, if required, using the standard BMC PATROL administration tools (refer to BMC PATROL documentation for further details on BMC PATROL administration tools).
Additionally, administrators can set alerts actions to specify which actions will be executed when a hardware failure is detected (see
Selecting the Threshold Mechanism
By default, Hardware Sentry automatically determines which mechanism (Tuning or Event Management) is best suited to the managed system when it first runs. This threshold mechanism selection can however be modified later on through the Threshold Mechanism Selection KM Command:
1.
Right-click the main Hardware Sentry/local host icon > KM Commands > KM Settings >
Additional Settings > Threshold Mechanism Selection...
T hre shold Me cha nism Se le ction
1. Select one of the following options:
User Guide
147
Hardware Sentry KM for PATROL
Version 1.8.01
Tuning: If selected, Hardware Sentry will manage its thresholds through the standard internal
PATROL mechanism (Override parameters). Thresholds are stored in the PATROL Agent configuration under the /___tuning___ tree.
Event Management: If this option is selected, the KM will manage its thresholds through the
Event Management mechanism. Thresholds are stored in the PATROL Agent configuration under the
/AS tree. This option requires that you set up the PATROL for Event Management KM on your
PATROL Agent. PATROL for Event Management has to be enabled and preloaded.
No Thresholds: Hardware Sentry will not set any thresholds on the monitored objects. You are required to set them manually.
In order to avoid side effects and unpredictable behavior, if you change the thresholds management option from one method to another, Hardware Sentry will automatically migrate the instance specific thresholds to the other mode and will reset the ANYINST/ALL_INSTANCES thresholds with default values. Note that a backup of the Hardware Sentry thresholds configuration is made prior to the migration.
Modifying Alert Thresholds
Since version 1.8.01 of Hardware Sentry KM for PATROL, all thresholds can be customized using the standard BMC administration tools.
For further details, please refer to the BMC PA TROL documentation.
Alert Actions
Alert Actions enables the PATROL administrator to choose specific actions to be executed when a hardware failure is detected. With Alert Actions, it is possible to either:
Customize the way a hardware problem notification is performed, or
Specify a recovery action to be run when a problem occurs.
Hardware Sentry can be configured to run one, several, or all types of Alert Actions when an alert is triggered regarding the monitored hardware.
By default, upon hardware failure, Hardware Sentry triggers a PATROL event and annotates the parameter’s graph with a comprehensive report of the problem, giving details about the failure, the possible consequences and the recommended action to solve the problem.
The Alert Actions that can be performed by Hardware Sentry are:
User Guide
148
Hardware Sentry KM for PATROL
Version 1.8.01
Annotate the parameter's graph
Send a pop-up to the PATROL consoles
Send a basic SNMP trap (using the PATROL MIB)
Alert Actions are highly customizable. One can customize the string that is sent through SNMP, set the username/password that is used to execute the OS Command, define the content of the PATROL event sent by Hardware Sentry, etc.
Additional information regarding the alert, such as the parameter name or its value, is available through
by Hardware Sentry and provide more details about the problem that occurs.
User Guide
149
Hardware Sentry KM for PATROL
Version 1.8.01
Edit Alert Actions
To modify the Alert Actions executed by Hardware Sentry upon a hardware failure, right-click on the main Hardware icon > KM Commands > KM Settings > Edit Alert Actions…
Select the Alert Actions to be executed
Check the boxes corresponding to the actions you would like executed upon a hardware failure.
By default, Hardware Sentry triggers a PATROL event and annotates the parameter that raises the alert, but there are all the actions that can be triggered:
Editing A le rt A ctions — Se le cting Pa ra m e te rs
User Guide
150
Hardware Sentry KM for PATROL
Version 1.8.01
Annotate the parameter's graph
Send a pop-up to the PATROL consoles
Send a basic SNMP trap (using the PATROL MIB)
Trigger a PATROL event
If you select Trigger a PATROL Event, you need to enter the string that will be displayed with the event.
Editing A le rt A ctions — A le rt A ction: T rigge r a PA T ROL Ev e nt
A PATROL Event can be viewed from:
Standard PATROL Consoles (Classic Console, PATROL Central)
PATROL Enterprise Manager
BMC Impact Manager
Other third-party products that interface with PATROL.
The PA TROL ev ent that is triggered is the ‘41’ ev ent from the standard PA TROL catalog. You can use macros that will
av ailable macrosA lert_A ctions_.
User Guide
151
Hardware Sentry KM for PATROL
Version 1.8.01
Annotate the parameter’s graph
If you select the Annotate the parameter’s graph action, you need to enter the string that will be displayed within the annotation point.
Editing A le rt A ctions — A le rt A ction: A nnota te Pa ra m e te r's Gra ph
You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables
*A lert_A ctions_Macro_Variabsection states the list of av ailable macrosA lert_A ctions_.
User Guide
152
Hardware Sentry KM for PATROL
Version 1.8.01
Execute an OS command
If you select the Execute an OS command action:
Editing A le rt A ctions — A le rt A ction: Ex e cute a n OS Com m a nd
Enter a command line to be executed
Enter the username and password used to run the command.
The command can be a program utility or a script shell, and can have arguments.
The command must be non-interactive (no window, no user input)
You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables
*A lert_A ctions_Macro_Variabsection states the list of av ailable macrosA lert_A ctions_A lert_A ctions_.
User Guide
153
Hardware Sentry KM for PATROL
Version 1.8.01
Execute a PSL command
If you select the Execute a PSL command action, you need to enter the PSL statement to be executed by the PATROL Agent. Although only a single line is permitted, it can have several PSL instructions.
Editing A le rt A ctions — A le rt A ction: Ex e cute a PSL Com m a nd
The PSL command is recommended for advanced user of PATROL.
You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables
*A lert_A ctions_Macro_Variabsection states the list of av ailable macrosA lert_A ctions_.
User Guide
154
Hardware Sentry KM for PATROL
Version 1.8.01
Send a pop-up to the PATROL Consoles
If you select the Send a pop-up to the PATROL Consoles action, you need to enter the message that will be displayed in the pop-up as well as the title of the pop-up window.
Editing A le rt A ctions — A le rt A ction: Se nd a Pop-up to the PA T ROL Console s
Too many pop-ups could annoy the operators.
You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables
*A lert_A ctions_Macro_Variabsection states the list of av ailable macrosA lert_A ctions_.
User Guide
155
Hardware Sentry KM for PATROL
Version 1.8.01
Write a line to a LOG file
If you select the Write a line to a LOG file action:
Editing A le rt A ctions — A le rt A ction: W rite a Line to a LOG File
Enter the LOG file path and the content of the line.
You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables
*A lert_A ctions_Macro_Variabsection states the list of av ailable macrosA lert_A ctions_.
User Guide
156
Hardware Sentry KM for PATROL
Version 1.8.01
Send a basic SNMP trap
If you select the Send a basic SNMP trap action:
Editing A le rt A ctions — A le rt A ction: Se nd a Ba sic SNMP T ra p
Enter the following:
IP address or hostname of the SNMP trap destination
SNMP port and community string
Text that will be sent in the SNMP trap
Upon a hardware failure, Hardware Sentry will send the trap that is defined in the PA TROL MIB (Trap number 11,
Enterprise ID: 1.3.6.1.4.1.1031.1.1.2, the tex t is stored in the 1.3.6.1.4.1.1031.1.1.2.1 OID). You can use macros
of av ailable macrosA lert_A ctions_.
User Guide
157
Hardware Sentry KM for PATROL
Version 1.8.01
Send a custom SNMP trap (advanced)
If you select the Send a custom SNMP trap action, you need to enter the following:
Editing A le rt A ctions — A le rt A ction: Se nd a Custom SNMP T ra p
Enter the following:
User Guide
158
Hardware Sentry KM for PATROL
Version 1.8.01
IP address or hostname of the SNMP trap destination
SNMP port and community string
All the characteristics of the trap: Enterprise ID, trap number and up to 4 varbinds.
Send an E-mail
If you select the Send an E-mail action, you need to complete the following panel:
A le rt A ctions: Se nd a n E-m a il
Enter the sender and the recipient email addresses in respectively the From and To fields, and type the
SMTP server name. Finally, enter the email Subject and type the Body of the message you wish to send.
User Guide
159
Hardware Sentry KM for PATROL
Version 1.8.01
Changes Validation
After selecting and defining Alert Actions, you need to validate your changes by clicking the Finish button.
Editing A le rt A ctions — Va lida tion
You can use macros that will be replaced at runtime. The A lert A ctions Macro Variables
section states the list of av ailable macrosA lert_A ctions_.
User Guide
160
Hardware Sentry KM for PATROL
Version 1.8.01
Alert Actions Macro Variables
Macro variables can be used in the Alert Actions to customize a string with information related to the encountered hardware failure (display name of the faulty object, value of the parameter, description of the problem, etc.).
Example
You can configure Hardware Sentry to trigger a PATROL event containing the display name of the faulty object by entering something like "Hardware problem with %{OBJECT_NAME}" in the "Trigger a
PATROL Event" dialog box.
You can use sev eral macros at one time.
The table below recapitulates the available macros for the Alert Actions.
Macro
%{/variable_name}
%{ALARM_TYPE}
%{ASCTIME:…}
%{CONSEQUENCE}
%{DATE}
%{FULLREPORT}
%{HOSTNAME}
%{NEWLINE}, %{\n}
%{OBJECT_CLASS}
%{OBJECT_DEVICEID}
%{OBJECT_ID}
Description
Value of the variable_name instance variable
Example: %{/worstParam} will give the name of the "worst parameter" of the instance that triggered the alert.
This feature is recommended for advanced users only!
Alarm type (INFORMATION, WARNING or ALARM)
Example: ALARM
Current date and time formatted as specified in the macro
Example: %{ASCTIME:%m %d %T %Y} will produce Jun 6 11:14:53 2005
The available formats for the %{ASCTIME:…} macro are listed in the asctime() description of the PSL Reference Guide (Book 2).
Description of the possible consequence of the detected problem
Example: The temperature of the chip, component or device that was cooled by this fan should grow quickly. This can lead to severe hardware damage and system crashes.
Current date in the YYYY-MM-dd format
Example: 2005-6-23
Full hardware health report about the instance that triggered the alert
Example: see the output of the "Instant Hardware Health Report" Menu command
Name of the computer monitored with the PATROL Agent
Example: SENTRYTEST003
Linefeed.
This is useful to produce multi-line information.
Class of the instance that triggered the alert
Example: MS_HW_FAN
Hardware Sentry internal device ID of the instance that triggered the alert
Example: 1.1
PATROL internal ID of the instance that triggered the alert
Example: MS_HW_DellOpenManagehdf_11
User Guide
161
Hardware Sentry KM for PATROL
Version 1.8.01
Macro
%{OBJECT_LABEL}
%{OBJECT_TYPE}
%{PARAMETER_NAME}
%{PARENT_CLASS}
%{PARENT_DEVICEID}
%{PARENT_ID}
%{PARENT_LABEL}
%{PARENT_TYPE}
%{PROBLEM}
%{RAW_VALUE}
%{RECOMMENDED_ACTION}
%{TIME}
%{VALUE}
Description
Display name of the instance that triggered the alert
Example: Fan: 1.1 (CPU 1)
Type of the device that triggered the alert
Example: Fan
Name of the parameter that triggered the alert
Example: PredictedFailure
Class of the object that the faulty instance is attached to
Example: MS_HW_ENCLOSURE
Hardware Sentry internal device ID of the object that the faulty instance is attached to
Example: 1
PATROL internal ID of the object that the faulty instance is attached to
Example: MS_HW_DellOpenManagehdf_1
Display name of the object that the faulty instance is attached to
Example: Computer: Dell PowerEdge 1600SC
Type of the object that the faulty instance is attached to
Example: Computer enclosure
Description of the problem encountered by the monitored device
Example: The speed of this fan is critically low (1503 rpm).
Raw value of the parameter that triggered the alert
Example: 67.30000
Recommended action to solve the problem
Example: Check if the fan is really no more cooling the system. If so, replace the fan.
Current time in the HH:MM:SS format
Example: 11:14:53
Formatted value (with unit) of the parameter that triggered the alert
Example: 67.3 °C
For details on the time formats av ailable in the % {TIME:…}, % {A SC TIME:…} and % {LA STTIME:…} macros, please
refer to the section Format Sy mbols for % {A SC TIME:…}
.
Format Symbols for %{ASCTIME:...} Macros
The following table recapitulates all of the time formats available in the %{TIME:…}, %{ASCTIME:…} and %{LASTTIME:…} macros.
Format
%%
%a
%A
%b
%B
Description
This symbol allows you to use a percent sign (%) in the format of a date string
Locale's abbreviated name of the day of week
Locale's full name of the day of week
Locale's abbreviated name of the month
Locale's full name of the month
User Guide
162
Hardware Sentry KM for PATROL
Version 1.8.01
%y
%Y
%Z
%EC
%EC
%Ex
%EX
%w
%W
%x
%X
Format
%p
%r
%R
%S
%l
%m
%M
%n
%t
%T
%u
%U
%V
%H
%I
%j
%k
%c
%C
%d
%D
%e
%h
Description
Locale's appropriate date and time representation
Data and time as %c
Day of month [1,31]; single digits are preceded by 0
Date as %m/%d/%y
Day of month [1,31]; single digits are preceded by a space
Locale's abbreviated name of the month
Hour (24-hour clock) [0,23]; single digits are preceded by 0
Hour (12-hour clock) [1,12]; single digits are preceded by 0
Day of year [1,366]; single digits are preceded by 0
Hour (24-hour clock) [0,23]; single digits are preceded by a space
Hour (12-hour clock) [1,12]; single digits are preceded by a space
Month as a decimal number [1,12]; single digits are preceded by 0
Minute [0,59]; leading zero is permitted but not required
Insert a new line
Locale's equivalent of either a.m. Or p.m.
Appropriate time representation in 12-hour clock format with %p
Time as %H:%M
Seconds [0,61]
Insert a tab
Time as %H:%M:%S
Day of week as a decimal number [1,7], with 1 representing Monday
Week of the year as a decimal number [0,53], with Sunday as the first day of week 1
Week of the year as a decimal number [01,53], with Monday as the first day of the week.
If the week containing 1 January has four or more days in the new year, then it is considered week 1; otherwise, it is week 53 of the previous year, and the next week, is, week 1.
Day of week as a decimal number [0,6], with 0 representing Sunday
Week of the year as a decimal number [0,53], with Monday as the first day of week 1
Locale's appropriate date representation
Locale's appropriate time representation
Year within century [0,99]
Year, including the century (for example 1993)
Abbreviated or full name of time zone, or no bytes if no information of the time zone exists
Locale's alternative appropriate date and time representation
Name of the base year (period) in the locale's alternative representation
Locale's alternative date representation
Locale's alternative time representation
User Guide
163
Hardware Sentry KM for PATROL
Version 1.8.01
Format
%EC
%EC
%OD
%OE
%OH
%OI
%Om
%OM
%OS
%OD
%Ow
%OW
%OD
Description
Offset from %EC (year only) in the locale's alternative representation
Alternative representation of the year in full
Day of the month using the locale's alternative numeric symbols
Same as %OD
Hour (24-hour clock) using the locale's alternative numeric symbols
Hour (12-hour clock) using the locale's alternative numeric symbols
Month using the locale's alternative numeric symbols
Minutes using the locale's alternative numeric symbols
Seconds using the locale's alternative numeric symbols
Week of the year (Sunday as the first day of the week) using the locale's alternative numeric symbols
Day of week (Sunday=0) using the locale's alternative numeric symbols
Week of the year (Monday as the first day of the week) using the locale's alternative numeric symbols
Year (offset from %C) in the locale's alternative representation and using the locale's alternative numeric symbols
Alert after N Times
Hardware Sentry KM for PATROL offers a global advanced alert setting in order to prevent false alerts.
You can now set/modify the number of times thresholds can be breached before triggering an alert on the Missing parameter.
This advanced alert setting, commonly known as Alert after N times is accessible by right-clicking the main Hardware icon > KM Commands > This System’s Settings > Alert after N Times…
User Guide
164
Hardware Sentry KM for PATROL
Version 1.8.01
A le rts A fte r n T im e s Pa ra m e te rs
This setting applies to the parameters of all the monitored devices of the system.
Intrusion Detection Alerts
Hardware Sentry triggers alerts if the enclosure/chassis of your managed system has been opened. An unexpectedly opened chassis could imply that the system is physically accessed by an unauthorized person. The Intrusion Detection Alert feature enables you to select the alert conditions.
Right-click the Hardware icon > KM Commands > KM Settings > Intrusion Detection Alerts:
User Guide
165
Hardware Sentry KM for PATROL
Version 1.8.01
Intrusion De te ction Se ttings
By default, Hardware Sentry triggers an alert ONLY upon the opening or breach of a closed chassis.
Network Link Alerts
Hardware Sentry triggers alerts when a break in the network link is detected for the parameters detailed below. By default, this alert is raised ONLY if a previously detected network link is broken.
LinkStatus
The LinkStatus parameter shows the current status of the network interface to the network (i.e.
whether or nor plugged-in). By default, Hardware Sentry will trigger a warning if a network interface previously connected to the network is now unplugged. However, it will not trigger an alert for network interfaces that were never connected.
DuplexMode
Monitoring network cards communication performance may be critical to ensure that they run at the expected speed in order to avoid network congestion or any other performance issues.
Most Ethernet cables allow communication in both directions simultaneous between two connected cards, this feature is commonly named "full duplex". However, a defective cable or a simple internal malfunction within the cards can prevent them from communicating both ways simultaneously. In that case, once a party begins receiving a signal, it must wait for the transmitter to stop transmitting, before replying. This communication mode is typically called "half-duplex" and can generate network congestion.
User Guide
166
Hardware Sentry KM for PATROL
Version 1.8.01
The DuplexMode parameter's value is set to 0 when the network adapter is running in "half-duplex" mode and 1 when in "full-duplex" mode. By default, the DuplexMode parameter triggers a WARNING when an adapter that was running in "full-duplex" suddenly starts communicating in "half-duplex".
LinkSpeed
The LinkSpeed parameter reports the speed that the network adapter and its remote counterpart currently use to communicate with each other. Note that the unit of this parameter is Mbits/sec.
By default, the LinkSpeed parameter triggers a WARNING when the adapter "slows down", i.e. renegotiates the link speed with its remote counterpart, and is forced (by some circumstances to figure out) to downgrade to a slower communication rate.
To change the default setting and select when these alerts should be raised, right-click on the
Hardware icon > KM Commands > This System's Settings > Network Link Alerts:
Ne twork Link A le rts
User Guide
167
Hardware Sentry KM for PATROL
Version 1.8.01
Notifying Internal KM Issues
Internal KM Issues Notification was previously known as the KM command Internal Message Notification and prior to that as Show/Hide Information Messages.
This notification feature enables Hardware Sentry to inform you of any internal problems that may occur or any special operations it may perform. The objective of this notification is to help resolve an issue (if any), other than hardware problems – which are reported through the regular system of warnings and alerts. This feature is useful to find out more about any anomalies that may occur.
By right clicking on Hardware icon > KM Commands > KM Settings > Additional Settings >
Internal KM Issues Notification, you can set the kind of messages you would like to be notified about:
All internal messages
Only internal problems
No internal message
Inte rna l KM Issue s Notifica tion
User Guide
168
Hardware Sentry KM for PATROL
Version 1.8.01
By default, all internal messages are sent to the System Output Window and are also registered as
PATROL events (event ID "HardwareSentryInternal" of the MS_HW_MAIN event catalog).
Internal errors are registered as ev ents ty pe "ERROR" (they appear in orange in PA TROL Ev ent Manager).
Internal warnings are registered as "W A RNING"
Informational messages are registered as "INFORMA TION".
Managing Unknown Status
At times, although rare, Hardware Sentry is unable to detect the status of a monitored device, and it returns the poll with "Unknown Status".
If this occurs, you can configure Hardware Sentry to perform certain actions:
Set the Status parameter to OK (default)
Ignore value and do not feed parameter
Trigger a WARNING on the Status parameter
Trigger an ALARM on the Status parameter
To access this feature, right-click the Hardware icon > KM Commands > KM Settings >
Additional Settings > Unknown Status Management:
Unknown Sta tus Ma na ge m e nt
In addition to the selected actions, if you select the option to Trigger an Internal KM Issue
Notification, an error message is displayed in the System Output Window of the PATROL console.
User Guide
169
Hardware Sentry KM for PATROL
Version 1.8.01
Reference Guide
This manual provides the following detailed chapters:
: Parameters, info boxes and menu commands for each application class
: supported platforms, instrumentation agents or system tools they require as well as the connectors that are used to monitor them. Details are given for each connector and show all the components discovered and monitored through them.
: global and host-specific variables that can be used.
Classes and Parameters
This section lists the application classes of Hardware Sentry. It gives you details on the icons that represent the class, Infobox, parameters and the menu commands available for each application class.
There are 23 main application classes and 18 “container” classes. The container classes have no parameters.
Parameters discov ered depend on the ty pe of managed element. To see which parameters are discov ered on y our managed sy stems, please refer to the C onnectors and Platforms Reference Table and then the corresponding topic in the C onnectors and Platform-specific Details section to learn about the parameters discov ered for each serv er.
Baselines and Key Performance Indicators
Some parameters are identified by default as Key Performance Indicators (KPIs) and therefore automatically included in the base lining calculation. To learn more about auto baselining and KPIs,
please refer to the Managing Baselines and Key Performance Indicators chapter.
In this guide, parameters flagged as KPIs and included by default in the baseline calculation process are respectively identified by the following icons:
Baselining
KPI
Reference Guide
170
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_BATTERY
MS_HW_BATTERY can be a children of MS_HW_ENCLOSURE and MS_HW_DISKCONTROLLER.
Icon
Parameters
Parameter
Charge
Status
Missing (*)
StatusInformation
Description
Percentage of the battery charge.
When the battery is no longer discovered, the parameter goes into alarm.
Battery Status.
Additional (textual) information about the current status of the battery.
Unit Default
Alert
Thresholds
Type
% Warning ≤ 50
Alarm ≤ 30
Statistics
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
Availability {0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a
None
--
For detailed information about B a se lining and K P I, see
Managing Baselines and Key Performance Indicators .
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
PATROL ID
Battery Information
Manufacturer
Model
Type
Description
The device's PATROL internal identifier. This ID is used for PATROL event reporting etc.
Heading preceding the fields with information on the monitored device
Name of the battery manufacturer
Details about the model of the battery
Details about the type of battery
Chemistry
Device ID
Chemistry type contained in the battery
ID of the monitored object as communicated by the instrumentation layer
Reference Guide
171
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the device
PATROL ID of the connector currently used to monitor the device
File name of the connector currently used to monitor the device
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored blade (properties of the object, its parameters, thresholds, etc.)
Pauses the Blade monitoring
Resumes the Blade monitoring after it has been paused
Removes the Blade from the monitoring environment
Refreshes all parameters of the application class
MS_HW_BATTERY_CONT
Icon
Parameters
None
InfoBox
None
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Reference Guide
172
Hardware Sentry KM for PATROL
Version 1.8.01
Function
Description
Refreshes all parameters of the application class
MS_HW_BLADE
Each instance of the MS_HW_BLADE class represents a blade server inside a blade enclosure.
Icon
Parameters
Parameter
Missing (*)
Status
StatusInformation
Description
When the blade is no longer discovered, the parameter goes into alarm
Blade Status.
Value set by bladeColl every 2 minutes.
Additional (textual) information about the current status of the battery.
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
--
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
PATROL ID
Blade Information
Name
Model
Device ID
Connector Information
Connector Display Name
Description
The blade’s PATROL internal identifier. This ID is used for PATROL event reporting etc.
Heading preceding the fields with information on the monitored device
Name of the blade
Blade model
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the blade
Reference Guide
173
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL ID of the connector currently used to monitor the blade
File name of the connector currently used to monitor the blade
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored blade (properties of the object, its parameters, thresholds, etc.)
Pauses the Blade monitoring
Resumes the Blade monitoring after it has been paused
Removes the Blade from the monitoring environment
Refreshes all parameters of the MS_HW_BLADE application class
MS_HW_BLADE_CONT
Icon
Parameters
None
InfoBox
None
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes all parameters of the application class
Reference Guide
174
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_CAPACITYREPORT
Icon
Parameters
Parameter
CPUCount
Description
Host total number of physical processors (CPU)
Unit
CPUs
Type
Statistics
ConnectedPorts
LogicalDiskSize
MemorySize
PhysicalDiskSize
UnallocatedDiskSpace
Number of connected ports.
Number of degrees before reaching the closest warning threshold.
Host total logical disk size
Host total memory (RAM)
Host total physical disk size
Power consumed by the host ports degrees
Celsius
GB
GB
GB
Watts
Statistics
Statistics
Statistics
Statistics
Statistics
Statistics
Host Total available disk space that is not allocated to any volume Gigabyte
(GB)
Statistics
For detailed information about B a se lining and K P I, see
Managing Baselines and Key Performance Indicators .
InfoBox
None.
Menu Commands
Function
Description
Refreshes all parameters of the application class
Reference Guide
175
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_CONNECTOR
Each instance of the MS_HW_CONNECTOR class represents a connector currently being used by
Hardware Sentry in order to discover and monitor the hardware components of the server.
Connectors are continuously monitored to ensure that the underlying technology being used by
Hardware Sentry to discover and monitor the hardware is always available.
If something goes wrong with the hardware instrumentation layer (but not with the hardware itself), an alert is raised by the Status parameter of the corresponding MS_HW_CONNECTOR instance. In such case, hardware components that were discovered and monitored through this connector are no longer monitored. Check the TestReport parameter to have more details about the connector failure.
Icon
Parameters
Parameter
Status
TestReport
Description
Connector Status.
Value set by connectorColl every 2 minutes
Text describing the tests that have been performed to evaluate the status of the connector.
Value set by connectorColl every 2 minutes.
Unit Default
Alert
Thresholds
Type
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a n/a
Collection
Status
--
InfoBox
Name
PATROL ID
Connector Display Name
Connector ID
Connector File Name@r by
<remote hostname"e name followed byt
Connector File Path
Connector Version
Connector Date
Description
PATROL internal identifier for the connector. This ID is used for PATROL event reporting etc.
Connector name as displayed in the console
PATROL ID of the connector
Name of the connector file i.e. the full HDF filename
Path to the connector file (*.HDF)
Version number of the connector
Connector build date
Reference Guide
176
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector Description
Description
Description of the connector, what it does and how…
Menu Commands
Name
Description
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring. May mean that the connector will not be used anymore to monitor the computer.
Refreshes all instance parameters of the application class
Reference Guide
177
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_CONNECTOR_CONT
This class is simply used to create a container for Connector for display purposes. It does not contain a parameter or infobox but provides an easy way to interact with all Connectors at the same time.
Icon
W hen the connectors hav e been manually "pre-selected", the icon is labeled "Pre-selected connectors" instead of
"Detected connectors".
Parameters
None
InfoBox
None
Menu Commands
Name Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Refreshes all the device Container dependencies
Reference Guide
178
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_CPU
Each instance of the MS_HW_CPU class represents a physical processor of the server. On highest-range servers, the Status parameter will raise an alert "on the fly" as soon as a processor fails. On most servers however, a failed processor causes a server crash. Upon reboot, the processor is likely to be automatically disabled by the BIOS which will then raise an alert in Hardware Sentry because the processor is "missing".
The CorrectedErrorCount and PredictedFailure parameters (available only for a few high-end processors) will help administrators intervene even before such a crash occurs.
Icon
Parameters
Parameter
CorrectedErrorCount
CurrentSpeed
Missing (*)
PredictedFailure
Status
StatusInformation
Description Unit Default
Alert
Thresholds
Type
Number of detected and corrected errors.
Value set by cpuColl every 2 minutes.
CPU speed.
When the physical processor is no longer discovered, the parameter goes into alarm errors None
MHz
{0 =
Present;
1 =
Missing}
None
1 = Alarm
Statistics
Statistics
Availability
This parameter will trigger a warning if a CPU failure is predicted to happen.
Value set by cpuColl every 2 minutes.
CPU Status.
Value set by cpuColl every 2 minutes.
{0 = OK;
1 =
Failure predicte d}
1 = Warning Availability
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Additional (textual) information about the current status of the CPU.
n/a None --
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Reference Guide
179
Hardware Sentry KM for PATROL
Version 1.8.01
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
CPU Information
Manufacturer
Model
Speed
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for the monitored CPU. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Name of the processor manufacturer
Model name of the processor
States the speed of the processor
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the CPU
PATROL ID of the connector currently used to monitor the CPU
File name of the connector currently used to monitor the CPU
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring.
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class
Reference Guide
180
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_CPU_CONT
Icon
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes all parameters of all the device container dependencies
MS_HW_CPUCORE
MS_HW_CPUCORE can be a child of MS_HW_CPU only.
Icon
Parameters
Parameter
Missing
(*)
Description
When the CPU Core is no longer discovered, the parameter goes into alarm.
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
Reference Guide
181
Hardware Sentry KM for PATROL
Version 1.8.01
Status CPU Core Status.
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
-StatusInformation
UsedTimePercent
Additional (textual) information about the current status of the CPU Core.
Percentage of the CPU Core usage.
The "Used Time Percent" parameter is calculated as: (UsedTime - LastUsedTime) /
(currentTime - lastTime) *100
Percent
(%)
---
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
PATROL ID
CPU Core Information
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
The device's PATROL internal identifier. This ID is used for PATROL event reporting etc.
Heading preceding the fields with information on the monitored device
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the device
PATROL ID of the connector currently used to monitor the device
File name of the connector currently used to monitor the device
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class.
Reference Guide
182
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_CPUCORE_CONT
Icon
Parameters
None.
InfoBox
None.
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device from the monitoring environment
Refreshes all parameters of the device container dependencies
Reference Guide
183
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_DISKCONTROLLER
A disk controller is a card inside a computer that connects one or several physical disk drives to this computer. Some intelligent disk controllers (such as RAID controllers) manage several physical disks as a single logical disk which is the only disk exposed to the operating system. Monitoring both physical and logical disks is essential to ensure that the storage is available.
The purpose of the Disk controller instance is to act as a container for Logical Disks and Physical Disks monitoring, and symbolize the way hard drives are setup on the platform.
Please note, however, that if a controller goes missing, all its disk dependencies will be missing as well.
In addition, some information regarding the Disk Controllers, like their brand, model or driver version, is displayed in their infobox.
Icon
Parameters
Parameter
BatteryStatus
ControllerStatus
Missing (*)
StatusInformation
Description Unit Default
Alert
Thresholds
Type
Availability This parameter triggers an alert to predict that the disk controller battery will be unable to support the controller in the event of a power failure. Value set by diskcontrollerColl every 2 minutes.
Additional (textual) information about the current status of the Disk Controller.
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm
This parameter displays the status of the disk controller.
Value set by diskcontrollerColl every 2 minutes.
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm
When the disk controller is no longer discovered, the parameter goes into alarm
{0 =
Present;
1 =
Missing} n/a
1 = Alarm
None
Availability
Availability
--
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Reference Guide
184
Hardware Sentry KM for PATROL
Version 1.8.01
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Disk Controller Information
Manufacturer
Model
BIOS Version
Firmware Version
Driver Version
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for the monitored disk controller. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Name of the disk controller manufacturer
Model details of the disk controller
BIOS version details
Disk controller’s firmware version
Disk controller’s driver version
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the disk controller
PATROL ID of the connector currently used to monitor the disk controller
File name of the connector currently used to monitor the disk controller
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, etc.)
Pauses the device monitoring.
Resumes the device monitoring after it has been paused.
Removes the device object from monitoring.
Refreshes all instance parameters of the application class.
Reference Guide
185
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_DISKENCLOSURE
Icon
Parameters
Parameter
IntrusionStatus
Missing
Status
Description
This parameter will trigger an alarm if the enclosure is open or not properly closed.
Value set by enclosureColl every 2 minutes.
When the disk enclosure is no longer discovered, the parameter goes into alarm.
Enclosure Status.
Value set by enclosureColl every 2 minutes.
Unit Default
Alert
Thresholds
Type
Availability {0 = OK;
2 =
Intrusion
Detected
}
1 = Warning
2 = Alarm
{0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm
Availability
Availability
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Enclosure Information
Manufacturer
Model
Type
Serial Number
BIOS Version
Device ID
Connector Information
Connector Display Name
Connector ID
Description
PATROL internal identifier for the enclosure/chassis. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Name of the enclosure/chassis manufacturer
Enclosure model details
Details about the type of enclosure/chassis
Serial number of the enclosure/chassis
BIOS version details
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the enclosure/chassis
PATROL ID of the connector used to monitor the enclosure/chassis
Reference Guide
186
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector File Name
Connector Version
Connector Date
Description
File name of the connector currently used to monitor the enclosure/chassis
Version details of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class.
MS_HW_ENCLOSURE
Basically, each MS_HW_ENCLOSURE instance represents a box with some hardware components inside.
This class is used to represent the computer’s main chassis, but also external disk array enclosures or blade enclosures.
Icon
Parameters
Parameter
IntrusionStatus
Missing (*)
Description
This parameter will trigger an alarm if the enclosure is open or not properly closed.
Value set by enclosureColl every 2 minutes.
When the disk array is no longer discovered, the parameter goes into alarm
This parameter reports the electricity consumption.
Unit Default
Alert
Thresholds
Type
Availability {0 = OK;
2 =
Intrusion
Detecte d}
2 = Alarm
{0 =
Present;
1 =
Missing}
1 = Alarm
Watts None
Availability
Statistics
Reference Guide
187
Hardware Sentry KM for PATROL
Version 1.8.01
Status Enclosure Status.
Value set by enclosureColl every 2 minutes.
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
StatusInformation Additional (textual) information about the current status of the Disk Controller.
--
For detailed information about B a se lining and K P I, see
Managing Baselines and Key Performance Indicators .
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Enclosure Information
Manufacturer
Model
Type
Serial Number
BIOS Version
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for the enclosure/chassis. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Name of the enclosure/chassis manufacturer
Enclosure model details
Details about the type of enclosure/chassis
Serial number of the enclosure/chassis
BIOS version details
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the enclosure/chassis
PATROL ID of the connector used to monitor the enclosure/chassis
File name of the connector currently used to monitor the enclosure/chassis
Version details of the connector
Connector build date
Menu Commands
Function
Acknowledge IntrusionStatus
Alert
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Allows you to acknowledge and clear the alert triggered by the IntrusionStatus parameter
Reference Guide
188
Hardware Sentry KM for PATROL
Version 1.8.01
Function
Description
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class.
MS_HW_FAN
To avoid too high temperatures, system vendors install fans on critical devices (processors, power supplies, etc.). Monitoring fans is important because they ensure a proper temperature for the system to work efficiently.
Depending on the available information, the following parameters will be displayed for each detected fan device:
The Missing parameter represents the availability of the fan. An alert is triggered if the fan is no longer discovered
The Speed parameter represents the speed of the corresponding fan (in rotations/minute).
The SpeedPercent parameter represents the speed of the corresponding fan in percentage of its maximal speed.
The Status parameter represents the current status of the fan. An alert is triggered if the fan stops spinning or does not spin fast enough
The StatusInformation parameter gives additional information about the current status of the fan.
Icon
Reference Guide
189
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters
Parameter
Missing (*)
Description
When the fan is no longer discovered, the parameter goes into alarm
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
RPM
1 = Alarm
Automatic Statistics Speed
SpeedPercent
Status
Fan Speed.
Value set by fanColl every 2 minutes
Fan Speed as a percentage of its maximal speed.
Value set by fanColl every 2 minutes.
Fan Status.
Value set by fanColl every 2 minutes
% of maximum speed
Automatic
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Statistics
Availability
-StatusInformation Additional (textual) information about the current status of the fan.
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Fan Information
Location
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
The fan’s PATROL internal identifier that will be reported in events etc. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Location of the fan
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the fan
PATROL ID of the connector currently used to monitor the fan
File name of the connector currently used to monitor the fan
Version details of the connector
Connector build date
Reference Guide
190
Hardware Sentry KM for PATROL
Version 1.8.01
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring.
Resumes the device monitoring after it has been paused.
Removes the device object from monitoring.
Refreshes all parameters of the application class.
MS_HW_FAN_CONT
This class is simply used to create a container for Fans for display purpose. It contains no parameter or infobox but provides and easy way to interact with all Fans at the same time.
Icon
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes parameters of all the device container dependencies
Reference Guide
191
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_LED
MS_HW_LED instances can be children of MS_HW_ENCLOSURE only.
Icon
Parameters
Parameter
Color
Missing
(*)
Status
StatusInformation
Description
Color of the LED.
When the led is no longer discovered, the parameter goes into alarm
Led Status.
Additional (textual) information about the current status of the LED.
Unit Default
Alert
Thresholds
Type
Availability {0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm
{0 =
Present;
1 =
Missing}
1 = Alarm
{0 =
Off; 1 =
Blinking;
2 = On} n/a
1 = Warning
2 = Alarm
None
Availability
Availability
--
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
PATROL ID
LED Information
Name
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Description
The device's PATROL internal identifier. This ID is used for PATROL event reporting etc.
Heading preceding the fields with information on the monitored device
Name of the LED
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the device
PATROL ID of the connector currently used to monitor the device
File name of the connector currently used to monitor the device
Reference Guide
192
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector Version
Connector Date
Description
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class.
MS_HW_LED_CONT
Icon
Parameters
None.
InfoBox
None.
Reference Guide
193
Hardware Sentry KM for PATROL
Version 1.8.01
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes all parameters of the device container dependencies
MS_HW_LOGICALDISK
!AL("Disk monitoring",0,`',`')RAID or advanced disk controllers expose several physical disks as a single logical disk to the operating 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 Status parameter is displayed. An alert is triggered when the logical disk is not full operational (degraded, rebuilding, etc.) or not available at all.
Icon
For non-RA ID disk controllers (as most of IDE controllers, for ex ample), no logical disk will be display ed.
Parameters
Parameter
ErrorCount
Missing (*)
Status
StatusInformation
Description Unit Default
Alert
Thresholds
Type
None Statistics Number of errors encountered by the physical disk.
Value set by physical DiskColl every 2 minutes.
When the logical disk is no longer discovered, the parameter goes into alarm
Errors
Logical Disk status.
Value set by logicalDiskColl every 2 minutes.
Additional (textual) information about the current status of the logical disk.
{0 =
Present;
1 =
Missing}
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Alarm
1 = Warning
2 = Alarm n/a None
Availability
Availability
Reference Guide
194
Hardware Sentry KM for PATROL
Version 1.8.01
UnallocatedSpace Amount of unused disk space in the logical disk (i.e. not allocated to the higher layer or the operating system).
GB None Statistics
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Logical Disk Information
Manufacturer
RAID Type
Size
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for the monitored logical disk. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Name of the manufacturer
Details on the type of RAID
Maximum capacity of the logical disk
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the logical disk
PATROL ID of the connector currently used to monitor the logical disk
File name of the connector currently used to monitor the logical disk
Version details of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Acknowledges the alert, and resets the error counter to zero. Available only if the
ErrorCount parameter is collected (platform-dependent)
Pauses the device monitoring.
Resumes the device monitoring after it has been paused.
Removes the device object from monitoring.
Refreshes all instance parameters of the application class.
Reference Guide
195
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_LOGICALDISK_CONT
This class is simply used to create a container for Logical Disks for display purpose. It contains no parameter or infobox but provides and easy way to interact with all Logical Disks at the same time.
Icon
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent devices from the monitoring environment
Refreshes the parameters of the device container dependencies
Reference Guide
196
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_LUN
Icon
Parameters
Parameter
AvailablePathCount
Description
Number of distinct paths available to the remote volume
Unit
paths
Default
Alert
Thresholds
Type
Warning when downgrades or fewer than expected.
Alarm when 0
Availability n/a -AvailablePathInformation
Missing
Status
(*)
Textual information about the paths to the remote volume
When the remote volume is no longer discovered, the parameter goes into alarm
Availability of the remote volume n/a
{0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a n/a
Availability
Availability
-StatusInformation Additional (textual) information about the current status of the volume
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
WWN
Local Device Name
Remote Device Name
Array Name
Description
WNN address of the disk array on the SAN.
Name of the device locally accessed
Name of the device remotely accessed
Name of the disk array
Reference Guide
197
Hardware Sentry KM for PATROL
Version 1.8.01
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device from the monitoring environment
Refreshes all parameters of the application class
MS_HW_LUN_CONT
Icon
Parameters
None.
InfoBox
None.
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes all parameters of the device container dependencies
Reference Guide
198
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_MAIN
There is only one instance of the MS_HW_MAIN class which is the main Hardware icon from which you can configure the product. All collectors are attached to this class.
Icon
Parameters
None.
InfoBox
Name
Product
Version
Release Date
Copyright
Web Site
Support
Description
Name of the product.
Current version of the product.
Release date of the current version of the product.
Copyright information
Web site address
Support contact information
Menu Commands
Function Description
KM Settings
KM Settings >
KM Settings >
KM Settings >
Displays all the command options for different monitoring settings
Enables you to select the Alert Actions (different methods of notification) to be executed by Hardware Sentry when a parameter breaches its threshold
Enables/Disables missing device detection. By default, Hardware Sentry detects
"missing devices" i.e. devices previously monitored but which have disappeared during the monitoring or after a reboot or due to some other cause
Allows you to decide when an intrusion detection alert for the enclosure/ systems chassis should be raised. The IntrusionStatus parameter of each enclosure object discovered by Hardware Sentry reports whether or not the chassis has been opened, and triggers an alarm as per user settings.
KM Settings >
KM Settings >
Enables you to schedule the automatic reset of the ErrorCount parameter of a specific device.
Enables you to customize the discovery cycle. By default, discovery is performed every hour
KM Settings >
Enables you to customize the polling cycle. By default, the polling interval is done every
2 minutes
KM Settings >
KM Settings >
Enables you to define which Java instance is to be used by Hardware Sentry
Activates or deactivates the debug mode.
Reference Guide
199
Hardware Sentry KM for PATROL
Version 1.8.01
Function
KM Settings > Additional
Settings
KM Settings > Additional
Description
Enables you to perform additional settings such as restoring device monitoring, displaying settings for UNIX Console and enabling/disabling debug mode.
Allows you to select the threshold mechanism:
Automatic (by default): Hardware Sentry determines the mode of threshold management best suited to the system. The different modes are:
Tuning: Hardware Sentry uses the internal PATROL mechanism to set thresholds
PCM/Event Management: Hardware Sentry automatically sets thresholds through
PCM/Event Management
No thresholds: Hardware Sentry does not set any thresholds and lets you specify them manually.
Enables you to set actions to be performed when Hardware Sentry is unable to detect the status of a monitored device.
KM Settings > Additional
KM Settings > Additional
KM Settings > Additional
Settings
KM Settings > Additional
This System’s Settings
Brings up the "Restore Device or Sensor Monitoring" wizard to restore one or several objects after their monitoring has been stopped
Gives you the option to turn on the UNIX console mode and modify all object labels to fit the PATROL UNIX Console label size.
Allows you to enable/disable and select the type of information messages displayed by
Hardware Sentry in the system output window of the PATROL Console.
Allows you to set the system properties and credentials and connectors be used for monitoring
Allows you to set the properties and credentials or the security settings (SNMP string) or the account used by Hardware Sentry to launch external commands.
This System’s Settings >
KM Settings >
This System’s Settings >
Allows you to choose the monitoring/alert settings for the network link status.
Allows you to manually enter the electricity consumption for a specific device.
Enables you to trigger a forced discovery and rediscover the hardware devices on the monitored host.
Removes the remote system added to the monitoring.
Enables you to monitor another system or an external device remotely using either
SNMP or WMI.
Provides access to various hardware inventory and reports.
Instantly generates a hardware health report for the entire managed system
Enables you to schedule automated hardware inventory on an hourly, daily, weekly or monthly basis.
Enables you to generate a report showing usage statistics returned by a specific ethernet/fiber port
Provides the energy consumption for hardware components.
Pauses the Hardware Sentry KM for PATROL.
Reference Guide
200
Hardware Sentry KM for PATROL
Version 1.8.01
Function
About
Description
Resumes the monitoring of all objects after it has been paused.
Triggers a complete re-initialization of Hardware Sentry. Customized settings are lost unless specified otherwise in the Reinitialize wizard.
States basic product information and BMC Software support contact information.
MS_HW_MEMORY
Each instance of the MS_HW_MEMORY module represents a memory module in the server.
The Status parameter will raise an "on the fly" alert on servers that can dynamically handle failed memory modules or, most often, for modules that have been disabled by the BIOS upon reboot (the module is then flagged as "missing").
The ErrorCount parameter represents the number of errors that have been fixed by ECC-enabled memory modules. Sometime the number of detected errors cannot be shown and the ErrorStatus parameter is used instead to raise an alert when too many errors have been detected and corrected, meaning that the memory module is about to fail.
In some case, the PredictedFailure parameter is used to alert administrators that the memory module is about to fail. The use of the ErrorCount, ErrorStatus or PredictedFailure parameter highly depends on the technology being used to report the health of memory modules.
Icon
Parameters
Parameter
ErrorCount
ErrorStatus
Missing
(*)
Description Unit Default Alert
Thresholds
1 = Warning Number of detected (and possibly, corrected) errors.
Value set by memoryColl every 2 minutes.
errors
This parameter will trigger an alert if the number of memory errors reaches a threshold set by the manufacturer’s agent.
Value set by memoryColl every 2 minutes.
When the memory module is no longer discovered, the parameter goes into alarm
{0 = No
Errors; 1 =
Detected
Errors; 2 =
Too Many
Errors}
1 = Warning
2 = Alarm
{0 =
Present; 1 =
Missing}
1 = Alarm
Type
Statistics
Availability
Availability
Reference Guide
201
Hardware Sentry KM for PATROL
Version 1.8.01
PredictedFailure This parameter will trigger a warning if a
Status memory failure is predicted to happen.
Value set by memoryColl every 2 minutes.
Memory Status.
Value set by memoryColl every 2 minutes.
{0 = OK; 1
= Failure
Predicted}
{0 = OK; 1
=
Degraded; 2
= Failed}
1 = Alarm
1 = Warning
2 = Alarm n/a None
Availability
Availability
StatusInformati on
Additional (textual) information about the current status of the memory.
--
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
ID
Connector Display Name
Connector File Name
Description
Memory module’s PATROL internal identifier. This ID is used for PATROL event reporting etc.
Display name of the Connector currently used to monitor the Memory module.
File name of the Connector currently used to monitor the Memory module.
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Acknowledges the alert and resets the error count to zero
Pauses the device monitoring.
Resumes the device monitoring after it has been paused.
Removes the device object from monitoring.
Refreshes all instance parameters of the application class.
Reference Guide
202
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_MEMORY_CONT
Icon
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the depending Memory modules of the selected container.
Resumes the monitoring of all the depending Memory modules of the selected container.
Removes the Memory container object as well as all its depending Memory modules from monitoring.
Refreshes all the Memory container dependencies.
Reference Guide
203
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_NETWORK
Each MS_HW_NETWORK instance represents a network adapter in the server.
The LinkStatus parameter reports whether the adapter is properly linked to the network or not from a pure hardware cable perspective (it will not report a bad IP configuration for example). By default, the
LinkStatus parameter raises an alert only for previously connected network adapters that are no longer linked to the network.
The ErrorPercent parameter represents the percentage of sent and received network packets that were in error. A high percentage of errors often means that the network link is improperly configured or that the network card is behaving badly and thus needs to be replaced.
Icon
Parameters
Parameter
DuplexMode
LinkSpeed
LinkStatus
Missing (*)
ReceivedBytesRate
Description Unit Default
Alert
Thresholds
Type
Statistics Percentage used of the available bandwidth.
% available bandwidt h
Automatic
Whether the port is configured to operate in half-duplex or full-duplex mode.
Automatic {0 =
Halfduplex;
1 = Full duplex}
% Automatic Transmitted and received packets in error as a percentage of all processed packets.
Value set by networkColl every 2 minutes.
Negotiated or configured link speed.
Mbits/s Automatic
1 = Alarm This parameter will trigger a warning if the network interface is not connected (i.e. no wire plugged-in).
Value set by networkColl every 2 minutes.
When the network adapters are no longer discovered, the parameter goes into alarm.
{0 =
Plugged;
1 =
Unplugg ed}
{0 =
Present;
1 =
Missing}
1 = Alarm
Received network traffic in megabytes per second.
Received network traffic in packets per second.
MB/s packets/ s
None
None
Availability
Statistics
Statistics
Availability
Availability
Statistics
Statistics
Reference Guide
204
Hardware Sentry KM for PATROL
Version 1.8.01
Status Network interface Status.
Value set by networkColl every 2 minutes.
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
StatusInformation
TransmittedBytesRate
Additional (textual) information about the current status of the network.
Emitted network traffic in megabytes per second.
Emitted network traffic in packets per second.
MB/s None
--
Statistics
Packets per second
%
None Statistics
ZeroBufferCreditPercent Percentage of zero buffer credits that occurred over the last polling interval.
None Statistics
For detailed information about B a se lining and K P I, see
Managing Baselines and Key Performance Indicators .
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
ID
Connector Display Name
Connector File Name
Description
Network interface’s PATROL internal identifier. This ID is used for PATROL event reporting etc.
Display name of the Connector currently used to monitor the Network interface.
File name of the Connector currently used to monitor the Network interface.
Menu Commands
Function Description
Reports traffic on a given Ethernet/Fiber Port.
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.).
Acknowledges and clears the alert raised due to loss of a network link on this interface
(by default, Hardware Sentry will not trigger another alert until the Network interface is plugged-in and unplugged)
Pauses the Network interface monitoring.
Resume
Resumes the Network interface monitoring after it has been paused.
Removes the Network interface object from monitoring.
Refreshes all instance parameters of the application class.
Reference Guide
205
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_NETWORK_CONT
Icon
Parameters
None.
InfoBox
None.
Menu Commands
Function
Description
Reports traffic on a given Ethernet/Fiber port.
Pauses the monitoring of all the depending Network interfaces of the selected container.
Resumes the monitoring of all the depending Network interfaces of the selected container.
Removes the Network interface container object as well as all its depending Network interfaces from monitoring.
Refreshes all the Network interface container dependencies.
Reference Guide
206
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_OTHERDEVICE
MS_HW_OTHERDEVICE instances represent hardware components that do not fall into other predefined categories (processors, memory modules, temperature sensors, fans, voltage sensors, power supplies, network cards, disk controllers, physical disks and logical disks).
Icon
Parameters
Parameter
Missing (*)
Status
StatusInformation
UsageCount
Description
When the device is no longer discovered, the parameter goes into alarm
Device Status.
Value set by otherDeviceColl every 2 minutes.
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
-Additional (textual) information about the current status of the other devices.
Number of times the device has been used.
Device value.
Times used n/a
Automatic
Automatic
Statistics
Statistics Value
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
ID
Connector Display Name
Connector File Name
Description
Other Device’s PATROL internal identifier. This ID is used for PATROL event reporting etc.
Display name of the Connector currently used to monitor the Other Device
File name of the Connector currently used to monitor the Other Device
Reference Guide
207
Hardware Sentry KM for PATROL
Version 1.8.01
Menu Commands
Function
Description
Pauses the Other Device monitoring
Resumes the Other Device monitoring after it has been paused
Removes the Other Device from monitoring
Refreshes all instance parameters of the application class
Displays a text box recapitulating miscellaneous information regarding the monitored device
(properties of the object, its parameters, thresholds, etc.)
MS_HW_OTHERDEVICE_CONT
This class is simply used to create a container for Other Devices for display purpose. It contains no parameter or infobox but provides and easy way to interact with all other Devices at the same time.
Icon
Parameters
None
InfoBox
None
Menu Commands
Function
Resume
Description
Pauses the monitoring of all the depending Other Devices of the selected Container
Resumes the monitoring of all the depending Other Devices of the selected Container
Removes the "Other Device" object as well as all its depending Other Devices from monitoring
Refreshes all the Other Devices Container dependencies
Reference Guide
208
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_PHYSICALDISK
Physical disks must be monitored to avoid loss of data, un-availabilities and performance degradation.
When available, the S.M.A.R.T. technology will be used to predict a disk failure before it occurs.
Depending on the available information, the PredictedFailure and/or Status parameters will be displayed for each discovered physical disk:
The PredictedFailure parameter uses the S.M.A.R.T. technology to predict physical disk failures.
An alert will be triggered if it is predicted that the Physical Disk will soon break down.
The Status parameter represents the current status of the physical disk. An alert is triggered if the physical disk is not available for proper operation.
Icon
Parameters
Parameter Description Unit Default
Alert
Thresholds
Type
Automatic Statistics ErrorCount
DeviceNotReadyErrorCount
MediaErrorCount
NoDeviceErrorCount
HardErrorCount
IllegalRequestErrorCount
Number of errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
errors
Number of not ready device errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
errors errors Number of media errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
Number of no device errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
errors
Number of hard errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
errors
Number of illegal request errors that the disk has encountered since the last reinitialization, or since the last manual reset.
errors
Alarm ≥ 1
Alarm ≥ 1
Alarm ≥ 1
Alarm ≥ 1
None
Statistics
Statistics
Statistics
Statistics
Statistics
Reference Guide
209
Hardware Sentry KM for PATROL
Version 1.8.01
RecoverableErrorCount
TransportErrorCount
Missing
PredictedFailure
Status
(*)
StatusInformation
Value set by physicalDiskColl every 2 minutes.
Number of recoverable errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
errors errors Number of transport errors that the disk has encountered since the last reinitialization, or since the last manual reset.
Value set by physicalDiskColl every 2 minutes.
When the physical disk is no longer discovered, the parameter goes into alarm
{0 =
Present;
1 =
Missing}
Informs if a failure is predicted.
Value set by physicalDiskColl every 2 minutes.
Physical Disk status.
Value set by physicalDiskColl every 2 minutes.
Additional (textual) information about the current status of the physical disk.
None
Alarm ≥ 1
1 = Alarm
{0 = OK;
1 =
Failure
Predicte d}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Statistics
Statistics
Availability
Availability
--
--
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Physical Disk Information
Manufacturer
Size
Serial Number
Device ID
Connector Information
Connector Display Name
Description
PATROL internal identifier for the physical disk. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Name of the physical disk manufacturer
Maximum storage capacity of the physical disk
Serial number of the physical disk
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the physical disk
Reference Guide
210
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL ID of the connector currently used to monitor the physical disk
File name of the connector currently used to monitor the physical disk
Version details of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Acknowledges the alert and resets the error count to zero
Pauses the monitoring of the device
Resumes the monitoring after it has been paused
Removes the device from the monitoring environment
Refreshes all parameters of the application class
Reference Guide
211
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_PHYSICALDISK_CONT
This class is simply used to create a container for Physical Disks for display purpose. It contains no parameter or infobox but provides and easy way to interact with all Physical Disks at the same time.
Icon
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent devices from monitoring
Refreshes all the device container dependencies
Reference Guide
212
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_POWERSUPPLY
The power supply is the component that transforms the AC Line into electric power needed by the computer. Therefore the power supply is a highly critical device of a computer that should never fail.
Because of that, many vendors build servers with redundant power supplies. Monitoring power supplies allows the operators to be alerted when a power supply fails, or even in some cases when a power supply is overloaded.
Depending on the available information, the UsedCapacity and/or Status parameters will be displayed for each power supply or power unit device:
The UsedCapacity parameter represents the power supply’s power currently in use in percentage.
An alert is triggered if the computer uses too much power than it can be supplied.
The Status parameter represents the current status of the power supply. An alert is triggered if an error occurs with the power supply.
Icon
Parameters
Parameter
Missing
(*)
Status
Description
When the power supply is no longer discovered, the parameter goes into alarm
Power Supply status.
Value set by powerSupplyColl every 2 minutes.
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
-StatusInformation
Additional (textual) information about the current status of the power supply.
Percentage of the Power Supply power currently in use if available.
Value set by powerSupplyColl every 2 minutes.
% Automatic Statistics
For detailed information about B a se lining and K P I, see
Managing Baselines and Key Performance Indicators .
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Reference Guide
213
Hardware Sentry KM for PATROL
Version 1.8.01
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Power Supply Information
Type
Power
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for the power supply. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Type of power supply
Maximum power output
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the power supply
PATROL ID of the connector used to monitor the power supply
File name of the connector currently used to monitor the power supply
Version details of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the monitoring of the device object
Resumes the monitoring after it has been paused
Removes the device object from the monitoring environment
Refreshes all parameters of the application class
MS_HW_POWERSUPPLY_CONT
This class is used to create a container for Power Supplies for display purpose. It contains no parameter or infobox but provides and easy way to interact with all Power Supplies at the same time.
Icon
Reference Guide
214
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent device objects of the selected container
Resumes the monitoring of all the dependent device objects of the selected container
Removes the device container object as well as all its dependencies from the monitoring environment
Refreshes the parameters of all the device container dependencies
Reference Guide
215
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_ROBOTICS
MS_HW_ROBOTICS can be a child of MS_HW_ENCLOSURE only.
Icon
Parameters
Parameter
ErrorCount
Missing (*)
Move Count
Status
StatusInformation
Description
Number of moves in failure.
When the robotics is no longer discovered, the parameter goes into alarm
Number of moves performed by the robot.
Device Status
Additional (textual) information about the current status of the robotics.
Unit Default
Alert
Thresholds
Type
Automatic Statistics errors
{0 =
Present;
1 =
Missing} moves
1 = Alarm
None
Availability
Statistics
Availability {0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None --
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
PATROL ID
Robotics Information
Manufacturer
Model
Serial Number
Type
Device ID
Identifying Information
Connector Information
Connector Display Name
Description
The device's PATROL internal identifier. This ID is used for PATROL event reporting etc.
Heading preceding the fields with information on the monitored device
Name of the device manufacturer
Model of the device
Serial number identifying the device
Details about the type of device
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the device
Reference Guide
216
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL ID of the connector currently used to monitor the device
File name of the connector currently used to monitor the device
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class.
Reference Guide
217
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_ROBOTICS_CONT
Icon
Parameters
None.
InfoBox
None.
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes all parameters of the device container dependencies
Reference Guide
218
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_TAPEDRIVE
MS_HW_TAPEDRIVE can be a child of MS_HW_ENCLOSURE and SEN_HW_DISKCONTROLLER.
Icon
Parameters
Parameter
ErrorCount
Missing (*)
MountCount
NeedsCleaning
Status
StatusInformation
Unmount Count
Description Unit Default
Alert
Thresholds
Type
Number of tape drive failures.
errors Automatic
When the tape drive is no longer discovered, the parameter goes into alarm
{0 =
Present;
1 =
Missing}
1 = Alarm
Number of mounts
Indicates whether the tapedrive needs cleaning.
Device status.
mounts None
{0 = OK;
1 =
Cleaning
Needed;
2 =
Cleaning
Needed
Immedia tely}
1 = Warning
2 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None Additional (textual) information about the current status of the tape drives.
Number of unmounts unmount s
None
Statistics
Availability
Statistics
Statistics
Availability
--
Statistics
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
InfoBox
Name
PATROL ID
Tape Drive Information
Description
The device's PATROL internal identifier. This ID is used for PATROL event reporting etc.
Heading preceding the fields with information on the monitored device
Reference Guide
219
Hardware Sentry KM for PATROL
Version 1.8.01
Name
Manufacturer
Model
Serial Number
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
Name of the device manufacturer
Model of the device
Serial number identifying the device
Details about the type of device
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the device
PATROL ID of the connector currently used to monitor the device
File name of the connector currently used to monitor the device
Version number of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored device (properties of the object, its parameters, thresholds, etc.)
Pauses the device monitoring
Resumes the device monitoring after it has been paused
Removes the device object from monitoring
Refreshes all instance parameters of the application class.
Reference Guide
220
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_TAPEDRIVE_CONT
Icon
Parameters
None.
InfoBox
None.
Menu Commands
Function Description
Pauses the monitoring of all the dependent devices of the selected container
Resumes the monitoring of all the dependent devices of the selected container
Removes the device container object as well as all its dependent objects from the monitoring environment
Refreshes all parameters of the device container dependencies
Reference Guide
221
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_TEMPERATURE
As any electronic devices, the chips and other components of a computer stop working when their temperature is getting too high (lots of unrecoverable errors, crashes and even hardware hurt). This temperature may get too high when the device is abnormally overloaded, when a fan is not working properly or when the ambient temperature is too hot. Monitoring the temperatures of the critical devices of your system allows you to take action before a crash occurs.
Depending on the available information, the Temperature and/or Status parameters will be displayed for each detected temperature sensor:
The Temperature parameter represents the current temperature reading in Celsius degrees (°C).
An alert is triggered if the temperature gets too high.
The Status parameter represents the current status of the temperature. An alert is triggered if the temperature gets too high.
Icon
Parameters
Parameter
Missing
(*)
Status
Description
When the temperature sensor is no longer discovered, the parameter goes into alarm
Temperature status.
Value set by temperatureColl every 2 minutes.
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
-StatusInformation
Temperature
Additional (textual) information about the current status of the temperature.
Temperature reading.
Value set by temperatureColl every 2 minutes.
degrees
Celsius
Automatic Statistics
For detailed information about B a se lining and K P I, see
Managing Baselines and Key Performance Indicators .
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Reference Guide
222
Hardware Sentry KM for PATROL
Version 1.8.01
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Temperature Sensor
Information
Location
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for temperature monitoring. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Location of the temperature sensor
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the temperature
PATROL ID of the connector used to monitor the temperature
File name of the connector currently used to monitor the temperature
Version details of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored
Temperature sensor (properties of the object, its parameters, thresholds, etc.)
Pauses the Temperature monitoring
Resumes the monitoring after it has been paused
Removes the Temperature object from the monitoring environment
Refreshes all parameters of the MS_HW_TEMPERATURE application class
MS_HW_TEMPERATURE_CONT
This class is used to create a container for Temperatures for display purpose. It contains no parameter or infobox but provides and easy way to interact with all Temperatures at the same time.
Icon
Reference Guide
223
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent Temperature objects of the selected container
Resumes the monitoring of all the dependent Temperature objects of the selected container
Removes the Temperature container object as well as all its dependent objects from the monitoring environment
Refreshes the parameters of all the Temperature container dependencies
Reference Guide
224
Hardware Sentry KM for PATROL
Version 1.8.01
MS_HW_VOLTAGE
Power supplies convert the AC line power into voltages and currents needed by the motherboard of the computer. The stability of the motherboard (and therefore of the overall computer) strongly depends on this power converter. Too low or too high voltages may lead to unpredictable system crashes.
Monitoring the value of the different voltages needed by the motherboard will help detecting system instability.
Depending on the available information, the following parameters will be displayed for each voltage sensor on the motherboard:
The Missing parameter represents the availability of the power converter. An alert is triggered when a power converter is no longer discovered
The Status parameter represents the current status of the voltage. An alert is triggered if the voltage output is too low for proper functioning.
The StatusInformation parameter gives additional information about the current status of the voltage.
The Voltage parameter represents the voltage output in milliVolts (mV). An alert is triggered if the voltage goes out of the proper range.
Icon
Parameters
Parameter
Missing (*)
Status
StatusInformation
Voltage
Description
When the power converter is no longer discovered, the parameter goes into alarm
Voltage status.
Value set by voltageColl every 2 minutes.
Unit Default
Alert
Thresholds
Type
Availability {0 =
Present;
1 =
Missing}
1 = Alarm
{0 = OK;
1 =
Degrade d; 2 =
Failed}
1 = Warning
2 = Alarm n/a None
Availability
-Additional (textual) information about the current status of the voltage.
Voltage reading.
Value set by voltageColl every 2 minutes.
mV Automatic Statistics
(*) The “Missing” parameter is dy namically activ ated only when the monitored component goes missing. A s long as the monitored component is properly discov ered and monitored, the “Missing” parameter cannot be display ed in the console. W hen the “Missing” parameter is activ ated, its v alue is alway s ‘1’, which triggers an alarm; unless y ou
modified the " alert after n times
" settings. You can disable the missing dev ice detection mechanism in the settings of the KM.
Reference Guide
225
Hardware Sentry KM for PATROL
Version 1.8.01
Depending on y our sy stem, all parameters may not be used. Only one of the parameters may be v isible. This will not affect the proper monitoring of the dev ice.
InfoBox
Name
PATROL ID
Voltage Information
Type
Device ID
Connector Information
Connector Display Name
Connector ID
Connector File Name
Connector Version
Connector Date
Description
PATROL internal identifier for voltage. This ID is used for PATROL event reporting etc.
Heading preceding fields with information on the monitored device
Type of voltage monitored
ID of the monitored object as communicated by the instrumentation layer
Heading preceding fields with information on the connector used to monitor the device
Displays name of the connector currently used to monitor the voltage
PATROL ID of the connector currently used to monitor the voltage
File name of the connector currently used to monitor the voltage
Version details of the connector
Connector build date
Menu Commands
Function
Description
Displays a text box recapitulating miscellaneous information regarding the monitored voltage sensor (properties of the object, its parameters, thresholds, etc.)
Pauses the Voltage monitoring
Resumes the Voltage monitoring after it has been paused
Removes the Voltage from the monitoring environment
Refreshes all parameters of the application class
MS_HW_VOLTAGE_CONT
This class is simply used to create a container for Voltages for display purpose. It contains no parameter or infobox but provides and easy way to interact with all Voltages at the same time.
Icon
Reference Guide
226
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters
None
InfoBox
None
Menu Commands
Function
Description
Pauses the monitoring of all the dependent Voltage objects of the selected container
Resumes the monitoring of all the dependent Voltage objects of the selected container
Removes the Voltage container object as well as all its dependent objects from the monitoring environment
Refreshes the parameters of all Voltage container dependencies
Reference Guide
227
Hardware Sentry KM for PATROL
Version 1.8.01
Connectors and Platforms
This section deals with connectors provided with this version of Hardware Sentry KM for PATROL. Since in most cases, the KM works along with vendor-specific agents of the platforms to first collect information and then monitor hardware components, it provides specific connectors for practically all platforms/environments.
A table gives you a quick overview of these connectors with their corresponding file names and applicable environments (i.e. type of computers, servers, operating systems).
Next, the section deals with detailed information on each of these connectors - stating the target, typical platforms, the pre-requisites for Hardware Sentry KM for PATROL to function optimally, technology used, and what it will discover (stating precise application class names) and then, most importantly, what it will monitor.
In order to know all about the connectors for your systems, first identify your platforms/environments in the reference table, and then read the corresponding details.
Connectors Index
The following table shows all the connectors provided with this versions of Hardware Sentry KM for
PATROL. Each connector is a file with the .hdf extension and they are stored in: $PATROL_HOME/lib/
MS_HW_hdf directory.
Connector Name Connector File Typical platform
Operating System
MS_HW_AdptStorManU nix.hdf
Sun Fire (x64)
f
MS_HW_IOManager.hd
MS_HW_DptStorageMa nager.hdf
MS_HW_AAC.hdf
MS_HW_BrocadeSwitch
.hdf
Fujitsu-Siemens
PRIMERGY
Fujitsu-Siemens
PRIMERGY
Fujitsu-Siemens
PRIMERGY
SAN Switches
Sun Solaris, Linux
Microsoft Windows, Linux
Microsoft Windows, Linux
Microsoft Windows, Linux
Storage Device
Cisco UCS Manager (Blade, Fabric
f
MS_HW_CiscoTelnet.hd
MS_HW_CiscoUCSBlade
.hdf
Cisco MDS9000
Series FC switches
Cisco UCS
Data Domain Storage Appliance -
DataDirect Networks (DDN) Disk
MS_HW_DataDomain.h
df
MS_HW_DDN.hdf
MS_HW_DellCMC.hdf
Data Domain
Storage Appliance
DDN Disk Array
Dell M1000E Chassis
Storage Device
N/A
Storage Device
Storage Device
N/A
228
Reference Guide
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name Connector File Typical platform
Operating System
MS_HW_DellDRACMC.h
df
Dell PowerEdge
MS_HW_Equallogic.hdf
Dell EqualLogic PS
Series Disk Systems
MS_HW_DellArrayMana ger.hdf
Dell PowerEdge
Dell PowerEdge
MS_HW_DellOpenMana ge.hdf
MS_HW_DellStorageMa nager.hdf
MS_HW_EMCDiskArray.
hdf
Dell PowerEdge
Disk Array
MS_HW_EmulexHbacmd
.hdf
Server with Emulex
HBAs
MS_HW_FibreAllianceS witch.hdf
SAN Switches
MS_HW_FujitsuSiemens
Blade.hdf
Fujitsu-Siemens BX
Blade Servers
Fujitsu-Siemens ServerView RAID
MS_HW_ServerviewNT.
hdf
Fujitsu-Siemens
PRIMERGY
MS_HW_FscRaid.hdf
MS_HW_FusionIO.hdf
Fujitsu-Siemens
PRIMERGY
All x86 based servers
HP Insight Management Agent iLO
MS_HW_HitachiBladeSy mphony.hdf
Hitachi
BladeSymphony
Chassis
HP BladeSystem MS_HW_HPBladeSyste m.hdf
MS_HW_HPBladeTelnet
.hdf
HP BladeSystem
MS_HW_CpqDriveArray
NT.hdf
HP ProLiant
MS_HW_CpqFCADriveA rray.hdf
MS_HW_CpqHBA.hdf
HP ProLiant
HP ProLiant
MS_HW_CpqIDEDriveAr ray.hdf
MS_HW_CpMgSm2.hdf
MS_HW_CpqNIC.hdf
MS_HW_CpqSCSIDrive
Array.hdf
HP ProLiant
HP ProLiant
HP ProLiant
HP ProLiant
N/A
Storage Device
Microsoft Windows, Linux
Microsoft Windows, Linux
Microsoft Windows, Linux
Storage Device
Linux, Sun Solaris
Storage Device
N/A
Microsoft Windows, Linux
Microsoft Windows, Linux
Microsoft Windows, Linux, Sun
Solaris
N/A
Microsoft Windows, Linux, Sun
Solaris
N/A
Microsoft Windows, Linux, HP
OpenVMS, HP Tru64, Sun Solaris
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Microsoft Windows, Linux, HP
OpenVMS, HP Tru64, Sun Solaris
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Reference Guide
229
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name Connector File Typical platform
MS_HW_CpMgServNT.h
df
HP ProLiant
MS_HW_HPInsightwbe m.hdf
MS_HW_HPInsightwmi.
hdf
HP ProLiant
HP ProLiant
MS_HW_CpMgServTru6
4.hdf
HP ProLiant
MS_HW_CpqSiMem.hdf
HP ProLiant
MS_HW_CpqHeResMem
2.hdf
HP ProLiant
MS_HW_HPiLO.hdf
MS_HW_HPDotHill.hdf
HP 9000, Integrity,
SuperDome
HP StorageWorks
MSA P2000
MS_HW_HPSSSU.hdf
HP StorageWorks
EVA
HP NetServer MS_HW_HPTopToolsNT
.hdf
MS_HW_HpNetRaidCon troller.hdf
MS_HW_HPUX.hdf
HP NetServer
HP 9000, HP
Integrity, HP
SuperDome
MS_HW_HPUXNetwork.
hdf
MS_HW_HPUXSasMgr.h
df
HP 9000, HP
Integrity, HP
SuperDome
HP 9000, HP
Integrity, HP
SuperDome
MS_HW_HPUXDisk.hdf
HP 9000, HP
Integrity, HP
SuperDome f
MS_HW_HPUXSAUtil.hd
HP 9000, HP
Integrity, HP
SuperDome
MS_HW_HPUXStm.hdf
HP 9000, HP
Integrity, HP
SuperDome f
MS_HW_HPUXWBEM.hd
HP-UX - WBEM
MS_HW_HPUXWBEMNe twork.hdf
MS_HW_IBMAIXChrpMa chstat.hdf
HP 9000, HP
Integrity, HP
SuperDome
IBM RS/6000, IBM pSeries, IBM eServer p5
Operating System
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Linux
Microsoft Windows
HP Tru64, HP OpenVMS
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
Microsoft Windows, Linux, HP
Tru64, HP OpenVMS, Sun Solaris
N/A
Storage Device
Storage Device
Microsoft Windows
Linux, Microsoft Windows
HP-UX
HP-UX
HP-UX
HP-UX
HP-UX
HP-UX
HP-UX
HP-UX
IBM AIX
Reference Guide
230
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name Connector File Typical platform
MS_HW_IBMAIX.hdf
IBM AIX - Environment (uesensor)
MS_HW_IBMAIXUeSens or.hdf
IBM RS/6000, IBM pSeries, IBM eServer p5
IBM RS/6000, IBM pSeries, IBM eServer p5 f
MS_HW_IBMAIXHBA.hd
IBM RS/6000, IBM pSeries, IBM eServer p5
f
MS_HW_IBMAIXDisk.hd
IBM RS/6000, IBM pSeries, IBM eServer p5
MS_HW_IBMBlade.hdf
IBM BladeCenter
IBM Director Agent 3.x - Windows
MS_HW_Director3NT.h
df
IBM Director Agent 4.x - Linux
MS_HW_Director4Linux
.hdf
IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
IBM Director Agent 4.x - Windows
MS_HW_Director4NT.h
df
IBM Director Agent 5.10.x - Linux
MS_HW_Director5Linux
.hdf
MS_HW_Director5NT.h
df
IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
IBM Director Agent 5.20.x - Linux
MS_HW_Director52Linu x.hdf
IBM Director Agent 6.x - Linux
MS_HW_Director52NT.
hdf
MS_HW_Director61Linu x.hdf
IBM Director Agent 6.x - Windows
MS_HW_Director61NT.
hdf
IBM DS (LSI) Disk Arrays (smcli)
MS_HW_smcli.hdf
IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
IBM xSeries, IBM
Netfinity
IBM DSxxxx Disk
Arrays
IBM Netfinity
IBM Netfinity Manager 5.20.x -
IBM Netfinity Manager 5.20.x -
MS_HW_IbmNetfinityM anagerBASIC.hdf
MS_HW_IbmNetfinityM anagerRAID.hdf
IBM Netfinity
IBM Netfinity Manager 5.20.x -
MS_HW_IbmNetfinityM anager.hdf
MS_HW_IBMVIOS.hdf
IBM Netfinity
Intel Base Board 5 Motherboards
MS_HW_IntelBaseBrd5.
hdf
Generic Servers
IBM RS/6000, IBM pSeries, IBM eServer p5
MS_HW_IntelModularSe rver.hdf
Generic Servers
Operating System
IBM AIX
IBM AIX
IBM AIX
IBM AIX
N/A
Microsoft Windows
Linux
Microsoft Windows
Linux
Microsoft Windows
Linux
Microsoft Windows
Linux
Microsoft Windows
Storage Device
Microsoft Windows
Microsoft Windows
Microsoft Windows
IBM AIX
Microsoft Windows, Linux
N/A
Reference Guide
231
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name Connector File Typical platform
Operating System
MS_HW_IpmiTool.hdf
Intel and AMDbased servers
MS_HW_EmulexHbacmd
.hdf
Linux Server with
HBAs
MS_HW_LinuxMultipath
.hdf
Dell PowerEdge,
Fujitsu-Siemens
PRIMERGY, HP
ProLiant, IBM xSeries, NEC
Express5800, Sun
Fire (x64) f
MS_HW_LSI1030Alt.hdf
Fujitsu-Siemens
PRIMERGY
MS_HW_LSIUtilUNIX.hd
Sun Fire (x64)
Linux, Sun Solaris, Microsoft
Windows
Linux
Linux
MS_HW_LinuxNetwork.
hdf
Dell PowerEdge, HP
ProLiant, Fujitsu-
Siemens PRIMERGY,
IBM xSeries, Sun
Fire
Linux
Linux MS_HW_QlogicSCLI.hdf
Linux Server with
HBAs
MS_HW_LSI1030.hdf
Fujitsu-Siemens
PRIMERGY
Microsoft Windows, Linux
Microsoft Windows, Linux
Linux, Sun Solaris
LsiLogic MegaRAID PowerConsole
MS_HW_MegaRaidPow erConsole.hdf
MS_HW_LSIMegaRaidS
AS.hdf
MS_HW_LSIUtilWindow s.hdf
MS_HW_LSIMegaCliWin dows.hdf
MS_HW_MylexControlle r.hdf
MS_HW_LSIMegaRaidS
AS5.hdf
MS_HW_McData.hdf
Windows servers equipped with an
LSI RAID controller f
MS_HW_SunMegaCli.hd
All Solaris Machines with LSI controllers and IBM Servers with EXP3000
External Bays
Microsoft Windows
Any System with an
LSI controller managed by
MegaCli / CmdTool2
Fujitsu-Siemens
PRIMERGY
Microsoft Windows
Microsoft Windows, Linux
Fujitsu-Siemens
PRIMERGY
Fujitsu-Siemens
PRIMERGY
Fujitsu-Siemens
PRIMERGY
SAN Switches
Microsoft Windows, Linux
Microsoft Windows, Linux
Microsoft Windows, Linux
Storage Device
Sun Solaris, Linux
MS_HW_MIB2.hdf
Any SNMPinstrumented device
Network, HP-UX, Storage Device,
HP OpenVMS, HP Tru64
MS_HW_MIB2Linux.hdf
Any SNMPinstrumented device
Linux
Reference Guide
232
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name Connector File Typical platform
Operating System
f
MS_HW_MIB2Solaris.hd
Any SNMPinstrumented device
Sun Solaris, Sun Solaris
MS_HW_MIB2NT.hdf
MS_HW_MBMNT.hdf
f
MS_HW_NECEsmPro.hd
Any SNMPinstrumented device
Microsoft Windows
No-name PC
NEC Express5800
Microsoft Windows
Microsoft Windows, Linux
MS_HW_NetApp.hdf
Disk Array f
MS_HW_PromiseFSC.hd
Fujitsu-Siemens
PRIMERGY
Storage Device
Microsoft Windows, Linux
MS_HW_QuantumTape
Library.hdf
MS_HW_SmartMonLinu x.hdf
Quantum (ADIC)
Tape Library
Dell PowerEdge,
Fujitsu-Siemens
PRIMERGY, HP
ProLiant, IBM xSeries, Sun Fire
(x64)
MS_HW_SMISDiskArray
.hdf
Disk Array
MS_HW_SMISHBA.hdf
Server with HBAs
Storage Device
Linux
Storage Device
SMI-S Compliant RAID Controller -
MS_HW_Director52Serv eRAIDLinux.hdf
IBM xSeries, IBM
Netfinity
SMI-S Compliant RAID Controller -
f
MS_HW_Director52Serv eRAIDNT.hdf
MS_HW_SMISSwitch.hd
IBM xSeries, IBM
Netfinity
SAN Switches
SMI-S Compliant Storage Libraries
MS_HW_SMISLibrary.h
df
MS_HW_SNIALibrary.h
df
Storage Libraries
MS_HW_SunXscf.hdf
IBM Tape Library
3584 / Various
TS3xxx libraries from IBM based on the SNIA mib
SPARC Enterprise
Mx000
StorageTek LSeries Tape Library
MS_HW_StorageTekLSe ries.hdf
StorageTek LSeries Storage Device
Storage Device MS_HW_StorageTekStr eamLine.hdf
MS_HW_SunAlom.hdf
StorageTek
StreamLine
Sun Fire (SPARC) N/A
MS_HW_SunBladeChas sis.hdf
Sun Blade Chassis
Microsoft Windows, Linux, IBM AIX,
HP-UX, Tru64, HP OpenVMS, Sun
Solaris
Linux
Microsoft Windows
Storage Device
Storage Device
Storage Device
Sun Solaris
N/A
Reference Guide
233
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name Connector File Typical platform
Operating System
MS_HW_SunF15K.hdf
Sun Fire (SPARC)
Sun ILOM (SSH)
MS_HW_SunILOMSNMP
.hdf
Sun Blade with
ILOM cards
MS_HW_SunILOMSSH.h
df
Sun Blade with
ILOM cards
Sun Solaris - Environment (ALOM-
MS_HW_SunScSnapsho t.hdf
Sun Fire (SPARC
T1/T2)
MS_HW_SunPrtdiag.hdf
Sun Fire (SPARC)
Sun Solaris - Environment (prtpicl)
MS_HW_SunPrtpicl.hdf
Sun Fire (SPARC)
MS_HW_SunFmadm.hdf
Sun Fire (SPARC)
MS_HW_SunCediag.hdf
Sun Fire (SPARC)
Sun Solaris - Multi-core Processors
MS_HW_SunPsrinfoT1.
hdf
MS_HW_SunNetwork.h
df
Sun Fire
Sun Fire (SPARC)
Sun Solaris
N/A
N/A
Sun Solaris
Sun Solaris
Sun Solaris
Sun Solaris
Sun Solaris
Sun Solaris
Sun Solaris
MS_HW_SunIostatNonS un.hdf
Sun Fire (SPARC)
Sun Solaris - Processors (psrinfo)
MS_HW_SunPsrinfo.hdf
Sun Fire (SPARC)
Sun Solaris - RAID Disks (raidctl)
Sun Solaris
MS_HW_SunTapeDrives
.hdf
Sun Fire (SPARC)
Sun Solaris
MS_HW_SunRaidctl.hdf
All Sun Platforms with hardware RAID
Controllers
Sun Solaris
MS_HW_SunIostat.hdf
Sun Fire (SPARC) Sun Solaris
Sun Solaris
Microsoft Windows
Linux
MS_HW_DiskPart.hdf
Windows
MS_HW_VMwareESXiDis ksIPMI.hdf
VMware ESXi
MS_HW_VMwareESXiDis ksStorage.hdf
VMware ESXi
MS_HW_VMwareESXi.h
df
MS_HW_VMwareESXiDis ksIPMI.hdf
MS_HW_VMwareESXiDis ksStorage.hdf
VMware ESXi
Linux
Linux
MS_HW_VMwareESX4i.
hdf
MS_HW_VMwareESXiDis ksIPMI.hdf
MS_HW_VMwareESXiDis ksStorage.hdf
VMware ESXi
MS_HW_GenBatteryNT.
hdf
Any Windows platform
Linux
Microsoft Windows
Reference Guide
234
Hardware Sentry KM for PATROL
Version 1.8.01
Connector Name
Connector File
MS_HW_WBEMGenDisk
NT.hdf
MS_HW_WBEMGenHBA
.hdf
MS_HW_WBEMGenNet work.hdf
Typical platform
Dell PowerEdge,
Fujitsu-Siemens
PRIMERGY, HP
ProLiant, IBM xSeries, NEC
Express5800, Sun
Fire (x64)
Dell PowerEdge,
Fujitsu-Siemens
PRIMERGY, HP
ProLiant, IBM xSeries, NEC
Express5800, Sun
Fire (x64)
Dell PowerEdge,
Fujitsu-Siemens
PRIMERGY, HP
ProLiant, IBM xSeries, NEC
Express5800, Sun
Fire (x64)
Operating System
Microsoft Windows
Microsoft Windows
Microsoft Windows
Adaptec IOManager
This connector provides disk monitoring through the Adaptec IO Manager SNMP sub-agent which supports 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
Reference Guide
235
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
Adaptec StorMan (RAID)
Gives information about physical disks and volumes of Adaptec SAS RAID controllers through the arcconf utility.
Target
Typical platform(s): Sun Fire (x64)
Operating system(s): Sun Solaris, Linux
Instrumentation layer: arcconf
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / BatteryStatus
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
236
Hardware Sentry KM for PATROL
Version 1.8.01
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
/[opt|usr]/StorMan/arcconf
Adaptec Storage Manager (DPT)
This connector provides disk monitoring through the Adaptec Storage Manager SNMP sub-agent which supports all DPT-based Adaptec RAID controllers.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Operating systems: Microsoft Windows, Linux
Instrumentation layer: Adaptec Storage Manager
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
237
Hardware Sentry KM for PATROL
Version 1.8.01
Adaptec Storage Manager Web Edition (AAC)
This connector provides disk monitoring through the Adaptec Storage Manager Web Edition SNMP subagent which supports all AAC-based Adaptec RAID controllers.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Operating system: Microsoft Windows, Linux
Instrumentation layer: Adaptec Storage Manager Web Edition
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
Brocade SAN Switch
This connector discovers the enclosure and fiber-channel ports of SAN switches as well as the various environment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol and supports the Brocade MIB (fcSwitch-MIB).
Target
Typical platform(s): SAN Switches
Reference Guide
238
Hardware Sentry KM for PATROL
Version 1.8.01
Operating system(s): Storage Device
Instrumentation layer: Brocade SNMP Agent (fcSwitch)
Technology used: SNMP
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / Speed
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / ZeroBufferCreditPrecent
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
239
Hardware Sentry KM for PATROL
Version 1.8.01
Cisco MDS9000 Series - SSH/Telnet
This connector discovers the enclosure and fiber-channel ports of SAN switches as well as the various environment sensors (temperatures, fans, power supplies, etc.).
Target
Typical platform(s): Cisco MDS9000 Series FC switches
Operating system(s): Storage Device
Instrumentation layer: Commands on the Cisco Bay Controller
Technology used: Telnet/SSH
Reference Guide
240
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / DuplexMode
MS_HW_ENCLOSURE / Powerconsumption
This connector targets remote dev ices only .
Cisco UCS Manager (Blade, Fabric Interconnect Switch)
This connector provides hardware monitoring for Cisco UCS Blade chassis (as well as the Cisco Fabric
Interconnect Switch) through the UCS Manager (running on the Fabric Interconnect Switch).
Target
Typical platform(s): Cisco UCS
Reference Guide
241
Hardware Sentry KM for PATROL
Version 1.8.01
Operating system(s): N/A
Instrumentation layer: Cisco UCS Manager (XML API)
Technology used: Cisco UCS XML API
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Reference Guide
242
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
This connector targets remote dev ices only .
DataDirect Networks (DDN) Disk Array - SNMP Agent
This connector monitors the HBA cards present in an HP Proliant system by connecting to the HP Insight
Management agent.
Target
Typical platform(s): HP Proliant
Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Reference Guide
243
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
This connector targets remote dev ices only .
Data Domain Storage Appliance - SNMP Agent
This connector discovers the enclosure and the disks of Data Domain disk arrays as well as the various environment sensors (temperatures, fans, power supplies). It relies on the SNMP protocol.
Target
Typical platform(s): Data Domain Storage Appliance
Operating system(s): Storage Device
Instrumentation layer: Data Domain SNMP Agent
Technology used: SNMP
Reference Guide
244
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_LOGICALDISK / UnallocatedSpace
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
This connector targets remote dev ices only .
Dell CMC (Dell Chassis Management Controller)
Provides environmental information (temperatures, fans and power supplies) on Dell Blade servers through the Dell Chassis Management Controller (CMC).
Target
Typical platform(s): Dell M1000E Chassis
Operating system(s): N/A
Instrumentation layer: Dell Chassis Management Controller (CMC)
Technology used: Telnet/SSH
Reference Guide
245
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Speed
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
This connector targets remote dev ices only .
Dell DRAC/MC (Dell Remote Access Controller/Modular
Chassis)
This connector provides environmental information (temperatures, fans and power supplies) on Dell
Blade 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)
Technology used: Telnet/SSH
Reference Guide
246
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Blades (MS_HW_BLADE)
Enclosure model (MS_HW_ENCLOSURE)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Parameters collected
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
MS_HW_FAN / Speed
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
This connector targets remote dev ices only .
Dell EqualLogic PS Series
There can be multiple PS Systems controlled by the same controller. Thus multiple enclosures are likely.
Target
Typical platform(s): Dell EqualLogic PS Series Disk Systems
Operating system(s): Storage Device
Instrumentation layer: Dell EqualLogic MIBs / SNMP Agent (EQLGROUP-MIB)
Technology used: SNMP
Reference Guide
247
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_FAN / Status
MS_HW_FAN / Speed
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector targets remote dev ices only .
Dell OpenManage Array Manager
This connector provides disks monitoring through the Dell OpenManage Array Manager SNMP agent (not to be confused with Storage Manager).
Target
Typical platform: Dell PowerEdge
Operating system(s): Microsoft Windows, Linux
Instrumentation layer: Dell OpenManage Server Administrator
Technology used: SNMP
Reference Guide
248
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Dell OpenManage Server Administrator
This connector provides hardware monitoring through the Dell OpenManage Server Administrator SNMP agent which supports almost all DELL PowerEdge servers.
Target
Typical platform: Dell PowerEdge
Operating systems: Microsoft Windows, Linux
Instrumentation layer: Dell OpenManage Server Administrator
Technology used: SNMP
Reference Guide
249
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_MEMORY / ErrorCount
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_CPU / CurrentSpeed
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
MS_HW_ENCLOSURE / PowerConsumption
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
250
Hardware Sentry KM for PATROL
Version 1.8.01
Dell OpenManage Storage Manager
This connector provides DELL disk array monitoring through the Dell Storage Manager Agent which supports almost all DELL disk arrays.
Target
Typical platform: Dell PowerEdge
Operating systems: Microsoft Windows, Linux
Instrumentation layer: Dell OpenManage Server Administrator
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Batteries (MS_HW_BATTERY)
Parameters collected
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
EMC Disk Arrays
This connector discovers the enclosure and the disks of EMC SAN disk arrays, as well as the storage pools and storage volumes. It will also discovery and monitor the FC ports of the array and the various environment sensors when available (temperatures, fans, power supplies, etc.). It relies on the WBEM technology and supports SMI-S compliant disk arrays only.
Reference Guide
251
Hardware Sentry KM for PATROL
Version 1.8.01
Target
Typical platform(s): Disk Array
Operating system(s): Storage Device
Instrumentation layer: EMC SMI-S Agent (ECOM)
Technology used: WBEM
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Collected parameters
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector targets remote dev ices only .
Reference Guide
252
Hardware Sentry KM for PATROL
Version 1.8.01
Emulex HBAs (hbacmd)
This connector discovers Emulex HBAs of servers running UNIX or Linux using the hbacmd utility provided with the Emulex Drivers.
Target
Typical platform(s): UNIX/Linux Server with Emulex HBAs
Operating system(s): Linux, Sun Solaris
Instrumentation layer: Emulex's hbacmd utility
Technology used: System commands
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
/usr/sbin/hbanyware/hbacmd
Reference Guide
253
Hardware Sentry KM for PATROL
Version 1.8.01
Fibre Alliance SNMP Agent (Switches)
This connector discovers the enclosure and fiber-channel ports of SAN switches as well as the various environment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol and supports the Fibre Alliance MIB (FCMGMT-MIB).
Target
Typical platform(s): SAN Switches
Operating system(s): Storage Device
Instrumentation layer: Fibre Alliance SNMP Agent (FCMGMT-MIB)
Technology used: SNMP
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / ReceivedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
254
Hardware Sentry KM for PATROL
Version 1.8.01
Fujitsu-Siemens Management Blade (FSC BX Blade Servers)
This connector provides hardware monitoring through the Fujitsu-Siemens Management Blade SNMP
Agent which supports the Fujitsu-Siemens Blade servers (BX300, BX600, etc.). Needs to run remotely.
Target
Typical platform: Fujitsu-Siemens BX Blade Servers
Operating systems: N/A
Instrumentation layer: Fujitsu-Siemens Management Blade
Technology used: SNMP
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
This connector targets remote dev ices only .
Fujitsu-Siemens ServerView RAID Agent
This connector provides disk monitoring through the Fujitsu-Siemens ServerView RAID SNMP sub-agent which supports many RAID controllers in Primergy servers.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Reference Guide
255
Hardware Sentry KM for PATROL
Version 1.8.01
Operating systems: Microsoft Windows, Linux
Instrumentation layer: Fujitsu-Siemens ServerView RAID Agent
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_DISKCONTROLLER / BatteryStatus
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
Fujitsu-Siemens Serverview
This connector provides hardware monitoring through the Fujitsu-Siemens Serverview Agent which supports almost all Fujitsu-Siemens PRIMERGY servers.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Operating systems: Microsoft Windows, Linux
Instrumentation layer: Fujitsu-Siemens Serveview Agent
Technology used: SNMP
Reference Guide
256
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_MEMORY / ErrorCount
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
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,
Reference Guide
257
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands: fio-status
Hitachi BladeSymphony Chassis
This connector provides hardware monitoring for the Hitachi BladeSymphony Chassis racks through the
Hitachi BladeSymphony Chassis Management Module
Target
Typical platform(s): Hitachi BladeSymphony Chassis
Operating system(s): N/A
Instrumentation layer: Hitachi BladeSymphony Chassis Management Module
Technology used: SNMP
Reference Guide
258
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
LEDs (MS_HW_LED)
Collected parameters
MS_HW_FAN / Speed
MS_HW_FAN / Status
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_BLADE / Status
MS_HW_OTHERDEVICE / Status
MS_HW_ENCLOSURE / PowerConsumption
MS_HW_LED / Status
This connector targets remote dev ices only .
HP BladeSystem
This connector provides hardware monitoring for the HP BladeSystem racks through the HP Insight
Management Agents.
Target
Typical platform: HP BladeSystem
Operating systems: Microsoft Windows, Linux
Instrumentation layer: HP iLO / HP Insight Management Agents
Technology used: SNMP
Reference Guide
259
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
This connector is able to monitor the local host and/or a remote sy stem.
HP BladeSystem - Telnet/SSH
This connector provides hardware monitoring for the HP BladeSystem racks through the Onboard
Administrator.
Target
Typical platform(s): HP BladeSystem
Operating system(s): N/A
Instrumentation layer: HP BladeSystem Onboard Administrator
Technology used: Telnet/SSH
Reference Guide
260
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / SpeedPercent
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / UsedWatts
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / powerconsumption
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent–Drive Array
This connector monitors the HP/Compaq Drive Arrays by connecting to the Storage Management SNMP 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
Technology used: SNMP
Reference Guide
261
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Parameters collected
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent–Fiber Array
This connector monitors the fiber-connected HP/Compaq StorageWorks Arrays by connecting to the
Fiber Array Management SNMP sub-agent of the HP Insight Manager agent.
Target
Typical platform: HP ProLiant
Operating systems: Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Reference Guide
262
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_DISKCONTROLLER / BatteryStatus
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_OTHERDEVICE / Status
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent - HBA
This connector monitors the HBA cards present in an HP ProLiant system by connecting to the HP Insight
Management agent.
Target
Typical platform(s): HP ProLiant
Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Reference Guide
263
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent–IDE Storage
This connector monitors the HP/Compaq IDE Drive Arrays by connecting to the Storage Management
SNMP sub-agent of the HP Insight Manager agent.
Target
Typical platform: HP ProLiant
Operating systems: Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
264
Hardware Sentry KM for PATROL
Version 1.8.01
HP Insight Management Agent–iLO
This connector provides hardware monitoring of the HP iLO card in HP ProLiant servers through the HP
Insight Manager (Server Agent) which supports almost all HP Proliant and Integrity servers under
Windows and Linux, as well as Tru64 servers.
Target
Typical platform: HP ProLiant
Operating systems: Microsoft Windows, Linux, HP OpenVMS, HP Tru64, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Discovered obj ects
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Parameters collected
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent (v8.25 or higher) - Memory
This connector provides Memory Information through the HP Insight Manager (Newer Server Agents).
Target
Typical platform(s): HP ProLiant
Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Reference Guide
265
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Memory modules (MS_HW_MEMORY)
Collected parameters
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent (v8.20 or lower) - Memory
This connector provides Memory Information through the HP Insight Manager (Older Server Agents).
Target
Typical platform(s): HP ProLiant
Operating system(s): Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Discovered obj ects
Memory modules (MS_HW_MEMORY)
Collected parameters
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent - Network
This connector discovers enclosures, Ethernet ports and aggregations through the HP Insight Manager
Agent.
Target
Typical platform(s): HP ProLiant
Reference Guide
266
Hardware Sentry KM for PATROL
Version 1.8.01
Operating system(s): Microsoft Windows, Linux, SUN, HP-UX
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / DuplexMode
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent–SCSI Storage
This connector monitors the HP/Compaq SCSI disk by connecting to the Storage Management SNMP sub-agent of the HP Insight Manager agent.
Target
Typical platform: HP ProLiant
Operating systems: Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Reference Guide
267
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent–Server
This connector provides hardware monitoring through the HP Insight Manager (Server Agent) which supports almost all HP Proliant and Integrity servers under Windows and Linux, as well as Tru64 servers.
Target
Typical platform: HP ProLiant
Operating systems: Microsoft Windows, Linux, HP Tru64, HP OpenVMS, Sun Solaris
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Reference Guide
268
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_CPU / CurrentSpeed
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_CPU / PredictedFailure
MS_HW_ENCLOSURE / PowerConsumption
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent–Server (Alpha)
This connector adds HP Tru64-specific hardware monitoring through the HP Insight Manager (Server
Agent).
Target
Typical platform: HP ProLiant
Operating systems: HP Tru64, HP OpenVMS
Instrumentation layer: HP Insight Management Agents
Technology used: SNMP
Reference Guide
269
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Power supplies (MS_HW_POWERSUPPLY)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP Insight Management Agent - Server - WBEM
This connector provides hardware monitoring through the HP Insight Manager (Server Agent) which supports almost all HP Proliant and Integrity servers under Windows and Linux, as well as Tru64 servers.
Target
Typical platform(s): HP ProLiant
Operating system(s): Linux
Instrumentation layer: HP Insight Management Agents - WBEM
Technology used: WBEM
Reference Guide
270
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / CurrentSpeed
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
271
Hardware Sentry KM for PATROL
Version 1.8.01
HP Insight Management Agent - Server - WMI
This connector provides hardware monitoring through the HP Insight Manager (Server Agent) which supports almost all HP Proliant and Integrity servers under Windows and Linux, as well as Tru64 servers.
Target
Typical platform(s): HP ProLiant
Operating system(s): Microsoft Windows
Instrumentation layer: HP Insight Management Agents - WMI
Technology used: WMI
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Reference Guide
272
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / CurrentSpeed
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
This connector is able to monitor the local host and/or a remote sy stem.
HP MP/GSP card (iLO)
This connector provides environmental information (temperatures, fans, etc.) on HP 9000 and Integrity servers through HP Integrated Lights-Out Management Card
Target
Typical platforms: HP 9000, Integrity, SuperDome
Operating system: N/A
Instrumentation layer: HP MP/GSP card (iLO)
Technology used: Telnet/SSH
Reference Guide
273
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
This connector targets remote dev ices only .
HP MSA 2000 & P2000
This connector discovers the Environmental, Physical Disk, Logical Disk, Management Network Cards and
Fibre Ports on P2000 / MSA Series Filers.
Target
Typical platform(s): HP StorageWorks MSA P2000
Operating system(s): Storage Device
Instrumentation layer: HP MSA Management Card
Technology used: Telnet/SSH
Reference Guide
274
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_LOGICALDISK / UnallocatedSpace
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_BLADE / Status
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / Status
This connector targets remote dev ices only .
W e recommend setting the collection interv al for all MSA Disk array s to at least 15 minutes to prev ent the management card from being ov erloaded.
This connector targets remote dev ices only .
Reference Guide
275
Hardware Sentry KM for PATROL
Version 1.8.01
HP StorageWorks EVA - SSSU
This connector monitors the environmental sensors located in Disk Shelves. Sensors and physical disks 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
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Memory modules (MS_HW_MEMORY)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Reference Guide
276
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_LOGICALDISK / UnallocatedSpace
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_FAN / Status
MS_HW_FAN / Speed
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / LinkStatus
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP TopTools Agent
This connector provides hardware monitoring through the HP TopTools Agent version 5.x which supports almost all HP NetServer servers under Windows.
Target
Typical platform: HP NetServer
Operating system: Microsoft Windows
Instrumentation layer: HP TopTools Agent
Technology used: System commands, WMI
Reference Guide
277
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Speed
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is av ailable for use to monitor the local host only .
HP TopTools NetRaid Agent
This connector monitors the RAID disks (physical and logical) attached to a HP NetRAID controller. It uses the information provided by the HP NetRAID SNMP Sub-Agent, installed with the HP TopTools
Server Agent.
Target
Typical platform: HP NetServer
Operating systems: Linux, Microsoft Windows
Instrumentation layer: HP TopTools NetRaid Agent
Technology used: SNMP
Reference Guide
278
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
HP-UX–Common
This connector provides hardware status information (processors, network interfaces) on HP-UX systems. 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.)
Technology used: System commands
Discovered obj ects
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
Reference Guide
279
Hardware Sentry KM for PATROL
Version 1.8.01
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the sudo utility for the following command: /usr/bin/adb.
HP-UX–Disks
This connector provides hardware SCSI disks status information on HP-UX systems. Requires root privileges.
Target
Typical platforms: HP 9000, HP Integrity, HP SuperDome
Operating system: HP-UX
Instrumentation layer: HP-UX system commands (pvdisplay, ioscan, etc.)
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the following command: /usr/sbin/ diskinfo
Reference Guide
280
Hardware Sentry KM for PATROL
Version 1.8.01
HP-UX - Network
Discovers 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.)
Technology used: System commands
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / LinkSpeed
This connector is able to monitor the local host and/or a remote sy stem.
HP-UX - SASMGR Managed Disks
Provides hardware SAS Raid disks status information on HP-UX systems. Requires root privileges.
Target
Typical platform(s): HP 9000, HP Integrity, HP SuperDome
Operating system(s): HP-UX
Instrumentation layer: HP-UX system commands (sasmgr, ioscan etc.)
Reference Guide
281
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_LOGICALDISK / Status
MS_HW_PHYSICALDISK / Status
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the 'sudo' utility for the following commands: * /opt/sas/bin/sasmgr
This connector is able to monitor the local host and/or a remote sy stem.
HP-UX - Smart Array RAID
Display the physical disks connected to a Smart Array Controller and any configured logical drives and spare drives.
Target
Typical platform(s): HP 9000, HP Integrity, HP SuperDome
Operating system(s): HP-UX
Instrumentation layer: HP-UX Smart Array Configuration Utility
Technology used: System commands
Reference Guide
282
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Batteries (MS_HW_BATTERY)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
/opt/raidsa/bin/sautil
HP-UX-STM
This connector enables monitoring physical disks and memory modules on HP-UX systems through the
Support Tools Manager utilities (STM).
Target
Typical platforms: HP 9000, HP Integrity, HP SuperDome
Operating system: HP-UX
Instrumentation layer: HP-UX Support Tools Manager (STM)
Technology used: System commands
Reference Guide
283
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Parameters collected
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_MEMORY / ErrorCount
This connector is able to monitor the local host and/or a remote sy stem.
HP-UX - WBEM
Target
Typical platform(s): HP 9000, HP Integrity, HP SuperDome
Operating system(s): HP-UX
Instrumentation layer: HP-UX WBEM Provider
Technology used: WBEM
Reference Guide
284
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks (MS_HW_LOGICALDISK)
RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_CPU / CurrentSpeed
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
285
Hardware Sentry KM for PATROL
Version 1.8.01
HP-UX - WBEM Network
Target
Typical platform(s): HP 9000, HP Integrity, HP SuperDome
Operating system(s): HP-UX
Instrumentation layer: HP-UX WBEM Provider
Technology used: WBEM
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / Speed
This connector is able to monitor the local host and/or a remote sy stem.
IBM BladeCenter Management Module
This connector provides hardware monitoring of the IBM BladeCenter chassis through the IBM
BladeCenter Management Module (SNMP-based). Needs to run remotely.
Target
Typical platform: IBM BladeCenter
Operating system: Not applicable
Instrumentation layer: IBM BladeCenter Management Module
Technology used: SNMP
Reference Guide
286
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE) -
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / SpeedPercent
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
This connector targets remote dev ices only .
IBM AIX–CHRP Environment
This connector provides hardware environment information (temperatures, voltages, fans, power supplies) 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)
Technology used: System commands
Reference Guide
287
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Power supplies (MS_HW_POWERSUPPLY)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the following commands:
/usr/sbin/bootinfo
/usr/sbin/machstat
IBM AIX–Common
This connector provides hardware status information (processors, network interfaces) on IBM AIX systems
Target
Typical platforms: IBM RS/6000, IBM pSeries, IBM eServer p5
Operating system: IBM AIX
Instrumentation layer: IBM AIX system commands (lsdev, entstat, etc.)
Technology used: System commands
Reference Guide
288
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_MEMORY / ErrorCount
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / DuplexMode
This connector is able to monitor the local host and/or a remote sy stem.
IBM AIX - Environment (uesensor)
This connector provides hardware environment information: temperatures, voltages, fans, power supplies on IBM AIX systems
Target
Typical platforms: IBM RS/6000, IBM pSeries, IBM eServer p5
Operating system: IBM AIX
Instrumentation layer: IBM AIX system commands (uesensor)
Technology used: System commands
Reference Guide
289
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Parameters collected
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
IBM AIX - HBA
Provides 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.)
Technology used: System commands
Reference Guide
290
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
IBM AIX–SCSI disks
This connector provides hardware status information of the non-RAID SCSI physical disks on IBM AIX systems
Target
Typical platforms: IBM RS/6000, IBM pSeries, IBM eServer p5
Operating systems: IBM AIX
Instrumentation layer: IBM AIX system commands (lsdev, pvdisplay, etc.)
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / ErrorCount
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
291
Hardware Sentry KM for PATROL
Version 1.8.01
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
/usr/bin/dd
IBM Director Agent 3.x–Windows
This connector provides hardware monitoring through the IBM Director Agent version 3.x which supports almost all IBM Netfinity and xSeries servers. This connector is WBEM-based.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Microsoft Windows
Instrumentation layer: IBM Director Agent 3.x
Technology used: WMI
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
292
Hardware Sentry KM for PATROL
Version 1.8.01
IBM Director Agent 4.x–Linux
This connector provides hardware monitoring through the IBM Director Agent version 4.x which supports some (not all) xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Linux
Instrumentation layer: IBM Director Agent 4.x
Technology used: WBEM
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
293
Hardware Sentry KM for PATROL
Version 1.8.01
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the following command: /opt/IBM/ director/CIMOM/bin/cimcli.
IBM Director Agent 4.x–Windows
This connector provides hardware monitoring through the IBM Director Agent version 4.x which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Microsoft Windows
Instrumentation layer: IBM Director Agent 4.x
Technology used: WMI
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Reference Guide
294
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
IBM Director Agent 5.10.x–Linux
This connector provides hardware monitoring through the IBM Director Agent version 5.x which supports some (not all) xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Linux
Instrumentation layer: IBM Director Agent 5.10.x
Technology used: WBEM
Reference Guide
295
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the following command: /opt/ibm/ director/cimom/bin/CLI.
Reference Guide
296
Hardware Sentry KM for PATROL
Version 1.8.01
IBM Director Agent 5.10.x–Windows
This connector provides hardware monitoring through the IBM Director Agent version 5.x which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Microsoft Windows
Instrumentation layer: IBM Director Agent 5.10.x
Technology used: WMI
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
297
Hardware Sentry KM for PATROL
Version 1.8.01
IBM Director Agent 5.20.x–Linux
This connector provides hardware monitoring through the IBM Director Agent version 5.20.x which supports some (not all) xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Linux
Instrumentation layer: IBM Director Agent 5.20.x
Technology used: WBEM
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the sudo utility for the command: /opt/ibm/icc/cimom/bin/CLI.
Reference Guide
298
Hardware Sentry KM for PATROL
Version 1.8.01
IBM Director Agent 5.20.x–ServeRAID - Linux
This connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agent component of the IBM Director Agent version 5.20.x which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Linux
Instrumentation layer: IBM Director Agent 5.20.x
Technology used: WBEM
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_LOGICALDISK / Status
MS_HW_PHYSICALDISK / Status
This connector is able to monitor the local host and/or a remote sy stem
IBM Director Agent 5.20.x–Windows
This connector provides hardware monitoring through the IBM Director Agent version 5.20.x which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platforms: IBM xSeries, IBM Netfinity
Operating system: Microsoft Windows
Instrumentation layer: IBM Director Agent 5.20.x
Reference Guide
299
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: WMI
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
IBM Director Agent 5.20.x–ServeRAID - Windows
This connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agent component of the IBM Director Agent version 5.20.x which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platform(s): IBM xSeries, IBM Netfinity
Operating system(s): Microsoft Windows
Instrumentation layer: IBM Director Agent 5.20.x
Technology used: WMI
Reference Guide
300
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_LOGICALDISK / Status
MS_HW_PHYSICALDISK / Status
This connector is able to monitor the local host and/or a remote sy stem.
IBM Director Agent 6.x - Linux
This connector provides hardware monitoring through the IBM Director Agent version 6.x.
Target
Typical platform(s): IBM xSeries, IBM Netfinity
Operating system(s): Linux
Instrumentation layer: IBM Director Agent 6.x
Technology used: WBEM
Reference Guide
301
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / IntrusionStatus
This connector is able to monitor the local host and/or a remote sy stem.
IBM Director Agent 6.x - Windows
This connector provides hardware monitoring through the IBM Director Agent version 6.x.
Target
Typical platform(s): IBM xSeries, IBM Netfinity
Operating system(s): Microsoft Windows
Instrumentation layer: IBM Director Agent 6
Technology used: WMI
Reference Guide
302
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
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
Operating system(s): Storage Device
Instrumentation layer: SMCLI
Technology used: System commands
Reference Guide
303
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_LOGICALDISK / UnallocatedSpace
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / LinkStatus
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor remote sy stem only .
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
Second_Address
Reference Guide
304
Hardware Sentry KM for PATROL
Version 1.8.01
IBM Netfinity Manager 5.20.x–Basic
This connector provides basic environment monitoring through the IBM Netfinity Manager Services SNMP sub-agent which supports almost all old IBM servers (Netfinity) under Windows.
Target
Typical platform: IBM Netfinity
Operating system: Microsoft Windows
Instrumentation layer: IBM Netfinity Manager 5.20.x
Technology used: SNMP
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
IBM Netfinity Manager 5.20.x–Disks
This connector provides IBM ServeRAID monitoring through the IBM Netfinity Manager Services SNMP sub-agent which supports almost all old IBM servers (Netfinity) under Windows.
Target
Typical platform: IBM Netfinity
Operating system: Microsoft Windows
Reference Guide
305
Hardware Sentry KM for PATROL
Version 1.8.01
Instrumentation layer: IBM Netfinity Manager 5.20.x
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
IBM Netfinity Manager 5.20.x–Normal
This connector provides environment monitoring through the IBM Netfinity Manager Services SNMP subagent which supports almost all old IBM servers (Netfinity) under Windows.
Target
Typical platform: IBM Netfinity
Operating systems: Microsoft Windows
Instrumentation layer: IBM Netfinity Manager 5.20.x
Technology used: SNMP
Reference Guide
306
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
This connector is able to monitor the local host and/or a remote sy stem.
IBM VIO Server
Provides hardware status information (processors, memory modules, network interfaces, HBAs, physical disks) on IBM VIO systems.
Target
Typical platform(s): IBM RS/6000, IBM pSeries, IBM eServer p5
Operating system(s): IBM AIX
Instrumentation layer: IBM AIX system commands through the IOS interface (lsdev, entstat, etc.)
Technology used: System commands
Reference Guide
307
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_MEMORY / ErrorCount
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / DuplexMode
This connector is able to monitor remote sy stems only
Intel Base Board 5 Motherboards
This connector provides hardware monitoring through the Intel Server Manager 8 SNMP Agents under
Windows and Linux.
Target
Typical platform(s): Generic Servers
Operating system(s): Microsoft Windows, Linux
Instrumentation layer: Intel Server Manager 8 SNMP Agents
Technology used: SNMP
Reference Guide
308
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Intel Modular Server
This connector provides hardware monitoring through the Intel Modular Server Chassis Management
Module's SNMP Agents.
Target
Typical platform(s): Generic Servers
Operating system(s): N/A
Instrumentation layer: Intel Server Manager 8 SNMP Agents
Technology used: SNMP
Reference Guide
309
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_FAN / Status
MS_HW_FAN / Speed
MS_HW_POWERSUPPLY / Status
MS_HW_BLADE / Status
MS_HW_OTHERDEVICE / Status
MS_HW_NETWORK / Status
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / LinkSpeed
This connector targets remote dev ices only .
IPMI
Gives environmental information (temperatures, fans, etc.) on several IPMI-enabled servers in-band and 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
Reference Guide
310
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
LEDs (MS_HW_LED)
Reference Guide
311
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Speed
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
MS_HW_LED / Status
MS_HW_LED / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
* ipmitool
Linux - Emulex HBAs (hbacmd)
This connector discovers Emulex HBAs of servers running Linux using the hbacmd utility provided with the Emulex Drivers.
Target
Typical platform(s): Linux Server with HBAs
Operating system(s): Linux
Instrumentation layer: Emulex's hbacmd utility
Reference Guide
312
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: System commands
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
/usr/sbin/hbanyware/hbacmd
Linux–Network
This 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
Operating system: Linux
Instrumentation layer: Linux system commands (ethtool, mii-tool)
Technology used: System commands
Discovered obj ects
Network cards (MS_HW_NETWORK)
Reference Guide
313
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters collected
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / DuplexMode
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the commands: ethtool mii-tool
Linux - Multipath
This connector provides the monitoring of HBA cards on all Linux systems through the multipath utility.
Target
Typical platform(s): Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NEC
Express5800, Sun Fire (x64)
Operating system(s): Linux
Instrumentation layer: Linux multipath utility
Technology used: System commands
Reference Guide
314
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
LUN (MS_HW_LUN)
Collected parameters
MS_HW_LUN / AvailablePathCount
MS_HW_LUN / AvailablePathInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands: multipath
Linux - QLogic HBAs (scli)
This connector discovers QLogic HBAs of servers running Linux using the scli utility provided with the
QLogic Drivers.
Target
Typical platform(s): Linux Server with HBAs
Operating system(s): Linux
Instrumentation layer: QLogic's SCLI utility
Technology used: System commands
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to
Reference Guide
315
Hardware Sentry KM for PATROL
Version 1.8.01
configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands: scli
LSI 1030-based GAM Server
This connector provides disk monitoring for LSI c1030-based disk controllers (also known as LSI
Integrated Mirroring) through the LSI1030 SNMP sub-agent.
Target
Typical platforms: Fujitsu-Siemens PRIMERGY
Operating systems: Microsoft Windows, Linux
Instrumentation layer: LSI GAM Server
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
LSI 1030-based GAM Server (Alternate MIB)
This connector provides disk monitoring for LSI c1030-based disk controllers (also known as LSI
Integrated Mirroring) through the LSI1030 SNMP sub-agent (based on the 1.3.6.1.4.1.3582.2 MIB).
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Reference Guide
316
Hardware Sentry KM for PATROL
Version 1.8.01
Operating system: Microsoft Windows, Linux
Instrumentation layer: LSI GAM Server
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
LSI Logic - LsiUtil - RAID (Windows)
Gives information about physical disks and volumes of LSI Logic SAS RAID controllers through the lsiutil utility.
Target
Typical platform(s): Windows servers equipped with an LSI RAID controller
Operating system(s): Microsoft Windows
Instrumentation layer: lsiutil
Technology used: System commands
Reference Guide
317
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is av ailable for use to monitor the local host only .
LSI Logic - LsiUtil - RAID
Gives information about physical disks and volumes of LSI Logic SAS RAID controllers through the lsiutil utility.
Target
Typical platform(s): Sun Fire (x64)
Operating system(s): Linux, Sun Solaris
Instrumentation layer: lsiutil
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
318
Hardware Sentry KM for PATROL
Version 1.8.01
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands: lsiutil
LSI Logic MegaRAID PowerConsole
This connector provides disk monitoring through the LsiLogic MegaRAID PowerConsole SNMP sub-agent which supports all MegaRAID-based RAID controllers.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Operating systems: Microsoft Windows, Linux
Instrumentation layer: LSI MegaRAID PowerConsole
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
LsiLogic MegaRAID SAS
This connector provides disk monitoring through the LsiLogic MegaRAID SAS SNMP sub-agent which supports all LSI MegaRaid SAS RAID controllers.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Reference Guide
319
Hardware Sentry KM for PATROL
Version 1.8.01
Operating systems: Microsoft Windows, Linux
Instrumentation layer: LSI MegaRAID SAS SNMP Agent
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / ErrorCount
This connector is able to monitor the local host and/or a remote sy stem.
LsiLogic MegaRAID SAS (Newer Controllers)
This connector provides disk monitoring through the LsiLogic MegaRAID SAS SNMP sub-agent which supports newer LSI MegaRaid SAS RAID controllers.
Target
Typical platform(s): Fujitsu-Siemens PRIMERGY
Operating system(s): Microsoft Windows, Linux
Instrumentation layer: LSI MegaRAID SAS SNMP Agent
Technology used: SNMP
Reference Guide
320
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / ErrorCount
This connector is able to monitor the local host and/or a remote sy stem.
LSI MegaCli
Gives physical disk and array status.
Target
Typical platform(s): Any System with an LSI controller managed by MegaCli / CmdTool2
Operating system(s): Microsoft Windows
Instrumentation layer: Windows system commands (MegaCli / CmdTool2)
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / BatteryStatus
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
321
Hardware Sentry KM for PATROL
Version 1.8.01
LSI/Mylex GAM Server
This connector provides disk monitoring through the Mylex SNMP sub-agent which supports all Mylex disk controllers.
Target
Typical platform(s): Fujitsu-Siemens PRIMERGY
Operating system(s): Microsoft Windows, Linux
Instrumentation layer: Mylex GAM Server
Technology used: SNMP
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
McData Fibre Switch
Target
Typical platform(s): McData San Switches
Operating system(s): Storage
Instrumentation layer: SNMP
Technology used: SNMP
Reference Guide
322
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Blades (MS_HW_BLADE)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_BLADE / Status
MS_HW_BLADE / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedBytesRate
MS_HW_NETWORK / ReceivedBytesRate
MegaCLI Managed Raid Controllers
Gives physical disk and array status.
Target
Typical platform(s): All Solaris Machines with LSI controllers and IBM Servers with EXP3000 External
Bays
Operating system(s): Sun Solaris, Linux
Instrumentation layer: MegaCli (LSI) managed RAID card
Reference Guide
323
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / BatteryStatus
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands:
MegaCli
MIB-2 Standard SNMP Agent - Network Interfaces
This connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-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
Technology used: SNMP
Discovered obj ects
Network cards (MS_HW_NETWORK)
Reference Guide
324
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
MIB-2 Standard SNMP Agent - Network Interfaces - Linux
This connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2 standard SNMP Agent.
Target
Typical platform(s): Any SNMP-instrumented device
Operating system(s): Linux
Instrumentation layer: MIB-2 Standard SNMP Agent
Technology used: SNMP
Discovered obj ects
Network cards (MS_HW_NETWORK)
Reference Guide
325
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
MIB-2 Standard SNMP Agent - Network Interfaces - Windows
This connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2 standard SNMP Agent.
Target
Typical platform(s): Any SNMP-instrumented device
Operating system(s): Microsoft Windows
Instrumentation layer: MIB-2 Standard SNMP Agent
Technology used: SNMP
Reference Guide
326
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
MIB-2 Standard SNMP Agent - Network Interfaces - Solaris
This connector discovers the enclosure and Ethernet ports of an Ethernet switch equipped with a MIB-2 standard SNMP Agent.
Target
Typical platform(s): Any SNMP-instrumented device
Operating system(s): Sun Solaris
Instrumentation layer: MIB-2 Standard SNMP Agent
Technology used: SNMP
Reference Guide
327
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
Motherboard Monitor
This connector provides hardware monitoring through Motherboard Monitor version 5.x which supports almost all non-branded PCs under Windows.
Target
Typical platform: Unbranded PC
Operating system: Microsoft Windows
Instrumentation layer: Motherboard Monitor
Technology used: System commands
Reference Guide
328
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
This connector is av ailable for use to monitor the local host only .
NetApp Filer - SNMP Agent
This connector discovers the enclosure and the disks of NetApp disk arrays (filer) as well as the various environment sensors (temperatures, fans, power supplies, etc.). It relies on the SNMP protocol.
Target
Typical platform(s): Disk Array
Operating system(s): Storage Device
Instrumentation layer: NetApp SNMP Agent
Technology used: SNMP
Reference Guide
329
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Batteries (MS_HW_BATTERY)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_LOGICALDISK / UnallocatedSpace
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
This connector is able to monitor remote sy stem only .
NEC ESMPRO Agent
This connector provides hardware monitoring through the NEC ESMPRO Agent which supports almost all
NEC Express5800 and some BULL NovaScale servers running Windows and Linux.
Target
Typical platform: NEC Express5800
Operating systems: Microsoft Windows, Linux
Instrumentation layer: NEC ESMPRO Agent
Reference Guide
330
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: SNMP
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Promise FastTrack
This connector provides disk monitoring through the Promise FastTrack SNMP agent.
Target
Typical platform: Fujitsu-Siemens PRIMERGY
Operating systems: Microsoft Windows, Linux
Instrumentation layer: Promise FastTrack SNMP Agent
Technology used: SNMP
Reference Guide
331
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_DISKCONTROLLER / BatteryStatus
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
Quantum (ADIC) Based Tape Libraries
Target
Typical platform(s): Quantum (ADIC) Tape Library
Operating system(s): Storage Device
Instrumentation layer: Quantum SNMP Agent (ADIC-TAPE-LIBRARY-MIB)
Technology used: SNMP
Reference Guide
332
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Fans (MS_HW_FAN)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Tape drive (MS_HW_TAPEDRIVE)
Robotic (MS_HW_ROBOTIC)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_TAPEDRIVE / Status
MS_HW_TAPEDRIVE / StatusInformation
MS_HW_TAPEDRIVE / NeedsCleaning
MS_HW_TAPEDRIVE / MountCount
MS_HW_ROBOTIC / Status
MS_HW_ROBOTIC / StatusInformation
This connector is able to monitor remote sy stem only .
SmartMonTools
This connector provides S.M.A.R.T.-enabled physical disk information through the smartd/smartctl utility under Linux
Target
Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, Sun Fire
(x64)
Operating system: Linux
Instrumentation layer: SmartMonTools
Technology used: System commands
Reference Guide
333
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Temperature sensors (MS_HW_TEMPERATURE)
Parameters collected
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_TEMPERATURE / Temperature
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the command:
/usr/sbin/smartctl
/bin/dd.
SMI-S Compliant Disk Arrays
This connector discovers the enclosure and the disks of SAN disk arrays, as well as the storage pools and storage volumes. It will also discovery and monitor the FC ports of the array and the various environment sensors when available (temperatures, fans, power supplies, etc.). It relies on the WBEM technology and supports SMI-S compliant disk arrays only.
Target
Typical platform(s): Disk Array
Operating system(s): Storage Device
Instrumentation layer: SMI-S Agent provided by the array vendor
Technology used: WBEM
Reference Guide
334
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_LOGICALDISK / UnallocatedSpace
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
SMI-S Compliant HBAs
This connector discovers the HBAs of a server. It relies on the WBEM technology and supports SMI-S compliant HBAs only.
Target
Typical platform(s): Server with HBAs
Operating system(s): Microsoft Windows, Linux, IBM AIX, HP-UX, Tru64, HP OpenVMS, Sun Solaris
Reference Guide
335
Hardware Sentry KM for PATROL
Version 1.8.01
Instrumentation layer: SMI-S Agent provided by the HBA vendor
Technology used: WBEM
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Network cards (MS_HW_NETWORK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
This connector is able to monitor the local host and/or a remote sy stem.
SMI-S Compliant RAID Controller - Linux
This connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agent component of the IBM Director Agent version 5.20.x / 6.10.x which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platform(s): IBM xSeries, IBM Netfinity
Operating system(s): Linux
Instrumentation layer: IBM Director Agent 5.20.x / 6.10.x
Technology used: WBEM
Reference Guide
336
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
SMI-S Compliant RAID Controller - Windows
This connector provides IBM ServeRAID disks monitoring through the IBM ServeRAID Manager Agent component of the IBM Director Agent version 5.20.x (or the 6.10.x common agent) which supports almost all IBM Netfinity and xSeries servers.
Target
Typical platform(s): IBM xSeries, IBM Netfinity
Operating system(s): Microsoft Windows
Instrumentation layer: IBM Director Agent 5.20.x / 6.10.x
Technology used: WMI
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
337
Hardware Sentry KM for PATROL
Version 1.8.01
SMI-S Compliant Storage Libraries
This connector discovers the enclosure of a storage library as well as its specialized devices: tape drives, cartridges, media changers, etc.. It will also discovery and monitor the FC ports of the array and the various environment sensors when available (temperatures, fans, power supplies, etc.). It relies on the WBEM technology and supports SMI-S compliant tape libraries only.
Target
Typical platform(s): Storage Libraries
Operating system(s): Storage Device
Instrumentation layer: SMI-S Agent provided by the library vendor
Technology used: WBEM
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Tape drives (MS_HW_TAPEDRIVE)
Robotics (MS_HW_ROBOTIC)
Reference Guide
338
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_TAPEDRIVE / Status
MS_HW_TAPEDRIVE / StatusInformation
MS_HW_TAPEDRIVE / MountCount
MS_HW_TAPEDRIVE / NeedsCleaning
MS_HW_ROBOTICS / Status
MS_HW_ROBOTICS / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
SMI-S Compliant SAN Switches
This connector discovers the enclosure and fiber-channel ports of SAN switches as well as the various environment sensors (temperatures, fans, power supplies, etc.). It relies on the WBEM technology and supports SMI-S compliant switches only.
Target
Typical platform(s): SAN Switches
Operating system(s): Storage Device
Instrumentation layer: SMI-S Agent provided by the switch vendor
Technology used: WBEM
Reference Guide
339
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
SNIA Compliant Tape Libraries
Target
Typical platform(s): IBM Tape Library 3584 / Various TS3xxx libraries from IBM based on the SNIA mib
Operating system(s): Storage Device
Instrumentation layer: SNIA Compliant SNMP Agent (SNIA-SML-MIB)
Technology used: SNMP
Reference Guide
340
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Enclosure model (MS_HW_ENCLOSURE)
Tape drive (MS_HW_TAPEDRIVE)
Robotic (MS_HW_ROBOTIC)
Collected parameters
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_TAPEDRIVE / Status
MS_HW_TAPEDRIVE / StatusInformation
MS_HW_TAPEDRIVE / NeedsCleaning
MS_HW_ROBOTIC / Status
MS_HW_ROBOTIC / StatusInformation
This connector targets remote dev ices only .
SPARC Enterprise Mx000 (XSCF)
Gives environmental information (temperatures, fans, etc.) and boards status on SPARC Enterprise
M4000, M5000, M8000 and M9000 servers.
Target
Typical platform(s): SPARC Enterprise Mx000
Operating system(s): Sun Solaris
Instrumentation layer: Sun XSCF utilities installed on the System Controller
Technology used: System commands
Reference Guide
341
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_OTHERDEVICE / PowerConsumption
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
This connector targets remote dev ices only .
StorageTek LSeries Tape Library
This connector provides basic hardware monitoring of the StorageTek LSeries tape libraries through their built-in SNMP agent. Needs to run remotely.
Target
Typical platform(s): StorageTek LSeries
Operating system(s): Storage Device
Instrumentation layer: StorageTek LSeries SNMP Agent
Technology used: SNMP
Reference Guide
342
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Tape drive (MS_HW_TAPEDRIVE)
Robotic (MS_HW_ROBOTIC)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_OTHERDEVICE / UsageCount
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_TAPEDRIVE / Status
MS_HW_TAPEDRIVE / StatusInformation
MS_HW_TAPEDRIVE / MountCount
MS_HW_ROBOTICS / Status
MS_HW_ROBOTICS / StatusInformation
MS_HW_ROBOTICS / MoveCount
MS_HW_ROBOTICS / ErrorCount
This connector is able to monitor remote sy stem only .
StorageTek StreamLine Tape Library
This connector provides basic hardware monitoring of the StorageTek StreamLine tape libraries through their built-in SNMP agent. Needs to run remotely.
Target
Typical platform(s): StorageTek StreamLine
Operating system(s): Storage Device
Instrumentation layer: StorageTek StreamLine SNMP Agent
Reference Guide
343
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: SNMP
Discovered obj ects
Enclosure model (MS_HW_ENCLOSURE)
Tape drive (MS_HW_TAPEDRIVE)
Collected parameters
MS_HW_ENCLOSURE / Status
MS_HW_ENCLOSURE / StatusInformation
MS_HW_TAPEDRIVE / Status
MS_HW_TAPEDRIVE / StatusInformation
MS_HW_TAPEDRIVE / MountCount
This connector is able to monitor remote sy stem only .
Sun Advanced Lights–Out Management (ALOM) card
This connector provides environmental and disk information (temperatures, fans, etc.) on Sun SPARC servers equipped with an ALOM card. Telnet must be enabled on the ALOM card.
Target
Typical platform: Sun Fire (SPARC)
Operating system: N/A
Instrumentation layer: Sun Advanced Lights-Out Management (ALOM) card
Technology used: Telnet/SSH
Reference Guide
344
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
This connector targets remote dev ices only .
SUN Blade Chassis
This connector provides hardware monitoring for the SUN Blade Chassis through the CMM SNMP Agent /
SSH (optional).
Target
Typical platform(s): SUN Blade Chassis
Operating system(s): N/A
Instrumentation layer: SUN Blade Chassis CMM SNMP Agent
Technology used: SNMP
Reference Guide
345
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Speed
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
This connector is able to monitor remote sy stem only .
Sun Fire F12K/F15K/F20K/F25K (SMS)
This connector provides environmental information (temperatures, fans, etc.) and boards status on Sun
Fire F12K, F15K, F20K and F25K servers.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun SMS utilities installed on the System Controller (SC on F15K, etc.)
Technology used: System commands
Reference Guide
346
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_ENCLOSURE / PowerConsumption
This connector is able to monitor the local host and/or a remote sy stem.
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
Operating system(s): N/A
Instrumentation layer: SUN Blade SP SNMP Agent
Technology used: SNMP
Reference Guide
347
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_VOLTAGE / Voltage
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is able to monitor remote sy stem only .
Sun Solaris–Environment (ALOM-CMT snapshot)
This connector provides environmental and disk information (temperatures, fans, etc.) on Sun SPARC
T1/T2 servers equipped with an ALOM card. Gathers the hardware information from the ALOM card inband (no telnet or SSH connection over the network). Requires the SUNWexplo (Sun Explorer) package.
Target
Typical platform: Sun Fire (SPARC T1/T2)
Operating system: Sun Solaris
Instrumentation layer: Sun Explorer and the ALOM-CMT card
Technology used: System commands
Reference Guide
348
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Other devices (MS_HW_OTHERDEVICE)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following commands: /opt/
SUNWexplo/bin/snapshot.
Sun Solaris–Environment (prtpicl)
This connector provides environmental information (temperatures, fans, etc.) on several Sun platforms through the prtpicl utility. This connector is to be used mainly on Solaris 10 systems.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (prtpicl, etc.)
Reference Guide
349
Hardware Sentry KM for PATROL
Version 1.8.01
Technology used: System commands
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Enclosure model (MS_HW_ENCLOSURE)
LEDs (MS_HW_LED)
Collected parameters
MS_HW_FAN / Speed
MS_HW_FAN / SpeedPercent
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_LED / Status
MS_HW_LED / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Sun Solaris–Environment (prtdiag, lom)
This connector provides environmental information (temperatures, fans, etc.) on several Sun platforms through the prtdiag or lom utility.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (prtdiag, lom, psrinfo, etc.)
Technology used: System commands
Reference Guide
350
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Enclosure model (MS_HW_ENCLOSURE)
Parameters collected
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the 'sudo' utility for the following command: /usr/sbin/lom.
Sun Solaris - Fault Manager (Memory)
This connector parses fmadm faulty command looking for faulty memory modules
Target
Typical platform(s): Sun Fire (SPARC)
Operating system(s): Sun Solaris
Instrumentation layer: Sun Solaris system commands (fmadm)
Technology used: System commands
Reference Guide
351
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Memory modules (MS_HW_MEMORY)
Collected parameters
MS_HW_OTHERDEVICE / Status
MS_HW_OTHERDEVICE / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the 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
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (cediag, cestat)
Technology used: System commands
Reference Guide
352
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Memory modules (MS_HW_MEMORY)
Parameters collected
MS_HW_MEMORY / PredictedFailure
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the command: /opt/SUNWcest/ bin/cediag.
Both cediag and cestat need to be added to the sudoers file.
Sun Solaris - Multi-core 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
Operating system(s): Sun Solaris
Instrumentation layer: Sun Solaris system commands (psrinfo, etc.)
Technology used: System commands
Reference Guide
353
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Processors (MS_HW_CPU)
CPU Cores (MS_HW_CPUCORE)
Collected parameters
MS_HW_CPUCORE / Status
MS_HW_CPUCORE / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Sun Solaris–Network
This connector provides the monitoring of network cards on all Sun Solaris systems.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (kstat, ndd, ifconfig, etc.)
Technology used: System commands
Discovered obj ects
Network cards (MS_HW_NETWORK)
Parameters collected
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / DuplexMode
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / ReceivedBytesRate
MS_HW_NETWORK / TransmittedBytesRate
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
354
Hardware Sentry KM for PATROL
Version 1.8.01
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the sudo utility for the following commands:
/usr/bin/kstat
/usr/sbin/ndd
Sun Solaris–Non-Sun Disks
This connector provides physical disk information (status and error count) on Sun Solaris platforms through the iostat -En utility. Supports only non-Sun disks in Sun systems. This connector needs to be manually activated and will never be picked up automatically during the platform detection and components discovery.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (iostat, dd)
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_PHYSICALDISK / HardErrorCount
MS_HW_PHYSICALDISK / MediaErrorCount
MS_HW_PHYSICALDISK / DeviceNotReadyErrorCount
MS_HW_PHYSICALDISK / NoDeviceErrorCount
MS_HW_PHYSICALDISK / TransportErrorCount
MS_HW_PHYSICALDISK / RecoverableErrorCount
MS_HW_PHYSICALDISK / IllegalRequestErrorCount
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
355
Hardware Sentry KM for PATROL
Version 1.8.01
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the 'sudo' utility for the following command: /usr/bin/ dd.
Sun Solaris–Processors (psrinfo)
This connector discovers and monitors the processor in any Sun SPARC-based Solaris machine through the psrinfo system command.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (psrinfo, etc.)
Technology used: System commands
Discovered obj ects
Processors (MS_HW_CPU)
Parameters collected
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Sun Solaris - RAID Disks (Raidctl)
Gives physical disk and array status.
Target
Typical platform(s): All Sun Platforms with Hardware Raid Controllers
Operating system(s): Sun Solaris
Reference Guide
356
Hardware Sentry KM for PATROL
Version 1.8.01
Instrumentation layer: Sun Solaris system commands (raidctl)
Technology used: System commands
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands. Alternatively, you can configure the product to use the 'sudo' utility for the following commands:* /usr/sbin/raidctl
Sun Solaris–Sun Disks
This connector provides physical disk information (status and error count) on Sun Solaris systems through the iostat -En utility. Supports only official Sun disks.
Target
Typical platform: Sun Fire (SPARC)
Operating system: Sun Solaris
Instrumentation layer: Sun Solaris system commands (iostat, dd)
Technology used: System commands
Reference Guide
357
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_PHYSICALDISK / ErrorCount
MS_HW_PHYSICALDISK / HardErrorCount
MS_HW_PHYSICALDISK / MediaErrorCount
MS_HW_PHYSICALDISK / DeviceNotReadyErrorCount
MS_HW_PHYSICALDISK / NoDeviceErrorCount
MS_HW_PHYSICALDISK / TransportErrorCount
MS_HW_PHYSICALDISK / RecoverableErrorCount
MS_HW_PHYSICALDISK / IllegalRequestErrorCount
MS_HW_PHYSICALDISK / PredictedFailure
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector is able to monitor the local host and/or a remote sy stem.
Credentials required
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Alternatively, you can configure the product to use the sudo utility for the command: /usr/sbin/dd.
Sun Solaris - Tape Drives
Gives physical disk information (status and error count) on Sun Solaris systems through the iostat -En utility. Supports only official Sun disks.
Target
Typical platform(s): Sun Fire (SPARC)
Operating system(s): Sun Solaris
Instrumentation layer: Sun Solaris system commands (iostat, dd)
Technology used: System commands
Reference Guide
358
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Tape drives (MS_HW_TAPEDRIVE)
Collected parameters
MS_HW_TAPEDRIVE / ErrorCount
This connector is able to monitor the local host and/or a remote sy stem.
This connector probably requires root privileges for its proper operation. You therefore will need to configure the product to use the root login/password to execute external commands.
Windows - DiskPart
Discovers and monitors the logical disks in a Microsoft Windows system through the DISKPART.EXE
utility, notably the software RAID volumes.
Target
Typical platform(s): Windows
Operating system(s): Microsoft Windows
Instrumentation layer: The DISKPART.EXE command-line utility
Technology used: System commands
Discovered obj ects
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Collected parameters
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
This connector is av ailable for use to monitor the local host only .
Reference Guide
359
Hardware Sentry KM for PATROL
Version 1.8.01
VMware ESXi 3.x
This connector provides hardware monitoring through the VMware ESXi implementation of SMASH, through the WBEM protocol.
Target
Typical platform(s): VMware ESXi
Operating system(s): Linux
Instrumentation layer: WBEM
Technology used: WBEM
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Reference Guide
360
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / StatusInformation
MS_HW_FAN / Speed
MS_HW_FAN / SpeedPercent
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / StatusInformation
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / StatusInformation
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_POWERSUPPLY / StatusInformation
MS_HW_MEMORY / Status
MS_HW_MEMORY / StatusInformation
MS_HW_CPU / Status
MS_HW_CPU / StatusInformation
MS_HW_NETWORK / Status
MS_HW_NETWORK / LinkStatus
MS_HW_ENCLOSURE / PowerConsumption
This connector is able to monitor the local host and/or a remote sy stem.
VMware ESX4i - Disks (IPMI)
This connector provides disk monitoring through the VMware ESX4i agent's discrete IPMI Sensors
Target
Typical platform(s): VMware ESX4i
Operating system(s): Linux
Instrumentation layer: WBEM
Technology used: WBEM
Discovered obj ects
Physical disks (MS_HW_PHYSICALDISK)
Reference Guide
361
Hardware Sentry KM for PATROL
Version 1.8.01
Collected parameters
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector targets remote dev ices only .
VMware ESX4i - Disks (VMware)
This connector provides disk monitoring through the VMware ESX4i agent's VMware classes.
Target
Typical platform(s): VMware ESX4i
Operating system(s): Linux
Instrumentation layer: WBEM
Technology used: WBEM
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Logical disks, RAIDs (MS_HW_LOGICALDISK)
Physical disks (MS_HW_PHYSICALDISK)
Collected parameters
MS_HW_DISKCONTROLLER / ControllerStatus
MS_HW_DISKCONTROLLER / StatusInformation
MS_HW_LOGICALDISK / Status
MS_HW_LOGICALDISK / StatusInformation
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
This connector targets remote dev ices only .
Reference Guide
362
Hardware Sentry KM for PATROL
Version 1.8.01
VMware ESXi 4.x / 5.x
This connector provides hardware monitoring through the VMware ESXi implementation of SMASH, through the WBEM protocol.
Target
Typical platform(s): VMware ESXi
Operating system(s): Linux
Instrumentation layer: WBEM
Technology used: WBEM
Discovered obj ects
Fans (MS_HW_FAN)
Voltage sensors (MS_HW_VOLTAGE)
Temperature sensors (MS_HW_TEMPERATURE)
Power supplies (MS_HW_POWERSUPPLY)
Memory modules (MS_HW_MEMORY)
Processors (MS_HW_CPU)
Network cards (MS_HW_NETWORK)
Enclosure model (MS_HW_ENCLOSURE)
Collected parameters
MS_HW_FAN / Status
MS_HW_FAN / Speed
MS_HW_FAN / SpeedPercent
MS_HW_VOLTAGE / Status
MS_HW_VOLTAGE / Voltage
MS_HW_TEMPERATURE / Status
MS_HW_TEMPERATURE / Temperature
MS_HW_POWERSUPPLY / Status
MS_HW_MEMORY / Status
MS_HW_CPU / Status
MS_HW_NETWORK / Status
MS_HW_NETWORK / LinkStatus
MS_HW_ENCLOSURE / PowerConsumption
This connector is able to monitor the local host and/or a remote sy stem.
Reference Guide
363
Hardware Sentry KM for PATROL
Version 1.8.01
WMI - Battery
This connector provides battery monitoring for Windows computers.
Target
Typical platform(s): Any Windows platform
Operating system(s): Microsoft Windows
Instrumentation layer: WMI
Technology used: WMI
Discovered obj ects
Batteries (MS_HW_BATTERY)
Collected parameters
MS_HW_BATTERY / Status
MS_HW_BATTERY / StatusInformation
MS_HW_BATTERY / Charge
MS_HW_BATTERY / TimeLeft
This connector is able to monitor the local host and/or a remote sy stem.
WMI–Disks
This connector provides monitoring of the S.M.A.R.T.-enabled disks that are directly handled by
Windows (and WBEM through the WMI service). Deactivates the connector if only MPIO disks (LUN Multi-
Path Disk Device) are found.
Target
Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NEC
Express5800, Sun Fire (x64)
Operating system: Microsoft Windows
Instrumentation layer: WMI
Technology used: WMI
Reference Guide
364
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Disk controllers (MS_HW_DISKCONTROLLER)
Physical disks (MS_HW_PHYSICALDISK)
Parameters collected
MS_HW_PHYSICALDISK / Status
MS_HW_PHYSICALDISK / StatusInformation
MS_HW_PHYSICALDISK / PredictedFailure
This connector is able to monitor the local host and/or a remote sy stem.
WMI - HBA
This connector provides the monitoring of HBA cards on all Windows-based systems through the WMI layer (root/WMI namespace).
Target
Typical platform(s): Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NEC
Express5800, Sun Fire (x64)
Operating system(s): Microsoft Windows
Instrumentation layer: WMI and Microsoft Fibre Channel Information tool
Technology used: WMI
Reference Guide
365
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Network cards (MS_HW_NETWORK)
LUN (MS_HW_LUN)
Collected parameters
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
MS_HW_LUN / AvailablePathCount
This connector is able to monitor the local host and/or a remote sy stem.
WMI–Network
This connector provides the monitoring of network cards on all Windows-based systems through the
WMI layer (root/WMI namespace).
Target
Typical platforms: Dell PowerEdge, Fujitsu-Siemens PRIMERGY, HP ProLiant, IBM xSeries, NEC
Express5800, Sun Fire (x64)
Operating system: Microsoft Windows
Instrumentation layer: WMI
Technology used: WMI
Reference Guide
366
Hardware Sentry KM for PATROL
Version 1.8.01
Discovered obj ects
Network cards (MS_HW_NETWORK)
Parameters collected
MS_HW_NETWORK / Status
MS_HW_NETWORK / StatusInformation
MS_HW_NETWORK / LinkStatus
MS_HW_NETWORK / LinkSpeed
MS_HW_NETWORK / ErrorCount
MS_HW_NETWORK / TransmittedPacketsRate
MS_HW_NETWORK / ReceivedPacketsRate
This connector is able to monitor the local host and/or a remote sy stem.
Configuration Variables
Global Configuration Variables
This section lists the configuration variables used by Hardware Sentry KM for PATROL. Configuration variables are stored in the PATROL Agent configuration and can be managed through:
PATROL Configuration Manager (PCM) wpconfig.exe (Windows) xpconfig (UNIX/Linux)
Global configuration variables are stored under the /SENTRY/HARDWARE folder in the configuration tree. Host-specific variables are stored under the /SENTRY/HARDWARE/<hostname> folder in the configuration tree. By default, variables for the local host are stored under /SENTRY/HARDWARE/ localhost. This folder cannot be removed from the configuration tree of Hardware Sentry.
The following table sums up the configuration variables used by Hardware Sentry globally, i.e that apply to all of the monitored hosts. These configuration variables are stored under /SENTRY/HARDWARE in the PATROL Agent’s configuration.
Variable Description
AlertActions List of alert actions to be executed by Hardware Sentry upon a hardware failure.
Default: A PATROL event and an annotation on the parameter.
automaticReinitialization If set to 1, triggers a re-initialization of the KM, as if the “Reinitialize KM” KM Command had been invoked. The discovery checks this variable every hour (by default) and deletes it before performing the re-initialization.
collectionHubHeapSizeMax Maximum heap size in megabytes allocated to the Java Collection Hub.
Default: Not set (assumed 128 MB) collectionHubHeapSizeMin Minimum heap size in megabytes allocated to Java Collection Hub.
Default: Not set (assumed 128 MB)
367
Reference Guide
Hardware Sentry KM for PATROL
Version 1.8.01
Variable Description
collectionHubOverrideJava
CommandLine
Command line used by the KM to launch the Java Collection Hub.
Default: Not set
This variable should only be set if instructed by Sentry Support. collectTimeout currentVersion
Maximum time in seconds the collectors wait for the previous collection to complete. When this timeout is reached, it means the previous collection did not complete in a timely fashion.
An error message is displayed in the System Output Window and the next collection is canceled.
Default: Not set (assumed 300 seconds)
Indicates the version level of the configuration. This should always match with the KM version. The KM uses this variable to perform migration operations on the configuration variables. The variable is automatically set by the KM during its initialization.
Default: 1.8.01.
t deactivatedDeviceClassLis List of classes that are deactivated, for which no discovery and no collection will be performed. Use this variable to completely disable the monitoring of a specific type of objects.
debugEndTime debugMode
Specifies when the debug mode will be disabled.
Format required: YYYY/MM/DD HH:MM:SS
When set to ‘1’, enables the debug mode of Hardware Sentry.
Default: Not set defaultCommandTimeout Timeout in seconds used when Hardware Sentry executes an OS Command.
Default: 30. Unit: seconds defaultReinitializationOptio ns
List of default options to be executed by Hardware Sentry on reinitialization. The default values are: 0=unchecked; 1=checked resetThresholds resetThresholdManagementMode resetAlertActions resetOtherAlertSettings resetDebugMode resetRemovedPausedObjectList resetReport resetSecuritySettings resetPreselectedConnectors
Insert a colon “;” between the variable and its value: “resetThresholds;1”; and if you enter multiple variables, they need to be separated by a carriage return.
Example: “resetThresholds;1” will display the remove thresholds option selected by default in the Reinitialize KM wizard.
dirCommand OS Command used to list the files in a directory. This command is used to find the installed connectors in the "hdfPath" directory.
Default:
On Windows: dir /A:-D /B /O:-D /T:W /S %{FOLDERPATH}
On UNIX/Linux: ls -atpR1 %{FOLDERPATH} disableDebugSNMPWalk disableForcedDefaultAcco unt
When set to 1, prevents the KM from performing an SNMP dump of the monitored systems in debug mode.
Default: Not set.
When set to 1, prevents the KM from explicitly using the /AgentSetup/defaultAccount credentials when running external commands.
Default: Not set.
Reference Guide
368
Hardware Sentry KM for PATROL
Version 1.8.01
Variable Description
disableJavaInformationMe ssage
When set to 1, suppresses the warning message displayed after changing the Java configuration settings.
Default: Not set.
disableLocalhost When set to 1, disables the default monitoring of the local host by the KM. To remove the monitoring of the local host, all of the /SENTRY/HARDWARE/localhost/… configuration variables need to be removed and the disableLocalhost variable must be set to 1 to prevent
Hardware Sentry KM for PATROL from restoring the variables for the monitoring of the local host.
Default: Not set.
disableMissingDeviceDetec tion
When set to ‘1’, disables the missing device detection mechanism of Hardware Sentry. By default, Hardware Sentry raises an alarm for devices that were discovered and that are no longer discovered.
Default: Not set disablePslExecuteBugWork around
When set to ‘1’, disables the workaround in the KM for a bug in the PslExecute() PSL function.
If the KM detects that the version of the PATROL Agent is affected by the PslExecute() bug, it uses an alternate technique to create asynchronous threads with the event_trigger() function and the RemPsl standard event. The disablePslExecuteBugWorkaround variable disables this workaround.
Default: Not set.
errorCountAutoResetTime out
Time in seconds after which the alerts on the ErrorCount parameters
(MS_HW_PHYSICALDISK, MS_HW_LOGICALDISK, MS_HW_MEMORY, MS_HW_ROBOTICS,
MS_HW_TAPEDRIVE) are automatically acknowledged and reset.
Default: Not set (assumes a manual acknowledge is required through a KM Command).
errorCountParametersThr esholds
Thresholds are set per parameter, one parameter threshold per line, using the following format:
<parameterName>;<alarm1ThresholdValue>;<alarm1Type>;
<alarm1NTimes>;<alarm2ThresholdValue>;<alarm2Type>;
<alarm2NTimes>
<parameterName>;<alarm1ThresholdValue>;<alarm1Type>;
<alarm1NTimes>;<alarm2ThresholdValue>;<alarm2Type>;
<alarm2NTimes>
Where: parameterName is DeviceNotReadyErrorCount, MediaErrorCount, NoDeviceErrorCount,
HardErrorCount, IllegalRequestErrorCount, RecoverableErrorCount or
TransportErrorCount alarm1ThresholdValue is the threshold for the ALARM1 range alarm1Type is the type of the alert for ALARM1 (VOID, OK, WARN or ALARM) alarm1NTimes is the number of times the parameter must stay in the ALARM1 range before triggering an alert (default: 1) alarm2ThresholdValue is the threshold for the ALARM2 range alarm2Type is the type of the alert for ALARM2 (VOID, OK, WARN or ALARM) alarm2NTimes is the number of times the parameter must stay in the ALARM2 range before triggering an alert (default: 1)
Example:
MediaErrorCount;1;ALARM;1 -> Trigger an alarm if one or more media error is encountered
RecoverableErrorCount;1;WARN;2;2;ALARM;1 -> Trigger a warning if 1 recoverable error is encountered twice in a row, alarm after 2
Reference Guide
369
Hardware Sentry KM for PATROL
Version 1.8.01
Variable Description
findWbemNamespaceTime out forceSnmpSerialization globalDiscoveryTimeout hdfPath
Number of seconds after which a remote Hardware Sentry KM for PATROL stops trying to get a server namespace via WBEM.
Default value: 1200s.
When set to ‘1’, forces the serialization of the SNMP requests made by Hardware Sentry. As
Hardware Sentry is a multi-threaded program, it can send several SNMP requests at the same time on multi-processor computers. Some poorly written SNMP agents may not support this.
Default: Not set.
Maximum time in seconds the main discovery process waits for the previous discovery to complete. When this timeout is reached, it means the previous discovery did not complete in a timely fashion. An error message is displayed in the System Output Window and the next discovery is canceled.
Default: Not set (assumed 600 seconds).
Alternate path where the connector files (*.hdf) are stored.
Default: Not set (assumed $PATROL_HOME/lib/MS_HW_hdf).
individualDiscoveriesTimeo ut interactiveCommandTimeo ut intrusionDetectionAlert
Maximum time in seconds the class-specific discovery processes wait for the previous discovery to complete. When this timeout is reached, it means the previous discovery did not complete in a timely fashion. An error message is displayed in the System Output Window and the next discovery is canceled.
Default: Not set (assumed 300 seconds).
Reserved for future use.
Default: Not set (assumed 15 seconds).
Alert settings for enclosure intrusion detection. Possible values are:
Never: No alert will ever be triggered even if the chassis is opened
Always: An alert will be always be triggered when the enclosure is opened
Default: An alert will be triggered only if a previously closed enclosure is detected open ipmiTimeout ipmitoolPath
Time in seconds after which IPMI queries are considered as failed.
Default value: Not set (assumed 300 seconds).
Indicates the path to the ipmitool utility on Linux and Solaris systems. This can be used if the
KM cannot find the location of the ipmitool utility automatically.
Default: Not set.
Password associated to the javaUsername variable.
javaPassword javaPath javaUsername maxConcurrentCollectThre ads
Maximum number of concurrent collection threads.
Default: 50.
maxConcurrentDiscoveryT hreads
Maximum number of concurrent discovery threads.
Default:10.
missingMaxOCC noMissingDeviceDetection
Classes
Path to the folder containing the Java executable used by the Collection Hub.
Default: Not set (The KM will search for a suitable JRE automatically).
Username used to launch the Java Collection Hub.
Default: Not set.
Default N times value for the “Missing” parameter. Will be applied to all hosts unless a host specific value is specified.
List of the classes that will not trigger "missing device" alerts. Typically, the related classes are:
MS_HW_LOGICALDISK
MS_HW_VOLTAGE
MS_HW_TEMPERATURE
Reference Guide
370
Hardware Sentry KM for PATROL
Version 1.8.01
Variable Description
MS_HW_ENCLOSURE
MS_HW_LED pathToAWK pathToAWKUnix pathToAWKWindows pausedObjectList pemMessages sowMessages
Path to the nawk or awk executable.
Default on Windows: Default: Not set (assumed %PATROL_HOME%\bin\nawk.exe).
Default on UNIX: Default: Not set (assumed /usr/bin/nawk or /usr/bin/awk).
Same as pathToAWK, but only applicable to UNIX agents
Same as pathToAWK, but only applicable to Windows agents
Lists the PATROL object path of paused objects.
How much internal information should be sent as PATROL events.
When set to ‘all’, all internal Hardware Sentry messages (problems and informational messages).
When set to ‘problems’, only errors and problems.
When set to ‘none’, no internal message at all.
This doesn’t affect the reporting of actual hardware problems.
Default: all remoteCommandMaxConn ectionsPerHost
Maximum number of Telnet or SSH sessions opened at once for a single host.
Default: Not set (assumed 5).
remoteCommandTimeout Number of seconds after which a remote OS command execution will be killed.
Default: Not set (assumed 60 seconds).
removedObjectList reportFilename reportFolder reportHostList reportScheduledDays reportScheduledTime reportScheduledToStart
List of instances that have been removed from the monitoring environment through the
Remove KM Command.
Report file name
Path to the folder where the report will be written
List of hosts for which a report should be written.
Day of the week/month when a report should be written
Time of the day at which the report should be written snmpTimeout
Type of Hardware Health Report scheduling. Possible values are:
Never: No report is written
Hourly: Writes a report every hour
Daily: Writes a report every day
Weekly: Writes a report every week
Monthly: Writes a report every month
Default: Never.
Timeout in seconds when performing SNMP queries. Only applicable when forced SNMP serialization has been enabled (/SENTRY/HARDWARE/forceSnmpSerialization)
Default: Not set (assumed 60 seconds).
snmpWalkMaxItems Maximum number of variables that can be processed by a single SNMP walk operation.
Default: Not set.
How much internal information should be displayed in the System Output Window in the
PATROL Console.
When set to ‘all’, all internal Hardware Sentry messages (problems and informational messages).
Reference Guide
371
Hardware Sentry KM for PATROL
Version 1.8.01
Variable Description
sshClientJarPath sshCommandJarPath startupDelay tableJoinTimeout telnetClientJarPath telnetCommandJarPath
When set to ‘problems’, only errors and problems.
When set to ‘none’, no internal message at all.
This doesn’t affect the reporting of actual hardware problems.
Default: All
Path to the SSH client JAR file.
Default: Not set.
This variable should only be set if instructed by Sentry Support.
Path to the SSH command JAR file.
Default: Not set.
This variable should only be set if instructed by Sentry Support.
Allows the administrator to specify the number of seconds that Hardware Sentry KM for
PATROL will wait before starting its platform detection and discovery. This variable may be useful on fast booting computers where the PATROL Agent starts before other important instrumentation services, which causes false alerts.
Default: Not set (zero)
Timeout in seconds when performing a Table Join
Default: 60
Path to the Telnet client JAR file.
Default: Not set.
This variable should only be set if instructed by Sentry Support.
Path to the Telnet command JAR file.
Default: Not set.
This variable should only be set if instructed by Sentry Support. telnetConnectionMethod
ThresholdManagementMo de ucsJarPath ucsTimeout
Default (Windows): Java (if configured in the KM)
Note: If the PATROL agent version is 3.6.011 or later the connection method used by the
KM is 'sopen'; otherwise it is left blank
Default (UNIX): Telnet
Specifies how Hardware Sentry should manage the alert thresholds on parameters. Please read carefully the Hardware Sentry User Guide for more information on this topic.
Possible values:
‘as’ (through PATROL for Event Management)
‘tuning’ (through the standard "Override parameter" mechanism)
‘none’ (No threshold is set by Hardware Sentry)
Default: ‘Tuning’
Path to the Cisco UCS client JAR file.
Default: Not set.
This variable should only be set if instructed by Sentry Support.
Timeout in seconds when performing a UCS queries.
Default: Not set (assumed 60 seconds).
ucsVbsPath unexpectedStatusManage ment
Path to the Cisco UCS Windows client.
Default: Not set.
This variable should only be set if instructed by Sentry Support.
Type of alert triggered by Hardware Sentry when an unknown status is returned when collecting device information. If the Internal notification is to be triggered as well, separate the values by ';'.
To trigger an Internal KM Issue notification set the second value to '1' . Or set it to '0' if you do not want to trigger the notification.
Example: Trigger a WARNING and no Internal KM Issue notification: 1;0
Ignore status and do not feed parameter but trigger an Internal KM Issue notification:
IGNORE;1
Reference Guide
372
Hardware Sentry KM for PATROL
Version 1.8.01
Variable
UNIXConsoleMode wbemTimeout wmiScriptPath
Description
Default value: 0;0 (Consider the status to be OK and do not trigger an Internal KM Issue notification).
When set to ‘1’, makes Hardware Sentry use short display name for the icons in the PATROL
Consoles. This can be useful for UNIX PATROL Classic Consoles but this flags affects every console connected to the agent.
Default: Not set
Timeout in seconds for a WBEM query to complete.
Default: Not set (assumed 60 seconds).
Path to the script used by the KM to perform WMI queries on Windows.
Default: Not set (use the default WMI client provided with the KM).
Host-Specific Configuration Variables
The following table sums up the configuration variables used by Hardware Sentry for each monitored system. These configuration variables are stored under /SENTRY/HARDWARE/<hostID> in the PATROL
Agent’s configuration.
Variable Description
hostname defaultWattage
Real host name or IP address to be used to communicate with the remote host.
Default: Not set (will use hostID).
Assumed power consumption in Watts of the monitored server. This value will be used instead of the measured or estimated value. Use this variable to override a PowerConsumption parameter value that seems unlikely.
forceWbemNamespa ce
Forces the use of a specific WBEM namespace instead of letting the KM decide the suitable namespace.
Default: Not set.
forceWmiNamespace Forces the use of a specific WMI namespace instead of letting the KM decide the suitable namespace.
Default: Not set ipmiUsername ipmiPassword ipmitoolCommand
Username used for IPMI-over-LAN connections.
Default: Not set (no IPMI-over-LAN query will be done).
Encrypted password used for IPMI-over-LAN connections.
To override the command line used by the KM to perform IPMI requests on Linux and Solaris systems. The specified command needs to provide the exact command to be executed with the following macros:
%{IPMICOMMAND} (will be replaced with “mc info”, “sdr”, “fru”, etc. at run time)
%{USERNAME}
%{PASSWORD}
Example: /usr/bin/ipmitool %{COMMAND} –u %{USERNAME} –p %{PASSWORD}.
Default: Not set (the KM will find the suitable ipmitool command to run automatically).
networkLinkAlarmTy pe
Type of the alert for the LinkStatus parameter of the MS_HW_NETWORK class. Possible values are:
OK
WARN
ALARM
Reference Guide
373
Hardware Sentry KM for PATROL
Version 1.8.01
Default: Not set (assumed WARN) networkLinkDuplexAl armType
Type of the alert for the DuplexMode parameter of the MS_HW_NETWORK class. Possible values are:
OK
WARN
ALARM
Default: Not set (assumed WARN).
networkLinkDuplexS etting
Indicates when the KM needs to trigger an alert on the LinkStatus parameter of the
MS_HW_NETWORK class:
NEVER (will never trigger an alert on LinkStatus)
DEFAULT (will trigger an alert only when LinkStatus downgrades from Plugged to Unplugged)
ALWAYS (will trigger an alert for all interfaces that are unplugged)
Default: Not set (assumed DEFAULT).
networkLinkSetting Indicates when the KM needs to trigger an alert on the LinkStatus parameter of the
MS_HW_NETWORK class:
NEVER (will never trigger an alert on LinkStatus)
DEFAULT (will trigger an alert only when LinkStatus downgrades from Plugged to Unplugged)
ALWAYS (will trigger an alert for all interfaces that are unplugged)
Default: Not set (assumed DEFAULT).
networkLinkSpeedAl armType
Type of the alert for the LinkSpeed parameter of the MS_HW_NETWORK class. Possible values are:
OK
WARN
ALARM
Default: Not set (assumed WARN).
networkLinkSpeedMi nimum
Minimum accepted LinkSpeed value when networkLinkSpeedSetting is configured to “ALWAYS”.
networkLinkSpeedSe tting operatingSystemTyp e
Indicates when the KM needs to trigger an alert on the LinkSpeed parameter of the
MS_HW_NETWORK class:
NEVER (will never trigger an alert on LinkSpeed)
DEFAULT (will trigger an alert only when LinkSpeed downgrades from a higher speed to a slower speed)
ALWAYS (will trigger an alert for all interfaces that are slower than the value indicated by the networkLinkSpeedMinimum configuration variable)
Default: Not set (assumed DEFAULT).
Specifies the type of the monitored platform.
Possible values:
HP (for HP-UX)
Linux
Network (for network switches)
NT (for Windows)
OOB (for management cards, chassis and VMware ESX)
OSF1 (for HP Tru64)
RS6000 (for IBM AIX)
SOLARIS (for Sun/Oracle Solaris)
Storage (for disk arrays, SAN switches and tape libraries)
Reference Guide
374
Hardware Sentry KM for PATROL
Version 1.8.01
osCommandPasswor d
VMS (for OpenVMS).
PSL encrypted password for the user account used to launch external commands (local or remote).
Default: Not set.
osCommandProtocol Protocol used to run remote OS commands.
Possible values are "ssh" or "telnet"
Default: telnet.
osCommandUsernam e
User account used by Hardware Sentry to launch external commands.
Default: Not set (will use the PATROL Agent default account for local commands).
parametersMaxOCC Alter After N Times values for connectors, numeric parameters and discrete parameters. The list is separated by semi-colons.
Default: Not set (assumed 1;1;1 i.e. trigger an alert on all parameters as soon as the thresholds are reached).
preselectedHDFFileLi st
Line-separated list of connectors that have been "pre-selected" by the administrator. It is recommended that you use the KM graphical user interface to modify this variable.
Default: Not set (means: perform platform detection) preselectedHDFFileLi st
Line-separated list of connectors that have been specifically selected by the user. It is recommended that you use the KM graphical user interface to modify this variable.
Default: Not set (means: perform automatic platform detection).
snmpCommunity sudoCommand
SNMP community string used by Hardware Sentry to make SNMP requests.
Default: Not set (let Hardware Sentry decide for local host, no SNMP query will be done on remote systems).
Syntax of the sudo command (including its full path and optional arguments) that will be used by
Hardware Sentry to launch the external commands specified in the useSudoCommandList variable.
Default: Path to the sudo utility if available in the $PATH t useSudoCommandLis Line-separated list of commands that will be launched by Hardware Sentry through the sudo utility.
Please use the graphical user interface to set this variable properly.
Default: Not set (will look for the sudo utility in the $PATH variable).
ucsUsername Username used to performance Cisco UCS XML API calls.
Default: Not set (no UCS XML API call will be done).
ucsPassword ucsEncryption
Encrypted password for the Cisco UCS XML API calls.
Whether the KM should use HTTP or HTTPS (encrypted) for the Cisco UCS XML API calls.
Possible values:
- 0 (non encrypted)
- 1 (encrypted)
Default: Not set (assumed 1, encrypted).
wbemEncryption wbemPassword wbemPort wbemUsername wmiPassword wmiUsername
Use of encryption when performing WBEM queries.
Possible values are: '0' (no encryption), '1' (encrypt data).
Default: 0 (no encryption).
Note: The port usually used to encrypt data for WBEM queries is 5989.
Encrypted password used to perform WBEM queries.
Port used to perform WBEM queries.
Default: 5988.
Username used to perform WBEM queries.
Default: Not set (no WBEM query will be done).
Encrypted password used to perform WMI queries to the remote host.
Username used to perform WMI queries to the remote host.
Default: Not set (no WMI query will be performed, unless wmiUsePatrolDefaultAccount is set to 1).
wmiUsePatrolDefault
Account
When set to 1, tells the KM to use the security token of the PATROL Agent’s default account to connect to remote systems with WMI when the wmiUsername variable is empty.
Reference Guide
375
Hardware Sentry KM for PATROL
Version 1.8.01
Default: Not set (assumed 0, where the KM does not perform any WMI query if wmiUsername is empty).
Reference Guide
376
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Index
- A -
Abnormalities 52
AC Line 69
Actions
Activation 56
Collection 56
Detection 56, 57
Discovery Process 56
Environment discovery 57
Initialization phase 56
Adaptec
AAC 238
Adaptec AAC-based RAID 238
Adaptec DPT-based RAID 237
Adaptec IOManager 235
Adaptec Storage Manager 237, 238
Adaptec Storage Manager DPT 237
Adaptec Storage Manager Web Edition 238
Adaptec Storage Manager Web Edition AAC
238
Adaptec StorMan (RAID) 236
Adaptec U320 HostRAID 235
Adapter 40
Add 41, 50
Create 41
Update 50
Agent 14, 16, 31, 54, 255
Brocade SNMP 238
EQLGROUP-MIB 247 fcSwitch 238
Fujitsu-Siemens Serveview 256
Fusion ioDrive (fio-status) 257
HP iLO / HP Insight Management 259
HP Insight Management 261, 262, 263,
264, 265, 266, 267, 268, 269, 272
HP Insight Management Agents 270
IBM Director Agent 5.20.x / 6.10.x 336, 337
Intel Server Manager 8 SNMP 308, 309
LSI MegaRAID SAS SNMP 319, 320
NetApp SNMP 329
PATROL 13, 39, 57
Promise FastTrack SNMP Agent 331
Quantum SNMP Agent 332
SNMP 57, 244, 247
SNMP Agent 243
SUN Blade Chassis CMM SNMP Agent 345
SUN Blade SP SNMP Agent 347
Alert 147
Actions 130, 148
False 164
Intrusion Detection 165
Macros 161
Network Link 130, 166
Setting 164
Alert Actions
Edit 150
Reset 111
ALL_INSTANCES
Threshold 148
ALOM
ALOM-CMT snapshot 348
ANYINST
Threshold 148
Application Classes 170
Enclosure 92
MS_HW_BATTERY 171, 247, 251, 261,
276, 282, 303, 364
MS_HW_BATTERY_CONT 172
MS_HW_BLADE 173, 240, 241, 246, 255,
258, 260, 276, 286, 309, 322
MS_HW_BLADE_CONT 174
MS_HW_CAPACITYREPORT 87, 175
MS_HW_CONNECTOR 96, 164, 176
MS_HW_CONNECTOR_CONT 178
MS_HW_CPU 179, 181, 249, 256, 268, 270,
272, 277, 279, 284, 288, 293, 294, 295, 297,
298, 299, 301, 302, 307, 308, 330, 341, 347,
353, 356, 360, 363
MS_HW_CPU_CONT 181
MS_HW_CPUCORE 181, 353
MS_HW_CPUCORE_CONT 183
MS_HW_DISKCONTROLLER 58, 171, 184,
219, 235, 236, 237, 238, 248, 251, 255, 257,
261, 262, 264, 267, 278, 280, 281, 282, 284,
291, 292, 293, 294, 295, 297, 298, 299, 300,
303, 305, 307, 309, 316, 317, 318, 319, 320,
321, 322, 323, 331, 332, 336, 337, 355, 356,
357, 362, 364
MS_HW_DISKENCLOSURE 186
377
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Application Classes 170
MS_HW_ENCLOSURE 58, 171, 187, 192,
216, 219, 238, 240, 241, 244, 245, 246, 247,
249, 251, 254, 255, 256, 258, 259, 260, 262,
268, 270, 272, 273, 274, 276, 277, 279, 284,
286, 288, 293, 294, 295, 297, 298, 299, 301,
302, 303, 306, 307, 308, 309, 310, 322, 328,
329, 330, 332, 334, 338, 339, 340, 341, 342,
343, 344, 345, 346, 347, 348, 350, 360, 363
MS_HW_FAN 189, 238, 240, 241, 244, 245,
246, 247, 249, 251, 254, 255, 256, 258, 259,
260, 268, 269, 270, 272, 273, 274, 276, 277,
283, 284, 286, 287, 289, 292, 293, 294, 295,
297, 298, 299, 301, 302, 303, 305, 308, 309,
310, 322, 328, 329, 330, 332, 334, 338, 339,
341, 342, 344, 345, 346, 348, 349, 350, 360,
363
MS_HW_FAN_CONT 191
MS_HW_LED 192, 258
MS_HW_LED_CONT 193
MS_HW_LOGICALDISK 194, 235, 236, 237,
238, 244, 247, 248, 251, 255, 261, 262, 264,
267, 274, 276, 278, 281, 282, 284, 292, 293,
294, 295, 297, 298, 299, 300, 303, 305, 316,
317, 318, 319, 320, 321, 322, 323, 329, 331,
334, 335, 336, 337, 356, 359, 362
MS_HW_LOGICALDISK_CONT 196
MS_HW_LUN 197, 314, 365
MS_HW_LUN_CONT 198
MS_HW_MAIN 56, 57, 59, 199
MS_HW_MEMORY 201, 249, 256, 265, 266,
268, 270, 272, 276, 277, 283, 284, 293, 294,
295, 297, 298, 299, 301, 302, 307, 308, 330,
341, 347, 350, 351, 352, 360, 363
MS_HW_MEMORY_CONT 203
MS_HW_NETWORK 204, 238, 240, 241,
251, 253, 254, 263, 265, 266, 270, 272, 274,
279, 281, 286, 288, 290, 303, 307, 309, 312,
313, 315, 324, 325, 326, 327, 329, 334, 335,
338, 339, 354, 360, 363, 365, 366
MS_HW_NETWORK_CONT 206
MS_HW_NETWORKCARD 276, 322
MS_HW_OTHERDEVICE 207, 240, 243,
245, 246, 249, 251, 258, 259, 260, 262, 265,
270, 272, 274, 276, 303, 309, 322, 334, 338,
339, 341, 342, 344, 346, 348
MS_HW_OTHERDEVICE_CONT 208
MS_HW_PHYSICALDISK 81, 209, 235, 236,
237, 238, 244, 247, 248, 251, 255, 257, 261,
262, 264, 267, 274, 276, 278, 280, 281, 282,
283, 284, 291, 292, 293, 294, 295, 297, 298,
299, 300, 303, 305, 307, 309, 316, 317, 318,
319, 320, 321, 322, 323, 329, 331, 333, 334,
336, 337, 344, 347, 348, 355, 356, 357, 361,
362, 364
MS_HW_PHYSICALDISK_CONT 212
MS_HW_POWERSUPPLY 213, 238, 240,
241, 244, 245, 246, 247, 249, 251, 254, 255,
256, 258, 259, 260, 268, 269, 270, 272, 273,
274, 276, 277, 283, 284, 286, 287, 289, 292,
293, 294, 295, 297, 298, 299, 301, 302, 303,
309, 310, 322, 328, 329, 330, 332, 334, 338,
339, 341, 342, 344, 345, 346, 348, 350, 360,
363
MS_HW_POWERSUPPLY_CONT 214
MS_HW_ROBOTIC 332, 338, 340, 342
MS_HW_ROBOTICS 216
MS_HW_ROBOTICS_CONT 218
MS_HW_TAPEDRIVE 219, 332, 338, 340,
342, 343, 358
MS_HW_TAPEDRIVE_CONT 221
MS_HW_TEMPERATURE 87, 222, 238, 240,
241, 244, 245, 246, 247, 249, 254, 255, 256,
257, 258, 259, 260, 268, 270, 272, 273, 274,
276, 277, 284, 286, 289, 292, 293, 294, 295,
297, 298, 299, 301, 302, 303, 305, 306, 308,
310, 322, 328, 329, 330, 333, 334, 338, 339,
342, 344, 345, 346, 347, 348, 349, 350, 360,
363
MS_HW_TEMPERATURE_CONT 223
MS_HW_VOLTAGE 91, 225, 249, 256, 257,
274, 277, 284, 286, 289, 292, 293, 294, 295,
297, 298, 299, 301, 302, 305, 306, 308, 310,
328, 330, 341, 344, 345, 346, 347, 348, 349,
350, 360, 363
MS_HW_VOLTAGE_CONT 226
Architecture 54, 56
AS_EVENTSPRING.kml 31
Automatic ErrorCount
Reset 141
- B -
Baselines 170
BMC ProactiveNet Performance Management
52
Generation 52
Manage 52
378
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Baselines 170
Requirements 52
Blade Chassis
Monitoring 70
BMC 31, 33
BMC Impact Manager 150
BMC Software 16
BMC Software FTP site 16
BMC Software Installation Utility 14, 16, 17
BMC Software PATROL 31
BMC ProactiveNet Performance Management
Abnormalities 52
Baselines 52
Key Performance Indicators 52
KPI 52
- C -
Changes 5
Cisco
Cisco MDS9000 Series FC switches 240
Cisco UCS 241
Cisco UCS B-Series, C-Series 9
Cisco UCS Interconnect Chassis 9
Cisco UCS Manager (Blade, Fabric
Interconnect Switch) 241
Cisco UCS Manager (XML API) 241
Cisco UCS XML API 241
Classic Console 17
Commands
About 199
Acknowledge Errorcount Alert and Reset
194, 201, 209
Acknowledge IntrusionStatus Alert 187
Add a Remote System or an External Device
199
Alert Actions 199 arameters 222 arcconf 236
Automatic ErrorCount Reset 199 cediag 352 cestat 352
CmdTool2 321
Connection, Credentials and Connectors
199 dd 355, 357, 358
Debug 199
Default Power Wattage 199
Discovery Interval 199
379
Display Settings for Unix Consoles 199
Energy Usage Report 199
Ethernet/Fiber Port Traffic Report 199, 206
Execute 150
Hardware Inventory 199
HP-UX system 279, 280, 281
IBM AIX system 287, 288, 289, 290, 291,
307 ifconfig 354
Instant Hardware Health Report 171, 173,
179, 181, 184, 186, 187, 189, 192, 194, 197,
207, 209, 213, 216, 219, 222, 225
Internal KM Issues Notification 199
Intrusion Detection Alerts 199 iostat 355, 357, 358
Java Settings 199
KM commands 130 kstat 354
Linux system 313 lsiutil 317, 318
MegaCli 321
Menu commands 111
Missing Device Detection 199 ndd 354
Network Link Alerts 199
OS Command 150
Pause 178
Pause Monitoring 171, 172, 173, 174, 176,
179, 181, 183, 184, 186, 187, 189, 191, 192,
193, 194, 196, 197, 198, 199, 201, 203, 206,
207, 208, 209, 212, 213, 214, 216, 218, 219,
221, 222, 223, 225, 226
Polling Interval 199
PSL command 150 psrinfo 353, 356
Raidctl 356
Refresh Parameters 171, 172, 173, 174,
175, 176, 178, 179, 181, 183, 184, 186, 187,
189, 191, 192, 193, 194, 196, 197, 198, 201,
203, 206, 207, 208, 209, 212, 213, 214, 216,
218, 219, 221, 223, 225, 226
Reinitialize KM 199
Remove 171, 172, 173, 174, 176, 179, 181,
183, 184, 186, 187, 189, 191, 192, 193, 194,
196, 197, 198, 201, 203, 206, 207, 208, 209,
212, 213, 214, 216, 218, 219, 221, 222, 223,
225, 226
Remove this System 199
Restore Device or Sensor Monitoring 199
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Commands
Resume Monitoring 171, 172, 173, 174,
176, 178, 179, 181, 183, 184, 186, 187, 189,
191, 192, 193, 194, 196, 197, 198, 199, 201,
203, 206, 207, 208, 209, 212, 213, 214, 216,
218, 219, 221, 222, 223, 225, 226
Schedule Hardware Inventory 199
System 236, 277, 279, 280, 281, 282, 283,
287, 288, 289, 290, 291, 303, 307, 310, 312,
313, 314, 315, 317, 318, 321, 323, 328, 333,
341, 346, 348, 349, 350, 351, 352, 353, 354,
355, 356, 357, 358
Threshold Mechanism Selection 199
Trigger a Discovery 199
Tune Threshold Tolerances 199
Unknown Status Management 199
Windows system 321 comma-separated list 31
Commit KMs 13
Common 17
Common Installer 17
Component 14, 68
Configuration
Basic 110
Variables 367, 373
Configuration Variables 31
Connection 114
Connector 5, 57, 58, 176, 228, 235, 236, 238,
240, 241, 243, 244, 245, 246, 247, 249, 251,
254, 255, 256, 257, 258, 259, 260, 261, 262,
263, 264, 265, 266, 267, 268, 269, 272, 273,
274, 276, 277, 278, 279, 280, 281, 282, 283,
284, 286, 287, 288, 289, 290, 291, 292, 293,
294, 295, 297, 298, 299, 300, 301, 302, 303,
305, 306, 307, 308, 309, 310, 312, 313, 314,
316, 317, 318, 319, 320, 321, 323, 324, 325,
326, 327, 328, 329, 330, 331, 332, 333, 334,
335, 336, 337, 338, 339, 340, 341, 342, 343,
344, 345, 346, 347, 348, 349, 351, 353, 354,
355, 356, 357, 360, 361, 362, 363, 364, 365, 366
Index 228
Selection 114
Console
Mode 143
PATROL 39
Console Server 13, 14, 17
Console Systems 17
Consumption
Electricity 92
Container 212
Container Classes 170
Controller 58
IDE 65
LSI RAID 317, 318
Cooling
Issues 87
Server 87
CPU report 104
Credentials 114, 236, 279, 280, 281, 282, 287,
293, 295, 298, 310, 312, 313, 314, 315, 318,
333, 348, 350, 351, 354, 355, 356, 357, 358
Critical device monitoring 59
Customize
Polling interval 132
- D -
Data
Incoming 83
Outgoing 83
Data Domain Storage Appliance 244
Datacenter
Electrical Issues 91
Temperature 87
DataDirect Networks (DDN) Disk Array 243
Deactivate
Debug Mode 111
Device Class 139
Debug Mode
Deactivate 111
Enable 130, 131
Default 17
Default Power Wattage 92
Degree 68
DELL 9
Dell CMC (Dell Chassis Management
Controller) 245
Dell DRAC Dell Remote Access Card 246
Dell EqualLogic MIBs 247
Dell EqualLogic PS Series 247
Dell EqualLogic PS Series Disk Systems 247
Dell EquaLogic PS Series 9
Dell Modular Chassis (blades) 9
Dell OpenManage Array Manager 248
Dell OpenManage Server 248, 249, 251
Dell OpenManage Server Administrator 9,
54, 248, 249, 251
Dell OpenManage Storage Manager 54,
251
DELL PERC RAID 248, 251
380
Hardware Sentry KM for PATROL
Version 1.8.01
DELL 9
DELL PERC RAID Controller 54
Dell PowerEdge 9, 54, 248, 249, 251
Detect 17, 59, 68, 69
Detection
Automatic 133
Missing Device 140
Developer 13
Device 59, 68
Detection 140
Missing 140
Device Class
Deactivate 139
Device Monitoring
Restore 142
Devices 356
Adapter 204
Backplanes 322
Batteries 251, 276
Battery 247, 261, 282, 303, 364
Blade 240, 241, 246, 255, 258, 286, 309
Blade chassis 54
Brocade SAN Switch 238
Cache Memory 276
Container 208
Controller 64, 65, 235, 237, 238, 248, 251
Controllers 276
CPU Cores 353
Disk 281, 282, 283, 284, 299, 300, 303,
307, 309
Disk array 54
Disk controller 63, 64, 184, 236, 255, 261,
262, 264, 267, 278, 280, 281, 282, 283, 291,
292, 293, 294, 295, 297, 298, 299, 300, 303,
305, 307, 309, 316, 317, 318, 319, 320, 321,
323, 331, 332, 336, 337, 355, 356, 357, 362,
364
Disk controllers 257, 284
Disk Shelves 276
Disk Systems 276
Disks 58, 65
EMU 276
Enclosure 255
Enclosure model 238, 240, 241, 244, 245,
246, 247, 249, 251, 254, 256, 258, 259, 260,
262, 268, 272, 273, 274, 277, 279, 284, 286,
288, 293, 294, 295, 297, 298, 299, 301, 302,
303, 306, 307, 308, 309, 310, 328, 329, 330,
332, 334, 338, 339, 340, 341, 342, 343, 344,
345, 346, 347, 348, 350, 360, 363
Index
381
Environment 255
Ethernet Ports 276
Fan 189, 191, 238, 240, 241, 244, 245,
246, 247, 249, 254, 255, 256, 258, 259, 260,
268, 269, 272, 273, 274, 277, 286, 287, 289,
292, 293, 294, 295, 297, 298, 299, 301, 302,
303, 305, 308, 309, 310, 328, 329, 330, 332,
334, 338, 339, 341, 342, 344, 345, 346, 348,
349, 350, 360, 363
Fans 87, 251, 276, 283, 284, 322
Fiber Ports 276, 322
Fiber switch 54
Hard disks 95
HP 276
IDE 65
IO Module 276
LED 192, 258
Locate 79
Logical disk 63, 64, 65, 235, 236, 237, 238,
244, 247, 248, 251, 255, 261, 262, 264, 267,
274, 278, 281, 282, 292, 293, 294, 295, 297,
298, 299, 300, 303, 305, 316, 317, 318, 319,
320, 321, 323, 329, 331, 334, 335, 336, 337,
356, 362
Logical disks 284
LUN 314, 365
Management Blade 255
Memory module 249, 256, 265, 266, 268,
272, 277, 283, 293, 294, 295, 297, 298, 299,
301, 302, 307, 308, 330, 341, 347, 350, 351,
352, 360, 363
Memory modules 95, 284
Network cards 238, 240, 241, 251, 253,
254, 263, 265, 266, 272, 274, 279, 281, 288,
290, 303, 307, 309, 312, 313, 315, 324, 325,
326, 327, 329, 334, 335, 338, 339, 354, 360,
363, 365, 366
Other devices 251
Others 207, 208, 240, 245, 246, 249, 258,
259, 260, 262, 265, 272, 274, 303, 309, 334,
338, 339, 341, 342, 344, 346, 348
Physical disk 63, 64, 65, 209, 212, 235,
236, 237, 238, 244, 247, 248, 251, 255, 261,
262, 264, 267, 274, 278, 280, 281, 282, 283,
291, 292, 293, 294, 295, 297, 298, 299, 300,
303, 305, 307, 309, 316, 317, 318, 319, 320,
321, 323, 329, 331, 333, 334, 336, 337, 344,
347, 348, 355, 356, 357, 361, 362, 364
Physical disks 251, 257, 276, 284
Physical processor 179
Power Supplies 91, 251, 276, 283, 284,
322
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Devices 356
Power supply 69, 213, 214, 238, 240, 241,
244, 245, 246, 247, 249, 254, 255, 256, 258,
259, 260, 268, 269, 272, 273, 274, 277, 286,
287, 289, 292, 293, 294, 295, 297, 298, 299,
301, 302, 303, 309, 310, 328, 329, 330, 332,
334, 338, 339, 341, 342, 344, 345, 346, 348,
350, 360, 363
Processor 61, 68, 249, 256, 268, 272, 277,
279, 288, 293, 294, 295, 297, 298, 299, 301,
302, 307, 308, 330, 341, 347, 353, 356, 360,
363
Processors 95, 284
RAID Disk 356
Raid Groups 276
RAIDs 236, 244, 247, 255, 261, 262, 264,
267, 274, 278, 281, 282, 284, 292, 293, 294,
295, 297, 298, 299, 300, 303, 305, 316, 317,
318, 319, 320, 321, 323, 329, 331, 334, 335,
336, 337, 356, 362
Robotics 332, 338, 340, 342
RS232 Bus 276
SAN Switches 322
Serial Crossbars 322
Switch Controllers 322
Tape drive 332, 338, 340, 342, 343, 358
Tape library 54
Temperature sensor 238, 240, 241, 244,
245, 246, 247, 249, 254, 256, 258, 260, 268,
272, 273, 274, 277, 286, 289, 292, 293, 297,
298, 299, 303, 305, 306, 308, 310, 328, 329,
330, 333, 334, 338, 339, 342, 344, 345, 346,
347, 348, 349, 350, 360, 363
Temperature sensors 257, 284
Temperatures 276, 322
UPM Cards 322
Voltage sensor 249, 256, 274, 277, 286,
289, 292, 293, 297, 298, 299, 305, 306, 308,
310, 328, 330, 341, 344, 345, 346, 347, 348,
349, 350, 360, 363
Voltage sensors 257, 284
Diagnosis
Datacenter Electrical Issues 91
Disable
Localhost Monitoring 128
Missing Device Detection 140
Discovery
Customize 132
Cycle 132
Interval 130
Process 58
Trigger 128
Disk 63, 65, 235, 236, 237, 238, 244, 248,
251, 255, 261, 264, 267, 278, 291, 292, 293,
294, 295, 297, 298, 316, 317, 318, 320, 331,
334, 335, 337, 344, 355, 356, 357, 361, 362
Controller 194
Disk controllers 184
Logical 54, 63, 64, 184, 194, 196
Monitoring 63, 64, 65
Physical 54, 63, 64, 65, 184, 194, 209, 212,
348, 364
Disks
Controller 81
Logical 81
Monitoring 81
Physical 81
DPT 237
Duplex
Full 166
Half 166
DuplexMode 266
- E -
ECOM 251
Edit
Alert Actions 150
Electricity
Consumption 92
Send 150
EMC
EMC Clariion 9
EMC SMI-S Provider (ECOM) 9
EMC Symmetrix 9
EMC Symmetrix V-Max 9
EMC SMI-S Agent 251
Emulex
Emulex HBA 9
Emulex HBAs 253
Enable
Debug Mode 130, 131
Enclosure.Discovery 58
Environment 13 lom 350
Monitoring 66, 72 prtdiag 350
Virtualized 72
Errors 68, 69
382
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Errors 68, 69
Detected 65
ErrorCount 201
ErrorStatus 201
Parameters 201
PredictedFailure 201
Status 201
Event
PATROL event 150
Trigger 150
EVENT_MANAGEMENT.kml 31
EventManager
Mechanism 147
Threshold 147
External Device
Monitoring 70
External disk array
Monitoring 77
Extracting the setup files 15
- F -
Failure
Hardware 95
Instrumentation 96
Fan
Detect 68
Monitoring 68
PATROL 58, 59, 68
Processor 68
Rotations/minute 68
Speed 68
SpeedPercent 68
Status 68
Temperature 68
FanColl 59
Fibre Alliance SNMP Agent (Switches) 254
Files
.hdf 57
Extracting 15
Ins_ALL_7520.tar 16 ins_ALL_7551.tar 16
Ins_WINDOWS_7520.exe 15, 16 ins_WINDOWS_7551.exe 15, 16
Mshw_ntx86_1300.exe 14, 15
Mshw_unix_1300.tar 14 mshw_unix_1400.tar 14 mshw_WINDOWS_1301.exe 15 mshw_WINDOWS_1400.exe 14
Perl.exe 17
Setup 15
Setup.exe 17
Setup.sh 17
Force
Localhost Monitoring 111
Fujitsu
BX Blade Servers 255
FSC BX Blade Servers 255
Fujitsu Eternus 9
Fujitsu-Siemens 255
Fujitsu-Siemens Blade 255
Fujitsu-Siemens BX Blade Chassis 9
Fujitsu-Siemens PRIMERGY 9, 316, 319,
320
Fujitsu-Siemens Serverview 9, 256
Fujitsu-Siemens ServerView RAID Agent
255
Fusion ioDrive (fio-status) 257
- G -
Generate
Baselines 52
- H -
Hardware 13, 14, 16, 31, 58, 59, 61, 68
Failure 95
Hardware agents 61
Hardware Sentry 13, 31, 54, 58, 59
Installation 13, 14, 16, 17
Uninstall 33
HBA 365 hbacmd 253
HDF
Display Name 58, 59
Heating
Issues 87
Hitachi
Hitachi AMS 9
Hitachi BladeSymphony 9
Hitachi BladeSymphony Chassis 258
Hitachi BladeSymphony Chassis Management
Module 258
Hitachi Device Manager 9
Hitachi USP-V 9
383
Hardware Sentry KM for PATROL
Version 1.8.01
Index
HP 284, 286
HP 9000 9, 273, 279, 280, 281, 282
HP AlphaServer 9
HP BladeSystem 259
HP BladeSystem - Telnet/SSH 260
HP BladeSystem Onboard Administrator
260
HP c-Class BladeSystem 9
HP CommandView EVA 9
HP CommandView XP (or Hitachi Device
Manager) 9
HP EVA Storage Systems 276
HP Insight Management Agent 9
HP Insight Management Agent - HBA 263
HP Insight Management Agent - Network
266
HP Insight Management Agent - Server - WMI
272
HP Insight Management Agent (v8.20 or lower) - Memory 266
HP Insight Management Agent (v8.25 or higher) - Memory 265
HP Insight Management Agent–Drive Array
261
HP Insight Management Agent–Fiber Array
262
HP Insight Management Agent–IDE Storage
264
HP Insight Management Agent–iLO 265
HP Insight Management Agents 262, 263,
264, 265, 266, 267, 268, 269, 272
HP Insight Management Agent–SCSI Storage
267
HP Insight Management Agent–Server 268
HP Insight Management Agent–Server (Alpha)
269
HP Integrity 9, 279, 280, 281, 282
HP MP/GSP card (iLO) 273
HP MSA 2000 & P2000 274
HP MSA Management Card 274
HP NetServer 9, 277, 278
HP OpenVMS 263, 264, 265, 266, 267, 268,
269
HP p-Class BladeSystem 9
HP ProLiant 9, 261, 262, 263, 265, 266,
267, 268, 269, 272
HP StorageWorks EVA 9
HP StorageWorks MSA P2000 274
HP StorageWorks XP 9
HP SuperDome 279, 280, 281, 282
HP SuperDome (Itanium) 9
HP SuperDome (PA-RISC) 9
HP TopTools Agent 277
HP TopTools NetRaid Agent 278
HP Tru64 263, 264, 265, 266, 267, 268,
269
HP-UX 280, 281, 282, 283
HP-UX - Network 281
HP-UX - SASMGR Managed Disks 281
HP-UX - Smart Array RAID 282
HP-UX Smart Array Configuration Utility
282
HP-UX Support Tools Manager (STM) 283
HP-UX system commands 281
HP-UX–Disks 280
HP-UX-STM 283
- I -
IBM
IBM 3584 Tape Library 9
IBM AIX 287, 289, 290, 291, 307
IBM AIX - HBA 290
IBM AIX system commands 287, 288, 289,
290, 291, 307
IBM AIX–CHRP Environment 287
IBM AIX–Common 288
IBM AIX–Environment (ue sensor) 289
IBM AIX–SCSI disks 291
IBM BladeCenter 9, 286
IBM BladeCenter Management Module 286
IBM Director Agent 9
IBM Director Agent 3.x 292
IBM Director Agent 3.x–Windows 292
IBM Director Agent 4.x 293, 294
IBM Director Agent 4.x–Linux 293, 294
IBM Director Agent 5.10.x 295, 297
IBM Director Agent 5.10.x–Linux 295
IBM Director Agent 5.10.x–Windows 297
IBM Director Agent 5.20.x / 6.10.x 336, 337
IBM Director Agent 5.20.x–Linux 298
IBM Director Agent 5.20.x–ServeRAID - Linux
299
IBM Director Agent 5.20.x–ServeRAID -
Windows 300
IBM Director Agent 5.20.x–Windows 299
IBM Director Agent 6 302
IBM Director Agent 6 - Linux 301
IBM Director Agent 6 - Windows 302
384
Hardware Sentry KM for PATROL
Version 1.8.01
IBM
IBM Director Agent 6.1.x 301
IBM DS (LSI) Disk Arrays (smcli) 303
IBM DS 3000, 4000, 5000 Series 9
IBM DS 6000, 8000 Series 9
IBM DS Storage Manager (SMcli) 9
IBM eServer p5 287, 288, 289, 290, 291,
307
IBM Netfinity 292, 293, 294, 295, 297, 299,
300, 301, 302, 336, 337
IBM Netfinity Manager 5.20.x–Basic 305
IBM Netfinity Manager 5.20.x–Disks 305
IBM Netfinity Manager 5.20.x–Normal 306
IBM pSeries 287, 288, 289, 290, 291, 307
IBM pSeries, IBM eServer p5, p6 9
IBM RS/6000 287, 288, 289, 290, 291, 307
IBM Storwize V7000 9
IBM Storwize V7000 CIM Agent 9
IBM SVC 9
IBM SVC CIM Agent 9
IBM VIO Server 9, 307
IBM XiV 9
IBM XIV Storage System SMI-S Agent 9
IBM XIV Storage System SMI-S AgentIBM
Storwize V7000 CIM Agent 9
IBM xSeries 292, 293, 294, 295, 297, 299,
300, 301, 302, 336, 337
IBM xSeries, IBM Netfinity 9
Improvement 5
InfoBox
Acknowledge Linkstatus Alert 204
Array Name 197
Battery Information 171
BIOS Version 184, 186, 187
Chemistry 171
Commands 204
Connector Date 171, 176, 179, 181, 184,
186, 187, 189, 192, 194, 209, 213, 216, 219,
222, 225
Connector Description 176
Connector Display Name 171, 176, 179,
181, 184, 186, 187, 189, 192, 194, 201, 204,
207, 209, 213, 216, 219, 222, 225
Connector File Name 171, 179, 181, 184,
186, 187, 189, 192, 194, 201, 204, 207, 209,
213, 216, 219, 222, 225
Connector File Name@r by <remote hostname"e name followed byt 176
Connector File Path 176
Index
385
Connector ID 171, 176, 179, 181, 184, 186,
187, 189, 192, 194, 209, 213, 216, 219, 222,
225
Connector Information 171, 179, 181, 184,
186, 187, 189, 192, 194, 209, 213, 216, 219,
222, 225
Connector Version 171, 176, 179, 181,
184, 186, 187, 189, 192, 194, 209, 213, 216,
219, 222, 225
Copyright 199
CPU Core Information 181
CPU Information 179
Device ID 171, 179, 181, 184, 186, 187,
189, 192, 194, 209, 213, 216, 219, 222, 225
Disk Controller Information 184
Driver Version 184
Enclosure Information 186, 187
Ethernet/Fiber Port Traffic Report 204
Fan Information 189
Firmware Version 184
ID 199, 201, 204, 207
Identifying Information 216
Instant Hardware Health Report 204
LED Information 192
Local Device Name 197
Location 189, 222
Logical Disk Information 194
Manufacturer 171, 179, 184, 186, 187,
194, 209, 216, 219
Model 171, 179, 184, 186, 187, 216, 219
Name 192
PATROL ID 171, 176, 179, 181, 184, 186,
187, 189, 192, 194, 209, 213, 216, 219, 222,
225
Pause Monitoring 204
Physical Disk Information 209
Power 213
Power Supply Information 213
Product 199
RAID Type 194
Refresh Parameters 204
Release Date 199
Remote Device Name 197
Remove 204
Resume Monitoring 204
Robotics Information 216
Serial Number 186, 187, 209, 216, 219
Size 194, 209
Support 199
Tape Drive Information 219
Hardware Sentry KM for PATROL
Version 1.8.01
Index
InfoBox
Temperature Sensor Information 222
Type 171, 186, 187, 213, 216, 225
Version 199
Voltage Information 225
Web Site 199
WWN 197
Install / Un-install 9, 31
Hardware Sentry 13, 14, 16, 17, 33
Migration 13
Packages 14, 15
Setup files 15
Instrumentation
Failure 96
Integration 39
BMC Portal 38
BMC ProactiveNet Performance Management
38
Integration Service Agent 41
Intel
Intel Base Board 5 308
Intel Modular Server 309
Intel Server Manager 8 SNMP Agents 308,
309
Internal
Messages 168
Problems 168
Internal Message Notification 168
Interval
Discovery 130
Polling 130
Inventory
Schedule Hardware 99
IPMI 361
IPMI–In-band(IpmiTool) 310 ipmitool 310
Issues
Cooling 87
Fixed 5
Heating 87
Performance 166
- J -
Java settings 133
- K -
Key Performance Indicator 170
Key Performance Indicators
BMC ProactiveNet Performance Management
52
Manage 52
KM 31
Commands 130
Commands for managed systems 113
Commands for monitored devices 144 comma-separated list 31
Reinitialize 111
Settings 130
KM Issues
Notification 168
KPI 170
BMC ProactiveNet Performance Management
52
Manage 52
- L -
LEDs
Misconfigured 69
Monitoring 69
Overheating 69
Turned off/on 69
Unplugged 69
License 17
Linux
Linux - Emulex HBAs (hbacmd) 312
Linux - Multipath 314
Linux - QLogic HBAs (scli) 315
Linux–Network 313
Listening
50001 17
Localhost
Monitoring 128
Localhost Monitoring
Force 111
Logical 58
LSI
LSI 1030-based GAM Server 316
LSI 1030-based GAM Server (Alternate MIB)
316
LSI GAM Server 316
386
Hardware Sentry KM for PATROL
Version 1.8.01
Index
LSI
LSI Logic - LsiUtil - RAID (Windows) 317,
318
LSI Logic MegaRAID PowerConsole 319
LSI MegaCli 321
LSI MegaRAID PowerConsole 319
LSI MegaRAID SAS SNMP Agent 319, 320
LSI RAID controller 317, 318
LsiLogic MegaRAID SAS 319
LsiLogic MegaRAID SAS (Newer Controllers)
320
LUN 197, 198
- M -
Macro Variables
%{/variable_name} 161
%{ALARM_TYPE} 161
%{ASCTIME:…} 161
%{CONSEQUENCE} 161
%{DATE} 161
%{FULLREPORT} 161
%{HOSTNAME} 161
%{NEWLINE}, %{\n} 161
%{OBJECT_CLASS} 161
%{OBJECT_DEVICEID} 161
%{OBJECT_ID} 161
%{OBJECT_LABEL} 161
%{OBJECT_TYPE} 161
%{PARAMETER_NAME} 161
%{PARENT_CLASS} 161
%{PARENT_DEVICEID} 161
%{PARENT_ID} 161
%{PARENT_LABEL} 161
%{PARENT_TYPE} 161
%{PROBLEM} 161
%{RAW_VALUE} 161
%{RECOMMENDED_ACTION} 161
%{TIME} 161
%{VALUE} 161
Macros
Format Symbols 162
Manage
Baselines 52
Key Performance Indicators 52
KPI 52
Managed System 17, 113
McData SAN Switch 9
McData San Switches 322
Mechanism
Event Management 147
Tuning 147
MegaCLI
MegaCli (LSI) managed RAID card 323
MegaCLI Managed Raid Controllers 323
Memory
Memory Module 61
MIB-2 Standard SNMP Agent
MIB-2 Standard SNMP Agent - Network
Interfaces 324
MIB-2 Standard SNMP Agent - Network
Interfaces - Linux 325
MIB-2 Standard SNMP Agent - Network
Interfaces - Solaris 327
MIB-2 Standard SNMP Agent - Network
Interfaces - Windows 326
Microsoft Fibre Channel Information tool 365
Migrating from previous versions of Hardware
Sentry 13
Modify
Alert Threshold 148
Module
Memory Module 61
Monitor Type 41
Monitored devices (KM commands) 144
Monitoring 216, 223, 225
Blade Chassis 70
Datacenter 87
Device 142
Disk 63, 64
Disk Controllers 64, 81
Disks Health 81
Enclosure 54
Environment 66
External Device 70
External disk array 77
Fan 68
Hardware 39, 54
LEDs 69
Localhost 128
Logical Disks 81
Memory modules 61
Pause 171, 173, 174, 175, 176, 178, 179,
181, 183, 184, 186, 187, 189, 191, 192, 193,
194, 196, 197, 198, 199, 201, 203, 204, 206,
207, 208, 209, 212, 213, 214, 216, 219, 221,
222, 223, 225, 226
Pause/Resume 145
387
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Monitoring 216, 223, 225
Physical disk 65
Physical disks 81
Power supplies 91
Power supply 54, 69
Processor 60
Remote System 70
Resume 171, 173, 174, 175, 176, 178, 179,
181, 183, 184, 186, 187, 189, 191, 192, 193,
194, 196, 197, 198, 199, 201, 203, 204, 206,
207, 208, 209, 212, 213, 214, 216, 219, 221,
222, 223, 225, 226
SAN switch 76
Server 75
Software 39
Speed 54
Status 54
Tape Library 78
Temperature 54, 68, 87, 222, 223
Terminate 146
Virtualized environment 72
Voltage 54, 69, 91, 225
Motherboard Monitor 328
MS_HARDWARE_SENTRY1.kml 13, 31
- N -
NEC
NEC ESMPRO Agent 330
NEC Express5800 9
NetApp 9
NetApp Filer - SNMP Agent 329
Network
Card 83
Traffic 83
Network Links
Alert 166
New features 5
Notification 147
Internal KM Issues 168
Internal KM Issues Notification 130
NT_BASE.kml 31
NT_PERFMON_WIZARD.kml 31
- O -
Operating System
HP-UX 286
Linux 322
Microsoft Windows 322, 359
Operating Systems 283, 333
HP OpenVMS 243, 261, 262, 263, 264, 265,
266, 267, 268, 269, 324, 335
HP Tru64 243, 261, 262, 263, 264, 265,
266, 267, 268, 269, 324
HP-UX 9, 279, 280, 281, 282, 284, 324,
335
IBM AIX 287, 288, 289, 290, 291, 307, 335
Linux 9, 14, 15, 16, 235, 236, 237, 238,
243, 248, 249, 251, 253, 255, 256, 257, 259,
261, 262, 263, 264, 265, 266, 267, 268, 270,
278, 293, 295, 298, 299, 301, 308, 310, 312,
313, 314, 315, 316, 319, 320, 323, 325, 330,
331, 335, 336, 360, 361, 362, 363
Microsoft Windows 251, 255, 256, 257,
259, 261, 262, 263, 264, 265, 266, 267, 268,
272, 277, 278, 292, 294, 297, 299, 300, 302,
305, 306, 308, 316, 317, 318, 319, 320, 321,
326, 328, 330, 331, 335, 337, 364, 365, 366
Network 324
OpenVMS 9
Solaris 9
Storage Device 240, 244, 247, 254, 274,
276, 303, 324, 329, 332, 334, 338, 339, 340,
342, 343
SUN 266
Sun Solaris 236, 253, 257, 261, 262, 263,
264, 265, 266, 267, 268, 310, 323, 327, 335,
341, 346, 348, 349, 350, 351, 352, 353, 354,
355, 356, 357, 358
Tru64 9, 335
UNIX 14, 15, 16, 17
VMware ESX4 9
Windows 9, 14, 15, 16, 17, 235, 237, 238,
243, 248, 249
Windows 2003 17
OS command 57
Other 68
- P -
Parameters 170, 361
AvailablePathCount 197, 314, 365
AvailablePathInformation 197, 314
BandwidthUtilization 83, 204
BatteryStatus 64, 81, 184, 236, 251, 255,
262, 321, 323, 331
Blade Information 173
388
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters 170, 361 bladeColl 199
CapacityReport 87
Charge 171, 364
Color 192
Connector 164, 286, 352, 358
Connector Date 173
Connector Display Name 173
Connector File Name 173
Connector ID 173
Connector Information 173
Connector Version 173 connectorColl 199
Controller 284
ControllerStatus 64, 81, 184, 236, 251,
257, 261, 262, 267, 281, 299, 300, 303, 309,
332, 336, 337, 362
CorrectedErrorCount 60, 179 cpuColl 199
CPUCount 175
Credentials 352
CurrentSpeed 270, 272, 284
DegreesBelowWarning 87, 175
Device ID 173
DeviceNotReadyErrorCount 209
Discrete 164 diskControllerColl 199 diskEnclosureColl 199
DuplexMode 83, 166, 204, 240, 307 enclosureColl 199
ErrorCount 61, 65, 194, 209, 216, 219,
238, 240, 247, 253, 254, 255, 256, 262, 266,
270, 279, 281, 283, 288, 290, 291, 307, 309,
312, 313, 319, 320, 322, 324, 325, 326, 327,
342, 351, 354, 355, 357, 358, 365, 366
ErrorPercent 83, 204
ErrorStatus 61
Failure 238 fanColl 199
HardErrorCount 209
IllegalRequestErrorCount 209
InfoBox 173
IntrusionStatus 186, 187, 249, 256, 293,
294, 295, 297, 298, 299
LinkSpeed 166, 204, 238, 240, 241, 253,
254, 266, 270, 274, 276, 281, 307, 309, 312,
315, 322, 324, 325, 326, 327, 365
Index
389
LinkStatus 83, 166, 204, 238, 240, 241,
253, 254, 263, 266, 270, 272, 274, 276, 279,
281, 286, 288, 290, 307, 309, 312, 315, 322,
324, 325, 326, 327, 329, 334, 335, 338, 339,
354, 360, 363, 365, 366 logicalDiskColl 199
LogicalDiskSize 175
MediaErrorCount 209 memoryColl 199
MemorySize 175
Missing 87
Model 173
MountCount 219, 332, 338, 342, 343
Move Count (Cumulative) 216
MoveCount 342
Name 173
NeedsCleaning 219, 332, 338, 340 networkColl 199
NoDeviceErrorCount 209
Numeric 164 otherDeviceColl 199
PATROL ID 173 physicalDiskColl 199
PhysicalDiskSize 175 powerConsumption 92, 175, 187, 240, 241,
258, 260, 341, 360 powerSupplyColl 199
Predicted 61
PredictedFailure 60, 61, 65, 81, 95, 179,
209, 235, 237, 238, 255, 261, 262, 264, 267,
268, 276, 309, 331, 333, 347, 352, 364
ReceivedByteRate 204
ReceivedBytes 322
ReceivedBytesRate 83, 238, 240, 241, 253,
254, 266, 270, 281, 307, 309, 312, 324, 325,
326, 327
ReceivedPacketRate 204
ReceivedPackets 322
ReceivedPacketsRate 83, 238, 240, 241,
253, 254, 266, 270, 281, 307, 312, 324, 325,
326, 327, 365
RecoverableErrorCount 209
Refresh 132, 145
Speed 60, 68, 87, 179, 189, 238, 241, 247,
249, 255, 256, 258, 276, 277, 286, 292, 293,
294, 295, 297, 298, 299, 301, 302, 308, 309,
310, 328, 344, 345, 348, 349, 360, 363
SpeedPercent 68, 87, 189, 260, 286, 349,
360, 363
Statis 237
Hardware Sentry KM for PATROL
Version 1.8.01
Parameters 170, 361
Status 60, 61, 63, 65, 68, 69, 81, 87, 91,
164, 171, 173, 176, 179, 181, 186, 187, 189,
192, 194, 197, 204, 207, 209, 213, 216, 219,
222, 225, 235, 236, 238, 240, 241, 243, 244,
247, 248, 249, 251, 253, 254, 255, 256, 257,
258, 259, 260, 261, 262, 263, 264, 265, 266,
267, 268, 269, 270, 272, 273, 274, 276, 277,
278, 279, 280, 281, 282, 283, 284, 286, 287,
288, 291, 292, 293, 294, 295, 297, 298, 299,
300, 301, 302, 303, 305, 307, 308, 309, 310,
312, 315, 316, 317, 318, 319, 320, 321, 322,
323, 324, 325, 326, 327, 329, 330, 331, 332,
333, 334, 335, 336, 337, 338, 339, 340, 341,
342, 343, 344, 345, 346, 347, 348, 349, 350,
351, 352, 353, 354, 355, 356, 357, 359, 360,
362, 363, 364, 365, 366
StatusInformation 197, 251, 253, 257, 258,
270, 274, 283, 284, 286, 301, 302, 307, 312,
315, 322, 336, 337, 359, 365
Technology 209
Temperature 68, 238, 240, 241, 244, 247,
249, 255, 256, 257, 258, 259, 260, 268, 270,
274, 276, 277, 284, 286, 292, 293, 294, 295,
297, 298, 299, 301, 302, 306, 308, 310, 328,
329, 330, 333, 334, 338, 339, 342, 344, 345,
346, 347, 348, 349, 350, 360, 363
Temperature sensors 259, 294, 295, 301,
302 temperatureColl 199
TestReport 96, 176
TimeLeft 364
TransmittedByteRate 204
TransmittedBytes 322
TransmittedBytesRate 83, 238, 240, 241,
253, 254, 266, 270, 281, 307, 309, 312, 324,
325, 326, 327
TransmittedPacketRate 204
TransmittedPackets 322
TransmittedPacketsRate 83, 238, 240, 241,
253, 254, 266, 270, 281, 307, 312, 324, 325,
326, 327, 365
TransportErrorCount 209
UnallocatedDiskSpace 175
UnallocatedSpace 194, 244, 274, 276
Unmount Count 219 usagecount 207, 342
UsedCapacity 69, 91, 213
UsedTimePercent 181
UsedWatts 260, 268
Voltage 69, 91, 249, 256, 257, 274, 277,
286, 289, 292, 293, 294, 295, 297, 298, 299,
301, 302, 306, 308, 310, 328, 330, 341, 344,
345, 346, 347, 348, 349, 350, 360, 363
Voltage sensors 294, 295, 301, 302 voltageColl 199
ZeroBufferCreditPercent 204
PATROL
Agent 13, 57
Component 9
Hardware 13
PATROL administrator 148
PATROL Agent 17, 31, 70, 85, 114, 147
PATROL Agents 39
PATROL Central 13, 17
PATROL Central – Web Edition 39
PATROL component 14
PATROL Configuration Manager 31, 147
PATROL Console 60, 79, 114, 145, 146
PATROL Console Server 39
PATROL Consoles 13, 63, 65, 147, 150
PATROL Consoles (Classic) 39
PATROL Enterprise Manager 150
PATROL event 148, 150
Pause
Monitoring 145
PCM 31
Performance
Degradation 65
Issues 166
Physical 58
Platform
Fujitsu-Siemens PRIMERGY 322
Windows 359
Platforms 228, 259
Cisco MDS9000 Series FC switches 240
Cisco UCS 241
Data Domain Storage Appliance 244
Dell EqualLogic PS Series Disk Systems 247
Dell M1000E Chassis 245
Dell PowerEdge 246, 249, 251, 313, 314,
333, 364, 365
Disk Array 329, 334
Fujitsu-Siemens BX Blade Servers 255
Fujitsu-Siemens PRIMERGY 235, 237, 238,
255, 256, 313, 314, 316, 319, 320, 331, 333,
364, 365
Generic Servers 308, 309
Index
390
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Platforms 228, 259
Hitachi BladeSymphony Chassis Management
Module 258
HP 9000 273, 279, 280, 281, 282, 283,
284, 286
HP BladeSystem - Telnet/SSH 260
HP EVA Storage Systems 276
HP Integrity 279, 280, 281, 282, 283, 284,
286
HP NetServer 277, 278
HP ProLiant 243, 261, 262, 263, 264, 265,
266, 267, 268, 269, 270, 272, 313, 314, 333,
364, 365
HP StorageWorks MSA P2000 274
HP SuperDome 279, 280, 281, 282, 283,
284, 286
IBM BladeCenter 286
IBM DSxxxx Disk Array 303
IBM eServer p5 287, 288, 289, 290, 291,
307
IBM Netfinity 292, 293, 294, 295, 297, 298,
299, 300, 301, 302, 305, 306, 336, 337
IBM pSeries 287, 288, 289, 290, 291, 307
IBM RS/6000 287, 288, 289, 290, 291, 307
IBM Tape Library 3584 340
IBM xSeries 292, 293, 294, 295, 297, 298,
299, 300, 301, 302, 313, 314, 333, 336, 337,
364, 365
Integrity 273
Linux Server with HBAs 312, 315
NEC Express5800 314, 330, 364, 365
SAN Switches 238, 254, 339
SPARC Enterprise Mx000 341
Storage Libraries 338
StorageTek LSeries 342
StorageTek StreamLine 343
SUN Blade Chassis 345
SUN Blade with ILOM cards 347
Sun Fire 313
Sun Fire (SPARC T1, T2) 353
Sun Fire (SPARC T1/T2) 348
Sun Fire (SPARC) 344, 346, 349, 350, 351,
352, 354, 355, 356, 357, 358
Sun Fire (x64) 236, 310, 314, 333, 364,
365
SuperDome 273
Supported 9
VMware ESX4i 361, 362
VMware ESXi 360, 363
Windows 364
Windows servers 317, 318
Polling
Interval 130
Polling interval
Customize 132
Power Supply
Monitoring 69
Overloaded 69
Preload 31
Previous versions 13
ProactiveNet 40, 41
Process 59
Collection 56, 59
Detection 56, 57
Discovery 56, 58
LogicalDiskColl 59
PhysicalDiskColl 59
Processor
Missing 60
Monitoring 60
Predicted Failure 60
Speed 60
Promise FastTrack 331
Protocol
SNMP 70
SSH 70
Telnet 70
WBEM 70, 114
WMI 70
Provider
WMI 54
PSL 57, 59
PW Commands 50
- Q -
QLogic
QLogic HBA 9
Quantum (ADIC) Based Tape Libraries 332
Quantum Tape Library 9
Query
WBEM 57
- R -
RAID 237, 238, 248, 251
Reference Guide 170
Refresh
391
Hardware Sentry KM for PATROL
Version 1.8.01
Index
Refresh
Parameters 132, 145
Reinitialize
KM 111
Remote System
Monitoring 70
Remove
Threshold 111
Report 249
Energy Usage 106
Ethernet/Fiber port traffic 107
Hardware Health 144
Instant 144
Schedule Hardware Inventory 99
Settings 107
Show 144
Reporting
Data Traffic 85
Electricity Consumption 92
Requirements 9
Reset 65
Alert Actions 111
Automatic ErrorCount 141
KM 111
Threshold 111
Restore
Device Monitoring 142
Paused Objects 111
Resume
Monitoring 145
Paused Objects 111
- S -
S.M.A.R.T 209
SAN Switch
Monitoring 76
Security 17
Security settings 114
Server
Monitoring 75
Servers
Cooling 87
Setup
Files 15
Show
Instant Hardware Health Report 144
Siemens 255
SmartMonTools 333
SMCLI 303
SMI-S
SMI-S Compliant Disk Arrays 334
SMI-S Compliant HBAs 335
SMI-S Compliant RAID Controller - Windows
337
SMI-S Compliant SAN Switches 339
SMI-S Compliant Storage Libraries 338
SNIA
SNIA Compliant Tape Libraries 340
SNMP 54, 235, 237, 238, 244, 248, 249, 251,
254, 255, 256, 258, 259, 261, 262, 263, 264,
265, 266, 267, 268, 269, 278, 286, 305, 306,
308, 309, 316, 319, 320, 322, 324, 325, 326,
327, 329, 330, 331, 332, 340, 342, 343, 345
Community 114
Custom SNMP Trap 150
Queries 114
SNMP Trap 150
Solaris 344, 346, 348, 349, 350, 351, 352,
353, 354, 355, 356, 357, 358
SPARC
SPARC Enterprise Mx000 (XSCF) 341
SSSU 276
Status 59, 292
PowerConsumption 246
Speed 246
Temperature 246
Status parameteres 292
Storage 237, 238
StorageTek
StorageTek LSeries 9
StorageTek LSeries Tape Library 342
StorageTek StreamLine (SL) 9
StorageTek StreamLine Tape Library 343 subfolder 15
Sudo 279
Options 114
Utility 114
SUN
Sun Advanced Lights-Out Management
(ALOM) 9
Sun Advanced Lights–Out Management
(ALOM) card 344
Sun Advanced Lights-Out Management ALOM card 344
SUN Blade Chassis 345
SUN Blade Chassis CMM SNMP Agent 345
Sun Blade Modular Chassis 9
392
Hardware Sentry KM for PATROL
Version 1.8.01
Index
SUN
SUN Blade SP SNMP Agent 347
Sun Explorer 348
Sun Fire (SPARC T1, T2) – 2009 and newer firmware 9
Sun Fire (SPARC T1, T2) – pre-2009 firmware 9
Sun Fire (SPARC T1/T2) 348
Sun Fire (SPARC) 9, 344
Sun Fire (X64) 9
Sun Fire F12K, F15K, F20K, F25K 9
Sun Fire F12K/F15K/F20K/F25K SMS 346
Sun Fire Mx000 9
SUN ILOM (SNMP) 347
Sun Solaris 344, 346, 348, 349, 350, 351,
352, 353, 354, 355, 356, 357, 358
Sun Solaris - Disks 357
Sun Solaris - Environment prtpicl 349
Sun Solaris - Fault Manager (Memory) 351
Sun Solaris - Network 354
Sun Solaris - Non-Sun Disks 355
Sun Solaris - Processors psrinfo 356
Support 292
Symbols
Format Symbols 162
Macros 162
System
Locate a Device 79
System commands 253
- T -
Tape Library
Monitoring 78
Task
Administrative 110
Technology
Command lines 9
HTTP 9
IPMI 9
SMART 65
SNMP 9
SSH 9
Telnet 9
WBEM 9
WMI 9
XML API 9
Telnet/SSH 240, 245, 246, 260, 273, 274, 344
Temperature 58, 272, 292
Celsius 68
Computing Issues 87
Data Center 87
Monitoring 68, 222, 223
Overheating 68
Terminate
Monitoring 146
Thorium 14
Threshold 66, 147, 164
ALL_INSTANCES 148
ANYINST 148
Mecanism Selection 147
Mechanism 130
Mode 148
Modify 148
Remove 111
Reset 111
Thresholds
Customize 50
Import 50
Traffic
Demand 83
Network 83
Spike 83
Transmission
Packets 83
Trigger 68
Discovery 128
Troubleshooting 131
Bottleneck 83
Connection 83
Tuning
Mechanism 147
Threshold 147
- U -
Unix
Console Mode 143
UNIX/Linux 31
Unknown Status Management 169
Use 69
Utility
BMC Software FTP site 16
BMC Software Installation Utility 16
Emulex's hbacmd 312
Linux multipath 314
393
Hardware Sentry KM for PATROL
Version 1.8.01
Utility
QLogic's SCLI 315
Sudo 70, 114, 314, 350, 351, 352, 354,
355, 356, 357, 358
- V -
Variables
Configuration 367, 373 disableMissing Devoice Detection 111
Global 367
Host-Specific 373 intrusion DetectionAlert 111 parametersMaxOCC 111 pemMessages 111 thresholdsFactorization 111 unexpectedStatusManagement 111
VMware
VMware ESX4 9
VMware ESX4i 361, 362
VMware ESXi 9
VMware ESXi 3.x 360
VMware ESXi 4.x 363
Voltage
Fluctuations 91
MilliVolts 69
Monitoring 69, 91, 225
- W -
WBEM 54, 251, 270, 292, 293, 295, 298, 299,
301, 334, 335, 336, 338, 339, 360, 361, 362, 363
Web 13, 14, 17, 238
Web Edition 13, 17
What's new 5
Windows 292
WMI 272, 277, 292, 294, 297, 299, 300, 302,
337, 364, 365
Dell PowerEdge 366
Fujitsu-Siemens PRIMERGY 366
HP ProLiant 366
IBM xSeries 366
NEC Express5800 366
Platforms 366
Sun Fire (x64) 366
WPCONFIG.EXE 31
- X -
Xpconfig 31
394
Index
About BMC® Software
BMC Software, Inc. NYSE:BMC, is a leading provider of enterprise management solutions that empower companies to manage their IT infrastructure from a business perspective. Delivering Business Service Management, BMC Software solutions span enterprise systems, applications, databases, and service management. Founded in 1980, BMC Software has offices worldwide and fiscal
2004 revenues of more than $1.4 billion. For more information about BMC
Software, visit www.bmc.com
.
About Sentry Software™
Sentry Software, a strategic Technology Alliance Partner of BMC Software, provides key monitoring solutions specifically designed to expand the capabilities of BMC Performance Manager, thus enabling up to 100% coverage of any infrastructure. Sentry Software specializes in single solutions for multiplatform monitoring of hardware, custom applications or any IT component, and blackout windows. Sentry Software products are deployed in 45 countries across the globe and lead the list of BMC Software’s third-party product sales.
For more information about Sentry Software, please visit www.sentrysoftware.net
.
Lataa
Mainos