cancel
Showing results for 
Search instead for 
Did you mean: 

T300, T310C and Ruckus one

Masterx81
New Contributor

Hi!

I own 3 T300 and 1 T310C, and checking on the supported devices page seem that they are supported on the ruckus one, so i've tried to add the serial numbers on the platform, but they never connect. I'm sure that all the configurations are ok. I've connected to the same platform also an R320 and an R350 without much problems.

So i've tried to upgrade one of the t300 to the latest "solo firmware" that i've found for the device (version  110.0.0.0.2005) but it still not connect to the ruckus cloud.

Then i've tried on 2 of the other devices (a t300 and a t310c) to upgrade to the unleashed version (i'm fairly new to the ruckus world, so i was unaware of the differences) but obviously they not connect to the cloud.

So, now i'm also trying to revert back to the "solo" firmware version on this 2 devices, but i can't, as the t310c set himself master of the unleashed "array", with fw version 200.7.10.2.339, the t300 is set as slave with fw version 200.7.10.2.339. When i try to ugrade manually the firmware versions back to the solo one's, i find the 110.0.0.0.663 for the T310C, and the 110.0.0.0.675 for the T300, and the firmware upgrade stops with the error:

The uploaded software version is 110.0.0.0.675, doesn't match with Master AP's 110.0.0.0.663, please choose the same version as Master AP.

So, how i can revert back them to the solo firmware, and connect them to the ruckus one cloud?

Thanks!

1 ACCEPTED SOLUTION

Masterx81
New Contributor

Nevermind, fixed.

I was able to connect the T300 with "solo" firmware resetting them to factory default, while for the firmware problem, i was able to replace it with the "solo" version via SSH.

Now all is connected to the ruckus one cloud.

Thanks!

View solution in original post

1 REPLY 1

Masterx81
New Contributor

Nevermind, fixed.

I was able to connect the T300 with "solo" firmware resetting them to factory default, while for the firmware problem, i was able to replace it with the "solo" version via SSH.

Now all is connected to the ruckus one cloud.

Thanks!