Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

OSS trace

The function logs activities in the proxy container relating to OSI-TP connections to the UTM partner application or to the openUTM-LU62 Gateway.

By default the OSS trace is deactivated. To activate the OSS trace of the proxy container in the Management Console:

  1. Select the following nodes in the navigation tree of the proxy:
    Advanced Features - Diagnosis - Configuration - General Diagnostic Info
    .

    The General tab of the General Diagnostic Info Configuration panel is displayed.

  2. Select the option Activate OSS Trace.

If the proxy container is running, the change comes into effect dynamically when saving the proxy. If the proxy container is not running, the change comes to effect when the proxy is next started.

The traces are written in a binary format to OSST.* files in the proxy container home directory. You can evaluate and display the trace information:

  • In the Management Console, choose the nodes
    Advanced Features - Diagnosis - Output - General Diagnostic Info
    in the navigation tree of the proxy and select the item Container OSS Traces. Then click the Show File button.

    The Management Console transfers the converted text file osstrac.txt to the local diagnostic path of the proxy (default: diag/<proxy_cont_name> in the Management Console home directory) and displays the file in a Text File panel.

  • On Solaris and Linux systems, change to the proxy container home directory and call the script as follows:

    shsc/ositrace.sh

    The traces produced are then written to the osstrac.txt file in the proxy container home directory and displayed in the system's default editor.

  • On Windows systems, change to the proxy container home directory and call the script as follows:

    shsc\ositrace.cmd

    The traces produced are then written to the osstrac.txt file in the proxy container home directory and displayed in the system's default editor.

For further diagnosis, you have to send the evaluated trace to the diagnostic system service.