Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID

[Jeffrey D. Sessler]

It’s important to separate marketing from the reality of how the technology 
functions.


  *   Band Steering – Cisco didn’t say it was impossible, what they said was 
that the client side of the equation was so fraught with issues that the 
feature would lead to greater problems, especially in diverse ecosystems such 
as education. That totally played out here, where the Aruba feature had to be 
disabled because it was causing a lot of issues.  In the central library, I 
could watch as Macs (in particular) would be bounced around like a hot potato. 
Even today, it’s a lot better, but clients are far better at making the right 
decision, so leaving the feature off, be it Cisco or Aruba, is a prudent idea.
  *   Spectrum Monitoring – Again, Aruba is/was dependent on what the 
off-the-shelf chipset is capable of. Perhaps this has improved in the latest 
AP’s, but we (and respected others in the field), found them rather blind to a 
lot of spectrum data that the CleanAir Cisco devices saw clearly – and 
significantly faster at detection of items the Aruba also saw. CleanAir AP’s 
have a dedicated equivalent of spectrum expert on them – they don’t need to use 
the client radios to do the work. It’s always on, always looking.
  *   Bugs – I don’t know the specifics on the current issues, but I know 
they’ve run into a number of show-stopper problems in the past. The controllers 
and APs are fairly new (24 months), so it’s not because they are running 
something unsupported. The companies you mention were customers before HP 
purchased Aruba. Given what the college’s here have expressed since the change, 
it would be difficult to speculate on their satisfaction under the new 
direction. It’s sort of like saying Cisco has 45% of the WiFi market, so with 
nearly a three-fold advantage over their nearest competitor, it’s surprising 
Toyota would go with a distant 2nd. Then again, companies often make decisions 
based on non-technical reasons e.g. joint marketing incentives, or because the 
alternative is a close partner with a competitor.




From: "wireless-lan@listserv.educause.edu"  
on behalf of "bosbo...@liberty.edu" 
Reply-To: "wireless-lan@listserv.educause.edu" 

Date: Friday, August 24, 2018 at 4:48 AM
To: "wireless-lan@listserv.educause.edu" 
Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client 
Fails to Associate: AID


Aruba introduced client band steering before we became their customer in 2008. 
At that time Cisco said band steering was not possible. Aruba has had spectrum 
monitoring since before Cisco’s CleanAir technology. We know who is following 
whom. That is why we made our choice.

Aruba has had ap preload for years but this is hands off seamless automated 
updating of controllers & APs.
.

I am very interested in what Aruba bugs have not been addressed, assuming they 
were running supported code. We work very closely with their support and they 
insure our needs are met. I am sure large companies like Microsoft, Google, & 
Toyota would not use Aruba if the support was lacking behind others.

With Aruba (& Cisco) one needs to move carefully when updating to insure the 
new version meets your stability requirements while fulfilling your needs.


The above is strictly my personal opinion and not that of my employer

Bruce Osborne
Senior Network Engineer
Network Operations - Wireless

 (434) 592-4229

LIBERTY UNIVERSITY
Training Champions for Christ since 1971

From: Jeffrey D. Sessler [mailto:j...@scrippscollege.edu]
Sent: Thursday, August 23, 2018 9:48 AM
Subject: Re: Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: 
AID Error

It’s great to hear Aruba is adding features such as “automated RF management” 
that Cisco has had for over a decade. In another ten years maybe they’ll catch 
up to Cisco’s CleanAir technology?  :D

In all seriousness,. if you’re talking specifically about AP updates, cisco has 
had AP code pre-download for years, resulting in between 2 to 4 minutes 
downtime when rebooting a multi-thousand AP controller. Not hitless, but low 
impact for sure.

If you make use of Prime 3.3 or above, you’ve got Rolling AP Upgrade, ensuring 
that AP’s are updated and rebooted in defined groups so that clients are 
minimally impacted i.e. they roam to another AP while an adjacent is being 
updated. It’s not hitless since the client must roam, but it’s as transparent 
as you’re going to get.

In my opinion, the only way we’re going to see better results for enterprise 
WiFi in EDU will be as customers transition to cloud-based managed-services. In 
this scenario, the vendor gains significant visibility on everything deployed 
in the field and isn’t waiting for a customer to decide to open a case and do 
all the necessary log/data collection e.g. Meraki.

