Re: Cisco 8540s, and 8.3.102 Code

2016-09-20 Thread Earl Barfield
Date:Mon, 19 Sep 2016 10:03:18 -0400 From:Garret Peirce Subject: Re: Cisco 8540s, and 8.3.102 Code We run 8.3 on some new 8540s. We moved to 8.3 to resolve a DFS issue in 8.2 (CSCuy45955 - AP stops xmitting beacons after some # of DFS events). This is fairly silent btw, look for a deart

Re: [WIRELESS-LAN] Cisco 8540s, and 8.3.102 Code

2016-09-20 Thread Jeffrey D. Sessler
For those interested, 8.2.121.15 includes additional 3800-series fixes. 8.2MR3 is also in late beta and includes the same fixes. This link has info on participating in the beta along with the resolved items. https://supportforums.cisco.com/discussion/13123681/82mr3-beta-availability Jeff On 9

Planning a WISM2 to 8540 migration

2016-09-20 Thread Manon Lessard
Hi I'm currently in the process of planning our migration to Cisco 8540s. Having been managing gear since the ye old days of WLSM, I know I have to scrub the heck off my versions just in case some "feature" could cause harm, but would like the group's input on pitfalls, code versions, bugs encou

Re: [WIRELESS-LAN] Cisco 8540s, and 8.3.102 Code

2016-09-20 Thread Garret Peirce
re: CSCuy45955 (5G beacons cease) , no we've never enabled 11k support. Our engineer discovered this bug after investigating the condition and found it related to sensed DFS events. re: Our current issue with corrupt boot images: We've seen issue now in a handful of unique instances (APs = 3602i &

Re: [WIRELESS-LAN] Cisco 8540s, and 8.3.102 Code

2016-09-20 Thread Luke Jenkins
Have you gotten bug IDs for the FRA and 11k issues? On Tue, Sep 20, 2016 at 6:49 AM, Earl Barfield wrote: > Date:Mon, 19 Sep 2016 10:03:18 -0400 >> From:Garret Peirce >> Subject: Re: Cisco 8540s, and 8.3.102 Code >> >> We run 8.3 on some new 8540s. >> >> We moved to 8.3 to resolve a DF