PRIMECLUSTER Global Link Services Configuration and Administration Guide: Redundant Line Control Function 4.1 (for Solaris(TM) Operating System)

6.2.4 Precautions about driver trace function

An operator with the superuser privilege can execute the strotr, stpotr or prtotr commands.

Since the high load on the CPU under trace processing deteriorates performance, trace should be performed sparingly.

A log file is created in the /var/opt/FJSVhanet/otr directory. When specifying the maximum size for the log file with the -b option, be sure to check for available disk space beforehand.

Collecting trace data by running a file trace may lead to a loss of trace data, but this event is rare.

If an invalid option is specified in a command (strotr, stpotr and prtotr commands), only commands with valid options are processed, and commands with invalid options are ignored.

Notes on collecting a driver trace:

A driver trace overwrites the old information because not possible to collect the information exceeding the specified buffer size or memory size. Therefore, clarify the procedure of the occurrence of a phenomenon, and make the time to activate a driver trace as short as possible. The procedure to collect a driver trace is as follows:

1) To start a driver trace of a Redundant Line Control function

# /opt/FSUNnet/bin/strotr -k sha -m 256 -A

2) To execute the procedure of reproduction

(The procedure of reproduction)

3) To stop a driver trace of a Redundant Line Control function

# /opt/FSUNnet/bin/stpotr -k sha

4) To output a driver trace of a Redundant Line Control function

In the following example, the result of outputting is output to a /tmp/sha.otr file.

# /opt/FSUNnet/bin/prtotr -k sha > /tmp/sha.otr

When collecting a driver trace in file trace mode, stop unnecessary communication on a transfer route. When there are many pieces of the collecting information, occasionally not possible to trace.