Diagnosis with the Management Console

You can configure logging and traces for the IBM Communications Server and evaluate and display message logs and trace files using the Management Console.

Configuring logging and traces

Select a communication service under the item Communications Services in the navigation tree or in Communication Service in the proxy's navigation tree and then choose Edit Properties in the communication services (in this case IBM Communications Server for Linux) context menu. The table Edit Properties of Communication Service Instance lists the defined values which you are now able to edit.

Check the appropriate options to activate or deactivate logging and traces. Additionally you can switch on more detailed versions of audit logging (with the Verbose Audits option) and of problem and exception logging (with the Verbose Errors option).

If the IBM Communications Server is running, the change comes into effect when you save the Communication Service.

Evaluating logging and traces

The IBM Communications Server writes the following files to the directory /var/opt/ibm/sna/:

• Audit messages to the logging file sna.aud.

• Error messages (problem and exception logging) to the logging file sna.err.

• Line traces in binary form to the trace files sna1.trc and sna2.trc.

To display these files, choose the following nodes in the navigation tree of the proxy: Advanced Features - Diagnosis - Output - General Diagnostic Info. In the table, select one of the entries Communications Server (Linux) Audit Log, Communications Server (Linux) Error Log or Communications Server (Linux) Line Trace. Then click the Show File button.

The Management Console converts a selected trace file to a text file and transfers the converted text file or the message log file to the local diagnostic path and displays the file in a Text File panel.

For detailed information, please refer to the IBM Communications Server documentation.