Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

Maxx upgrade happened for us tonight, so I did a clean reboot. Ill kee an eye on these over the next few days.

 

DownstreamBonding Channel Value

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 38 dB 37 dB 37 dB 38 dB 37 dB 37 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
6 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dBmV  5 dBmV  5 dBmV  

 

UpstreamBonding Channel Value

Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID2354 2354 2354 2354 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level38 dBmV 37 dBmV 40 dBmV 40 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value

Channel ID
Total Unerrored Codewords8508443 7651415 7660833 7669899 7645881 7647937 7651050 7652203 
Total Correctable Codewords18 13 16 23 
Total Uncorrectable Codewords503 1285 516 542 1656 675 672 568 

 

Apr 27 2016 19:44:266-NoticeI502.0Received REG-RSP while in REG-HOLD1 state;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:43:236-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:43:225-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:42:556-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:42:555-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:42:353-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:42:053-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:41:346-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 19:41:345-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot from GUI/Configuration page ;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 14:31:173-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 00:42:346-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 00:42:335-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 00:42:133-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 00:40:526-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 00:40:525-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:06:233-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;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:a8:03:d6;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 27 2016 00:33:233-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;
Apr 26 2016 18:27:135-WarningT202.0Lost MDD Timeout;CM-MAC=84:61:a0:a8:03:d6;CMTS-MAC=00:17:10:86:ab:cb;CM-QOS=1.1;CM-VER=3.0;

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Expert

Re: Yet another SB6141 issue thread (slow DL speeds)

repost the level page in  a few hourslet's see if they cleaned up whatever was causing the ingress on multiple channels, especially ch1, the home- primary channel causing the "RCS Primary DS Failure"

 

Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

Hate to drag this one back to the top, but Im finally getting somewhere with TWC.

 

In the past 2-3 months, Ive had maintenance out at the house multiple times. Incrementally better, but still having this DS Partial Service fallback issue. Multiple Tier 3 calls, multiple truck rolls. No resolution.

 

Had a tech yesterday for an honest-to-God modem failure (under warranty thankfully) who sub'd me a Technicolor modem for the meantime. In doing some testing, we picked up a significant amount of noise on the drop between the hut in the driveway and the house box. Maintenance is being scheduled to dig and replace the line in the next few weeks while I wait on a modem replacement. Hoping that this fixes the issue going forward.

Expert

Re: Yet another SB6141 issue thread (slow DL speeds)

Is this on a temporary line and has the issue stopped?

 

Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

Unfortunately, no, issue hasnt stopped.

 

In the past 3 weeks, I had the Technicolor modem which also had T3 timeouts. I got the Arris warranty replacement and less than 24 hours after activating, I get this. 

 

Download speeds at 200k. I literally am at my wits end with this. Smiley Mad

Sharer

Re: Yet another SB6141 issue thread (slow DL speeds)

Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

No, but I have now. Is there a way you could get me your support or ticket information? Ive got a truck roll happening on Wednesday and Id like to provide that so they wont give me the "its just you". If you know what node youre on, that would be helpful as well.

Sharer

Re: Yet another SB6141 issue thread (slow DL speeds)

You're in Belews Creek, I'm in Greensboro, so TWC likely would see them as unrelated to each other.  I don't know the support ticket number, was never told it by anyone.  If there are any posts in my thread that you think would support your tech visit, click the Options link in the upper right corner of the post(s) and click Print, to print out the post.  Show them to the tech who comes.  

Since the TWC engineers here are now testing the leased SB6141 they have, and my tech Billy is still on the case, you can try having your tech call Billy when you see him.  I cam send you the number in a private message here on the forum.  Billy may be able to explain what the engineers are looking at, if the cases are similar.  I recommend having the tech call, not you, as Billy may not appreciate getting calls from customers he's not involved with on their issues. 

I still think the issue is line noise/ingress/interference, and the SB6141 is more sensitive to it than other brands and models.  Interestingly, my issue didn't start till the TV stations converted over to encrypted digital and we all had to switch to digital adapter boxes on TV, in October 2015 through mid-January 2016.  Suddenly I started having these Internet issues at that time.

Participant

Re: Yet another SB6141 issue thread (slow DL speeds)

You know whats interesting? Thats about when this issues started for me as well IIRC. I had the modem for months at the new house with nary an issue...

 

 

Expert

Re: Yet another SB6141 issue thread (slow DL speeds)

You too have serious broadcast tv ingress.

. Are you two on the same head end?

 633 has a poor s/n , but i don't show a ch 41 on air there, it may be bleed from ch 40 as they overlap the cable ch's.

 Here's the printout.:

http://www.tvfool.com/?option=com_wrapper&Itemid=29&q=id%3de2cba5ade73879

 For a start, all extra spliters need to be removed and all connectors replaced to see if that reduces or eliminates the problem...