Previous Topic: NBA Policy Copied to a Text FileNext Topic: Collect Diagnostic Data


Log Files

You configure logging operations by editing the tags in nbapolicy.xml, especially the <loglevel> tag. These tags determine the default level of logging for the packet capture process, plus logging levels for individual filters.

NBA log files are written to the \log, \log\err, and \log\out folders on the NBA. The .log and .txt files are useful in diagnosis of configuration and system problems. The .err and .out files provide diagnostic information for CA support staff.

The NBA maintains the following log files:

Activity log files

These are generated by the NBA service, with separate log files generated for each CPU on the NBA.

They record startup messages and errors, operation messages, and configuration changes recorded in nbaconfig.xml or nbapolicy.xml. For example, if the NBA goes offline, or if its operating mode is changed from active to passive, these details are recorded in the activity log files. The logging level is configurable through the <loglevel> tag in nbapolicy.xml.

Activity log files use this name format:

<n>logMSG<date>.log

Where <n> identifies the CPU and <date> is the date and time when the log file was created.

Agent Management log files

These are generated by the NBA Management Application service, which always runs on CPU-X.

They mainly record NBA policy changes written to nbapolicy.xml. For example, if a network or application filter is amended, this change is recorded in the agent management log file. The logging level is configurable through the <loglevel> tags in nbapolicy.xml.

The log files use this name format:

<n>logAMM<date>.log

Where <n> and <date> are as described above.

Statistics log files

These contain statistics about packet processing. Data is organized in a tabular layout. The log files use this name format:

<n>logstats<date>.log

Where <n> and <date> are as described above.

Stderr log files

These are written to the \log\err subfolder during startup of the NBA service and the NBA Management Application service respectively. The files contain error information and use these name formats:

<n><app><date>.err

Where <n> and <date> are as described above and <app> is the name of the NBA application that wrote the file.

Stdout log files

These are written to the \log\out subfolder during startup of the NBA service and the NBA Management Application service respectively. The files contain startup progress messages.

<n><app><date>.err

Where <n>, <date>, and <app> are as described above.