Ian, I could be misremembering, but I believe, at least on the 2800/3800, that the OS is based on Meraki's with the additional cisco pieces such as CAPWAP added-in. Also, the engineering team members I've worked with for the product are located in San Jose.
I do agree that there were growing pains with the launch of the 2800/3800s. You had a new underlying OS and new technology e.g. software-defined-radio sitting on top of it. We had a few challenges, but the engineering team in San Jose worked directly with us to resolve the problems. As for time to market. There are some enterprise WiFi vendors that use the same off-the-shelf chips and reference designs as the home router folks. There are other vendors that develop their own chips including radio code so they can innovate. Sometimes that innovation means you don't get to lay claim to "first to market." Jeff On 8/23/18, 7:03 AM, "Ian Lyons" <ily...@rollins.edu> wrote: Good point Lee My experience through the painful upgrade/failure was that Cisco doesn’t know the pain point. They kept saying, point blank, we were the only people having issues. I immediately whipped out my laptop and showed them that others were having issues. The blinking and open/closed mouths that ensued were comical until I realized I just went against everything they had believed. The end result was that my comment and documentation was ignored. The data did not line up with their expectations and was ignored. Further, the new AC code is BRAND NEW. The Aero code that runs all the older B,G,N ap's could not be upgraded to handle AC. So they started over...from scratch, without having bought a company. I watched our Cisco team call China and made live edits to kernel code and have it compiled in real time and packaged up for us to test the next day to solve our problems. My $.02, Cisco is a Marketing company and not an Engineering company (any more). They cut their QA dept and rushed product out the door so they wouldn’t be lapped. Aruba already had been shipping for 14 months a Wave 2 AC AP by the time a 1810/2802/3802 AP was rolled out. Even Belkin was announcing a Wave 2 AC AP the week our Cisco Ap's were shipped. I remember this as I was told it would be 1 month more before I got them and then they showed up. I joked with my sales guy, did the Belkin announcement scare you? We laughed.... However, the initial order of 500 AP's that I received, did not work. They all had bad code on them that prevented the devices from talking to the controller without manual configuration of the WLC on each AP. I think the local Cisco people are GREAT. Sales, Regional support, even TAC... However, the institution itself (cisco) concerns me. They rely on acquisitions to get new gear and struggle to incorporate the gear smoothly into their products. I am still waiting for Firepower 9300 to look anything remotely like a Checkpoint or Palo Alto NGFW Firewall. They no longer are the market leaders in tech. Aruba and Palo alto have superior products that work, right out of the gate. Ian -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> On Behalf Of Lee H Badman Sent: Thursday, August 23, 2018 9:33 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error One thing that Cisco has in its favor (my theory): most struggling customers don't know the scale of the code problems because they don't really talk to other customers. This list aggregates the pain and lays it bare for all to see, and it's very concerning. I'd love to see AireOS scrapped, personally. And a new management option for those of us who don't want hyper-bloated "unified" whatever. I don't know what would come next, but stability and reliability needs to be moved way, way up the priority list. -Lee -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> On Behalf Of Ian Lyons Sent: Thursday, August 23, 2018 8:25 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error As a result of the lack of QA, we removed all 1000 of our Cisco AP's and moved to Aruba. Since then, we have had zero problems. Cisco really needs to get their stuff together, their Wireless has not been an Enterprise level product, in my opinion. Ian -----Original Message----- From: The EDUCAUSE Wireless Issues Constituent Group Listserv <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> On Behalf Of Kenny, Eric Sent: Thursday, August 23, 2018 8:02 AM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error We were hit with the AID bug around this time last year on an 8.3 release. At the time the bug was a Sev 2 with Cisco. They provided an engineering release which we ran until the issue was finally resolved in later code. More proof that QA in large environments is lacking, to say the least. I’m with Bruce on this one, we are running Aruba 8.3.0.1 release and have used the live upgrades a few times now. The only issues we’ve seen with it are our mesh deployment, but I hear they are working on that. Client devices will roam as Joachim mentioned, but as long as you have roaming setup correctly, it’s almost always transparent to the user. ----------------------------------- Eric Kenny Network Architect Harvard University ITS ----------------------------------- > On Aug 23, 2018, at 7:33 AM, Osborne, Bruce W (Network Operations) <bosbo...@liberty.edu> wrote: > > Come over to the Intelligent Wi-Fi side! :D > > We just moved to Aruba 8.2.x this summer and are impressed with the automated RF management capabilities. We can now upgrade all or part of our wireless network with zero downtime. > > We also are in the process from moving from 3 independent systems (campus, remote, LPV) to a single unified system, simplifying configuration and adding more consistency.. > > Bruce Osborne > Senior Network Engineer > Network Operations - Wireless > > (434) 592-4229 > > LIBERTY UNIVERSITY > Training Champions for Christ since 1971 > > From: Lee H Badman [mailto:lhbad...@syr.edu] > Sent: Wednesday, August 22, 2018 4:20 PM > Subject: Re: Cisco - Field Notice - 70253 - Wireless Client Fails to > Associate: AID Error > > Is crazy- Cisco is up to 8.8.x on support site, but I hesitate to move from 8.2 MR7 as it actually works. Like hesitate to move, ever. EVER. > > -Lee Badman > > From: The EDUCAUSE Wireless Issues Constituent Group Listserv > <WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU> On Behalf Of Mccormick, Kevin > Sent: Wednesday, August 22, 2018 1:30 PM > To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU > Subject: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client > Fails to Associate: AID Error > > New field notice was published yesterday. > > https://www.cisco.com/c/en/us/support/docs/field-notices/702/fn70253.h > tml > > You may want to check if you are being affected. > > Following versions are affected. > > 8.0.150.0, 8.0.152.0 > 8.4.100.0 > 8.5.103.0 > > If you are running 8.0, TAC has 8.0MR5esc available. > > > Kevin McCormick > Network Administrator > University Technology - Western Illinois University > ke-mccorm...@wiu.edu | (309) 298-1335 | Morgan Hall 106b Connect with > uTech: Website | Facebook | Twitter > > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. > ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss. ********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/discuss.