Extreme Networks ExtremeWare Command Reference Manual page 676

Commands for Status Monitoring and Statistics
depending on whether the
if necessary. If the list of filter items has been exhausted with no match, the incident is excluded.
Events, Components, and Subcomponents. As mentioned, a single event can be included or
excluded by specifying the event's name. Multiple events can be added or removed by specifying an
ExtremeWare component name plus an optional severity. Some components, such as BGP, contain
subcomponents, such as Keepalive, which is specified as BGP.Keepalive. (BGP is supported only on the
"i" series switches.) Either components or subcomponents can be specified. The keyword
a component name can be used to indicate all ExtremeWare components.
Severity Levels. When an individual event name is specified following the
severity value is needed since each event has pre-assigned severity. When a component, subcomponent,
or the keyword is specified following the
all
severity is specified, the severity used for each applicable subcomponent is obtained from the
pre-assigned severity threshold levels for those subcomponents. For example, if STP is specified as the
component, and no severity is specified, then only messages with severity of
passed, since the threshold severity for the STP component is
component, and no severity is specified, then only messages with severity of
passed, since the threshold severity for the STP.InPBDU subcomponent is
command to see this information.
components
The severity keyword
all
of (or ) with severity
delete exclude
component of all severity values.
NOTE
If no severity is specified when delete or exclude is specified, severity all is used
If the keyword is present following the severity value, then only the events in the specified
only
component at that exact severity are included. Without the
component at that severity or more urgent are included. For example, using the option
implies critical, error, or warning events, whereas the option
warning
warning events only. Severity
EMS events with severity
debug mode is enabled.
Filter Optimization. Each time a
the events specified are compared against the current configuration of the filter to try to logically
simplify the configuration.
For example, if the command:
configure log filter bgpFilter1 add events bgp.keepalive severity error only
were to be followed by the command:
configure log filter bgpFilter1 add events bgp severity info
the filter item in the first command is automatically deleted since all events in the BGP.Keepalive
subcomponent at severity
first command redundant.
676
keyword was used. Subsequent filter items on the list are compared
exclude
events
can be used as a convenience when
deletes (or excludes) previously added events of the same
all
is not a valid choice.
all only
,
debug-summary debug-verbose
configure log filter
would be also included as part of the second command, making the
error
events
keyword, a severity value is optional. If no
error
. If STP.InBPDU is specified as the
error
warning
warning
or
delete exclude
keyword, events in the specified
only
severity warning only
, or will not be logged unless
debug-data
command is issued for a given filter name,
in place of
all
keyword, no
and greater are
and greater are
. Use the
show log
is specified. The use
severity
implies
ExtremeWare 7.5 Command Reference Guide