cancel
Showing results for 
Search instead for 
Did you mean: 

no ranging T3, RCS partial service, Lost MDD Timeout

Doobydave
On our wavelength

Hi, 

I am trying to resolve an ongoing issue with both dropouts (a few a week), but more annoyingly Zoom etc chats that stutter and catch up. My headline download and upload speeds are ok. On multiple video chats using many different services the same happens, and others on the call say it's only me with a poor connection.

I am running a Hub 3.0 in modem mode. The stuttering on video calls happens if using wifi or ethernet cable. When using either and close enough to the router my DL speed is over 500mbs and my Upload speed is around 36mbs. Pings, jitter and loss all seem fine.

I am posting a series of logs below - can anyone suggest any ideas?

Many thanks,

Dooby

Network Log

Time Priority Description

07/02/2021 11:02:20noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/02/2021 10:59:45Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2021 18:52:14noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2021 18:52:14ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2021 08:27:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 12:48:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 12:48:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 22:01:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 21:10:40noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 21:10:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 05:18:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2021 09:09:42Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2021 09:26:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 18:08:2Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 18:08:1Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 17:58:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 17:58:19Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 17:57:17Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 17:57:15Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 17:56:17Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12987500006.838256 qam21
21387500005.438256 qam1
31467500005.638256 qam2
41547500005.940256 qam3
5162750000638256 qam4
6170750000638256 qam5
71787500005.938256 qam6
81867500005.338256 qam7
91947500006.138256 qam8
102027500006.340256 qam9
112107500006.538256 qam10
122187500006.538256 qam11
132267500006.338256 qam12
142347500006.338256 qam13
15242750000638256 qam14
162507500005.938256 qam15
17258750000638256 qam16
18266750000638256 qam17
192747500005.938256 qam18
202827500006.538256 qam19
212907500006.538256 qam20
223067500006.938256 qam22
233147500006.838256 qam23
243227500006.938256 qam24

 

39 REPLIES 39

Doobydave
On our wavelength

not all the logs would fir on one post - so more below.

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
yewrkldJKDHSUBsgvca69834n



Primary Downstream Service Flow

SFID27812
Max Traffic Rate690000278
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID27811
Max Traffic Rate44000278
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling Type

BestEffort

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

12580000044.5512064 qam4
23260000045512064 qam3
33940001244.5512064 qam2
44620003943.5512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0020
3ATDMA0000
4ATDMA0000

 

Item Status Comments
Acquired Downstream Channel (Hz)
298750000
Locked
Ranged Upstream Channel (Hz)
25800000
Locked
Provisioning State
Online

and finally.

 

Hub 3.0 device information

The information below shows current status of this Hub 3.0.

Standard specification compliant: DOCSIS 3.0
Hardware version: 10
Software version: 9.1.1912.304
  
  
  
  

Hi all,

An update - I've just completed a speed test while on a particularly bad zoom call. All was fine except the jitter was 173ms.

 

Regards,

Dooby.

So, there's nothing obviously wrong with your router stats - though there's a second table on the Downstream tab that you haven't posted (look for the one with pre and post-rs errors listed, and post that here).

A small number of T3 timeouts is normal - the RCS partial service message, though, indicates that a channel is dropping - lots of them would give cause for concern.. 

It would be worth setting up a BQM to graph the quality of your connection - it sounds like there is potentially an overutilisation issue in your area, and this will help to show whether or not that's the case.. once set up, find the Live Graph and click "Create Sharing Link" - post that back here.

Doobydave
On our wavelength

Thanks tehwolf,

I've signed up and created the broadband monitor a couple of hours ago and got 100% packet loss so need to make some changes in the router settings somewhere.

 

I think this is the second table you mention.

 

Thanks,

Dooby

Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.9150
2Locked38.670
3Locked38.970
4Locked40.980
5Locked40.360
6Locked40.3240
7Locked38.960
8Locked38.6160
9Locked40.360
10Locked40.990
11Locked40.3220
12Locked38.970
13Locked38.970
14Locked38.9110
15Locked38.660
16Locked38.9100
17Locked38.980
18Locked38.670
19Locked38.980
20Locked38.9100
21Locked38.6130
22Locked38.9240
23Locked38.9220
24Locked38.690

it is - thanks - there are no errors showing on there, so no problems with that.

as for the BQM - I've read conflicting reports about how to do this - you may need to try finding the firewall settings and enabling "ICMP echo reply" if you have that option.. i say conflicting reports because I'm sure I've seen people say that this is no longer a configurable option on the hub and that by default they will respond to pings.. but have a look and see if you can find anything.. 

Doobydave
On our wavelength

Hi, tehwolf,

Yes, the Hub 3.0 has no settings to change around ping and does not accept as a matter of course, although mine is in modem mode so that probably makes a difference.

This morning the BQM was a sea of red, but I changed some firewall settings in my Synology router and now it seems to be working as it should. I'll let the day map out and post a screenshot of the results. What's the bet i have zero issues with connection today 🙂

Thanks,

Dooby

Doobydave
On our wavelength

On another posters page, I saw instructions on how to post my live BMQ here, below.

Regards,

Dooby

MY BMQ 

Here's some screenshots.

On 2 of the big packet loss video calls were attempted at those times, and the calls were not possible. The 4am spikes are the router re-booting.

 

Regards,

Dooby

screencapture-www-thinkbroadband-com-broadband-monitoring-quality-view-b13a68563c184eea83ad0935464aace5858915d0-21-02-2021-1614157918970.pngscreencapture-www-thinkbroadband-com-broadband-monitoring-quality-view-b13a68563c184eea83ad0935464aace5858915d0-22-02-2021-1614157872315.pngscreencapture-www-thinkbroadband-com-broadband-monitoring-quality-view-b13a68563c184eea83ad0935464aace5858915d0-23-02-2021-1614157800131.pngscreencapture-www-thinkbroadband-com-my-profile-1614157733184.pngscreencapture-www-thinkbroadband-com-broadband-monitoring-quality-view-b13a68563c184eea83ad0935464aace5858915d0-20-02-2021-1614157953854.png