Is there a way to find out why a controller seems to intermittently drop off the network?
I had a call about the wireless network seeming to drop off every 10 minutes or so. Of course when I checked the controller and APs were up (uptime of 19 days), and ran a continuous ping to the controller with no drops for close to an hour.
When I called the user it turned into a "one user couldn't connect" type of issue, although I did see some messages in the event log about our RADIUS server being unreachable.
As there were other users connected, I wrote it off as a user issue.
Of course approx 30 minutes later, the ping on the controller dropped. Called user and the controller was up, but no link light on the Gig 1/8 port. Verified cable, unplugged and plugged back in, still no light. Checked Cisco switch and no issues on that port (uptime of 19 weeks). Shut the port and no shut the port - still no link on the controller. Had user pull power cord and replug......eventually controller came back up.
Continued to ping and eventually dropped the connection, but did come back up (missed about 20 pings).
Checking the event log, found these messages:
2017-06-27 | 18:23:59 | Link 4105 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | Physical port 1/8 is down. Admin state is 1 operational state is 2 |
2017-06-27 | 18:23:59 | Link 20483 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | VLAN 2 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | VLAN 2 configuration has changed. Change type is 3 |
2017-06-27 | 18:23:59 | Link 20484 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | VLAN 110 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | VLAN 110 configuration has changed. Change type is 3 |
2017-06-27 | 18:23:59 | Link 20482 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | VLAN 4095 is down. Admin status is 1; oper status is 2 |
2017-06-27 | 18:23:59 | VLAN 4095 configuration has changed. Change type is 3 |
2017-06-27 | 18:24:13 | Link 4105 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:13 | Physical port 1/8 is up. Admin state is 1 operational state is 1 |
2017-06-27 | 18:24:47 | Link 20483 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:47 | VLAN 2 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:47 | VLAN 2 configuration has changed. Change type is 3 |
2017-06-27 | 18:24:47 | Link 20484 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:47 | VLAN 110 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:47 | VLAN 110 configuration has changed. Change type is 3 |
2017-06-27 | 18:24:47 | Link 20482 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:47 | VLAN 4095 is up. Admin status is 1; oper status is 1 |
2017-06-27 | 18:24:47 | VLAN 4095 configuration has changed. Change type is 3 |
2017-06-27 | 18:26:17 | Resource 1 :: Controlpath CPU has exceeded 45% threshold (actual:52%). |
2017-06-27 | 18:27:17 | Resource 1 :: Controlpath CPU has dropped below 45% threshold (actual:0%). |
Is there anything I can do to see why the controller may be dropping out? This is a 620 controller, running 6.4.2.3 firmware.