View source for ZenPack:HP-UX (Commercial)

{{ZenPack
|Summary=The HpuxMonitor ZenPack enables Resource Manager to use Secure Shell (SSH) to monitor Hewlett Packard UNIX (HP-UX) hosts.
|Organization=Zenoss, Inc.
|ZenPack name=ZenPacks.zenoss.HpuxMonitor
|Documentation URL=http://www3.zenoss.com/l/3432/2013-02-28/33h45x
|Flavor=commercial
|Releases={{Release
|Version=2.0.1
|Release date=2016/09/06
|Compatible with=Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x, Zenoss Resource Manager 5.1.x, Zenoss Resource Manager 5.x.x
|Download URL=https://zenoss.leapfile.net/
}}
|Devices=
|Applications=
|Integrations=
|DataAudits=
}}
The <span class="zenpack">ZenPacks.zenoss.HpuxMonitor</span> ZenPack uses Secure Shell (SSH) to monitor HP-UX hosts.

This ZenPack models and monitors devices placed in the <span class="ph filepath">/Server/SSH/HP-UX</span> device class (or <span class="ph filepath">/Server/SSH/HP-UX/Itanium</span> if appropriate) by running commands and parsing the output.


== Features ==

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

* Initial discovery and periodic remodeling of relevant components.
* Performance monitoring.

This ZenPack provides:

* File system and process monitoring
* Network interfaces and route modeling
* CPU utilization information
* Hardware information (memory, number of CPUs, machine serial numbers, model numbers)
* OS information (OS level command style information)
* Installed software information

=== Discovery ===

Standard device components will be automatically discovered through the HP-UX server address, username and password you provide. The properties and relationships will be periodically updated by modeling.

The components, relations, and attributes will be updated on Zenoss' normal remodeling interval, which defaults to every 12 hours.


=== Performance Monitoring ===

The following metrics will be collected every 5 minutes by default.

* Default OS performance Metrics

;Device
* sysUptime
* laLoadInt1
* laLoadInt5
* laLoadInt15
* ssCpuIdle
* ssCpuSystem
* ssCpuUser
* ssCpuInterrupt
* io_reads_and_writes
* percentMemUsed
* percentSwapUsed

;FileSystem
* availBlocks
* availInodes
* totalBlocks
* totalInodes
* usedBlocks
* usedInodes
* percentInodesUsed

;OSProcess
* ps_cpu
* ps_mem
* ps_count

;ethernetCsmacd
* ifInErrors
* ifInOctets
* ifInPackets
* ifOutErrors
* ifOutOctets
* ifOutPackets

<br clear=all>


== Usage ==

<span class="notetitle">Note:</span>
If using a distributed collector setup, SSH requires firewall access (default of port 22) from the collector to the monitored server.

=== Set HP-UX Server Monitoring Credentials ===

All HP-UX servers must have a device entry in an organizer below the <span class="ph filepath">/Devices/Server/SSH/HP-UX</span> device class.

<span class="notetitle">Note:</span>
The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.

<ol>
<li>Navigate to the device class or device.

<ul>
<li>If applying changes to a device class:

<ol>
<li>Select the class in the devices hierarchy.
</li>
<li>Click '''Details'''.
</li>
<li>Select Configuration Properties.
</li></ol>
</li>
<li>If applying changes to a device:

<ol>
<li>Click the device in the device list.
</li>
<li>Select Configuration Properties.
</li></ol>
</li></ul>
</li>
<li>Verify the credentials for the service account to access the service.

{| class="wikitable"
|+ <span class="tablecap"><span class="tablecap">HP-UX Configuration Properties</span></span>
!width="50%"|Name
!width="50%"|Description
|-
|zCommandUsername

|HP-UX user with privileges to gather performance information

|-
|zCommandPassword

|Password for the HP-UX user

|}

</li>
<li>Click <span class="ph uicontrol guibutton">Save</span> to save your changes.
</li></ol>

=== Add an HP-UX Server ===

The following procedure assumes that the credentials have been set.

<ol>
<li>From Infrastructure > Devices, select Add a Single Device.
</li>
<li>Enter the following information in the dialog:

{| class="wikitable"
|+ <span class="tablecap"><span class="tablecap">Adding HP-UX Device Information</span></span>
!width="50%"|Name
!width="50%"|Description
|-
|Name or IP

|HP-UX host to model

|-
|Device Class

|<span class="ph filepath">/Server/SSH/HP-UX</span> or <span class="ph filepath">/Server/SSH/HP-UX/Itanium</span>

|-
|Model Device

|Select this option unless adding a device with username/password different than found in the device class. If you do not select this option, then you must add the credentials, and then manually model the device.

|}

</li>
<li>Click '''Add Device''' to add the device.
</li></ol>

== Troubleshooting ==

This ZenPack requires the following collector process to be running.

{| class="wikitable"
!width="50%"|Type
!width="50%"|Name
|-
|Modeler
|<span class="keyword cmdname">zenmodeler</span>
|-
|Performance Collector
|<span class="keyword cmdname">zencommand</span>
|}

