Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye ... FWIW, on TWC chat with 'Addie' for quite a while this a.m.  I past on your recommendations (minus some of the commentary ;-) ) regarding what needed to be done to fix this issue.  Appointment tomorrow (Feb 19, 6-7pm).  We will see ...?

 

........................................

Edited to add (primarily for my own reference):  I got a call from caller id 'TWC Support' at 1:44pm today letting me know that TWC had been previously working on this issue and now it's 'FIXED'.  The caller, I didn't get his name (he was a bit hard for me to understand), was looking, I think, for confirmation that this issue was fixed so they could cancel tomorrow's appointment.  I disagreed and told them I absolutely wanted someone to come out and look at the drop and pole connections.  I was told that tomorrows appointment would not be able to do that (what!?), but that an appointment for next Tuesday at 'sometime' (I.e., no specific time) would get a tech there to look at the issues with the drop and wiring/hardware on the pole.

 

BTW, looking at the 'Signal' page on the modem, the only change from stats shown below was an increase in 'Total Uncorrected Codewords'.  Understandable since I continue to use the Internet.  ;-)

........................................

 

And for reference here's my latest 'Signal' stats:

 DownstreamBonding Channel Value

Channel ID10 13 14 15 16 
Frequency501000000 Hz 519000000 Hz 531000000 Hz 555000000 Hz 573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 
Signal to Noise Ratio38 dB 38 dB 39 dB 39 dB 39 dB 39 dB 39 dB 39 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
7 dBmV  7 dBmV  6 dBmV  6 dBmV  8 dBmV  7 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID1890 1890 1890 1890 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 47 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 StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID10 13 14 15 16 
Total Unerrored Codewords23742022402 22549678247 22430022149 22077449477 22173271265 19120097102 17598947638 15417909187 
Total Correctable Codewords20 162 178 208 565 257 2293 1618 
Total Uncorrectable Codewords551 5656 6384 8843 10076 8168 117677 146471 

 

And logs:

 

TimePriorityCodeMessage

Feb 16 2016 22:17:275-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 21:44:245-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 21:44:245-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 21:44:016-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 19:41:115-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 19:41:115-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 19:40:466-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 16:25:355-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 16:25:355-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 12 2016 23:07:085-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 12 2016 23:07:085-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

.

 

Expert

Re: Yet another SB6141 related issue?

TWC cannot fix a physical problem remotely...

 

I "see " all too many potential issues on that pole  . Hopefully the tech they send out will replace connectors and escallate the amp issue to the bucket truck crew.

  And like do they now send out techs without ladders?  (saves money on ladder safety training?)

All connectors need to be cut off and replaced, need some shiny copper on the center conductor.

I can see some pencil pusher trying to save money by telling them not to...

 

