The function logs all connection-oriented activities within the proxy container.
By default, the UTM-BCAM trace is deactivated. To activate the UTM-BCAM trace of the proxy container in the Management Console:
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.
Select the option Activate BCAM Trace. In addition, in the field BCAM Trace Length you can set the length up to which the trace information should be written.
If the proxy container is running, the change comes into effect dynamically when saving the proxy. If the proxy is not running, the change comes to effect when the proxy is next started.
The traces are written in a binary format to KDCBTRC.*
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 and select the item Container BCAM Traces. Then click the Show File button.
The Management Console transfers the converted text file
btrc.txt
to the local diagnostic path of the proxy
(default:diag/<proxy_cont_name>
in the Management Console home directory). The Management Console displays the file in a Text File panel.On Linux systems, change to the proxy container home directory and call the script as follows:
shsc/nettrace.sh
The traces produced are then written to the
btrc.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\nettrace.cmd
The traces produced are then written to the
btrc.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.