12-07-2021 17:49 - edited 12-07-2021 18:19
We have had a solid red light on our Hub 3 for the past 6 days.
No area faults identified.
Several pinhole resets done.
Hub not overheating but turned off for 45 minutes and restarted as cold. Hub has plenty of ventilation.
No issue with internet speed. 5ghz signal is consistent, 2.4ghz signal drops out a few times a days.
Turned off 2.4ghz signal and restarted. Turned into modem mode and restarted.
Checked all cabling.
Spoken to a Faults Advisor for 45 minutes on the phone, various checks and reboots done. Still solid red light and advised nothing more to be done, monitor for 24 hours.
Any help as to the cause and fix of the red light would be much appreciated.
Answered! Go to Answer
on 12-07-2021 20:01
Thanks for your reply mazj_uk. I've booked a visit from an engineer - you will find confirmation via your online account (virg.in/myVM) and can reschedule from there if needed.
Please keep us posted with how the visit goes, or let us know if we can help with anything else.
Tom
on 12-07-2021 18:41
Here's my Hub data:
Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz)
331000000
Locked
Ranged Upstream Channel (Hz)
32600000
Locked
Provisioning State
Online
on 12-07-2021 18:42
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 0 | 40 | 256 qam | 25 |
2 | 203000000 | 1 | 40 | 256 qam | 9 |
3 | 211000000 | 1 | 40 | 256 qam | 10 |
4 | 219000000 | 0.9 | 40 | 256 qam | 11 |
5 | 227000000 | 0.5 | 40 | 256 qam | 12 |
6 | 235000000 | 0.2 | 40 | 256 qam | 13 |
7 | 243000000 | 0 | 40 | 256 qam | 14 |
8 | 251000000 | 0 | 40 | 256 qam | 15 |
9 | 259000000 | 0 | 40 | 256 qam | 16 |
10 | 267000000 | 0 | 40 | 256 qam | 17 |
11 | 275000000 | 0 | 40 | 256 qam | 18 |
12 | 283000000 | 0 | 40 | 256 qam | 19 |
13 | 291000000 | 0 | 38 | 256 qam | 20 |
14 | 299000000 | 0.2 | 38 | 256 qam | 21 |
15 | 307000000 | 0 | 40 | 256 qam | 22 |
16 | 315000000 | 0 | 40 | 256 qam | 23 |
17 | 323000000 | -0.2 | 38 | 256 qam | 24 |
18 | 371000000 | 0 | 40 | 256 qam | 26 |
19 | 379000000 | 0 | 38 | 256 qam | 27 |
20 | 387000000 | 0 | 40 | 256 qam | 28 |
21 | 395000000 | -0.2 | 40 | 256 qam | 29 |
22 | 403000000 | -0.2 | 38 | 256 qam | 30 |
23 | 411000000 | -0.4 | 38 | 256 qam | 31 |
24 | 419000000 | -0.2 | 38 | 256 qam | 32 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 368 | 0 |
2 | Locked | 40.3 | 18 | 0 |
3 | Locked | 40.9 | 23 | 0 |
4 | Locked | 40.3 | 23 | 0 |
5 | Locked | 40.3 | 29 | 0 |
6 | Locked | 40.3 | 46 | 0 |
7 | Locked | 40.9 | 44 | 0 |
8 | Locked | 40.3 | 47 | 0 |
9 | Locked | 40.3 | 51 | 0 |
10 | Locked | 40.3 | 69 | 0 |
11 | Locked | 40.3 | 104 | 0 |
12 | Locked | 40.3 | 118 | 0 |
13 | Locked | 38.9 | 175 | 0 |
14 | Locked | 38.9 | 190 | 0 |
15 | Locked | 40.3 | 211 | 0 |
16 | Locked | 40.3 | 303 | 0 |
17 | Locked | 38.9 | 355 | 0 |
18 | Locked | 40.3 | 850 | 0 |
19 | Locked | 38.9 | 992 | 0 |
20 | Locked | 40.3 | 1117 | 0 |
21 | Locked | 40.9 | 1174 | 0 |
22 | Locked | 38.9 | 1565 | 0 |
23 | Locked | 38.9 | 1734 | 0 |
24 | Locked | 38.6 | 1928 | 0 |
on 12-07-2021 18:43
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 42.8 | 5120 | 64 qam | 5 |
2 | 53700000 | 43.8 | 5120 | 64 qam | 2 |
3 | 46200005 | 43.5 | 5120 | 16 qam | 3 |
4 | 39400000 | 42.8 | 5120 | 32 qam | 4 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 12-07-2021 18:44
General Configuration
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | cmreg-vmdg505-bbt057-b.cm |
Primary Downstream Service Flow
SFID | 1283580 |
Max Traffic Rate | 117000047 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 1283579 |
Max Traffic Rate | 10500047 |
Max Traffic Burst | 16320 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
on 12-07-2021 18:46
Network Log
12/07/2021 17:30:28 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/07/2021 00:23:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/07/2021 21:37:16 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/07/2021 12:01:47 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/07/2021 08:51:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/07/2021 15:14:10 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/07/2021 21:37:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/07/2021 16:16:6 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/07/2021 16:15:1 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/07/2021 17:52:53 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/07/2021 08:04:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/07/2021 02:12:8 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/07/2021 01:51:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 12-07-2021 18:50
Hi @mazj_uk,
Welcome to our community forums and thank you for your first posts.
Sorry to hear you are having issues with the red light on your hub. We can understand you concern and want to do our best to help.
How long has this light issue been ongoing? Are you experiencing other issues with your Hub? Does this affect you use of broadband or WIFI?
Thanks,
on 12-07-2021 18:51
Irrespective of the hub data, if the hub is displaying a red power light & is not being used in modem mode then the issue needs to be resolved for safety reasons. False positive indications are dangerous as they can mask a real overheat fault, which is a fire risk.
I will escalate this thread for a priority response.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
12-07-2021 19:18 - edited 12-07-2021 19:25
As per above the light has been solid red for 6 days, we have no issue with our speed. 5ghz signal is fine, 2.4ghz signal drops a couple of times a day.
on 12-07-2021 19:31
Thanks for flagging this nodrogd.
So we can help further I will contact you via Private Message mazj_uk - just look out for the purple envelope and we'll take it from there.
Tom