Daily Motorola modem reboots, T3 timeouts, upstream power level issue?
I've been looking through posts on this forum and elsewhere over the last couple weeks and it appears I may have a similar issue as many others where my Motorola SB6141 modem reboots itself due to T3 Timeout errors. I attempted to contact Cox through email and got the usual canned response about rebooting, clearing cookies, etc. I don't think the responder even read my email. I'm posting here now since it appears there are better responses to problems like this, at least from @TiffanyR and @DerrickW. Based on my observation, my upstream power levels increase to 52 - 54 dBvM around the time of these errors, and then drop down to 48-50 dBvM through the rest of the day. I have no splitters in line. The cable is new and well-connected. Below are relevant logs from the last two days, and a current snapshot of my signal page (while the modem is running). Please let me know what I can do to alleviate this issue. Time Priority Code Message 6/20/2015 10:48:28 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:48:28 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:46:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:46:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:28:01 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:27:32 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:27:32 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:27:31 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:27:17 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:27:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:27:02 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:18:46 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:18:46 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 1/1/1970 0:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 1/1/1970 0:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:18:00 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:18:00 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:17:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:17:45 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/20/2015 10:17:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:57:14 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:57:14 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 1/1/1970 0:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=[omitted];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:28 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:28 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:16 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:07 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:07 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:56:06 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:45:14 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:45:14 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 1/1/1970 0:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:44:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:44:30 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:44:15 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:44:15 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:44:00 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:44:00 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; 6/19/2015 10:43:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=[omitted];CMTS-MAC=[omitted];CM-QOS=1.1;CM-VER=3.0; SIGNAL INFO Downstream Bonding Channel Value Channel ID 121 122 123 124 129 130 131 132 Frequency 813000000 Hz 819000000 Hz 825000000 Hz 831000000 Hz 861000000 Hz 867000000 Hz 873000000 Hz 879000000 Hz Signal to Noise Ratio 37 dB 37 dB 37 dB 37 dB 37 dB 38 dB 36 dB 36 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 -4 dBmV -5 dBmV -6 dBmV -6 dBmV -7 dBmV -7 dBmV Upstream Bonding Channel Value Channel ID 3 1 2 4 Frequency 23300000 Hz 36300000 Hz 29800000 Hz 18400000 Hz Ranging Service ID 49 49 49 49 Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level 48 dBmV 50 dBmV 49 dBmV 48 dBmV Upstream Modulation [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM [3] 16QAM [3] 64QAM Ranging Status Success Success Success Success Signal Stats (Codewords) Bonding Channel Value Channel ID 121 122 123 124 129 130 131 132 Total Unerrored Codewords 130449138 129742962 129751152 129758812 129732938 129732353 129734139 129736247 Total Correctable Codewords 17 12 8 5 18 20 194 77 Total Uncorrectable Codewords 602 542 541 1449 1508 1600 1506 5834.6KViews0likes7Comments
Lost MDD timeout / T3 Timeout
here are 2 pictures of my event logs a few hours apart. I get a few different timeouts and im unsure what they mean or indicate. My biggest issue lately has been very weak upload speeds, and packet loss.. To save a bit of trouble informatively: Speed plan- 940mbps/35mbps Modem- Arris SB8200 Docsis 3.1 / 3.0 Router- Netgear Nighthawk R9000 All new coax wiring in home. Coax running into home is only split 1 time. -3.5db to my tv -3.5db to my cable modem All ethernet cables are Cat8 All wires and connections are properly connected and not loose699Views0likes0CommentsIncreasing frequency of internet outages (T3 timeouts)
I'm having ever more frequent internet drops over the last several weeks. It typically drops for only 1 to 10 minutes at a time. But happening more frequently of late. Sometimes it recovers on its own. Sometimes I need to reset the modem (Netgear CM1000v2). When I check the logs in my modem, the outages always seem to align with "T3 time-outs". My understanding is that this is indicative of some upstream interference, outside of my house. Perhaps stemming from an issue elsewhere in the neighborhood. I have read lots and lots of other accounts of people that experience this, and what seems like a very difficult issue to resolve. Pinpointing where in the system the issue is, source of noise/interference, etc. requiring more sr tech's to figure it out. I just spent the last 3 hours with a Cox live chat agent trying to express the issue. But only met with responses like "Thank you for staying connected". Or "I completely understand your concern. Thank you for reaching and letting us know about...". Clearly copy/paste responses the call center uses. Then asking me about other devices in my house, etc. I get it that Level 1 support is what it is. But when 20-30 minutes go by between each response, this is an unworkable path towards resolution. I've heard an informal FCC complaint is the only way to get any action. Is that really how the process works? I'm asking the community for a practical way to get support. The end of the last chat with the live agent ended with a presumptive "Just to recap, you messaged us today about your internet . I helped you with the internet . Your satisfaction means everything to us . Have we covered everything you wanted to discuss today?" Um...no.72Views0likes1Comment
Lost MDD timeout / T3 Timeout
here are 2 pictures of my event logs a few hours apart. I get a few different timeouts and im unsure what they mean or indicate. My biggest issue lately has been very weak upload speeds, and packet loss.. To save a bit of trouble informatively: Speed plan- 940mbps/35mbps Modem- Arris SB8200 Docsis 3.1 / 3.0 Router- Netgear Nighthawk R9000 All new coax wiring in home. Coax running into home is only split 1 time. -3.5db to my tv -3.5db to my cable modem All ethernet cables are Cat8 All wires and connections are properly connected and not loose
