IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Maintaining monitoring agents
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Clear the Deployment Status table
Each time you issue an tacmd command or use the Tivoli Enterprise Portal navigator to remotely manage a Tivoli Enterprise Monitoring Agent, information about the transaction is preserved in the Tivoli Enterprise Monitoring Server Deployment Status table. To make it easier to manage the contents of this table, especially in large environments, you can schedule the periodic removal of completed transactions from the table.
Enable this feature to review completed deployment transactions at opportune times and reduce the amount of monitoring server overhead by maintaining a modest table size. To schedule periodic clearing of completed transactions from the Deployment Status table, you need to specify how often you want the clearing to occur.
This feature is controlled by the monitoring server CLEARDEPLOYSTATUSFREQ=X environment variable, where X is the number of hours between the automated clearing of the table. If X is zero (0) or if the environment variable is not specified, automatic clearing is disabled. Valid values include 0 - 720.
You can enable the feature in two ways:
- Add the environment variable to the monitoring server configuration file directly, so that the server enables automated clearing at startup.
- Set the environment variable on an already running monitoring server using the IBM Tivoli Monitoring Service Console.
When automated clearing is enabled, the monitoring server automatically finds completed deployment transactions, removes them from the Deployment Status table, and then records the information about the deleted transaction in a log file for examination by the user at a later time. The automated clearing runs at the hourly interval that you specify when setting the environment variable.
Procedure
- Modify the monitoring server environment file
- Open the environment file on the computer where the monitoring server is installed:
- Use Manage Tivoli Enterprise Monitoring Services (Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Enterprise Monitoring Services). Right-click Tivoli Enterprise Monitoring Server and click Advanced → Edit ENV File.
- Change to the install_dir/config directory and open the <hostname>_ms_<temsname>.config and ms.ini files in a text editor.
- Add the environment variable, specifying your hourly interval. For example: CLEARDEPLOYSTATUSFREQ=1.
- Save the file.
- Recycle the monitoring server to implement the changes.
- Modify the monitoring server environment file using the IBM Tivoli Monitoring Service Console
See "Using the IBM Tivoli Monitoring Service Console" in the Troubleshooting Guide for detailed information.
- Open a web browser to http://hostname:1920, where hostname is the host name or IP address of the system where the monitoring server is running. The utility then displays with information about the components that are currently running on this system.
- Select the ms link to modify the environment variable.
- Enter your user ID and passwords.
- Enter the BSS1 SET CLEARDEPLOYSTATUSFREQ=1 command, where 1 is your hourly interval.
Results
The log file cleardeploystatus.log in the monitoring server logs subdirectory (install_dir/logs for Linux and UNIX or install_dir\logs for Windows) contains a text line for each Deployment Status table transaction that is cleared. Each time the monitoring server is started, it logs ---Clear Deploy Status Log--- in the log file.Each transaction that is cleared from the table has the following information written to the log file:
- Transaction ID: Global transaction identifier of the transaction that completed.
- Submitted: Timestamp that the transaction was initially submitted for processing.
- Command: The deployment command processed.
- Status: The completion status (SUCCESS or FAILURE).
- Retries: The number of times the transaction was tried before it completed.
- Monitoring server name: The name of the monitoring server responsible for processing the transaction.
- Target host name: The managed system name or managed node identifier where the command was completed.
- Platform: The reported platform architecture of the OS agent executing on the target.
- Product: The product code of the agent for which the transaction was processed.
- Version: The version of the product for which the transaction was attempted.
- Completion message: If the status returned is a failure, an explanation of the reason for the failure.
What to do next
You can change the location of the log file where the monitoring server records the transactions which are cleared from the Deployment Status table, by adding the environment variable CLEARLOG to the monitoring server configuration file specifying a fully qualified path name on the local system, or any fully qualified path name on a mounted file system.Use a mounted file system is useful when there is a monitoring server and a server backup. By using a mounted file system as the destination, the logs for both systems can be set to the same fully qualified path name to accommodate failover conditions.
The acting hub monitoring server performs the automated cleansing of the Deployment Status table for the entire enterprise. If you have a backup monitoring server for the hub, then also set the environment variable on the backup to the same value as specified on the hub so that the clearing process occurs at the same time in the event of a hub failover.
Parent topic:
Maintaining monitoring agents