boot

Changes the next boot partition or image on a specified device or on the logged device. The WiNG devices have two partitions: primary and secondary, with each partition containing an image of the operating system. Whenever the device boots up it loads the image from the partition specified here.

The partition currently in control of the boot process is the active partition, the other partition is the inactive partition with the alternate image. Use this command to manually change the next boot partition or image.

Supported in the following platforms:

  • Access Points — AP7502, AP7522, AP7532, AP7562, AP7602, AP7612, AP7622, AP7632, AP7662, AP8163, AP8432, AP8533
  • Wireless Controller — RFS4010
  • Service Platforms — NX5500, NX7500, NX9500, NX9600, VX9000

Syntax

boot system [active|inactive|primary|secondary] {on <DEVICE-NAME>}

Parameters

boot system [active|inactive|primary|secondary] {on <DEVICE-NAME>}

system [active|inactive|primary|secondary]

Specifies the image used by the device to boot up

  • active – Changes the next boot image to the current, running (active) image

  • inactive – Changes the next boot image to the current, inactive image

  • primary – Changes the next boot partition to the primary partition.

  • secondary – Changes the next boot partition to the secondary partition.

Note:

You will need to reload the device in order for the change to take effect.

on <DEVICE-NAME>

Optional. Changes the next boot image or partition on a specified device

  • <DEVICE-NAME> – Specify the name of the AP, wireless controller, or service platform.

Note: If no device is specified, the logged device's next boot-up configuration is changed.

Examples

ap8432-5C63F0#show boot
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       04/04/2019 23:45:30     02/14/2019 12:52:42     5.9.5.0-001D
  Secondary     03/12/2019 23:57:24     01/19/2019 13:25:26     5.9.4.0-019B
--------------------------------------------------------------------------------
Current Boot       : Secondary
Next Boot          : Primary
Software Fallback  : Enabled
ap8432-5C63F0#
ap8432-5C63F0#boot system secondary
Updated system boot partition
ap8432-5C63F0#
ap8432-5C63F0#show boot
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       04/04/2019 23:45:30     02/14/2019 12:52:42     5.9.5.0-001D
  Secondary     03/12/2019 23:57:24     01/19/2019 13:25:26     5.9.4.0-019B
--------------------------------------------------------------------------------
Current Boot       : Secondary
Next Boot          : Secondary
Software Fallback  : Enabled
ap8432-5C63F0#
nx9500-6C8809#show boot on ap7562-84A224
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       04/05/2019 00:45:49     04/09/2019 12:35:32     5.9.5.0-001D
  Secondary     01/30/2019 02:30:04     02/03/2019 23:55:14     5.9.4.0-010D
--------------------------------------------------------------------------------
Current Boot       : Primary
Next Boot          : Primary
Software Fallback  : Enabled
VM support         : Not present
nx9500-6C8809#

The following example shows the 'Primary' boot partition as the current and next boot partition, with image 5.9.5.0-001D. You can change the boot partition to 'Secondary' by executing the following command. However, the change will take effect only after the access point is reloaded.

nx9500-6C8809#boot system inactive ap7562-84A224
Updated next boot partition to secondary
nx9500-6C8809#reload