Setting log files

You can manage recorded information through trace logs, message logs, and account logs.

On Linux, these files are in /var/adm/

On Windows, these files are in the installation directory under SafeLinx Server\logs\

To view or reset these files, an administrator must have at least Read-only ACL permission on the SafeLinx Server.

You should maintain your message, account, and trace logs regularly. Your business needs dictate whether you keep historical records as well as how often you start new records. For database records, this means archiving and purging records. To purge accounting and billing records, use the -p parameter with the wg_acct command.

At SafeLinx Server startup, logging information is appended to the existing file. You can reset the files at any time so that previous logging files are renamed to include the current date. If you reset the files more than once during a single day, the files are renamed to include the current date and time. You cannot reset the account log file if you are using a relational database for data storage.

To reset the files, from the Resources pane, right-click the SafeLinx Server on which you want to reset the files, then click Reset log files. You can choose to reset an individual file or all files. If you configured the SafeLinx Server to use a relational database for accounting and billing, resetting the account file has no effect.

Trace logging

You can log individual users' Wireless Link Protocol/PPP level of trace information. By default, tracing is turned off. To start tracing, make sure that you have SafeLinx Server ACL permission, then click Start trace on the Account tab of the user you want to trace.

To stop tracing, clear the Start trace check box.

Message Logging

To set the level of information that is logged in the message log file, click the Logging tab on a SafeLinx Server. When you click None, no messages are logged in the message log file. You can control the level of messages that are logged on a SafeLinx Server by selecting all log levels or none, or one or more log levels from:

Debug

Data used for problem analysis.

Error

Messages about unexpected events on which you must act on.

Log

General information messages.

Status

Dump of status information, such as packet rates, byte rates, and system load.

TCP-lite

Messages about data that uses the TCP-lite transport.

Trace-IP

Hexadecimal dump of only IP-related data packets.

Trace-data

Hexadecimal dump of data packets.

Warning

Messages about events on which you may need to take action.

You can set the maximum size of the message log file. Click the Logging tab on a SafeLinx Server, then enter the maximum size of the message log file in MB. When the maximum file size is reached, the file is renamed in the form wg.log.bak.

You can also specify the allowable number of backup files that are saved. Also on the Logging tab of a SafeLinx Server, enter the number of backup files that are allowed, up to a maximum of 10 files. If you specify zero, no files are backed up. When the maximum file size is reached, the file is truncated to 0 bytes, then logging continues at the beginning of the message log file.

Account logging

You can set the level of information that is logged, such as for an MNI or SMS client, in the account file, click the Accounting and billing tab on an MNI or messaging services. When you click None, no information is logged in the account file.

For SMS network traffic, you cannot set specific levels of logging; the default is that all levels of information are logged. For an MNI, you can control the level of account records that are logged by selecting all log levels or none, or one or more log levels from:

Login

Events that occur when SafeLinx Clients establish a connection to a SafeLinx Server.

Logout

Events that occur when SafeLinx Clients disconnect from a SafeLinx Server.

Connect

Events that occur when a SafeLinx Client negotiates a dial-up connection with a modem on the SafeLinx Server. On an initial dial-up session with the SafeLinx Server, the SafeLinx Client's physical connection is established, then login is established.

Disconnect

Events that occur when a dial-up connection is disconnected from a modem on the SafeLinx Server.

Packet

Data that records and accounts for each packet.

Session

Data that records the duration of a session from login to logout.

Hold

Data that records when SafeLinx Clients are in short-hold mode and physical connections are dropped, but login connections are maintained.

You can stop account logging on an individual MNI or for an entire SafeLinx Server. To stop account logging for an MNI, click the Accounting and billing tab on an MNI, then click None. To stop account logging for a SafeLinx Server, click the Account and billing tab on a SafeLinx Server, then click Write accounting and billing recoreds to the following.

When you clear the Write accounting and billing records to the following check box, you can still modify the relational database configuration or modify the path of the file.