Extreme Networks ExtremeWare XOS 11.1, Manual

Page: 138 / 496

Status Monitoring and Statistics
ExtremeWare XOS 11.1 Concepts Guide
138
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.
Each time a filter item is added to or deleted from a given filter, the specified events 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 configure the switch so messages reaching the target match a specified match expression. The
message text is compared with the configured match expression to determine whether to pass the
message on. To require that messages match a match expression, use the following command:
configure log target [console | memory-buffer | nvram | primary-msm | backup-msm |
session | syslog [all | <ipaddress> | <ipPort> {vr <vr_name>} [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 compared only with the messages that have already passed the target’s filter. For more
information on controlling the format of the messages, see
“Formatting Event Messages” on page 140 .
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 single
character, while other characters match only themselves (case is significant). Quantifiers include the star
character (*) that matches zero or more occurrences of the immediately preceding token. Constraints
include the caret character (^) that matches at the beginning of a message and the currency character ($)
that matches at the end of a message. Bracket expressions are not supported. There are a number of
sources available on the Internet and in various language references describing the operation of regular
expressions.
Table 21 shows some examples of regular expressions.