User guide

Event Management System/Logging
ExtremeWare 7.2e Installation and User Guide 123
Once enabled, the target receives the messages it is configured for. See the section “Target
Configuration” for information on viewing the current configuration of a target. The memory buffer can
only contain the configured number of messages, so the oldest message is lost when a new message
arrives, and the buffer is full.
Use the following command to stop sending messages to the target:
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
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, 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
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-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, 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 the section
“Displaying Debug Information” for more information about debugging.