EasyManuals Logo

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

Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010
748 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #102 background imageLoading...
Page #102 background image
Table 15: Fields in Structured-Data Messages (continued)
ExamplesDescriptionField
junos@2636.1.1.1.2.18 for
the M120 router
An identifier for the type of hardware
platform that generated the message.
The junos@2636 prefix indicates that
the platform runs the Junos OS. It is
followed by a dot-separated numerical
identifier for the platform type. For a list
of the identifiers, see Table 17 on
page 40.
junos@2636.platform
username="regress"A variable-value pair for each element
in the message-text string that varies
depending on the circumstances that
triggered the message. Each pair
appears in the format variable = "value".
variable-value-pairs
User 'regress' exiting
configuration mode
English-language description of the
event or error (omitted if the brief
statement is included at the [edit system
syslog file filename structured-data]
hierarchy level). For the text for each
message, see the chapters following
System Log Messages.
message-text
By default, the structured-data version of a message includes English text at the end, as
in the following example (which appears on multiple lines only for legibility):
<165>1 2007-02-15T09:17:15.719Z router1 mgd 3046 UI_DBASE_LOGOUT_EVENT
[junos@2636.1.1.1.2.18 username="regress"] User 'regress' exiting configuration mode
When the brief statement is included at the [edit system syslog file filename
structured-data ] hierarchy level, the English text is omitted, as in this example:
<165>1 2007-02-15T09:17:15.719Z router1 mgd 3046 UI_DBASE_LOGOUT_EVENT
[junos@2636.1.1.1.2.18 username="regress"]
Table 16 on page 38 maps the codes that appear in the priority-code field to facility and
severity level.
NOTE: Not all of the facilities and severities listed in Table 16 on page 38 can be included
in statements at the [edit system syslog] hierarchy level (some are used by internal
processes). For a list of the facilities and severity levels that can be included in the
configuration, see “Specifying the Facility and Severity of Messages to Include in the
Log” on page 8.
Table 16: Facility and Severity Codes in the priority-code Field
debuginfonoticewarningerrorcriticalalert
Severity
emergencyFacility (number)
76543211kernel (0)
15141312111098user (1)
Copyright © 2010, Juniper Networks, Inc.38
Junos 10.3 System Log Messages Reference

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Juniper JUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010 and is the answer not in the manual?

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

General IconGeneral
BrandJuniper
ModelJUNOS OS 10.3 - SYSTEM LOG MESSAGES REFERENCE 7-12-2010
CategorySoftware
LanguageEnglish

Related product manuals