Expert

Re: Yet another SB6141 related issue?

you have serious ingress issues. it doesn't affect a router.

The router needs to autodetect wan settings and I doubt you can preconfigure much of anything other than a ssid and the dhcp start.

 

Valued Participant

Re: Yet another SB6141 related issue?

I had to reboot the SB6141 a couple of hours ago after installing the 'new' router as mention in my last post.

 

8 downstream channels at the moment.  Of couse.

 

The 4 upstream are already rearranging ...

 

Signal:

 

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 507000000 Hz 513000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 537000000 Hz 543000000 Hz 
Signal to Noise Ratio39 dB 40 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  8 dBmV  7 dBmV  7 dBmV  7 dBmV  7 dBmV  6 dBmV  6 dBmV  

 

UpstreamBonding Channel Value
Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID3523 3523 3523 3523 
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 Codewords342852701 341965575 341974625 341982827 341961097 341962179 341964429 341991735 
Total Correctable Codewords17 40 18 12 18 
Total Uncorrectable Codewords572 520 540 542 629 654 601 

654 

 

 

 And the log:

 

TimePriorityCodeMessage

Feb 22 2016 15:30:096-NoticeI401.0TLV-11 - unrecognized OID;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 22 2016 15:30:085-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;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 22 2016 15:29:406-NoticeI401.0TLV-11 - unrecognized OID;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 22 2016 15:29:405-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;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 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;

 

 

.

Expert

Re: Yet another SB6141 related issue?

Last partial service was on the 19th, you now have 8 channels in a row. Wonder if TWC fixed something that was loose...

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye types:  Last partial service was on the 19th...

 

I know!  I really, really didn't want to force a reboot today, but I had no choice.  The new router I'm configuring for a friend would not pick up an IP Address for the WAN without the reboot.  I should have tried spoofing the MAC from the router I normally use for my LAN to prevent having to reboot I guess.  Oh, well.

 

...you now have 8 channels in a row.

 

Always been that way after a reboot.  And then, some time later, things start to go south with 'partial service' messages, etc.

 

Wonder if TWC fixed something that was loose...

 

Loose where?  I've seen no TWC in the area in the last 4-5 days.

.

 

Expert

Re: Yet another SB6141 related issue?

Copy and paste the modems signal page again. It show the ingress as higher correction on afflicted channels .

If it's an overhead line and windy, they'll be a lot worst  a calm day

 

Highlighted
Valued Participant

Re: Yet another SB6141 related issue?

This didn't take long.  Lost a downstream channel and got another 'partial' error in the logs

 

@MsRaye types:  Copy and paste the modems signal page again. It show the ingress as higher correction on afflicted channels .

 

Yup, will do next.

 

If it's an overhead line and windy, they'll be a lot worst  a calm day

 

No winds yet, but latest wind advisory for this area:

...WIND ADVISORY REMAINS IN EFFECT FROM NOON TUESDAY TO MIDNIGHT CST TUESDAY NIGHT...

 

Here's 'Signal':

DownstreamBonding Channel Value
Channel ID
Frequency501000000 Hz 507000000 Hz 513000000 Hz 519000000 Hz 531000000 Hz 537000000 Hz 549000000 Hz 
Signal to Noise Ratio39 dB 40 dB 39 dB 39 dB 39 dB 39 dB 39 dB 
Downstream ModulationQAM256 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  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 ID3523 3523 3523 3523 
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 Codewords1047943798 1047056673 1047065717 1047073924 866189576 866190786 866194818 
Total Correctable Codewords23 81 28 25 
Total Uncorrectable Codewords572 520 540 542 1249 2167 1231 

 

And the latest part of the Log:

TimePriorityCodeMessage

Feb 22 2016 21:37:535-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 22 2016 21:37:535-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 22 2016 15:30:096-NoticeI401.0TLV-11 - unrecognized OID;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 22 2016 15:30:085-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;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 22 2016 15:29:406-NoticeI401.0TLV-11 - unrecognized OID;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 22 2016 15:29:405-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:17:10:86:b3:11;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=3c:df:a9:43:ac:bf;CMTS-MAC=00:00:00:00:00:00;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 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

 

 

 