The campuses in our consortium that had been on Aruba have been migrating to 
Cisco this summer. Since the purchase by HP, support and innovation h

RE: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Lee H Badman]

I can't say I love ClearPass (we use it) and the recent relicensing felt very 
much like yet another revenue grab. Not sure the grass is totally greener 
anywhere. If Mist would tone down the buzzword-driven marketing and start 
highlighting real-world value proposition and case studies of very large 
accounts, that could be interesting. Likewise, if Ubiquiti could get their 
enterprise approach together and stop feeling so wonky on the company side, 
they too could be interesting. I'll admit there where we use cloud-managed in 
our branches, I LOOOVE no keeping up controllers or NMS systems, as I've 
had years where I have spent months dealing with bugs on both. 

I do wish every WLAN company CEO would remind themselves that there are end 
users at the end of the string out there, and that stability trumps feature 
bloat and that phrases like "our new blood-sucking licensing insures you have 
access to INNOVATION!" just sound desperate. (Oh, and I want a pony, too!)

-Lee


-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
 On Behalf Of Osborne, Bruce W (Network 
Operations)
Sent: Friday, August 24, 2018 7:53 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client 
Fails to Associate: AID Error

Actually Aruba has moved from the "HA Pair" structure to a Cluster structure in 
AOS 8. We have 8 controllers in our Campus Cluster. Actually, the AP, SSID, & 
client can all be on different controllers within the cluster, each with a 
designated backup controller.

Since our cluster is split between 2 data centers, we have grouped the 
controllers so the standby is always in the opposite data center to the active 
one chosen.

Bruce Osborne
Senior Network Engineer
Network Operations - Wireless
 
 (434) 592-4229
 
LIBERTY UNIVERSITY
Training Champions for Christ since 1971

-Original Message-
From: Joachim Tingvold [mailto:joac...@tingvold.com]
Sent: Thursday, August 23, 2018 10:21 AM
Subject: Re: Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: 
AID Error

On 23 Aug 2018, at 15:48, Jeffrey D. Sessler wrote:
> It’s great to hear Aruba is adding features such as “automated RF 
> management” that Cisco has had for over a decade.

My understanding of the “automated RF management” part is directly related to 
the upgrade process (and not DCA/TPC, as you’re suggesting, which Aruba has had 
for some time).

It splits the APs automatically into groups based on their channel assignment 
(since, given similar approach as DCA, this gives a rough estimation on “APs 
that are overlapping each other” — could also be improved in the future using 
signal strength an AP sees other APs). 
It then moves clients off of one of those groups (making them join other, 
adjacent APs), reloading those clientless APs into the new software version, 
and then moves clients back when it moves onto the next “channel group”. 
Cleanse and repeat until all groups are done, giving you “zero downtime”.

This is at least how it was last time I read about it, and is by far superior 
to the way Cisco does it (where you manually have to fiddle with groups within 
Prime — and that’s without talking about Prime itself…).

The Cisco-solution also requires a separate controller to do this, whilst Aruba 
uses it’s redundant controller by automatically handling “splitting” the 
HA-pair (by upgrading one of them, moving the APs according to the “channel 
groups”, and then finally upgrading the last controller).

The “equivalent” with Cisco would be to split your HA pair manually, move all 
APs to one of them, upgrade the other, move them using the 
rolling-AP-group-thingie in Prime, then upgrade the last, and finally join them 
back as a HA, causing significantly more downtime than a normal Cisco upgrade 
process. Or you could buy a completely separate WLC to achieve this, but that’s 
somewhat a waste of money if you already do HA/SSO (and buy WLCs in pairs).

> In all seriousness,. if you’re talking specifically about AP updates, 
> cisco has had AP code pre-download for years, resulting in between 2 
> to 4 minutes downtime when rebooting a multi-thousand AP controller.
> Not hitless, but low impact for sure.

I’ve never managed to do less than ~400 seconds on HA/SSO-enabled 8540s with 
3k+ APs. That’s “a lot of time” many places (maybe not edu, but for sure in 
healthcare or other mission-critical businesses), which would be reduced to 
whatever time it takes for a client to re-associate after being “kicked” off 
the network (so time depends on the client, but would probably be sub-1s in 
many cases).

