IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agentless OS Monitor User's Guides > Agentless Monitoring for Windows User's Guide > Troubleshooting > Trace logging > RAS trace parameters IBM Tivoli Monitoring, Version 6.3


Manually setting RAS trace parameters

You can manually edit the RAS1 trace logging parameters.


The Agentless Monitor for Windows uses RAS1 tracing and generates the logs described in Table 1. The default RAS1 trace level is ERROR.


Procedure

  1. Open the trace options file:

    • Windows systems:

      install_dir\tmaitm6\KR2ENV_instance name

    • UNIX systems:

      install_dir /config/r2_instance name.config

  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:kr2 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 specific program. When this value is exceeded, the oldest log files are discarded. The default value is 9.

    • LIMIT: The maximum size, in megabytes (MB) of a RAS1 log file. The default value is 5.

    • IBM Software Support might guide you to modify the following parameters:

      • COUNT: The number of log files to keep in the rolling cycle of one program startup. The default is 3.

      • PRESERVE: The number of files that are not to be reused in the rolling cycle of one program startup. The default value is 1.

      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.


What to do next

Monitor the size of the logs directory. Default behavior can generate a total of 45 - 60 MB for each agent that is running on a computer. For example, each database instance that you monitor can generate 45 - 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 1 that include a process ID number (PID).

Use collector trace logs as an additional source of troubleshooting information.

The KDC_DEBUG setting and the Maximum error tracing setting can generate a large amount of trace logging. Use these settings only temporarily while you are troubleshooting problems. Otherwise, the logs can occupy excessive amounts of hard disk space.


Parent topic:

RAS trace parameters

+

Search Tips   |   Advanced Search