Observer

Rough time with DNS drops, T3 errors, and other connectivity issues

Hello!  I've been a TWC/Spectrum customer now for a few months and everything has been pretty **bleep** good until about two or three weeks ago.   I started to get T3 and T4 disconnections and more.  I called TWC and they sent some good inhouse techboys over and they worked their butts off checking and replacing everything in the lines up to and under the house a few days back.  But unfortunately, my issues persist.   Any help would be appreciated.

 

Home 100Mpbs plan,  single user-owned modem:

Model Name: SB6141
Vendor Name: ARRIS Group, Inc.
Firmware Name: SB_KOMODO-1.0.7.0-SCM00-NOSH
Boot Version: PSPU-Boot(25CLK)(W) 1.0.12.18m5
Hardware Version: 8.0

 

Signal Info: https://imgur.com/a/RBIi3

Modem Logs: https://imgur.com/a/GZ0BC

Tracert Logs: https://imgur.com/a/LmQzv

 

If that isn't enough to get started, let me know, thanks to anyone and everyone in advance!

 

 

 

 

7 REPLIES
Expert

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

Modems Acceptance channel bandwidth is exceeded.

 It's got a spread of 140 mHz and max spec is 96 mHz on a 6141.

 

Do a factoty reset and see if you can get the difference between lowest to highest freq channel down below 96 mHz. If you can and a day later, channels are skipped, there's still an ingress issue that spectrum didn't fix

 

 

Observer

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

Alrighty, did a factory reset earlier this morning and recorded the signal values after to see and reference later.

 

After factory reset Signals:  https://i.imgur.com/l8k5RWr.png

 

I'll return tonight or tomorrow with another status update and see the change.

Expert

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

please copy and paste the signal page here, the imgyr links can't be directly viewed and compared... 

All the cahannels are now adjacent, need to see which have a problem and are dropped. Right now it looks like broadcast tv ingress from bad connections...

also need your zip to see what's on air there.

 

Observer

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

I'm very near Fayetteville in North Carolina, ZIP: 28304

 

Here are the current signals:

Downstream 	Bonding Channel Value
Channel ID 	9  	10  	11  	12  	13  	14  	15  	16 
Frequency 	507000000 Hz 	513000000 Hz 	519000000 Hz 	525000000 Hz 	531000000 Hz 	537000000 Hz 	543000000 Hz 	549000000 Hz 
Signal to Noise Ratio 	37 dB 	37 dB 	37 dB 	37 dB 	36 dB 	37 dB 	37 dB 	37 dB 
Downstream Modulation 	QAM256 	QAM256 	QAM256 	QAM256 	QAM256 	QAM256 	QAM256 	QAM256 
Power Level	4 dBmV  	4 dBmV  	4 dBmV  	4 dBmV  	4 dBmV  	4 dBmV  	3 dBmV  	4 dBmV  

Upstream 	Bonding Channel Value
Channel ID 	2  	4  	3  	1 
Frequency 	24200000 Hz 	37000000 Hz 	30600000 Hz 	19400000 Hz 
Ranging Service ID 	7147 	7147 	7147 	7147 
Symbol Rate 	5.120 Msym/sec 	2.560 Msym/sec 	5.120 Msym/sec 	2.560 Msym/sec 
Power Level 	40 dBmV 	42 dBmV 	41 dBmV 	39 dBmV 
 

TimePriorityCodeMessage

Oct 03 2017 23:56:423-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:14:046-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:14:045-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:13:123-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:13:095-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:12:453-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:09:055-WarningT202.0Lost MDD Timeout;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 20:09:055-WarningN/ADS Partial Service Fallback: MDD Lost-> CM in DOCSIS 3.0 Recovery Mode ;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 10:40:566-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 10:40:565-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 10:40:423-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 10:40:325-WarningU102.0TCS Partial Service;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 10:40:306-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Oct 03 2017 10:40:305-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:243-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:17:10:8b:42:9b;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:176-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=20:3d:66:07:f9:34;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Observer

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

And now tonight, the Signals:

 