--
Joachim

**
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 b

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Tristan Gulyas]

Hi all,

We were hit in a very bad way by this bug last year and had it fixed in our 
engineering release that we're running now.  This bug delayed our migration to 
the 8540s by several months.

I am a little surprised that it's taken this long, given we first discovered 
this bug early last year.  We did have a workaround image and later a fix, 
supplied in our engineering code releases.

I can, however, confirm that the fix works.  The good news is that the issue 
doesn't affect COS-based APs.

Cheers,
Tristan
-- 
TRISTAN GULYAS
Senior Network Engineer

Technology Services, eSolutions
Monash University
738 Blackburn Road
Clayton 3168
Australia

T: +61 3 9902 9092  
E: tristan.gul...@monash.edu
monash.edu 

> On 23 Aug 2018, at 3:30 am, Mccormick, Kevin  wrote:
> 
> New field notice was published yesterday.
> 
> https://www.cisco.com/c/en/us/support/docs/field-notices/702/fn70253.html 
> 
> 
> 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.

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Jeffrey D. Sessler]

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"  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 
 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 
 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 
 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

  

RE: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Lee H Badman]

OK then.

-Original Message-
From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
 On Behalf Of Jeffrey D. Sessler
Sent: Thursday, August 23, 2018 10:32 AM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client 
Fails to Associate: AID Error

Here is my counter to your statement Lee:

Until I joined my neighborhood Nextdoor app, I had no idea that people were 
getting their mail stolen, animals taken by coyotes and mountain lions, 
unlocked cars ransacked, and so on. As I studied this, I realized that I was 
now seeing a small number of posts from a pool of nearly 12,000 members in the 
neighborhoods I was now connected to. I also noticed that the posts heavily 
skewing toward issues/problems vs positives. In my twenty years living in my 
neighborhood, I've never experienced one of these issues. Life is great, 
ignorance is bliss, and I'm not going to concern myself with a problem that 
appears to impact one tenth of one percent of the neighborhood population. 

You see, the Nextdoor Neighborhood app, like this forum, hyper-focuses on 
problems from a small subset of a vendor's overall installed base. It's not 
like people show up here and post a "best practice" for setting up a given 
technology/feature or talk about how awesome a new piece of tech is. It's a 
place to share and seek answers to problems, and like the Nextdoor app, it's 
sometimes difficult to believe that "life is great" for the vast majority of 
people. 

Jeff 


On 8/23/18, 6:32 AM, "The EDUCAUSE Wireless Issues Constituent Group Listserv 
on behalf of Lee H Badman"  wrote:

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 
 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 
 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) 
 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 E

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Jeffrey D. Sessler]

Here is my counter to your statement Lee:

Until I joined my neighborhood Nextdoor app, I had no idea that people were 
getting their mail stolen, animals taken by coyotes and mountain lions, 
unlocked cars ransacked, and so on. As I studied this, I realized that I was 
now seeing a small number of posts from a pool of nearly 12,000 members in the 
neighborhoods I was now connected to. I also noticed that the posts heavily 
skewing toward issues/problems vs positives. In my twenty years living in my 
neighborhood, I've never experienced one of these issues. Life is great, 
ignorance is bliss, and I'm not going to concern myself with a problem that 
appears to impact one tenth of one percent of the neighborhood population. 

You see, the Nextdoor Neighborhood app, like this forum, hyper-focuses on 
problems from a small subset of a vendor's overall installed base. It's not 
like people show up here and post a "best practice" for setting up a given 
technology/feature or talk about how awesome a new piece of tech is. It's a 
place to share and seek answers to problems, and like the Nextdoor app, it's 
sometimes difficult to believe that "life is great" for the vast majority of 
people. 

Jeff 


On 8/23/18, 6:32 AM, "The EDUCAUSE Wireless Issues Constituent Group Listserv 
on behalf of Lee H Badman"  wrote:

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 
 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 
 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) 
 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 
>  On Behalf Of Mccormick, Kevin
   

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Joachim Tingvold]

