User guide

122 ExtremeWare 7.2e Installation and User Guide
Status Monitoring and Statistics
Event Management System/Logging
Beginning in ExtremeWare 7.1.0, the system responsible for logging and debugging was updated and
enhanced. We use the general term, event, for any type of occurrence on a switch which could generate
a log message, or require an action. For example, a link going down, a user logging in, a command
entered on the command line, or the software executing a debugging statement, are all events that
might generate a log message. The new system for saving, displaying, and filtering events is called the
Event Management System (EMS). With EMS, you have a lot more options about which events generate
log messages, where the messages are sent, and how they are displayed. Using EMS you can:
• send event messages to a number of logging targets (for example, syslog host and NVRAM)
• filter events on a per-target basis
— by component, subcomponent, or specific condition (for example, IGMP.Snooping messages, or the
IP.Forwarding.SlowPathDrop condition)
— by match expression (for example, any messages containing the string “user5”)
— by matching parameters (for example, only messages with source IP addresses in the 10.1.2.0/24
subnet)
— by severity level (for example, only messages of severity critical, error, or warning)
• change the format of event messages (for example, display the date as “12-May-2003” or
“2003-05-12”)
• display log messages in real-time, and filter the messages that are displayed, both on the console and
from telnet sessions
• display stored log messages from the memory buffer or NVRAM
• upload event logs stored in memory to a TFTP server
• display counts of event occurrences, even those not included in filter
• display debug information, using a consistent configuration method
Sending Event Messages to Log Targets
There are five types of targets that can receive log messages:
• console display
• current session (telnet or console display)
• memory buffer (can contain 200-20,000 messages)
• NVRAM (messages remain after reboot)
• syslog host
The first four types of targets exist by default, but before enabling any syslog host, the host’s
information needs to be added to the switch using the
configure syslog command. Extreme
Networks EPICenter can be a syslog target.
By default, the memory buffer and NVRAM targets are already enabled and receive messages. To start
sending messages to the targets, use the following command:
enable log target [console-display | memory-buffer | nvram | session | syslog [<host
name/ip> {:<udp-port>} [local0 ... local7]]]