Agreed. I'd go so far as to say that I have never seen or heard of a buggier product set than the AireOS WLCs. I can't imagine Airespace would have survived over time had Cisco not bought them to get into the thin AP paradigm given the chronic code issues.
Lee Badman | Network Architect (CWNE#200) Information Technology Services (NDD Group) 206 Machinery Hall 120 Smith Drive Syracuse, New York 13244 t 315.443.3003 e [email protected]<mailto:[email protected]> w its.syr.edu SYRACUSE UNIVERSITY syr.edu From: The EDUCAUSE Wireless Issues Community Group Listserv <[email protected]> On Behalf Of Gray, Sean Sent: Friday, July 17, 2020 10:57 AM To: [email protected] Subject: Re: [WIRELESS-LAN] Icing ISE 2.1 but where to jump Hopefully that means we are moving back to functionality over features for a few patches. That's certainly not been the case for newer WLC code trains Sean Gray | B.Sc (Hons) Voice, Collaboration & Wireless Network Analyst ITS, University of Lethbridge From: The EDUCAUSE Wireless Issues Community Group Listserv <[email protected]<mailto:[email protected]>> On Behalf Of Jake Snyder Sent: July 16, 2020 3:12 PM To: [email protected]<mailto:[email protected]> Subject: Re: [WIRELESS-LAN] Icing ISE 2.1 but where to jump Caution: This email was sent from someone outside of the University of Lethbridge. Do not click on links or open attachments unless you know they are safe. Please forward suspicious emails to [email protected]<mailto:[email protected]>. Typically I've monitored the release cycle on patches to determine how "bad" things were. In the olden days, Cisco would release a patch when a fixed number of serious issues were resolved. You could then track how many serious bugs were being fixed by the interval between patches. Quicker patches means more issues with a higher severity. If the intervals between patches went down, things were starting to stabilize. So if you saw a patch two months in a row, it might be a "let's wait for the next one." Not sure that will hold true, now that Cisco is saying that "all" releases will be stable-train moving forward for ISE. I see it's been a while from 2.7 to 2.7p1. That could be a good sign. Typically I would wait 2 months before upgrading to make sure there weren't repeated patches. You see this even with some long-lived trains that have patches 8,9,10,11 all very close together. On Jul 16, 2020, at 2:02 PM, Ciesinski, Nick <[email protected]<mailto:[email protected]>> wrote: ISE 2.7 is a stable release. Cisco released very few new features and instead focused a lot of bug fixes in 2.6 and 2.7. ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community ********** Replies to EDUCAUSE Community Group emails are sent to the entire community list. If you want to reply only to the person who sent the message, copy and paste their email address and forward the email reply. Additional participation and subscription information can be found at https://www.educause.edu/community