.

Expert

Re: Yet another SB6141 related issue?

Broadcast tv CH 26 @ 543 mHz... caused the DS partial service...

 

Antennapoint/ antennaweb don't show a ch 26 anywhere near Austin, but their data bases are old.

 

stick an antenna on your  set, do a scan , see what's there. You need the actual rf channel or frequency, not the alias

Strongest channels should be the worst problems

 

 

Valued Participant

Re: Yet another SB6141 related issue?

@MsRaye -- Broadcast tv CH 26 @ 543 mHz... caused the DS partial service...

 Antennapoint/ antennaweb don't show a ch 26 anywhere near Austin, but their data bases are old.

 stick an antenna on your  set, do a scan , see what's there. You need the actual rf channel or frequency, not the alias

Strongest channels should be the worst problems

 

There's a CH 26 up in Waco?  Bit far away but at one time I recall seeing some reception from Belton, TX, maybe farther over the air.

 

I have a 'Leaf' (Mohu) antenna (old model, not on their website now) connected I picked up a couple years on a Slickdeals deal.  Did a re-scan this a.m.  26 Digital, 0 analog.  FWIW, here's the list:

 

7-1 KTBC-HD (Fox 7)
7-2 KTBC-SD
7-3 Buzzr
13-5 RF13-5 (Audio only)
14-1 KBVO-CD
18-1 KLRU-HD
18-2 KLRU-CR
18-3 KLRU-Q
18-4 KLRU-VM
24-1 KVUE-DT (ABC)
24-2 NVUE-TV
24-3 KVUE-3
31-3 KTFO-CD
31-2 KAKW-DT
36-1 KXAN DT (NBC)
36-2 COZI TV
36-3 ION TV
42-1 KEYE-DT
42-2 NEYE-TV
54-1 KNVA-HD
54-2 GRIT
54-3 LAFF
62-1 KAKW-DT
62-2 KTFO-CD
62-3 GetTV
62-4 Escape

 

Did I mention, I don't watch TV?

.

Expert

Re: Yet another SB6141 related issue?

nearest 26 is in Waco texas  it's alias is 25.1 long haul @ 60 miles.

m

 

here's the list of rf to aliased channels within 80 miles of you:

database is old:

SignAffiliateRF ChannelVirtual ChannelBandPowerCityDistance Heading

Total results: 17
KNVACW4954.1UHF500.0 kWAustin13.76 mi193.58°
KXAN-TVNBC2136.1UHF700.0 kWAustin13.76 mi193.58°
KLRUPBS2218.1UHF700.0 kWAustin14.08 mi194.24°
KEYE-TVCBS4342.1UHF1000.0 kWAustin14.09 mi194.18°
KVUEABC3324.1UHF1000.0 kWAustin14.09 mi194.18°
KTBCFOX77.1VHF15.86 kWAustin14.74 mi191.02°
KAKW-TVUNIVISION1362.1VHF45.0 kWKilleen20.41 mi314.59°
KNCTPBS4646.1UHF232.34 kWBelton32.97 mi11.88°
KXAM-TVNBC2714.1UHF660.0 kWLlano50.09 mi282.77°
KCWXCW52.1VHF10.24 kWFredericksburg57.99 mi243.09°
KWKTFOX4444.1UHF159.6 kWWaco60.35 mi24.19°
KWBU-TVPBS2034.1UHF700.0 kWWaco60.37 mi23.10°
KCEN-TVNBC96.1VHF25.0 kWTemple60.75 mi30.71°
KWTX-TVCBS1010.1VHF13.8 kWWaco61.09 mi24.53°
KXXVABC2625.1UHF1000.0 kWWaco62.24 mi24.41°
KNIC-TVUNIVISION1817.1UHF223.75 kWBlanco73.10 mi219.09°
KYLEFOX2828.1UHF50.0 kWBryan79.39 mi81.19°
Expert

Re: Yet another SB6141 related issue?

when you compare your scan with my table from antennapoint.com, you are getting channels not on my list indicating they're changes. Maybe one is on 26.

 

The aliases are a PITA....