
Media Flow Controller System Logging Overview
229
Media Flow Controller Administrator’s Guide
Configuring and Using Media Flow Controller Logs and Alarms
•
info
—Informational messages (administrator actions)
•
debug
—Debug-level messages (all messages)
Logging class options are:
•
mgmt-core
—Management daemon (mgmtd) only
•
mgmt-back
—Other back end components
•
mgmt-front
—Front end components, utilities, and tests
Configuring Media Flow Controller System Logging (CLI)
1.
Set the minimum severity of log messages to be saved in log files on local persistent
storage (regardless of source), the severity level at which user-executed CLI commands
are logged, or disable local logging altogether.
logging local <severity_level>
logging level cli commands <severity_level>
logging local none
2.
Set or remove (with no) a per-class override on the global logging level for logged
messages local or to a specified remote syslog server; all classes without an override use
the global logging level set with logging local <severity_level> (default is notice). Use
the no variant or set none as the severity level to disable logging from that class entirely.
logging local override class <class> priority <severity_level>
logging <IP_address> trap override class <class> priority <severity_level>
3.
Set or remove (with no) a remote syslog server to receive log messages; and a severity
level of logged messages sent to all, or a specified, remote syslog server.
logging <IP_address>
logging trap <severity_level>
logging <IP_address> trap <severity_level>
4.
Stop sending log messages to any, or a specified, remote syslog server.
logging trap none
logging <IP_address> trap none
5.
Allow (or disable with no) this system to receive log messages from another host; disabled
by default. If enabled, only log messages matching or exceeding the minimum severity
specified with logging local <log level> are logged, regardless of what is sent.
logging recieve
6.
Set (or reset default with no) the format in which log messages should be set. The default
is standard.
logging format standard
logging format welf
7.
Set (or remove with no) the firewall name that should be associated with each message
logged in WELF (Web trends Enhanced Log Format). If no firewall name is set, the
hostname is used by default. Neither of these commands enables WELF logging if it is not
already enabled with logging format welf.
logging format welf fw-name <firewall_name>
8.
Include (or disable with no) an additional field in each log message showing the number of
seconds since the Epoch; default is disabled. This is independent of the standard syslog
datetime at the beginning of each message in the format "Feb 25 18:00:00". Aside from
indicating the year at full precision, its main purpose is to provide subsecond precision.
Содержание MEDIA FLOW CONTROLLER 2.0.4 -
Страница 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Страница 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Страница 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Страница 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Страница 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Страница 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...