Filtering Events Sent To Targets - Extreme Networks ExtremeWare 7.2e Installation And User Manual

disable log target [console-display | memory-buffer | nvram | session | syslog
[<host name/ip> {:<udp-port>} [local0 ... local7]]]
NOTE
Refer to your UNIX documentation for more information about the syslog host facility.

Filtering Events Sent to Targets

Not all event messages are sent to every enabled target. Each target receives only the messages that it is
configured for.
Target Configuration
To specify the messages to send to a enabled target, you will set a message severity level, a filter name,
and a match expression. These items determine which messages are sent to the target. You can also
configure the format of the messages in the targets. Each target has a default configuration that mimics
the expected behavior of prior ExtremeWare releases. For example, the console display target is
configured to get messages of severity
and greater, and the memory buffer target gets messages of severity
warning
All the targets are associated by default with a filter named DefaultFilter, that passes all events at or
above the default severity threshold, like the behavior of earlier releases (the earlier releases had no
filters). All the targets are also associated with a default match expression that matches any messages
(the expression that matches any message is displayed as
finally, each target has a format associated with it.
To display the current log configuration of the targets, use the following command:
show log configuration target {console-display | memory-buffer | nvram | session |
syslog <host name/ip> {: <udp-port>}[local0 ... local7]}
To configure a target, there are specific commands for filters, formats, and severity that are discussed in
the following sections.
Severity
Messages are issued with one of the severity level specified by the standard BSD syslog values
(RFC 3164),
critical
debugging,
debug-summary
and
emergency
The three severity levels for extended debugging,
require that debug mode be enabled (which may cause a performance degradation). See the section
"Displaying Debug Information" for more information about debugging.
Table 27: Severity Levels Assigned by the Switch
Level
Critical
Error
ExtremeWare 7.2e Installation and User Guide
info
, , ,
error warning notice
,
debug-verbose
are not needed since
alert
Description
A serious problem has been detected which is compromising the operation of the
system and that the system can not function as expected unless the situation is
remedied. The switch may need to be reset.
A problem has been detected which is interfering with the normal operation of the
system and that the system is not functioning as expected.
and greater, the NVRAM target gets messages of severity
Match: (none)
, and , plus three severity levels for extended
info
, and . Note that RFC 3164 syslog values
debug-data
is the most severe event in the system.
critical
, d
debug-summary ebug-verbose
1
Event Management System/Logging
and greater.
debug-data
from the command line). And
, and
debug-data
,
127