I'm wondering if anybody can give me some insight on what might be wrong with my network connections. I have a new SB6141 modem. Eversince I started using my modem my speeds have become very erratic and after long streaming sessions or during large downloads that take up a lot of bandwidth the modem will reboot itself. This seldomly happened with my old modem which is why I purchased this new one, because I thought the old one was dying. Now I'm wondering if it's just some coax cables that have gone bad. Here is my modem log notes:
Downstream Bonding Channel Value
Channel ID 3 4 5 6 8 9 10 12
Frequency 663000000 Hz 669000000 Hz 675000000 Hz 681000000 Hz 693000000 Hz 699000000 Hz 705000000 Hz 717000000 Hz
Signal to Noise Ratio 38 dB 38 dB 38 dB 38 dB 39 dB 38 dB 38 dB 38 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
4 dBmV 4 dBmV 5 dBmV 5 dBmV 5 dBmV 5 dBmV 4 dBmV 3 dBmV
Upstream Bonding Channel Value
Channel ID 11
Frequency 22600000 Hz
Ranging Service ID 9938
Symbol Rate 5.120 Msym/sec
Power Level 45 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 3 4 5 6 8 9 10 12
Total Unerrored Codewords 498681708 497909159 497918395 497926509 497903267 497904373 497904489 497902729
Total Correctable Codewords 116 104 184 114 149 200 135 164
Total Uncorrectable Codewords 1463 2347 1670 2255 1658 1487 2433 2354
Jun 16 2014 12:42:09 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:42:08 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:41:23 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:22:58 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:22:57 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:22:07 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:20:07 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:20:07 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:20:06 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:17:42 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 12:16:51 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 11:45:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jun 16 2014 11:41:45 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:21 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:01:5c:63:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=cc:65:ad:d3:46:3c;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
I'm noticing that I'm getting a lot of T3 and T4 timeouts. I have no splitters on my network. My modem connects to to the coax right out of the wall. I have a new coax arriving tomorrow that I will test with that one. Does anybody have any extra insight with this issue?
