Skip to main content

5 Messages

 • 

150 Points

Tue, May 29, 2018 7:12 PM

Answered

upgrade/downgrade from fsi to ui is not allowed

What that means this warning?

Responses

Brand User

2.6K Messages

 • 

44.8K Points

2 years ago

Where do you see this warning?

5 Messages

 • 

150 Points

2 years ago

On the AP when I'm trying to do the firmware upgrade

8 Messages

 • 

194 Points

2 years ago

Noticed this if you are going to SZ3.6.1 to Solo firmware 100. Change to the new (ish) 104.X.XXXX Solo firmware and it should work.

Kind regards

Gareth

5 Messages

 • 

150 Points

2 years ago

Upgrading from 3.x to 104.x worked, when I tried to upgrade to SZ to ZD directly showed this message

8 Messages

 • 

194 Points

2 years ago

SZ to ZD isn't a supported path annoyingly, you have to go through solo firmware first so SZ to Solo then Solo to ZD.

43 Messages

 • 

684 Points

2 years ago

seeing this same error when trying to update from APs w vsz FW v3.2.1.0.642 to  FW v3.6.2.x). (and APs stuck at v3.2.1... )

AP Image Signing: AP [2C:C5:D3:xxxx] with firmware version [3.2.1.0.642] is USI. USI to FSI upgrade is not allowed due to difference in Image formats.


or some APs are showing:
working|reading firmware file header
failed|firmware size not as specified in control file

(no FW nor anything blocking any comms bw APs and vSZ)
Brand User

2.6K Messages

 • 

44.8K Points

2 years ago

Hi All,


   The initial question from Diego, found his SZ 3.x AP needed a Solo AP image, to be converted to ZD management use (thread marked Answered).
---

Hi Stephen, and All,


   We have multiple Forums Categories (https://forums.ruckuswireless.com/ruckuswireless/categories ),
and posting a new question is welcome/preferred over adding to an existing one, (especially if in Answered state).
Thanks!

   My answer Stephen, is that you need to start with vSZ on 3.2.x and go thru an SZ 3.4.x zone upgrade, before
trying to upgrade further to 3.6.2.  Upgrade planners should look at the Release Notes for the version you want
to get to (to be sure your AP models are still supported, that your VM has sufficient resources, and that you are
on a version that can upgrade to this release).

   SZ 3.6.2.0.78 (GA) Release Notes say you can upgrade from 3.4.x:
https://support.ruckuswireless.com/documents/2435-smartzone-3-6-2-0-78-mr2-release-notes


   And SZ 3.4.0.0.976 (GA) Release Notes say you can upgrade from 3.2.x:
https://support.ruckuswireless.com/documents/1098-smartzone-3-4-0-0-976-ga-release-notes

   Did you start with vSZ on 3.2.x, and did/do you have an intermediate SZ 3.4 zone, before you tried to move(supported) APs to your SZ 3.6.2 zone?
   I hope this is helpful.
 

43 Messages

 • 

684 Points

2 years ago

thanks that is helpful.  Our scenario is a bit unique-   we had a vsz that broke about 2 years ago,  so aps had been running with no controller in that time (we only use ZD/vSZ to manage APs, no traffic tunnels nor any advanced features). 

we recently built a brand new vsz which is at at 3.6.2 and are trying to move APs over (from no/dead controller , to this new one).   We have not had issues with other APs that are in the same scenario (about 25 moved so far successfully).    Now we are trying to move these 68x and having this issue.

thanks

2 Messages

 • 

70 Points

2 years ago

the question  is did you begin with vSZ on 3.2.x too did do you have a moderate SZ 3.4 zone before you attempted to move(supported) APs to your SZ 3.6.2 zone 

I trust this is useful 
best regards 

3 Messages

 • 

80 Points

2 years ago

the question  is did you begin with vSZ on 3.2.x too did do you have a moderate SZ 3.4 zone before you attempted to move(supported) APs to your SZ 3.6.2 zone 

I trust this is useful 
best regards 
see: https://inro.in/lucky-patcher/ , https://inro.in/9apps/ & https://inro.in/vidmate/