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

Configuring the Log Retention Period

Each day at midnight, the previous day’s log files are completed, and new log files are created for the new day’s transactions. To prevent the log files from filling up available disk space, you can configure SBR Carrier to discard the log files after a specified number of days.

To configure the log retention period using the Web GUI:

  1. Select RADIUS Configuration > Reports > Settings.

    The Settings page (Figure 276) appears.

    Figure 276: Settings Page

    Settings Page
  2. Enter the number of days you want SBR Carrier to retain the log file in the Days to Keep Server Log File field.
  3. Click Save to save the setting.

Cluster Management Nodes

A cluster management node is a machine that hosts the SSR management process. It controls itself and all data nodes in the cluster. It provides configuration data, starts and stops nodes, backs up the database, and performs other database operations. It also manages a database process that supports the SSR storage engine. Cluster configuration data is located in an identical config.ini file on each node of the management cluster.

Cluster management logs are available in the following directory:

/opt/JNPRndb_mgmd/logs

To configure log retention for cluster management nodes:

  1. Log in to the SBR system.
  2. Open the config.ini file from the /opt/JNPRhadm path.
  3. Update the LogDestination option under the [ndb_mgmd] section to specify the maximum size of the log file in bytes and the number of logs to be preserved.

    Default value for LogDestination=ndb_node_id_cluster.log

    Default value for maxsize=1000000

    Default value for maxfiles=6

  4. When ndb_node_id_cluster.log reaches the configured maxsize, the existing log file name is incremented by the next highest available number and a new ndb_node_id_cluster.log is created.

    For example, when the ndb_node_id_cluster.log file reaches its maxsize, a new ndb_node_id_cluster.log file is created to record the logs and the previously recorded log file is incremented to ndb_node_id_cluster.log.1.

  5. Alternatively, specify LogDestination=SYSLOG:facility=local0 and configure the log file destination within syslog.conf. Log rotation at fixed intervals can be controlled by logrotate.d.

SSR Data Nodes

An SSR data node is machine that hosts the SSR data process. It runs the ndbd data process. The ndbd process cooperatively manages, replicates, and stores data in the SSR storage engine with other data nodes. Each data node has its own memory and permanent storage. Each one maintains both a portion of the working copy of the SSR database and a portion of one or more replicas of the database.

SSR data node logs are available in the following directory:

/opt/JNPRndbd/logs

To configure log retention for SSR data nodes:

  1. Log in to the SBR system.
  2. Open the config.ini file from the /opt/JNPRhadm path.
  3. Update the MaxNoOfSavedMessages option under the [ndbd] section to specify the number of trace files to be stored on the SSR data nodes.

    Default value for MaxNoOfSavedMessages=25

  4. When the configured limit is reached, the existing logs are overwritten.

Modified: 2017-09-27