Default System Log Settings
Table 4 summarizes the default system log settings that apply to all platforms that run the Junos OS, and specifies which statement to include in the configuration to override the default value.
Table 4: Default System Logging Settings
| Setting | Default | Overriding Statement | Instructions |
|---|---|---|---|
Alternative facility for message forwarded to a remote machine | For change-log: local6 For conflict-log: local5 For dfc: local1 For firewall: local3 For interactive-commands: local7 For pfe: local4 | [edit system syslog]
host hostname {
facility-override facility;
} | |
Format of messages logged to a file | Standard Junos format, based on UNIX format | [edit system syslog]
file filename {
structured-data;
} | |
Maximum number of files in the archived set | 10 | [edit system syslog]
archive {
files number;
}
file filename {
archive {
files number ;
}
} | |
Maximum size of log file | J Series: 128 kilobytes (KB) M Series, MX Series, and T Series: 1 megabyte (MB) TX Matrix: 10 MB | [edit system syslog]
archive {
size size;
}
file filename {
archive {
size size;
}
} | |
Timestamp format | Month, date, hour, minute, second For example: Aug 21 12:36:30 | [edit system syslog] time-format format; | |
Users who can read log files | root user and users with the Junos maintenance permission | [edit system syslog]
archive {
world-readable;
}
file filename {
archive {
world-readable;
}
} |
In addition, the following messages are generated by default on specific platforms. To view either type of message, you must configure at least one destination for messages as described in Minimum System Logging Configuration.
- On J Series platforms, a message is logged when a process
running in the kernel consumes 500 or more consecutive milliseconds
of CPU time.
To log the message on an M Series, MX Series, or T Series platform, include the kernel info statement at the appropriate hierarchy level:
[edit system syslog] (console | file filename | host destination | user username) { kernel info; } - The master Routing Engine on each T640 routing node in
a routing matrix forwards to the master Routing Engine on the TX Matrix
platform all messages with a severity of info and higher.
This is equivalent to the following configuration statement included
on the TX Matrix platform:
[edit system syslog] host scc-master { any info; }
Hide Navigation Pane
Show Navigation Pane
Download
SHA1