Extreme Networks ExtremeWare 7.2e, Installation And User Manual

Page: 131 / 344

Event Management System/Logging
ExtremeWare 7.2e Installation and User Guide 131
show log configuration filter {<filter name>}
The output produced by the command (for the earlier filter) is similar to the following:
Log Filter Name : myFilter
I/ Severity
E Comp SubComp Condition CEWNISVD
- ------- ----------- ----------------------- --------
E STP OutBPDU * CEWNI+++
I STP * * ********
Include/Exclude: (I) Include, (E) Exclude
Severity Values: (C) Critical, (E) Error, (W) Warning, (N) Notice, (I) Info
(*) Pre-assigned severities in effect for each subcomponent
Debug Severity : (S) Debug-Summary, (V) Debug-Verbose, (D) Debug-Data
(+) Debug Severity requested, but log debug-mode not enabled
If Match parameters present:
Parameter Flags: (S) Source, (D) Destination (as applicable)
(I) Ingress, (E) Egress,
Parameter Types: Port - Physical Port list, Slot - Physical Slot #
MAC - MAC address, IP - IP Address/netmask, Mask - Netmask
VID - Virtual LAN ID (tag), VLAN - Virtual LAN name
Nbr - Neighbor, Rtr - Routerid, EAPS - EAPS Domain
Strict Match : (Y) every match parameter entered must be present in the event
(N) match parameters need not be present in the event
The show log configuration filter command shows each filter item, in the order that it will be applied
and whether it will be included or excluded. The above output shows the two filter items, one
excluding events from the STP.OutBPDU component, the next including the remaining events from the
STP component. The severity value is shown as “*”, indicating that the component’s default severity
threshold controls which messages are passed. The
Parameter(s)
heading is empty for this filter, since
no match was configured for this filter. Matches are discussed in the section, “Matching Expressions”.
Each time a filter item is added to or deleted from a given filter, the events specified are compared
against the current configuration of the filter to try to logically simplify the configuration. Existing items
will be replaced by logically simpler items if the new item enables rewriting the filter. If the new item is
already included or excluded from the currently configured filter, the new item is not added to the filter.
Matching Expressions
You can specify that messages that reach the target match a specified match expression. The message
text is compared with the match expression to determine whether to pass the message on. To require
that messages match a match expression, is to use the following command:
configure log target [console-display | memory-buffer | nvram | session |
syslog [<host name/ip> {: <udp-port>} [local0 ... local7]]] match [any
|<match-expression>]
The messages reaching the target will match the
match-expression
, a simple regular expression. The
formatted text string that makes up the message is compared with the match expression, and is passed
to the target if it matches. This command does not affect the filter in place for the target, so the match
expression is only compared with the messages that have already passed the target’s filter. For more
information on controlling the format of the messages, see the section, “Formatting Event Messages”.
Simple Regular Expressions. A simple regular expression is a string of single characters including
the dot character (.), which are optionally combined with quantifiers and constraints. A dot matches any