I've been having issues for about a month now. My internet goes in and out. It looks as if my modem just keeps cycling. Sometimes I'll go all day and be fine, other times I'm barely up at all. It's a sb6141. When I call tech support they tell me something looks wrong with my lines/signal and they send out a tech. Third tech left tonight and I still don't have consistant internet. Little over two weeks ago the first one showed up when it was working so that trip was pointless. The second tech a day later seemed to fix it for a bit, he did something outside at my box, adjusted a splitter and moved an amp. It's been fine about two weeks, but now it's doing it again. This third tech tonight, without going outside to check anything just told me my modem was bad. I explained to him, and showed him, the brand new modem I bought just to make sure it wasn't the modem. That new modem did the exact same thing. I even disconnected my tv by removing the splitter and just hooked up my modem. I bypassed my router and ran ethernet cable. He said it's just a crap modem model and I need another one. I told him it's on the website as Cox approved, he then offered to rent me one with panoramic wifi. When I didn't want that he said that then there was nothing he could do and left. I find it hard to believe my 1.5 year old modem and a brand new one are both bad.
I have an appointment with a 4th tech for Monday, my next day off work or else it would be sooner. Below are my signals and my logs, when I tried a brand new modem I got the exact same signal levels and error logs. All the cables insider are new as well. Anyone have any suggestions?
This is my signal page:
Downstream Bonding Channel Value
Channel ID 33 34 35 36 37 38 39 40
Frequency 345000000 Hz 351000000 Hz 357000000 Hz 363000000 Hz 369000000 Hz 375000000 Hz 381000000 Hz 387000000 Hz
Signal to Noise Ratio 39 dB 39 dB 39 dB 39 dB 40 dB 39 dB 40 dB 39 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
9 dBmV 9 dBmV 9 dBmV 9 dBmV 9 dBmV 8 dBmV 8 dBmV 9 dBmV
Upstream Bonding Channel Value
Channel ID 2
Frequency 23792000 Hz
Ranging Service ID 1199
Symbol Rate 5.120 Msym/sec
Power Level 57 dBmV
Upstream Modulation [3] 16QAM
[3] 64QAM
Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 33 34 35 36 37 38 39 40
Total Unerrored Codewords 24382798 23518303 23527456 23535482 23511464 23512409 23516606 23545416
Total Correctable Codewords 1021 1468 1172 1266 922 1000 1849 1209
Total Uncorrectable Codewords 6525 6372 5701 5759 6869 7343 7472 6605
My logs constantly look like this:
Time Priority Code Message
Nov 18 2017 21:37:20 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:37:20 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;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=xxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:36:29 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:35:59 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:14:56 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:14:56 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:14:50 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:14:30 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:14:25 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:14:04 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:13:34 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:13:05 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:12:57 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:12:45 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:12:15 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:11:43 4-Error U101.0 TCS Fail on all Upstream Channels;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:11:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:11:25 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
Nov 18 2017 21:11:25 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxx;CMTS-MAC=00:38:df:9a:89:5c;CM-QOS=1.1;CM-VER=3.0;
↧