Software Reboot

You can use boot commands to immediately initiate software boots from a software image stored in primary or secondary flash on a RUCKUS device, or from a BootP or TFTP server. You can test new versions of code on a RUCKUS device or choose the preferred boot source from the console boot prompt without requiring a system reset.

Note: You must verify a successful TFTP transfer of the boot code before you reset the system. If the boot code is not transferred successfully but you try to reset the system, the system will not have the boot code with which to successfully boot.

By default, the RUCKUS device first attempts to boot from the image stored in its primary flash, then its secondary flash, and then from a TFTP server. You can modify this booting sequence from the global configuration mode of the CLI using the boot system command.

To initiate an immediate boot from the CLI, enter one of the boot system commands. Refer to the RUCKUS FastIron Command Reference for more information.

Note: When using the boot system tftp command, the IP address of the device and the TFTP server should be in the same subnet.
Note: If you are booting the device from a TFTP server through a fiber connection, use the following command: boot system tftp ip-address filename fiber-port.
Note: The boot system tftp command is not supported in a stacking environment.
Parent topic: Operations, Administration, and Maintenance