PerroLoco's profile

New Contributor

 • 

4 Messages

Saturday, June 20th, 2015

Closed

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

DownstreamBonding 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  

UpstreamBonding Channel Value
Channel ID
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  18  20  194  77 
Total Uncorrectable Codewords 602  542  541  1449  1508  1600  1506  583 

Former Moderator

 • 

7.1K Messages

10 years ago

@PerroLoco

T3 events are a symptom of a basic upstream signal/communication issue.  It sounds like you've already done a basic check of the connections.  If that hasn't helped it will likely be necessary for a technician to come out and take a look.

New Contributor

 • 

4 Messages

10 years ago

Hi Chris - that's kind of what I was thinking. Let me know how I can facilitate.

Other thoughts for the record:

  • I've read elsewhere that heat may degrade signal on older coax. Since my modem resets around the same time every day I started wondering if some older cabling is getting hit by the sun at that time. I've looked around the house but haven't found anything obvious.
  • I've also read that signal amps with active return may resolve the problem, but didn't want to go there without checking the basics first (such as a visit by a technician).

Thanks for the help.

New Contributor

 • 

11 Messages

10 years ago

God luck, took me a year, three gateway upgrades and cox blaming faulty equipment to fix the problem. I did everything they asked for a solid year and it ended up being the trunk/node. they much rather have spent over 30 hours in field tech services rewire a house 2x then to ever check the Node/ Trunk which is what T3/T4 is referring to. 

My node was split about a month ago and have experienced zero of the problems I had before. Good luck getting someone who actually wants to work for you on the phone. It took me a year of headaches and dropping service to finally get someone on the phone to escalate the issue. 

New Contributor

 • 

4 Messages

10 years ago

Thanks for chiming in Diskrete, and sorry it was such a hassle. This was my own fear having been through something similar with other service providers.

The Cox tech came out this morning and replaced my coax connector from the wall to the modem. He also disconnected some old splitters I didn't know were out in the box. Since then there have been no new errors in the modem's logs, including during the time of day when the modem was rebooting itself. It's only been a few hours, so it's too early to tell if it's truly fixed, but the initial indications are good.

New Contributor

 • 

48 Messages

10 years ago

Don't spend any money and don't listen to Cox when they try to tell you that the problem is on your end.  The problem is with their signal.  Mine drops out constantly and I like many others have spent a small fortune trying to fix a problem that wasn't mine to fix.  There either needs to be some kind of real resolution to this, or there needs to be a legal remedy.

New Contributor

 • 

6 Messages

10 years ago

Don't know if this will help but my Motorola was slow and intermittently dropping the connection every 10 minutes or so. Tried everything I knew and then noticed that I have moved some boxes near [on it] and when I took them off the modem was very warm.

Put it in a well ventilated place, cooled off and since then [4 days] zero problems.

John

New Contributor

 • 

4 Messages

10 years ago

Update:

  • The outage I was getting about the same time every day hasn't recurred.
  • Still seeing errors but way fewer. Less than 20 rows in the logs and only a few T3-timeouts since repairs done on 5/23. No log entries whatsoever since 5/24 (currently 5/27)
  • Signal levels are improved and holding steady. Downstream levels hover around zero dBvM. Upstream consistently in low-to-mid 40s.

New hypothesis: Old splitters were diffusing the upstream signal just enough to trigger modem reboots. Why it was daily around the same time I can't be sure. Possibly when the sun hit the box on the house? I may never know.

Recent Discussions

View More

Loading...