scc-reX indicates that the other Routing Engine on the TX Matrix platform generated the
message (X is 0 or 1).
The message-source Field on a T640 Routing Node in a Routing Matrix
The format of the message-source field in a message on a T640 routing node in a routing
matrix depends on two factors:
•
Whether the message was generated on the local Routing Engine or the other Routing
Engine. 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 21 on page 45 specifies the format of the message-source field in the various cases.
Table 21: Format of message-source Field in Messages Logged on TX
Matrix Platform
FormatProcess or ComponentGenerating Routing Engine
hostname-lccY
process[processID]
ProcessLocal
hostname-lccY
lccY-componentZ process
Component
hostname-lccY lccY-reX
process[processID]
ProcessOther
hostname-lccY lccY-reX
lccY-componentZ process
Component
hostname-lccY is the hostname of the local Routing Engine and the T640 routing node’s
LCC index number.
lccY-componentZ process identifies the hardware component and process that generated
the message (Y matches the value in the hostname-lccY field and the range of values for
Z depends on the component type). For example, lcc0-fpc0 CMLC refers to a process
on the FPC in slot 0. The T640 routing node has index LCC0 in the routing matrix.
lccY-reX indicates that the other Routing Engine on the routing node generated the
message (Y matches the value in the hostname-lccY field and X is 0 or 1).
process[process-ID] is the name and PID of the kernel or user-space process that generated
the message. If the lccY-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.
Examples: Displaying a Log File
Display the contents of the /var/log/messages file stored on the local Routing Engine.
(The /var/log directory is the default location for log files, so you do not need to include
45Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring System Log Messages
To Next Page
Loading...