logging
129
Media Flow Manager Administrator’s Guide
CHAPTER 5 CLI Commands
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
, next 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
, next 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
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
logging severity level
, next for details.
•
<IP_address>
—Send syslog messages to the specified remote syslog server.
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
, below.
Table 4
Logging Severity Levels
Level
Description
alert
Action must be taken immediately for functioning to continue.
crit
An unexpected error-causing condition or response for unknown reasons.
debug
Messages generated by the system debugging utility.
emerg
System is unusable or cannot recover.
err
Error conditions.
