Event Management System/Logging
ExtremeWare XOS 11.1 Concepts Guide
133
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
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
and
syslog
targets are disabled on the backup MSM, as they are handled on the primary. If the
condition for the
primary-msm
target is met by a message generated on the backup, the event is sent to
the primary MSM.
Note that the
backup-msm
target is active only on the primary MSM, and the
primary-msm
target is
active only on the backup MSM.
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.
Содержание ExtremeWare XOS 11.1
Страница 16: ...Contents ExtremeWare XOS 11 1 Concepts Guide 16...
Страница 20: ...Preface ExtremeWare XOS 11 1 Concepts Guide 20...
Страница 21: ...1 Using ExtremeWare XOS...
Страница 22: ......
Страница 78: ...Managing the ExtremeWare XOS Software ExtremeWare XOS 11 1 Concepts Guide 78...
Страница 168: ...Virtual LANs ExtremeWare XOS 11 1 Concepts Guide 168...
Страница 200: ...Policies and ACLs ExtremeWare XOS 11 1 Concepts Guide 200...
Страница 252: ...Security ExtremeWare XOS 11 1 Concepts Guide 252...
Страница 265: ...2 Using Switching and Routing Protocols...
Страница 266: ......
Страница 294: ...Ethernet Automatic Protection Switching ExtremeWare XOS 11 1 Concepts Guide 294...
Страница 354: ...Extreme Standby Router Protocol ExtremeWare XOS 11 1 Concepts Guide 354...
Страница 416: ...IP Multicast Routing ExtremeWare XOS 11 1 Concepts Guide 416...
Страница 417: ...3 Appendixes...
Страница 418: ......
Страница 432: ...Software Upgrade and Boot Options ExtremeWare XOS 11 1 Concepts Guide 432...