IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Deploy monitoring agents across your environment > Bulk agent deployment
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Deploy status
Because deployment transactions are asynchronous (that is, they run in the background), monitoring the status of deployments is an important activity to ensure they complete successfully.
There are three mechanisms for monitoring deployment status, as follows.
- The tacmd getDeployStatus CLI command.
For more information about this command, see the Command Reference.
- The Tivoli Enterprise Portal's Deployment Status workspaces.
- Deployment attribute groups, and situations created using the Tivoli Enterprise Portal that are based on these groups.
Use these features, you can display and monitor the progress of deployments running in your environment. You can track the status of your deployments either by individual transaction or by group transaction. A group transaction represents a deployment using groups of agents deployed to groups of targets. Each transaction possesses a status that indicates the progress the transaction has made in the deployment process. The valid status values for a deployment transaction are listed below.
- Status
- Description
- Pending
- The transaction is waiting in the queue to begin processing.
- In-Progress
- The transaction has begun the deployment process but has not yet finished.
- Success
- The transaction has completed successfully.
- Failed Retrying
- The transaction experienced a recoverable error during the deployment process and will be restarted periodically at the point of failure for a predefined number of iterations. The number of retry iterations is defined by configurable property ERRORRETRYLIMIT. The time between each successive attempt is defined by the RETRYTIMEINTERVAL property. Both of these properties can be set in the monitoring server's configuration file, KBBENV, and take effect when the monitoring server is restarted. The default value for ERRORRETRYLIMIT is 3 retries, and the default value for RETRYTIMEINTERVAL is 7 minutes. These default values are based on a typical bulk deployment scenario using the createNode command. A smaller RETRYTIMEINTERVAL value (for example, 20 seconds) might be better suited if you perform more bulk upgrade scenarios than deployments.
If an error persists after all retry iterations are exhausted, the transaction moves to Failed status.
- Failed
- The transaction has completed with an unrecoverable failure, or the number of retry attempts has been exhausted. Consult the status message included with the transaction status for more information about the failure.
- Deployment Status workspaces
There are six workspaces related to bulk deployment. Three can be accessed directly from the workspaces menu of the Navigator tree's Enterprise item. The remaining three can be accessed by selecting links.
- Deployment attribute groups and situations
The hub Tivoli Enterprise Monitoring Server provides two attribute groups that you can use to monitor the status of bulk deployments within the IBM Tivoli Monitoring environment: Deploy Status and Deploy Summary.
Parent topic:
Bulk agent deployment