cancel
Showing results for 
Search instead for 
Did you mean: 

Slow 500 service

WYNIR0
On our wavelength

Upgraded last week from 350 to 500 and even after a call to service team where they sent a new profile to the Hub I'm still maxing at about 320 whereas I peaked at 380 before.  Will post router stats below. Is anyone able to assist please?

 

1 ACCEPTED SOLUTION

Accepted Solutions

Andrew-G
Alessandro Volta

@WYNIR0 What's the position on Downstream post-RS errors? When you last posted those there were a bad number of those.  A post-RS error is a data packet that can't be corrected by the hub's on board error correction, and so the data needs to be re-requested.  That will usually have a dramatic and bad effect on speeds, and the cause is radio frequency noise ingress through a faulty joint or cable.  Be aware that a reboot of the hub resets the error counters to zero.  As this affects lower frequencies, a possible cause is emergency services radio, ham radio or aviation & radar, in which case the noise may be intermittent.

Try undoing and redoing the coax connections for the cable to the hub (finger tight only, both ends of the cable, plus any other VM coax connected gear like splitters or TV boxes).  If after that you still see rising post-RS error counts then it will need a technician visit - the remote "kick" VM can give the hub won't make any difference to a noise ingress fault.

See where this Helpful Answer was posted

12 REPLIES 12

WYNIR0
On our wavelength

Item Status Comments

Acquired Downstream Channel (Hz)
299000000
Locked
Ranged Upstream Channel (Hz)
39399996
Locked
Provisioning State
Online

Downstream bonded channels

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

1299000000237256 qam21
21390000003.436256 qam1
31470000003.535256 qam2
41550000003.436256 qam3
5163000000337256 qam4
6171000000337256 qam5
71790000002.936256 qam6
81870000002.736256 qam7
91950000002.537256 qam8
102030000002.536256 qam9
112110000001.936256 qam10
122190000001.736256 qam11
132270000001.536256 qam12
142350000001.436256 qam13
152430000001.237256 qam14
162510000001.537256 qam15
172590000000.736256 qam16
182670000000.736256 qam17
19275000000136256 qam18
20283000000237256 qam19
212910000002.237256 qam20
223070000002.237256 qam22
23315000000237256 qam23
24323000000237256 qam24

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked37.611111
2Locked36.32228196
3Locked35.7641178
4Locked36.6397133
5Locked37.6246100
6Locked37.3224114
7Locked36.621997
8Locked36.616652
9Locked37.313052
10Locked36.619542
11Locked36.323648
12Locked36.312338
13Locked36.626632
14Locked36.630645
15Locked37.314143
16Locked37.310129
17Locked36.61248
18Locked36.68818
19Locked36.67011
20Locked37.38811
21Locked37.3895
22Locked37.67921
23Locked37.68519
24Locked37.389

20

eneral Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
73254k;fg87dsfd;kfoA,.iye



Primary Downstream Service Flow

SFID20238
Max Traffic Rate575000000
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID20215
Max Traffic Rate38520000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort
 
 

WYNIR0
On our wavelength
Network LogTime Priority Description
22/07/2021 05:50:42noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2021 19:37:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2021 16:15:40noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/07/2021 01:08:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2021 20:18:32noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2021 18:19:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2021 17:25:55noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2021 07:59:50noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/07/2021 07:59:50ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/07/2021 22:07:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2021 21:44:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2021 08:52:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2021 18:17:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2021 08:34:42noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/07/2021 01:24:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:54Warning!ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 07:21:37noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/07/2021 07:21:37ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/07/2021 18:04:11Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2021 04:01:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

WYNIR0
On our wavelength

Downstream bonded channels

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

1299000000237256 qam21
21390000003.436256 qam1
31470000003.535256 qam2
41550000003.436256 qam3
5163000000337256 qam4
6171000000337256 qam5
71790000002.936256 qam6
81870000002.736256 qam7
91950000002.537256 qam8
102030000002.536256 qam9
112110000001.936256 qam10
122190000001.736256 qam11
132270000001.536256 qam12
142350000001.436256 qam13
152430000001.237256 qam14
162510000001.537256 qam15
172590000000.736256 qam16
182670000000.736256 qam17
19275000000136256 qam18
20283000000237256 qam19
212910000002.237256 qam20
223070000002.237256 qam22
23315000000237256 qam23
24323000000237256 qam24



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked37.611111
2Locked36.32228196
3Locked35.7641178
4Locked36.6397133
5Locked37.6246100
6Locked37.3224114
7Locked36.621997
8Locked36.616652
9Locked37.313052
10Locked36.619542
11Locked36.323648
12Locked36.312338
13Locked36.626632
14Locked36.630645
15Locked37.314143
16Locked37.310129
17Locked36.61248
18Locked36.68818
19Locked36.67011
20Locked37.38811
21Locked37.3895
22Locked37.67921
23Locked37.68519
24Locked37.38920

WYNIR0
On our wavelength

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
73254k;fg87dsfd;kfoA,.iye



Primary Downstream Service Flow

SFID20238
Max Traffic Rate575000000
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID20215
Max Traffic Rate38520000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort

 

Item Status Comments
Acquired Downstream Channel (Hz)
299000000
Locked
Ranged Upstream Channel (Hz)
39399996
Locked
Provisioning State
Online

COnfig looks fine - deffo the 500

How are you measuring your speed?



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

WYNIR0
On our wavelength

using the speedtest.net app from a  pc directly wired to the router attached to the Hub. 1Gig Nic and all Cat 6 cables.

Sofia_B
Forum Team (Retired)
Forum Team (Retired)

Hi @WYNIR0

 

Thanks for your post 🙂 

 

I'm very sorry to hear you're experiencing slow speeds, I appreciate this is frustrating and we apologise for any inconvenience caused. 

 

How have things been since posting? I've managed to locate your account and I can see the team sent hits and requested a reboot, has this helped improve the speeds for you? 

 

Let us know.

 

Thanks, 

Sofia
Forum Team



New around here? To find out more about the Community check out our Getting Started guide


Andrew-G
Alessandro Volta

@WYNIR0 What's the position on Downstream post-RS errors? When you last posted those there were a bad number of those.  A post-RS error is a data packet that can't be corrected by the hub's on board error correction, and so the data needs to be re-requested.  That will usually have a dramatic and bad effect on speeds, and the cause is radio frequency noise ingress through a faulty joint or cable.  Be aware that a reboot of the hub resets the error counters to zero.  As this affects lower frequencies, a possible cause is emergency services radio, ham radio or aviation & radar, in which case the noise may be intermittent.

Try undoing and redoing the coax connections for the cable to the hub (finger tight only, both ends of the cable, plus any other VM coax connected gear like splitters or TV boxes).  If after that you still see rising post-RS error counts then it will need a technician visit - the remote "kick" VM can give the hub won't make any difference to a noise ingress fault.

WYNIR0
On our wavelength

Thanks, Speeds still around 300 Mbit. I've been busy with work and kids so not had a chance to look any further as yet. Am on leave for a few days after today so will spend some time on it, check connections, keep an eye on Post RS errors and report back.

 

Appreciate the assistance everyone.