Specifications

Event Management System/Logging
ExtremeWare XOS 10.1 Concepts Guide 103
configure log target [console | memory-buffer | nvram | session | syslog [<all |
ipaddress> [local0 ... local7]]] {severity <severity> {only}}
When you specify a severity level, messages of that severity and greater will be sent to the target. If you
want only messages of the specified severity to be sent to the target, use the keyword
only. For
example, specifying
severity warning will send warning, error, and critical messages, but specifying
severity warning only will just send warning messages.
Another command that can be used to configure severity levels is the command used to associate a
filter with a target:
configure log target [console | memory-buffer | nvram | session | syslog [all |
<ipaddress> [local0 ... local7]]] filter <filter name> {severity <severity> {only}}
When you specify a severity level as you associate a filter with a target, you further restrict the
messages reaching the target. The filter may only allow certain categories of messages to pass. Only the
messages that pass the filter, and then pass the specified severity level will 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 discussed in the
section “Filtering By Components and Conditions”.
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 listing 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
them. 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: