ZenPack:IBM Power

From Zenoss Wiki
Revision as of 16:28, 18 December 2014 by Eedgar (Talk | contribs)$7

Jump to: navigation, search

Note: This ZenPack is available in commercial versions of Zenoss. Click here to request more information about this commercial ZenPack. Click here to see all commercial ZenPacks.

Zenoss, Inc.
ZenPack name
More Information
GitHub page/HomePage

Devices Monitored:

IBM Power ZenPack

Monitoring IBM Power Servers with the help of HMC interface.


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.


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


Version 1.0
Requires [[ZenPack:PythonCollector>=1.2|PythonCollector>=1.2 ZenPack]]
Compatible with Zenoss Resource Manager 4.2.x


This ZenPack provides support for monitoring IBM Power Server (P5/P6/P7), with the IBM HMC interface. Monitoring is performed using the HMC interface. This ZenPack is currently supported for IBM Power servers running on the AIXLinux Operating System.

Supported versions of HMC
V 7
Supported versions of Power Servers
Supported Operating systems of Logical partition
AIX, Linux


Zenoss Version
External Dependencies
SSH should be configured and running on IBM HMC Server.
This should be verified using SSH command from HMC server:
lssyscfg -r sys
  • This will list all the Managed Systems under HMC


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.
  • Service impact and root cause analysis. (Requires Zenoss Service Dynamics)


IBM HMC Server

The following components will be automatically discovered through the HMC Server IP address and the host name you provide. The properties and relationships will be continually maintained

HMC Server
Attributes: Serial Number, BIOS, Model Number, Version, Build Level, Service Pack, Release
Relationships: Managed Systems, Logical Partitions, HMC Service Processor
Managed Systems
Attributes: Server Name, Serial Number, Model, Service Partition, State
Relationships: HMC Server, I/O Devices, Processor Pools, HEA, HEAPorts, LHEA, LHEA Ports, Profiles, Port Groups, IO Pools
Relationships: LogicalPartitions
I/O Devices
Attributes: Slot, Server Name, Owner, Description, Bus ID, I/O Pool ID
Relationships: Managed Systems
I/O Pools
Attributes: Pool ID, Server Name, LPAR Name, LPAR ID, I/O Pools Allowed
Relationships: Managed Systems
Logical Partitions
Attributes: LPAR Name, LPAR ID, Server Name, Serial Number, Work Group ID, OS Version, Processing Units, Assigned Memory, State
Relationships: HMC Server
HMC Service Processor
Attributes: Serial Number, IP Address, Location Code, Service Processor Role, Connection State
Relationships: HMC Server
Processor Pools
Attributes: Pool Name, Shared Processor Pool ID, LPAR IDs
Relationships: ManagedSystem
Attributes: phys_loc, state
Relationships: ManagedSystem
Hea Port
Attributes: speed, duplex, state
Relationships: ManagedSystem, Hea, PortGroup, LogicalPartition
Attributes: capability, drc_name
Relationships: ManagedSystem, LogicalPartition
LHea Port
Attributes: drc_name, drc_index, state
Relationships: ManagedSystem, PortGroup, LogicalPartition
Port Group
Attributes: phys_port_ids, curr_port_group_mcs_value
Relationships: ManagedSystem, LogicalPartition, HeaPort, LHeaPort

Performance Monitoring

The following metrics will be collected every 5 minutes by default. Any other IBM HMC Server metrics can also be collected by adding them to the appropriate monitoring template.

  • Packets
  • Processor Utilization
  • Processor Units Used
  • Memory Used
  • Processor Utilization
  • Memory Utilization
  • Utilization

Event Monitoring

This zenpack will monitor the power states of the logical partitions and managed systems. Currently this is the only out of box event creation.

IBM Power Server

Installed Items

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

Configuration Properties
  • zCollectorPlugins
  • zSnmpMonitorIgnore
  • zDeviceTemplates
  • zCommandUsername
  • zCommandPassword
  • zCommandCommandTimeout
  • zCommandPort
  • zKeyPath
