on 04-05-2023 18:56
Hi...
Firstly let me say I have been an IT engineer for 25 years.
I have a HUB5 in moded mode connected to a draytek 2866
I got a rock solid 540 DL on the 500 connection but having just upgraded to Gig1 The speed varys so much but averages around 500 so in terms of download it's a step back... Upload has increased and is solid at 52.
Before I go through the hassle of contacting VM support I thought I would ask here 🙂
Looking at my superhub there seems to be more errors / warnings but I am not sure what the issue is.
Do I have an issue based on the logs from my hub?
My router is full gigabit capable and is doing very little [no WiFi no QoS etc]
Any thought appreciated...
Thanks
GaZ
Time Priority Description
04-05-2023 13:40:06 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:40:06 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:40:02 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
04-05-2023 13:39:57 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:57 | warning | Dynamic Range Window violation |
04-05-2023 13:39:56 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:56 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:56 | warning | Dynamic Range Window violation |
04-05-2023 13:39:56 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:56 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:56 | warning | Dynamic Range Window violation |
04-05-2023 13:39:56 | warning | Dynamic Range Window violation |
04-05-2023 13:39:56 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:56 | warning | Dynamic Range Window violation |
04-05-2023 13:39:51 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:50 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:47 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:39:45 | notice | Honoring MDD; IP provisioning mode = IPv4 |
04-05-2023 13:24:51 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:24:47 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:24:28 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:24:27 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:24:07 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:24:07 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:23:47 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:23:47 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:23:28 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:23:28 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:23:08 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:23:07 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:21:58 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
04-05-2023 13:21:57 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 04-05-2023 21:26
Can we please have the full upstream and downstream stats?
on 05-05-2023 10:58
Oops... I meant to add that and forgot 😎
Upstream bonded channels
0 | 49600000 | 47.5 | 5120 | QAM 64 | 1 |
1 | 43100000 | 47 | 5120 | QAM 64 | 2 |
2 | 36600000 | 46.5 | 5120 | QAM 64 | 3 |
3 | 30100000 | 46 | 5120 | QAM 64 | 4 |
4 | 23600000 | 45.3 | 5120 | QAM 64 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Downstream bonded channels
1 | 259000000 | -4.1 | 42 | QAM 256 | 16 |
2 | 139000000 | -5.1 | 41 | QAM 256 | 1 |
3 | 147000000 | -5.1 | 41 | QAM 256 | 2 |
4 | 155000000 | -6.3 | 41 | QAM 256 | 3 |
5 | 163000000 | -5.2 | 41 | QAM 256 | 4 |
6 | 171000000 | -5 | 41 | QAM 256 | 5 |
7 | 179000000 | -4.7 | 42 | QAM 256 | 6 |
8 | 187000000 | -4.3 | 42 | QAM 256 | 7 |
9 | 195000000 | -3.9 | 42 | QAM 256 | 8 |
10 | 203000000 | -3.8 | 42 | QAM 256 | 9 |
11 | 211000000 | -4 | 42 | QAM 256 | 10 |
12 | 219000000 | -4.1 | 42 | QAM 256 | 11 |
13 | 227000000 | -4.1 | 42 | QAM 256 | 12 |
14 | 235000000 | -4.2 | 42 | QAM 256 | 13 |
15 | 243000000 | -4.1 | 42 | QAM 256 | 14 |
16 | 251000000 | -4.3 | 42 | QAM 256 | 15 |
17 | 267000000 | -3.9 | 42 | QAM 256 | 17 |
18 | 275000000 | -3.9 | 42 | QAM 256 | 18 |
19 | 283000000 | -3.5 | 42 | QAM 256 | 19 |
20 | 291000000 | -3.4 | 42 | QAM 256 | 20 |
21 | 299000000 | -3.4 | 42 | QAM 256 | 21 |
22 | 307000000 | -3.5 | 42 | QAM 256 | 22 |
23 | 315000000 | -3.6 | 41 | QAM 256 | 23 |
24 | 323000000 | -3.5 | 41 | QAM 256 | 24 |
25 | 331000000 | -3.5 | 41 | QAM 256 | 25 |
26 | 339000000 | -3.4 | 42 | QAM 256 | 26 |
27 | 347000000 | -3.4 | 42 | QAM 256 | 27 |
28 | 355000000 | -3.6 | 42 | QAM 256 | 28 |
29 | 363000000 | -3.3 | 42 | QAM 256 | 29 |
30 | 371000000 | -3.3 | 42 | QAM 256 | 30 |
31 | 379000000 | -3.1 | 42 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 42 | 4 | 0 |
2 | Locked | 41 | 13 | 0 |
3 | Locked | 41 | 13 | 0 |
4 | Locked | 41 | 10 | 0 |
5 | Locked | 41 | 14 | 0 |
6 | Locked | 41 | 9 | 0 |
7 | Locked | 42 | 11 | 0 |
8 | Locked | 42 | 7 | 0 |
9 | Locked | 42 | 28 | 47 |
10 | Locked | 42 | 9 | 0 |
11 | Locked | 42 | 10 | 0 |
12 | Locked | 42 | 11 | 0 |
13 | Locked | 42 | 7 | 0 |
14 | Locked | 42 | 11 | 0 |
15 | Locked | 42 | 9 | 0 |
16 | Locked | 42 | 7 | 0 |
17 | Locked | 42 | 7 | 0 |
18 | Locked | 42 | 10 | 0 |
19 | Locked | 42 | 8 | 0 |
20 | Locked | 42 | 10 | 0 |
21 | Locked | 42 | 5 | 0 |
22 | Locked | 42 | 5 | 0 |
23 | Locked | 41 | 10 | 0 |
24 | Locked | 41 | 9 | 0 |
25 | Locked | 41 | 12 | 0 |
26 | Locked | 42 | 8 | 0 |
27 | Locked | 42 | 8 | 0 |
28 | Locked | 42 | 12 | 0 |
29 | Locked | 42 | 13 | 0 |
30 | Locked | 42 | 4 | 0 |
31 | Locked | 42 | 9 | 0 |
I woke up around 4am and ran a few speedtests on my mobile which gave me 700-800 so better overnight.
Perhaps our connection is just oversubscribed?
05-05-2023 11:32 - edited 05-05-2023 11:33
Downstream power levels are on the low side and may benefit from the fitting of an attenuator. Downstream channel 9 is showing a few post RS errors. I can't see any Docsis 3.1 channels.
You might want to try a 30 second pinhole reset of the hub. Also set up a BQM.
on 08-05-2023 10:13
Hi ZaGaZ,
Thank you for reaching out to us in our community and welcome, sorry to see you were not seeing any improvements in speed after your upgrade, I was able to locate you on our system with the details we have for you and can see you have our Router in Modem Mode, please do a pin reset and put our Router back in Router mode and then run some further checks and send the stats again.
Regards
Paul.
on 08-05-2023 10:38
I had exactly the same issue. A service visit has resolved this with a new hub swapped over from the hub 4. Much better, Wi-Fi speeds have doubled
on 10-05-2023 17:50
Finally had some time today to look into this and I have fixed it - Turns out you have toi enable Hardware acceleration on the Draytek 2866 series to achieve the faster speeds. Not getting full GB 🙂 Thanks everyone...
on 12-05-2023 18:29
Hi ZaGaZ,
Thank you for reaching back out and for the update, glad to hear you have worked out why you didn't see any improvements in speed, you can check what is hitting the Router by doing a speed test Via Sm Knows Real Speed.
If you need any further support, please reach back out.
Regards
Paul.