Tracing Subscriber Management Session Database Replication Operations for Subscriber Access
The Junos OS trace feature tracks subscriber management database replication operations and records events in a log file. The error descriptions captured in the log file provide detailed information to help you solve problems.
By default, nothing is traced. When you enable the tracing operation, the default tracing behavior is as follows:
- Important events are logged in a file located in the /var/log directory. By default, the router uses the filename bdbrepd. You can specify a different filename, but you cannot change the directory in which trace files are located.
- When the trace log file filename reaches 128 kilobytes (KB), it is compressed and renamed filename.0.gz. Subsequent events are logged
in a new file called filename, until
it reaches capacity again. At this point, filename.0.gz is renamed filename.1.gz and filename is compressed and renamed filename.0.gz. This process repeats until
the number of archived files reaches the maximum file number. Then
the oldest trace file—the one with the highest number—is
overwritten.
You can optionally configure the maximum file size to be from 10 KB through 1 gigabyte (GB). You can also specify the number of trace files to be from 2 through 1000. (For more information about how log files are created, see the Junos OS System Log Messages Reference.)
By default, only the user who configures the tracing operation can access log files. You can optionally configure read-only access for all users.
To configure all aspects of subscriber management database replication tracing operations:
- Configure a trace log filename.
See Configuring the Subscriber Management Session Database Replication Trace Log Filename.
- Configure the number and size of trace logs.
See Configuring the Number and Size of Subscriber Management Session Database Replication Log Files.
- Configure user access to trace logs.
See Configuring Access to the Subscriber Management Session Database Replication Log File.
- Configure a regular expression to filter the information to be included in the trace log.
- Configure flags to specify which events are logged.
See Configuring the Subscriber Management Session Database Replication Tracing Flags.
