Cisco Wlc Ap Software Being Upgraded Please Try Again Later
Managing Software
Upgrading the Controller Software
When you upgrade the controller software, the software on the admission points associated with the controller is also automatically upgraded. When an access point is loading software, each of its LEDs blinks in succession.
 Caution | Exercise not power down the controller or any access betoken during this process; otherwise, the software prototype could exist corrupted. Upgrading a controller with a large number of access points can have as long every bit 30 minutes, depending on the size of your network. Yet, with the increased number of concurrent admission point upgrades supported in the controller software release, the upgrade time should exist significantly reduced. The access points must remain powered, and the controller must non exist reset during this time. |
Guidelines and Restrictions for Upgrading Controller Software
The following are some of the general guidelines and restrictions that are applicable when upgrading the controller software. For any release-specific restrictions, come across the relevant release notes.
For correct interoperability among Cisco Wireless infrastructure, including but not limited to mobility amid controllers, AP compatibility, see the Cisco Wireless Solutions Software Compatibility Matrix at:
https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html-
For every software upgrade, see the corresponding release notes for whatever caveats, considerations, or possible interim upgrades required to upgrade your controller to the desired release of software.
-
We recommend that yous have a backup of your configuration in an external repository before whatever software upgrade activity.
-
Ensure that the configuration file that you back upwardly does not contain < or > special character. If either of the special characters is nowadays, then the download of the backed up configuration file fails.
-
The upgrade of the controller software, with a fast connectedness to your TFTP, SFTP, or FTP file server, can take approximately fifteen to 25 minutes or less from the get-go of the software transfer to reboot of controller (might have longer if the upgrade also includes a Field Upgrade Software installation during the aforementioned maintenance window). The time required for the upgrade of the associated APs might vary from one network to another, due to a variety of deployment-specific factors, such every bit number of APs associated with controller, speed of network connectivity between a given AP and the controller, and and so on.
-
We recommend that, during the upgrade procedure, you exercise not power off controller or any AP associated with the controller.
-
Controllers back up standard SNMP Direction Information Base (MIB) files. MIBs can be downloaded from the Download Software area in Cisco.com.
-
The objects under the SNMP table bsnAPIfDot11CountersEntry like bsnAPIfDot11RetryCount, bsnAPIfDot11TransmittedFrameCount, and so on, per SNMP MIB description, are defined to use the alphabetize as 802.3 (Ethernet) MAC address of the AP. However, the controller sends the AP radio MAC accost in snmpget, getnext, and getbulk. This is because the snmpwalk returns index using base radio MAC address instead of the AP Ethernet MAC address.
-
You can reduce the network downtime using the post-obit options:
-
You can predownload the AP image.
For more information about predownloading the AP prototype, run into the "Predownloading an Image to an Access Point" section.
-
For FlexConnect admission points, use the FlexConnect Efficient AP upgrade characteristic to reduce traffic between the controller and the AP (main site and the branch).
For more information well-nigh configuring FlexConnect AP upgrades, come across the Configuring FlexConnect AP Upgrades for FlexConnect APs section.
-
Upgrading Controller Software (GUI)
Before you begin
Process
| Step 1 | Upload your controller configuration files to a server to back them upwards.
| ||
| Stride 2 | Get the controller software image by following these steps: | ||
| Stride 3 | Re-create the controller software prototype (filename.aes) to the default directory on your TFTP or FTP server.
| ||
| Stride 4 | (Optional) Disable the 802.11 networks.
| ||
| Step v | Choose Commands > Download File to open the Download File to Controller page. | ||
| Footstep 6 | From the File Type drop-down list, choose Lawmaking. | ||
| Footstep 7 | From the Transfer Mode drop-down listing, choose from the post-obit options:
| ||
| Step 8 | In the IP Address field, enter the IP accost of the server. | ||
| Step 9 | (Optional) If you lot are using a TFTP server, the default values of 10 retries for the Maximum Retries text field, and 6 seconds for the Timeout text field should work correctly without any aligning. However, you tin alter these values if desired. To exercise so, enter the maximum number of times that the TFTP server attempts to download the software in the Maximum Retries field and the amount of time (in seconds) that the TFTP server attempts to download the software in the Timeout field. | ||
| Step 10 | In the File Path field, enter the directory path of the software. | ||
| Step 11 | In the File Proper name field, enter the name of the controller software file (filename.aes). | ||
| Stride 12 | If you are using an FTP server, follow these steps:
| ||
| Stride 13 | Click Download to download the software to the controller. A bulletin is displayed indicating the status of the download. | ||
| Pace 14 | (Optional) Afterwards the download is complete, you can cull to predownload the image to your access points. For more information, run across the "Predownloading an Image to an Access Point" section. | ||
| Footstep 15 | Click Reboot to reboot the controller. | ||
| Footstep xvi | If prompted to save your changes, click Save and Reboot. | ||
| Step 17 | Click OK to confirm. | ||
| Stride 18 | Later on the controller reboots, repeat step 6 to step 16 to install the remaining file. | ||
| Stride nineteen | If you accept disabled the 802.11 networks, reenable them. | ||
| Pace 20 | To verify the controller software version, cull Monitor on the controller GUI and meet Software Version in the Controller Summary area. |
Upgrading Controller Software (CLI)
Earlier you begin
Procedure
| Pace ane | Upload your controller configuration files to a server to back them upwards.
| ||||||
| Step 2 | Get the controller software image by post-obit these steps: | ||||||
| Step 3 | Copy the controller software prototype (filename.aes) to the default directory on your TFTP or FTP server. | ||||||
| Footstep 4 | Log onto the controller CLI. | ||||||
| Step five | On the controller CLI over Telnet or SSH, enter the ping server-ip-address command to verify that the controller can contact the TFTP or FTP server. | ||||||
| Step half-dozen | (Optional) Disable the 802.11 networks past entering this command:
| ||||||
| Step 7 | View current download settings by inbound the transfer download outset command. Press n at the prompt to view the current download settings. | ||||||
| Footstep 8 | Change the download settings, if necessary past entering these commands:
(Optional) If yous are using a TFTP server, also enter these commands:
If y'all are using an FTP server, also enter these commands:
| ||||||
| Pace 9 | View the current updated settings by entering the transfer download first command. Printing y at the prompt to confirm the current download settings and beginning the software download. | ||||||
| Footstep 10 | (Optional) After the download is consummate, you tin choose to predownload the prototype to your access points. For more information, see the "Predownloading an Paradigm to an Access Point" section. | ||||||
| Footstep 11 | Salvage the lawmaking update to nonvolatile NVRAM and reboot the controller by entering this command: The controller completes the bootup process. | ||||||
| Step 12 | After the controller reboots, echo Steps vii through eleven to install the remaining file. | ||||||
| Step 13 | If you lot take disabled the 802.xi networks in Stride 6, reenable them by entering this command: | ||||||
| Step 14 | To verify the controller software that is installed, enter the show sysinfo command and come across Product Version. | ||||||
| Stride 15 | (Optional) To verify the Cisco Unified Wireless Network Controller Boot Software file that is installed on the controller, enter the testify sysinfo command on the controller CLI and encounter Recovery Paradigm Version or Emergency Image Version.
|
Predownloading an Image to an Access Indicate
To minimize network outages, yous can download an upgrade image to the access point from the controller without resetting the access indicate or losing network connectivity. Previously, yous would download an upgrade epitome to the controller and reset it, which causes the access point to go into discovery mode. Later on the admission point discovers the controller with the new prototype, the access point downloads the new image, resets, goes into discovery mode, and rejoins the controller.
You can now download the upgrade image to the controller and then download the image to the access point while the network is still operational. You tin can as well schedule a reboot of the controller and access points, either subsequently a specified corporeality of time or at a specific date and time. When both devices are up, the access indicate discovers and rejoins the controller.
Concurrent Controller to AP Image Upgrade
This tabular array lists the controllers and their maximum concurrent AP image download back up.
| Controller | Maximum Number of Concurrent AP Image Download Supported |
|---|---|
| Cisco 5520 Wireless Controller | yard |
| Cisco 8540 Wireless Controller | 1000 |
| Cisco vWLC | yard |
Flash Retentiveness Requirements on Access Points
This table lists the Cisco AP models and the minimum amount of gratuitous flash memory required for the predownload procedure to work:
| Cisco AP | Minimum Free Flash Memory Required |
|---|---|
| 3700(I/E) | 16 MB |
| 3600(I/E) | 14 MB |
| 3502(I/E) | 14 MB |
| 2700(I/Due east) | sixteen MB |
| 2602(I/E) | 14 MB |
| 1700(I/E) | 16 MB |
| 1602(I/Eastward) | 12 MB |
| 1262 | xiv MB |
| 1142 | 12 MB |
 Note |
