Revision as of 17:19, 8 September 2015

HP Proliant (Commercial) ZenPack

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Releases

Version 3.0.1- Download

Summary of changes: Fixes issue with ESX modeler plugin

Released on 2015/06/10

Requires PythonCollector ZenPack,WBEM ZenPack

Compatible with Zenoss Resource Manager 4.2.x

Version 3.0.0- Download

Released on 2014/10/10

Requires PythonCollector ZenPack,WBEM ZenPack

Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x

Version 1.0.0- Download

Released on 2014/03/07

Requires PythonCollector ZenPack,WBEM ZenPack

Compatible with Zenoss Resource Manager 4.2.x

Background

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.

Gallery

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• Blade Proliant Server.png
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

Prerequisites

Zenoss Version

>=4.2.3

External Dependencies

HP SNMP Agent should be running on Linux/Windows devices. Intergraded Lights Outs Agent should be configured on Proliant Servers.

This should be verified using snmpwalk from your ZenOSS server:

snmpwalk -v2c -c [community] [hostname]

Features

The features added by this ZenPack be summarized as follows. They are each detailed further below.

• Initial discovery and continual synchronization of relevant components.

• Performance monitoring.

• Event management.

• Service impact and root cause analysis. (Requires Zenoss Service Dynamics)

Discovery

HP C7000 Enclosure

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

Power Subsystem

Attributes: Name, Enclosure Name, Present Output, Output Capacity, Input Status, Status

Relationships: Enclosure

Device Bays

Attributes: Name, Server Name, Enclosure Name, Product Name, Part Number, Serial Number, Status

Relationships: Enclosure

Temperature Sensors

Attributes: Name, Enclosure Name, Location, Current Reading, Caution Trap, Condition

Relationships: Enclosure

Thermal Subsystem

Attributes: Name, Enclosure Name, Part Number, Spare Part Number, Status

Relationships: Enclosure

Interconnect Bays

Attributes: Name, Enclosure Name, Product Name, Serial Number, Status

Relationships: Enclosure

Enclosure

Attributes: Name, Model, Serial Number, UUID, Part Number, Firmware Version, Condition

Relationships: Power Subsystem, Device Bays, Temperature Sensors, Thermal Subsystem, Interconnect Bays, Onboard Administrator

Onboard Administrator

Attributes: Name, Enclosure Name, Bay Number, Serial Number, Role, Presence, Condition

Relationships: Enclosure

HP Proliant Servers (G6, G7 and G8)

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.

Physical Drives

Attributes: Name, Server Name, Model, Drive Type, Firmware Version, Capacity, Rotation Speed, Status

Relationships: Proliant Server

PCI Devices

Attributes: Name, Server Name, PCI Bus, Device Number, Slot Type, Slot Width, Board Name

Relationships: Proliant Server

Temperature Sensors

Attributes: Name, Server Name, Location, Current Reading, Threshold, Status

Relationships: Proliant Server

Logical Drives

Attributes: Name, Server Name, Capacity, Reads, Writes, Sectors Read, Sectors Written, Status

Relationships: Proliant Server

Management Processor

Attributes: Name, Server Name, Serial Number, Firmware Version, Active License Type, Interface Status

Relationships: Proliant Server

Memory

Attributes: Name (Location), Server Name, Module Status, Type, Size, Frequency, Technology, Condition

Relationships: Proliant Server

System Board

Attributes: Product Name, Server Name, Rom Version, Hours In Service, TPM Module, Size, Maximum Size, Policy, Status

Relationships: Proliant Server

Proliant Server

Attributes: Server Name, Serial Number, Product Name, Product Id, Host OS, Host OS Detail

Relationships: System Board, Management Processor, Processors, PCI Devices, Memory, Cooling Fans, Network Interface Controller, Physical Drives, Temperature Sensors, Power Supplies, Logical Drives, OS/Hypervisors, File Systems

Cooling Fans

Attributes: Name, Server Name, Location, Type, Hot Pluggable, Speed, Redundancy State, Status

Relationships: Proliant Server

Processors

Attributes: Name, Server Name, Processor, Cores, L1, L2, L3

Relationships: Proliant Server

OS/Hypervisors

Attributes: Name (OS), Server Name, OS Type, OS Versions Description