On 23 Aug 2018, at 15:48, Jeffrey D. Sessler wrote:
It’s great to hear Aruba is adding features such as “automated RF 
management” that Cisco has had for over a decade.


My understanding of the “automated RF management” part is directly 
related to the upgrade process (and not DCA/TPC, as you’re suggesting, 
which Aruba has had for some time).


It splits the APs automatically into groups based on their channel 
assignment (since, given similar approach as DCA, this gives a rough 
estimation on “APs that are overlapping each other” — could also 
be improved in the future using signal strength an AP sees other APs). 
It then moves clients off of one of those groups (making them join 
other, adjacent APs), reloading those clientless APs into the new 
software version, and then moves clients back when it moves onto the 
next “channel group”. Cleanse and repeat until all groups are done, 
giving you “zero downtime”.


This is at least how it was last time I read about it, and is by far 
superior to the way Cisco does it (where you manually have to fiddle 
with groups within Prime — and that’s without talking about Prime 
itself…).


The Cisco-solution also requires a separate controller to do this, 
whilst Aruba uses it’s redundant controller by automatically handling 
“splitting” the HA-pair (by upgrading one of them, moving the APs 
according to the “channel groups”, and then finally upgrading the 
last controller).


The “equivalent” with Cisco would be to split your HA pair manually, 
move all APs to one of them, upgrade the other, move them using the 
rolling-AP-group-thingie in Prime, then upgrade the last, and finally 
join them back as a HA, causing significantly more downtime than a 
normal Cisco upgrade process. Or you could buy a completely separate WLC 
to achieve this, but that’s somewhat a waste of money if you already 
do HA/SSO (and buy WLCs in pairs).


In all seriousness,. if you’re talking specifically about AP 
updates, cisco has had AP code pre-download for years, resulting in 
between 2 to 4 minutes downtime when rebooting a multi-thousand AP 
controller. Not hitless, but low impact for sure.


I’ve never managed to do less than ~400 seconds on HA/SSO-enabled 
8540s with 3k+ APs. That’s “a lot of time” many places (maybe not 
edu, but for sure in healthcare or other mission-critical businesses), 
which would be reduced to whatever time it takes for a client to 
re-associate after being “kicked” off the network (so time depends 
on the client, but would probably be sub-1s in many cases).


--
Joachim

**
Participation and subscription information for this EDUCAUSE Constituent Group 
discussion list can be found at http://www.educause.edu/discuss.

RE: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Ian Lyons]

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 
 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 
 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 
 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) 
>  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. 
>

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Jeffrey D. Sessler]

It’s great to hear Aruba is adding features such as “automated RF management” 
that Cisco has had for over a decade. In another ten years maybe they’ll catch 
up to Cisco’s CleanAir technology?  :D

In all seriousness,. if you’re talking specifically about AP updates, cisco has 
had AP code pre-download for years, resulting in between 2 to 4 minutes 
downtime when rebooting a multi-thousand AP controller. Not hitless, but low 
impact for sure.

If you make use of Prime 3.3 or above, you’ve got Rolling AP Upgrade, ensuring 
that AP’s are updated and rebooted in defined groups so that clients are 
minimally impacted i.e. they roam to another AP while an adjacent is being 
updated. It’s not hitless since the client must roam, but it’s as transparent 
as you’re going to get.

In my opinion, the only way we’re going to see better results for enterprise 
WiFi in EDU will be as customers transition to cloud-based managed-services. In 
this scenario, the vendor gains significant visibility on everything deployed 
in the field and isn’t waiting for a customer to decide to open a case and do 
all the necessary log/data collection e.g. Meraki.

The campuses in our consortium that had been on Aruba have been migrating to 
Cisco this summer. Since the purchase by HP, support and innovation has waned, 
with bugs they’ve hit not being addressed. Clearly, like the difference in mu 
and Lee’s Cisco experience, it’s not all rainbows and unicorns on the Aruba 
side either.

Jeff



From: "wireless-lan@listserv.educause.edu"  
on behalf of "bosbo...@liberty.edu" 
Reply-To: "wireless-lan@listserv.educause.edu" 

