Frequent outages

[yooooo83]

Hello,

I am experiencing semi-frequent outages. I have just started service with Xfinity (10/20) and have been having issues since.

I have the Motorola MB8600 Modem which is Xfinity approved for gigabit service. I have been poking around reddit and these forums and believe I have the same issue as several other people. For completeness, here are the downstream/upstream and event logs from my modem.

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected    1 Locked QAM256 5 507.0 9.3 41.8 122 0    2 Locked QAM256 1 483.0 9.6 42.0 108 0    3 Locked QAM256 2 489.0 9.5 42.0 145 0    4 Locked QAM256 3 495.0 9.4 42.0 92 0    5 Locked QAM256 4 501.0 9.3 41.9 131 0    6 Locked QAM256 6 513.0 9.4 41.7 164 0    7 Locked QAM256 7 519.0 9.4 41.5 123 0    8 Locked QAM256 8 525.0 9.3 41.7 85 0    9 Locked QAM256 9 531.0 9.0 41.6 83 0    10 Locked QAM256 10 537.0 9.3 41.8 75 0    11 Locked QAM256 11 543.0 9.3 41.7 94 0    12 Locked QAM256 12 549.0 9.3 41.8 60 0    13 Locked QAM256 13 555.0 9.3 41.5 58 0    14 Locked QAM256 14 561.0 9.6 41.8 82 0    15 Locked QAM256 15 567.0 9.9 41.9 84 0    16 Locked QAM256 16 573.0 10.0 41.7 56 0    17 Locked QAM256 17 579.0 9.8 41.3 70 0    18 Locked QAM256 18 585.0 9.5 40.2 58 0    19 Locked QAM256 19 591.0 10.0 41.7 58 0    20 Locked QAM256 33 459.0 9.4 41.8 189 0    21 Locked QAM256 34 465.0 9.6 42.0 188 0    22 Locked QAM256 35 471.0 9.5 41.3 198 0    23 Locked QAM256 36 477.0 9.5 41.8 163 0    24 Locked OFDM PLC 37 690.0 12.0 39.8 403504369 0    25 Locked QAM256 38 429.0 9.5 42.2 329 1    26 Locked QAM256 39 435.0 9.4 42.0 277 0    27 Locked QAM256 40 441.0 9.3 42.1 227 0    28 Locked QAM256 41 453.0 9.3 41.8 216 0    29 Locked QAM256 42 405.0 9.4 42.2 414 0    30 Locked QAM256 43 411.0 9.4 42.2 415 1    31 Locked QAM256 44 417.0 9.5 42.3 347 0    32 Locked QAM256 45 423.0 9.4 42.1 309 0

Upstream Bonded Channels

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)    1 Locked SC-QAM 1 5120 35.6 41.3    2 Locked SC-QAM 2 5120 29.2 41.3    3 Locked SC-QAM 3 5120 22.8 40.8    4 Locked SC-QAM 4 5120 16.4 40.5    5 Locked SC-QAM 5 1280 39.6 43.0

Log

Time    Priority    Description      11:33:28 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:34:23 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:34:44 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:36:36 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:37:01 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:38:40 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:38:54 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:39:25 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:42:03 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:42:45 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     11:59:55 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:01:39 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:02:02 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:03:16 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:04:21 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:04:48 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:05:29 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:07:09 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:08:18 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:08:51 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:33:03 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     12:33:40 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:00:12 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:01:57 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:02:25 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:04:30 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:09:12 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:09:56 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:14:22 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:15:50 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:17:51 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     13:17:52 Sat Oct 24 2020   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 37; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;

I have also had T3 Timeout errors, but I have since restarted the modem which cleared the logs. Please advise on what to do. I was with AT&T on 50 mbps down for over 3 years and never had a single issue. Only reason I switched was for gigabit, but it's not worth the instability and if this isn't resolved I will have to go back.

Here are a couple of threads that seem similar:

https://forums.xfinity.com/t5/Your-Home-Network/Major-Internet-Issues-Any-Ideas-RESOLVED/td-p/337543...

https://forums.xfinity.com/t5/Your-Home-Network/CM-Status-issues-and-spotty-connectivity/m-p/3376320

Thanks for your time.

[yooooo83]

Following up on this because I have not received any responses. I had an outage last night. Here is the event log from modem:

Event Log

Time    Priority    Description      16:32:18 Thu Oct 22 2020   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     17:02:19 Thu Oct 22 2020   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     17:17:59 Thu Oct 22 2020   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     17:20:27 Thu Oct 22 2020   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     18:01:17 Thu Oct 22 2020   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     18:12:33 Thu Oct 22 2020   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     01:20:04 Tue Oct 27 2020   Critical (3)   Resetting the cable modem due to docsDevResetNow     Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6     07:08:33 Tue Oct 27 2020   Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=00:40:36:6b:ee:d8;CMTS-MAC=00:01:5c:9f:32:55;CM-QOS=1.1;CM-VER=3.1;

Can someone please take a look and offer guidance?

[AnotherMe2]

I had the same story past night 10/27/2020

2020-10-27, 08:03:37 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 08:03:37 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 08:03:37 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 08:01:35 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 08:01:33 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 08:01:33 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:57:23 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:57:22 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:57:22 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:55:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:55:41 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:55:41 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:53:14 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:53:12 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:53:12 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:49:50 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:49:49 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:49:49 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:47:23 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:47:21 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:47:21 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:42:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:42:45 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:42:45 Critical (3) Ranging Request Retries exhausted;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;
2020-10-27, 07:40:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:72:98;CMTS-MAC=00:01:5c:6f:22:51;CM-QOS=1.1;CM-VER=3.1;