Relationships: Proliant Server

The following additional components apply only to Rack and Tower servers.

Power Supplies

Attributes: Name, Server Name, Capacity Used, Maximum Capacity, Redundancy State, Status

Relationships: Proliant Server

HP VMware ESXi (G6, G7 and G8)

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.

Proliant Server

Attributes: Server Name, Serial Number, Product Name, Product Id, Host OS, Host OS Detail

Relationships: Physical Drives, PCI Devices, Temperature Sensors, Logical Drives, Management Processor, Memory, System Board, Cooling Fans, Processors, OS/Hypervisors, Network Interface

Physical Drives

Attributes: Name, Server Name, Serial Number, Bus Width, Configuration Type, Rotational Speed, Block Size, Status

Relationships: Proliant Server

PCI Devices

Attributes: Name, Server Name, PCI Bus, Device Number, Vendor ID, Device ID, Board Name

Relationships: Proliant Server

Temperature Sensors

Attributes: Name, Server Name, Location, Status

Relationships: Proliant Server

Logical Drives

Attributes: Name, Server Name, Package Redundancy, Stripe Size, Block Size, Status

Relationships: Proliant Server

Management Processor

Attributes: Model, Server Name, Serial Number, Firmware Version, Active License Type, Status

Relationships: Proliant Server

Memory

Attributes: Name (Location), Server Name, Type, Size, Frequency, Status

Relationships: Proliant Server

System Board

Attributes: Product Name, Server Name, Serial Number, ROM Version, Redundant ROM Version

Relationships: Proliant Server

Cooling Fans

Attributes: Name, Server Name, Location, Status

Relationships: Proliant Server

Processors

Attributes: Model, Server Name, Cores, L1, L2, L3, Status

Relationships: Proliant Server

OS/Hypervisors

Attributes: Name (OS), Server Name, OS Type, OS Versions, OS Description

Relationships: Proliant Server

Network Interface

Attributes: Name, Server Name, MAC Address, Status

Relationships: Proliant Server

Event monitoring

According to the following Component states this ZenPack will trigger clear , error or warning events with an appropriate summary message.

SNMP Onboard Administrator

Temperature Sensors

Clear event: Status is Other or OK

Warning event: Status is Degraded

Critical event: Status is Failed

Thermal Subsystem

Clear event: Status is Other or OK

Warning event: Status is Degraded

Critical event: Status is Failed

Power Subsystem

Clear event:

• Input Status is No Error
• Status is Other or OK

Warning event: Status is Degraded

Critical event:

• Input Status is one of the following: General Failure, Bist Failure, Fan Failure, Temperature Failure, Inter Lock Open, Eprom Failed, Vref Failed, Dac Failed, Ram Test Failed, Voltage Channel Failed, Orring Diode Failed, Brown Out, Giveup On Startup, Nvram Invalid, Calibration Table Invalid
• Status is Failed

Device Bays

Clear event:

• Powered State is Other or On

• Status is Other or OK

Warning event:

• Powered State is Off, Powered Staged Off or Reboot

• Status is Degraded

Critical event: Status is Failed

Onboard Administrator

Clear event: Status is Other or OK

Warning event: Status is Degraded

Critical event: Status is Failed

Enclosure

Clear event: Status is Other or OK

Warning event: Status is Degraded

Critical event: Status is Failed

SNMP Blade/Rack Device

Management Processors

Clear event: Interface Status is Other or OK

Warning event: Interface Status is Not Responding

Critical event: Interface Status is Failed

Logical Drives

Clear event: Status is Other or OK

Warning event: Status is one of the following Un Configured, Recovering, Ready For Rebuild, Rebuilding, Wrong Drive, Bad Connect, Over Heating, Shutdown, Expanding, Not Available, Queued For Expansion, Multi Path Access Degraded, Erasing

Critical event: Status is Failed

Memory

Clear event: Status is Other or OK

Warning event: Status is Not Responding

Critical event: Status is Failed

Cooling Fan

Clear event: Status is Other or OK

Warning event: Status is Not Responding

Critical event: Status is Failed

Physical Drive

Clear event: Status is Other or OK

Warning event: Status is Erasing,Erase Done, Erase Queued

Critical event: Status is Failed

Temperature Sensors

Clear event: Status is Other or OK

