Supported Platforms
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
- QFX Series
- Overview of Single-Chassis System Logging Configuration
Junos OS System Logging Facilities and Message Severity Levels
Table 1 lists the Junos system logging facilities that you can specify in configuration statements at the [edit system syslog] hierarchy level.
Table 1: Junos OS System Logging Facilities
Facility | Type of Event or Error |
|---|---|
any | All (messages from all facilities) |
authorization | Authentication and authorization attempts |
change-log | Changes to the Junos OS configuration |
conflict-log | Specified configuration is invalid on the router type |
daemon | Actions performed or errors encountered by system processes |
dfc | Events related to dynamic flow capture |
firewall | Packet filtering actions performed by a firewall filter |
ftp | Actions performed or errors encountered by the FTP process |
interactive-commands | Commands issued at the Junos OS command-line interface (CLI) prompt or by a client application such as a Junos XML protocol or NETCONF XML client |
kernel | Actions performed or errors encountered by the Junos OS kernel |
pfe | Actions performed or errors encountered by the Packet Forwarding Engine |
user | Actions performed or errors encountered by user-space processes |
Table 2 lists the severity levels that you can specify in configuration statements at the [edit system syslog] hierarchy level. The levels from emergency through info are in order from highest severity (greatest effect on functioning) to lowest.
Unlike the other severity levels, the none level disables logging of a facility instead of indicating how seriously a triggering event affects routing functions. For more information, see Disabling the System Logging of a Facility.
Table 2: System Log Message Severity Levels
Severity Level | Description |
|---|---|
any | Includes all severity levels |
none | Disables logging of the associated facility to a destination |
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 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 |
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
- QFX Series
- Overview of Single-Chassis System Logging Configuration
Published: 2013-01-16
Supported Platforms
Related Documentation
- M, PTX, T Series
- Single-Chassis System Logging Configuration Overview
- M, MX, PTX, T Series
- Examples: Configuring System Logging
- QFX Series
- Overview of Single-Chassis System Logging Configuration
