When the hub Tivoli Enterprise Monitoring Server is
configured for self-describing agent capability (by setting the variable
KMS_SDA=Y) and started, you can dynamically change the operational
state of the hub self-describing agent feature without recycling the
hub monitoring server.
It is the hub monitoring server that controls the self-describing
agent function for all remote monitoring servers and portal servers,
provided these components are started and with the self-describing
agent capability turned on. The following table describes the administration
commands to dynamically control the self-describing agent function
at the hub monitoring server:
Table 1. tacmd commands to control
the operational state of the hub self-describing agent functiontacmd Command |
Description |
tacmd suspendsda |
Disable (suspend) self-describing agent capability
without recycling the hub monitoring server. |
tacmd resumesda |
Enable (resume) self-describing agent capability
without recycling the hub monitoring server. |
tacmd listsdastatus |
Confirm if the self-describing agent capability
is enabled or disabled for each hub or remote Tivoli Enterprise Monitoring Server. |
For the full syntax, including parameter descriptions, see
the
IBM Tivoli Monitoring Command Reference.
You can issue the
tacmd suspendsda command if
you want to turn off the self-describing agent function during critical
monitoring periods. Once the maintenance period arrives, you can issue
the
tacmd resumesda command to allow any available
self-describing agents to upgrade server product support again, if
needed. When the self-describing agent function is changed from disabled
(suspend) to enabled (resume), the hub monitoring server ensures that
all running remote monitoring servers and all running self-describing
agent enabled agents are notified to retry their installation attempt.
If the notified agent product support is allowed to install via the
self-describing agent capability, and this version of its product
support files are not yet installed on the hub or remote monitoring
server, the self-describing agent installation takes place.
Note: - The tacmd commands suspendsda and resumesda work
only when the hub monitoring server is started and self-describing
agent capability is turned on by setting the variable KMS_SDA=Y. These
commands cannot turn on the self-describing agent function if the
self-describing agent capability configured is not configured (that
is, when KMS_SDA=N at the hub monitoring server). In this case, running
the commands has no effect and a warning is displayed.
- You cannot run the suspendsda and resumesda commands
against any remote monitoring server or Hot Standby (FTO) mirror hub
monitoring server. The self-describing agent enablement status of
the remote monitoring server is controlled only by the existing configuration
variable KMS_SDA on the hub monitoring server.
Complete the following steps to suspend and then resume the self-describing
agent capability without recycling the hub monitoring server:
- Enable the hub monitoring server for self-describing agent capability
by setting the variable KMS_SDA=Y and start the hub monitoring server.
The hub monitoring server is now enabled for self-describing agent
capability. Any products currently configured to allow self-describing
agents to install will take place if the agents are running.
- Issue the command tacmd suspendsda to dynamically
turn OFF the self-describing agent function for the hub monitoring
server. This command also turns off all self-describing agent capability
for all remote monitoring servers and portal servers.
- Issue the command tacmd resumesda to dynamically
turn ON the self-describing agent function for the hub monitoring
server. This command also turns on all self-describing agent capability
for all remote monitoring servers and portal servers.
- Issue the command tacmd listsdastatus to view
the self-describing agent enablement status of all Tivoli Enterprise Monitoring Servers
in the enterprise and to confirm that the enablement is complete.