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 19:53
Your BQM is fine I suggest you look at getting your own wifi router with 1Gb ports and use hub in modem mode
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 09-03-2024 10:17
The second technician came today and changed the upstream power levels, said the Hub is fine. Fingers crossed, let's see. In any case planning to use the modem mode in future
on 12-03-2024 11:14
"ATOM is restarted" continues, it must be the processor in the Hub. Third technician booked, then I can get freedom from this amazingly reliable service !
on 15-03-2024 12:53
Hi @Noobify 👋.
Thanks for reaching out to us. Apologies for the issues that you have had with your hub, I can see you have stated you will be having another engineer, and have spoken about modem mode, could you please on the day that you have the engineer, should you get a replacement Hub, do not switch into modem mode straight away. We would need the Hub to complete its initial set up as well as any and all updates as it has been in storage since we have released updates. This would need to be in router mode for 24 hours to allow for it to be at maximum performance,
Sabrina
05-04-2024 22:09 - edited 05-04-2024 22:20
Moved to a Mesh with Hub 3 in modem mode, the stability has improved but issue still exists, here are the network log again, in case any one can find a cause, may be @Sabrina_B ?
Time Priority Description
05/04/2024 20:59:47 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/04/2024 08:28:40 | 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/04/2024 08:28:40 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/04/2024 07:14:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/03/2024 01:48:22 | 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; |
31/03/2024 01:48:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/03/2024 12:45:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/03/2024 12:29:3 | 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; |
23/03/2024 12:29:3 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/03/2024 09:36:18 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/03/2024 22:35:47 | 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; |
18/03/2024 22:35:47 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 14:30:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 13:43:58 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 13:33:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 10:35:47 | 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; |
15/03/2024 10:35:47 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 09:46:1 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 09:45:48 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/03/2024 09:18:21 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 05-04-2024 22:11
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 36600000 | 35 | 5120 | 64 qam | 11 |
2 | 23600000 | 31 | 5120 | 64 qam | 13 |
3 | 30100000 | 33 | 5120 | 64 qam | 12 |
4 | 43100000 | 36.5 | 5120 | 64 qam | 10 |
5 | 49600000 | 38 | 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 | 1 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
5 | ATDMA | 0 | 0 | 1 | 0 |
on 05-04-2024 22:12
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 291000000 | 3 | 36 | 256 qam | 20 |
2 | 139000000 | 7.9 | 37 | 256 qam | 1 |
3 | 147000000 | 7.1 | 37 | 256 qam | 2 |
4 | 155000000 | 6.6 | 37 | 256 qam | 3 |
5 | 163000000 | 6 | 37 | 256 qam | 4 |
6 | 171000000 | 6 | 37 | 256 qam | 5 |
7 | 179000000 | 5.6 | 37 | 256 qam | 6 |
8 | 187000000 | 5.5 | 37 | 256 qam | 7 |
9 | 195000000 | 5 | 37 | 256 qam | 8 |
10 | 203000000 | 4.5 | 36 | 256 qam | 9 |
11 | 211000000 | 4 | 36 | 256 qam | 10 |
12 | 219000000 | 3.5 | 37 | 256 qam | 11 |
13 | 227000000 | 3.5 | 36 | 256 qam | 12 |
14 | 235000000 | 3.5 | 36 | 256 qam | 13 |
15 | 243000000 | 2.5 | 36 | 256 qam | 14 |
16 | 251000000 | 2 | 36 | 256 qam | 15 |
17 | 259000000 | 2 | 36 | 256 qam | 16 |
18 | 267000000 | 2.4 | 37 | 256 qam | 17 |
19 | 275000000 | 2.5 | 36 | 256 qam | 18 |
20 | 283000000 | 2.9 | 36 | 256 qam | 19 |
21 | 299000000 | 3.5 | 36 | 256 qam | 21 |
22 | 307000000 | 3.5 | 37 | 256 qam | 22 |
23 | 315000000 | 3.5 | 37 | 256 qam | 23 |
24 | 323000000 | 3.7 | 37 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 36.6 | 53 | 0 |
2 | Locked | 37.3 | 59 | 192 |
3 | Locked | 37.3 | 61 | 0 |
4 | Locked | 37.3 | 84 | 0 |
5 | Locked | 37.3 | 75 | 0 |
6 | Locked | 37.3 | 49 | 0 |
7 | Locked | 37.6 | 61 | 0 |
8 | Locked | 37.3 | 59 | 0 |
9 | Locked | 37.3 | 45 | 0 |
10 | Locked | 36.6 | 66 | 0 |
11 | Locked | 36.6 | 69 | 0 |
12 | Locked | 37.3 | 66 | 0 |
13 | Locked | 36.6 | 52 | 0 |
14 | Locked | 36.6 | 79 | 0 |
15 | Locked | 36.6 | 77 | 0 |
16 | Locked | 36.6 | 120 | 0 |
17 | Locked | 36.6 | 101 | 0 |
18 | Locked | 37.3 | 108 | 0 |
19 | Locked | 36.6 | 104 | 0 |
20 | Locked | 36.6 | 56 | 0 |
21 | Locked | 36.6 | 68 | 0 |
22 | Locked | 37.3 | 52 | 0 |
23 | Locked | 37.6 | 63 | 0 |
24 | Locked | 37.6 | 83 | 0 |
on 06-04-2024 09:30
The upstream power is fine, actually. The power level from Hub is commanded by the VM end and is contingent on whether or not the VM end can read the keep-alive messages from the Hub. In modem mode, the ATOM messages are unlikely to occur because the (wretched) Hub 3 has nothing to do other than act as a bridge to your router.
The DHCP Renew messages are passive and you don’t need to worry about them.
So, in terms of your experience, what is going wrong now?
on 06-04-2024 10:29
Thanks so much !