Warning event: Status is Not Responding

Critical event: Status is Failed

Power Supplies

Clear event:

• Input Status is No Error
• Status is Other or OK

Warning event: Status is Degraded

Critical event:

• Input Status is one of the following: General Failure, Bist Failure, Fan Failure, Temperature Failure, Inter Lock Open, Eprom Failed, Vref Failed, Dac Failed, Ram Test Failed, Voltage Channel Failed, Orring Diode Failed, Brown Out, Giveup On Startup, Nvram Invalid, Calibration Table Invalid
• Status is Failed

Processors

Clear event: Status is Other or OK

Warning event: Status is Not Responding

Critical event: Status is Failed

VMWare ESXi Devices

Management Processor

Clear event: Interface Status is Unknown or OK

Warning event: Interface Status is Degraded

Critical event: Interface Status is Major failure

Network Interface

Clear event: Status is OK

Warning event: Status is Degraded

Critical event: Status is MajorFailure

Processors

Clear event: Status is Unkown or OK

Warning event: Status is Stopped

Critical event: Status is Predictive Failure or Error

Logical Drives

Clear event: Status is Unknown or OK

Warning event: Status is Degraded or Minor Failure

Critical event: Status is Major Failure or Critical Failure or Non-recoverable Error

Memory

Clear event: Status is Unknown or OK

Warning event: Status is Degraded

Cooling Fan

Clear event: Status is OK

Warning event: Status is Degraded

Critical event: Status is Major Failure

Physical Drive

Clear event: Status is Unknown or OK

Warning event: Status is Degraded or Minor Failure

Critical event: Status is Major Failure or Critical Failure or Non-recoverable Error

Temperature Sensors

Clear event: Status is OK

Critical event: Status is Failed

Performance Monitoring

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.

SNMP Onboard Administrator

Temperature

Temperature Sensors

Temperature: Current Temperature in Celsius(MAXIMUM)

Power Supply

Power Subsystem

Power Supply: Current Power Supply in WAtts DC(MAXIMUM)

SNMP Blade/Rack Device

Temperature

Temperature Sensors

Temperature: Current temperature in Celsius (MAXIMUM)

Logical Drive

Logical Drives

Logical Drive Usage: Current Reading and Writting rate of Logical Disk Per Second (MAXIMUM)

Power Supplies

Power Supplies

Power Supplies: Current Power Supply in WAtts DC(MAXIMUM)

System Uptime

System Uptime

System Uptime: Current Time in Hours (MAXIMUM)

VMWare ESXi Device

System Uptime

System Uptime

System Uptime: Current Time in Hours (MAXIMUM)

Throughput

Throughput

Throughput: Inbound/Outbound in Bits/sec (MAXIMUM)

Packets, Errors

Packets

Packets: Inbound/Outbound in Bits/sec (MAXIMUM)

Errors

Throughput: Receive/Send in errors/sec (MAXIMUM)

Fan Speed

Fan Graph

Fan Speed: Current Speed in Percentage (MAXIMUM)

Temperature

Temperature Sensors

Temperature: Current Reading in Celsius (MAXIMUM)

Event Management

The following event classes and their subclasses will be continually collected and passed into the Zenoss event management system.

• Alarm

• Event

Various information encoded in these event classes will be used to automatically determine as best as possible the following Zenoss event fields.

Standard Zenoss Event Fields

• device (set to device class)

• component

• summary

• severity

• eventClassKey (for mapping specific event types)

Installed Items

Installing this ZenPack will add the following items to your Zenoss system.

Configuration Properties

• zCollectorPlugins

• zSnmpMonitorIgnore

• zWBEMPassword

• zWBEMPort

• zWBEMUseSSL

• zWBEMUsername

Device Classes

• /Devices/Server/HP/OnboardAdministrator

HP OnBoard Administrator will be added in this device class using OA IP. This device is most likely a Blade Chassis.

This device class uses the HP.snmp.HPEnclosureModeler modeler plugin.

• /Devices/Server/HP/Proliant

Linux/Windows HP Blade/Rack server will be added in this device class using Blade/Rack device IP.

This device class uses the HP.snmp.HPDeviceModeler and HP.snmp.HPSNMPModeler snmp modeller plugin.

If you wish to add these snmp components to existing devices just add the modeller plugins to those devices.

