Map Your Own IT Ecosystem
See how Zenoss fits into your IT ecosystem.
Start MAPPING NOW
Huntington Success Story
Learn how Huntington consolidated from 37 tools to a single monitoring solution.
Customer Support Portal
Zenoss Learning Center
Zenoss & Cisco: Changing IT with service assurance for hybrid data centers.
Zenoss Partner Portal
Become a Partner
BBC Success Story
The BBC chose Zenoss for three key reasons: scalability, flexibility and value for money.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
This ZenPack provides support for monitoring HP Proliant Servers (G6,G7 and G8), including blade servers with the HP Proliant c7000 Enclosure. Monitoring is performed using the SNMP API interface. This ZenPack currently supports HP Proliant servers running on Windows OS or Linux OS or VMWare ESXi.
snmpwalk -v2c -c [community] [hostname]
The features added by this ZenPack are summarized as follows. They are each detailed further below.
The following components will be automatically discovered through the Onboard Administrator (OA) IP address and the host name you provide. The properties and relationships will be continually maintained
The following components will be automatically discovered through the Server IP address and the host name you provide. The properties and relationships will be continually maintained.
The following additional components apply only to Rack and Tower servers.
According to the following Component states this ZenPack will trigger clear , error or warning events with an appropriate summary message.
The HP Proliant ZenPack uses several methods to collect both model and performance data depending on the device types, which fall into 3 categories:
The following metrics will be collected every 5 minutes by default. Any other HP Proliant Server metrics can also be collected by adding them to the appropriate monitoring template.
The following event classes and their subclasses will be continually collected and passed into the Zenoss event management system.
Various information encoded in these event classes will be used to automatically determine as best as possible the following Zenoss event fields.
Installing this ZenPack will add the following items to your Zenoss system.
The following plugins will be used for modeling OnBoard Administrator and Blade using the respective OA and Blade IP Addresses via SNMP interface.
The following plugins will be used for modeling Blade/Rack details using the WBEM via request and response.
The following plugins will be used for modeling an ilo.
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.
Most of the impacts described above follow the default policy of a node being in the worst state of the nodes that impact it. For example, an Enclosure failure will imply that all related hosts are also failed.
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 Windows HP Proliant device using the Zenoss web interface.
Use the following steps to start monitoring VMware ESXi device using the Zenoss web interface.
Use the following steps for successful modeling.
Use the following steps to monitor a Windows Device using the ZenPacks.zenoss.Microsoft.Windows zenpack. Adding a device in this class will use SNMP and WinRM to gather modeling and monitoring data.
'/Devices/Server/Server/HP/OnboardAdministrator' <device name> setManageIp="<IP Address>"
'/Devices/Server/HP/Proliant' <device name> setManageIp="<IP Address>"
'/Devices/Server/HP/ILO' <device name> setManageIp="<IP Address>"
'/Devices/Server/VMware/ESXi/HP' <device name> setManageIp="<IP Address>", zWBEMUsername='<username>', zWBEMPassword='<password>', zWBEMPort=5989, zWBEMUseSSL='true'
Example : /Server/HP/OnboardAdministrator CMC_1 setManageIp='10.100.10.30'
Example : /Server/HP/ILO ILO setManageIp='10.100.10.31'
Example : /Server/HP/Proliant Linux-Blade setManageIp='10.100.10.32'
* Note you can add the proliant components to any device as long as they are modeled with the HP.snmp.HPSNMPModeler plugin.
Example : /Server/VMware/ESXi/HP vmware_1 setManageIp='10.100.10.35', zWBEMUsername='root', zWBEMPassword='password', zWBEMPort=5989, zWBEMUseSSL='true'
You can then load the Devices using zenbatchload with the following command.
When adding a window Blade server to Windows/HP Organizer in HP Proliant Zenpack,an event : "zeneventlog /Status/WMI event Could not read the Windows event log (NT_STATUS_ACCESS_DENIED). Check your user/password settings and verify network connectivity" is generated . The Temperature Sensor Component in Onboard Administrator shows 0 C for Interconnect Tray Row.
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-184.108.40.206-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.
$ sudo su - zenoss
$ zenpack --install ZenPacks.zenoss.HP.Proliant-*.egg
$ zenoss restart
View the discussion thread.
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.