Extreme Networks ExtremeWare XOS 10.1, Manual

Page: 102 / 256

102 ExtremeWare XOS 10.1 Concepts Guide
Status Monitoring and Statistics
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 an 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. For example, the console display target is
configured to get messages of severity
info
and greater, the NVRAM target gets messages of severity
warning
and greater, and the memory buffer target gets messages of severity
debug-data
and greater.
All the targets are associated by default with a filter named DefaultFilter, that passes all events at or
above the default severity threshold. All the targets are also associated with a default match expression
that matches any messages (the expression that matches any message is displayed as
Match : (none)
from the command line). And 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 | memory-buffer | nvram | session | syslog
<ipaddress> [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
,
error
,
warning
,
notice
, and
info
, plus three severity levels for extended
debugging,
debug-summary
,
debug-verbose
, and
debug-data
. Note that RFC 3164 syslog values
emergency
and
alert
are not needed since
critical
is the most severe event in the system.
The three severity levels for extended debugging,
debug-summary
,
debug-verbose
, and
debug-data
,
require that debug mode be enabled (which may cause a performance degradation). See “Displaying
Debug Information” on page 111 for more information about debugging.
Table 19: Severity levels assigned by the switch
Level Description
Critical A serious problem has been detected which is compromising the operation of the
system and that the system cannot function as expected unless the situation is
remedied. The switch may need to be reset.
Error A problem has been detected which is interfering with the normal operation of the
system and that the system is not functioning as expected.
Warning An abnormal condition, not interfering with the normal operation of the system, has
been detected which may indicate that the system or the network in general may not
be functioning as expected.
Notice A normal but significant condition has been detected, which signals that the system is
functioning as expected.
Info (Informational) A normal but potentially interesting condition has been detected, which signals that the
system is functioning as expected and simply provides potentially detailed information
or confirmation.
Debug-Summary A condition has been detected that may interest a developer determining the reason
underlying some system behavior.