Ruckus R500 with firmware 2.6.0.0.370 connect to VsZ with version 5.2.0.0.685

  • 1
  • Question
  • Updated 9 months ago
Dear All Master,

we have problem with our AP Indoor, we have Ruckus R500 with firmware 2.6.0.0.370 connect to VsZ with version 5.2.0.0.685, in now cannot register to VsZ, anyone can help me to solve this problem.


Regards,
Fahrizal Z
Photo of Fahrizal Zulqifli

Fahrizal Zulqifli

  • 20 Posts
  • 0 Reply Likes

Posted 9 months ago

  • 1
Photo of Sanjay Kumar

Sanjay Kumar, Employee

  • 259 Posts
  • 83 Reply Likes
Hi Fahrizal,

Could you please reconfirm the R500 firmware version? If it is 2.6.0.0.370 version, then this is not supported on the vSZ running on 5.2.0.0.685.

If this is the first time connecting this AP to this vSZ, then you might need to upgrade to Standalone version and then add it to the vSZ.
Photo of Fahrizal Zulqifli

Fahrizal Zulqifli

  • 20 Posts
  • 0 Reply Likes
Hi Sanjay,

Thanks for your answer our question, but you can inform to me about stand alone version, how version update to support our AP??.


Regards,
Fahrizal Z
Photo of Sanjay Kumar

Sanjay Kumar, Employee

  • 259 Posts
  • 83 Reply Likes
Hi Fahrizal,

Since this is a old version, I'm not sure about the exact path.
However, you can try upgrading to the least standalone version 9.8.1.0.101 from the below link.
https://support.ruckuswireless.com/software?filter=68#firmwares

You can also try to put 100.0.0.0.127 on the AP, but I do not want the AP to brick.

Try a step by step upgrade from 2.6.x to 9.8.1.0.101 >> 9.8.2.0.15 >> 9.8.3.0.14 >> 100.0.0.0.127 >> 104.0.0.1347

Once on 104 version, you should be able to connect to the vSZ on 5.2 version.

Photo of Fahrizal Zulqifli

Fahrizal Zulqifli

  • 20 Posts
  • 0 Reply Likes
Dear Sanjai,

thanks for information, but after i upgrade to firmware 104.0.0.1347, the AP still cannot join to controller, any idea again?


Regards,
Fahrizal Z
Photo of Sanjay Kumar

Sanjay Kumar, Employee

  • 259 Posts
  • 83 Reply Likes
Hi Fahrizal,

I do not see the SSH tunnel establishing with the controller. Check the below details:

1. Does the controller has enough AP license?
2. Ping between the AP and the controller.
3. AP and Zone country code. ("get countrycode" is the command from the AP CLI)
4. If the above is fine, try disabling the AP cert check from the controller CLI. Probably the AP has older certificate.

ruckus# config
ruckus(config)# no ap-cert-check
ruckus(config)# exit