Table of Contents
Advertisement
408
C
A: T
HAPTER
ROUBLESHOOTING A
Using Log Commands
WX S
WITCH
Specifying a severity level sends log messages for events or conditions at
that level or higher to the logging destination. Table 39 lists the severity
levels and their descriptions. (For defaults, see Table 38, "System Log
Destinations and Defaults," on page 407.)
Table 39 Event Severity Levels
Severity
emergency
alert
critical
error
warning
notice
info
debug
To enable, disable, or modify system logging to the WX switch's log
buffer, console, current Telnet session, or trace buffer, use the following
command:
set log {buffer | console | current | sessions | trace}
[severity severity-level] [enable | disable]
To enable, disable, or modify system logging to a syslog server, use the
following command:
set log server ip-addr [severity severity-level
[local-facility facility-name]] [enable | disable]
To view log entries in the system or trace buffer, use the following
command:
display log buffer | trace
Description
The WX switch is unusable.
Action must be taken immediately.
You must resolve the critical conditions. If the conditions are
not resolved, the WX can reboot or shut down.
The WX is missing data or is unable to form a connection.
A possible problem exists.
Events that potentially can cause system problems have
occurred. These are logged for diagnostic purposes. No
action is required.
Informational messages only. No problem exists.
Output from debugging.
The debug level produces a lot of messages, many of which
can appear to be somewhat cryptic. Debug messages are
used primarily by 3Com for troubleshooting and are not
intended for administrator use.
Advertisement
Table of Contents