• /Devices/Server/VMware/ESXi/HP

HP VMware ESXi Blade/Rack server will be added in this device class using Blade/Rack device IP.

• /Devices/Server/HP/ILO

This device class uses the HP.ilo.HPILO3Modeler modeler plugin to monitor ILO3/ILO4 devices.

There is a HP.ilo.HPILOModeler plugin to monitor older ILO2 devices.

create /Devices/Server/HP/ILO/2 and add HP.ilo.HPILOModeler to this class to monitor older ilo2 devices.

Modeler Plugins

The following plugins will be used for modeling OnBoard Administrator and Blade using the respective OA and Blade IP Addresses via SNMP interface.

• HPEnclosureModeler

This plugin is for modeling OnBoard Administrator.

• HPSNMPModeler

This plugin is for modeling Blade and Rack devices.

• HPDeviceModeler

This plugin is for retrieving the basic HP hardware and os information.

The following plugins will be used for modeling Blade/Rack details using the WBEM via request and response.

• HPWBEMDeviceModeler

This plugin is for modeling HP firmware, Operating System and controller information.

• HPWBEMPlugin

This plugin is for modeling basic information about the HP VMware ESXi Blade/Rack Server.

The following plugins will be used for modeling an ilo.

• HP.ilo.HPILO3Modeler

This plugin is for modeling ILO3 or ILO4 devices.

• HP.ilo.HPILOModeler

This plugin is for modeling ILO devices.

Datasource Types

• SNMP

• WBEM

• ILO

Monitoring Templates

• HPTemperatureSensors(in /Server/HP/Proliant/OnboardAdministrator)

• HPTemperature (in /Server, /Server/VMware/ESXi/HP)

• HPServerPowerSupply (in /Server, /Server/HP/ILO)

• HPPowerSubsystem(in /Server/HP/Proliant/OnboardAdministrator)

• HPThermalSubsystem(in /Server/HP/Proliant/OnboardAdministrator)

• HPDeviceBay(in /Server/HP/Proliant/OnboardAdministrator)

• HPOnboardAdmin(in /Server/HP/Proliant/OnboardAdministrator)

• HPEnclosure(in /Server/HP/Proliant/OnboardAdministrator)

