Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010 User Manual

Table 10: Numerical Codes for Severity Levels Reported in Priority
Information (continued)
DescriptionSeverity LevelNumerical Code
Conditions that warrant
monitoring
warning4
Conditions that are not errors
but might warrant special
handling
notice5
Events or nonerror conditions
of interest
info6
Software debugging messages
(these appear only if a
technical support
representative has instructed
you to configure this severity
level)
debug7
In the following example, the CHASSISD_PARSE_COMPLETE message belongs to the
daemon facility and is assigned severity info (6):
Aug 21 12:36:30 router1 chassisd[522]:
%DAEMON-6-CHASSISD_PARSE_COMPLETE: Using new configuration
When the explicit-priority statement is not included, the priority does not appear in the
message:
Aug 21 12:36:30 router1 chassisd[522]: CHASSISD_PARSE_COMPLETE: Using new
configuration
For more information about message formatting, see “Displaying and Interpreting System
Log Message Descriptions” on page 47.
Including the Year or Millisecond in Timestamps
By default, the timestamp recorded in a standard-format system log message specifies
the month, date, hour, minute, and second when the message was logged, as in the
following example:
Aug 21 12:36:30
To include the year, the millisecond, or both in the timestamp, include the time-format
statement at the [edit system syslog] hierarchy level:
edit system syslog]
time-format (year | millisecond | year millisecond);
The modified timestamp is used in messages directed to each destination configured by
a file, console, or user statement at the [edit system syslog] hierarchy level, but not to
destinations configured by a host statement.
21Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages

Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010 Specifications

General

Brand	Juniper
Model	JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010
Category	Software
Language	English