Extreme Networks Summit Summit24, Installation And User Manual

Page: 151 / 244

Setting the System Recovery Level
Summit24e3 Switch Installation and User Guide 151
Setting the System Recovery Level
You can configure the system to automatically reboot after a software task exception, using the
following command:
config sys-recovery-level [none | critical | all]
Where the following is true:
•
none
— Configures the level to recovery without a system reboot.
•
critical
— Configures ExtremeWare to log an error into the syslog and automatically reboot the
system after a critical exception.
•
all
— Configures ExtremeWare to log an error into the syslog and automatically reboot the system
after any exception.
The default setting is
none
.
NOTE
Extreme Networks recommends that you set the system recovery level to
critical
. This allows
ExtremeWare to log an error to the syslog and automatically reboot the system after a critical exception.
Logging
The switch log tracks all configuration and fault information pertaining to the device. Each entry in the
log contains the following information:
• Timestamp — The timestamp records the month and day of the event, along with the time (hours,
minutes, and seconds) in the form HH:MM:SS. If the event was caused by a user, the user name is
also provided.
• Fault level — Table 41 describes the three levels of importance that the system can assign to a fault.
By default, log entries that are assigned a critical or warning level remain in the log after a switch
reboot. Issuing a clear log command does not remove these static entries. To remove log entries of all
levels (including warning or critical), use the following command:
clear log static
• Subsystem — The subsystem refers to the specific functional area to which the error refers. Table 42
describes the subsystems.
Table 41: Fault Levels Assigned by the Switch
Level Description
Critical A desired switch function is inoperable. The switch may need to
be reset.
Warning A noncritical error that may lead to a function failure.
Informational Actions and events that are consistent with expected behavior.
Debug Information that is useful when performing detailed
troubleshooting procedures.