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


Suspend the self-describing capability

You can suspend and resume the self-describing capability for your environment using the tacmd suspendSda and tacmd resumeSda commands without having to recycle the monitoring server. You can suspend the self-describing capability for various reasons such as, when modifying the self-describing installation options or when going into maintenance mode.

The tacmd suspendSda and tacmd resumeSda commands dynamically change the self-describing behavior only when the hub monitoring server is configured with KMS_SDA=Y. Issuing the tacmd suspendSda and tacmd resumeSda commands will not override the KMS_SDA=N setting. If the tacmd resumeSda command is issued when KMS_SDA=N, the command is ignored until KMS_SDA=Y.

Issuing either the tacmd suspendSda or tacmd resumeSda commands updates the TAPPLPROPS table. This setting is saved regardless of the KMS_SDA setting. Best practice is to set the hub monitoring server environment variable to KMS_SDA=Y, then run the tacmd suspendSda or tacmd resumeSda commands.

See the IBM Tivoli Monitoring Command Reference for complete syntax information.


Procedure


What to do next

You can run the tacmd listSdaStatus to view the suspend state of your monitoring servers. See Self-describing agent installation.


Parent topic:

Self-describing monitoring agents

Related tasks:

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 agent installation
Self-describing auto refresh and seeding


+

Search Tips   |   Advanced Search