Extreme Networks ExtremeWare 7.7, Command Reference Manual

Page: 684 / 2620

684 ExtremeWare 7.7 Command Reference Guide
Commands for Status Monitoring and Statistics
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
all
in place of
a component name can be used to indicate all ExtremeWare 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 is specified as the
component, and no severity is specified, then only messages with severity of
error
and greater are
passed, since the threshold severity for the STP component is
error
. If STP.InBPDU is specified as the
component, and no severity is specified, then only messages with severity of
warning
and greater are
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 keyword
only
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.
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.
As another example, a new exclude filter item may not need to be added if no current include filter
items contain any of the events described in the exclude statement. To illustrate, suppose a new filter
were created and configured as follows:
create log filter myFilter