on 10-06-2024 10:32
Hi, recently my hub has been unstable, constantly requiring me to do a reset, I use it in Modem mode and still I keep loosing connection needing to reboot. I have noticed that the status light has turned to a solid red since these issues have been present.
Any help would be appreciated.
Thanks
on 10-06-2024 11:14
Are you sure it’s red? Hub3 in modem mode the LED is magenta and can look red to a lot of people. Please post some 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 10-06-2024 12:19
Hello craigchaos88
Sorry to hear of the red light and connection issues in regards to your Hub, we appreciate you taking the time to raise this via the forums.
When using the Hub in modem mode it should show the base light as a magenta colour, due to it currently being in modem mode we're limited as to what we can see in regards to the Hub and it's stats but what we can see, all of the levels and specs are in the ranges we'd expect them to be.
Please can you try this for me:
• Turn the power switch off on the back of the Hub.
• Ensure the Hub is upright, in a well-ventilated location and out of direct sunlight, if possible.
• Switch the hub back on at the power. The Hub should now operate normally.
Please report back with the result.
Rob
on 20-06-2024 23:31
Hi Tudor,
Please see the info you requested below:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 3.5 | 40 | 256 qam | 25 |
2 | 139000000 | 5.1 | 40 | 256 qam | 1 |
3 | 163000000 | 5 | 40 | 256 qam | 4 |
4 | 171000000 | 4.5 | 40 | 256 qam | 5 |
5 | 195000000 | 4.9 | 40 | 256 qam | 8 |
6 | 203000000 | 4.3 | 40 | 256 qam | 9 |
7 | 227000000 | 4 | 40 | 256 qam | 12 |
8 | 235000000 | 4 | 40 | 256 qam | 13 |
9 | 259000000 | 3.5 | 40 | 256 qam | 16 |
10 | 267000000 | 3.7 | 40 | 256 qam | 17 |
11 | 291000000 | 3 | 40 | 256 qam | 20 |
12 | 299000000 | 3.4 | 40 | 256 qam | 21 |
13 | 323000000 | 3.2 | 40 | 256 qam | 24 |
14 | 339000000 | 3.5 | 40 | 256 qam | 26 |
15 | 347000000 | 4 | 40 | 256 qam | 27 |
16 | 355000000 | 4 | 40 | 256 qam | 28 |
17 | 363000000 | 4.5 | 40 | 256 qam | 29 |
18 | 371000000 | 4 | 40 | 256 qam | 30 |
19 | 379000000 | 4.4 | 40 | 256 qam | 31 |
20 | 387000000 | 3.9 | 40 | 256 qam | 32 |
21 | 395000000 | 4.3 | 40 | 256 qam | 33 |
22 | 403000000 | 4 | 40 | 256 qam | 34 |
23 | 411000000 | 3.5 | 40 | 256 qam | 35 |
24 | 419000000 | 4.1 | 40 | 256 qam | 36 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 5868 | 2111 |
2 | Locked | 40.3 | 239369136 | 37338 |
3 | Locked | 40.3 | 41928823 | 460424 |
4 | Locked | 40.3 | 11703856 | 7564 |
5 | Locked | 40.9 | 14993309 | 373005 |
6 | Locked | 40.3 | 10507418 | 113657 |
7 | Locked | 40.3 | 23225 | 4516 |
8 | Locked | 40.9 | 8672 | 3504 |
9 | Locked | 40.3 | 5563 | 2741 |
10 | Locked | 40.9 | 4305 | 2232 |
11 | Locked | 40.9 | 223677 | 4989 |
12 | Locked | 40.3 | 29313 | 5271 |
13 | Locked | 40.3 | 5681 | 2831 |
14 | Locked | 40.3 | 43034 | 2842 |
15 | Locked | 40.3 | 7163600 | 171401 |
16 | Locked | 40.3 | 15782331 | 853715 |
17 | Locked | 40.9 | 69483 | 3783 |
18 | Locked | 40.3 | 4263 | 3635 |
19 | Locked | 40.9 | 2440 | 3714 |
20 | Locked | 40.3 | 4033 | 2732 |
21 | Locked | 40.9 | 9053 | 2608 |
22 | Locked | 40.3 | 5897 | 2670 |
23 | Locked | 40.3 | 2343 | 3391 |
24 | Locked | 40.3 | 2010 | 3033 |
1 | 43100000 | 44 | 5120 | 64 qam | 2 |
2 | 23600000 | 42 | 5120 | 64 qam | 5 |
3 | 30100000 | 43 | 5120 | 64 qam | 4 |
4 | 36600000 | 43.5 | 5120 | 64 qam | 3 |
5 | 49600000 | 44.5 | 5120 | 64 qam | 1 |
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 3 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
5 | ATDMA | 0 | 0 | 3 | 0 |
on 20-06-2024 23:31
And also:
Time Priority Description
20/06/2024 22:21:52 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 22:21:42 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 20:49:53 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 20:49:53 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 18:52:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 06:10:0 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 03:12:30 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 03:12:30 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/06/2024 03:12:30 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/06/2024 21:57:31 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2024 22:07:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2024 08:49:54 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2024 08:49:54 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/06/2024 23:24:5 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/06/2024 23:24:4 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2024 13:55:4 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2024 06:25:27 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2024 06:25:27 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2024 21:17:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2024 20:49:53 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 23-06-2024 09:16
Hi craigchaos88,
Thanks for providing that information. So we can continue to support you, can you let us know how things were after you followed the instructions in Rob's post above?
Once we know the results, we can then look to help further 😊
Thanks,
on 28-06-2024 21:40
Hi, sorry for the late reply. The issue is still present and getting worse. I have my router in modem mode and have reset the WiFi router which I have connected also. I have read on other posts on this forum that the red light indicates that there is an internal fault with the hub. It is free from obstruction and is well ventilated. I am worried this may cause a fire as the other posts have suggested its an overheating issue.
28-06-2024 21:44 - edited 28-06-2024 21:44
setup a BQM
Broadband Quality Monitor | thinkbroadband
on 29-06-2024 13:48
… and before the Forum Team ask you to put your Hub into router mode (which will be a complete waste of everybody’s time), the Red light is a matter entirely local to the Hub itself and its guts.
Is the Hub warmer/hotter than you would think to be normal? If so, I recommend you don’t leave it on unattended.
on 01-07-2024 14:28
Hi @craigchaos88, thank you for your response.
In order to look into this for you further, we'll send you a private message on here. Look out for the envelope in the top right-hand corner.
If you're on a portable device with a smaller screen, click on the icon in the top right-hand corner and select "messages" from the additional menu options.
Regards,
Daniel