Difference between revisions of "ZenPack:AIX"

From Zenoss Wiki
Jump to: navigation, search
(Replace 2.2.1 release with 2.2.2.)
 
(9 intermediate revisions by 5 users not shown)
Line 3: Line 3:
 
|Organization=Zenoss, Inc.
 
|Organization=Zenoss, Inc.
 
|ZenPack name=ZenPacks.zenoss.AixMonitor
 
|ZenPack name=ZenPacks.zenoss.AixMonitor
|Documentation URL=http://www3.zenoss.com/l/3432/2013-02-27/33fv9l
+
|Documentation URL=http://pages.zenoss.com/ContactUs-ZP.html?utm_source=Cm&utm_medium=WS&utm_campaign=Contact-ZenPack&utm_asset=REQ&utm_product=AIX
 
|Flavor=commercial
 
|Flavor=commercial
 
|Releases={{Release
 
|Releases={{Release
|Version=2.0.0
+
|Version=2.2.2
|Release date=2014/12/18
+
|Release date=2016/08/30
|Compatible with=Zenoss Resource Manager 4.2.x
+
|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/
 +
}}{{Release
 +
|Version=2.0.1
 +
|Release date=2015/04/02
 +
|Compatible with=Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x
 +
|Download URL=https://zenoss.leapfile.net/
 
}}
 
}}
 
|Devices=
 
|Devices=
Line 25: Line 31:
 
}}
 
}}
 
The <span class="zenpack">ZenPacks.zenoss.AixMonitor</span> ZenPack uses Secure Shell (SSH) to monitor AIX hosts.
 
The <span class="zenpack">ZenPacks.zenoss.AixMonitor</span> ZenPack uses Secure Shell (SSH) to monitor AIX hosts.
 
  
 
This ZenPack models and monitors devices placed in the <span class="ph filepath">/Server/SSH/AIX</span> device class by running commands and parsing the output. The account used to monitor the device does not require root access or special privileges.
 
This ZenPack models and monitors devices placed in the <span class="ph filepath">/Server/SSH/AIX</span> device class by running commands and parsing the output. The account used to monitor the device does not require root access or special privileges.
 +
 +
== 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:
 
This ZenPack provides:
Line 38: Line 50:
 
* LPP and RPM information (such as installed software)
 
* LPP and RPM information (such as installed software)
  
== Prerequisites ==
+
=== Discovery ===
  
 +
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.
  
{| class="wikitable"
+
;Server (Device)
!width="50%"|Prerequisite
+
: Attributes: ent_cpu, ent_vproc, active_cpu, systemId, prof_max_mem, ent_mem
!width="50%"|Restriction
+
|-
+
|Product
+
|<span class="ph">Zenoss platform</span> 4.2.x
+
|-
+
|Required ZenPacks
+
|ZenPacks.zenoss.AixMonitor
+
|-
+
|AIX Releases Supported
+
|5.3 and 6.1 and 7.1
+
|}
+
  
 +
;EntAdapter
 +
: Attributes: devname, location, parent, physloc
  
<span class="notetitle">Note:</span>
+
;FCAdapter
If using a distributed collector setup, SSH requires firewall access (default of port 22) from the collector to the monitored server.
+
: Attributes: devname, location, parent, physloc
  
 +
;HDisk
 +
: Attributes: devname, location, parent, physloc
  
== Add an AIX Server ==
+
=== Performance Monitoring ===
  
 +
The following metrics will be collected every 5 minutes by default.
  
The following procedure assumes that the credentials have been set.
+
* Default OS performance Metrics
  
 +
;Device
 +
* ssCpuIdle
 +
* ssCpuSystem
 +
* ssCpuUser
 +
* ssCpuWait
 +
* ssRawContexts
 +
* ssRawInterrupts
 +
* io_read
 +
* io_written
 +
* hrMemorySize
 +
* memAvailReal
 +
* percentMemUsed
 +
* swap_percentUsed
 +
* sysUptime
 +
* laLoadInt1
 +
* laLoadInt5
 +
* laLoadInt15
  
