Reset Search
 

 

Article

How to Upgrade the Firmware of Adopted APs From a WiNG Virtual Controller

« Go Back

Information

 
TitleHow to Upgrade the Firmware of Adopted APs From a WiNG Virtual Controller
Objective
Upgrading adopted APs with mismatched firmware versions via the virtual controller. 
Environment
  • AP75XX
  • AP75XXE
  • AP65XX
  • AP65XXE
  • AP76XX
  • AP8533
  • AP8232
  • AP8432
  • WiNG SWIFT UI
  • WiNG Enterprise UI
  • WiNG 5.X
Procedure
Prerequisites:
  • TFTP or FTP server. 
  • Latest Firmware
  • Client APs and virtual controller in same broadcast domain
  • All firewalls disabled on computer if using TFTP
  • Web browser, preferably Chrome or Firefox
Upgrade procedure:
  1. APs using Swift UI (Procedure for APs with Enterprise UI further down):
(for this example we will be using the TFTP server, but FTP is another option should you wish to follow that route. The procedure is exactly the same with the exception of replacing TFTP with FTP when selecting the Protocol and entering the required information into the appropriate fields)
  1. Load the image file into the tftp server's root directory
  2. Make sure all firewalls are off
  3. Make sure that the TFTP server interface shows the correct IP address of the computer It is installed on
  4. Log into the virtual controller via the web browser and go down to Configuration > Access points
  5. Select the virtual controller by checking the box to the left of the its name
  6. Click on the Tools menu and select Upgrade

User-added image

  1.  Make sure that the "Remote" radio button is selected. Under Protocol, select the TFTP radio button and enter the IP address of the TFTP  server and full image name (case sensitive):

User-added image

  1. Click on the Upgrade button at the bottom right hand corner of the page
  2. Check the progress bar to make sure that the firmware was successfully loaded, then reboot the AP from the Tools menu

 User-added image

  1. Once the virtual controller is rebooted, the adopted APs should upgrade automatically. On some models the adopted APs will not automatically upgrade after the virtual controller has been upgraded and rebooted, in this case upgrade the virtual controller again by following steps 6 to 9. After the second virtual controller upgrade and reboot, the adopted APs should automatically upgrade. 
  1. APs with Enterprise UI:
(for this example we will be using the TFTP server, but FTP is another option should you wish to follow that route. The procedure is exactly the same with the exception of replacing TFTP with FTP when selecting the Protocol and entering the required information into the appropriate fields)
  1. Load the image file into the tftp server's root directory
  2. Make sure all firewalls are off
  3. Make sure that the TFTP server interface shows the correct IP address of the computer It is installed on
  4. Log into the virtual controller via the web browser and click on the Operations tab
  5. By default you should be in the Devices Menu. Expand System > Expand Default (or your RF-Domain name if other than Default) > Select the virtual controller from the list
  6. On the Summary page click on the Firmware Upgrade button

User-added image

  1.  By default the protocol selected is TFTP. Change host selection from Hostname to IPV4 Address > enter the IP address of the TFTP  server > Enter the full image name (case sensitive) into the Path/File field. You do not need to enter a path if the image is in the root directory of the TFTP server. 

User-added image

  1. Click on the Apply button and check the progress bar to make sure that the firmware was successfully loaded. Click the OK button once done. 

 User-added image
User-added image

  1. Click on the Reload button to reboot the AP
User-added image
  1. Make sure that the Next Boot partition is the correct one and click on reload again
User-added image
  1. Once the virtual controller is rebooted, the adopted APs should upgrade automatically. On some models the adopted APs will not automatically upgrade after the virtual controller has been upgraded and rebooted, in this case upgrade the virtual controller again by following steps 6 to 10. After the second virtual controller upgrade and reboot, the adopted APs should automatically upgrade. 
  2. If for some reason the APs will still not upgrade after the seconds VC upgrade,upload the AP image to the VC manually by following these steps: 
    1. SSH into the virtual controller and run these commands
>en 
#show device-upgrade versions
If the image is not listed proceed to next step
#device-upgrade load-image <ap_model> tftp://<tftp_server_Ip_address>/<filename.img>
Example: 
#device-upgrade load-image ap7632 tftp://192.168.10.3/AP7632-5.9.2.4-004R.img

FTP method if preferred:
#device-upgrade load-image <ap_model> ftp://<ftp_username>:<ftp_password>@<ftp_server_Ip_address>/<filename.img>
Once done, check to make sure that the image was properly uploaded:
#show device-upgrade versions
  1. Reload (reboot) the adopted APs so that they may start upgrading 
Additional notes
Upgrading the adopted APs from the virtual controller will not work if:
  • You select Local instead of Remote upgrade (Swift UI on Device Upgrade page)
  • You are upgrading from CLI
  • You are using anything other than TFTP or FTP, i. e. HTTP
  • The AP image is not listed in device-upgrade versions

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255