Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

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 Impact of Different Local and Forwarded Severity Levels on System Log Messages on a TX Matrix Router.

  • 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 1 specifies the format of the message-source field in the various cases.

Table 1: Format of message-source Field in Messages Logged on TX Matrix Platform

Generating MachineGenerating Routing EngineProcess or ComponentFormat

TX Matrix platform

Local

Process

hostname process[processID]

Component

hostname scc-reX process[processID]

Other

Process

hostname scc-reX scc-componentZ process

Component

hostname scc-reX scc-componentZ process

T640 routing node

Local

Process

hostname lccY-masterprocess[processID]

Component

hostname lccY-master scc-componentZ process

Other

Process

hostname lccY-master lccY-reX process[processID]

Component

hostname lccY-master lccY-reX lccY-componentZ process

hostname is the hostname of the local Routing Engine on the TX Matrix platform.

lccY-master is the master Routing Engine on the T640 routing node with the indicated LCC index number (Y is from 0 through 3).

lccY-reX indicates that the backup Routing Engine on the T640 routing node generated the message (X is 0 or 1). The routing node has the indicated LCC index number (Y matches the value in the lccY-master field.

lccY-componentZ process identifies the hardware component and process on the T640 routing node that generated the message (Y matches the value in the lccY-master field and the range of values for Z depends on the component type). For example, lcc2-fpc1 PFEMAN refers to a process on the FPC in slot 1 on the T640 routing node with index LCC2.

process[process-ID] is the name and PID of the kernel or user-space process that generated the message. If the scc-reX or 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.

scc-componentZ process identifies the hardware component and process on the TX Matrix platform that generated the message (the range of values for Z depends on the component type). For example, spmb1 GSIB refers to a process on one of the processor boards in the Switch Interface Board (SIB) with index 1.

scc-reX indicates that the other Routing Engine on the TX Matrix platform generated the message (X is 0 or 1).