ITM Agent Insights: UNIX OS monitoring agent on AIX and merged attributes from AIX Premium agent
DougDoering 120000E6GG Visits (9195)
The UNIX OS agent - UX - has incorporated numerous attributes that were previously provided by the AIX Premium agent - PX - that was part of the System P package. If experiencing problems with a "merged" metric, it is important to understand that different subsets of the "PX" metrics were incorporated at different levels of UNIX OS agent. Depending on which attribute group is not able to be collected, the issue may be due to the version of the UX component on the endpoint (or the level of UX agent application support).
Starting with 6.23 Fixpack 1, the UNIX OS agent on AIX platforms added the following "PX" attributes:
Additional "PX" attributes were incorporated in the 6.3 release of the Monitoring Agent for UNIX OS.
Further "enhancement" of the UNIX OS agent on AIX added additional "PX" metrics at 6.3 Fixpack 2.
From the details of APAR IV61542, the following additional "PX" metrics were merged into the UX agent:
Since the various "PX" attributes were added at different levels, it is important as a first step to verify the environment where any problem is reported with these merged metrics to understand if the UNIX OS agent level is sufficient to gather the attribute group.
It is also important to know whether the issue impacts ALL of the merged "PX" metrics, or only specific attribute groups.
Problems with only some metrics point to issues with the version of the UX agent or its application support, or a specific attribute collection issue.
Problems with ALL of the merged "PX" metrics point to general issues with prerequisite levels of AIX, or the aixdp_daemon not running.
Confirm the installed UX version / release by review of "cinfo -i" output on the AIX endpoint (or review cinfo.info file from the output from pdcollect utility).
Also confirm the level of UX application support on the ITM infrastructure (TEMS / TEPS / TEPD).
After confirming the version / release of the UX component, confirm that the AIX operating system meets the minimum system requirements to provide the metrics.
A quick review of the UX agent's .LG0 file can confirm whether the system does not meet the OS requirement to provide the "PX" metrics:
Look for a "KUXMAA002" message in the <hostname>:KUX.LG0 file on the UX agent endpoint.
KUXMAA002 The AIX data provider requirements are not met. The aixdp_daemon process will not be started and all related AIX metrics will not be available
If there is no "KUXMAA002" message in the .LG0 file, confirm that the "aixdp_daemon" process is not disabled by review of the UX agent's .ini file.
If the ux.ini file contains KUX_AIXDP=false this will disable the data provider process that the merged "PX" metrics rely on.
If the aixdp_daemon is not intentionally disabled by UX configuration setting, check to confirm that the "aixdp_daemon" process is running by review of "ps -ef" at the OS, or by reviewing the contents of "tasklist.info" file from pdcollect ouptut.
If the "aixdp_daemon" process is not running, review the UX agent's <hos
Review the RAS1 tracing in the "aixdp_daemon" RAS1 log.
Resolving the overall problem being experienced depends on the nature of the problem.
Since different metrics were incorporated into the UX agent at different levels, it is important to rule out the version of the UX component as being cause simply due to the metric not being available in that version / release.
If the issue is not related to the level of the UX agent including the specific attribute group, make sure the OS meets requirements and that the aixdp_daemon is not intentionally disabled in ux.ini configuration file.
Ruling out the above, if there are still problems, it may require increased diagnostics to gather additional details to RAS1 logs for the attribute collection performed by the aixdp_daemon, or review of traceback / core if the aixdp_daemon is terminating. This usually requires involving Support through a problem ticket for troubleshooting assistance.
DCF 1644193 provides some useful information to understand if the aixdp_daemon data provider is having issues:
Additional ITM Agent Insights series of IBM Tivoli Monitoring Agent blogs are indexed under ITM
Subscribe and follow us for all the latest information directly on your social feeds: