Status Monitoring and Statistics
log message. The system for saving, displaying, and filtering events is called the Event Management
System (EMS). With EMS, you have many 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 per target, by:
●
Component, subcomponent, or specific condition (for example, BGP messages, IGMP.Snooping
■
messages, or the IP.Forwarding.SlowPathDrop condition)
Match expression (for example, any messages containing the string "user5")
■
Matching parameters (for example, only messages with source IP addresses in the 10.1.2.0/24
■
subnet)
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-2005" or "2005-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 buffer or NVRAM 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
You can specify seven types of targets to receive log messages:
Console display
●
Current session (Telnet or console display)
●
Memory buffer (can contain 200 to 20,000 messages)
●
NVRAM (messages remain after reboot)
●
Primary MSM
●
Backup MSM
●
Syslog host
●
The first six types of targets exist by default; but before enabling any syslog host, you must add the
host's information to the switch using the
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 | memory-buffer | nvram | primary-msm | backup-msm |
session | syslog [all | <ipaddress> | <ipPort>] {vr <vr_name>} [local0 ... local7]]]
After you enable this feature, the target receives the messages it is configured for. See
Configuration"
later in this chapter for information on viewing the current configuration of a target. The
memory buffer can contain only the configured number of messages, so the oldest message is lost when
a new message arrives, once the buffer is full.
ExtremeWare XOS 11.1 Concepts Guide
command. Extreme Networks EPICenter
configure syslog
"Target
132