Browser

Another thread about modem rebooting

Here is log and from what I have already briefly read.

I am seeing a T3 and T4 time out.

Does this indicate a problem with the coaxical from the node? I recieve my line from a power line. After 3 ways spillter outside house (see images below)Then it goes to a  3.5db spillter one half voip modem then to arris docis2 modem. All new cables on spillter side.

We have VOIP, and two digital tv boxes, the digital tv boxes are not after my splitter mentioned.

I hope I gave you enough info.

50mbs service Charlotte Matthews NC 28105

 

Note: After reading this guys thread. His numbers look the same and the problem was clearly outside of the house. I am going to investigate where my line is coming from. Its all underground here I think.

http://forums.timewarnercable.com/t5/Connectivity/Cable-Modem-Reboot-due-to-T4-timeout/td-p/75424/hi...

Anyone care to voice opinion?

May 09 2016 13:39:483-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:23:246-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:23:245-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:23:093-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:22:556-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:22:555-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:203-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:22:123-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:21:283-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:21:123-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:14:593-CriticalR05.0Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:14:576-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:14:565-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:14:266-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:14:265-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:13:413-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:13:403-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
May 09 2016 13:13:403-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=84:61:a0:7d:97:b5;CMTS-MAC=00:17:10:87:8c:90;CM-QOS=1.1;CM-VER=3.0;
9 REPLIES 9
Browser

Re: Another thread about modem rebooting

Channel ID
Frequency555000000 Hz 561000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 
Signal to Noise Ratio38 dB 38 dB 37 dB 37 dB 38 dB 38 dB 38 dB 38 dB 
Downstream ModulationQAM256 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  -5 dBmV  -5 dBmV  -4 dBmV  -4 dBmV  -5 dBmV  -4 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID3908 3908 3908 3908 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level43 dBmV 43 dBmV 42 dBmV 46 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusT4 TimeOut T4 TimeOut Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID
Total Unerrored Codewords63441746 62509445 62521273 62528191 62505406 62504957 62508647 62529013 
Total Correctable Codewords211 50 140 109 18 130 99 
Total Uncorrectable Codewords1365 2461 637 2254 1891 3551 1810 1754 
Browser

Re: Another thread about modem rebooting

Here are images from what where I think the node is and outside my house. I could be wrong about node though.

OK wrong about node. last picture is from the power lines that end in my front yard. I live at end of a street. I seemed to located where the line is coming from.

 

Spectrum Employee

Re: Another thread about modem rebooting

Oooooh! Photos!  Heart

 

Ok here's your aggregate signal level history for the past week or two.

It wiggles around more than I'd like to see on the upstream/return/transmit signal power.

What worries me is that transmit power level your modem is pushing.

There's been a few times it's exceeded the acceptable ranges for a SB6141:

