hit counter script

System Log; File Management; Rebooting The Device - Cisco 300 Series Administration Manual

Managed switch
Hide thumbs Also See for 300 Series:
Table of Contents

Advertisement

Administration

System Log

System Log

File Management

Rebooting the Device

STEP 1
STEP 2
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
See
Administration: System
See
Administration: File
Some configuration changes, such as enabling jumbo frame support, require the
system to be rebooted before they take effect. However, rebooting the device
deletes the Running Configuration, so it is critical that the Running Configuration is
saved to the Startup Configuration before the device is rebooted. Clicking Apply
does not save the configuration to the Startup Configuration. For more information
on files and file types, see the
You can back up the configuration by using
Copy/Save Configuration
upload the configuration from a remote device. See the
Configuration/Log
section.
There are cases when you might prefer to set the time of the reboot for some time
in the future. This could happen for example in one of the following cases:
You are performing actions on a remote device, and these actions might
create loss of connectivity to the remote device. Pre-scheduling a reboot
restores the working configuration and enables restoring the connectivity to
the remote device. If these actions are successful, the delayed reboot can
be cancelled.
Reloading the device cause loss of connectivity in the network, thus by
using delayed reboot, you can schedule the reboot to a time that is more
convenient for the users (e.g. late night).
To reboot the device:
Click Administration > Reboot.
Click one of the Reboot buttons to reboot the device.
Log.
Management.
System Files
section.
Administration > File Management >
or clicking Save at the top of the window. You can also
5
Download/Backup
65

Advertisement

Table of Contents
loading

Table of Contents