on 06-12-2022 21:35
Hello,
I'm getting terrible ping spikes and multiple errors in the log. I've tried splitting the 2.4GHz and 5GHz but not much has changed. The 3.0 hub seems also to have very low range since I get only about 20 Mbps on my first floor and the router is on the ground floor.
Does anybody have any idea? Is this a Virgin Media issue that I need to contact an engineer? Please help. Thanks
These are the errors I'm seeing:
06/12/2022 21:19:31 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 21:17:7 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 20:37:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 20:35:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 17:50:32 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 16:33:54 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 11:47:0 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 06-12-2022 22:32
Please post a full set of stats, you do not have to logon to the hub to get the stats:
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-12-2022 16:44
Hi,
Thanks for your help Tudor.
Here's the data, downstream:
1 | 507000000 | 10.9 | 39 | 256 qam | 13 |
2 | 515000000 | 11.5 | 40 | 256 qam | 14 |
3 | 523000000 | 12 | 40 | 256 qam | 15 |
4 | 531000000 | 12 | 40 | 256 qam | 16 |
5 | 539000000 | 11.3 | 40 | 256 qam | 17 |
6 | 547000000 | 10.5 | 38 | 256 qam | 18 |
7 | 555000000 | 10.4 | 38 | 256 qam | 19 |
8 | 563000000 | 11 | 38 | 256 qam | 20 |
9 | 571000000 | 11.8 | 40 | 256 qam | 21 |
10 | 579000000 | 12 | 40 | 256 qam | 22 |
11 | 587000000 | 11.6 | 40 | 256 qam | 23 |
12 | 595000000 | 11.3 | 40 | 256 qam | 24 |
13 | 603000000 | 11 | 38 | 256 qam | 25 |
14 | 611000000 | 11.4 | 38 | 256 qam | 26 |
15 | 619000000 | 11.6 | 40 | 256 qam | 27 |
16 | 627000000 | 11.6 | 38 | 256 qam | 28 |
17 | 635000000 | 11.4 | 38 | 256 qam | 29 |
18 | 643000000 | 11.1 | 40 | 256 qam | 30 |
19 | 651000000 | 11 | 38 | 256 qam | 31 |
20 | 659000000 | 11.3 | 40 | 256 qam | 32 |
21 | 667000000 | 11.6 | 40 | 256 qam | 33 |
22 | 675000000 | 11.9 | 38 | 256 qam | 34 |
23 | 683000000 | 11.3 | 38 | 256 qam | 35 |
24 | 691000000 | 10.8 | 40 | 256 qam | 36 |
on 07-12-2022 16:45
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 39.8 | 1557 | 1311 |
2 | Locked | 40.3 | 1545 | 1778 |
3 | Locked | 40.3 | 956 | 1556 |
4 | Locked | 40.9 | 612 | 835 |
5 | Locked | 40.3 | 897 | 188 |
6 | Locked | 38.9 | 1115 | 432 |
7 | Locked | 38.9 | 1383 | 972 |
8 | Locked | 38.9 | 1348 | 1862 |
9 | Locked | 40.3 | 948 | 1909 |
10 | Locked | 40.3 | 621 | 918 |
11 | Locked | 40.3 | 675 | 273 |
12 | Locked | 40.3 | 818 | 597 |
13 | Locked | 38.9 | 1127 | 1163 |
14 | Locked | 38.9 | 1133 | 1782 |
15 | Locked | 40.3 | 821 | 1615 |
16 | Locked | 38.9 | 481 | 851 |
17 | Locked | 38.9 | 629 | 123 |
18 | Locked | 40.3 | 720 | 445 |
19 | Locked | 38.9 | 811 | 1115 |
20 | Locked | 40.3 | 823 | 1520 |
21 | Locked | 40.3 | 549 | 1331 |
22 | Locked | 38.9 | 416 | 521 |
23 | Locked | 38.9 | 554 | 188 |
24 | Locked | 40.3 | 689 | 450 |
on 07-12-2022 16:45
1 | 23599783 | 44 | 5120 | 64 qam | 9 |
2 | 43099970 | 41.5 | 5120 | 64 qam | 2 |
3 | 36600112 | 43.8 | 5120 | 64 qam | 3 |
4 | 49599965 | 41.5 | 5120 | 64 qam | 1 |
5 | 30099995 | 44 | 5120 | 64 qam | 4 |
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
07/12/2022 16:36:57 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/12/2022 15:37:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/12/2022 12:56:29 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/12/2022 11:58:58 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/12/2022 05:58:28 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 21:19:31 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 21:17:7 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 20:37:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 20:35:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 17:50:32 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 16:33:54 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 11:47:0 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 11:46:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 11:43:47 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 07:57:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/12/2022 06:23:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/12/2022 17:37:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/12/2022 18:21:34 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/12/2022 13:33:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 07-12-2022 16:46
I should also mention that I've contacted VM in the mean time and they've arranged an engineer to visit on Monday saying that my 3.0 Hub seems to have an issue. Not sure if that's really true to be honest...
I have also set up the monitor since last night:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/57583fe9ade27bae9db09cd3d33c16c6ae...
Thanks
on 09-12-2022 17:02
Hey SaymonVoid, thanks for reaching out on our help forum about the issues faced with your services.
A warm welcome from us in the community, we'd love to best help with this.
Since you've stated that you spoke with our staff over a call and we've arranged a tech visit to replace the hub, this means the findings when we checked indicated an issue with your equipment.
As your appointment is on Monday next week, could you please get back to us with your update here after this visit so we know it's sorted?
Also happy to assist in case you're still having issues with the service after our engineer has left the property, just pop us a message and let us know.
on 12-12-2022 16:53
Hi,
the engineer came around today and he mentioned something about power levels being too high and that my unit was overloaded because I'm very close to the cabinet. He added a piece and replaced the Hub with a new 3.0. So far so good, I've only been testing briefly throughout the day but the signal is much better now.
Thanks
on 12-12-2022 21:12
Hi,
Unfortunately the issue persists with very high latency spikes while gaming. I feel like at this point it may be something to do with the cabinet, the engineer did mention that the situation was quite messy in there. I'll try contacting him again.
Here's the new broadband monitor:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/5f961c4efb428d3ec4bff745b370c4c272...
on 12-12-2022 21:17