I was enjoying no problems since changing 2.4ghz from auto to 11 and 5ghz from 48 to 44 for around 2 months until there was an internet outage and I ended up rebooting my CBR750 and the satellite. Now I'm back to the same stupid problem. Is there something I should look at in the logs or admin console when it occurs again?
Also, I'm trying to understand the messages in the event log but I can't seem to find a document explaining what they mean and whether I should be concerned.
Time
Priority
Description
Feb 12 2023 17:23:40
Critical (3)
No Ranging Response received - T3 time-out
Feb 12 2023 17:23:40
Critical (3)
No Ranging Response received - T3 time-out
Feb 12 2023 17:23:40
Critical (3)
No Ranging Response received - T3 time-out
Feb 12 2023 17:23:40
Critical (3)
No Ranging Response received - T3 time-out
Feb 12 2023 17:23:40
Critical (3)
No Ranging Response received - T3 time-out
Feb 12 2023 17:23:40
Critical (3)
No Ranging Response received - T3 time-out
Feb 13 2023 13:54:48
Notice (6)
CM-STATUS message sent. Event Type Code: 5
Feb 13 2023 17:09:00
Alert (2)
CM Certificate Error
Feb 14 2023 00:17:19
Critical (3)
No Ranging Response received - T3 time-out
Feb 14 2023 13:43:33
Notice (6)
DS profile config update. DS Chan ID: 193.
Feb 14 2023 15:36:50
Warning (5)
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 14 2023 15:36:50
Notice (6)
TLV-11 - unrecognized OID
Feb 14 2023 15:36:50
Critical (3)
Config File Rejected due to Invalid or Unexpected TLV 11
Feb 14 2023 15:37:01
Warning (5)
RCS Partial Service
Feb 14 2023 15:37:01
Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 14 2023 15:37:11
Alert (2)
CM Certificate Error
Feb 14 2023 15:37:29
Notice (6)
CM-STATUS message sent. Event Type Code: 4
Feb 14 2023 17:09:10
Alert (2)
CM Certificate Error
Feb 15 2023 01:20:31
Critical (3)
No Ranging Response received - T3 time-out
Feb 15 2023 17:08:47
Alert (2)
CM Certificate Error
Feb 15 2023 19:42:14
Critical (3)
No Ranging Response received - T3 time-out
Feb 16 2023 17:08:43
Alert (2)
CM Certificate Error
Feb 16 2023 18:32:31
Critical (3)
No Ranging Response received - T3 time-out
Feb 17 2023 06:07:56
Notice (6)
DS profile config update. DS Chan ID: 193.
Feb 17 2023 07:27:20
Warning (5)
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 17 2023 07:27:20
Notice (6)
TLV-11 - unrecognized OID
Feb 17 2023 07:27:20
Critical (3)
Config File Rejected due to Invalid or Unexpected TLV 11
Feb 17 2023 07:27:24
Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
Feb 17 2023 07:27:33
Alert (2)
CM Certificate Error
Feb 17 2023 11:18:26
Critical (3)
No Ranging Response received - T3 time-out
Feb 17 2023 17:08:30
Alert (2)
CM Certificate Error
Feb 17 2023 17:44:43
Critical (3)
No Ranging Response received - T3 time-out
Feb 18 2023 17:09:13
Alert (2)
CM Certificate Error
Feb 19 2023 02:21:38
Critical (3)
No Ranging Response received - T3 time-out
Feb 19 2023 17:09:06
Alert (2)
CM Certificate Error
Feb 19 2023 20:29:33
Critical (3)
No Ranging Response received - T3 time-out
Feb 19 2023 23:56:25
Notice (6)
DS profile config update. DS Chan ID: 193.
Feb 20 2023 15:27:45
Critical (3)
No Ranging Response received - T3 time-out
Feb 20 2023 17:09:09
Alert (2)
CM Certificate Error
Feb 20 2023 21:29:46
Critical (3)
No Ranging Response received - T3 time-out
Feb 21 2023 16:46:22
Warning (5)
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1
Feb 21 2023 16:46:22
Notice (6)
TLV-11 - unrecognized OID
Feb 21 2023 16:46:22
Critical (3)
Config File Rejected due to Invalid or Unexpected TLV 11
Feb 21 2023 16:46:26
Warning (5)
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
