Loading and Saving Configuration Files

For easy configuration management, all RUCKUS devices support both the download and upload of configuration files between the devices and a TFTP server on the network.

You can upload either the startup configuration file or the running configuration file to the TFTP server for backup and use in booting the system:

  • Startup configuration file - This file contains the configuration information that is currently saved in flash. To display this file, enter the show configuration command at any CLI prompt.
  • Running configuration file - This file contains the configuration active in the system RAM but not yet saved to flash. These changes could represent a short-term requirement or general configuration change. To display this file, enter the show running-config or write terminal command at any CLI prompt.

Each device can have one startup configuration file and one running configuration file. The startup configuration file is shared by both flash modules. The running configuration file resides in DRAM.

When you load the startup-config file, the CLI parses the file three times.

  1. During the first pass, the parser searches for system-max commands. A system-max command changes the size of statically configured memory.
  2. During the second pass, the parser implements the system-max commands if present and also implements trunk configuration commands (trunk command) if present.
  3. During the third pass, the parser implements the remaining commands.

After you make configuration changes to the active system, you can save those changes by writing them to flash memory. When you write configuration changes to flash memory, you replace the startup configuration with the running configuration. The following example saves configuration changes to the active system to flash memory.

device# write memory

Note: To return the unit to the default startup configuration, use the delete startup-config command. Refer to the RUCKUS FastIron Command Reference for more information.

The following example displays how to back out of the changes you have made to the running configuration and return to the startup configuration. 

device# reload

In this section:

  1. Logging Changes to the Startup-config File
    You can configure a RUCKUS device to generate a Syslog message when the startup-configuration file is changed. The trap is enabled by default.
  2. Copying a Configuration File To or From a TFTP Server
    You can upload a copy of the running configuration file from a Layer 2 or Layer 3 switch to a Trivial File Transfer Protocol (TFTP) server. The following task copies the startup-config or running-config file to or from a TFTP server.
  3. Maximum File Sizes for Startup-config File and Running-config File
  4. Dynamic Configuration Loading
Parent topic: Configuration File Management