Wich stable FW for both ZD1100,1200,3000 and some standalone AP ?

  • 1
  • Question
  • Updated 2 years ago
Hi

I have some problems with the lastest FW... they are no more universal for ZD controled AP, and standalone AP...

I need one who work whith all my models of Zone directors (actually 1100,1200 and 3K) ans also who let the AP working in standalone mode.

We deploy often for temporary using and sometime the timming is very short and the time to deploy sandalone FW is not aviable.

the AP we used are: ZF7982, 7372, 7782S, R700, T301n and t301s.

Thanks.
Photo of Jean-Pierre Fourrier

Jean-Pierre Fourrier

  • 8 Posts
  • 1 Reply Like

Posted 2 years ago

  • 1
Photo of Sean

Sean

  • 346 Posts
  • 88 Reply Likes
9.8.3.0.14 (MR3) is the build that you need as its supported by all your hardware:

https://support.ruckuswireless.com/software/793-standalone-ap-software-9-8-3-0-14-all-aps

Good Luck
Photo of Michael Brado

Michael Brado, Official Rep

  • 2106 Posts
  • 297 Reply Likes
While ZD 9.8.3 is the latest ZoneDirector firmware to support all those AP models, you can run Standalone image 100.1.0.0.432 where you need/want to.

7982, 7372, R700 use this:
https://support.ruckuswireless.com/software/838-standalone-ap-software-100-1-0-0-432-indoor-aps
7782s, T301n, T301s use this:
https://support.ruckuswireless.com/software/839-standalone-ap-software-100-1-0-0-432-outdoor-aps

APs running the Standalone 100.x firmware, can be directed to connect to a ZD with DHCP option 43, DNS 'director.localdomain', or manual AP CLI 'set director ip a.b.c.d (a.b.c.e)' commands.
(Edited)
Photo of John D

John D, AlphaDog

  • 497 Posts
  • 137 Reply Likes
Wow, I didn't know that was doable, and the ZD won't try to upgrade the firmware on the standalone AP's? What's the range of backwards compatibility for this? 100.1.0.0.432 seems a lot like 9.12.1 MR refresh — if ZD1100 can manage it, it seems to breathe some new life into it for managing AC AP's.
Photo of Michael Brado

Michael Brado, Official Rep

  • 2106 Posts
  • 297 Reply Likes
Yes, a ZD will re-flash any Standalone AP to whatever version the ZD is running (ie 9.8.3.0.14).
But..., APs being used as Standalone, ie. not on the same VLAN/subnet or at the same location, can run the 100.1.0.0.432 (similar to ZD 9.12.1 MR) features and bug fixes.
Photo of Sean

Sean

  • 346 Posts
  • 88 Reply Likes
You need to issue the following command on the AP's to get them to join a SZ, SCG, ZD, as it is not always on by default:
set discovery-agent enabled

To prevent the AP's joining a ZD etc. you simply issue this:

set discovery-agent disabled
(Edited)
Photo of Jim Michael

Jim Michael

  • 37 Posts
  • 11 Reply Likes
In my experience there IS no stable build for ZD1100 with Rxx APs. Hoping the forthcoming 9.10.2 fixes the current connectivity issues.
Photo of Sean

Sean

  • 346 Posts
  • 88 Reply Likes
what connectivity issues?

are you on about hearbeat timeout issues?
Photo of Jim Michael

Jim Michael

  • 37 Posts
  • 11 Reply Likes
Biggest issue currently is that APs will (seemingly) randomly stop authenticating clients (just normal WPA2 PSK clients). In the ZD you will then see clients on that AP being "blocked for too many failed attempts" and the clients start re-prompting for valid credentials. Restarting the affected AP immediately fixes the issue. Because of the randomness (both in time between occurrences and in which AP is affected) my theory is that some "bad" device is entering the network and the AP doesn't handle it well. In any case, it's extremely frustrating to have to routinely reboot APs to keep them working. I miss the glory days of 7962s that were exceedingly stable. And don't even get me started on the practice of Ruckus releasing new APs with features missing (airtime fairness on 5g, wlan prioritization, etc). Grrrr.
Photo of Sean

Sean

  • 346 Posts
  • 88 Reply Likes
I thought they had solved most of the client connectivity issues in 9.8 MR3, for the r700 at least anyway.

The only one they have not fixed that I am aware of is when you have force DHCP enabled and the clients cannot roam (I found this one myself and am eagerly awaiting a fix)

ATF for the 5GHz is going to take some time for 802.11ac, as most other vendors have opted to use 3 radio AP's (the 3rd radio being 802.11ac clients only)
(Edited)