Skip to main content
D

Mon, Apr 5, 2021 9:42 PM

R510 keeps dropping connections and going offline for few min after latest patch kernel panic

R510 keeps dropping connections and going offline for few min after latest patch 200.9.10.4.233

2021/04/05  16:19:54
High
Radio [5G] of AP[Downstairs@90:3a:72:11:18:30] is ON
2021/04/05  16:19:54
High
Radio [2.4G] of AP[Downstairs@90:3a:72:11:18:30] is ON
2021/04/05  16:18:49
High
AP[Downstairs@90:3a:72:11:18:30] warm boot successfully,last reboot reason [kernel panic].
2021/04/05  16:18:46
High
AP[Downstairs@90:3a:72:11:18:30] joins with uptime [73] s and last disconnected reason [AP Restart : kernel panic]
2021/04/05  16:16:52
High
Radio [2.4G] of AP[Downstairs@90:3a:72:11:18:30] is OFF
2021/04/05  16:16:43
High
URL Filtering is disabled due to insufficient license
2021/04/05  16:06:11
High
Radio [5G] of AP[Downstairs@90:3a:72:11:18:30] is ON
2021/04/05  16:06:11
High
Radio [2.4G] of AP[Downstairs@90:3a:72:11:18:30] is ON
2021/04/05  16:05:59
High
Unleashed network change master role from [Downsta
2021/04/05  16:05:08
High
AP[Upstairs@18:4b:0d:36:16:90] joins with uptime [1303] s and last disconnected reason [Heartbeat Loss]
2021/04/05  16:05:07
High
AP[Downstairs@90:3a:72:11:18:30] warm boot successfully,last reboot reason [kernel panic].
2021/04/05  16:05:05
High
AP[Downstairs@90:3a:72:11:18:30] joins with uptime 

Responses

Employee

 • 

57 Messages

 • 

1K Points

6 d ago

Hi Dariusz,

Greeting from CommScope/Ruckus. As per the issue described you would need to open a support case to enable additional debug on the AP's and isolate the root cause. 

1) Please open a new case either from WEB Portal.

https://support.ruckuswireless.com/cases/new

or 

2) Please reach out to below and a rep would help you in opening a ticket.

https://support.ruckuswireless.com/contact-us

Note : You can provide AP support log and Network topology (switch model and version) where AP's are connected to for initial investigation.

Best Regards

Vineet

26 Messages

 • 

430 Points

5 d ago

We had this issue soms time ago (with another version of the firmware). We were able to solve it by performing a factory reset on the affected access points.