Reset Search
 

 

Article

Recommendations for upgrading WiNG 5 wireless controller with remote site APs.

« Go Back

Information

 
TitleRecommendations for upgrading WiNG 5 wireless controller with remote site APs.
Objective
Recommendations for upgrading WiNG 5 wireless controllers with remote site APs.
Environment
  • Wireless WiNG
  • WiNG 5.x, 7.x
  • RFS6010
  • RFS7010
  • RFS4010
  • NX9XXX
  • NX75XX
  • NX65XX
  • NX45XX
  • NX55XX
  • VX9000
  • CLI
  • SSH
  • Console (baud rate: 19200 or 115200)
Procedure
1. Prior to starting the upgrade process, log into the controller via SSH (Secure Shell) using PuTTy.exe (or any 3rd party emulation software available) and run these commands to disable auto AP upgrade:
>enable
#self
#no device-upgrade auto
#com wr
2. Upgrade the RFS/NX/VX controller (s):
(TFTP if being used in this example, but FTP and/or USB may be also be used. Detailed instructions can be found here)
#upgrade tftp://<tftp server IP address>/<firmware image> 
3. After the firmware has been successfully uploaded, reboot the controller into the new firmware version:
#reload (Select y to confirm reload once prompted to)
4. This step is only applicable for RFS series wireless controllers. For all other controllers (NX/VX) proceed to step 6. Due to flash partition size limitations, not all AP images are preloaded on the  RFS series wireless controllers; and you may get errors while trying to load additional AP images. in such a case, access the controller and perform the following:.
#cd flash:/upgrade
#dir
 If any files are resident, delete them to free up space:
#del *.* (Select y to confirm when prompted to) 
5. Now you should be able to upload the AP image file/s to the wireless controller:
(TFTP is being used in this example, but FTP and/or USB may be also be used. Detailed instructions can be found here)
#device-upgrade load-image <ap type> tftp://<tftp server IP address>/<AP firmware image> 
(To make sure you select the correct <ap type> use the question mark "?" for available options)
#device-upgrade load-image ap?
  ap621   Firmware image file of AP621 Device
  ap622   Firmware image file of AP622 Device
  ap650   Firmware image file of AP650 Device
  ap6511  Firmware image file of AP6511 Device
  ap6521  Firmware image file of AP6521 Device
  ap6522  Firmware image file of AP6522 Device
  ap6532  Firmware image file of AP6532 Device
  ap6562  Firmware image file of AP6562 Device
  ap71xx  Firmware image file of AP71XX Device
  ap7502  Firmware image file of AP7502 Device
  ap7522  Firmware image file of AP7522 Device
  ap7532  Firmware image file of AP7532 Device
  ap7562  Firmware image file of AP7562 Device
  ap81xx  Firmware image file of AP81XX Device
  ap82xx  Firmware image file of AP82XX Device
  ap8432  Firmware image file of AP8432 Device
  ap8533  Firmware image file of AP8533 Device
6. Verify that the firmware image/s for the AP/s to be upgraded is/are present on the controller (if not, go back to step 5):
#show device-upgrade versions
7. Once you have verified that the AP image/s is/are loaded, you can start upgrading the remote sites:
#device-upgrade rf-domain <rf-domain name> <ap type> no-reboot 
(If you press the tab key after "rf-domain", all rf-domains configured on the controller will be displayed.
To make sure you select the correct <ap type> use the question mark "?" for available options)
8. It may be possible to upgrade AP at several sites (RF-Domains) at a time, as long as the WAN link is stable. You can keep an eye on the upgrades on each rf-domain by using the following command: 
#show device-upgrade status on <rf-domain name>
You can use the "watch" command for the above to monitor the status of downloads to the APs on that specific rf-domain:
#watch <Interval in seconds 1-3600> show device-upgrade status on <rf-domain name>
(ctrl c to cancel)
9. Once all the APs in an RF-Domain are upgraded, they will need to be rebooted into the new firmware. From the controller run the following command:
#reload on <rf-domain name> 
(tab will populate all rf-domain names configured on the controller (#reload on [TAB]).
Please make sure that all APs have been upgraded in the specified RF-Domain before issuing this command.)
To view all available reload options use the ? (question mark): #reload ?, #reload on <rf-domain name> ?, etc.)
NOTE: FTP and/or USB (if supported on the wireless controller) can be used to upload images (wireless controller and AP):
#ftp://ftp_user:ftp_pwd@IP_FTP/file_name
#usb1:/file_name
If using usb (only applicable on RFS/NX platforms), insert the USB stick into the wireless controller and from the CLI/enable prompt, perform the following
#cd usb1
#dir
If an error comes up stating that USB is not mounted, unplug the USB drive from the wireless controller and try the above again (sometimes the USB drive does not mount on first attempt). Also, the above commands assume that the image files are in the root directory of FTP/TFTP/USB.
 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255