Craig Mullen
asked on
Cisco 1832 random reboots when connected to Virtual Wireless Controller
Hi Guys
I have a Cisco Virtual Wireless Controller (Software Version 8.4.100.0) managing 13 Access Points across two sites, one local, one remote connected via a Site-to-Site VPN. I have two models of Access Point connected;
Local Site:
2x Cisco AIR-AP1832I-E-K9
7x Cisco AIR-CAP1602I-E-K9
Remote Site:
3x Cisco AIR-AP1832I-E-K9
1x Cisco AIR-CAP1602I-E-K9
At our remote site, all Access Points are up and stable, and have been for 19 days as of right now. Friday 18th August I configured the 9 Access Points at our local site and left the office with everything working.
On Monday at 9AM, they were still working and had been connected to the controller all weekend, but by 10AM the two Cisco 1832's had dropped off and weren't pingable. I started looking into it and they were rebooting after suffering a "Kernel Panic". I did a factory reset on one of the points, reconnected to the controller and seemed stable, until I disconnected and reconnected the AP, and it couldn't find the controller again, crashing with the same "Kernel Panic" error (Which I appreciate is generic).
Then, as I was leaving at about 5PM, they suddenly both reconnected to the controller and were both up, and stable, until 12PM today (Tuesday), where they dropped off again. One has come back up, one hasn't, but they only dropped off after I rebooted one of the Cisco 1602's. Now, I can consistently get the AP's to drop off the controller when rebooting an unrelated access point.
I've been workign on this now for almost two full days, and I'm no closer to resolving the issue. I've attached the log from one of the AP's that's crashing. Any help would be greatly appreciated.
AP-3.txt
I have a Cisco Virtual Wireless Controller (Software Version 8.4.100.0) managing 13 Access Points across two sites, one local, one remote connected via a Site-to-Site VPN. I have two models of Access Point connected;
Local Site:
2x Cisco AIR-AP1832I-E-K9
7x Cisco AIR-CAP1602I-E-K9
Remote Site:
3x Cisco AIR-AP1832I-E-K9
1x Cisco AIR-CAP1602I-E-K9
At our remote site, all Access Points are up and stable, and have been for 19 days as of right now. Friday 18th August I configured the 9 Access Points at our local site and left the office with everything working.
On Monday at 9AM, they were still working and had been connected to the controller all weekend, but by 10AM the two Cisco 1832's had dropped off and weren't pingable. I started looking into it and they were rebooting after suffering a "Kernel Panic". I did a factory reset on one of the points, reconnected to the controller and seemed stable, until I disconnected and reconnected the AP, and it couldn't find the controller again, crashing with the same "Kernel Panic" error (Which I appreciate is generic).
Then, as I was leaving at about 5PM, they suddenly both reconnected to the controller and were both up, and stable, until 12PM today (Tuesday), where they dropped off again. One has come back up, one hasn't, but they only dropped off after I rebooted one of the Cisco 1602's. Now, I can consistently get the AP's to drop off the controller when rebooting an unrelated access point.
I've been workign on this now for almost two full days, and I'm no closer to resolving the issue. I've attached the log from one of the AP's that's crashing. Any help would be greatly appreciated.
AP-3.txt
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I do, see attached.
I formatted both AP's yesterday to different versions (One to 8.5.103.0 and one to 8.2.151.0), once they connect to the Controller, they downgrade/upgrade to the same version as the Controller (8.4.100.0) and have the same issue. It could potentially be the version supplied by the Controller is corrupt? I'd be surprised as the other 11 AP's using that version are fine, but at this point I'll try anything.
AP-3-paniclog.rtf
AP-7-paniclog.rtf
I formatted both AP's yesterday to different versions (One to 8.5.103.0 and one to 8.2.151.0), once they connect to the Controller, they downgrade/upgrade to the same version as the Controller (8.4.100.0) and have the same issue. It could potentially be the version supplied by the Controller is corrupt? I'd be surprised as the other 11 AP's using that version are fine, but at this point I'll try anything.
AP-3-paniclog.rtf
AP-7-paniclog.rtf
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hope this helped.
ASKER
I've been down the PoE route and tried with a DC Adapter, and tried different sized cables and different network ports and points around the building, same issue. Someone on the Cisco forums has suggested a downgrade on the Controller to 8.2.141.0 as it's a more stable release. Not sure if you have any thoughts on that?