EasyManuals Logo

Extreme Networks ExtremeWare XOS Guide User Manual

Extreme Networks ExtremeWare XOS Guide
698 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #203 background imageLoading...
Page #203 background image
Event Management System/Logging
ExtremeWare XOS 11.3 Concepts Guide
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
exclude keyword was
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/ Severity
E Comp. Sub-comp. Condition CEWNISVD
- ------- ----------- ----------------------- --------
I STP InBPDU --------
E STP CreatPortMsgFail -E------
I STP --------
Include/Exclude: I - Include, E - Exclude
Component Unreg: * - Component/Subcomponent is not currently registered
Severity Values: C - Critical, E - Error, W - Warning, N - Notice, I - Info
Debug Severity : S - Debug-Summary, V - Debug-Verbose, D - Debug-Data
+ - Debug Severities, but log debug-mode not enabled
If Match parameters present:
Parameter Flags: S - Source, D - Destination, (as applicable)
I - Ingress, E - Egress, B - BGP
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
L4 - Layer-4 Port #, Num - Number, Str - String
Nbr - Neighbor, Rtr - Routerid, EAPS - EAPS Domain
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 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 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
Parameter(s) heading is empty for this filter because no match is configured for this filter. Matches are
described in “Matching Expressions” next.

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the Extreme Networks ExtremeWare XOS Guide and is the answer not in the manual?

Extreme Networks ExtremeWare XOS Guide Specifications

General IconGeneral
BrandExtreme Networks
ModelExtremeWare XOS Guide
CategorySoftware
LanguageEnglish

Related product manuals