I have a similar issue downstream from me, a hardline splitter with a hardline tap making a 120 degree bend accross the street to a house set back too far for normal drop (they're cable service is off btw I see the drop to their house is taken off and twc has terminators on the taps 2 ports.) 

Well the wind flexes the hardline at the splitter and the hardlines aluminum condutor is totally broken. I can sit under it with a portable tv and get free cable, lol.

This is not affecting my downstream because it's further downstream and an amp or two past me. BUT, it's allowing upstream noise in that affects everyone on the node and is pushing our upstream levels up to overcome  the noise...  T3's T4's result.

 

And ummm yeah, TWC calls to cancel service calls anyway they can...  "sorta works" is good enough...Woman Sad

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types:  TWC cannot fix a physical problem remotely...

 

Understood.

 

I "see " all too many potential issues on that pole  . Hopefully the tech they send out will replace connectors and escallate the amp issue to the bucket truck crew.

 

I think they are going to try to blow this appointment off, too?  I.e., logged onto my account... there is no evidence of a 'Scheduled Appointment' shown.  I'm going to follow up with some more 'Chat'...  Then again, under 'Equipment|Troubleshoot' my modem is indicated as: 'Not Connected' (red dot) and yet my speeds/connectivity are excellant at this time!  LOL.

 

And like do they now send out techs without ladders?  (saves money on ladder safety training?)

 

LOL, again.

 

All connectors need to be cut off and replaced, need some shiny copper on the center conductor.

 

Got it.  I've consolidated all your comment/recommendation into text document to have handy when/if the tech shows up on Tuesday.

 

Thanks again for you help!

.

Expert

Re: Yet another SB6141 related issue?

another little issue... the hardline to the left of the amp is supposed to be fastened to the messanger cable by a wrap of stainless wire.... looks like it's broken as well and the hardlines loose...

 

 

 I've heard the apt guys in major cities like NY actually work out of a backpack and don't use a van since parkings so bad... lol.

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types:  another little issue... the hardline to the left of the amp is supposed to be fastened to the messanger cable by a wrap of stainless wire.... looks like it's broken as well and the hardlines loose...

 

Ok, added to the '(wish) list'.

 

Thanks

.

Expert

Re: Yet another SB6141 related issue?

Everything out at the pole ponts to damaged  hardline causing your intermittents. The guy they send out can't fix them but needs to get the proper crew to clean that up... Loose and stressed out hardline is a major issue, it will fracture at the connectors

Fractures start out as intermittents and gradually get worst as the aluminum is soft and get's beaten apart over time.

 It can also loosenen up the captive screw for the center conductor, however that doesn't allow ingress or egress.

 

 

 I don't like telling TWC what to do, but in this case they need to clean up the pole. If that ones poorly maintained, you can bet there' s more.

 

 Be sure you tell the tech this is an intermittent issue.  and Online technicians don't like what they see on the pole.

 

.

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye  types:  Everything out at the pole ponts to damaged  hardline causing your intermittents. The guy they send out can't fix them but needs to get the proper crew to clean that up...

...

 

Yes, understood.

 

 I don't like telling TWC what to do, but in this case they need to clean up the pole. If that ones poorly maintained, you can bet there' s more.

 

Agreed.

 

Be sure you tell the tech this is an intermittent issue.  and Online technicians don't like what they see on the pole.

 

I will.  Thanks.

.

Valued Participant

Re: Yet another SB6141 related issue?

Lost some downstream channels AND got some new log entries ...

 

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 513000000 Hz 519000000 Hz 537000000 Hz 543000000 Hz 
Signal to Noise Ratio38 dB 39 dB 39 dB 39 dB 39 dB 
Downstream ModulationQAM256 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
7 dBmV  7 dBmV  7 dBmV  6 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID1890 1890 1890 1890 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 47 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 StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID
Total Unerrored Codewords28882217329 27686808859 27567168163 26743966380 26866296087 
Total Correctable Codewords22 211 190 337 600 
Total Uncorrectable Codewords551 6280 7099 10773 12040 

 

 

logs ...

 

 

TimePriorityCodeMessage

Feb 19 2016 19:48:575-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 19 2016 19:48:575-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 16 2016 22:17:275-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 15 2016 15:12:065-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 21:44:245-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 21:44:245-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 21:44:016-NoticeN/AMDD Recovery following MDD Loss;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Feb 14 2016 19:41:115-WarningT202.0Lost MDD Timeout;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;

 

 

 Edited to add:

 

FWIW...  no noticable deterioration of connectivity at this time.  Speed down/up - excellent...

 

 ⟫ speedtest-cli
0.3.4
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Time Warner Cable (70.123.yyy.zzz)...
Selecting best server based on latency...
Hosted by Suddenlink Communications LLC (Georgetown, TX) [14.55 km]: 53.283 ms
Testing download speed........................................
Download: 113.79 Mbit/s
Testing upload speed..................................................
Upload: 11.45 Mbit/s
Fri Feb 19 20:09:41 CST 2016

.

Expert

Re: Yet another SB6141 related issue?

Yup.. pretty ugly....

Hopefully the only problem is right up on that pole.

 

 

Valued Participant

Re: Yet another SB6141 related issue?

This is mostly for the record.  On TWC Chat today was able to verify that I do have a 'no scheduled time' appointment tomorrow (Feb 23, 2016) on record.

 

The following may seem a bit OT, but really it's not! I have to configure a new router for a friend who lives a couple of states from me.  So that I'm sure the router is stable I'm going to run it for a week or so as my network router before shipping it off to her.  Thus, I may have to reset/reboot my SB6141 even though connectivity remains 'good'.  For now.

 

With that typed, I'm only pasting current 'Signal' info since there have been no additional log entries since the previous 'paste' last Friday, Feb 19, 2016.

 

Signal:

 DownstreamBonding Channel Value

Channel ID11 12 
Frequency501000000 Hz 519000000 Hz 537000000 Hz 561000000 Hz 567000000 Hz 
Signal to Noise Ratio38 dB 38 dB 38 dB 38 dB 37 dB 
Downstream ModulationQAM256 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
7 dBmV  6 dBmV  6 dBmV  7 dBmV  7 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID1890 1890 1890 1890 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level47 dBmV 47 dBmV 47 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 StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID11 12 
Total Unerrored Codewords39600812525 38281060053 38161434832 37180309721 37302604359 
Total Correctable Codewords25 237 224 370 688 
Total Uncorrectable Codewords551 6928 7720 12149 13256 

 

 

FWIW...

.