Modem is self-owned, SB6141. It keeps rebooting with T3 and T4 errors. I'm in the Columbus, OH area. This is the log and signal information from directly after the last reboot. I've checked the line inside, all connections are tight, no splitter, but there is an inline coupling. It seems tight and shows no wear? Really not sure what is going on...
Sep 10 2019 19:01:22 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 19:01:22 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:24 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot due to T4 timeout ;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 19:00:22 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 18:59:47 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 13:29:25 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 13:29:25 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:23 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot due to T4 timeout ;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 13:28:28 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:19:31 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:19:31 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:19:18 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:18:56 | 5-Warning | U102.0 | TCS Partial Service;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:18:54 | 6-Notice | I401.0 | TLV-11 - unrecognized OID;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:18:54 | 5-Warning | Z00.0 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:33 | 3-Critical | R02.0 | No Ranging Response received - T3 time-out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Jan 01 1970 00:00:17 | 6-Notice | N/A | Cable Modem Reboot from GUI/Configuration page ;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; |
Sep 10 2019 12:17:36 | 3-Critical | R04.0 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:05:b1:92:92:aa;CMTS-MAC=00:01:5c:7c:ec:4c;CM-QOS=1.1;CM-VER=3.0; |
Channel ID | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 18 | |
Frequency | 675000000 Hz | 681000000 Hz | 687000000 Hz | 693000000 Hz | 699000000 Hz | 705000000 Hz | 711000000 Hz | 729000000 Hz | |
Signal to Noise Ratio | 38 dB | 38 dB | 38 dB | 39 dB | 39 dB | 39 dB | 39 dB | 37 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| 4 dBmV | 5 dBmV | 5 dBmV | 5 dBmV | 5 dBmV | 4 dBmV | 4 dBmV | 1 dBmV |
Channel ID | 50 | 52 | 51 | 49 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 13394 | 13394 | 13394 | 13394 |
Symbol Rate | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 40 dBmV | 43 dBmV | 42 dBmV | 40 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 18 |
Total Unerrored Codewords | 2158714 | 936978 | 954145 | 962330 | 930295 | 931804 | 930063 | 927720 |
Total Correctable Codewords | 216 | 5 | 0 | 0 | 19 | 24 | 27 | 11 |
Total Uncorrectable Codewords | 2315 | 1304 | 1428 | 1426 | 1562 | 1518 | 1531 | 1514 |
Solved! Go to Solution.
Are you in a house or apartment? Have you checked the line outside as much as you have access to? If everything inside is nice and tight then it could be a loose connection or a squirrel chewed coax from your drop line, water in the pedestal, or even a noisy neighbor.
Okay a tech will be coming out, however they are saying that the problem is only the modem. This is my most recent signal information, it is still timing out - just so i know what to expect on Friday, does this look like a modem issue is likely the cause? At no point in any of the timeouts has the power light gone out. Thank you again for your help!
Channel ID | 22 | 16 | 17 | 18 | 19 | 20 | 21 | 23 | |
Frequency | 753000000 Hz | 717000000 Hz | 723000000 Hz | 729000000 Hz | 735000000 Hz | 741000000 Hz | 747000000 Hz | 759000000 Hz | |
Signal to Noise Ratio | 38 dB | 38 dB | 38 dB | 38 dB | 37 dB | 37 dB | 38 dB | 38 dB | |
Downstream Modulation | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | QAM256 | |
Power Level
| 1 dBmV | 3 dBmV | 3 dBmV | 2 dBmV | 2 dBmV | 1 dBmV | 1 dBmV | 0 dBmV |
Channel ID | 50 | 52 | 51 | 49 |
Frequency | 24200000 Hz | 37000000 Hz | 30600000 Hz | 19400000 Hz |
Ranging Service ID | 11805 | 11805 | 11805 | 11805 |
Symbol Rate | 5.120 Msym/sec | 5.120 Msym/sec | 5.120 Msym/sec | 2.560 Msym/sec |
Power Level | 40 dBmV | 43 dBmV | 43 dBmV | 40 dBmV |
Upstream Modulation | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [1] 16QAM [2] 64QAM | [3] QPSK [2] 16QAM |
Ranging Status | Success | Success | Success | Success |
Channel ID | 22 | 16 | 17 | 18 | 19 | 20 | 21 | 23 |
Total Unerrored Codewords | 66497361 | 66513970 | 66522508 | 66505877 | 66486760 | 66488533 | 66488116 | 66492786 |
Total Correctable Codewords | 11 | 2 | 0 | 2 | 16 | 13 | 49 | 48 |
Total Uncorrectable Codewords | 1702 | 1383 | 1488 | 1297 | 1509 | 1531 | 1484 | 1464 |
I'm not saying they're wrong about it being a bad modem, but modems rarely, if ever, go bad. If the phone rep told you it was a bad modem then take that with a grain of salt knowing that they are usually not trained techs.
@RAIST5150 may not want to say it yet, but I will: The repeated dropouts prrobably have nothing to do with your modem. Your upstream signal level looks about right compared with the downstream. Incoming levels and packet error rates tell me that when you do have signal your cableTV programming and internet are both running OK. I'll bet dollars to donuts the problem is outside your home, somewhere out on Spectrum's network.
You said you had a storm-related outage in the last two weeks. They should look for another loose connector or a cable pullout along the overhead feeder trunk that they haven't found and repaired, OR the safety ground wire on your cable ground block is loose, corroded, or missing.