Extreme Networks ExtremeWare XOS 11.5, Command Reference Manual

Page: 574 / 2024

Commands for Status Monitoring and Statistics
ExtremeWare XOS 11.5 supports only the Summit X450 family of switches and the BlackDiamond 8800 series switch.
ExtremeWare XOS 11.5 Command Reference Guide
574
the
exclude
keyword was used. Subsequent filter items on the list are compared 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
XOS component name plus an optional severity. Some components, such as
BGP , contain
subcomponents, such as Keepalive , which is specified as BGP.Keepalive . Either components or
subcomponents can be specified. The keyword
all
in place of a component name can be used to
indicate all ExtremeWare XOS components.
Severity Levels. When an individual event name is specified following the events keyword, no severity
value is needed since each event has pre-assigned severity. When a component, subcomponent, or the
all
keyword is specified following the
events
keyword, a severity value is optional. If no 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 were specified as the component, and no
severity is specified for the add of an include item, then only messages with severity of
error
and
greater would be passed, since the threshold severity for the STP component is
error
. If STP.InBPDU
were specified as the component, and no severity is specified, then only messages with severity of
warning
and greater would be passed, since the threshold severity for the STP.InPBDU subcomponent
is
warning
. Use the
show log components
command to see this information.
The severity keyword
all
can be used as a convenience when
delete
or
exclude
is specified. The use
of
delete
(or
exclude
) with severity
all
deletes (or excludes) previously added events of the same
component of all severity values.
NOTE
If no severity is specified when delete or exclude is specified, severity all is used
If the
only
keyword is present following the severity value, then only the events in the specified
component at that exact severity are included. Without the
only
keyword, events in the specified
component at that severity or more urgent are included. For example, using the option
severity
warning
implies critical, error, or warning events, whereas the option
severity warning only
implies
warning events only. Severity
all only
is not a valid choice.
Any EMS events with severity
debug-summary
,
debug-verbose
, or
debug-data
will not be logged
unless debug mode is enabled
Filter Optimization. Each time a
configure log filter
command is issued for a given filter name, 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
error
would be also included as part of the second command, making the
first command redundant.