This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.
Monitoring HP Proliant G6/G7/G8/G9/G10 rack/blade servers and enclosures.
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
Compatible with Zenoss Core 4.2.x, Zenoss Core 5.0.x, Zenoss Core 5.1.x, Zenoss Core 5.2.x, Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x, Zenoss Resource Manager 5.1.x, Zenoss Resource Manager 5.2.x
This ZenPack provides support for monitoring HP Proliant Servers (G6, G7, G8, G9, and G10), including blade servers with the HP Proliant c7000 Enclosure. Discovery and monitoring are performed using SNMP, iLO (XML/HTTP), and/or WBEM protocols depending on environment.
This ZenPack currently supports HP Proliant servers running Windows or Linux (with installed/configured HP SIM SNMP subagent), HP Enclosures (via SNMP) as well as iLO devices (via either iLO or SNMP) and VMWare ESXi (using HP custom ESXi with WBEM/CIM access configured).
It is important to note that not all features of this ZenPack are supported across all protocols, since each of them provides a part, but not all, of the total information used by the ZenPack. This limitation is based on the amount and quality information that is available from each of the supported protocol. What this means is that certain metrics for a given component type (such as a temperature sensor) may or may not be available depending on the type of device that is monitored and/or on the protocol used to collect that data.
This ZenPack relies on several protocols to achieve coverage of various aspects of the HP Proliant architecture. At the most basic level, SNMP should be configured so as to facilitate access to HP/Compaq MIBs (CPQSINFO-MIB, CPQRACK-MIB, etc) and the associated OIDs. Support on a bare metal install of Linux or Windows OS, for example, requires installation of HP SIM and its associated software components, including a SNMP subagent and associated configuration for its use with the OS SNMP agent. Configuration of these software components is covered by various documentation available from HP and is beyond the scope of this document.
SNMP is also supported natively by HP OnboardAdministrator (if available) and optionally by the iLO management interface.
As noted above, iLO management interface can be monitored (as a Zenoss device) via iLO protocol (essentially XML via HTTP) or SNMP (which can be enabled in the iLO GUI interface).
An additional important item to note is that the iLO management interface GUI requires that the associated server's FQDN and IP address be set manually.This ZenPack requires the configuration of FQDN(or hostname)/IP be set in order for Zenoss to create associations on its side between monitored Proliant servers and their associated iLO device in Zenoss.
Support for HP Proliant hardware running VMWare ESXi OS relies on a custom ESXi image available from HP. This custom image provides support for Proliant-specific monitoring and performance data that is not avaiable using the version of ESXi provided by VMWare. Additionally, WBEM support must be configured and enabled on the ESXi host.
The following components will be automatically discovered using either the SNMP, iLO, or WBEM related connection parameters you provide. The properties and relationships will be continually updated on Zenoss' normal remodeling interval which defaults to every 12 hours.
Relationships: Cooling Fan, Device Bay, Interconnect Bay, Onboard Administrator, Power Supply, Temp Sensor, HPTemperatureSensors, HPThermalSubsystem
Relationships: Processor, Cooling Fan, Logical Drive, Management Controller, Memory Slot, Network Interface, NIC, HPOSHypervisor, PCI Device, Physical Drive, Power Supply, System Board, Temp Sensor, RAID Controller, FC Adapter, FC Port
Relationships: Chassis, FC Port
Relationships: Chassis, FC Adapter
Relationships: Chassis, Logical Drive, Physical Drive
Relationships: Chassis, RAID Controller
The following metrics will be collected every 5 minutes by default. The average statistic is collected, and the graphed value is per second for anything that resembles a rate.
Metrics (WBEM): FramesTooLong, EncodingDisparityErrors, RXBroadcastFrames, ErrorFrames, MulticastFramesTransmitted, LossOfSyncCounter, LinkFailures, LinkResetsReceived, BytesReceived, DumpedFrames, FramesTooShort, CRCErrors, PacketsReceived, PacketsTransmitted, LossOfSignalCounter, TXBroadcastFrames, DelimiterErrors, LinkResetsTransmitted, PrimitiveSeqProtocolErrCount, BytesTransmitted, AddressErrors, MulticastFramesReceived
Metrics (WBEM): status
Metrics (WBEM): status, speed
Metrics (SNMP): status, cpqRackServerBladeWattageAvg, cpqRackServerBladePOSTStatus, cpqRackServerBladePowered, condition
Metrics (SNMP): status
Metrics (WBEM): cpqDaAccelBattery, CacheReadPercent, cpqDaAccelStatus, CacheParityReadErrors, CacheModuleTemperature, ControllerTemperature, CacheParityWriteErrors, cpqDaCntlrCondition, CacheWritePercent
Metrics (WBEM): status, BytesReceived, PacketsReceived, PacketsTransmitted, InternalMACReceiveErrors, InternalMACTransmitErrors, BytesTransmitted
Metrics (ILO): status
Metrics (WBEM): MediaFailures, ReadOperations, HardwareErrors, SectorsWritten, SectorsRead, OtherTimeOuts, BadTargetErrors, WriteOperations, status, NotReadyErrors, HardReadErrors, DRQTimeOuts, FormatErrors, HardWriteErrors
Metrics (SNMP): status, currentPowerSupply, condition
Metrics (SNMP): hoursInService
Metrics (WBEM): status, currentReading
Metrics (SNMP): status, currentReading
Event managment is handled both actively and passively. Passively, this takes the form of SNMP traps, translations and correlations for which 516 notifications defined in the various HP/Compaq MIBs are included in the form of Event class instances with transforms.
Active Event managment revolves around the tracking of the numeric state indicators defined variously according to SNMP, ILO, or WBEM and mapped to corresponding Zenoss event severities.
Critical Event (esx): status is Major Failure or Critical Failure or Non-recoverable Error
Critical Event (snmp): status is Failed
Critical Event (esx): speed is Major Failure
Critical Event (snmp): cpqFcaHostCntlrStatus is Failed
Critical Event (snmp): cpqDaCntlrPartnerBoardStatus is Failed
Critical Event (snmp): condition is Failed
Critical Event (snmp): cpqSm2CntlrBatteryStatus is Failed
Error Event (snmp): status is Degraded
Clear Event (esx): status is OK or Degraded or MajorFailure
Critical Event (esx): status is Critical Failure
Critical Event (snmp): condition is General Failure or Bist Failure or Fan Failure or Temp Failure or Inter Lock Open or Eprom Failed or Vref Failed or Dac Failed or Ram Test Failed or Voltage Channel Failed or Orring Diode Failed or Brown Out or Give Up On Startup or Nvram Invalid or Calibration Table Invalid
Critical Event (esx): status is Predictive Failure or Error
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for services running on HP Proliant. The service impact relationships shown in the diagram and described below are automatically added. These will be included in any services that contain one or more of the explicitly mentioned components.
The HP Proliant ZenPack uses several methods to collect both model and performance data depending on the device types, which fall into 3 categories:
Onboard Administrator is HP's solution for hardware management and monitoring. It provides a SNMP interface that Zenoss uses to monitor both HP chassis and blade hardware as well as certain OS components with the OA agent installed and configured. SNMP access can also be configured for use with the iLO management interface (via the managment GUI) or with a bare metal install of Linux or Windows by installing HP SIM and related software (including its SNMP subagent)
Data from ILO devices is provided by a HTTPS interface listening on port 443. The zILOUserName, zILOPassword, zILOUseSSL, and zILOPort zProperties control access to ILO devices. The ILO interface accepts and returns XML-formatted query strings, and this ZenPack features a custom api definining these queries and their output formatting.
WBEM support is required for montitoring ESXi on HP Proliant hardware. The zWBEMUsername, zWBEMPassword, zWBEMPort, and zWBEMUseSSL zProperties control access to HP ESXi devices. Data collection relies on the WBEM ZenPack, and also uses a HTTP-based protocol (WBEM). HP provides custom-built ESXi ISOs that provide the HP WBEM software to the base ESXi image.
Endpoint configuration is beyond the scope of this document, but online resources are available at http://h10032.www1.hp.com/ctg/Manual/c04341228
Use the following steps to start monitoring the Onboard Administrator using the Zenoss web interface.
Use the following steps to start monitoring Linux HP Proliant device using the Zenoss web interface.
Use the following steps to start monitoring a HP ILO device using the Zenoss web interface.
Several scripts are included for use with troubleshooting or sample data collection. These scripts reside in the
Installing this ZenPack will add the following items to your Zenoss system.
/Server/HP/Proliant: SNMP monitoring with HP MIBs
SNMP Datasource (SNMP)
FC Port (HPFibreChannelPort)
The HP Proliant Zenpack can be upgraded. To upgrade the ZenPack, install the latest version over the existing one. There is no action for the user to migrate the data. The performance data and events of old ZenPack are retained as per the retain policy settings.
In order to fully support monitoring a system with multiple onboard administrators the "enclosure ip mode" option must be enabled and the enclosure must be given a static ip address that is shared between the two onboard administrators. Failure to do so may cause monitoring to stop when the active onboard administrator goes offline.
When upgrading from 1.0 to 3.0 you may see an issue related to catalogs. If you installed the zenpack from the ui the ui may complain that the zenpack install failed. Install the zenpack from the command line as a workaround. The observe messages similar to "WARNING zen.catalogservice: Detected catalog inconsistency - to repair, run: 'python /opt/zenoss/ZenPacks/ZenPacks.zenoss.CatalogService-126.96.36.199-py2.7.egg/ZenPacks/zenoss/CatalogService/sync_rids.py'" to finish the installation of this zenpack run the script as it suggests. then restart the zenoss instances.
Ilo device modelling reuses the original snmp components of this zenpack. Because the ilo does not return exactly the same results as is available via snmp monitoring, there will be cases where some fields are always set to N/A or Unknown. This is a known issue and is not currently considered a defect.
The servername variable needs to be set inside the ILO for this zenpack to work properly with ILO hardware. - For the ILO 4, please go into the ILO GUI under Administration -> Access Settings -> Under Access Options there is "Server Name" and update the name for the ILO server.
Since this ZenPack depends on the PythonCollector ZenPack for some of its capabilities, the zenpython collector daemon should be stopped manually prior to uninstallation of this ZenPack in order to avoid a traceback error. The zenpython daemon can be restared again once uninstallation is complete.
Update Physical Disk possible status values (ZPS-2946)
Tested with Zenoss 5.3.3, Zenoss 6.2.0, and Zenoss Cloud
Updated unit tests for build platform compatability (ZPS-29150, ZEN-28507)
Fix various ILO modeling issues (ZPS-)
Updated list of recognized XML status strings
Ensure all SNMP templates available to /Devices/Server/HP/ILO/SMNP
Improved handling of components with blank id (ZEN-22872, ZEN-22851, ZEN-21680)
Updated zenpacklib.py to address modeler timeouts from attribute-indexed components
Numerous enhancements and bugfixes
Fixes ZEN-18151. HP.wbem.HPWBEMPlugin modeling traceback on tempStatus()
Re-based SNMP Device templates on /Server/Linux to ensure consistency
Major rewrite of significant sections of the zenpack to use zenpacklib and remove obvious defects.