on 18-03-2023 22:11
Interner was fine and has been since isstalation of hub
But the last two days it keeps saying that the hub isnt connected properly.. Nothing has moved or been changed or tampered with.
I switched itnoff last night til. This morning and it was fine all day until now again 10pm
There seems to be no issues int he area etc
on 18-03-2023 22:33
on 18-03-2023 22:51
Please don’t post photos as they are difficult to read..
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 19-03-2023 08:58
Ty for advice
Downsream
1 | 330000000 | 3.1 | 42 | QAM 256 | 25 |
2 | 210000000 | 4 | 41 | QAM 256 | 10 |
3 | 218000000 | 3.4 | 42 | QAM 256 | 11 |
4 | 226000000 | 3.2 | 41 | QAM 256 | 12 |
5 | 234000000 | 3.7 | 42 | QAM 256 | 13 |
6 | 242000000 | 3.6 | 42 | QAM 256 | 14 |
7 | 250000000 | 2.6 | 42 | QAM 256 | 15 |
8 | 258000000 | 3.2 | 42 | QAM 256 | 16 |
9 | 266000000 | 3.6 | 42 | QAM 256 | 17 |
10 | 274000000 | 2.4 | 41 | QAM 256 | 18 |
11 | 282000000 | 3 | 42 | QAM 256 | 19 |
12 | 290000000 | 3.3 | 42 | QAM 256 | 20 |
13 | 298000000 | 3.4 | 42 | QAM 256 | 21 |
14 | 306000000 | 2.7 | 42 | QAM 256 | 22 |
15 | 314000000 | 3.9 | 42 | QAM 256 | 23 |
16 | 322000000 | 3.1 | 42 | QAM 256 | 24 |
17 | 338000000 | 3.7 | 41 | QAM 256 | 26 |
18 | 346000000 | 3.7 | 42 | QAM 256 | 27 |
19 | 354000000 | 1.9 | 42 | QAM 256 | 28 |
20 | 362000000 | 3.1 | 42 | QAM 256 | 29 |
21 | 370000000 | 3 | 42 | QAM 256 | 30 |
22 | 378000000 | 2.7 | 42 | QAM 256 | 31 |
23 | 386000000 | 2.8 | 42 | QAM 256 | 32 |
24 | 394000000 | 3.3 | 42 | QAM 256 | 33 |
25 | 402000000 | 2.9 | 42 | QAM 256 | 34 |
26 | 410000000 | 2.7 | 42 | QAM 256 | 35 |
27 | 418000000 | 2.7 | 42 | QAM 256 | 36 |
28 | 522000000 | 1.1 | 42 | QAM 256 | 37 |
29 | 530000000 | 1.8 | 42 | QAM 256 | 38 |
30 | 538000000 | 1.7 | 42 | QAM 256 | 39 |
31 | 546000000 | 2 | 42 | QAM 256 | 40 |
Downstream bonded channels
1 | Locked | 42 | 5 | 0 |
2 | Locked | 41 | 112 | 0 |
3 | Locked | 42 | 80 | 0 |
4 | Locked | 41 | 51 | 0 |
5 | Locked | 42 | 37 | 0 |
6 | Locked | 42 | 27 | 0 |
7 | Locked | 42 | 35 | 0 |
8 | Locked | 42 | 29 | 0 |
9 | Locked | 42 | 18 | 0 |
10 | Locked | 41 | 19 | 0 |
11 | Locked | 42 | 18 | 0 |
12 | Locked | 42 | 15 | 0 |
13 | Locked | 42 | 11 | 0 |
14 | Locked | 42 | 12 | 0 |
15 | Locked | 42 | 8 | 0 |
16 | Locked | 42 | 7 | 0 |
17 | Locked | 41 | 6 | 0 |
18 | Locked | 42 | 7 | 0 |
19 | Locked | 42 | 10 | 0 |
20 | Locked | 42 | 6 | 0 |
21 | Locked | 42 | 6 | 0 |
22 | Locked | 42 | 8 | 0 |
23 | Locked | 42 | 4 | 0 |
24 | Locked | 42 | 4 | 0 |
25 | Locked | 42 | 1 | 0 |
26 | Locked | 42 | 2 | 0 |
27 | Locked | 42 | 4 | 0 |
28 | Locked | 42 | 0 | 0 |
29 | Locked | 42 | 1 | 0 |
30 | Locked | 42 | 1 | 0 |
31 | Locked | 42 | 0 | 0 |
Upstream bonded channels
0 | 46200000 | 49.3 | 5120 | QAM 64 | 1 |
1 | 39400000 | 49.5 | 5120 | QAM 64 | 2 |
2 | 32600000 | 47.8 | 5120 | QAM 64 | 3 |
3 | 25800000 | 47.3 | 5120 | QAM 64 | 4 |
4 | 53700000 | 49.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 |
Network Log
19-03-2023 05:40:12 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
19-03-2023 05:40:05 | 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; |
19-03-2023 05:39:53 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-03-2023 05:39:50 | notice | Honoring MDD; IP provisioning mode = IPv4 |
19-03-2023 05:39:43 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-03-2023 05:39:32 | critical | Cable Modem Reboot via RG reboot command |
18-03-2023 22:02:30 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-03-2023 22:02:01 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-03-2023 22:01:56 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-03-2023 22:01: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; |
18-03-2023 21:58:36 | critical | DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-03-2023 21:58:26 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-03-2023 21:58:15 | critical | Cable Modem Reboot due to power button reset |
18-03-2023 11:53:43 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-03-2023 11:53:31 | critical | Cable Modem Reboot via RG reboot command |
17-03-2023 21:31:36 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:31:02 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:30:48 | 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; |
17-03-2023 21:30:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:30:41 | 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; |
17-03-2023 21:30:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:30:37 | 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; |
17-03-2023 21:30:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:30:31 | 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; |
17-03-2023 21:26:37 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:26:36 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:26:36 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:24:41 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:08:21 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:05:59 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 21:00:20 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
17-03-2023 20:59:46 | 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; |
on 19-03-2023 09:04
Believe i have done this correctly now
on 21-03-2023 11:15
Hi there @Cwilson1985
Thank you so much for your post and welcome back to the forums, it's great to have you here.
I am so sorry to hear that you have faced these issues with your service, I have taken a look on our side and I cannot see anything that could be causing this issues.
Can I ask how things are looking since your last post?
on 21-03-2023 11:17
I had the same issue yesterday had to switch off for a few hours, and its been working since, but no saying its not going to be fine forever