irgendwas stimmt mit dem WLAN in einem L-321agn nicht mehr:
Was ist ein "[WLAN-1] WLAN error: interrupt stuck"?
Code: Alles auswählen
root@AP-EH-Anbau-156/158:/
> ls st/tcp/sys/last
Idx. Time Source Level Message
===========--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 2017-09-19 19:23:04 KERN Alarm last message repeated 3 times
2 2017-09-19 19:22:58 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
3 2017-09-19 19:22:58 AUTHPRIV Notice Login from 10.10.10.11 via SSH
4 2017-09-19 19:22:56 KERN Alarm last message repeated 1016 times
5 2017-09-19 18:49:04 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
6 2017-09-19 18:49:04 CRON Notice System time changed to 9/19/2017 16:49:04 (UTC), time difference is +0:00:01
7 2017-09-19 18:49:02 KERN Alarm last message repeated 17 times
8 2017-09-19 18:48:28 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
9 2017-09-19 18:48:28 CRON Notice System time changed to 9/19/2017 16:48:28 (UTC), time difference is +0:00:01
10 2017-09-19 18:48:26 KERN Alarm last message repeated 1171 times
11 2017-09-19 18:09:24 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
12 2017-09-19 18:09:23 CRON Notice System time changed to 9/19/2017 16:09:23 (UTC), time difference is +0:00:01
13 2017-09-19 18:09:22 KERN Alarm last message repeated 15 times
14 2017-09-19 18:08:52 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
15 2017-09-19 18:08:52 CRON Notice System time changed to 9/19/2017 16:08:52 (UTC), time difference is +0:00:01
16 2017-09-19 18:08:50 KERN Alarm last message repeated 700 times
17 2017-09-19 17:45:30 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
18 2017-09-19 17:45:30 AUTHPRIV Alarm Login from 192.168.102.217 via HTTPS failed
19 2017-09-19 17:45:28 KERN Alarm last message repeated 550 times
20 2017-09-19 17:27:08 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
21 2017-09-19 17:27:08 CRON Notice System time changed to 9/19/2017 15:27:08 (UTC), time difference is +0:00:01
22 2017-09-19 17:27:06 KERN Alarm last message repeated 1743 times
23 2017-09-19 16:29:00 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
24 2017-09-19 16:28:59 CRON Notice System time changed to 9/19/2017 14:28:59 (UTC), time difference is +0:00:01
25 2017-09-19 16:28:58 KERN Alarm last message repeated 14 times
26 2017-09-19 16:28:31 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
27 2017-09-19 16:28:30 CRON Notice System time changed to 9/19/2017 14:28:30 (UTC), time difference is +0:00:01
28 2017-09-19 16:28:28 KERN Alarm last message repeated 1244 times
29 2017-09-19 15:47:01 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
30 2017-09-19 15:47:00 CRON Notice System time changed to 9/19/2017 13:47:00 (UTC), time difference is +0:00:01
31 2017-09-19 15:46:58 KERN Alarm last message repeated 1733 times
32 2017-09-19 14:49:13 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
33 2017-09-19 14:49:12 CRON Notice System time changed to 9/19/2017 12:49:12 (UTC), time difference is +0:00:01
34 2017-09-19 14:49:10 KERN Alarm last message repeated 8 times
35 2017-09-19 14:48:55 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
36 2017-09-19 14:48:54 CRON Notice System time changed to 9/19/2017 12:48:54 (UTC), time difference is +0:00:01
37 2017-09-19 14:48:52 KERN Alarm last message repeated 3245 times
38 2017-09-19 13:00:43 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
39 2017-09-19 13:00:42 CRON Notice System time changed to 9/19/2017 11:00:42 (UTC), time difference is -0:00:03
40 2017-09-19 13:00:44 KERN Alarm last message repeated 6147 times
41 2017-09-19 09:35:51 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
42 2017-09-19 09:35:50 CRON Notice System time changed to 9/19/2017 7:35:50 (UTC), time difference is +0:00:01
43 2017-09-19 09:35:49 KERN Alarm last message repeated 1030 times
44 2017-09-19 09:01:29 KERN Alarm [WLAN-1] WLAN error: interrupt stuck
45 2017-09-19 09:01:29 CRON Notice System time changed to 9/19/2017 7:01:29 (UTC), time difference is +0:00:01
Jirka
P.S.: Hmm, nach einem Coldboot geht es erst mal wieder. Vorübergehend?
Weiß eigentlich ein WLC von diesen Problemen des APs? Wie kann ich solche Probleme in Zukunft besser von alleine erkennen? Was kann ich per SNMP abfragen, was im Fehlerfall dann einen Fehler(wert) ausgibt? (Hätte ich mal doch noch nicht so schnelle einen Coldboot machen sollen.) Oder geht es nur über Auswertung des Syslogs?