User guide

Event Management System/Logging
ExtremeWare 7.2e Installation and User Guide 125
Components and Conditions
Beginning with the introduction of EMS in release 7.1.0, the event conditions detected by ExtremeWare
were organized into components and subcomponents. This is somewhat similar to the fault log
subsystems used in previous versions. Not all conditions have been placed in the
component/subcomponent structure of EMS, but all the conditions will be moved over time into this
structure. To get a listing of the components and subcomponents in your release of ExtremeWare, use
the following command:
show log components {<event component> | all}
For example, to get a listing of the subcomponents that make up the STP component, use the following
command:
show log components stp
The output produced by the command is similar to the following:
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
In the display above is listed the component, the subcomponents that make up that component, and the
default severity threshold assigned to that component. A period (.) is used to separate component,
subcomponent, and condition names in EMS. 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 will often have 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}}} {detail}
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 3
Dump Debug-Data 3
Ign Debug-Summary 2
Trace Info 2
In the display above is listed the four conditions contained in the STP.InBPDU component, the severity
of the condition, and the number of parameters in the event message. In this example, the severities of
the events in the STP.InBPDU subcomponent range from error to debug-summary.
When you use the detail keyword you will see the message text associated with the conditions. For
example, if you want to see the message text and the parameters for the event condition
STP.InBPDU.Trace, use the following command: