Status Monitoring and Statistics
ExtremeWare XOS 11.3 Concepts Guide
198
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
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 | 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 “Target
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.
Use the following command to stop sending messages to the target:
disable log target [console | memory-buffer | nvram | primary-msm | backup-msm |
session | syslog [all | <ipaddress> | <ipPort>] {vr <vr_name>} [local0 ... local7]]]
NOTE
Refer to your UNIX documentation for more information about the syslog host facility.
Dual MSM Systems—Modular Switches Only
A system with dual MSMs keeps the two MSMs synchronized by executing the same commands on
both. However, the full data between the EMS servers is not synchronized. The reason for this design
decision is to make sure that the control channel will not be overloaded when a high number of log
messages are generated.
In order to capture events generated by one MSM onto the other MSM, there are two additional targets
shown in the target commands—one called
master-msm and one called backup-msm. The first target is
active only on the non-primary (backup) EMS server and is used to send matching events to the
primary EMS server. The other target is active only on the primary EMS server and is used to send
matching events to all other EMS servers.
If the condition for the
backup-msm target is met by a message generated on the primary MSM, the
event is sent to the backup MSM. When the backup MSM receives the event, it will see if any of the
local targets (NVRAM, memory, or console) are matched. If so that event gets processed. The
session