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

user@host> file show lccn:log-file-pathname
By default, the show log and file show commands display the specified log file stored on
the master Routing Engine on the T640 routing node. To display the log from a particular
Routing Engine, prefix the file- or pathname with the string lccn-master, lccn-re0, or
lccn-re1, followed by a colon. The following examples all display the /var/log/messages
file stored on the master Routing Engine (in slot 0) on routing node LCC2:
user@host> show log lcc2:messages
user@host> show log lcc2-master:messages
user@host> show log lcc2-re0:messages
user@host> file show lcc2:/var/log/messages
If the T640 routing nodes are forwarding messages to the TX Matrix platform (as in the
default configuration), another way to view messages generated on a T640 routing node
during a terminal session on the TX Matrix platform is simply to display a local log file.
However, the messages are intermixed with messages from other T640 routing nodes
and the TX Matrix platform itself. For more information about message forwarding, see
“Messages Logged When Local Severity Level Is Lower” on page 29, “Messages Logged
When Local Severity Level Is Higher” on page 30, and “Messages Logged When Local
and Forwarded Severity Level Are the Same” on page 29.
For information about the fields in a log message, see “Interpreting Messages Generated
in Structured-Data Format” on page 36, “Interpreting Messages Generated in Standard
Format by Services on a PIC” on page 41, and “Interpreting Messages Generated in
Standard Format by a JUNOS Process or Library” on page 41. For examples, see “Examples:
Displaying a Log File” on page 45.
Interpreting System Log Messages
The fields in a message written to the system log depend on whether the message was
generated by a Junos process or subroutine library, or by services on a PIC, and whether
it is in standard format or structured-data format. For more information, see the following
sections:
•
Interpreting Messages Generated in Structured-Data Format on page 36
•
Interpreting Messages Generated in Standard Format by a Junos Process or
Library on page 41
•
Interpreting Messages Generated in Standard Format by Services on a PIC on page 41
Interpreting Messages Generated in Structured-Data Format
Beginning in Junos OS Release 8.3, when the structured-data statement is included in
the configuration for a log file, Junos processes and software libraries write messages to
the file in structured-data format instead of the standard Junos format. For information
about the structured-data statement, see “Logging Messages in Structured-Data Format”
on page 11.
Structured-format makes it easier for automated applications to extract information
from the message. In particular, the standardized format for reporting the value of
variables (elements in the English-language message that vary depending on the
circumstances that triggered the message) makes it easy for an application to extract
Copyright © 2010, Juniper Networks, Inc.36
Junos 10.3 System Log Messages Reference

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