Because it adds overhead and slows down the processors on the M series. Rory
From: [email protected] [mailto:[email protected]] On Behalf Of Matt Hoppes Sent: Sunday, March 12, 2017 8:43 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs Out of curiosity why was this not turned on already? AC should be able to script it. If not I can script it for you. On Mar 12, 2017, at 11:41, Rory Conaway <[email protected]<mailto:[email protected]>> wrote: We have confirmed that extra reporting has to be on for AC APs to see the detail information on the stations button. So, I have hundreds of radios that now need that feature turned on. Is there a script or some option in AirControl that I’m missing so I don’t have to log in manually and do 800+ radios? Or possibly is this something that can simply go into a firmware upgrade and fix? Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rory Conaway Sent: Wednesday, March 1, 2017 7:17 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs Nope, no difference. Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rory Conaway Sent: Wednesday, March 1, 2017 7:14 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs Didn’t make an immediate difference. I’m going to try and reboot the AP and see if it sees it then. Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Mike Hammett Sent: Wednesday, March 1, 2017 6:57 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs What about extra reporting? That one seems more important than the AirMax setting. ----- Mike Hammett Intelligent Computing Solutions<http://www.ics-il.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/ICSIL>[http://www.ics-il.com/images/googleicon.png]<https://plus.google.com/+IntelligentComputingSolutionsDeKalb>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/intelligent-computing-solutions>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/ICSIL> Midwest Internet Exchange<http://www.midwest-ix.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/mdwestix>[http://www.ics-il.com/images/linkedinicon.png]<https://www.linkedin.com/company/midwest-internet-exchange>[http://www.ics-il.com/images/twittericon.png]<https://twitter.com/mdwestix> The Brothers WISP<http://www.thebrotherswisp.com/> [http://www.ics-il.com/images/fbicon.png]<https://www.facebook.com/thebrotherswisp>[http://www.ics-il.com/images/youtubeicon.png]<https://www.youtube.com/channel/UCXSdfxQv7SpoRQYNyLwntZg> ________________________________ From: "Rory Conaway" <[email protected]<mailto:[email protected]>> To: "Ubiquiti Users Group" <[email protected]<mailto:[email protected]>> Sent: Wednesday, March 1, 2017 7:55:20 AM Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs So what’s weird is that I have a second Rocket AC that has 45 clients on it, and 3 of them came up with names. The rest are blank. I checked the AirMax settings and all of them are set at Base, the ones that came up and the ones that don’t. On the ones that came up, the distance is correct. Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rory Conaway Sent: Tuesday, February 28, 2017 11:51 PM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs We will be testing that tonight. Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jesse DuPont Sent: Tuesday, February 28, 2017 5:47 PM To: Ubiquiti Users Group <[email protected]<mailto:[email protected]>> Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs Agreed. But it is relevant to the general priority upstream traffic from the SM is given, including this meta information. I shouldn't have had to change it from NONE to get them to stay reliably reachable and passing traffic, but alas, I did so there's something there. Anyway, I wasn't necessarily advocating that he should have to change it, I was more saying that "this" is what I have, how is it different from yours, since our experience was different. I also agree, probably just Extra Reporting is disabled on the SMs. Jesse DuPont Network Architect email: [email protected]<mailto:[email protected]> Celerity Networks LLC Celerity Broadband LLC Like us! facebook.com/celeritynetworksllc<http://facebook.com/celeritynetworksllc> Like us! facebook.com/celeritybroadband<http://facebook.com/celeritybroadband> <image001.png> On 2/28/17 2:32 PM, Josh Luthman wrote: I don't believe Airmax priority is relevant to the extra reporting... Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Tue, Feb 28, 2017 at 4:08 PM, Jesse DuPont <[email protected]<mailto:[email protected]>> wrote: Yeah, not so much turning AirMax off, but setting the AirMax Priority to something other than None. Jesse DuPont Network Architect email: [email protected]<mailto:[email protected]> Celerity Networks LLC Celerity Broadband LLC Like us! facebook.com<http://facebook.com>/celeritynetworksllc Like us! facebook.com<http://facebook.com>/celeritybroadband <image002.png> On 2/28/17 1:52 PM, Josh Luthman wrote: I've always had it on. I can't remember ever seeing it off... Josh Luthman Office: 937-552-2340<tel:%28937%29%20552-2340> Direct: 937-552-2343<tel:%28937%29%20552-2343> 1100 Wayne St Suite 1337 Troy, OH 45373 On Feb 28, 2017 3:41 PM, "Rory Conaway" <[email protected]<mailto:[email protected]>> wrote: I will check. I know we have extra reporting turned off as that was pretty much mandatory in earlier versions of firmware on the 802.11n radios. We never turned on extra reporting on the CPE side, never had any reason to. We usually didn’t enable it unless we had an issue we were troubleshooting. Jesse, I will make those changes also and see what happens. I believe that client radios automatically detect AirMax and turn on so I don’t believe we ever turned it on manually. Do those changes also fix the distance calculation? Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of James Craig via Ubnt_users Sent: Tuesday, February 28, 2017 11:54 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs Hi Rory, Any chance that you have Extra Reporting disabled on the M units? Does re-enabling help? Steve: We have replaced AMC/AMQ with isolated capacity. It should provide better insight to expected performance and in what direction any possible issues might be. The legacy AC2 java interface doesn't support Isolated Capacity, but this has been added into the replacement HTML5 AC2 client (available in 2.1beta+). On Tue, Feb 28, 2017 at 8:31 AM, Steve Barnes <[email protected]<mailto:[email protected]>> wrote: This is the first time I heard of this Rory. This bothers me greatly. I had not tried a AirPrism with only 6.0 clients. I have only used 8.0 AP with new towers with 8.0 clients. If you put a 8.0 client on that AP will their info show? Ben Moore: Is UBNT doing anything about this? That is missing A LOT of important data. Name, device, TX signal would really bother me. Also why does UBNT call these AP PtMP airMAX AC is they do not show the AMQ or AMC anywhere. WE cant use that in AC2 to see the quality of the links. Steve Barnes Wireless Operations Manager New Lisbon Broadband NLBC.COM<http://NLBC.COM> PCSWIN.COM<http://PCSWIN.COM> 765-584-2288 ext:1101<tel:%28765%29%20584-2288> From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Rory Conaway Sent: Monday, February 27, 2017 6:44 PM To: Ubiquiti Users Group <[email protected]<mailto:[email protected]>> Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs <image003.jpg> This is what I’m talking about with 6.0 clients. No names and the distances are screwed up. Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Rory Conaway Sent: Monday, February 27, 2017 8:59 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs I’ll have to look but why would that matter? 8.0 APs were showing 8.0 clients but not 6.0 client names. 6.0 aren’t showing any client names. Rory From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jesse DuPont Sent: Monday, February 27, 2017 8:02 AM To: Ubiquiti Users Group Subject: Re: [Ubnt_users] 6.0 Firmware not showing Device Names of clients on APs Rory, What is the AirMax Priority set to on your stations having issues on 6.0? Jesse DuPont Network Architect email: [email protected]<mailto:[email protected]> Celerity Networks LLC Celerity Broadband LLC Like us! facebook.com/celeritynetworksllc<http://facebook.com/celeritynetworksllc> Like us! facebook.com/celeritybroadband<http://facebook.com/celeritybroadband> <image004.png> On 2/27/17 6:56 AM, Clay Stewart wrote: No issues here, but make sure every client is upgraded too. Saw improvements, especially in 900Mhz rockets. On Sat, Feb 25, 2017 at 10:28 PM, Roy <[email protected]<mailto:[email protected]>> wrote: XW 6.0 seems to be fine. Clients are on XM 6.0. Uptime is 8 days so stability seems to be OK. Reason for 8 days was the massive power outage caused tby the storm in Northern CA. On 2/25/2017 5:17 PM, Rory Conaway wrote: Anyone else having this issue? Rory Conaway • Triad Wireless • CEO 4226 S. 37th Street • Phoenix • AZ 85040 602-426-0542<tel:%28602%29%20426-0542> [email protected]<mailto:[email protected]> www.triadwireless.net<http://www.triadwireless.net/> “Baseball - we do not stop playing because we grow old, we grow old because we stop playing” _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list [email protected]<mailto:[email protected]> http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________ Ubnt_users mailing list [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
