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

Starting the RADIUS Process and Separate Session Database Process

During startup of the standalone SBR, the SBRD script reads the StandaloneMode parameter in the sbrd.conf file. If the parameter is set as local, the CST is hosted within the RADIUS process. If the StandaloneMode parameter is set as cstserver, the separate session database process is started.

Note:

  • You can set the StandaloneMode parameter to local only if you have set the PersistSessions parameter in the radius.ini file as 1 (local) or 0 (none). Also, you can set the StandaloneMode parameter to cstserver only if you have set the PersistSessions parameter to 3 (cstserver).
  • In a 64-bit Linux machine, the separate session database process should be disabled (that is, the Enable parameter in the dbclusterRPC.gen should be set to 0) when you manually place SBR Carrier into single-process accounting mode from dual-process accounting mode. For more information about the StandaloneMode and PersistSessions parameters, see Steel-Belted Radius Carrier Reference Guide.

If the separate session database process is not started due to any failure, the RADIUS process waits and retries establishing remote procedure call (RPC) communication on the basis of the value set in the NumberofRetries parameter in the dbclusterRPC.gen file. If the RPC communication succeeds, the RADIUS process is continued.

If the retry attempts expire, the RADIUS process may default to use the standalone SBR internal session database on the basis of the value configured for the FallbackLocal parameter in the radius.ini file. If the FallbackLocal parameter is set to true, the RADIUS process tries to persist the SSR cluster in local mode. If the FallbackLocal parameter is set to false, the RADIUS process is stopped and the error is indicated through SNMP traps and logging messages.

Session restoration happens asynchronously if the CSTRestorationBlock parameter is set to 0, enabling SBR Carrier to start up without waiting for the session restoration process to complete. If the CSTRestorationBlock parameter is set to 1, session restoration happens synchronously. This setting causes SBR Carrier to wait until all sessions are restored before processing RADIUS transactions. The time required to complete startup depends on the size of the radadscst.hst file.

After the successful startup of the separate session database process, the RPC server service is started and the separate session database process is changed to active state. The separate session database process listens for the timeout duration as specified in the StartupListenTimeout parameter of the cstserver.ini file for any incoming RPC messages. If no messages are received within this predefined timeout, the separate session database process is gracefully stopped.

Modified: 2017-03-07