on 07-06-2023 10:11
Hi, I bit the bullet and upgraded my fibre .. I received upgrade pack when going from m500 to gig1 and new hub5.
so far, I am only hitting around 800mbps DL and 45/50mbps UL .. and would be expecting more.
I am using hub in modem mode which connects to my unifi udm and associated AP’s around house.
Network logs are showing lots of warnings and the max traffic rate as 1200000450 bps
Could an insightful person take a look please as not the speeds I was expecting having come from a very good m500 service.
Answered! Go to Answer
on 07-06-2023 21:33
There is no "train up" period with VM, it works straight away. Have you got a UDM or a UDM-Pro? What is the firmware level of the UDM and also the level of the Network Application? I have a lot of experience with the UDM-Pro, currently on 3.0.20 and 7.4.156. Could you please supply some stats so we can check out your circuit.
How to get stats from a VM hub (no need to logon to the hub)
Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode
on 07-06-2023 10:50
Did you run the Speedtest from the UDM or from a device?
on 07-06-2023 11:19
Hello and thank you for responding.
I've run both speed tests over Wi-Fi and over eth and from UDM and device. Same issue.
does it take time to train up as only installed it yesterday afternoon but would have though it would be synched by now.
I've also reset the pin hole in hub, turned my router off and then brought back on line hub first (as modem) and then my UDM.
Thanks again!
on 07-06-2023 20:52
Anyone from virgin able to offer any advice etc? The ms all!
on 07-06-2023 21:33
There is no "train up" period with VM, it works straight away. Have you got a UDM or a UDM-Pro? What is the firmware level of the UDM and also the level of the Network Application? I have a lot of experience with the UDM-Pro, currently on 3.0.20 and 7.4.156. Could you please supply some stats so we can check out your circuit.
How to get stats from a VM hub (no need to logon to the hub)
Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode
on 07-06-2023 22:59
You need to do a speed test directly from the hub to rule out your own equipment/setup.
on 08-06-2023 12:47
Thanks Tudor,
I am using a standard UDM device (with multiple wired nanoAP's) with the latest official firmware @ 3.0.20.
Downstream bonded channels
1 | 306000000 | 5.3 | 40 | QAM 256 | 22 |
2 | 138000000 | 5.8 | 38 | QAM 256 | 1 |
3 | 146000000 | 5.6 | 38 | QAM 256 | 2 |
4 | 154000000 | 5.3 | 38 | QAM 256 | 3 |
5 | 162000000 | 5.1 | 38 | QAM 256 | 4 |
6 | 170000000 | 5 | 38 | QAM 256 | 5 |
7 | 178000000 | 5 | 38 | QAM 256 | 6 |
8 | 186000000 | 5.1 | 39 | QAM 256 | 7 |
9 | 194000000 | 5.3 | 39 | QAM 256 | 8 |
10 | 202000000 | 5.2 | 39 | QAM 256 | 9 |
11 | 210000000 | 5.3 | 39 | QAM 256 | 10 |
12 | 218000000 | 5.3 | 39 | QAM 256 | 11 |
13 | 226000000 | 5.2 | 39 | QAM 256 | 12 |
14 | 234000000 | 5 | 39 | QAM 256 | 13 |
15 | 242000000 | 4.7 | 39 | QAM 256 | 14 |
16 | 250000000 | 4.4 | 39 | QAM 256 | 15 |
17 | 258000000 | 4.8 | 40 | QAM 256 | 16 |
18 | 266000000 | 5.3 | 40 | QAM 256 | 17 |
19 | 274000000 | 5.3 | 40 | QAM 256 | 18 |
20 | 282000000 | 5.2 | 40 | QAM 256 | 19 |
21 | 290000000 | 5.3 | 40 | QAM 256 | 20 |
22 | 298000000 | 5.3 | 40 | QAM 256 | 21 |
23 | 314000000 | 5.1 | 40 | QAM 256 | 23 |
24 | 322000000 | 4.8 | 40 | QAM 256 | 24 |
25 | 330000000 | 4.5 | 40 | QAM 256 | 25 |
26 | 338000000 | 4.4 | 39 | QAM 256 | 26 |
27 | 346000000 | 4.6 | 40 | QAM 256 | 27 |
28 | 354000000 | 4.7 | 40 | QAM 256 | 28 |
29 | 362000000 | 4.9 | 40 | QAM 256 | 29 |
30 | 370000000 | 4.8 | 40 | QAM 256 | 30 |
31 | 378000000 | 4.6 | 40 | QAM 256 | 31 |
Upstream bonded channels
0 | 53700000 | 42 | 5120 | QAM 64 | 5 |
1 | 46200000 | 41.8 | 5120 | QAM 64 | 6 |
2 | 39400000 | 42.3 | 5120 | QAM 64 | 7 |
3 | 32600000 | 41.5 | 5120 | QAM 64 | 8 |
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 |
Network Log
08-06-2023 14:21:49 | 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; |
08-06-2023 14:21:49 | warning | Dynamic Range Window violation |
08-06-2023 14:16:29 | warning | Dynamic Range Window violation |
08-06-2023 14:16:29 | 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; |
08-06-2023 13:41:13 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
08-06-2023 13:41:07 | 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; |
08-06-2023 13:41:02 | 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; |
08-06-2023 13:40:58 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-06-2023 13:40:56 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-06-2023 13:40:54 | notice | Honoring MDD; IP provisioning mode = IPv4 |
08-06-2023 13:40:45 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-06-2023 13:40:29 | critical | Cable Modem Reboot due to power button reset |
08-06-2023 12:05:25 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-06-2023 12:05:09 | critical | Cable Modem Reboot due to power button reset |
06-06-2023 18:36:06 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
06-06-2023 18:35:48 | critical | Cable Modem Reboot via RG reboot command |
06-06-2023 18:30: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; |
06-06-2023 18:30:41 | critical | Cable Modem Reboot via RG reboot command |
06-06-2023 18:28:05 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
06-06-2023 18:28:00 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
06-06-2023 18:27:48 | critical | Cable Modem reset to Factory Default via reset button |
Thanks in advance, appreciated.
on 08-06-2023 12:50
Thanks for the info, I have tested all the equipment router side (i.e. my equipment) and all is well. I expected such as was always seeing the 500+mbps that I was expecting previously on my last service with virgin. All I have done is upgrade to the GiG1 service, replaced the hub (and placed again in modem mode) so would expect it to be the same but faster. Alas, it is not.
on 08-06-2023 13:01
also, app version is 7.4.156 .. sorry I missed that part of question 🙂
on 08-06-2023 14:13
Further thoughts. You only seem to have 4 upstream channels when you should have 6 (only 5 will show as there is a bug in the hub’s firmware that omits displaying the DOCSIS 3.1 channels). So looks like two upstreams are probably missing.
Have you got DPI turned on? You could try an SSH connection to the UDM and take a look in /var/logs and see if anything is obvious and also run ‘journalctl’ from that session.