on 11-03-2023 11:39
Hi, Looked through the forums and saw a similar post to mine so thought I'd ask a similar question and hopefully get some insight and quite happy to wait my turn for mods to get round to advising but obviously appreciate any input other members have.
Upgraded to the 1Gb yesterday and although getting much faster speeds it's not quite as high as I'd hoped for but not far off so perhaps there's something simple that can be done to squeeze every last drop out of my connection.
Got a hub 5 in modem mode
Cat 6 cable connected to the 2.5g port
connected to 2.5g port on my Asus RT-AX86U router
Speed test results on router come in as
Acquired Downstream Channel(Hz) | 203000000 | Locked |
Ranged Upstream Channel(Hz) | 60300000 | Ranged |
Provisioning State | Online | Operational |
Downstream bonded channels
1 | 203000000 | 2.3 | 39 | QAM 256 | 9 |
2 | 139000000 | 2.1 | 39 | QAM 256 | 1 |
3 | 147000000 | 2.1 | 39 | QAM 256 | 2 |
4 | 155000000 | 2.1 | 39 | QAM 256 | 3 |
5 | 163000000 | 2.1 | 39 | QAM 256 | 4 |
6 | 171000000 | 2.2 | 39 | QAM 256 | 5 |
7 | 179000000 | 2.4 | 39 | QAM 256 | 6 |
8 | 187000000 | 2.5 | 39 | QAM 256 | 7 |
9 | 195000000 | 2.6 | 39 | QAM 256 | 8 |
10 | 211000000 | 2.4 | 39 | QAM 256 | 10 |
11 | 219000000 | 2.5 | 39 | QAM 256 | 11 |
12 | 227000000 | 2.7 | 39 | QAM 256 | 12 |
13 | 235000000 | 2.6 | 39 | QAM 256 | 13 |
14 | 243000000 | 2.3 | 39 | QAM 256 | 14 |
15 | 251000000 | 2.1 | 39 | QAM 256 | 15 |
16 | 259000000 | 2.1 | 39 | QAM 256 | 16 |
17 | 267000000 | 2.1 | 39 | QAM 256 | 17 |
18 | 275000000 | 2 | 39 | QAM 256 | 18 |
19 | 283000000 | 1.8 | 39 | QAM 256 | 19 |
20 | 291000000 | 1.6 | 38 | QAM 256 | 20 |
21 | 299000000 | 1.4 | 39 | QAM 256 | 21 |
22 | 307000000 | 1.4 | 38 | QAM 256 | 22 |
23 | 315000000 | 1.6 | 39 | QAM 256 | 23 |
24 | 323000000 | 1.9 | 39 | QAM 256 | 24 |
25 | 331000000 | 2.2 | 39 | QAM 256 | 25 |
26 | 339000000 | 2.4 | 39 | QAM 256 | 26 |
27 | 347000000 | 2.3 | 39 | QAM 256 | 27 |
28 | 355000000 | 2.3 | 39 | QAM 256 | 28 |
29 | 363000000 | 2.5 | 39 | QAM 256 | 29 |
30 | 371000000 | 2.7 | 39 | QAM 256 | 30 |
31 | 379000000 | 2.7 | 39 | QAM 256 | 31 |
Downstream bonded channels
1 | Locked | 39 | 0 | 0 |
2 | Locked | 39 | 0 | 0 |
3 | Locked | 39 | 0 | 0 |
4 | Locked | 39 | 0 | 0 |
5 | Locked | 39 | 1 | 0 |
6 | Locked | 39 | 0 | 0 |
7 | Locked | 39 | 0 | 0 |
8 | Locked | 39 | 0 | 0 |
9 | Locked | 39 | 0 | 0 |
10 | Locked | 39 | 0 | 0 |
11 | Locked | 39 | 0 | 0 |
12 | Locked | 39 | 0 | 0 |
13 | Locked | 39 | 0 | 0 |
14 | Locked | 39 | 0 | 0 |
15 | Locked | 39 | 0 | 0 |
16 | Locked | 39 | 0 | 0 |
17 | Locked | 39 | 0 | 0 |
18 | Locked | 39 | 0 | 0 |
19 | Locked | 39 | 0 | 0 |
20 | Locked | 38 | 0 | 0 |
21 | Locked | 39 | 0 | 0 |
22 | Locked | 38 | 0 | 0 |
23 | Locked | 39 | 0 | 0 |
24 | Locked | 39 | 0 | 0 |
25 | Locked | 39 | 0 | 0 |
26 | Locked | 39 | 0 | 0 |
27 | Locked | 39 | 0 | 0 |
28 | Locked | 39 | 0 | 0 |
29 | Locked | 39 | 0 | 0 |
30 | Locked | 39 | 0 | 0 |
31 | Locked | 39 | 0 | 0 |
Upstream bonded channels
0 | 60300000 | 36.5 | 5120 | QAM 64 | 1 |
1 | 53700000 | 36.5 | 5120 | QAM 64 | 2 |
2 | 46200000 | 37 | 5120 | QAM 64 | 3 |
3 | 39400000 | 36.5 | 5120 | QAM 64 | 4 |
4 | 32600000 | 36.5 | 5120 | QAM 64 | 5 |
5 | 23600000 | 36 | 5120 | QAM 64 | 6 |
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 |
5 | ATDMA | 0 | 0 | 0 | 0 |
General Configuration
Allowed |
1 |
Enabled |
3.1 |
fg87dsfd;kfoA,.iyewrkldJK |
Primary Downstream Service Flow
5724 |
1200000450 bps |
42600bytes |
0 bps |
Primary Upstream Service Flow
5723 |
55000270 bps |
42600bytes |
0 bps |
16320bytes |
Best Effort |
Answered! Go to Answer
on 15-03-2023 17:48
Hi colonelblighty,
Thanks for coming back to us on this one.
We're glad all is OK with the connection itself. In terms of the 3db attenuator, as all your current signal levels are in the optimal range, we would advise leaving this there as otherwise it could cause intermittent issues.
If you have any further issues, pop back and let us know.
Many thanks,
on 11-03-2023 11:40
Network stats added as OP exceeded limit
Network Log
11-03-2023 11:06:46 | 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; |
11-03-2023 11:06:46 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-03-2023 10:55:43 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:37 | warning | Dynamic Range Window violation |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:37 | warning | Dynamic Range Window violation |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:37 | warning | Dynamic Range Window violation |
11-03-2023 10:55:37 | warning | Dynamic Range Window violation |
11-03-2023 10:55:37 | warning | Dynamic Range Window violation |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:37 | warning | Dynamic Range Window violation |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:37 | 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; |
11-03-2023 10:55:31 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 4.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-03-2023 10:55:28 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-03-2023 10:55:26 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-03-2023 10:55:24 | notice | Honoring MDD; IP provisioning mode = IPv4 |
11-03-2023 10:55:15 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-03-2023 10:54:58 | critical | Cable Modem Reboot due to power button reset |
10-03-2023 09:28: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; |
10-03-2023 09:28:30 | critical | Cable Modem Reboot via RG reboot command |
09-03-2023 22:39:42 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
03-03-2023 17:26:05 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
25-02-2023 09:07:25 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 18:41:45 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 11:22:25 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 11:10:53 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
22-02-2023 11:10:35 | critical | Cable Modem Reboot via RG reboot command |
07-02-2023 01:40:10 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1 |
11-03-2023 12:11 - edited 11-03-2023 12:12
Stats look good to me but the hub might be due a full reboot without the ethernet connection.
Also try disabling QOS on the Asus router.
on 11-03-2023 12:33
Thanks for the reply,
I had rebooted earlier before posting any stats disconnecting the ethernet cable when I did so. Tried turning off the QoS service and did a few tests and the top one and most recent in the table with it turned back on.
11-03-2023 13:05 - edited 11-03-2023 13:06
The plug will be due to you having fibre (Yellow cable) to the VM box outside which then needs to be converted to coax for the HUB and TV boxes, which requires power to the blue device seen below:
Have you tried a few of the sites available to your ASUS router?
I have the same router and find the suggested site is not always the fastest, even though the latency is better.
Depending on the time of day you may not always see the expected speeds.
on 11-03-2023 13:18
Aah makes sense now thanks.
I tried a few and they did vary from a poor 230 up to a 1030 I think I got so all in all not bad at all.
I've read some posts saying instead of the attenuator I should really have an equaliser instead but I don't really know what the difference is.
on 13-03-2023 15:31
Hi @colonelblighty,
Thank you for your posts and welcome to our community forums. We're here to help.
I'm sorry to hear you're not completely happy with your connection speeds. I've taken a look at your stats and speed test readings and I can't seem to see any issue detected there. Are you having any intermittent connection loss at all?
Thanks,
on 13-03-2023 15:34
Hi,
Nope all good thanks and based on the advice of other posters reckon if this is as good as it gets then I'm satisfied.
I would like to know if the 3db attenuator is required as when I first got the FTTP I was the first one in our area to get it and I remember them saying the signal was too strong but I don't know if this is still the case or not.
on 13-03-2023 16:34
@colonelblighty wrote:Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 60300000 36.5 5120 QAM 64 1 1 53700000 36.5 5120 QAM 64 2 2 46200000 37 5120 QAM 64 3 3 39400000 36.5 5120 QAM 64 4 4 32600000 36.5 5120 QAM 64 5 5 23600000 36 5120 QAM 64 6
Ooo 6 upstream channels😋
on 15-03-2023 17:48
Hi colonelblighty,
Thanks for coming back to us on this one.
We're glad all is OK with the connection itself. In terms of the 3db attenuator, as all your current signal levels are in the optimal range, we would advise leaving this there as otherwise it could cause intermittent issues.
If you have any further issues, pop back and let us know.
Many thanks,