An administrator can provide a profile with unique device configuration file and firmware upgrade support. In a clustered environment, these operations can be performed on one device, then propagated to each member of a cluster and onwards to devices managed by each cluster member. The number of concurrent device upgrades and their start times can be customized to ensure a sufficient number of devices remain in duty while upgrades are administered to others.
To define a profile's access point upgrade configuration:
A list of profiles (default and user-created) is displayed.
The selected profile's configuration menu is displayed.
Expand Management and select Firmware.
Refer to the Auto Install via DHCP Option section to configure automatic configuration file and firmware updates.
|
Enable Configuration Update |
Select the Enable Configuration Update radio button (from within the Automatic Configuration Update field) to enable automatic configuration file updates for the profile from an external location. If enabled (the setting is disabled by default), provide a complete path to the target configuration file used in the update. |
|
Enable Firmware Upgrade |
Select this option to enable automatic firmware upgrades (for this profile) from a user defined remote location. This value is disabled by default. |
|
Start Time (minutes) |
Use the spinner control to set the number of minutes to delay the start of an auto upgrade operation. Stagger the start of an upgrade operation as needed in respect to allowing an access point to complete its current client support activity before being rendered offline during the update operation. The default setting is 10 minutes. |
Refer to the parameters within the Legacy Device Firmware Management field to set legacy access point firmware provisions:
|
Migration Firmware from AP71xx 4.x path |
Provide a path to a firmware image used to provision AP71xx model access points currently utilizing a 4.x version legacy firmware file. Once a valid path is provided, the update is enabled to the version maintained locally for AP71xx models. |
|
Legacy AP650 Auto Update |
Select this option to provision AP650 model access points from their legacy firmware versions to the version maintained locally for that model. This setting is enabled by default, making updates to AP650 models automatic if a newer AP650 image is maintained locally. |
Use the parameters within the Automatic Adopted AP Firmware Upgrade section to define an automatic firmware upgrade from a local file.
|
Enable Controller Upgrade of AP Firmware |
Select this radio button to enable adopted radios to upgrade to a newer firmware version using its associated controller's most recent resident firmware file for that access point model. This parameter is disabled by default. |
|
Number of Concurrent Upgrades |
Use the spinner control to define the maximum number (1 - 20) of adopted access points that can receive a firmware upgrade at the same time. Keep in mind, during a firmware upgrade, the access point is offline and unable to perform its normal wireless client support function until the upgrade process is complete and the access point rebooted. |
Select the Persist Image on Controller button (from within the Firmware Persistence for Adopted Devices field) to enable the NX5500, NX7500, NX9500, and NX9600 series RF Domain manager to retain and store the new image of an access point selected for a firmware update. The image is only stored on the RF Domain manager when there's space to accommodate it.
The upgrade sequence is different depending on whether the designated RF Domain manager is a controller/service platform or access point.
When the RF Domain manager is an access point - The NOC uploads a provisions an access point model's firmware on to the access point RF Domain manager. The NOC initiates an auto-update for access points using that model's firmware. If the Persist Image on Controller option is selected, the RF Domain manager retains the image for that model. The NOC then provisions the firmware of the next access point type to the RF Domain manager. The auto-update process is then repeated for that model. Once all the selected models have been updated, the RF Domain manager's model is updated last.
When the RF Domain manager is a controller or service platform - The NOC adopts controllers to the NOC's cluster within its RF Domain. The NOC triggers an update on active controllers or service platforms and reboots them as soon as the update is complete. As soon as the active nodes come back up, the NOC triggers an update on standby controllers or service platforms and reboots them as soon as the update is complete. When the standby controllers or service platforms come back up the following conditions apply: If the reboot is not scheduled - The access points adopted to RF Domain members are not updated. It's expected the controllers and service platforms have auto-upgrade enabled which will update the access points when re-adopted. If the reboot is scheduled - The NOC pushes the first access point model's firmware to the RF Domain manager. The NOC initiates an access point upgrade on all access points on the RF Domain manager for that model. If the Persist Image on Controller option is selected, the RF Domain manager retains the image for that model. The NOC then provisions the firmware of the next access point type to the RF Domain manager. This process is repeated until each selected access point model is updated.
The Persist Image feature is enabled for all controller and service platform RF Domain managers with the flash memory capacity to store firmware images for the selected access point models they provision. This feature is disabled for access point RF Domain managers that do not typically have the flash memory capacity needed.
Select OK to save the changes made to the profile's Management Firmware configuration. Select Reset to revert to the last saved configuration.