LIVE Webinar: Dec. 19, 1pm CSTLearn how to overcome the challenges posed by containerized microservices in highly dynamic IT environments.
451 Research: Key Trends in Machine Learning, AI & Cloud
Zenoss is the only enterprise monitoring solution certified Nutanix Ready - Integrated.
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Forrester Insights:Powering Digital Transformation With Intelligent Monitoring & Analytics
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
This ZenPack provides status and performance monitoring of HP-UX.
This ZenPack is included with commercial versions of Zenoss. Enterprise support for this ZenPack is provided to active Zenoss customers.
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x - 5.1.x
The ZenPacks.zenoss.HpuxMonitor ZenPack uses Secure Shell (SSH) to monitor HP-UX hosts.
This ZenPack models and monitors devices placed in the /Server/SSH/HP-UX device class (or /Server/SSH/HP-UX/Itanium if appropriate) by running commands and parsing the output.
The features added by this ZenPack can be summarized as follows. They are each detailed further below.
This ZenPack provides:
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.
The following metrics will be collected every 5 minutes by default.
Default OS performance Metrics
Note: If using a distributed collector setup, SSH requires firewall access (default of port 22) from the collector to the monitored server.
All HP-UX servers must have a device entry in an organizer below the /Devices/Server/SSH/HP-UX device class.
Note: The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.
Verify the credentials for the service account to access the service.
HP-UX user with privileges to gather performance information
Password for the HP-UX user
Click Save to save your changes.
The following procedure assumes that the credentials have been set.
Enter the following information in the dialog:
Name or IP
HP-UX host to model
/Server/SSH/HP-UX or /Server/SSH/HP-UX/Itanium
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.
Click Add Device to add the device.
This ZenPack requires the following collector process to be running:
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.
The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show messages stating:
ERROR zen.SshClient CHANNEL_OPEN_FAILURE: Authentication failure
WARNING:zen.SshClient:Open of command failed (error code 1): open failed
If the sshd daemon's log file on the remote device is examined, it may report that the MAX_SESSIONS number of connections has been exceeded and that it is denying the connection request. At least in the OpenSSH daemons, this MAX_SESSIONS number is a compile-time option and cannot be reset in a configuration file.
To work around this limitation of the sshd daemon, use the configuration property zSshConcurrentSessions to control the number of connections created by zencommand to the remote device.
Navigate to the device or device class in the Zenoss platform interface.
Apply an appropriate value for the maximum number of sessions.
Maximum number of sessions supported by the remote device's MAX_SESSIONS parameter. Common values for AIX are 2 or 10.
WARNING:zen.zencommand:Command timed out on device device_name: command
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 zCommandCommandTimeout to a larger value.
Apply an appropriate value for the command timeout.
The number of seconds to wait for commands to complete on the remote device.
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
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.