Accelerate Your Path to Full-Stack Monitoring and Alerting
Register for this live webinar featuring Zenoss and VictorOps today!
Why Customers Choose Us
Discover why the largest companies in the world choose Zenoss.
Customer Support Portal
Zenoss Learning Center
Zenoss Partner Portal
Become a Partner
Top 5 Focus Areas to Succeed With DevOps
Forrester shares the tools, technologies and best practices to meet the challenges of today's modern IT environments.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
This ZenPack provides status and performance monitoring of AIX systems.
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
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x
The ZenPacks.zenoss.AixMonitor ZenPack uses Secure Shell (SSH) to monitor AIX hosts.
This ZenPack models and monitors devices placed in the /Server/SSH/AIX device class by running commands and parsing the output. The account used to monitor the device does not require root access or special privileges.
The features added by this ZenPack can be summarized as follows. They are each detailed further below.
This ZenPack provides:
The following components will be automatically discovered through the AIX server address, username and password you provide. The properties and relationships will be periodically updated by modeling.
Attributes: ent_cpu, ent_vproc, active_cpu, systemId, prof_max_mem, ent_mem
Attributes: devname, location, parent, physloc
The following metrics will be collected every 5 minutes by default.
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
Note: If using a distributed collector setup, SSH requires firewall access (default of port 22) from the collector to the monitored server.
All AIX servers must have a device entry in an organizer below the /Devices/Server/SSH/AIX 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.
AIX user with privileges to gather performance information
Password for the AIX 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
AIX host to model
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/AIX/IBM_PowerVM device class is intended to be used when monitoring PowerVM LPARs. This device class creates an additional AIXExt template to be used in monitoring the PowerVM equipment.
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.
When Migrating from 1.2.0 to a newer version of this ZenPack the Filesystem cycle time changed from 60 to 300. If your filesystem graphs are not updating you will need to delete the existing filesystem rrd files so that new ones can be generated with the new 300 second step time.
When upgrading this ZenPack from version 1.3.0 to a later version, a traceback containing the text:
AttributeError: 'ZenPack' object has no attribute '__of__'
may be encountered. This traceback does not affect the functionality of the ZenPack, which should function normally after installation is completed.
Some commands used in the AIXExt template may be incompatible with your version of AIX. You should disable those datasources if that is the case and it is impacting your installation.
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.