on 21-06-2022 20:13
I have had a hub 3 for a couple of years now but the last few weeks it has taken to resetting itself. Here are the details I can think of. I have made no changes or done anything to cause the issue.
Can someone please help me? It is incredibly frustrating and no one at Virgin seems to care.
Answered! Go to Answer
on 23-06-2022 13:49
on 22-06-2022 15:06
on 22-06-2022 15:30
Hi John,
Thanks for your help. I have joined think broadband as you suggested and here are the details when I check my router status.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 203000000 | 5.3 | 40 | 256 qam | 9 |
2 | 211000000 | 5.1 | 40 | 256 qam | 10 |
3 | 219000000 | 4.5 | 40 | 256 qam | 11 |
4 | 227000000 | 3.7 | 38 | 256 qam | 12 |
5 | 235000000 | 3.2 | 40 | 256 qam | 13 |
6 | 243000000 | 3.7 | 40 | 256 qam | 14 |
7 | 251000000 | 3.9 | 40 | 256 qam | 15 |
8 | 259000000 | 4 | 40 | 256 qam | 16 |
9 | 267000000 | 4.1 | 40 | 256 qam | 17 |
10 | 275000000 | 4 | 40 | 256 qam | 18 |
11 | 283000000 | 4.4 | 40 | 256 qam | 19 |
12 | 291000000 | 4.4 | 40 | 256 qam | 20 |
13 | 299000000 | 4.4 | 40 | 256 qam | 21 |
14 | 307000000 | 4.4 | 40 | 256 qam | 22 |
15 | 315000000 | 4.3 | 40 | 256 qam | 23 |
16 | 323000000 | 4.1 | 40 | 256 qam | 24 |
17 | 331000000 | 4 | 40 | 256 qam | 25 |
18 | 339000000 | 4 | 40 | 256 qam | 26 |
19 | 347000000 | 3.7 | 40 | 256 qam | 27 |
20 | 355000000 | 3.7 | 40 | 256 qam | 28 |
21 | 363000000 | 3.2 | 40 | 256 qam | 29 |
22 | 371000000 | 3 | 38 | 256 qam | 30 |
23 | 379000000 | 2.4 | 38 | 256 qam | 31 |
24 | 387000000 | 2 | 40 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 289637 | 142248 |
2 | Locked | 40.3 | 281073 | 120689 |
3 | Locked | 40.3 | 276728 | 117455 |
4 | Locked | 38.9 | 279357 | 133894 |
5 | Locked | 40.3 | 277990 | 120478 |
6 | Locked | 40.9 | 261322 | 88030 |
7 | Locked | 40.9 | 249470 | 71905 |
8 | Locked | 40.3 | 239974 | 62328 |
9 | Locked | 40.9 | 229439 | 56283 |
10 | Locked | 40.3 | 228086 | 54942 |
11 | Locked | 40.9 | 212055 | 42949 |
12 | Locked | 40.3 | 201564 | 36083 |
13 | Locked | 40.3 | 190988 | 31958 |
14 | Locked | 40.3 | 178600 | 27880 |
15 | Locked | 40.3 | 174739 | 27894 |
16 | Locked | 40.3 | 169833 | 27009 |
17 | Locked | 40.3 | 153054 | 21698 |
18 | Locked | 40.3 | 140942 | 18118 |
19 | Locked | 40.3 | 137676 | 17529 |
20 | Locked | 40.3 | 136788 | 16203 |
21 | Locked | 40.3 | 129604 | 15693 |
22 | Locked | 38.9 | 123182 | 14231 |
23 | Locked | 38.9 | 113091 | 13662 |
24 | Locked | 40.3 | 104249 | 11933 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 47.5 | 5120 | 64 qam | 4 |
2 | 46200000 | 48.3 | 5120 | 64 qam | 3 |
3 | 25800000 | 46.3 | 5120 | 64 qam | 6 |
4 | 32600000 | 47 | 5120 | 64 qam | 5 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
on 22-06-2022 15:31
Time Priority Description
22/06/2022 14:23:9 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:28:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:07:32 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:06:59 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:06:46 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:06:26 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:01:49 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 11:01:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 09:36:18 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 08:49:45 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 08:49:27 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 08:49:10 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:55:15 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:42:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:42:36 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:19:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:17:36 | 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.0; |
22/06/2022 07:11:21 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:09:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2022 07:08:7 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 22-06-2022 15:56
on 23-06-2022 07:24
Thanks John. I did as requested by turning it off for 5 minutes an checked the cables but it didn't work. Here is my monitor too. I guess red is bad
on 23-06-2022 10:56
No red means you have no connection, which is not the case. You need to go into the settings of the hub and turn on Accept ICMP messages. This is what TB uses.
on 23-06-2022 11:02
Thanks Tudor. I have gone into the hub settings and looked through the menus and can’t find reference to ICMP messages to accept them. Could you provide some direction here?
on 23-06-2022 13:49
on 29-06-2022 15:18
Resolved
Thanks everyone for your help in understanding what what happening.
It took 14 phone calls to Virgin for them to finally send an engineer and the cause was corroded wiring to my house. The engineer was great and fixed everything quickly and no more dropouts.
Sad that it took 14 calls to get someone out though.