To upgrade (or otherwise change) switch software, you must arm the switch with a new release file and then restart all of the switch modules. Use the boot system command to arm the ARX with a release file.

release-file (1-1024 characters) identifies the release file. Use the show directories releases command to see all available release files. Use copy to copy a release file to the switch.

Use show boot to verify that the switch is armed with the new release file.

To revert to an older release after an upgrade, you can downgrade the switch to the old software. You should only do this under the guidance of F5 Support. Downgrading deletes all configuration parameters, both the running-config and the global-config; save both configuration files off of the box before you use this command to downgrade (use copy running-config and copy global-config). Then edit the config files so that they only use CLI commands from the downgrade release. Use boot system to select the old release, then use reload to install it. When you enter the boot system command, a CLI prompt asks for confirmation before deleting the configuration. Enter yes to continue. After the reload, copy the edited config files onto the system, run the running-config, use license activate to enable the license, and then run the global-config.

Each release file may contain module firmware bundled with the software. The release installation (after reboot) puts all such firmware into flash memory on each module, ready to be installed. Use the show firmware upgrade command to enumerate any modules that have newer versions of firmware waiting for them. To install the new firmware onto the module(s), use firmware upgrade.

Contact F5 Support to renew or extend your service contract, then run the license activate or license activate file command to reactivate your license.

The ARX-1500 and ARX-2500 store their metalog data on their internal disks, along with logs, software-release files, and other management data. Managed volumes write their metalog data as clients change the volume state; the metalog is used to restore the volume configuration in the event of a failure. The metalog is also copied to the redundant peer, if there is one (see redundancy). The speed of many volume operations depends on fast metalog writes.

A software installation may include firmware upgrades for the chassis modules, but does not install the new firmware. Use the firmware upgrade command to install firmware from a new software release.

slot-id (1-2) loads the firmware into the given slot only. The firmware is installed and activated the next time the switch reboots. This option is only valid on an ARX-4000.

all loads and installs the latest firmware on all modules in the chassis. This causes the ARX to reboot.

The CLI prompts for confirmation before upgrading any firmware; enter yes to proceed.

Firmware is low-level software, such as BIOS, the RAID controller, software for the FPGAs, and the software components that manage the systems boot process. Each module type has a different set of FPGAs; these include the System-Status Bus (SSB) FPGA, the Non-Volatile RAM (NVR) FPGA, the MetaLog (MTL) FPGA, the franklog FPGA, and the macau FPGA. Module startup is managed by a set of three additional firmware components: the bootstrap software starts the hardware, then the diagnostics run to verify the hardware functions, and finally the boot-loader loads and starts all of the system software. The show firmware upgrade and show chassis moduleinfo commands show the versions for all of these components and FPGAs.

You can use the show firmware upgrade command to see if there is a difference between running and waiting versions of firmware, or to see the status of a firmware upgrade that you invoked with this command.

The firmware upgrade all command reboots the ARX. If the ARX is in a redundant pair, you can only use this syntax on the backup ARX. Certain RAID-maintenance processes also block the firmware upgrade all command: a raid rebuild (which you can stop with raid offline) or a raid verify (which you can stop with no raid verify).

Use the boot system and reload commands to install a full software release package, including (possibly) new firmware releases.

The ARX can be armed with a waiting release file, meaning that the waiting release is swapped with the running release the next time the modules are rebooted. Use the show boot command to see both the running release and the armed release.

Use boot system to arm the switch with the new release file. Use reload to restart all modules and put the new release file into service.

Use the show chassis software command to see the software version(s) running, armed, and otherwise available on the chassis.

System Software shows two software-release files:

Module firmware comes bundled with new software releases, but it is not installed on the modules along with the software. Use the show firmware upgrade command to determine whether or not the latest software release has new firmware for your modules.

verbose (optional) expands the output with detailed version numbers for each firmware package and module.

You can use the firmware upgrade command to manually install the firmware after the software is installed. Use the show firmware upgrade command to view the running versions of firmware along with the versions that may be waiting.

The summary version shows a table with two columns: Slot and Status Summary. The Status Summary for each slot compares the running firmware with the firmware that is available from the installed software release: Up to date, Pending, Upgrade available, and Upgrade in progress are possible values.