Extreme Networks ExtremeWare 7.2e, Installation And User Manual

Page: 133 / 344

Event Management System/Logging
ExtremeWare 7.2e Installation and User Guide 133
configure log filter myFilter add events bridge severity notice match source
mac-address 00:01:30:23:C1:00 and destination mac-address 01:80:C2:00:00:02
Match Versus Strict-Match.
The
match
and
strict-match
keywords control the filter behavior for
incidents whose event definition does not contain all the parameters specified in a
configure log
filter events match
command. This is best explained with an example. Suppose an event in the
XYZ component, named XYZ.event5, contains a physical port number, a source MAC address, but no
destination MAC address. If you configure a filter to match a source MAC address and a destination
MAC address, XYZ.event5 will match the filter when the source MAC address matches regardless of the
destination MAC address, since the event contains no destination MAC address. If you specify the
strict-match
keyword, then the filter will never match event XYZ.event5, since this event does not
contain the destination MAC address.
In other words, if the
match
keyword is specified, an incident will pass a filter so long as all parameter
values in the incident match those in the match criteria, but all parameter types in the match criteria
need not be present in the event definition.
Formatting Event Messages
Event messages are made up of a number of items. The individual items can be formatted, however,
EMS does not allow you to vary the order of the items. To format the messages for a particular target,
use the following command:
configure log target [console-display | memory-buffer | nvram | session |
syslog [<host name/ip> {:<udp-port>} [local0 ... local7]]]
format [timestamp [seconds | hundredths | none]
| date [dd-mm-yyyy | dd-Mmm-yyyy | mm-dd-yyyy | Mmm-dd | yyyy-mm-dd | none]
| severity [on | off]
| event-name [component | condition | none | subcomponent]
| host-name [on | off]
| priority [on | off]
| tag-id [on | off]
| tag-name [on | off]
| sequence-number [on | off]
| process-name [on | off]
| process-id [on | off]
| source-function [on | off]
| source-line [on | off]]
Using the default format for the session target, an example log message might appear as:
05/29/2003 12:15:25.00 <Warn:SNTP.RslvSrvrFail> The SNTP server parameter value
(TheWrongServer.example.com) can not be resolved.
If you set the current session format using the following command:
configure log target session format date mm-dd-yyy timestamp seconds event-name
component
The same example would appear as:
05/29/2003 12:16:36 <Warn:SNTP> The SNTP server parameter value
(TheWrongServer.example.com) can not be resolved.
In order to provide some detailed information to technical support, you set the current session format
using the following command: