Interpreting Messages Generated in Standard Format by a Junos Process or Library
The syntax of a standard-format message generated by a Junos OS process or subroutine
library depends on whether it includes priority information:
•
When the explicit-priority statement is included at the [edit system syslog file filename]
or [edit system syslog host (hostname | other-routing-engine)] hierarchy level, a system
log message has the following syntax:
timestamp message-source: %facility–severity–TAG: message-text
•
When directed to the console or to users, or when the explicit-priority statement is not
included for files or remote hosts, a system log message has the following syntax:
timestamp message-source: TAG: message-text
Table 18 on page 41 describes the message fields.
Table 18: Fields in Standard-Format Messages Generated by a Junos
Process or Library
DescriptionField
Time at which the message was logged.timestamp
Identifier of the process or component that generated the message and the
routing platform on which the message was logged. This field includes two or
more subfields, depending on how system logging is configured. See “The
message-source Field on a TX Matrix Platform” on page 43,“The
message-source Field on a T640 Routing Node in a Routing Matrix” on page 45,
and “The message-source Field on a Single-Chassis System” on page 43.
message-source
Code that specifies the facility to which the system log message belongs. For
a mapping of codes to facility names, see Table: Facility Codes Reported in
Priority Information in “Including Priority Information in System Log Messages”
on page 18.
facility
Numerical code that represents the severity level assigned to the system log
message. For a mapping of codes to severity names, see Table: Numerical
Codes for Severity Levels Reported in Priority Information in “Including Priority
Information in System Log Messages” on page 18.
severity
Text string that uniquely identifies the message, in all uppercase letters and
using the underscore (_) to separate words. The tag name begins with a prefix
that indicates the generating software process or library. The entries in this
reference are ordered alphabetically by this prefix.
Not all processes on a routing platform use tags, so this field does not always
appear.
TAG
Text of the message. For the text for each message, see the chapters following
System Log Messages.
message-text
Interpreting Messages Generated in Standard Format by Services on a PIC
Standard-format system log messages generated by services on a PIC, such as the
Adaptive Services (AS) PIC, have the following syntax:
41Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages
To Next Page
Loading...
Need help?
General