Spoiler
date & timeForwardReturnForward SNR
2016-04-25 16:21:25-2.54237.9
2016-04-25 18:19:07-34237.6
2016-04-25 20:18:10-2.44237.9
2016-04-25 22:16:45-3.243.837.6
2016-04-26 00:17:46-2.542.837.3
2016-04-26 02:18:38-342.837.6
2016-04-26 04:16:33-2.542.837.9
2016-04-26 06:18:39-2.542.837.6
2016-04-26 08:18:22-2.842.837.6
2016-04-26 10:27:33-2.942.837.6
2016-04-26 12:23:56-2.942.837.6
2016-04-26 14:22:12-3.54237.3
2016-04-26 16:15:55-3.34237.3
2016-04-26 18:19:01-3.54237.6
2016-04-26 20:19:53-3.44237.3
2016-04-26 22:17:13-348.337.6
2016-04-27 00:17:01-2.648.337.9
2016-04-27 02:23:32-3.248.337.6
2016-04-27 04:18:52-3.348.337
2016-04-27 06:17:38-3.348.337.6
2016-04-27 08:26:39-3.748.337
2016-04-27 10:23:39-3.848.337
2016-04-27 12:24:18-3.648.337
2016-04-27 14:21:34-3.248.337
2016-04-27 16:20:02-3.748.337
2016-04-27 18:17:55-3.648.337
2016-04-27 20:24:06-2.948.337.6
2016-04-27 22:16:54-2.43837.9
2016-04-28 00:19:22-2.63837.9
2016-04-28 02:26:00-340.837.6
2016-04-28 04:24:41-2.449.537.9
2016-04-28 06:19:09-2.549.537.9
2016-04-28 08:26:03-2.549.537.9
2016-04-28 10:18:59-4.149.537.3
2016-04-28 12:17:41-4.549.537.3
2016-04-28 14:18:16-3.249.537.3
2016-04-28 16:22:57-3.549.337.3
2016-04-28 18:17:34-3.349.337.6
2016-04-28 20:21:26-349.337.3
2016-04-28 22:20:04-349.337.3
2016-04-29 00:17:01-2.650.537.9
2016-04-29 02:24:11-2.750.337.6
2016-04-29 04:24:35-2.95137.6
2016-04-29 06:24:00-3.95137
2016-04-29 08:22:11-3.95137
2016-04-29 10:26:50-3.75137
2016-04-29 12:18:25-3.65137.3
2016-04-29 14:16:36-3.55137.3
2016-04-29 16:17:30-3.75137.6
2016-04-29 18:17:55-4.65137.6
2016-04-29 20:16:55-442.337
2016-04-29 22:17:59-2.642.537.6
2016-04-30 00:21:46-2.650.537.6
2016-04-30 02:18:35-3.34237.6
2016-04-30 04:25:19-2.75037.6
2016-04-30 06:25:04-2.942.837.6
2016-04-30 08:17:20-2.842.837.9
2016-04-30 10:18:23-3.242.837.6
2016-04-30 12:16:03-3.543.337.6
2016-04-30 14:18:07-3.650.837.3
2016-04-30 16:16:31-3.750.837.3
2016-04-30 18:18:20-3.850.837.9
2016-04-30 20:22:51-3.550.837.9
2016-04-30 22:16:06-3.555.837.9
2016-05-01 00:15:46-3.554.537.3
2016-05-01 02:23:22-4.246.337.3
2016-05-01 04:23:42-4.346.337.6
2016-05-01 06:22:47-4.346.337.6
2016-05-01 08:17:58-4.346.337.6
2016-05-01 10:26:47-348.337.6
2016-05-01 12:18:50-3.54337.6
2016-05-01 14:22:31-3.255.337.6
2016-05-01 16:23:10-442.837
2016-05-01 18:21:50-4.24137
2016-05-01 20:18:04-4.341.537.3
2016-05-01 22:22:05-445.837.9
2016-05-02 00:19:50-3.851.537
2016-05-02 02:25:34-4.54037.3
2016-05-02 04:17:32-4.54037.6
2016-05-02 06:17:41-4.44037.6
2016-05-02 08:25:42-4.44037.6
2016-05-02 10:24:33-4.34637.6
2016-05-02 12:19:26-3.352.537.3
2016-05-02 14:22:26-3.941.537
2016-05-02 16:22:03-2.946.337.6
2016-05-02 18:21:44-3.34537.3
2016-05-02 20:17:24-3.443.837.3
2016-05-02 22:16:48-3.643.837
2016-05-03 00:23:45-3.242.337.3
2016-05-03 02:22:07-3.642.337.3
2016-05-03 04:23:19-3.642.337.6
2016-05-03 06:25:24-3.642.337.3
2016-05-03 08:22:40-3.54137
2016-05-03 10:18:13-3.84737
2016-05-03 12:23:30-3.84737
2016-05-03 14:19:58-3.453.337
2016-05-03 16:18:05-443.337.3
2016-05-03 18:22:40-3.65437
2016-05-03 20:23:17-3.55437
2016-05-03 22:16:53-4.447.537.3
2016-05-04 00:17:53-4.348.537.6
2016-05-04 02:21:47-3.552.837.3
2016-05-04 04:24:30-3.151.837.6
2016-05-04 06:18:52-3.442.537.3
2016-05-04 08:19:59-4.242.537
2016-05-04 10:27:02-4.15437.3
2016-05-04 12:16:40-4.742.537.3
2016-05-04 14:17:31-3.84237.6
2016-05-04 16:16:56-4.14237.3
2016-05-04 18:21:19-3.74237
2016-05-04 20:18:54-4.24237.6
2016-05-04 22:16:47-3.44237.6
2016-05-05 00:23:15-3.24237.6
2016-05-05 02:21:51-4.24237.6
2016-05-05 04:19:16-4.14237.6
2016-05-05 06:23:29-2.94237.6
2016-05-05 08:18:51-2.94237.6
2016-05-05 10:19:36-3.74237
2016-05-05 12:18:49-3.74237
2016-05-05 14:23:07-3.54237.6
2016-05-05 16:19:48-3.44237.3
2016-05-05 18:16:50-3.74237.3
2016-05-05 20:16:39-2.943.537.6
2016-05-05 22:19:39-443.537.9
2016-05-06 00:17:48-3.243.337.6
2016-05-06 02:25:42-3.343.337.3
2016-05-06 04:21:32-3.143.337.6
2016-05-06 06:25:50-3.143.337.6
2016-05-06 08:22:26-3.443.337.6
2016-05-06 10:26:28-3.554.337.3
2016-05-06 12:19:43-3.753.837
2016-05-06 14:18:19-3.653.837
2016-05-06 16:17:12-3.653.837
2016-05-06 18:22:39-3.553.837
2016-05-06 20:17:27-3.453.837.3
2016-05-06 22:17:04-4.341.837.6
2016-05-07 00:19:38-3.248.537.6
2016-05-07 02:17:38-351.337.6
2016-05-07 04:17:49-352.337.6
2016-05-07 06:19:42-2.750.537.6
2016-05-07 08:18:08-3.347.837.3
2016-05-07 10:26:35-3.852.337
2016-05-07 12:19:00-4.539.837.3
2016-05-07 14:17:02-3.952.337
2016-05-07 16:16:31-3.952.337
2016-05-07 18:22:38-3.852.837
2016-05-07 20:19:56-441.537.6
2016-05-07 22:22:30-3.845.837
2016-05-08 00:15:40-4.34137.6
2016-05-08 02:18:24-3.652.837.3
2016-05-08 04:25:02-3.642.537
2016-05-08 06:22:05-3.642.537.3
2016-05-08 08:25:46-3.742.537
2016-05-08 10:24:57-3.652.537
2016-05-08 12:15:44-3.552.337.3
2016-05-08 14:17:57-4.343.837.6
2016-05-08 16:16:26-3.943.837
2016-05-08 18:19:48-3.843.837
2016-05-08 20:18:51-3.843.837
2016-05-08 22:21:21-3.443.837.3
2016-05-09 00:19:38-3.250.837.3
2016-05-09 02:17:12-443.337
2016-05-09 04:21:40-3.144.337.6
2016-05-09 06:19:04-3.946.837
2016-05-09 08:17:17-4.146.837.3
2016-05-09 10:25:40-3.946.837
2016-05-09 12:22:55-4.546.837
2016-05-09 14:17:28-4.54337.3

 

 

