Skip to main content

Mon, Jul 9, 2018 4:26 PM

R500 access point go offline and non responsive when configuring with 1100 controller

Hello everyone, We have an issue configuring new R500 access points with a ZD1100 controller and wanted to know if anyone else has either seen this issue or has a fix.

We have a ZD1100 running version 9.10.2.0 build 11. We have tried to introduce two R500 access points and when the controller sees them it detects it joins with a different firmware/custom file version and is being upgraded. We then get a message that the AP is disconnected and we cannot communicate with the access point again.

2018/07/05  12:54:20Medium AP joins with uptime [147] s and last disconnected reason [Update Backup Image]
2018/07/05  12:52:57Medium AP joins with different firmware/custom file version and is being upgraded.

Do we need to match the firmware when joining new access points before joining the controller or do we need to upgrade the firmware on the controller. I am aware this is an older controller but the R500 is supported on this firmware version.

Responses

Brand User

Former Employee

 • 

2.6K Messages

 • 

44.8K Points

3 years ago

Are the ZD and AP on the same VLAN?  Do you see the AP in the DHCP lease table, and can you ping it (from a workstation or from the ZD)?

You might try flashing the AP with an older Solo AP image (which will join either ZD or SZ) that you can download here:
https://support.ruckuswireless.com/software/709-standalone-ap-software-100-1-0-0-194-all-aps 

3 Messages

 • 

90 Points

3 years ago

Yes, network connectivity is all good. I can see the device picking up a DHCP addresses and attempt to communicate with the controller. I will try an older firmware as you suggested. Thanks will post progress.

21 Messages

 • 

326 Points

3 years ago

Experiencing the same issue. Hopefully, there is a solution.

3 Messages

 • 

90 Points

3 years ago

Managed to get to the bottom of our issue . It was down to VLAN configuration on the switch. When the ap was updated it was set to use a particular VLAN and became unresponsive. Once we tagged the switch port with the correct VLAN I’d it responded to pings.