<ol>
+
;EntAdapter
<li>From Infrastructure > Devices, select Add a Single Device.
+
* receive_bytes
</li>
+
* receive_packets_dropped
<li>Enter the following information in the dialog:
+
* transmit_bytes
 +
* transmit_packets_dropped
 +
* recvHugeutil
 +
* recvLargeutil
 +
* recvMediumutil
 +
* recvSmallutil
 +
* recvTinyutil
  
 +
;FCAdapter
 +
* control_requests
 +
* input_bytes
 +
* input_requests
 +
* output_requests
 +
* output_bytes
 +
* output_requests
  
{| class="wikitable"
+
;HDisk
|+ <span class="tablecap"><span class="tablecap">Adding AIX Device Information</span></span>
+
* b_written
!width="50%"|Name
+
* b_read
!width="50%"|Description
+
* policies_algorithm
|-
+
* policies_reserve_policy
|Name or IP
+
  
|AIX host to model
+
<br clear=all>
  
|-
+
== Service Impact and Root Cause Analysis ==
|Device Class
+
  
|<span class="ph filepath">/Server/SSH/AIX</span>
+
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.
  
|-
+
[[File:aix-impact-yuml.png|thumb|320px|IBM and Power Server Impact Relationship Diagram]]
|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.
+
;Internal Impact Relationships
  
|}
+
* Ethernet Adapter impacts related Device (LPAR)
 +
* Fibre Channel Adapter impacts related Device (LPAR)
 +
* HDisk Drive impacts related Device (LPAR)
  
 +
<br clear=all>
 +
== Usage ==
  
</li>
+
<span class="notetitle">Note:</span>
<li>Click '''Add Device''' to add the device.
+
If using a distributed collector setup, SSH requires firewall access (default of port 22) from the collector to the monitored server.
</li></ol>
+
 
+
 
+
== Set AIX Server Monitoring Credentials ==
+
  
 +
=== Set AIX Server Monitoring Credentials ===
  
 
All AIX servers must have a device entry in an organizer below the <span class="ph filepath">/Devices/Server/SSH/AIX</span> device class.
 
All AIX servers must have a device entry in an organizer below the <span class="ph filepath">/Devices/Server/SSH/AIX</span> device class.
 
  
 
<span class="notetitle">Note:</span>
 
<span class="notetitle">Note:</span>
 
The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.
 
The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.
 
  
 
<ol>
 
<ol>
Line 133: Line 166:
 
</li>
 
</li>
 
<li>Verify the credentials for the service account to access the service.
 
<li>Verify the credentials for the service account to access the service.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 150: Line 182:
  
 
|}
 
|}
 
  
 
</li>
 
</li>
Line 156: Line 187:
 
</li></ol>
 
</li></ol>
  
 +
=== Add an AIX Server ===
  
== Device Components ==
+
The following procedure assumes that the credentials have been set.
  
This zenpack creates new custom components for Ethernet Adapters, Fiber Channel Adapters and Hard Disks.
+
<ol>
These new components can impact the Aix Device.
+
<li>From Infrastructure > Devices, select Add a Single Device.
 +
</li>
 +
<li>Enter the following information in the dialog:
  
== Monitoring Metrics ==
+
{| class="wikitable"
  Metrics are provided in the following templates.
+
|+ <span class="tablecap"><span class="tablecap">Adding AIX Device Information</span></span>
Devices/Server/SSH/Aix:  AIXExt, Device, EntAdapter, ethernetCsmacd, FCAdapter, FileSystem, HDisk, OSProcess,
+
!width="50%"|Name
 +
!width="50%"|Description
 +
|-
 +
|Name or IP
  
== IBM_PowerVM Device Class ==
+
|AIX host to model
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.
+
|-
 +
|Device Class
 +
 
 +
|<span class="ph filepath">/Server/SSH/AIX</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>
 +
|}
  
== Resolving CHANNEL_OPEN_FAILURE Issues ==
+
=== IBM_PowerVM Device Class ===
 +
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.
  
 +
=== 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:
 
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:
Line 180: Line 249:
  
 
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.
 
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>
 
<ol>
Line 206: Line 274:
 