|
Access Point Predownload Process
The admission point predownload characteristic works as follows:
-
The controller image is downloaded.
-
(Optional) The principal image becomes the fill-in image of the controller and the downloaded image becomes the new primary epitome. Change the current boot image as the backup paradigm by using the config boot fill-in control to ensure that if a arrangement failure occurs, the controller boots with the last working image of the controller.
-
Kickoff the AP image predownload procedure for all joined APs or a specific AP, by entering the config ap image predownload primary {all | ap-proper name} command.
-
The upgrade image is downloaded every bit the backup paradigm on the APs. Y'all can verify this past using the testify ap image all command.
-
Modify the boot epitome to primary image manually using the config kicking primary command and reboot the controller for the upgrade prototype to be activated.
or
-
You issue a scheduled reboot with the swap keyword. The swap keyword has the following importance: The swapping occurs to the primary and backup images on the admission signal and the currently active image on controller with the backup image.
-
When the controller reboots, the access points are disassociated and eventually come up with an upgraded paradigm. Once the controller responds to the discovery request sent by an access point with its discovery response packet, the access point sends a join request.
-
-
The actual upgrade of the images occur. The following sequence of actions occur:
-
During kick time, the admission point sends a join request.
-
The controller responds with the join response with the image version that the controller is running.
-
The access point compares its running epitome with the running image on the controller. If the versions friction match, the access point joins the controller.
-
If the versions practice not match, the access point compares the version of the backup paradigm and if they friction match, the access point swaps the primary and backup images and reloads and subsequently joins the controller.
-
If the master prototype of the access signal is the aforementioned equally the controller image, the access signal reloads and joins the controller.
-
If none of the higher up conditions are true, the admission point sends an image information request to the controller, downloads the latest image, reloads, and joins the controller.
-
| Note | Commonly, when upgrading the epitome of an AP, you can utilise the preimage download feature to reduce the amount of time the AP is unavailable to serve clients. However, information technology also increases the downtime considering the AP cannot serve clients during an upgrade. The preimage download feature can be used to reduce this downtime. Even so, in the case of a branch office fix upwardly, the upgrade images are still downloaded to each AP over the WAN link, which has a higher latency. A more efficient manner is to employ the FlexConnect AP Image Upgrade characteristic. When this feature is enabled, ane AP of each model in the local network first downloads the upgrade image over the WAN link. For more data about FlexConnect AP upgrades, see the "FlexConnect AP Image Upgrades" affiliate. |
Guidelines and Restrictions for Predownloading an Image to an Access Point
-
The maximum number of concurrent predownloads is limited to half the number of concurrent normal image downloads. This limitation allows new access points to join the controller during paradigm downloading.
-
If you reach the predownload limit, and so the access points that cannot become an image sleep for a time between 180 to 600 seconds and so reattempt the predownload.
-
Before you predownload, you lot should modify the active controller boot image to the fill-in image to ensure that if the controller reboots for some reason, information technology comes back up with the earlier running prototype, non the partially downloaded upgrade image.
-
This predownload feature is not supported on 1242 and 1131 Cisco AP models.
-
When the system time is changed by using the config time command, the time fix for a scheduled reset is not valid and the scheduled system reset is canceled. You are given an choice either to abolish the scheduled reset before configuring the time or retain the scheduled reset and not configure the time.
-
All the primary, secondary, and 3rd controllers should run the same images equally the primary and backup images. That is, the primary image of all 3 controllers should exist X and the secondary epitome of all 3 controllers should exist Y or the feature is not effective.
Having different versions of the controller software running on primary, secondary, and tertiary controllers adds unnecessary and protracted delays to APs failing over and joining the other available controllers in an N+1 setup. This is due to the APs existence forced to download different image versions when failing over to a secondary or third controller, and joining back to their principal controller when information technology is available.
-
At the time of the reset, if any AP is downloading the controller prototype, the scheduled reset is canceled. The following bulletin appears with the reason why the scheduled reset was canceled: %OSAPI-three-RESETSYSTEM_FAILED: osapi_task.c:4458 System will not reset every bit software is being upgraded. -
Predownloading a 7.2 or later version of image on a Cisco Aironet 1240 admission signal is not supported when upgrading from a previous controller release. If predownloading is attempted to the Cisco Aironet 1240 access signal, the AP gets disconnected.
-
There are two images for the1550 Mesh AP - 1550 with 64 MB retention and 1550 with 128 MB memory. During the controller upgrade to vii.6 and higher versions, the AP images are downloaded and there are 2 reboots.
-
If y'all upgrade from a release that is prior to Release seven.five straight to Release 7.vi.10 or a later release, the predownload procedure on Cisco AP2600 and AP3600 fails. After the controller is upgraded to Release seven.6.X or a later release, the new prototype is loaded on Cisco AP2600 and AP3600. Later the upgrade to a Release 7.six.X epitome, the predownload functionality works as expected. The predownload failure is only a one-time failure.
-
If you upgrade from 8.2 to 8.4 release, the predownload process on Cisco AP1700, AP2700, or AP3700 fails with the following error message:
Not enough free space to download.Subsequently the controller is reloaded with eight.iv, the backup image version still shows up as 3.0.
-
If an AP is in the process of downloading a software image, the status of the download is not shown on the controller CLI. During the image download procedure, any configuration performed on the AP via the controller CLI is not applied. Therefore, we recommend that you lot do not perform any configuration on the AP via the controller CLI if an epitome download on the AP is in progress.
Predownloading an Image to Access Points—Global Configuration (GUI)
Process
| Step 1 | To configure the predownloading of access signal images globally, cull Wireless > Access Points > Global Configuration to open the Global Configuration page. |
| Step 2 | In the AP Image Pre-download section, perform 1 of the post-obit:
|
| Step iii | Click OK. |
| Step iv | Click Apply. |
Predownloading an Image to Access Points (CLI)
Process
| Step i | Specify APs that volition receive the predownload paradigm by entering one of these commands:
The output lists APs that are specified for predownloading and provides for each AP, master and secondary prototype versions, the version of the predownload epitome, the predownload retry time (if necessary), and the number of predownload attempts. The output also includes the predownload condition for each device. The status of the APs is as follows:
| ||||||
| Step ii | Set a reboot time for the controller and the APs. Use i of these commands to schedule a reboot of the controller and APs:
Employ the show reset control to display scheduled resets. Data similar to the following appears: |
Bootloader and Recovery Image
The controller, by default, maintains ii software images: a primary image and a backup prototype. The primary prototype is the active image used past the controller and the backup epitome is used as a backup for the principal (active) image.
The controller bootloader (ppcboot) stores a copy of the primary (active) image and the backup image. If the master image is corrupted, you must utilise the bootloader to boot with the backup paradigm.
You lot can change the active prototype using either of the post-obit 2 methods:
-
Assuming that the controller has a valid fill-in image, reboot the controller. During the kick process on the controller, printing Esc cardinal to come across additional options. You are prompted to choose an option from the following:
-
Run primary prototype
-
Run backup image
-
Manually upgrade primary prototype
-
Change active kicking prototype
-
Articulate configuration
Choose Option 4: Alter active boot epitome from the kicking bill of fare to set the backup image every bit the active boot epitome. The controller, when rebooted, boots with the new active image.
-
-
You can too manually change the active booti paradigm of the controller using the config boot {primary | backup} command.
Each controller can kicking off the primary, previously loaded OS image or boot off the fill-in prototype, an Bone epitome that was loaded earlier. To change the controller boot option, use the config boot command. By default, the primary image on the controller is called as the agile paradigm.
| Note | To properly use the bootloader menu, you must have a console connexion. |
Configuring Boot Order (GUI)
Procedure
| Step 1 | Cull to navigate to the Config Boot Prototype page, which displays the main and backup images shortly bachelor on the controller and also indicates the current image in use. |
| Step ii | From the Image drop-downwards listing, cull the image to be used as the active image. |
| Footstep 3 | Save the configuration and reboot the controller. |
-
The controller, when rebooted, boots with the image that yous chose.
-
When you upgrade the controller with the new image, the controller automatically writes the new epitome as the principal image and the previously existing primary image is written over the backup prototype.
Note
The previously existing backup prototype will be lost.
-
On the controller GUI, to see the active prototype that the controller is currently using, choose to navigate to the Summary folio and see the Software Version field.
On the controller CLI, use the show boot command to view the master and backup image present on the controller.
Recovering an Access Point Using TFTP
| Note | IPv6 is not supported in AP recovery images. |
Procedure
| Step 1 | Download the required recovery paradigm from Cisco.com and install it in the root directory of your TFTP server. |
| Step ii | Connect the TFTP server to the same subnet every bit the target admission betoken and power-cycle the access betoken. The access signal boots from the TFTP image and so joins the controller to download the oversized access indicate image and consummate the upgrade process. |
| Pace iii | Subsequently the admission indicate has been recovered, you can remove the TFTP server. |
lopezeaddelartion.blogspot.com
Source: https://www.cisco.com/c/en/us/td/docs/wireless/controller/8-5/config-guide/b_cg85/managing_software.html
0 Response to "Cisco Wlc Ap Software Being Upgraded Please Try Again Later"
Post a Comment