topic Re: R500 not compatible with ac-7260 in ZoneDirector

R500 not compatible with ac-7260

trevor_wright_6 — Wed, 12 Nov 2014 10:31:44 GMT

Just installed zd1100 and r500s, worked ok when eventually got hold of relevant firmware. (new customer) Having problems connecting tosh with intel ac7260. Seems problem is to do with channelfly and .h messages. Works if select one channel as this disable channelfly. (tried on standalone unit). Been asked to manually set channel in ZD as test but need to check interference. Other option to set run stop time. Running build 101 and have downloaded build 108 but not sure if it includes any fix. First ruckus install so not overly happy.
Trevor

Re: R500 not compatible with ac-7260

victor_tort — Wed, 12 Nov 2014 19:21:49 GMT

Hello Trevor,

Which version are you talking about?

Could you please elaborate a little bit more your tests and your results?

Re: R500 not compatible with ac-7260

michael_brado — Wed, 12 Nov 2014 22:55:56 GMT

Initial 9.8.0 GA release for R500/R700 had issue ZF-7357: Not using 2-stream rate with Intel 7260 2x2 11ac NICs.

Firmware builds 9.8.1.0.101+ have the fix to improve performance for these clients.

Next 9.8 MR2 release is expected in Nov14. Not sure if 5G background scanning
will be enabled or disabled by default. If not enabled, running ChannelFly for a
period of time will allow your APs to decide on other than channel 149. Stopping
it after a period of running, was recommended to prevent problems in .106/.108
interim builds.

Re: R500 not compatible with ac-7260

koen_verbeeck — Thu, 13 Nov 2014 16:57:11 GMT

Just disable channel fly and only use background scanning. Or just let channelfly run during the night when there are no clients (for about 6 hours) make sure to reboot all access point before you leave, you can configure this under radio group options and services. Also what version are u using? Is the client firmware supporting 202.11h channel change announcements.

Re: R500 not compatible with ac-7260

trevor_wright_6 — Thu, 13 Nov 2014 19:53:08 GMT

Newbie to Ruckus I believe disable command is via the command line
but I do not know the syntax, can you help.
ZD is 9.8.1.101.
Intel say they support 802.11h
running latest intel s/w.
T

Re: R500 not compatible with ac-7260

michael_brado — Fri, 14 Nov 2014 18:41:52 GMT

Hi Trevor,

The ZD WebUI is meant to be more user friendly than command line. From the
Configure tab, Services on the left, the boxes to configure 2.4/5G channel selection
(self healing) are found. We suggest to check the 5G box to enable Automatic
adjustment, and pick ChannelFly from the dropdown (rather than Bkgd Scanning).

Apply this change and let your APs use the algorithm which entails an off-channel
scan an building of an internal database with interference seen. After at least two
hours, the AP ought to have selected a better-than-default channel. You can then
change the ZD Configure/Services, and uncheck the 5G Automatically adjust box.

This only applies to 5G band when you have our newest 11ac AP models in use.
You can use background scanning or channelfly algorithm on your 2.4G channels,
and leave it running. I hope this is helpful.

Re: R500 not compatible with ac-7260

john_d — Sat, 15 Nov 2014 06:35:19 GMT

Thank you for this helpful suggestion! So just to clarify, I should check the automatically adjust power box for 5GHz on AC AP's? Does it do harm on a heterogeneous deployment of 7982's and R700's? Just trying to reconcile this with the General advice that ruckus recommends allowing Beamflex to do its thing instead of allowing the AP's to decrease their power levels.

Re: R500 not compatible with ac-7260

john_d — Sat, 15 Nov 2014 06:58:50 GMT

Never mind - looking at the ZD pane, it makes more sense. There's 3 settings that start with "Automatically Adjust", and you weren't implying to turn on the power reducing option.

Re: R500 not compatible with ac-7260

josh_hymer — Mon, 09 Nov 2015 15:56:50 GMT

We are having major issues with our R710 deployment. Looks like the Lenovo Chromebook N21s are using the same Intel 7260 card. Anyone having issues with these?

Re: R500 not compatible with ac-7260

neal_landry — Mon, 16 Nov 2015 20:36:41 GMT

I have had nothing but problems with the 7260 and my R710's. Impossible to recreate the issues for support, so we are left with a less functional wireless network.

Re: R500 not compatible with ac-7260

