Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
System Log Facility Codes and Numerical Codes Reported in Priority Information
Table 1 lists the facility codes that can appear in system log messages and maps them to facility names.
 | Note: If the second column in Table 1 does not include the Junos facility name for a code, the facility cannot be included in a statement at the [edit system syslog] hierarchy level. The Junos OS might use the facilities in Table 1—and others that are not listed—when reporting on internal operations. |
Table 1: Facility Codes Reported in Priority Information
Code | Junos Facility Name | Type of Event or Error |
|---|---|---|
AUTH | authorization | Authentication and authorization attempts |
AUTHPRIV | Authentication and authorization attempts that can be viewed by superusers only | |
CHANGE | change-log | Changes to the Junos configuration |
CONFLICT | conflict-log | Specified configuration is invalid on the router type |
CONSOLE | Messages written to | |
CRON | Actions performed or errors encountered by the cron process | |
DAEMON | daemon | Actions performed or errors encountered by system processes |
DFC | dfc | Actions performed or errors encountered by the dynamic flow capture process |
FIREWALL | firewall | Packet filtering actions performed by a firewall filter |
FTP | ftp | Actions performed or errors encountered by the FTP process |
INTERACT | interactive-commands | Commands issued at the Junos OS CLI prompt or invoked by a client application such as a Junos XML protocol or NETCONF client |
KERN | kernel | Actions performed or errors encountered by the Junos kernel |
NTP | Actions performed or errors encountered by the Network Time Protocol (NTP) | |
PFE | pfe | Actions performed or errors encountered by the Packet Forwarding Engine |
SYSLOG | Actions performed or errors encountered by the Junos system logging utility | |
USER | user | Actions performed or errors encountered by user-space processes |
Table 2 lists the numerical severity codes that can appear in system log messages and maps them to severity levels.
Table 2: Numerical Codes for Severity Levels Reported in Priority Information
Numerical Code | Severity Level | Description |
|---|---|---|
0 | emergency | System panic or other condition that causes the router to stop functioning |
1 | alert | Conditions that require immediate correction, such as a corrupted system database |
2 | critical | Critical conditions, such as hard errors |
3 | error | Error conditions that generally have less serious consequences than errors in the emergency, alert, and critical levels |
4 | warning | Conditions that warrant monitoring |
5 | notice | Conditions that are not errors but might warrant special handling |
6 | info | Events or nonerror conditions of interest |
7 | debug | Software debugging messages (these appear only if a technical support representative has instructed you to configure this severity level) |
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
Published: 2012-11-15
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
