Formatting Event Messages - Extreme Networks ExtremeWare XOS Guide Manual

Status Monitoring and Statistics
The string type is used to match a specific string value of an event parameter, such as a user name. A
string can be specified as a simple regular expression.
Match Versus Strict-Match. The and keywords control the filter behavior for
match strict-match
incidents whose event definition does not contain all the parameters specified in a
configure log
command. This is best explained with an example. Suppose an event in the
filter events match
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
keyword, then the filter will never match event XYZ.event5, since this event does not
strict-match
contain the destination MAC address.
In other words, if the keyword is specified, an incident will pass a filter so long as all parameter
match
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 | memory-buffer | nvram | session | syslog [all |
<ipaddress> [local0 ... local7]]]
format [timestamp [seconds | hundredths | none]
| date [dd-mm-yyyy | dd-Mmm-yyyy | mm-dd-yyyy | Mmm-dd | yyyy-mm-dd | none]
| severity
| event-name [component | condition | none | subcomponent]
| priority
| process-name
| process-slot
| source-line
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 timestamp seconds date mm-dd-yyyy 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.
To provide some detailed information to technical support, you set the current session format using the
following command:
configure log target session format timestamp hundredths date mmm-dd event-name
condition source-line process-name
108 ExtremeWare XOS 10.1 Concepts Guide