Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Thanks for the input on that. We have another pair of 8540s I could try this with and see if it works. The current setup has been working for months with no issues then all of a sudden last week this all happened. Jason Mallon Network Engineer II, OIT The University of Alabama

RE: Cisco 8540 WLC random reboots

We had this issue very recently when upgrading our 8540s from 8.2.166.0 to 8.5.131.0 (MR3): A few days after the upgrade, the Standby 8540s started going through reboot loop, because it had an NaServCaCert_p12.pem certificate missing from the Active 8540. When the Standby can’t find the

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Sounds like we are going to wait for MR3 to come out now as well. Jason Mallon Network Engineer II, OIT The University of Alabama jemal...@ua.edu From: The EDUCAUSE Wireless Issues Constituent Group Listserv on behalf of Jess Walczak Reply-To: The

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Jason, My mistake, I misunderstood. Yeah, then, from others said, it would seem that our best bet is to get that MR3 version of 8.5.131.0. That is what our local Cisco SE told us to do when we met up with them in late June. Thanks!--JW On Mon, Jul 9, 2018 at 2:27 PM, Mallon, Jason wrote: >

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

We are on 8.5.120.0 with the 1815w APs as well. We are having an issue with the HA unit rebooting and going into maintenance mode, and when we try to fix it going into a boot loop. Jason Mallon Network Engineer II, OIT The University of Alabama

Re: Cisco 8540 WLC random reboots

This is something we're experiencing on a very limited scope right now on 8.2 MR6 interim. We are going to 8.2 MR7 this week and as soon as it gets to us we are going to 8.5 MR3 interim. We're not sure if it's an IPv6 issue or a mac issue or a wifi issue or a network core issue or. On

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Jason, FWIW, we run all of our 1815w APs on code version 8.5.120.0 in FlexConnect mode (although they worked when we tested them in Local mode as well). I thought you might like to know that you potentially don't need to run them on 8.4 code any longer. Thanks!--JW Jess Walczak Senior Network

Re: Cisco 8540 WLC random reboots

Yeah, you would need the 8.5 mr3 interim that's due out end of this month. On 7/9/2018 3:03 PM, Mallon, Jason wrote: We actually can’t run that code.  We have 1815w APs in place that require a code of 8.4.100, which is now a differed release. *Jason Mallon* Network Engineer II, OIT The

RE: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Hi All, Is there a general consensus that 8.5.131 is good code? We are working to solve an issue in short- our IPV6 wireless will drop off wireless (we are in testing now). Our next hope is that a code upgrade will fix the issue. If this doesn’t work we will circle back with TAC and y’all will

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

We actually can’t run that code. We have 1815w APs in place that require a code of 8.4.100, which is now a differed release. Jason Mallon Network Engineer II, OIT The University of Alabama jemal...@ua.edu From: The EDUCAUSE Wireless Issues

Re: Cisco 8540 WLC random reboots

I am curious what HA bug are you having an issue with an 8.5.131? Jason Mallon Network Engineer II, OIT The University of Alabama jemal...@ua.edu From: Rick Coloccia Date: Monday, July 9, 2018 at 12:17 PM To: The EDUCAUSE Wireless Issues Constituent

RE: [WIRELESS-LAN] Cisco 8540 WLC random reboots

We are running 8.2.167.3 in HA with no problem of 6ish months. Now I’ve jinxed it! From: The EDUCAUSE Wireless Issues Constituent Group Listserv On Behalf Of Alan D Wang Sent: Monday, July 9, 2018 1:27 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU Subject: Re: [WIRELESS-LAN] Cisco 8540 WLC random

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Do you have the bug ID for the major HA bug? On Mon, Jul 9, 2018 at 1:17 PM, Rick Coloccia wrote: > Hi, yes, it is, but the 8.5.131 code that is out now has a major HA bug > that is very hard to recover from. > > Cisco wireless engineers promised us code by the end of July that will > address

RE: [WIRELESS-LAN] Cisco 8540 WLC random reboots

We are on 8.2.151.0 on our 8540s and have not had any issues. Granted, we are also not using HA in our current design. -Erik From: The EDUCAUSE Wireless Issues Constituent Group Listserv On Behalf Of Rick Coloccia Sent: Monday, July 9, 2018 1:17 PM To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

Yes, we ran into this, as did other schools from what I hear. After working with TAC for quite awhile, they came out with 8.5.131.0 and that seems to fix the issue, as well as some other issues. Its been bug wack-a-mole since 8.5 code came out, but so far (*fingers crossed* *knock-on-wood*)

Re: Cisco 8540 WLC random reboots

Hi, yes, it is, but the 8.5.131 code that is out now has a major HA bug that is very hard to recover from. Cisco wireless engineers promised us code by the end of July that will address that issue. On 7/9/2018 1:15 PM, Swartz, Pola wrote: 8.5.131 code is available now. Smile, Pola On Jul

Re: [WIRELESS-LAN] Cisco 8540 WLC random reboots

8.5.131 code is available now. Smile, Pola On Jul 9, 2018, at 11:14 AM, Rick Coloccia mailto:coloc...@geneseo.edu>> wrote: Lots of bugs in 8.5.120, including some giant HA bugs. The version of 8.5.131 coming later this month is where you'll want to be. Specifically, one of the fixes in the

Re: Cisco 8540 WLC random reboots

Lots of bugs in 8.5.120, including some giant HA bugs. The version of 8.5.131 coming later this month is where you'll want to be. Specifically, one of the fixes in the version of 8.5 coming later this month deals with HA issues. On 7/9/2018 12:44 PM, Mallon, Jason wrote: We are currently

Cisco 8540 WLC random reboots

We are currently in the process of migrating to 8540s (8.5.120) from 8510s. Here recently we started noticing the HA unit on two of the pairs was in maintenance mode. We rebooted the controllers and they seem to have stayed in a continuous boot loop. We restarted one of the controllers to