Log Destination - Juniper JUNOSE SOFTWARE 11.2.X - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Command Reference Manual

JunosE 11.2.x Command Reference Guide A to M

log destination

Syntax
Release Information
Description
Options
1232
To specify the destination and severity of messages logged:
log destination { console | nv-file | syslog ipAddress [ facility facilityId ] }
{ severity { severityValue | severityNumber } | off }
no log destination [ console | nv-file | syslog [ ipAddress ] ]
To specify which event categories are logged to syslog:
log destination syslog ipAddress { include | exclude } category [ category ]*
no log destination syslog ipAddress { include | exclude } [ category ]*
Command introduced before JunosE Release 7.1.0.
Configures the logging of system messages. You can direct messages to a destination,
limit the messages logged based on severity level, or limit the event categories for which
messages are logged. The no versions restore default settings or reverse the effect of
previous commands that limited event categories.
NOTE: You can display traffic logs—such as ipTraffic, icmpTraffic, tcpTraffic, and
udpTraffic—only via the show log data command or from the SRP module console. You
cannot redirect traffic logs elsewhere, such as to a system log or nonvolatile storage
file, or to a Telnet session.
console—Configures or modifies logging to the local console
nv-file—Configures or modifies logging to the nonvolatile log file; the nv-file can accept
only events at a severity level of critical or higher in importance
syslog—Configures or modifies logging to a system log server
ipAddress—IP address of the system log application on a remote host
facility—Specifies the system log facility on the host
facilityId—Number in the range 0–7 that identifies the corresponding logging facility,
local0–local7
severity—Sets minimum severity of the log messages displayed; described either by a
descriptive term—severityValue—or by a corresponding number—severityNumber—in
the range 0–7. The lower the number, the higher the priority:
emergency or 0—System unusable
alert or 1—Immediate action needed
critical or 2—Critical condition exists
error or 3—Error condition
Copyright © 2010, Juniper Networks, Inc.