23-07-2021 10:27 - edited 23-07-2021 10:32
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?
Answered! Go to Answer
on 26-07-2021 08:47
@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.
on 23-07-2021 10:29
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
1 | 299000000 | 2 | 37 | 256 qam | 21 |
2 | 139000000 | 3.4 | 36 | 256 qam | 1 |
3 | 147000000 | 3.5 | 35 | 256 qam | 2 |
4 | 155000000 | 3.4 | 36 | 256 qam | 3 |
5 | 163000000 | 3 | 37 | 256 qam | 4 |
6 | 171000000 | 3 | 37 | 256 qam | 5 |
7 | 179000000 | 2.9 | 36 | 256 qam | 6 |
8 | 187000000 | 2.7 | 36 | 256 qam | 7 |
9 | 195000000 | 2.5 | 37 | 256 qam | 8 |
10 | 203000000 | 2.5 | 36 | 256 qam | 9 |
11 | 211000000 | 1.9 | 36 | 256 qam | 10 |
12 | 219000000 | 1.7 | 36 | 256 qam | 11 |
13 | 227000000 | 1.5 | 36 | 256 qam | 12 |
14 | 235000000 | 1.4 | 36 | 256 qam | 13 |
15 | 243000000 | 1.2 | 37 | 256 qam | 14 |
16 | 251000000 | 1.5 | 37 | 256 qam | 15 |
17 | 259000000 | 0.7 | 36 | 256 qam | 16 |
18 | 267000000 | 0.7 | 36 | 256 qam | 17 |
19 | 275000000 | 1 | 36 | 256 qam | 18 |
20 | 283000000 | 2 | 37 | 256 qam | 19 |
21 | 291000000 | 2.2 | 37 | 256 qam | 20 |
22 | 307000000 | 2.2 | 37 | 256 qam | 22 |
23 | 315000000 | 2 | 37 | 256 qam | 23 |
24 | 323000000 | 2 | 37 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.6 | 111 | 11 |
2 | Locked | 36.3 | 2228 | 196 |
3 | Locked | 35.7 | 641 | 178 |
4 | Locked | 36.6 | 397 | 133 |
5 | Locked | 37.6 | 246 | 100 |
6 | Locked | 37.3 | 224 | 114 |
7 | Locked | 36.6 | 219 | 97 |
8 | Locked | 36.6 | 166 | 52 |
9 | Locked | 37.3 | 130 | 52 |
10 | Locked | 36.6 | 195 | 42 |
11 | Locked | 36.3 | 236 | 48 |
12 | Locked | 36.3 | 123 | 38 |
13 | Locked | 36.6 | 266 | 32 |
14 | Locked | 36.6 | 306 | 45 |
15 | Locked | 37.3 | 141 | 43 |
16 | Locked | 37.3 | 101 | 29 |
17 | Locked | 36.6 | 124 | 8 |
18 | Locked | 36.6 | 88 | 18 |
19 | Locked | 36.6 | 70 | 11 |
20 | Locked | 37.3 | 88 | 11 |
21 | Locked | 37.3 | 89 | 5 |
22 | Locked | 37.6 | 79 | 21 |
23 | Locked | 37.6 | 85 | 19 |
24 | Locked | 37.3 | 89 | 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
SFID | 20238 |
Max Traffic Rate | 575000000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 20215 |
Max Traffic Rate | 38520000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
on 23-07-2021 10:30
22/07/2021 05:50:42 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 19:37:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 16:15:40 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 01:08:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 20:18:32 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 18:19:54 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 17:25:55 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 07:59:50 | notice | DHCP 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:50 | Error | DHCP 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:13 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 21:44:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/07/2021 08:52:31 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/07/2021 18:17:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/07/2021 08:34:42 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/07/2021 01:24:48 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:54 | Warning! | ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/07/2021 07:21:37 | notice | DHCP 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:37 | Error | DHCP 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:11 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/07/2021 04:01:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 23-07-2021 10:31
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 299000000 | 2 | 37 | 256 qam | 21 |
2 | 139000000 | 3.4 | 36 | 256 qam | 1 |
3 | 147000000 | 3.5 | 35 | 256 qam | 2 |
4 | 155000000 | 3.4 | 36 | 256 qam | 3 |
5 | 163000000 | 3 | 37 | 256 qam | 4 |
6 | 171000000 | 3 | 37 | 256 qam | 5 |
7 | 179000000 | 2.9 | 36 | 256 qam | 6 |
8 | 187000000 | 2.7 | 36 | 256 qam | 7 |
9 | 195000000 | 2.5 | 37 | 256 qam | 8 |
10 | 203000000 | 2.5 | 36 | 256 qam | 9 |
11 | 211000000 | 1.9 | 36 | 256 qam | 10 |
12 | 219000000 | 1.7 | 36 | 256 qam | 11 |
13 | 227000000 | 1.5 | 36 | 256 qam | 12 |
14 | 235000000 | 1.4 | 36 | 256 qam | 13 |
15 | 243000000 | 1.2 | 37 | 256 qam | 14 |
16 | 251000000 | 1.5 | 37 | 256 qam | 15 |
17 | 259000000 | 0.7 | 36 | 256 qam | 16 |
18 | 267000000 | 0.7 | 36 | 256 qam | 17 |
19 | 275000000 | 1 | 36 | 256 qam | 18 |
20 | 283000000 | 2 | 37 | 256 qam | 19 |
21 | 291000000 | 2.2 | 37 | 256 qam | 20 |
22 | 307000000 | 2.2 | 37 | 256 qam | 22 |
23 | 315000000 | 2 | 37 | 256 qam | 23 |
24 | 323000000 | 2 | 37 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.6 | 111 | 11 |
2 | Locked | 36.3 | 2228 | 196 |
3 | Locked | 35.7 | 641 | 178 |
4 | Locked | 36.6 | 397 | 133 |
5 | Locked | 37.6 | 246 | 100 |
6 | Locked | 37.3 | 224 | 114 |
7 | Locked | 36.6 | 219 | 97 |
8 | Locked | 36.6 | 166 | 52 |
9 | Locked | 37.3 | 130 | 52 |
10 | Locked | 36.6 | 195 | 42 |
11 | Locked | 36.3 | 236 | 48 |
12 | Locked | 36.3 | 123 | 38 |
13 | Locked | 36.6 | 266 | 32 |
14 | Locked | 36.6 | 306 | 45 |
15 | Locked | 37.3 | 141 | 43 |
16 | Locked | 37.3 | 101 | 29 |
17 | Locked | 36.6 | 124 | 8 |
18 | Locked | 36.6 | 88 | 18 |
19 | Locked | 36.6 | 70 | 11 |
20 | Locked | 37.3 | 88 | 11 |
21 | Locked | 37.3 | 89 | 5 |
22 | Locked | 37.6 | 79 | 21 |
23 | Locked | 37.6 | 85 | 19 |
24 | Locked | 37.3 | 89 | 20 |
on 23-07-2021 10:31
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
SFID | 20238 |
Max Traffic Rate | 575000000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 20215 |
Max Traffic Rate | 38520000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
Acquired Downstream Channel (Hz) | 299000000 | Locked |
Ranged Upstream Channel (Hz) | 39399996 | Locked |
Provisioning State | Online |
on 23-07-2021 10:50
on 23-07-2021 10:56
using the speedtest.net app from a pc directly wired to the router attached to the Hub. 1Gig Nic and all Cat 6 cables.
on 26-07-2021 08:31
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,
New around here? To find out more about the Community check out our Getting Started guide
on 26-07-2021 08:47
@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.
on 28-07-2021 08:58
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.