Step 1: Log Messages to a Local Log File

Action

To log messages to a local log file on the router, follow these steps:

1. In configuration mode, go to the following hierarchy level:

[edit]

user@host# edit system syslog 

2. Configure the file, facility, and level:

user@host# set file filename facility level

For example:

[edit system syslog] 

user@host# set file security authorization info

3. Verify the configuration:

user@host# show

For example:

[edit system syslog] 

user@host# show

file security

authorization info

4. Commit the configuration:

user@host# commit

Table 49 lists the JUNOS system logging facilities. Each message is assigned to a facility, which is a group of messages that are either generated by the same software process or concern a similar condition or activity (such as authentication attempts).

Table 49: JUNOS System Logging Facilities

Facility	Type of Event or Error
any	Any (includes messages from all facilities).
authorization	Authentication and authorization attempts.
change-log	Change to the JUNOS configuration.
conflict-log	Configuration that is inconsistent with router hardware.
cron	Actions performed or errors encountered by the cron process.
daemon	Actions performed or errors encountered by various system processes.
firewall	Packet filtering actions performed by a firewall filter.
interactive-commands	Commands issued at the JUNOS command-line interface (CLI) operational mode prompt.
kernel	Actions performed or errors encountered by the JUNOS kernel.
pfe	Actions performed or errors encountered by the Packet Forwarding Engine.
user	Actions performed or errors encountered by various user-space processes.

Table 50 lists the system log message severity levels supported by the JUNOS software. Each message is assigned a severity level, which indicates how seriously it affects router functioning.

Table 50: System Log Message Severity Levels

Severity Level	Description
emergency	System panic or other condition that causes the router to stop functioning.
alert	Conditions that require immediate correction, such as a corrupted system database.
critical	Critical conditions, such as hard drive errors.
error	Error conditions that generally have less serious consequences than errors at the emergency, alert, and critical levels.
warning	Conditions that warrant monitoring.
notice	Conditions that are not errors but might warrant special handling.
info	Events or nonerror conditions of interest.
debug	Software debugging messages. Specify this level only when directed by a technical support representative.