Updating a monitoring agent

When a new version of a distributed monitoring agent is released, you can apply the new version locally or remotely to one managed system at a time, or to many simultaneously. Use the Configure Managed System window to apply the update.
Note: Agent updates are automatic and this procedure is not required if your monitoring agent is at Version 6.2.3 or higher unless the self-describing capability is disabled.

Before you begin

A patch is for a specific version of the agent. The prereq field of the depot entry contains an agent of the same type as the agent itself. For example, if 6.1 UD (DB2 monitoring) is the selected agent, the prereq field in the depot entry must contain a deployment bundle notation such as ud:061000000.

You cannot upgrade an agent to a new version with this procedure, but rather with the tacmd upgradeAgent command. Do not try to change the configuration of a managed system at this time because your changes will be lost when the installation of the updates begins.

To use this feature, your user ID must have Manage permission for Agent Management.

Procedure

  1. Right-click the Agent level Navigator item Navigator item for the agent that you want to upgrade.
  2. Click configureConfigure to open the Configure Managed System window.
  3. Click the Agent tab.
  4. Compare the installed version of the monitoring agent with any available product updates, then highlight the row of the agent to update and click Install Updates.

Results

Installation of the updates begins and might take several minutes to complete. The list that displays reflects the contents of the deployment depot. If Install Updates is disabled, one or more of the following conditions exist:
  • The depot entry does not match the product type.
  • The VVRR fields for the agent and the depot entry are the same, where VV is the version number and RR is the revision number. For example, an entry of 0610 prevents you from applying a fix pack intended for a Version 6.2 agent.
  • The depot entry is at an older version than the agent.
  • The host version field of the depot entry does not contain the host platform for the agent.
  • The prereq field of the depot entry does not contain an agent of the same type as the agent itself. For example, if 6.1 UD (DB2 monitoring) is the selected agent, the prereq field in the depot entry must contain a deployment bundle notation such as ud:061000000, which is one way to denote a patch deployment bundle.