Tracing Diameter Base Protocol Processes for Subscriber Access
The Junos OS trace feature tracks Diameter base protocol 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 jdiameterd. 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 specify the number of trace files to be from 2 through 1000. You can also configure the maximum file size to be from 10 KB through 1 gigabyte (GB). For more information about how log files are created, see the System Log Explorer.
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 Diameter base protocol tracing operations:
- (Optional) Configure a trace log filename.
- (Optional) Configure the number and size of trace logs.
- (Optional) Configure user access to trace logs.
- (Optional) Configure a regular expression to filter the information to be included in the trace log.
- (Optional) Configure flags to specify which events are logged.
- (Optional) Configure a severity level for messages to specify which event messages are logged.