Xfinity plant
Xfinity globe
Community Forum

Internet Drops every day and modem resets

New Poster

Internet Drops every day and modem resets

 

Below is current status with internet up and at the bottom is the event log. Internet drops every day and most days many times. Usually the modem ends up resetting. Not sure what to do.
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 2 399000000 Hz 3.5 dBmV 41.0 dB 63 278
2 Locked QAM256 5 417000000 Hz 4.0 dBmV 41.4 dB 0 0
3 Locked QAM256 9 441000000 Hz 4.9 dBmV 42.4 dB 0 0
4 Locked QAM256 10 453000000 Hz 4.6 dBmV 42.3 dB 0 0
5 Locked QAM256 11 459000000 Hz 3.8 dBmV 41.8 dB 0 0
6 Locked QAM256 12 465000000 Hz 4.2 dBmV 42.2 dB 0 0
7 Locked QAM256 13 471000000 Hz 4.5 dBmV 42.4 dB 0 0
8 Locked QAM256 14 477000000 Hz 4.2 dBmV 42.3 dB 0 0
9 Locked QAM256 15 483000000 Hz 4.1 dBmV 42.1 dB 0 0
10 Locked QAM256 16 489000000 Hz 4.3 dBmV 42.3 dB 0 0
11 Locked QAM256 21 519000000 Hz 4.4 dBmV 42.7 dB 0 0
12 Locked QAM256 22 525000000 Hz 4.8 dBmV 43.0 dB 0 0
13 Locked QAM256 23 531000000 Hz 4.9 dBmV 42.9 dB 0 0
14 Locked QAM256 24 537000000 Hz 3.8 dBmV 42.2 dB 0 0
15 Locked QAM256 25 543000000 Hz 2.5 dBmV 41.3 dB 0 0
16 Locked QAM256 27 555000000 Hz 0.9 dBmV 40.2 dB 0 0

 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 49.3 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 49.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 49.0 dBmV


 

Current System Time: Wed Feb 28 09:25:44 2018


 ARRIS
 
SB6183
 
 
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.

 
Time Priority Description
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Feb 28 08:58:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 28 08:53:55 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 28 08:53:42 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 28 08:53:42 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 28 08:53:42 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Tue Feb 27 23:30:43 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 27 23:26:40 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 27 23:26:24 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 27 23:26:24 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 27 23:26:24 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Tue Feb 27 11:12:08 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 27 11:07:49 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 26 09:36:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 26 09:32:28 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 26 08:57:46 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Mon Feb 26 08:53:32 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Feb 25 09:03:17 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 25 08:58:57 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Feb 25 08:51:17 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 25 08:47:09 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 25 08:47:06 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 25 08:47:06 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 25 08:47:06 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Sun Feb 25 08:24:48 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sun Feb 25 08:20:31 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sat Feb 24 10:31:53 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 24 10:27:42 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 24 10:19:02 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 24 10:14:42 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 24 10:14:39 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 24 10:14:39 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 24 10:14:39 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Fri Feb 23 11:02:18 2018 Critical (3) Resetting the cable modem due to docsDevResetNow
Fri Feb 23 10:37:41 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 23 10:33:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Fri Feb 23 10:31:19 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 23 10:26:59 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 23 10:26:29 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 23 10:26:29 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 23 10:26:29 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:39:52 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:35:34 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:35:34 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:35:34 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:35:18 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:35:18 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:35:18 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;
Thu Feb 22 09:20:01 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:15:41 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:15:41 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:15:41 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:15:27 2018 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:15:27 2018 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 09:15:27 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 08:47:32 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 22 08:43:12 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;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=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.0;CM-VER=3.0;

 
 
 
Expert

Re: Internet Drops every day and modem resets

The upstream power is borderline / too high and may be intermittently fluctuating even higher out of spec. That can cause random disconnects, spontaneous re-booting of the modem, and speed and latency problems.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.


New Poster

Re: Internet Drops every day and modem resets

