Community Forum

Internet disconnects intermittently.

Regular Visitor

Internet disconnects intermittently.

A few months ago, I changed from the Triple Play to Internet only service.  I also went from 105 speed to 250.  Ever since then, I've been having disconnect problems.  This has happened with multiple modems and routers.  Current Setup is Arris SB6183 and Netgear AC1750 R6400

2 Techs have been to the house so far.  Any guidance on how to find the issue?

 

Status

The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem.

 
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel   Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK  
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed  

 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 4 495000000 Hz 6.8 dBmV 39.7 dB 44 135
2 Locked QAM256 5 507000000 Hz 7.0 dBmV 39.0 dB 49 72
3 Locked QAM256 7 519000000 Hz 7.1 dBmV 40.0 dB 45 151
4 Locked QAM256 8 525000000 Hz 6.9 dBmV 39.9 dB 48 54
5 Locked QAM256 9 531000000 Hz 6.7 dBmV 39.9 dB 24 60
6 Locked QAM256 12 549000000 Hz 6.5 dBmV 39.9 dB 19 114
7 Locked QAM256 14 561000000 Hz 6.3 dBmV 39.8 dB 20 102
8 Locked QAM256 15 567000000 Hz 6.2 dBmV 39.7 dB 28 113
9 Locked QAM256 16 573000000 Hz 6.2 dBmV 39.7 dB 18 87
10 Locked QAM256 17 579000000 Hz 6.2 dBmV 39.7 dB 33 121
11 Locked QAM256 18 585000000 Hz 6.2 dBmV 39.7 dB 18 65
12 Locked QAM256 20 597000000 Hz 6.3 dBmV 39.7 dB 23 97
13 Locked QAM256 21 603000000 Hz 6.3 dBmV 39.7 dB 26 84
14 Locked QAM256 28 645000000 Hz 6.5 dBmV 39.5 dB 17 58
15 Locked QAM256 31 663000000 Hz 6.5 dBmV 39.5 dB 20 73
16 Locked QAM256 32 669000000 Hz 6.7 dBmV 39.5 dB 20 69

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 43.3 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 44.0 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 43.0 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 42.5 dBmV

 

Event Log

The table below contains the log of events that the SB6183 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.

 
Tue Jun 18 18:23:22 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 19 18:05:52 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 19 18:10:12 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Sat Jun 22 14:12:28 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:23:52 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Jun 22 14:45:43 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:45:43 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:45:43 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:46:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:46:19 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:46:19 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:46:26 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 14:50:46 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Sat Jun 22 15:22:13 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Jun 23 22:47:36 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 09:33:43 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 09:33:43 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 09:33:43 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 09:34:06 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 09:34:06 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 09:34:06 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 09:38:13 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Mon Jun 24 10:03:55 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 10:03:55 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 10:03:55 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 10:04:30 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 10:04:30 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 10:04:30 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 10:08:29 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 12:52:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 12:52:56 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 12:52:56 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 12:53:16 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 12:57:36 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 13:34:40 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:34:40 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:34:40 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:35:17 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:35:17 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:35:17 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:35:28 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 13:39:37 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 14:19:48 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 14:24:09 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 14:37:37 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 14:41:57 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 15:16:37 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 15:20:57 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 16:14:22 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 16:18:42 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 16:20:18 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 16:20:50 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 17:24:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 17:24:19 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 17:24:19 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 17:24:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 17:29:07 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 20:18:20 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 20:18:20 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 20:18:20 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 20:18:56 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 24 20:23:16 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 22:01:12 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 22:02:54 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Jun 24 22:06:42 2019 Critical (3) Resetting the cable modem due to docsDevResetNow
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Tue Jun 25 07:26:26 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 25 07:26:26 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 25 07:26:26 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 25 07:26:52 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 25 07:31:12 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Tue Jun 25 07:38:09 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=d4:04:cd:97:c7:33;CMTS-MAC=00:01:5c:b1:bc:51;CM-QOS=1.1;CM-VER=3.0;
 
Expert

Re: Internet disconnects intermittently.

Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.


There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Highlighted
Official Employee

Re: Internet disconnects intermittently.

I couldn't agree with you more, EG! Thanks for letting us know about this! 

 

cdziedzic, appreciate you taking the time to post your logs and let us know about your service issues on the forums. Thanks for allowing us an opportunity to resolve! Let's check your historical plots as well as your signal levels at and outside the premise to get an idea of what might be going on in your area. Please send me a private message with your full name for help! 

 

Ken


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!