Supported Platforms
Displaying a Log File from a Routing Matrix
One way to display a log file stored on the local Routing Engine of any of the individual platforms in a routing matrix (T640 routing nodes or TX Matrix platform) is to log in to a Routing Engine on the platform, enter Junos OS CLI operational mode, and issue the show log or file show command described in Displaying a Log File from a Single-Chassis System.
To display a log file stored on a T640 routing node during a terminal session on the TX Matrix platform, issue the show log or file show command and add a prefix that specifies the T640 routing node’s LCC index number as lccn, followed by a colon. The index can be from 0 (zero) through 3:
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:
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 Impact of Different Local and Forwarded Severity Levels on System Log Messages on a TX Matrix Router.
For information about the fields in a log message, see Interpreting Messages Generated in Structured-Data Format, Interpreting Messages Generated in Standard Format by Services on a PIC, and Interpreting Messages Generated in Standard Format by a Junos Process or Library. For examples, see Examples: Displaying a Log File.