I eliminated a splitter yesterday and thought things were better, but I now have issues again today. it seems to happen between about 930 and 11 am daily.  See below.

 

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 9 441000000 Hz 11.2 dBmV 42.3 dB 71 178
2 Locked QAM256 1 393000000 Hz 10.4 dBmV 41.6 dB 116 32
3 Locked QAM256 2 399000000 Hz 10.5 dBmV 41.6 dB 131 34
4 Locked QAM256 3 405000000 Hz 9.8 dBmV 41.2 dB 103 29
5 Locked QAM256 4 411000000 Hz 9.6 dBmV 41.2 dB 79 33
6 Locked QAM256 5 417000000 Hz 10.9 dBmV 42.0 dB 56 32
7 Locked QAM256 6 423000000 Hz 11.1 dBmV 42.1 dB 68 38
8 Locked QAM256 7 429000000 Hz 10.4 dBmV 41.7 dB 28 40
9 Locked QAM256 8 435000000 Hz 10.0 dBmV 41.6 dB 60 93
10 Locked QAM256 10 453000000 Hz 10.9 dBmV 42.3 dB 33 52
11 Locked QAM256 11 459000000 Hz 10.2 dBmV 42.0 dB 60 84
12 Locked QAM256 12 465000000 Hz 10.8 dBmV 42.5 dB 33 54
13 Locked QAM256 13 471000000 Hz 11.2 dBmV 42.8 dB 38 25
14 Locked QAM256 14 477000000 Hz 11.0 dBmV 42.7 dB 32 27
15 Locked QAM256 18 501000000 Hz 10.8 dBmV 42.8 dB 43 25
16 Locked QAM256 25 543000000 Hz 7.8 dBmV 40.8 dB 5 28

 
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.0 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 44.0 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 43.8 dBmV


 

Current System Time: Thu Mar 01 09:56:40 2018

 

 

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.

 
Time Priority Description
Thu Mar 01 09:57:59 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Feb 28 10:09:29 2018 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 28 10:08:27 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-QOS=1.1;CM-VER=3.0;
Wed Feb 28 10:08:23 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=74:ea:e8:f0:ff:61;CMTS-MAC=00:01:5c:68:24:70;CM-
Expert

Re: Internet Drops every day and modem resets

The upstream power is much better but now the downstream power is high. The up and down power levels work equally and oppositely of each other when introducing or eliminating line attenuation. It is a fine balancing act. Perhaps it would be best to get a tech out to properly balance your line.

New Poster

Re: Internet Drops every day and modem resets

What range should the downstream and upstream power be at? I totally removed the splitter yesterday. I can get a new oneand replace.


@EG wrote:

The upstream power is much better but now the downstream power is high. The up and down power levels work equally and oppositely of each other when introducing or eliminating line attenuation. It is a fine balancing act. Perhaps it would be best to get a tech out to properly balance your line.


 

Expert

Re: Internet Drops every day and modem resets

As I stated it is a balancing act. A "new splitter" is not necessarily the answer;

 

https://www.dslreports.com/faq/16085

Expert

Re: Internet Drops every day and modem resets


@mskj7 wrote:

What range should the downstream and upstream power be at? I totally removed the splitter yesterday. I can get a new oneand replace.

Hi @mskj7,

You can find a troubleshooting guide right here on the forums which will give you some guidance on signal levels and splitters. I've asked an employee to look at your account on the backend, they may be able to see issues that we can't. They can also set you up with a service call if needed. 

 

Tip: If you need service, sign up for the Service Protection Plan (SPP). It's around $6 a month and you must keep it for at least 60 days after your service call. If you have SPP, you won't incur a service charge. You can sign up when you schedule an appointment.

Official Employee

Re: Internet Drops every day and modem resets

 

Hello mskj7, it sounds like you may need a technician out to look into your service issues on site. I can assist you with getting a tech scheduled, can you please send me a private message with your full name, street address, and account number by clicking on my name (ComcastAmir) and then "private message me"?