• September 19, 2020, 05:30:34 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Upgrade from wing 5.2 to 5.5 via CLI - syntax issues  (Read 12533 times)

0 Members and 1 Guest are viewing this topic.

Offline jdcaduceus

  • Rookie
  • **
  • Posts: 8
Upgrade from wing 5.2 to 5.5 via CLI - syntax issues
« on: December 23, 2013, 07:13:41 PM »
I am very thankful for this forum as it has helped me navigate the issues of my ap7131.   I am now trying to upgrade wings 5.2 to 5.5.   I have the .img and binary files but am having trouble with the CLI syntax. 

I see several references to say I should use the following commands at the admin prompt:

Upgrade ftp(location of file)-use img file

Others say to use syntax:

Ap-upgrade ap7131 ftp(location of file) use img file.   

When I use the command nothing happens or I get a response that identifies my ap7131 MAC address and says 0 AP queued for upgrade. 

I need some help with syntax to get this to work.  Can someone direct me on the appropriate syntax to upgrade from wings 5.2 to 5.5?    Do I use the binary or img file when doing upgrade via CLI?

Thanks in advance for any advice to make this work. 


Offline noobie

  • Full Member
  • ***
  • Posts: 92
Re: Upgrade from wing 5.2 to 5.5 via CLI - syntax issues
« Reply #1 on: December 24, 2013, 02:11:43 AM »

you should use the syntax below (before that ensure you are in a privilege mode (type "enable")):

"upgrade ftp://user:pass@server/firmware.img"

"ap-upgrade" is a command to upgrade adopted devices, if the AP would act as a Virtual controller, in 5.5. I think its now called "device-upgrade", since you now can adopt controllers.

Have fun:)

Offline romnet

  • Jr. Member
  • **
  • Posts: 25
Re: Upgrade from wing 5.2 to 5.5 via CLI - syntax issues
« Reply #2 on: December 24, 2013, 02:42:04 AM »
Hi all,

Here is an extract for others to make sure the document is spread :

AP Upgrade/Downgrade Procedure  (independent ap only)
The method described in this section uses the Command Line Interface (CLI) procedures. To log into
the CLI, either SSH, Telnet or serial access can be used. 
5.3.1 Upgrade from WiNG v5.1.x or higher to WiNG v5.5
1. Copy the APXXXX-5.5.X-0XXR.img to your tftp/ftp server. 
2. Use the ―upgrade ftp://<username>:<password>@<ip address of server>/<name of file>, or
―upgrade tftp://<ip address of server>/<name of file> command from CLI or AccessPoint-
>Firmware->Update Firmware option from the GUI. You may need to specify the username and
password for your ftp server. 
3. Restart the Access Point. From CLI the command is ―reload. 
Note: WiNG 5.1.3 added support for the new NAND for AP 7131N. WiNG 5.1.4 added support for the
new NAND for AP 7161. Hardware revs with the new NAND will be unable to downgrade below
these versions or version 4.1.5 – as these support the new NAND, but previous versions do not.


From older 4.x


 Upgrade/Downgrade for AP 7131/AP 7131N from WiNG v4.x to WiNG v5.x 
Upgrade from WiNG v4.x to WiNG v5.x
If an AP 7131 has a firmware release version 3.2.0 or earlier, it is mandatory to upgrade the access
point to release version before an upgrade to release version 4.x or later can be attempted.
Users on AP 7131 release version 3.2.2 need not downgrade to version 3.2.1 and can directly
upgrade to a release version 4.x or later.
Users are strongly cautioned against upgrading from the AP 7131 System Boot OS prompt. 
Upgrading from the Boot OS prompt is not a recommended and supported upgrade methodology
on the AP 7131.
To conduct a firmware update on the AP 7131 from the run-time system software
1. Select ‘System Configuration’, ‘Firmware Update’ from the AP 7131 menu tree of the GUI. 
2. Specify the name of the target firmware file within the ‘Filename’ field.
3. If the target firmware file resides within a directory, specify a complete path for the file
within the ‘Filepath (optional)’ field.
4. Enter an IP address for the FTP or TFTP server used for the update.
5. Select either the FTP or TFTP button to define whether the firmware file resides on a FTP or
TFTP server.
6. Set the following FTP parameters if applicable:
a. Username - Specify a username for the FTP server login.
b. Password - Specify a password for FTP server login.
7. Click ‘Apply’.
Click the ‘Perform Update’ button to initiate the update. Upon confirming the firmware update, the
AP reboots and completes the update. This step may take several minutes. After this upgrade the
access point will reload and come up with wing 5.x firmware.
Note:  Please use the special "migration image" (AP7131-5.5.X-0XXR.bin) when upgrading from 4.x
to 5.x.
If the user upgrades an AP 7131/AP 7131N running a version of code older than using the AP
migration image, there is a possibility of the AP getting “stuck” on coming up with 5.x.  If this occurs,
the following error message is seen on the console after bootup:
***cpu not running at correct speed.  Expected(500Mhz) current> Speed(600MHz)***
To work-around this issue, the administrators need to type the following command after the error
message: ‘achip fix-cpu-speed’
When the AP comes upto runtime, upgrade again using the ‘upgrade’ command to the latest 5.3

Offline superbaim

  • Full Member
  • ***
  • Posts: 67
Re: Upgrade from wing 5.2 to 5.5 via CLI - syntax issues
« Reply #3 on: January 22, 2014, 11:39:27 PM »
I have experience upgrade ap6532 5.2 firmware to 5.5, it cannot directly upgrade to 5.5 you must upgraded to 5.4. hope this help

Offline Jakub

  • Jr. Member
  • **
  • Posts: 31
Re: Upgrade from wing 5.2 to 5.5 via CLI - syntax issues
« Reply #4 on: January 27, 2014, 09:55:26 AM »
It depend which upgrade you tried .. with RFS? Then you can use ap-upgrade command for all AP-7131.
But if it is Virtual controller or standalone APs then you need upgade all APs one by one manualy:

8. In Virtual Controller deployments, APs running version 5.4 will not adopt to a virtual
controller running version 5.5. First upgrade APs to version 5.5 (manually) and then upgrade
the Virtual Controller. New APs need to be upgraded to 5.5 manually before connecting to a
WiNG 5.5 Virtual Controller network.

I was really dissapointed when I found this in last public release notes for 5.5.1