Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 330 / 400

Media Flow Controller CLI Commands Media Flow Controller Administrator’s Guide
330 logging Copyright © 2010, Juniper Networks, Inc.
rotation was based on size, this delays it somewhat as it reduces the size of the
active log file to zero.
•
max-num
—Configure how many old local log files to keep. If the number of log
files ever exceeds this number (either at rotation time, or when this setting is
lowered), the system deletes as many as necessary, starting with the oldest, to
bring it down to this number. Default is 10.
•
upload
—Upload a local log file to a remote host (specified with URL or scp path);
specify which (available ) log file first:
•
current
—The current log file.
•
1
—Archived, compressed log file "messages.1.gz".
•
2
—Archived, compressed log file "messages.2.gz".
To specify an archived log file, give its number as displayed by show log files.
The current log file has the name "messages" if you do not specify a new name for
it in the upload URL. The archived log files have the name "messages.<n>.gz" if
you do not specify a new name in the URL, and are compressed with gzip
regardless. See
“Terminology” on page 30 for the scp URL format and
requirements.
•
format
—Set log messages format. The no variant resets the format to default
(standard), whether or not welf is used with it. Arguments:
•
standard
(default)—Squid standard format.
•
welf
—Web trends Enhanced Log Format. Use fw-name to specify the firewall name
that should be associated with each message logged in WELF format. If no firewall
name is set, the hostname is used by default. Use no logging format welf fw-name
to delete.
•
level cli commands
—Set the severity level at which user-executed CLI commands are
logged. Default is notice. See logging severity level , for details.
•
local
—Set local logging options.
•
override
—Enable, and add or delete (with no) a per-class override on the logging
level. All classes that do not have an override use the global logging level set with
logging local <severity_level>. Use no logging local override to disable all class-
specific overrides to the local log level. Default is enabled. The no variant that
disables them leaves them in configuration, but disables them so the logging level for
all classes is determined by the global setting. Use the class argument to divide log
messages according to their origin. The default classes are mgmt-core (for mgmtd
alone), mgmt-back (for other back end components), and mgmt-front (for front end
components, utilities, and tests).
•
<severity_level>
—Set the minimum severity of log messages to be saved on local
persistent storage, also applies to log messages originating from other hosts; or use
none to disable local logging (you can also use no logging local). See
logging
severity level , for details. Default is notice.
•
recieve
—Allow this system to receive log message from another host. Default is
disabled. If enabled, only log messages matching or exceeding the severity specified with
logging local <severity_level> are logged, regardless of what is sent from the remote
host. Use no logging receive to disable.
•
trap <severity_level>
—Set minimum severity of log messages sent to syslog
servers. This sets both the default for new servers, as well as the setting for all existing