michael_brado — Mon, 16 Nov 2015 21:17:29 GMT

With most client adapters, using the latest drivers often provide latest fixes, both public and internal.
I've seen a couple posts in Intel/Microsoft forums that also provide client side settings that greatly improved performance (ie from 54mb to 866mbps)

I don't have a PC/Apple/Chromebook with this Intel adapter, only that this info/advice can be found on the web:

Driver version 17.0.3.2+

https://downloadcenter.intel.com/search?keyword=Intel%c2%ae+Dual+Band+Wireless-AC+7260

802.11n Channel Width for 2.4 GHz : Auto
802.11n Channel Width for 5.2 GHz : Auto
Ad Hoc Channel 802.11b/g : 1
Ad Hoc QoS Mode : WMM Disabled
ARP offload for WoWLAN : Enabled
Bluetooth(R) AMP : Enabled
Fat Channel Intolerant : Disabled
GTK rekeying for WoWLAN : Enabled
HT Mode : VHT Mode
Mixed Mode Protection : CTS-to-self Enabled
NS offload for WoWLAN : Enabled
Preferred Band : 1. No Preference
Roaming Aggressiveness : 5. Highest
Sleep on WoWLAN Disconnect : Disabled
Transmit Power : 5. Highest
U-APSD support : Disabled
Wake on Magic Packet : Enabled
Wake on Pattern Match : Enabled
Wireless Mode : 6. 802.11a/b/g

PS. The 54mb CU had TKIP on his WLAN, use WPA2/AES on PSK WLANs.

Re: R500 not compatible with ac-7260

josh_hymer — Mon, 16 Nov 2015 21:34:54 GMT

Unfortunately we cannot download drivers from Intel's site since they are Chromebooks. 😞

Re: R500 not compatible with ac-7260

gwehe_schilver — Mon, 16 Nov 2015 22:08:45 GMT

Hey, Michael Brado,
We need a CHROME solution.

Re: R500 not compatible with ac-7260

josh_hymer — Mon, 16 Nov 2015 22:16:57 GMT

Yes, we have an open case currently. 00344561. We just keep chasing our tails trying to figure out a solution. If you have any progress, please let me know. We are having major roaming issues and traffic delay issues. If we hardwire the connection we are good, or most other devices work pretty good.

Re: R500 not compatible with ac-7260

michael_brado — Mon, 16 Nov 2015 22:18:06 GMT

I'm sure both of the two companies who make your PC/radio card are trying to solve this too,

but browsing the Internet, I have found a suggested Chromebook fix:

I created a config.properties file in my
site folder and added the following line:

config.uapsd_enabled=false

and Provisioned the UAP

Re: R500 not compatible with ac-7260

josh_hymer — Mon, 16 Nov 2015 22:21:16 GMT

Can you link the site? I am not exactly sure where this is supposed to be entered. On the google management/Zone Director/Chromebook. Thank you for your quick response.

Re: R500 not compatible with ac-7260

josh_hymer — Mon, 16 Nov 2015 22:22:44 GMT

I think I found it.. We had these APs and just removed them for this reason.. interesting.
https://community.ubnt.com/t5/UniFi-Wireless/Problems-with-Intel-Dual-Band-Wireless-AC-7260-in-Lenov...

Re: R500 not compatible with ac-7260

michael_brado — Mon, 16 Nov 2015 22:23:45 GMT

I'm not admin-wise in the world of Chromebooks, so hope others on that platform can be of assistance.

Yours is the link where I found the advice.

Re: R500 not compatible with ac-7260

josh_hymer — Mon, 16 Nov 2015 22:27:22 GMT

Ok, yes, this fix is only for the Unfi wireless controller for Ubiquiti access points only. I made this exact change on our UBNT server and it helped. Unfortunately this is only a fix for Ubnt equipment only (Which is super cheap and we removed all the UAP-ACs about 1 month ago.). It is not for the very costly and well known wireless company Ruckus. 😞

Re: R500 not compatible with ac-7260

gwehe_schilver — Mon, 16 Nov 2015 22:31:08 GMT

So in other words... just to make sure an old guy like me understands..... The Ruckus r500's (and in my case the zf7363 AP's) cannot properly handle the "newer" intel AC-7260 wireless cards, forcing us to try a configuration change in a no-where-to -be-named application to fix a Ubiquity problem? DO I have the correct?