Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem

network-admin — Wed, 16 May 2018 22:52:18 GMT

Hi,

We are trying to solve some client performance/disconnection issues on AP370s,

One thing I noticed it that one of the problem APs had >2400 interrupts per second when looking at 'show cpu detail'.

The APs log also has a lot of the messages below. Can anyone tell me if either of these things gives a clue to the problems we are having?

This AP is currently running HiveOS 6.5r7, but it has had 6.5r8b and 6.5r9 , it was downgrade because I hoped it my resolve the problems.

2018-05-16 15:27:40 debug kernel: FWLOG: [42178378] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:39 debug kernel: FWLOG: [42178064] WAL_DBGID_DEV_TX_TIMEOUT ( 0x5 )

2018-05-16 15:27:39 debug kernel: FWLOG: [42177749] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:39 debug kernel: FWLOG: [42177319] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:38 debug kernel: FWLOG: [42177004] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:38 debug kernel: FWLOG: [42176689] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:38 debug kernel: FWLOG: [42176187] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:37 debug kernel: FWLOG: [42175872] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:37 debug kernel: FWLOG: [42175558] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:37 debug kernel: FWLOG: [42175127] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:36 debug kernel: FWLOG: [42174813] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:36 debug kernel: FWLOG: [42174498] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:36 debug kernel: FWLOG: [42174068] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:35 debug kernel: FWLOG: [42173753] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:35 debug kernel: FWLOG: [42173438] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:34 debug kernel: FWLOG: [42172936] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:34 debug kernel: FWLOG: [42172621] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:34 debug kernel: FWLOG: [42172307] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:33 debug kernel: FWLOG: [42171877] WAL_DBGID_DEV_TX_TIMEOUT ( 0x5 )

2018-05-16 15:27:33 debug kernel: FWLOG: [42171562] WAL_DBGID_DEV_TX_TIMEOUT ( 0x5 )

2018-05-16 15:27:33 debug kernel: FWLOG: [42171247] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:32 debug kernel: FWLOG: [42170817] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:32 debug kernel: FWLOG: [42170502] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:32 debug kernel: FWLOG: [42170187] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:31 debug kernel: FWLOG: [42169685] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:31 debug kernel: FWLOG: [42169370] WAL_DBGID_DEV_TX_TIMEOUT ( 0x5 )

2018-05-16 15:27:31 debug kernel: FWLOG: [42169056] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:30 debug kernel: FWLOG: [42168626] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

2018-05-16 15:27:30 debug kernel: FWLOG: [42168311] WAL_DBGID_DEV_TX_TIMEOUT ( 0x1 )

Re: Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem

GeorgiaMason — Thu, 17 May 2018 20:21:17 GMT

Not sure what most of that means, but based on the "TX timeout" part and some quick googling, I think that's going to be interference related. Interference is signal damage, which slows your wifi down.

They have some guides for how to start cleaning up interference. Depending on what manager you're using:

NG- https://thehivecommunity.aerohive.com/s/article/Radio-Frequency-Interference-NG

Classic- https://thehivecommunity.aerohive.com/s/article/Radio-Frequency-Interference-Troubleshooting

Re: Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem

network-admin — Wed, 23 May 2018 20:17:10 GMT

Thanks for the response Georgia.

topic Re: Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem in Aerohive Migrated Content

Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem

Re: Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem

Re: Are HIgh interrupts or WAL_DBGID_DEV_TX_TIMEOUT messages a problem