Extreme Networks ExtremeWare XOS 11.3, Руководство пользователя

Страница: 200 / 698

Status Monitoring and Statistics
ExtremeWare XOS 11.3 Concepts Guide
200
The three severity levels for extended debugging—
debug-summary
,
debug-verbose
, and
debug-data
—
require that debug mode be enabled (which may cause a performance degradation). See “Displaying
Debug Information” on page 209 for more information about debugging.
You can use more than one command to configure the severity level of the messages sent to a target.
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 | primary-msm | backup-msm |
session | syslog [all | <ipaddress> | <ipPort> {vr <vr_name>} [local0 ... local7]]]
{severity <severity> {only}}
When you specify a severity level, messages of that severity level and greater are sent to the target. If
you want only those 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 to the target,
but specifying
severity warning only
sends only warning messages.
You can also use the following command to configure severity levels, which associate a filter with a
target:
configure log target [console | memory-buffer | primary-msm | backup-msm | nvram |
session | syslog [all | <ipaddress> | <ipPort> {vr <vr_name>} [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 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 202 .
Table 30: Severity levels assigned by the switch
Level Description
Critical A serious problem has been detected that is compromising the operation of the
system; the system cannot function as expected unless the situation is remedied. The
switch may need to be reset.
Error A problem has been detected that is interfering with the normal operation of the
system; the system is not functioning as expected.
Warning An abnormal condition, not interfering with the normal operation of the system, has
been detected that indicate that the system or the network in general may not be
functioning as expected.
Notice A normal but significant condition has been detected, which signals that the system is
functioning as expected.
Info (Informational) A normal but potentially interesting condition has been detected, which signals that
the system is functioning as expected; this level simply provides potentially detailed
information or confirmation.
Debug-Summary A condition has been detected that may interest a developer seeking the reason
underlying some system behavior.
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.