Logging Severity Level - Juniper MEDIA FLOW MANAGER 2.0.2 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Manager Administrator's Guide
name is set, the hostname is used by default. Use no logging format welf fw-name
to delete.
level cli commands
logged. Default is notice. See
local
override
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>
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
severity
recieve
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>
servers. This sets both the default for new servers, as well as the setting for all existing
servers. The no variant sets the level to none, disabling logging to remote servers
altogether (though the list of servers is not erased). This command does not affect console
or local logging. See
<IP_address>
Hostnames are not allowed. Use no logging <IP_address> to stop. Use the trap option
(set minimum severity of log messages sent to the specified server) arguments, override,
and <severity_level>, as described above for logging local.

logging severity level

Logging severity-level options are described in
Table 4
Logging Severity Levels
Level
alert
crit
debug
emerg
err
—Set the severity level at which user-executed CLI commands are
—Set local logging options.
—Enable, and add or delete (with no) a per-class override on the logging
—Set the minimum severity of log messages to be saved on local
level, next for details. Default is notice.
—Allow this system to receive log message from another host. Default is
—Set minimum severity of log messages sent to syslog
logging severity
—Send syslog messages to the specified remote syslog server.
Action must be taken immediately for functioning to continue.
An unexpected error-causing condition or response for unknown reasons.
Messages generated by the system debugging utility.
System is unusable or cannot recover.
Error conditions.
logging severity
level, next for details.
level, next for details.
Table
4, below.
Description
CHAPTER 5 CLI Commands
logging
logging
129

Advertisement

Table of Contents
loading

Table of Contents