Reset Search
 

 

Article

How to upgrade a WiNG controller or AP from CLI

« Go Back

Information

 
TitleHow to upgrade a WiNG controller or AP from CLI
Objective
To upgrade a WiNG controller or AP from CLI using one of the following methods:
  • FTP server
  • ​TFTP server
  • USB thumb drive (Only for controllers and APs with USB slots)
  • SFTP server
Environment
  • WiNG 5.x
  • WiNG controllers
  • WiNG APs
  • TFTP
  • FTP
  • USB
  • SFTP
  • CLI
Procedure
Prerequisites:
  • FTP server
  • TFTP server
  • USB thumb driver
  • SFTP server
  • FTP, TFTP and SFTP servers should be using their default ports (This will eliminate the need to add a port # to the upgrade command)
  • Firmware loaded into the root directory of the FTP, TFTP, SFTP server or USB drive (This will eliminate the need to add a path to the upgrade command)
  • SSH client such as Putty.exe or a console cable for serial connection (depending on AP/controller model, the baud rate would be either 19200 or 115200)
Procedure:
  • Log into the device via SSH or console port and run the following commands:
  1. FTP method (recommended):  
>en
#upgrade ftp://<username>:<password>@<ftp-server-IP>/filename.img 
Example: #upgrade ftp://steve:123456@192.168.0.100/RFS4000-5.8.6.0-011R.img  (the file name is case sensitive)
#show boot
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       07/16/2016 03:06:45     05/09/2017 15:41:09     5.8.4.0-034R
  Secondary     02/23/2017 16:53:24     04/11/2017 15:18:16     5.8.6.0-011R
--------------------------------------------------------------------------------
Current Boot       : Primary
Next Boot          : Secondary
Software Fallback  : Enabled
#reload
The system will be rebooted, do you want to continue? (y/n): y
 Note: Make sure that the FTP server password is set. Try the following syntax If no password is being used:
#upgrade ftp://<username>@<ftp-server-IP>/filename.img 
Example: #upgrade ftp://steve@192.168.0.100:21/RFS4000-5.8.6.0-011R.img  (the file name is case sensitive)
 
  1. TFTP method(Note: All firewalls should be turned off for this method to work.)  
>en
#upgrade tftp://<tftp-server-IP>/filename.img 
Example: #upgrade tftp://192.168.0.100/RFS4000-5.8.6.0-011R.img   (the file name is case sensitive)
#show boot
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       07/16/2016 03:06:45     05/09/2017 15:41:09     5.8.4.0-034R
  Secondary     02/23/2017 16:53:24     04/11/2017 15:18:16     5.8.6.0-011R
--------------------------------------------------------------------------------
Current Boot       : Primary
Next Boot          : Secondary
Software Fallback  : Enabled
#reload
The system will be rebooted, do you want to continue? (y/n): y
 
  1. USB method (Only for controllers and APs with USB slots):  
    1. Make sure that the drive is properly mounted and recognized:
>en 
#cd usb1

IMPORTANT: if you encounter the error: %% Error:  can not mount USB when you run the above commands, then the USB thumb drive is not recognized.
Try one of the following:
- Unplug and replug the USB thumb drive (sometimes the USB drive does not mount on first attempt)​
- Use the second USB port, if available. In this case the command will become: #cd usb2
- Use another thumb drive
- Reboot the controller or AP with the thumb drive plugged in (except in the case of NX95xx and NX96xx controllers. See additional notes)
  1. List the files within the USB drive to confirm that the firmware image to be loaded is correct:
#dir usb1
Directory of usb1:/
-rw- 103317504 Thu Dec 26 17:51:24 2016 RFS4000-5.8.6.0-011R.img
  1. Proceed with the upgrade:
#upgrade usb1:/filename.img 
Example: #upgrade usb1:/RFS4000-5.8.6.0-011R.img   (the file name is case sensitive)
#show boot
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       07/16/2016 03:06:45     05/09/2017 15:41:09     5.8.4.0-034R
  Secondary     02/23/2017 16:53:24     04/11/2017 15:18:16     5.8.6.0-011R
--------------------------------------------------------------------------------
Current Boot       : Primary
Next Boot          : Secondary
Software Fallback  : Enabled
#reload
The system will be rebooted, do you want to continue? (y/n): y
 
  1. SFTP method
>en
#upgrade sftp://<username>:<password>@<sftp-server-IP>/filename.img 
Example: #upgrade sftp://steve:123456@192.168.0.100/RFS4000-5.8.6.0-011R.img  (the file name is case sensitive)
#show boot
--------------------------------------------------------------------------------
     IMAGE            BUILD DATE             INSTALL DATE          VERSION
--------------------------------------------------------------------------------
  Primary       07/16/2016 03:06:45     05/09/2017 15:41:09     5.8.4.0-034R
  Secondary     02/23/2017 16:53:24     04/11/2017 15:18:16     5.8.6.0-011R
--------------------------------------------------------------------------------
Current Boot       : Primary
Next Boot          : Secondary
Software Fallback  : Enabled
#reload
The system will be rebooted, do you want to continue? (y/n): y
Note: Make sure that the SFTP server password is set. Try the following syntax If no password is being used:
#upgrade sftp://<username>@<sftp-server-IP>/filename.img 
Example: #upgrade sftp://steve@192.168.0.100:21/RFS4000-5.8.6.0-011R.img  (the file name is case sensitive)
Additional notes
NX95xx and NX96xx controller will not fully boot if USB drive is detected during POST. Remove USB drive before rebooting controller.

Related articles: 
How to upgrade/downgrade WiNG controllers from CLI using a USB thumb drive
Recommendations for upgrading WiNG 5 wireless controller with remote site APs.
How to upgrade adopted APs from a WiNG virtual controller

Please contact our Global Technical Assistance Center (GTAC) if further assistance is required: 

Feedback

 

Was this article helpful?


   

Feedback

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

Characters Remaining: 255