Brocade Mobility RFS Controller CLI Reference Guide (Supporting software release 5.5.0.0 and later) - Manual (Page 58)

40 Brocade Mobility RFS Controller CLI Reference Guide
53-1003098-01
2
Network administrators can use the device-upgrade command to schedule firmware upgrades
across adopted devices within the network. Devices are upgraded based on their device names,
MAC addresses, or RF Domain. The firmware image used for the upgrade can either be
user-defined or built-in.
The user-defined image is pulled from the defined location and applied to the device(s). Use the
device-upgrade > load-image command to provide the image file name and location. User-defined
images always get precedence over built-in images.
NOC and site controllers possess built-in firmware images for the various device types. If the
administrator has not specified an image file name and location, the image on the controller is
used to upgrade the device. The following example describes the various scenarios possible in the
absence of a user-defined image.
A site controller has been scheduled to upgrade all adopted APs. Before executing the upgrade, the
site controller compares the image it possesses with the image on the NOC controller. In case of an
image version mismatch, the site controller does the following:
1. If the site controller is a cluster member, it pulls the image:
• From a cluster peer, provided the AP image version on the peer and the NOC controller
matches.
• From the NOC controller, if the AP image version on the peer and the NOC controller are
mismatched.
• From the NOC controller, if none of the cluster members possess a AP image.
2. If the site controller is not a cluster member, it pulls the image from the NOC controller.
When upgrading devices in a RF Domain, the process is controlled and driven by the NOC
controller. For example, in case of a scheduled upgrading of all APs within an RF Domain, the NOC
controller:
1. Adopts all controllers, in the RF Domain, to the NOC cluster and gets the status of each
controller.
2. Upgrades all controllers, in the cluster, without rebooting them.
Once the upgrade is completed, the following two scenarios are possible:
Scenario 1: If the upgrade/reboot options ARE NOT specified by the network
administrator, the NOC controller:
a. Pushes the AP image on to the RF Domain manager.
b. Reboots the active controller within the RF Domain.
c. Reboots standby controllers after the active controller has successfully rebooted.
If the controllers are auto upgrade enabled, all APs are upgraded after the controllers have
rebooted and the APs have been re-adopted.
Scenario 2: If the upgrade/reboot options ARE specified by the network administrator, the
NOC controller:
a. Reboots the active controller followed by the standby controllers.
b. Pushes the AP image file on to the RF Domain manager.
c. Initiates upgrades on all AP within the RF Domain.
Ensure the RF Domain controllers are auto upgrade enabled.