on 03-03-2024 11:34
Hi Experts,
I'm on Hub 3. Experiencing terrible wifi stability which disappears almost twice a day and comes back up once restarted The technician who visited couldn't resolve with usual cable check, replace with another Hub 3 splitter check etc. Here are the logs: - any solutions or advice ?
Answered! Go to Answer
on 05-03-2024 20:00
There is a hardware fault with the HUB, so putting it in modem mode probably won't resolve the issue.
on 03-03-2024 11:36
BCM Link - <a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/810eb2541e547af7fe1d3758ecb6f38ec3..."><img alt="My Broadband Ping - HN" src="https://www.thinkbroadband.com/broadband/monitoring/quality/share/810eb2541e547af7fe1d3758ecb6f38ec3..." /></a>
on 03-03-2024 11:37
Time Priority Description
03/03/2024 11:01:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/03/2024 08:51:15 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/03/2024 03:57:8 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/03/2024 03:57:8 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2024 10:06:36 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/03/2024 21:20:36 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/03/2024 06:24:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/02/2024 21:14:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/02/2024 01:25:42 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/02/2024 01:25:42 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/02/2024 20:44:46 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2024 11:07:37 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2024 11:07:7 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2024 10:26:48 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2024 09:23:4 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2024 09:00:8 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/02/2024 01:18:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2024 17:28:32 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2024 17:28:32 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2024 16:28:32 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 03-03-2024 11:37
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 5 | 37 | 256 qam | 25 |
2 | 139000000 | 8 | 37 | 256 qam | 1 |
3 | 147000000 | 7.1 | 37 | 256 qam | 2 |
4 | 155000000 | 6.5 | 37 | 256 qam | 3 |
5 | 163000000 | 6 | 37 | 256 qam | 4 |
6 | 171000000 | 6 | 37 | 256 qam | 5 |
7 | 179000000 | 5.9 | 37 | 256 qam | 6 |
8 | 187000000 | 5.8 | 37 | 256 qam | 7 |
9 | 195000000 | 5.5 | 37 | 256 qam | 8 |
10 | 203000000 | 5 | 37 | 256 qam | 9 |
11 | 211000000 | 4.6 | 37 | 256 qam | 10 |
12 | 219000000 | 4.5 | 37 | 256 qam | 11 |
13 | 227000000 | 3.9 | 37 | 256 qam | 12 |
14 | 235000000 | 3.7 | 37 | 256 qam | 13 |
15 | 259000000 | 2.5 | 37 | 256 qam | 16 |
16 | 267000000 | 3 | 37 | 256 qam | 17 |
17 | 291000000 | 3.7 | 37 | 256 qam | 20 |
18 | 299000000 | 4.1 | 37 | 256 qam | 21 |
19 | 323000000 | 4.8 | 37 | 256 qam | 24 |
20 | 355000000 | 5.5 | 37 | 256 qam | 28 |
21 | 363000000 | 5.3 | 37 | 256 qam | 29 |
22 | 387000000 | 3.7 | 37 | 256 qam | 32 |
23 | 395000000 | 3.5 | 37 | 256 qam | 33 |
24 | 419000000 | 2.9 | 37 | 256 qam | 36 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.6 | 5 | 0 |
2 | Locked | 37.3 | 5 | 0 |
3 | Locked | 37.6 | 19 | 0 |
4 | Locked | 37.3 | 17 | 0 |
5 | Locked | 37.3 | 0 | 0 |
6 | Locked | 37.3 | 0 | 0 |
7 | Locked | 37.6 | 5 | 0 |
8 | Locked | 37.6 | 5 | 0 |
9 | Locked | 37.3 | 5 | 0 |
10 | Locked | 37.3 | 4 | 0 |
11 | Locked | 37.3 | 6 | 0 |
12 | Locked | 37.3 | 5 | 0 |
13 | Locked | 37.3 | 4 | 0 |
14 | Locked | 37.3 | 5 | 0 |
15 | Locked | 37.3 | 0 | 0 |
16 | Locked | 37.6 | 5 | 0 |
17 | Locked | 37.6 | 5 | 0 |
18 | Locked | 37.3 | 5 | 0 |
19 | Locked | 37.6 | 5 | 0 |
20 | Locked | 37.6 | 5 | 0 |
21 | Locked | 37.3 | 5 | 0 |
22 | Locked | 37.6 | 5 | 0 |
23 | Locked | 37.3 | 5 | 0 |
24 | Locked | 37.3 | 13 | 0 |
on 03-03-2024 11:38
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36600000 | 36.5 | 5120 | 64 qam | 11 |
2 | 23600009 | 32.5 | 5120 | 64 qam | 13 |
3 | 30100000 | 34 | 5120 | 64 qam | 12 |
4 | 43100019 | 36.5 | 5120 | 64 qam | 10 |
5 | 49599986 | 39 | 5120 | 64 qam | 9 |
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 |
5 | ATDMA | 0 | 0 | 1 | 0 |
on 03-03-2024 13:07
Looking at the date time of the two ATOM log messages, does that correspond to some unusually intense use of the VM Hub or is it just an Intel Atom processor glitch ?
on 03-03-2024 15:21
Nothing intense in terms of usage at all, pretty random, does this mean this replacement Hub 3 is also faulty and needs to be replaced ?
on 03-03-2024 16:01
The Atom restarts are usually when the CPU is overloaded. Also those power levels don’t seem right in that the spread is high? One of the Upstream is too low in any case. Should be at least 34.
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
on 05-03-2024 16:11
Hello Noobify
Sorry to hear of the connection issues experienced, we understand and appreciate you raising this via the forums and welcome to the community.
We can see you have spoken to the team since posting, were they able to offer any advice or a resolution during the call?
Rob
on 05-03-2024 19:35
Hi Rob, The disconnection/retention Team offered to send another Technical person to check the Virgin router, hoping this time he/she will be able to diagnose and fix the issues which the kind contributors above diagnosed