dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1463
share rss forum feed

dorkino
Premium
join:2004-02-22
Atlanta, GA

3 edits

[Signals] Daily T4 reboots (high heat to blame?)

Click for full size
Click for full size
Hello friendly DSLReports community,

My SB6121 modem has picked up a habit recently of restarting itself in the afternoons. It seems to do it more often when the temp outside rises above 90F. Could this be just something I need to live with while the weather is hot - i.e. is this normal? And, do you think it's a problem with my equipment/wiring, or could it be the cableco's stuff?

The modem has a wire coming to it that's off of the first split in the box on the outside of the house. However, that wire is spliced two times along the way - once in a bedroom outlet and again in the attic. There's probably a total run of about 100' - 150' or so of coax from the box to the modem.

I've posted my signals and logs. I have noticed that the upstream power level can be up to +5dBmV higher during the hot afternoons. Also note that the new firmware reached my modem during one of the reboots yesterday. This problem preceded the FW update, so I don't suspect it. Although the TLV-11 errors that I'm experiencing now are curious.

I'm considering finding a way to run a wire direct from the outside box to the modem instead of this 3-wire (spliced twice) solution. Good idea, or waste of time?

Edit: Anyone have recommendation on what 100' wire to purchase, offa say Amazon? For cablemodems, does it matter if it's triple or quad shielded, low-loss, or is that mostly just marketing mumbo jumbo designed to get more money out of me?

Edit 2: Looks like I caught one of the downstream channels in T4 time-out status on the signals page. This is a little later in the day now, around 6:45PM, which is about 3 hrs after when the first signals were taken. As you can see, the upstream power has dropped by a few dBmV.

Thank you

Jul 25 2012 14:14:14 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 25 2012 14:14:14 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 25 2012 14:13:31 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 25 2012 13:27:54 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 15:25:26 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 15:25:26 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 15:24:39 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 15:00:14 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 15:00:14 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from shell ;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 14:59:28 6-Notice E112.0 SW download Successful - Via Config file
Jul 24 2012 14:58:51 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 14:58:25 6-Notice E102.0 SW Download INIT - Via Config file d11_m_sb6121_speedtier_c01.cm
Jul 24 2012 14:58:19 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:12 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 24 2012 14:57:33 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;
Jul 23 2012 20:23:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=(redacted);CMTS-MAC=00:00:00:00:00:42;CM-QOS=1.1;CM-VER=3.0;

bdnhsv

join:2012-01-20
Huntsville, AL

Your levels look fine - DS is perfect, and US is just a little hot, but not bad. My guess is there is noise somewhere between you and the node that serves your area. Heat can exacerbate noise in a cable plant. I would recommend you either call your local cable office or use the direct forum here to get the ISP to investigate the problem. If it's a problem with the line coming to your apartment then they should replace it free of charge.


dorkino
Premium
join:2004-02-22
Atlanta, GA

Thanks for your reply. I'm in a house, not an apartment, but the same should apply.

I'm taking a few steps of my own to attempt to isolate the issue. Today, I switched the wire that's going to the cablemodem from the spliced attic line to a wire coming directly from the box to another bedroom, then hooked a RG-59 (didn't have any RG-6 long enough) wire from that drop directly to the modem. The idea is to remove those splices and attic heat from the equation. We'll see how things go today.

Also, I've read about using terminator caps on open ports. In the box outside, there are two splitters: One splits 2-ways with one wire going to the cable modem and the other goes to a 5-way splitter that accepts DC power. That splitter is not currently powered, nor do any of its wires go into anything being used for TV because I cancelled my cable TV service awhile back. However, the DC input port on the splitter was open, so I screwed in a wire that leads to one of the unused bedrooms. But that got me thinking about all of the cable jacks in the bedrooms that currently have nothing attached... any one of those could be introducing noise on the line. So I'm planning on tracking down a terminator cap, disconnecting the 5-way splitter from the 2-way splitter in the outside box, and capping the 2nd port on that 2-way. No idea if this will make a difference, but it feels like the right thing to do.



EG
The wings of love
Premium
join:2006-11-18
Union, NJ
kudos:10
reply to bdnhsv

said by bdnhsv:

Your levels look fine - DS is perfect, and US is just a little hot, but not bad.

That's just one snapshot in time. The return power could be fluctuating even higher out of spec intermittently.

bdnhsv

join:2012-01-20
Huntsville, AL
reply to dorkino

Sorry about the apt vs house statement - must have been thinking about someone else. Definitely a good idea to put caps on open outlets and remove any un-needed splitters. Also make sure any connections you have are nice and tight - more than just hand tightened.


bdnhsv

join:2012-01-20
Huntsville, AL
reply to EG

EG - I agree thus my statement about possible noise.


dorkino
Premium
join:2004-02-22
Atlanta, GA
reply to dorkino

Click for full size
It suddenly occurred to me that since I'm only needing to use the internet services from the cableco, I don't need a splitter at all. There's already a barrel connector that the cableco installed in the box that has a ground wire running from it. I disconnected the wire that leads from it to the 2-way and hooked the cablemodem wire directly to it. My upstream xmit power has lowered a good bit. I suppose I'll want to keep an eye on those downstream power levels as they might be too high at some point. Easy enough to reduce those if they become a problem. We'll see what happens with this config... thanks guys.

andyross
Premium,MVM
join:2003-05-04
Schaumburg, IL

A downstream of +/-5 is ideal. I would only worry if it got to +/-10 or higher.