Discussion

Some are the same as those used by the Unix syslog utility, and some are specific to
the JUNOS software.
Table 5-1. JUNOS system log facilities
Facility name Facility code Message source
any — Any facility
authorization AUTH, AUTHPRIV Authentication and authorization attempts
change-log CHANGE Router configuration changes
conflict-log CONFLICT Router configuration changes that are inconsistent with the
router hardware
CONSOLE
Kernel messages to the console (/dev/console)
CRON
Scheduled processes
daemon DAEMON JUNOS software processes
firewall FIREWALL Packet filtering done by firewall filters
ftp FTP FTP
interactive-commands INTERACT Commands issued at the JUNOS CLI or by a JUNOScript client
application
kernel KERNEL JUNOS kernel
NTP
NTP
pfe PFE Packet forwarding software
SYSLOG
System logging
user USER User processes
Each system log message has a severity level (see Table 5-2) that reflects the seriousness
of the event that generates the message. Each severity level has a name and
number, which are the same as those used by the Unix syslog utility. The lower the
number, the more critical the event.
Table 5-2. JUNOS system log severity levels
Severity name Severity number Description
any — All severity levels
none — No severity levels
debug 7 Information normally used in debugging
info 6 Informational events about normal router operations
notice 5 Conditions that are not errors but are of more interest than normal router events
warning 4 General warnings for events you might want to keep an eye on
error 3 General error conditions
critical 2 Critical errors, such as hard drive failures
alert 1 Errors that require immediate correction, such as corrupted system files
emergency 0 Conditions that cause the router to stop functioning
This is the Title of the Book, eMatter Edition
Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.
Introduction | 163