[Contents] [Prev] [Next] [Index] [Report an Error]

Interpreting Messages Generated in Standard Format by a JUNOS Process or Library

The syntax of a standard-format message generated by a JUNOS software process or subroutine library depends on whether it includes priority information:

Table 22 describes the message fields.

Table 22: Fields in Standard-Format Messages Generated by a JUNOS Process or Library

FieldDescription

timestamp

Time at which the message was logged.

message-source

Identifier of the process or component that generated the message and the routing platform on which the message was logged. This field includes two or more subfields, depending on how system logging is configured. See Format of the message-source Field.

facility

Code that specifies the facility to which the system log message belongs. For a mapping of codes to facility names, see Table 13.

severity

Numerical code that represents the severity level assigned to the system log message. For a mapping of codes to severity names, see Table 14.

TAG

Text string that uniquely identifies the message, in all uppercase letters and using the underscore (_) to separate words. The tag name begins with a prefix that indicates the generating software process or library. The entries in this reference are ordered alphabetically by this prefix.

Not all processes on a routing platform use tags, so this field does not always appear.

For a list of prefixes for the tags described in this reference, see System Log Messages.

message-text

Text of the message. For the text for each message, see the chapters following System Log Messages.


[Contents] [Prev] [Next] [Index] [Report an Error]