Specifications

Event Management System/Logging
ExtremeWare XOS 11.0 Concepts Guide 135
When you specify a severity level as you associate a filter with a target, you further restrict the
messages reaching that target. The filter may allow only certain categories of messages to pass. Only the
messages that pass the filter and then pass the specified severity level reach the target.
Finally, you can specify the severity levels of messages that reach the target by associating a filter with a
target. The filter can specify exactly which message it will pass. Constructing a filter is described in
“Filtering By Components and Conditions” on page 136.
Components and Conditions
The event conditions detected by ExtremeWare XOS are organized into components and
subcomponents. To get a listing of the components and subcomponents in your release of ExtremeWare
XOS, use the following command:
show log components {<event component> | version}
For example, to get a list of the components and subcomponents in your system, use the following
command:
show log components
The partial output produced by the command is similar to the following:
* BD-PC.5 # show log components
Severity
Component Title Threshold
------------------- ---------------------------------------------- -------------
...
...
STP Spanning-Tree Protocol (STP) Error
InBPDU STP In BPDU subcomponent Warning
OutBPDU STP Out BPDU subcomponent Warning
System STP System subcomponent Error
...
...
The display above lists the components, subcomponents, and the default severity threshold assigned to
each. In EMS, you use A period (.) is used to separate component, subcomponent, and condition names.
For example, you can refer to the InBPDU subcomponent of the STP component as STP.InBPDU. On the
CLI, you can abbreviate or TAB complete any of these.
A component or subcomponent often has several conditions associated with it. To see the conditions
associated with a component, use the following command:
show log events [<event condition> | [all | <event component>] {severity <severity>
{only}}] {details}
For example, to see the conditions associated with the STP.InBPDU subcomponent, use the following
command:
show log events stp.inbpdu
The output produced by the command is similar to the following:
Comp SubComp Condition Severity Parameters
------- ----------- ----------------------- ------------- ----------
STP InBPDU Drop Error 2 total
STP InBPDU Dump Debug-Data 3 total