cancel
Showing results for 
Search instead for 
Did you mean: 

R500 short-term disconnection from the network

Andriy
New Contributor III

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.

1 ACCEPTED SOLUTION

Andriy
New Contributor III

The problem was found.
One of the connected clients (device) had a problem. Just turned it off and the problem went away.

View solution in original post

13 REPLIES 13

Andriy
New Contributor III

2.4 and 5

Andriy
New Contributor III

--- 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

Andriy
New Contributor III

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 )

Andriy
New Contributor III

Two, one for 2.4 and the other for 5. If you deplete them, the problem does NOT go away.

Andriy
New Contributor III

The problem was found.
One of the connected clients (device) had a problem. Just turned it off and the problem went away.