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

For more information, see the following sections:
•
The message-source Field on a Single-Chassis System on page 43
•
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
The message-source Field on a Single-Chassis System
The format of the message-source field in a message on a single-chassis system depends
on whether the message was generated on the local Routing Engine or the other Routing
Engine (on a system with two Routing Engines installed and operational). Messages from
the other Routing Engine appear only if its configuration includes the other-routing-engine
statement at the [edit system syslog host] hierarchy level.
•
When the local Routing Engine generated the message, there are two subfields:
hostname process[process-ID]
•
When the other Routing Engine generated the message, there are three subfields:
hostname reX process[process-ID]
hostname is the hostname of the local Routing Engine.
process[process-ID] is the name and PID of the process that generated the message. If
the reX field also appears, the process is running on the other Routing Engine. If a process
does not report its PID, the [process-ID] part does not appear.
reX indicates that the other Routing Engine generated the message (X is 0 or 1).
The message-source Field on a TX Matrix Platform
The format of the message-source field in a message on a TX Matrix platform depends
on several factors:
•
Whether the message was generated on the TX Matrix platform or a T640 routing
node in the routing matrix. By default, the master Routing Engine on each T640 routing
node forwards messages from all facilities with severity info and higher to the master
Routing Engine on the TX Matrix platform. When you configure system logging on the
TX Matrix platform, its logs include the forwarded messages. For more information,
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.
•
Whether the message was generated on the local Routing Engine or the other Routing
Engine on the originating machine (TX Matrix platform or T640 routing node). Messages
from the other Routing Engine appear only if its configuration includes the
other-routing-engine statement at the [edit system syslog host] hierarchy level.
•
Whether the message was generated by a kernel or user-space process, or by the
microkernel on a hardware component.
Table 20 on page 44 specifies the format of the message-source field in the various
cases.
43Copyright © 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