Extreme Networks ExtremeWare XOS Guide Manual page 203

For example, assume that myFilter is configured as before, and assume that you want to exclude the
STP.CreatPortMsgFail event. To add that condition, use the following command:
configure log filter myFilter add exclude events stp.creatportmsgfail
You can also add events and subcomponents to the filter. For example, assume that myFilter is
configured as before, and you want to include the STP.InBPDU subcomponent. To add that condition,
use the following command:
configure log filter myFilter add events stp.inbpdu
You can continue to modify this filter by adding more filter items. The filters process events by
comparing the event with the most recently configured filter item first. If the event matches this filter
item, the incident is either included or excluded, depending on whether the
used. if necessary, subsequent filter items on the list are compared. If the list of filter items is exhausted
with no match, the event is excluded and is blocked by the filter.
To view the configuration of a filter, use the following command:
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/
E Comp. Sub-comp.
- ------- ----------- ----------------------- --------
I STP InBPDU
E STP
I STP
Include/Exclude: I - Include,
Component Unreg: * - Component/Subcomponent is not currently registered
Severity Values: C - Critical,
Debug Severity : S - Debug-Summary,
+ - Debug Severities, but log debug-mode not enabled
If Match parameters present:
Parameter Flags: S - Source,
I - Ingress,
Parameter Types: Port - Physical Port list,
MAC
VID
L4
Nbr
Proc - Process Name
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
applied and whether it will be included or excluded. The above output shows the three filter items, one
including events from the STP.InBPDU component, one excluding the event STP.CreatPortMsgFail, and
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
heading is empty for this filter because no match is configured for this filter. Matches are
Parameter(s)
described in "Matching Expressions"
ExtremeWare XOS 11.3 Concepts Guide
Condition
CreatPortMsgFail
E - Exclude
E - Error,
V - Debug-Verbose,
D - Destination, (as applicable)
E - Egress,
- MAC address, IP - IP Address/netmask,
- Virtual LAN ID (tag),
- Layer-4 Port #, Num
- Neighbor, Rtr - Routerid, EAPS - EAPS Domain
command shows each filter item, in the order that it will be
next.
Event Management System/Logging
exclude
Severity
CEWNISVD
--------
-E------
--------
W - Warning, N - Notice,
D - Debug-Data
B - BGP
Slot - Physical Slot #
Mask - Netmask
VLAN - Virtual LAN name
- Number, Str - String
keyword was
I - Info
203