Date: Thursday, August 23, 2018 at 4:33 AM
To: "wireless-lan@listserv.educause.edu" 
Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client 
Fails to Associate: AID Error

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 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
On Behalf Of Mccormick, Kevin
Sent: Wednesday, August 22, 2018 1:30 PM
To: 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto: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.html

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<https://www.youracclaim.com/user/kevin-mccormick>
Network Administrator
University Technology - Western Illinois University
ke-mccorm...@wiu.edu<mailto:ke-mccorm...@wiu.edu> | (309) 
298-1335 | Morgan Hall 106b
Connect with uTech: Website<http://www.wiu.edu/utech> | 
Facebook<https://www.facebook.com/uTechWIU> | 
Twitter<https://twitter.com/WIU_uTech>
[http://www.wiu.edu/university_technology/images/signatures/currentimage.jpg]
** 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.

RE: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Lee H Badman]

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 
 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 
 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) 
>  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 
>  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 

RE: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Ian Lyons]

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 
 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) 
>  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 
>  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.

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Kenny, Eric]

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) 
>  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 
>  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.html
> 
> 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.

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Lee H Badman]

8.2.167.3 here

From: The EDUCAUSE Wireless Issues Constituent Group Listserv 
 on behalf of Jason Watts 
Sent: Wednesday, August 22, 2018 4:56:14 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client 
Fails to Associate: AID Error

Lee,

When you say 8.2 MR7 are you specifically referring to 8.2.167.204?

Another thing that annoys me about Cisco is the abstruse range of naming and 
versioning formats for software releases and code trains. But I suppose this is 
a lot of vendors these days. /rant

Jason Watts | Senior Network Administrator

PRATT INSTITUTE


On Wed, Aug 22, 2018 at 4:20 PM Lee H Badman 
mailto:lhbad...@syr.edu>> wrote:
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 
mailto:WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU>> 
On Behalf Of Mccormick, Kevin
Sent: Wednesday, August 22, 2018 1:30 PM
To: 
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU<mailto: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.html

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<https://www.youracclaim.com/user/kevin-mccormick>
Network Administrator
University Technology - Western Illinois University
ke-mccorm...@wiu.edu<mailto:ke-mccorm...@wiu.edu> | (309) 
298-1335 | Morgan Hall 106b
Connect with uTech: Website<http://www.wiu.edu/utech> | 
Facebook<https://www.facebook.com/uTechWIU> | 
Twitter<https://twitter.com/WIU_uTech>
[http://www.wiu.edu/university_technology/images/signatures/currentimage.jpg]
** 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.

Re: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Jason Watts]

Lee,

When you say 8.2 MR7 are you specifically referring to 8.2.167.204?

Another thing that annoys me about Cisco is the abstruse range of naming
and versioning formats for software releases and code trains. But I suppose
this is a lot of vendors these days. /rant

*Jason Watts* | Senior Network Administrator

*PRATT INSTITUTE*


On Wed, Aug 22, 2018 at 4:20 PM Lee H Badman  wrote:

> 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.html
>
> 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 <https://www.youracclaim.com/user/kevin-mccormick>
>
> Network Administrator
>
> University Technology - Western Illinois University
>
> ke-mccorm...@wiu.edu | (309) 298-1335 <3092981335> | Morgan Hall 106b
>
> Connect with uTech: Website <http://www.wiu.edu/utech> | Facebook
> <https://www.facebook.com/uTechWIU> | Twitter
> <https://twitter.com/WIU_uTech>
>
> ** 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.

RE: [WIRELESS-LAN] Cisco - Field Notice - 70253 - Wireless Client Fails to Associate: AID Error

[Lee H Badman]

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 
 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.html

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<https://www.youracclaim.com/user/kevin-mccormick>
Network Administrator
University Technology - Western Illinois University
ke-mccorm...@wiu.edu<mailto:ke-mccorm...@wiu.edu> | (309) 
298-1335 | Morgan Hall 106b
Connect with uTech: Website<http://www.wiu.edu/utech> | 
Facebook<https://www.facebook.com/uTechWIU> | 
Twitter<https://twitter.com/WIU_uTech>
[http://www.wiu.edu/university_technology/images/signatures/currentimage.jpg]
** 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.