11-16-2023 11:31 PM
Hello.
There are three R500 points in the network. Connected to Mikrotik POE. There is a short-term dump of one of the points (2-4 packages). If you turn it off, this problem appears on the second point. If you disable the second point, the problem appears on the third point.
Solved! Go to Solution.
11-19-2023 03:17 PM - edited 11-20-2023 09:08 AM
The problem was found.
One of the connected clients (device) had a problem. Just turned it off and the problem went away.
11-20-2023 04:01 AM
2.4 and 5
11-18-2023 12:11 AM - edited 11-20-2023 09:06 AM
--- System Log ----
Nov 17 05:24:20 Dasha 22 user.warn kernel: Keyix=0 Keylen=16 Keyflags=0 Cipher=0
Nov 17 05:24:20 Dasha 22 user.warn kernel: Keydata=0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
Nov 17 05:24:20 Dasha 22 user.warn kernel: FWLOG: [56338499] WAL_DBGID_TX_SCH_REGISTER_TIDQ ( 0xff, 0x1 )
Nov 17 05:24:51 Dasha 22 daemon.notice meshd[358]: Scan returned 0 entries.
Nov 17 05:25:13 Dasha 22 user.warn kernel: !!!!BAW screewed baw_used:1 baw_size:0 nretry:1 baw_start:236 baw_end:236 seq_st:0 tidno:0
Nov 17 05:25:13 Dasha 22 user.warn kernel: !!!!BAW screewed baw_used:1 baw_size:0 nretry:1 baw_start:236 baw_end:236 seq_st:0 tidno:0 new_agg_limit:1 nretry_drops:0
11-18-2023 12:12 AM - edited 11-21-2023 07:11 AM
Nov 17 07:58:03 Gost 21 user.warn kernel: FWLOG: [1469165] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x166aed, 0x4000d89, 0x10, 0x9a )
Nov 17 07:58:03 Gost 21 user.warn kernel: FWLOG: [1469165] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x3f0037, 0x20003, 0x1d801d2 )
Nov 17 07:58:03 Gost 21 user.warn kernel: FWLOG: [1469176] WAL_DBGID_BB_WDOG_TRIGGERED ( 0x166af8, 0x4000d89, 0x10, 0x9b )
Nov 17 07:58:03 Gost 21 user.warn kernel: FWLOG: [1469176] WAL_DBGID_STA_VDEV_XRETRY ( 0x202e0, 0x3f0037, 0x20003, 0x1d801d2 )
Nov 17 07:58:03 Gost 21 user.warn kernel: FWLOG: [1469176] WAL_DBGID_STA_VDEV_XRETRY ( 0xab1, 0x9b )
11-18-2023 12:31 AM
Two, one for 2.4 and the other for 5. If you deplete them, the problem does NOT go away.
11-19-2023 03:17 PM - edited 11-20-2023 09:08 AM
The problem was found.
One of the connected clients (device) had a problem. Just turned it off and the problem went away.