B5 Log File - Help understanding Channel Change

Can anyone help me understand this log entry?

2017-01-14 19:10:45 (UTC +0000) root: MIMO_EVENT Channel Change p.ch:106(5530 MHz) s.ch:0(0 MHz) bw:140

What triggered the channel change?

Here’s what came before and after:

2017-01-08 15:52:15 (UTC +0000) syslog: MIMO_EVENT AutoEverything: NEW CHANNELS : ch1-> 5550 ch2-> 5550 bw-> 80 pw1-> 7 pw2-> 7 fdd-> 0 est_phyrat-> 584
2017-01-08 15:53:14 (UTC +0000) root: MIMO_EVENT CAC_END:Channel:110
2017-01-08 15:53:19 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-01-11 08:21:18 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-01-11 08:21:36 (UTC +0000) root: MIMO_EVENT Wireless associated
2017-01-14 19:10:45 (UTC +0000) root: MIMO_EVENT Channel Change p.ch:106(5530 MHz) s.ch:0(0 MHz) bw:140
2017-01-14 19:10:47 (UTC +0000) syslog: MIMO_EVENT AutoEverything: NEW CHANNELS : ch1-> 5530 ch2-> 5530 bw-> 40 pw1-> 7 pw2-> 7 fdd-> 0 est_phyrat-> 400
2017-01-14 21:07:16 (UTC +0000) root: MIMO_EVENT Wireless disassociated
2017-01-14 21:07:18 (UTC +0000) syslog: MIMO_EVENT AutoEverything: NEW CHANNELS : ch1-> 5560 ch2-> 5560 bw-> 80 pw1-> 7 pw2-> 7 fdd-> 0 est_phyrat-> 584
2017-01-14 21:08:16 (UTC +0000) root: MIMO_EVENT CAC_END:Channel:112
2017-01-14 21:08:24 (UTC +0000) root: MIMO_EVENT Wireless associated

Is there a document anywhere which would help me decode all the different log entries?

Thanks

Hi Chris,

Auto Everything made the channel change after association due to high PER. If Auto Everything chooses a channel in a DFS band, there is a mandatory waiting period before re-associating. That is what the CACs mean. DFS channels can be avoided if you prefer by creating exclusions.

More info about these topics can be found in these links:
http://backhaul.help.mimosa.co/backhaul-faq-auto-everything
http://backhaul.help.mimosa.co/backhaul-faq-supported-frequencies (DFS info here)
http://backhaul.help.mimosa.co/backhaul-ug-exclusions-restrictions

1 Like