So... Might be related to the T3 & T4 time-out channel errors I was thinking...

 

 

Looks like I'm getting closer to the issue, because these seem to be the channels having the specific issue:

Logical Upstream/Return Channel 12/13.0/0 (19.4 MHz)

Corrected10.0509%
Uncorrected492.4924%

 

 

Logical Upstream/Return Channel 12/13.1/0 (24.2 MHz)

Corrected2437.8768%
Uncorrected130.4214%

 

Now there's not a lot of upstream data, so these percentage ratio should easily shift.  But if they are representative of what's going on regularly, this could be a problem, yes... The 30.6 MHz and 37 MHz upstream channels are just fine btw (at least from what I saw as of now).

 

 

~edit~

 

PS: I don't particularly like how sharply those wires must be bent/curved when that cover is back on.  They say not to twist or kink the coax wiring with sharp turns because it actually alters the 75 Ohm rating.  If you must to a sharp 90 degree turn, they make fittings for that purpose.  Sometimes though in real-world engineering you get "close enough"

 

which reminds me of a related joke:

  • A mathematician moves through a room towards a doorway and get infinitely close to the door but never actually stands in the doorway.  Hour after hour passes until finally the mathmatician can't feasibly tell if they've reached the limit.
  • An engineer walks into the doorway, shrugs and says "close enough plus or minor acceptable tolerances"