Device Classes
  • /Devices/Server/IBM/Power/HMC
IBM HMC Server will be added in this device class using HMC IP.

Modeler Plugins

The following plugins will be used for modeling HMC Server and IBM Power Server using the HMC Server IP Addresses via SSH interface.

  • HMCModelerPlugin
This plugin is for modeling IBM HMC Server and IBM Power Server.

Datasource Types
Monitoring Templates
  • PortGroup (in /Server/IBM/Power/HMC)
  • Hea (in /Server/IBM/Power/HMC)
  • HeaPort (in /Server/IBM/Power/HMC)
  • LHea (in /Server/IBM/Power/HMC)
  • LHeaPort (in /Server/IBM/Power/HMC)
  • Device (in /Server/IBM/Power/HMC)
  • IODevices (in /Server/IBM/Power/HMC)
  • IOPools (in /Server/IBM/Power/HMC)
  • Profile (in /Server/IBM/Power/HMC)
  • ProcessorPools (in /Server/IBM/Power/HMC)
  • ServiceProcessor (in /Server/IBM/Power/HMC)
  • ManagedSystems (in /Server/IBM/Power/HMC)
  • LogicalPartitions (in /Server/IBM/Power/HMC)

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

IBM and Power Server Impact Relationship Diagram
Internal Impact Relationships
  • Managed Systems, Logical Partitions, HMC Service Processor and Processor Pools impacts the related HMC Server
  • Memory, Processors, I/O Devices, Host Ethernet Adapters and I/O Pools failure impacts the related Managed Systems which impacts the HMC Server.
  • Managed Systems failure impacts the related Logical Partitions which impacts the HMC 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 HMC Server failure will imply that all related hosts are also failed.

Zenoss Analytics

This ZenPack provides additional support for Zenoss Analytics. Perform the following steps to install extra reporting resources into Zenoss Analytics after installing the ZenPack.

  1. Copy analytics-bundle.zip from $ZENHOME/ZenPacks/ZenPacks.zenoss.IBM.Power/analytics/ on your Zenoss server.
  2. Navigate to Zenoss Analytics in your browser.
  3. Login as superuser.
  4. Remove any existing IBM Power ZenPack folder.
    1. Choose Repository from the View menu at the top of the page.
    2. Expand Public in the list of folders.
    3. Right-click on IBM Power ZenPack folder and choose Delete.
    4. Confirm deletion by clicking OK.
  5. Add the new IBM Power ZenPack folder.
    1. Choose Server Settings from the Manage' menu at the top of the page.
    2. Choose Import in the left page.
    3. Remove checks from all check boxes.
    4. Click Choose File to import a data file.
    5. Choose the analytics-bundle.zip file copied from your Zenoss server.
    6. Click Import.You can now navigate back to the IBM Power ZenPack folder in the repository to see the following resources added by the bundle.


Adding HMC Server

Use the following steps to start monitoring HMC Server using the Zenoss web interface.

  1. Navigate to the Infrastructure page.
    Add Device
  2. Navigate to organizer Devices/Server/IBM/Power/HMC.
  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. IBM HMC Server will be added in the /Devices/Server/IBM/Power/HMC 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 zCommandUsername and zCommandPassword.
  4. Model the device.


  • 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/IBM/Power/HMC' <device name>  setManageIp="<IP Address>", zCommandUsername='<username>', zCommandPassword='<password>'

Example : /Devices/Server/IBM/Power/HMC HMC_1 setManageIp='', zCommandUsername='hcladmin', zCommandPassword='root123'

You can then load the Devices using zenbatchload with the following command.

zenbatchload <filename>


  • Storage Mapping has not been implemented in this release.


  • Initial release.


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.IBM.Power-*.egg
  4. Restart these services:
    $ zenoss restart


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

blog comments powered by Disqus