Event Management System/Logging
ExtremeWare XOS 10.1 Concepts Guide
103
To configure the severity level of the messages sent to a target, there is more than one command that
you can use. The most direct way to set the severity level of all the sent messages is to use the following
command:
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 described in
“Filtering By Components and Conditions” on page 105.
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
Debug-Verbose
A condition has been detected that may interest a developer analyzing some system
behavior at a more verbose level than provided by the debug summary information.
Debug-Data
A condition has been detected that may interest a developer inspecting the data
underlying some system behavior.
Table 19: Severity levels assigned by the switch (continued)
Level
Description
Summary of Contents for ExtremeWare XOS 10.1
Page 12: ...12 ExtremeWare XOS 10 1 Concepts Guide Contents...
Page 15: ...Part 1 Using ExtremeWare XOS...
Page 16: ......
Page 20: ...20 ExtremeWare XOS 10 1 Concepts Guide ExtremeWare XOS Overview...
Page 32: ...32 ExtremeWare XOS 10 1 Concepts Guide Accessing the Switch...
Page 74: ...74 ExtremeWare XOS 10 1 Concepts Guide Virtual LANs VLANs...
Page 80: ...80 ExtremeWare XOS 10 1 Concepts Guide Forwarding Database FDB...
Page 112: ...112 ExtremeWare XOS 10 1 Concepts Guide Status Monitoring and Statistics...
Page 133: ...Part 2 Using Switching and Routing Protocols...
Page 134: ......
Page 174: ...174 ExtremeWare XOS 10 1 Concepts Guide Virtual Router Redundancy Protocol...
Page 184: ...184 ExtremeWare XOS 10 1 Concepts Guide IP Unicast Routing...
Page 202: ...202 ExtremeWare XOS 10 1 Concepts Guide Interior Gateway Protocols...
Page 216: ...216 ExtremeWare XOS 10 1 Concepts Guide Exterior Gateway Routing Protocols...
Page 224: ...224 ExtremeWare XOS 10 1 Concepts Guide IP Multicast Routing...
Page 225: ...Part 3 Appendixes...
Page 226: ......
Page 234: ...234 ExtremeWare XOS 10 1 Concepts Guide Software Upgrade and Boot Options...
Page 242: ...242 ExtremeWare XOS 10 1 Concepts Guide Troubleshooting...
Page 256: ...4 ExtremeWare XOS 10 1 Concepts Guide Index of Commands...