</li>
 
</li>
 
<li>Apply an appropriate value for the maximum number of sessions.
 
<li>Apply an appropriate value for the maximum number of sessions.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 218: Line 285:
  
 
|}
 
|}
 
  
 
</li>
 
</li>
Line 224: Line 290:
 
</li></ol>
 
</li></ol>
  
 
+
=== Resolving Timeout Issues ===
== 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:
 
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:
Line 232: Line 296:
 
<pre class="pre codeblock screen">WARNING:zen.zencommand:Command timed out on device device_name: command</pre>
 
<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.
 
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>
 
<ol>
Line 258: Line 321:
 
</li>
 
</li>
 
<li>Apply an appropriate value for the command timeout.
 
<li>Apply an appropriate value for the command timeout.
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 270: Line 332:
  
 
|}
 
|}
 
  
 
</li>
 
</li>
Line 276: Line 337:
 
</li></ol>
 
</li></ol>
  
 +
=== Known Issues ===
 +
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. 
  
== Features ==
 
  
The features added by this ZenPack can be summarized as follows. They are each detailed further below.
+
When upgrading this ZenPack from version 1.3.0 to a later version, a traceback containing the text:
  
* Initial discovery and periodic remodeling of relevant components.
+
AttributeError: 'ZenPack' object has no attribute '__of__'
* Performance monitoring.
+
  
=== Discovery ===
+
may be encountered.  This traceback does not affect the functionality of the ZenPack, which should function normally after installation is completed.
  
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.
 
  
;Server (Device)
+
=== Limitations ===
: Attributes: ent_cpu, ent_vproc, active_cpu, systemId, prof_max_mem, ent_mem
+
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.
  
;EntAdapter
+
=== Changes ===
: Attributes: devname, location, parent, physloc
+
  
;FCAdapter
+
2.2.2
: Attributes: devname, location, parent, physloc
+
* Make event class /Status/OSProcess for process monitoring (ZEN-21999)
 +
* Add zCredentialsZProperties: zCommandUsername & zCommandPassword
 +
* Add mem__pct and fs__pct datapoint aliases (ZEN-24619)
  
;HDisk
+
2.2.1
: Attributes: devname, location, parent, physloc
+
* Updated zenpacklib.py to address modeler timeouts from attribute-indexed components
  
=== Performance Monitoring ===
+
2.2.0
 
+
* Fix excessive remote command execution (ZEN-16740)
The following metrics will be collected every 5 minutes by default.
+
* IP Service modeling no longer ignoring zIpServiceMapMaxPort (ZEN-17360)
 
+
* Fix incorrect ssCpuIdle alias for multi-core systems (ZEN-17360)
* Default OS performance Metrics
+
* Fix handling of European date formats (ZEN-19089)
 
+
* Fix incorrect template bindings (ZEN-20078)
;Device
+
* Fix incorrect modeling time (ZEN-22127)
* ssCpuIdle
+
* Add/revise custom component icons, fix icon positioning (ZEN-22191, ZEN-22294)
* ssCpuSystem
+
* Fix missing Impact YAML file (ZEN-22250)
* ssCpuUser
+
* Fixed missing graph datapoints (ZEN-22259)
* ssCpuWait
+
* ssRawContexts
+
* ssRawInterrupts
+
* io_read
+
* io_written
+
* hrMemorySize
+
* memAvailReal
+
* percentMemUsed
+
* swap_percentUsed
+
* sysUptime
+
* laLoadInt1
+
* laLoadInt5
+
* laLoadInt15
+
 
+
;EntAdapter
+
* receive_bytes
+
* receive_packets_dropped
+
* transmit_bytes
+
* transmit_packets_dropped
+
* recvHugeutil
+
* recvLargeutil
+
* recvMediumutil
+
* recvSmallutil
+
* recvTinyutil
+
 
+
;FCAdapter
+
* control_requests
+
* input_bytes
+
* input_requests
+
* output_requests
+
* output_bytes
+
* output_requests
+
 
+
;HDisk
+
* b_written
+
* b_read
+
* policies_algorithm
+
* policies_reserve_policy
+
 
