Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Separate Session Database Process Overview

In the standalone version of SBR, the Current Sessions Table (CST) may be hosted as a separate executable process, called the separate session database process, instead of being hosted as a shared library within the SBR core RADIUS process. The separate session database process is implemented as a 64-bit process, thereby enabling many more sessions to be hosted than the 32-bit RADIUS process. Both the RADIUS process and the separate session database process run in the same physical machine.

Note: Hosting CST as a separate process in the standalone SBR is supported only in the 64-bit Linux platform.

Logging Information of the Separate Session Database Process

The logging information of the separate session database process is stored in a separate log file. This log file is named with the convention <DATE+CSTSERVER.log>. Every midnight, the current file is closed and a new file is created for logging. If the size of the log file exceeds the configured maximum size before midnight, the current file is renamed <DATE+CSTSERVER_00001.log> and a new file is created as <DATE+CSTSERVER.log>.

Modified: 2017-09-27