sturrocks's profile

sturrocks

New Contributor

 • 

1 Message

Closed

Just moved into a new house with Cox 300mbps. Constant T3 T4 errors and modem resets

Hi,

So the modem upstream light begins blinking green and then the internet will temporarily shut down and then come back up. This happens 5-10 times a day especially while streaming video of any kind, and video will freeze/buffer and games will lagspike like crazy, etc. When looking at 192.168.100.1/ around the time that this happens I can see that the usual 4 upstream channels are not there and there will only be 1 or 2, and eventually all four will come back.

Main Errors in the log that appear with frequency:

  • Unicast ranging received abort response
  • Dynamic Range Window Violation
  • Started Unicast ranging Ranging- No response received T3 timeout
  • Received Response to Broadcast Maintenance Request but no unicast maintenance opportunities received T4 timeout

I have a new C7000v2 modem/router

2020-2-8, 00:49:56 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 00:50:01 Warning (5) Dynamic Range Window violation
2020-2-8, 00:50:29 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 00:52:19 Warning (5) Dynamic Range Window violation
2020-2-8, 00:54:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 00:54:22 Warning (5) Dynamic Range Window violation
2020-2-8, 00:54:37 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 00:54:40 Warning (5) Dynamic Range Window violation
2020-2-8, 00:55:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 00:55:39 Warning (5) Dynamic Range Window violation
2020-2-8, 04:23:32 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:23:32 Warning (5) Dynamic Range Window violation
2020-2-8, 04:23:34 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:23:34 Warning (5) Dynamic Range Window violation
2020-2-8, 04:23:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:23:37 Warning (5) Dynamic Range Window violation
2020-2-8, 04:23:39 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:23:40 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:24:12 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:24:43 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:24:51 Warning (5) Dynamic Range Window violation
2020-2-8, 04:25:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:01 Warning (5) Dynamic Range Window violation
2020-2-8, 04:25:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:04 Warning (5) Dynamic Range Window violation
2020-2-8, 04:25:06 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:06 Warning (5) Dynamic Range Window violation
2020-2-8, 04:25:15 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:20 Warning (5) Dynamic Range Window violation
2020-2-8, 04:25:35 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:39 Warning (5) Dynamic Range Window violation
2020-2-8, 04:25:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:25:59 Warning (5) Dynamic Range Window violation
2020-2-8, 04:26:08 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:26:09 Warning (5) Dynamic Range Window violation
2020-2-8, 04:26:15 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:26:19 Warning (5) Dynamic Range Window violation
2020-2-8, 04:26:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=00:27:90:0d:56:41;CM-QOS=1.1;CM-VER=3.0;
2020-2-8, 04:26:48 Warning (5)

Dynamic Range Window violation

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 1 783000000 Hz -4.4 dBmV 37.4 dB 140 355
2 Locked QAM256 33 405000000 Hz -2 dBmV 39.1 dB 559 548
3 Locked QAM256 2 789000000 Hz -4.6 dBmV 37.3 dB 135 253
4 Locked QAM256 3 795000000 Hz -5 dBmV 37.1 dB 126 407
5 Locked QAM256 4 801000000 Hz -4.9 dBmV 36.9 dB 121 371
6 Locked QAM256 5 807000000 Hz -4.6 dBmV 37.2 dB 129 346
7 Locked QAM256 6 813000000 Hz -4.6 dBmV 37.1 dB 92 238
8 Locked QAM256 7 819000000 Hz -4.8 dBmV 36.9 dB 94 168
9 Locked QAM256 8 825000000 Hz -5 dBmV 36.6 dB 114 279
10 Locked QAM256 17 879000000 Hz -3.5 dBmV 37.3 dB 82 257
11 Locked QAM256 18 885000000 Hz -3.2 dBmV 37.5 dB 82 234
12 Locked QAM256 19 891000000 Hz -3.3 dBmV 37.5 dB 108 349
13 Locked QAM256 20 897000000 Hz -3.2 dBmV 37.4 dB 95 222
14 Locked QAM256 21 903000000 Hz -3.4 dBmV 37.3 dB 71 292
15 Locked QAM256 22 909000000 Hz -3.2 dBmV 37.4 dB 88 325
16 Locked QAM256 23 915000000 Hz -3.4 dBmV 37.2 dB 120 252
17 Locked QAM256 24 921000000 Hz -4.3 dBmV 36.8 dB 0 0
18 Locked QAM256 34 411000000 Hz -2.8 dBmV 38.1 dB 0 0
19 Locked QAM256 35 417000000 Hz -2.6 dBmV 38 dB 0 0
20 Locked QAM256 36 423000000 Hz -3 dBmV 37.5 dB 0 0
21 Locked QAM256 37 429000000 Hz -2.5 dBmV 37.6 dB 0 0
22 Locked QAM256 38 435000000 Hz -2.5 dBmV 37.5 dB 0 0
23 Locked QAM256 39 441000000 Hz -2.1 dBmV 38.1 dB 0 0
24 Locked QAM256 40 447000000 Hz -1.8 dBmV 38.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 17600000 Hz 35.6 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 24000000 Hz 37.3 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30400000 Hz 38.4 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 36800000 Hz 38.6 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

From what I understand my SNR and power levels are ok, but not sure. When these problems happen there will only be 1 or 2 upstream channels and the power level will be 40+ though as opposed to the 4 shown here

Discussions

 • 

Updated 

595

1

0

0

B

BrianM

Moderator

 • 

886 Messages

Judging by the recent modem history we will likely need a technician out to the home. Short of that, make sure you have bypassed any possible splitters/checked connection for tightness etc.

Brian
Cox Support Forum Moderator

0

0