=== Itanium Device Class ===
The Devices/Server/SSH/HP-UX/Itanium device class is intended to be used when monitoring Intel Itanium-based hardware.  This device class uses some different commands to obtain Itanium-related data. 

=== Resolving CHANNEL_OPEN_FAILURE Issues ===

The <span class="keyword cmdname">zencommand</span> daemon's log file (<span class="ph filepath">$ZENHOME/<var class="keyword varname replaceable">collector</var>/zencommand.log</span>) may show messages stating:

<pre class="pre codeblock screen">ERROR zen.SshClient CHANNEL_OPEN_FAILURE: Authentication failure
WARNING:zen.SshClient:Open of command failed (error code 1): open failed</pre>
If the <span class="keyword cmdname">sshd</span> daemon's log file on the remote device is examined, it may report that the <samp class="ph codeph literal">MAX_SESSIONS</samp> number of connections has been exceeded and that it is denying the connection request. At least in the OpenSSH daemons, this <samp class="ph codeph literal">MAX_SESSIONS</samp> number is a compile-time option and cannot be reset in a configuration file.

To work around this limitation of the <span class="keyword cmdname">sshd</span> daemon, use the configuration property <var class="keyword varname">zSshConcurrentSessions</var> to control the number of connections created by <span class="keyword cmdname">zencommand</span> to the remote device.

<ol>
<li>Navigate to the device or device class in the <span class="ph">Zenoss platform</span> interface.

<ul>
<li>If applying changes to a device class:

<ol>
<li>Select the class in the devices hierarchy.
</li>
<li>Click '''Details'''.
</li>
<li>Select Configuration Properties.
</li></ol>
</li>
<li>If applying changes to a device:

<ol>
<li>Click the device in the device list.
</li>
<li>Select Configuration Properties.
</li></ol>
</li></ul>
</li>
<li>Apply an appropriate value for the maximum number of sessions.

{| class="wikitable"
|+ <span class="tablecap"><span class="tablecap">Concurrent SSH Configuration Properties</span></span>
!width="50%"|Name
!width="50%"|Description
|-
|zSshConcurrentSessions

|Maximum number of sessions supported by the remote device's <samp class="ph codeph literal">MAX_SESSIONS</samp> parameter. Common values for AIX are 2 or 10.

|}

</li>
<li>Click '''Save''' to save your changes.
</li></ol>

=== Resolving Timeout Issues ===

The <span class="keyword cmdname">zencommand</span> daemon's log file (<span class="ph filepath">$ZENHOME/<var class="keyword varname replaceable">collector</var>/zencommand.log</span>) may show messages stating:

<pre class="pre codeblock screen">WARNING:zen.zencommand:Command timed out on device device_name: command</pre>
If this occurs, it usually indicates that the remote device has taken too long to return results from the commands. To increase the amount of time for devices to return results, change the configuration property <var class="keyword varname">zCommandCommandTimeout</var> to a larger value.

<ol>
<li>Navigate to the device or device class in the <span class="ph">Zenoss platform</span> interface.

<ul>
<li>If applying changes to a device class:

<ol>
<li>Select the class in the devices hierarchy.
</li>
<li>Click '''Details'''.
</li>
<li>Select Configuration Properties.
</li></ol>
</li>
<li>If applying changes to a device:

<ol>
<li>Click the device in the device list.
</li>
<li>Select Configuration Properties.
</li></ol>
</li></ul>
</li>
<li>Apply an appropriate value for the command timeout.

{| class="wikitable"
|+ <span class="tablecap"><span class="tablecap">SSH Timeout Configuration Properties</span></span>
!width="50%"|Name
!width="50%"|Description
|-
|zCommandCommandTimeout

|The number of seconds to wait for commands to complete on the remote device.

|}

</li>
<li>Click '''Save''' to save your changes.
</li></ol>


=== Notes === 
The HP-UX machines may require updating /etc/PATH

You may want only one of the cpu or cpu_itanium plugins.
Listing the PA-RISC or Itanium processors requires root access
on the HP-UX to call /usr/bin/adb. Alternatively, the command
strings can be modified to use sudo. Sudo can be installed from
http://hpux.connect.org.uk/ftp/hpux/Sysadmin/sudo-1.8.0/

Some modeler commands depend on the "machinfo" command, which may need to be installed on the target HP-UX device
=== Known Issues ===


=== Limitations === 


=== Changes === 

;2.0.1
* Fix modeling "ValueError" when swap volumes are disabled (ZEN-23286)
* Add common datapoint aliases (ZEN-24619)

;2.0.0
* conversion to YAML definitions and ZenPackLib
* More user friendly graph legends (ZEN-22432)
* Lowered default zSshConcurrentSessions to 5 (ZEN-22431)
* Changed event class for High Load threshold (ZEN-22433)
{{ZenPackFooter}}