• HPPhysicalDrive(in /Server, /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPCoolingFan(in /Server , /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPSystemBoard( in /Server , /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPManagementProcessor( in /Server , /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPProcessor( in /Server , /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPLogicalDrive( in /Server , /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPMemory( in /Server , /Server/HP/ILO and /Server/VMware/ESXi/HP)

• HPNetworkInterface( in /Server/VMware/ESXi/HP)

Service Impact and Root Cause Analysis

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.

Enclosure and Blade Impact Relationship Diagram

NonBlade device Impact Relationship Diagram

Internal Impact Relationships

• Device Bays, Temperature Sensors, Power Subsystem, Interconnect Bay and Onboard Administrator failure impacts the related Enclosure which impacts the Blade/Rack server.

• Physical Drive, Logical Drive, Temperature Sensors, Memory, Processors, Management processor, System Board, Proliant Servers, Cooling Fans, PCI Devices, Power Supplies and OS/Hypervisors failure impacts the related Blade/Rack server.

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.

Usage

Adding SNMP Onboard Administrator

Use the following steps to start monitoring the Onboard Administrator using the Zenoss web interface.

1. Navigate to the Infrastructure page.
   

   Add Device
2. Navigate to organizer Devices/Server/HP/Proliant/OnboardAdministrator.
3. Choose Add a Single Device from the add button..
   
4. Fill out the form.
   

   Add Dialog
   • Name can be anything you want.
   • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
5. Click ADD.

Adding Linux SNMP Blade/Rack Device

Use the following steps to start monitoring Linux HP Proliant device using the Zenoss web interface.

1. Navigate to the Infrastructure page.
   File:HP Linux Blade add menu.png

   Add Device
2. Navigate to organizer Devices/Server/HP/Proliant.
3. Choose Add a Single Device from the add button.
   
4. Fill out the form.
   

   Add Dialog
   • Name can be anything you want.
   • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
5. Click ADD.

Adding an ILO Device

Use the following steps to start monitoring Windows HP Proliant device using the Zenoss web interface.

1. Set the zILOPassword and zILOUserName for the organizer Devices/Server/HP/ILO.
2. Navigate to the Infrastructure page.
3. Navigate to organizer Devices/Server/HP/ILO.
4. Choose Add a Single Device from the add button.
   
5. Fill out the form.
   • Name can be anything you want.
   • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
6. Click ADD.

Adding VMware ESXi device

Use the following steps to start monitoring VMware ESXi device using the Zenoss web interface.

1. Navigate to the Infrastructure page.
   

   Add Device
2. Navigate to organizer Devices/Server/VMware/ESXi/HP.
3. Choose Add a Single Device from the add button.
   
4. Fill out the form.
   

   Add Dialog
   • Name can be anything you want.
   • Hostname or IP must be resolvable and accessible from the collector server chosen in the Collector field.
5. Click ADD.
6. HP VMware ESXi server will be added in the /Devices/Server/VMware/ESXi/HP device class.

Use the following steps for successful modeling.

1. Select the device added.
2. Navigate to Configuration Properties.
   

   Model device
3. Provide the values for zWBEMPassword, zWBEMPort, zWBEMUseSSL and zWBEMUsername.
4. Model the device.

Adding Windows Blade/Rack device to the /Server/Microsoft/Windows/HP class

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.

1. Navigate to the Infrastructure page
2. Navigate to Devices/Server/Microsoft/Windows device class
3. Select + on the bottom left to add a device class
4. For Name textbox, enter HP and select Submit
5. Select Details for Devices/Server/Microsoft/Windows/HP device class
6. Select Modeler Plugins
7. Add HP.snmp.HPSNMPModeler and HP.snmp.HPDeviceModeler to the Selected list
8. Select 'Save'
9. Please look at http://wiki.zenoss.org/ZenPack:Microsoft_Windows_(beta)#Usage on details to model/monitor using WinRM

zenbatchload

• Alternatively you can use zenbatchload to add devices from the command line.
• To do this, you must create a file with contents similar to the following.
• Replace all values in angle brackets with your values minus the brackets.
• Multiple devices can be added under the same sections.

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

zenbatchload <filename>

Limitation

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.

Known Issue when monitoring systems with Failover Onboard Administrators

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.

Known Issue upgrading from 1.0 to 3.0

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

Known issue regarding ilo unknown or N/A values

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.

Changes

3.0.1

• standardized commonly used code for converting RRD status to formatted string
• standardized most component properties to those common between collection methods (some still outstanding)
• standardized common datasource/datapoint names throughout templates
• simplified customized classes to reduce duplication of function
• removed duplicate property definitions with similar names but identical values
• removed most component properties that should have been performance or status datasources
• standardized unit testing for modeler plugins and class loading
• folded deviceMap modeler plugins into component modeler plugins, removed device map plugins
• added ZenPack class to remove all RRD templates upon ZP uninstall
• changed Fan Speed to display status string (only ILO shows actual speed)
• SNMP modeler plugins are now appropriate for use wherever SNMP is supported
• deprecated HPOSHypervisor and HPThermalSubsystem components
• removed COMMAND datasource from HPLogicalDrive (used snmpindex_dct instead)
• added ILO datasource queries for HPChassis, HPProcessor, HPManagementController, HPNetworkInterfaceController, and updated ILODatasource to accommodate
• added "perfID" to ILO HPTemperature components to correct some missing datapoints
• updated migrate methods to remove all templates before re-adding from YAML
• removed "uptime" metric from HPSystemBoard since it duplicates the Device sysUptime datapoint
• added several status indicators to HPManagementController component (SNMP)
• re-based SNMP Device templates on /Server/Linux to ensure consistency

3.0.0

• major rewrite of significant sections of the zenpack to use zenpacklib and remove obvious defects.

1.0.0

• Initial release of the zenpack

Installation

Normal Installation (packaged egg)

1. Download the appropriate egg file for the version of Zenoss you are running.
2. Ensure you are logged in as the zenoss user:

   $ sudo su - zenoss

3. Install the ZenPack:

   $ zenpack --install ZenPacks.zenoss.HP.Proliant-*.egg

4. Restart these services:

   $ zenoss restart

Discuss

New: Don't forget to add yourself to the Zenoss User Map!