Setting RAS trace parameters

Objective

Pinpoint a problem by setting detailed tracing of individual components of the monitoring agent and modules.

Background Information

The Blue Medora Agent for Symantec Endpoint Protection uses RAS1 tracing and generates the logs described in Table 2. The default RAS1 trace level is ERROR.

Before you begin

See Overview of log file management to ensure that you understand log rolling and can reference the correct log files when you manage log file generation.

After you finish

Monitor the size of the logs directory. Default behavior can generate a total of 45 to 60 MB for each agent that is running on a computer. For example, each database instance that you monitor can generate 45 to 60 MB of log data. See the "Procedure" section to learn how to adjust file size and numbers of log files to prevent logging activity from occupying too much disk space.

Regularly prune log files other than the RAS1 log files in the logs directory. Unlike the RAS1 log files that are pruned automatically, other log types can grow indefinitely, for example, the logs in Table 2 that include a process ID number (PID).

Consider using collector trace logs as an additional source of troubleshooting information.

Procedure

On Windows systems, you can use the graphical user interface to set trace options:

1. Open the Manage Tivoli Enterprise Monitoring Services window.
2. Right-click the icon of the monitoring agent whose logging you want to modify.
3. Select Advanced > Edit Trace Parms. The Tivoli Enterprise Monitoring Server Trace Parameters window is displayed.
4. Select a new trace setting in the pull-down menu in the Enter RAS1 Filters field or type a valid string.

   The selections are as follows:

   • General error tracing. KBB_RAS1=ERROR
   • Intensive error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL)
   • Maximum error tracing. KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)
     Notes:
     As this example shows, you can set multiple RAS tracing options in a single statement.
5. Modify the value for 'Maximum Log Size Per File (MB)" to change the log file size (changes LIMIT value).
6. Modify the value for 'Maximum Number of Log Files Per Session" to change the number of log files per startup of a program (changes COUNT value).
7. Modify the value for 'Maximum Number of Log Files Total" to change the number of log files for all startups of a program (changes MAXFILES value).
8. (Optional) Click Y (Yes) in the KDC_DEBUG Setting menu to log information that can help you diagnose communications and connectivity problems between the monitoring agent and the monitoring server.
   Note:
   The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use them only temporarily, while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.
9. Click OK. You see a message reporting a restart of the monitoring agent so that your changes take effect.

You can also manually edit the RAS1 trace logging parameters using this method:

1. Open the trace options file:

   Windows: install_dir\tmaitm6\KB2ENV

2. Edit the line that begins with KBB_RAS1= to set trace logging preferences. For example, if you want detailed trace logging, set the Maximum Tracing option:KBB_RAS1=ERROR (UNIT:kqz ALL) (UNIT:kra ALL)
3. Edit the line that begins with KBB_RAS1_LOG= to manage the generation of log files:
   • MAXFILES: the total number of files that are to be kept for all startups of a given program. When this value is exceeded, the oldest log files are discarded. Default value is 9.
   • LIMIT: the maximum size, in megabytes (MB) of a RAS1 log file. Default value is 5.
   Notes:
   The KBB_RAS1_LOG parameter also provides for the specification of the log file directory, log file name, and the inventory control file directory and name. Do not modify these values or log information can be lost.
4. Restart the monitoring agent so that your changes take effect.