Participant

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

Nope, nothing loose and the wiring in the house is golden, I did it myself and Im not exactly an amateur...Smiley Wink

 

Ill call TWC and get it elevated to Tier 3 first thing tomorrow.

Expert

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

Post another signal page snapshot, hopefully a reset hasn't cleared it out... That may show an Ingress patern

 

Participant

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

 

DownstreamBonding Channel Value

Channel ID14 
Frequency555000000 Hz 561000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 633000000 Hz 
Signal to Noise Ratio37 dB 38 dB 38 dB 37 dB 37 dB 37 dB 38 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
8 dBmV  8 dBmV  8 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  4 dBmV  

 

UpstreamBonding Channel Value

Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID5047 5047 5047 5047 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level34 dBmV 41 dBmV 41 dBmV 33 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 T4 TimeOut T4 TimeOut Success 

 

Signal Stats (Codewords)Bonding Channel Value

Channel ID14 
Total Unerrored Codewords542620653 541682314 539246057 539271041 539222100 539226376 539229365 301691893 
Total Correctable Codewords438 507 406 259 641 510 328 169 
Total Uncorrectable Codewords4481 4267 6035 5210 4058 2099 1332 2754 

 

 

 

TimePriorityCodeMessage

Apr 13 2016 20:47:523-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 13 2016 20:04:065-WarningU102.0TCS Partial Service;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 13 2016 20:03:523-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;

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Expert

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

get TWC out... you have bad upstream interference, ingress

this proves the point! upstream /reverse path is unstable!

 

Ranging StatusSuccess T4 TimeOut T4 TimeOut Success 
Participant

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

Yep, I saw that earlier tonight, as well as the DS side jumping around channels. 

 

Ill see if I can get TWC out tomorrow and update when that happens.

Spectrum Employee

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

I'm a bit late to seeing this particular topic.  But your forward / downstream signal is borderline high.
This is definitely leaning towards having a tech coming out, but it would be good for whatever phone agent you speak to to carefully check service codes on the account and while they're at it.

If you do have a tech come out, might want to kindly ask for a thoroughput test on the worst-case channel(s), just to be sure it's not jittering around a lot.  Signal stability FTW.

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: Yet another SB6141 issue thread (slow DL speeds)

If you are seeing DS channels change and getting DS partial service, there's a broken or loose connection somewhere allowing broadcast tv in. Make sure everything is not loose but more than finger tight

Nothing obvious, call twc

 

 

Participant

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

Looks like it rebooted over night

 

TimePriorityCodeMessage

Apr 14 2016 06:01:323-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 14 2016 02:14:066-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 14 2016 02:14:065-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 14 2016 02:13:386-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 14 2016 02:13:385-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:203-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;

 

Upstream as of this morning:

UpstreamBonding Channel Value

Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID5641 5641 5641 5641 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level41 dBmV 42 dBmV 42 dBmV 38 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 T4 TimeOut Success 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Expert

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

Yes that's bad,

call it in as modem rebooting due to excessive T4 errors

 

Participant

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

Its not a good thing when T3 support says on the phone "Holy cow, this is bad, like, really BAD", right? Smiley LOL

 

Truck roll happens tonight. Modem is locked up again (I can get to my network from work, but cant get to the diagnostics webpage), so that tells me its probably in T4 timeout again. We will see what the tech says tonight.