Dynamic Configuration Loading

You can load dynamic configuration commands (commands that do not require a reload to take effect) from a file on a TFTP server into the running-config on a RUCKUS device. You can make configuration changes off-line, then load the changes directly into the device running-config, without reloading the software.

Dynamic Configuration Usage Considerations

  • Use this feature only to load configuration information that does not require a software reload to take effect. For example, you cannot use this feature to change statically configured memory using a system-max command or to enter trunk group configuration information into the running configuration.
  • Do not use this feature if you have deleted a trunk group but have not yet placed the changes into effect by saving the configuration and then reloading. When you delete a trunk group, the command to configure the trunk group is removed from the device running configuration, but the trunk group remains active. To finish deleting a trunk group, save the configuration to the startup-config file, then reload the software. After you reload the software, you can then load the configuration from the file.
  • Do not load port configuration information for member ports in a trunk group. Since all ports in a trunk group use the port configuration settings of the LAG virtual interface in the group, the software cannot implement the changes to the member port.

In this section:

  1. Preparing the Configuration File
  2. Loading the Configuration Information into the Running-config
Parent topic: Loading and Saving Configuration Files