IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Maintaining monitoring agents > Self-describing monitoring agents

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Self-describing agent installation

The local monitoring server application properties table (TAPPLPROPS) stores the results of the monitoring server self-describing agent product installations. This table includes the current detected version of manually installed monitoring server products. This table also stores self-describing information such as installation options, seed distribution, and suspend records. For more information about the TAPPLPROPS attributes, see the Application Property Installation attributes in the Tivoli Enterprise Portal User's Guide for more information.

You can use two different tacmd commands to check the self-describing status of your monitoring servers:


Use the tacmd listSdaStatus command

In IBM Tivoli Monitoring V6.3 or later, the tacmd listSdaStatus command displays the self-describing enablement status for a monitoring server. You can display the self-describing enablement status for a list of monitoring servers or for all monitoring servers, which is the default action. The operational state of the self-describing agent facility (suspended or active) for the hub monitoring server is also provided if the command is issued to an IBM Tivoli Monitoring V6.3 or later hub monitoring server. The self-describing operational state (suspended or active) of the hub determines the self-describing activity for all the monitoring servers that are attached to that hub monitoring server.

The self-describing enablement status is indicated by the values of HUB/RTEMS name, STATE, and STATUS.

In this example, a message states that the self-describing function is currently suspended. HUB_A and RTEMS_1 are both enabled for self-description. STATUS code 0 indicates self-describing is enabled. RTEMS_2 is not enabled for self-description and STATUS code 16 (SDA disabled because KMS_SDA=N) is provided as an explanation.

tacmd listSdaStatus
KUILSS203I: SDA functions are suspended.
HUB/RTEMS STATE STATUS
HUB_A ON 0
RTEMS_1 ON 0
RTEMS_2 OFF 16

For more information, examples, and descriptions of the tacmd listSdaStatus command STATUS codes, see the IBM Tivoli Monitoring Command Reference.


Use the tacmd listappinstallrecs command

Use the tacmd listappinstallrecs command to monitor the application support installation records.

The command returns the application support installation records and displays the current self-describing agent product installation status for all monitoring servers in the environment. Remember that this command is not available when the monitoring server is not running. If the monitoring server and the portal server are both started, you can also see self-describing agent information and settings in the Audit Logs workspace. See Audit logging.

The tacmd listappinstallrecs command displays the current self-describing agent product installation status for all monitoring servers in the environment.

HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS
HUB_LZ A4 06300000 5655 TMS 06300000 0
HUB_LZ HD 06300000 5655 TMS 06300000 Y IC 0
HUB_LZ HD 06300000 5655 TPW 06300000 IC 0
HUB_LZ LZ 06230000 5655 TPS 06230000 IC 0
HUB_LZ NT 06230000 5655 TMS 06230000 0
HUB_LZ TM 06230000 5655 TMS 06230000 0
HUB_LZ 11 06230000 5655 TMS 06230000 ME 1005
RTEMS_LZ A4 06230000 5655 TMS 06230000 0
RTEMS_LZ LZ 06230000 5655 TMS 06230000 Y IC 0
RTEMS_LZ R6 06230000 5655 TMS 06230000 0
RTEMS_LZ 11 06230000 5655 TMS 06230000 Y ME 1014

The HUB/RTEMS column lists the node name of the monitoring server where the record was collected. Rows with IC in the STATE column stand for self-describing agent Install Complete. You can also see in this example that the hub monitoring server and the remote monitoring server both have an appinstallrecs entry for monitoring server support (TMS), but the hub monitoring server has two additional appinstallrecs entries for portal server support (TPS), and portal browser client support (TPW) packages. These additional packages are installed only on the hub monitoring server so they are available to the portal server.

If the STATE column is blank, application support was manually installed. A MANUALINST column shows Y if you use the -d (detail) option. The self-describing agent appinstallrecs states are as follows:

IR Install Request: New install request on the work queue.
IM Install Metadata: Retrieve the install request from the work queue and begin the metadata install and auto-refresh work.
MC Metadata Complete: Metadata install and auto-refresh has completed.
IC Install Complete: SDA application support has completed successfully.
ME Metadata Error: Metadata Installation Error. STATUS code provides additional information.

Tip: IR, IM, and MC appinstallrecords all indicate that normal self-describing agent installation is in progress. For information about application support installation records with a STATE value of ME, see Self-describing agent installation errors.

For detailed information about the tacmd listappinstallrecs command STATUS codes, see the IBM Tivoli Monitoring Command Reference.

In IBM Tivoli Monitoring V6.3 or later, the listappinstallrecs -t TEMS option is no longer supported. Use the listSdaStatus command instead.


Parent topic:

Self-describing monitoring agents

Related tasks:

Suspend the self-describing capability
Enable or disable the self-describing capability at the monitoring server
Enable or disable the self-describing capability at the agent
Determine if agents are enabled for self-description

Related reference:

Environment variables that control the self-describing capability

Related information:

Self-describing event flow at the monitoring server
Self-describing auto refresh and seeding

+

Search Tips   |   Advanced Search