+
<br clear=all>
+
 
+
=== Known Issues ===
+
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.
+
  
=== Limitations ===
+
2.0.1
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.
+
* Fix handling of locales that use comma for decimals. (ZEN-16506)
 +
* Fix inability to discover DB2 databases on AIX servers. (ZEN-17193)
  
=== Changes ===
 
 
2.0.0
 
2.0.0
* Support Aix 7.1
+
* AIX 7.1 Support
* Aix SS CPU data inaccurate (ZEN-8637)
+
* AIX SS CPU data inaccurate (ZEN-8637)
* Aix Parser Broken (ZEN-15092)
+
* AIX Parser Broken (ZEN-15092)
 
* Graphs returning Nan (ZEN-15099, ZEN-15157, ZEN-15199)
 
* Graphs returning Nan (ZEN-15099, ZEN-15157, ZEN-15199)
 
* Unable to gather some memory metrics (ZEN-15139)
 
* Unable to gather some memory metrics (ZEN-15139)
Line 372: Line 390:
 
* Some components missing during upgrade (ZEN-15193)
 
* Some components missing during upgrade (ZEN-15193)
 
* Traceback during installation (ZEN-15166)
 
* Traceback during installation (ZEN-15166)
 
 
{| class="wikitable"
 
!width="50%"|Type
 
!width="50%"|Name
 
|-
 
|Modeler
 
|<span class="keyword cmdname">zenmodeler</span>
 
|-
 
|Performance Collector
 
|<span class="keyword cmdname">zencommand</span>
 
|}
 
 
{{ZenPackFooter}}
 
{{ZenPackFooter}}

Latest revision as of 16:23, 7 September 2016


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.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.AixMonitor


Applications Monitored: 



AIX ZenPack

The AIX Monitor ZenPack enables Resource Manager to use Secure Shell (SSH) to monitor AIX hosts.

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 2.2.2- Download
Released on 2016/08/30
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
Version 2.0.1- Download
Released on 2015/04/02
Compatible with Zenoss Resource Manager 4.2.x, Zenoss Resource Manager 5.0.x

Background

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.

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)
  • LPP and RPM information (such as installed software)

Discovery

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.

Server (Device)
Attributes: ent_cpu, ent_vproc, active_cpu, systemId, prof_max_mem, ent_mem
EntAdapter
Attributes: devname, location, parent, physloc
FCAdapter
Attributes: devname, location, parent, physloc
HDisk
Attributes: devname, location, parent, physloc

Performance Monitoring

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

  • Default OS performance Metrics
Device
  • ssCpuIdle
  • ssCpuSystem
  • ssCpuUser
  • ssCpuWait
  • ssRawContexts
  • ssRawInterrupts
  • io_read
  • io_written
  • hrMemorySize
  • memAvailReal
  • percentMemUsed
  • swap_percentUsed
  • sysUptime
  • laLoadInt1
  • laLoadInt5
  • laLoadInt15
EntAdapter
  • receive_bytes
  • receive_packets_dropped
  • transmit_bytes
  • transmit_packets_dropped
  • recvHugeutil
  • recvLargeutil
  • recvMediumutil
  • recvSmallutil
  • recvTinyutil
FCAdapter
  • control_requests
  • input_bytes
  • input_requests
  • output_requests
  • output_bytes
  • output_requests
HDisk
  • b_written
  • b_read
  • policies_algorithm
  • policies_reserve_policy


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.

File:Aix-impact-yuml.png
IBM and Power Server Impact Relationship Diagram
Internal Impact Relationships
  • Ethernet Adapter impacts related Device (LPAR)
  • Fibre Channel Adapter impacts related Device (LPAR)
  • HDisk Drive impacts related Device (LPAR)


Usage

Note: If using a distributed collector setup, SSH requires firewall access (default of port 22) from the collector to the monitored server.