Downstream Bonding Channel Value
Channel ID11 12 13 15 16 19 24 
Frequency507000000 Hz 519000000 Hz 525000000 Hz 531000000 Hz 543000000 Hz 549000000 Hz 567000000 Hz 597000000 Hz 
Signal to Noise Ratio37 dB 37 dB 37 dB 37 dB 36 dB 36 dB 37 dB 36 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
3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  3 dBmV  4 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency24200000 Hz 37000000 Hz 30600000 Hz 19400000 Hz 
Ranging Service ID7147 7147 7147 7147 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level41 dBmV 42 dBmV 42 dBmV 40 dBmV 
Upstream Modulation[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[1] 16QAM
[2] 64QAM
 
[3] QPSK
[2] 16QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Stats (Codewords)Bonding Channel Value
Channel ID11 12 13 15 16 19 24 
Total Unerrored Codewords4120633392 4072025829 4072050310 4072052701 4071987968 4069247868 4069286687 4069378323 
Total Correctable Codewords49 70 63 79 124 207 150 337 
Total Uncorrectable Codewords565 2059 3017 3056 2917 4335 2694 4382 

 

 


Observer

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

Ouch.    DNS issues popping up this morning

 

Tracing route to howtogeek.com [23.92.23.113]
over a maximum of 30 hops:

  1     4 ms     2 ms     1 ms  192.168.0.1
  2    17 ms    26 ms    16 ms  142.254.198.189
  3    93 ms   128 ms     *     174.111.107.114
  4   125 ms   111 ms    16 ms  cpe-024-025-039-200.ec.res.rr.com [24.25.39.200]
  5    22 ms    15 ms    23 ms  24.93.64.190
  6    66 ms    23 ms    43 ms  bu-ether14.atlngamq46w-bcr00.tbone.rr.com [66.109.6.82]
  7    47 ms    31 ms    31 ms  bu-ether11.atlngamq47w-bcr01.tbone.rr.com [66.109.6.35]
  8    23 ms    22 ms    26 ms  0.ae0.pr1.atl20.tbone.rr.com [107.14.17.184]
  9    28 ms    31 ms    20 ms  ix-ae-14-0.tcore1.A56-Atlanta.as6453.net [64.86.113.37]
 10    46 ms    47 ms    45 ms  if-ae-43-2.tcore2.A56-Atlanta.as6453.net [64.86.113.150]
 11    40 ms    75 ms    40 ms  66.198.154.24
 12    51 ms    39 ms    44 ms  216.6.87.1
 13    40 ms    39 ms    42 ms  216.6.87.242
 14    39 ms    43 ms    38 ms  66.198.111.166
 15    42 ms    45 ms    40 ms  173.255.239.3
 16    39 ms    38 ms    41 ms  23.92.23.113

Trace complete.
PS C:\WINDOWS\system32> tracert google.com

Tracing route to google.com [172.217.11.142]
over a maximum of 30 hops:

  1     1 ms     1 ms     5 ms  192.168.0.1
  2    14 ms    20 ms    10 ms  142.254.198.189
  3    32 ms    40 ms    38 ms  174.111.107.112
  4   592 ms    12 ms    20 ms  24.25.39.198
  5     *       27 ms    31 ms  be36.drhmncev01r.southeast.rr.com [24.93.64.188]
  6    52 ms    35 ms    32 ms  bu-ether15.asbnva1611w-bcr00.tbone.rr.com [66.109.6.80]
  7    38 ms    26 ms    30 ms  0.ae2.pr1.dca10.tbone.rr.com [107.14.17.204]
  8    28 ms    30 ms    34 ms  ix-ae-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
  9    29 ms    30 ms    35 ms  72.14.198.28
 10    51 ms    30 ms    35 ms  108.170.240.113
 11    33 ms    32 ms    35 ms  216.239.49.185
 12    66 ms    35 ms    65 ms  216.239.48.6
 13    35 ms    27 ms    26 ms  216.239.40.130
 14    45 ms    33 ms    50 ms  108.170.236.237
 15    30 ms    32 ms    32 ms  108.170.249.65
 16    31 ms    34 ms    30 ms  108.170.225.107
 17    34 ms    41 ms    26 ms  172.217.11.142

Expert

Re: Rough time with DNS drops, T3 errors, and other connectivity issues

Looks like Broadcast tv ingress, something is corroded or loose, open splitter ports, etc...