So my point about the wiring is that as long as it gets the job done, as some point you just have to call the job done (like the engineer).  The rebooting issue isn't likely caused by the wiring in the picture, but rather the loss of upstream channels.

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.
Browser

Re: Another thread about modem rebooting

Hehe yeah I read about posting the photos Smiley Wink

My across the street neighbor had some techs over so I ran over there after they were finished and saw me running and pretend to run away lol because it was 5:00pm.

That was so funny. So he told me to put ticket in and gave me his number.

That bend cable was installed by TWC employee hehe.

 

Agent5x thanks a lot, but what do you recommend?

To get a tech out here?

What will they be able to do that I cannot and I am like entry level knowledge when it comes to understanding how all this stuff works. Could you elaborate just a few more sentences about your concerns about my modem return power?

 

I highighted questions if you just wanted to read those to make things easier.

I enjoyed your reply and thanks!

Dave

Spectrum Employee

Re: Another thread about modem rebooting

In layman's terms, I strongly suspect a leak somewhere in the vacinity of your address, and you are having intermittent service issues that need to be addressed. Your modem's log and this spiking return signal power are your best evidence.

 

You may have noticed how coaxial cable has those screw-on hex-bolt-like connectors?  That's to keep the sensitive signals inside, in; and keep electromagnetic interference outside, out.

 

In your case, to get more specific, your modem is having to push too hard to "return" signals back "upstream" to TWC's servers to your neighborhood's node.  It's that node and the CMTS (cable modem termination server). The CMTS controls the nodes and they are connected together by insanely fast fiber optic cable.  It is this CMTS that is telling my tools about the errors being encountered in your modem's transmission back to the node.

 

Upstream issues are occassionally an issue with the modem's internal electronics, but I'd say are just as likely to be a bad amplifier somewhere (inside your home if there is one, or on the street you live on).  Usually when the modem starts to fail, it makes this easy-to-see pattern of increasing times it goes offline and the period that it's offline gets longer.  I'm not seeing that with your modem, thus I suspect a leak more.  But the specific, root cause is unknown until a tech can physically see & measure things on-site.

 

So yes. Tech please.  Polite (b/c asking for help), yet persistent (because it's your service & monthly cost) should be your motto for this issue.

 

 

 

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.
Expert

Re: Another thread about modem rebooting

Make sure that the modem splitter is on the -3.5 db port outside not one of the 2 -7dB  ports.

 Break loose all the conncections outside and snug them down more than finger tight.  use a 7/16 or small crescent wrench

 

 

 

 BTW, "node" is everyone that is connected to the same CMTS as you, usually on a single fiber pair to coaxial hardline feeding several hundred homes

 

Browser

Re: Another thread about modem rebooting

MsRaye:

Yes I uh was editing post and forgot to remove the node part. I thought I was getting line from other source.

Even had to remove pictures I posted, it was embarrasing.

 

After I looked at the photos all the cables were cut at spliter.

Its obvious my lack of knowledge in this area.

Thanks!

Cat Surprised

 

Agent5x:

 

Thanks! I really enjoyed all the information. Its was nice

Expert

Re: Another thread about modem rebooting

But is your problem fixed?

 

Spectrum Employee

Re: Another thread about modem rebooting


@laudium wrote:

 

 

Agent5x:

 

Thanks! I really enjoyed all the information. Its was nice


Np, hope it helped. Smiley Happy
I'm always happy to teach when people are willing to listen & learn. (I mean this as a compliment towards you)

 

And as always photos are awesome to have on these forums -- it really gives some context to the discussion.

My postings on this site are my own, off-the-clock, and don’t necessarily represent TWC’s/Charter's strategies or opinions.