Set AIX Server Monitoring Credentials

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.

  1. Navigate to the device class or device.
    • If applying changes to a device class:
      1. Select the class in the devices hierarchy.
      2. Click Details.
      3. Select Configuration Properties.
    • If applying changes to a device:
      1. Click the device in the device list.
      2. Select Configuration Properties.
  2. Verify the credentials for the service account to access the service.
    AIX Configuration Properties
    Name Description
    zCommandUsername AIX user with privileges to gather performance information
    zCommandPassword Password for the AIX user
  3. Click Save to save your changes.

Add an AIX Server

The following procedure assumes that the credentials have been set.

  1. From Infrastructure > Devices, select Add a Single Device.
  2. Enter the following information in the dialog:
    Adding AIX Device Information
    Name Description
    Name or IP AIX host to model
    Device Class /Server/SSH/AIX
    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.
  3. Click Add Device to add the device.

Troubleshooting

This ZenPack requires the following collector process to be running.

Type Name
Modeler zenmodeler
Performance Collector zencommand

IBM_PowerVM Device Class

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.

Resolving CHANNEL_OPEN_FAILURE Issues

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.

  1. Navigate to the device or device class in the Zenoss platform interface.
    • If applying changes to a device class:
      1. Select the class in the devices hierarchy.
      2. Click Details.
      3. Select Configuration Properties.
    • If applying changes to a device:
      1. Click the device in the device list.
      2. Select Configuration Properties.
  2. Apply an appropriate value for the maximum number of sessions.
    Concurrent SSH Configuration Properties
    Name Description
    zSshConcurrentSessions Maximum number of sessions supported by the remote device's MAX_SESSIONS parameter. Common values for AIX are 2 or 10.
  3. Click Save to save your changes.

Resolving Timeout Issues

The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show messages stating:

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.

  1. Navigate to the device or device class in the Zenoss platform interface.
    • If applying changes to a device class:
      1. Select the class in the devices hierarchy.
      2. Click Details.
      3. Select Configuration Properties.
    • If applying changes to a device:
      1. Click the device in the device list.
      2. Select Configuration Properties.
  2. Apply an appropriate value for the command timeout.
    SSH Timeout Configuration Properties
    Name Description
    zCommandCommandTimeout The number of seconds to wait for commands to complete on the remote device.
  3. Click Save to save your changes.

Known Issues

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.


Limitations

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.

Changes

2.2.2

  • Make event class /Status/OSProcess for process monitoring (ZEN-21999)
  • Add zCredentialsZProperties: zCommandUsername & zCommandPassword
  • Add mem__pct and fs__pct datapoint aliases (ZEN-24619)

2.2.1

  • Updated zenpacklib.py to address modeler timeouts from attribute-indexed components

2.2.0

  • Fix excessive remote command execution (ZEN-16740)
  • IP Service modeling no longer ignoring zIpServiceMapMaxPort (ZEN-17360)
  • Fix incorrect ssCpuIdle alias for multi-core systems (ZEN-17360)
  • Fix handling of European date formats (ZEN-19089)
  • Fix incorrect template bindings (ZEN-20078)
  • Fix incorrect modeling time (ZEN-22127)
  • Add/revise custom component icons, fix icon positioning (ZEN-22191, ZEN-22294)
  • Fix missing Impact YAML file (ZEN-22250)
  • Fixed missing graph datapoints (ZEN-22259)

2.0.1

  • Fix handling of locales that use comma for decimals. (ZEN-16506)
  • Fix inability to discover DB2 databases on AIX servers. (ZEN-17193)

2.0.0

  • AIX 7.1 Support
  • AIX SS CPU data inaccurate (ZEN-8637)
  • AIX Parser Broken (ZEN-15092)
  • Graphs returning Nan (ZEN-15099, ZEN-15157, ZEN-15199)
  • Unable to gather some memory metrics (ZEN-15139)
  • Added Impact Adapters (ZEN-15153)
  • Rename Components (ZEN-15155)
  • Disk Drive Components returning wrong data (ZEN-15159)
  • Add graph legends (ZEN-15162)
  • Installation Traceback (ZEN-15166)
  • Supply Missing Template (ZEN-15180)
  • Some components missing during upgrade (ZEN-15193)
  • Traceback during installation (ZEN-15166)

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


Discuss

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

blog comments powered by Disqus