on 17-05-2024 08:52
For a month or more I have noticed that my in house WIFI is randomly dropping out. I noticed this on my iPhone where I suddenly have no access by WIFI to the internet. Often the WIFI symbol is showing but not working.
I thought, at first, it was a problem with my iPhone but exactly the same happens to my wife's iPhone at the same time. After a short while it resumes as it should and works ok.
This occurs in parts of the house where I have a WIFI extender and also right next to my Hub 3 Router.
I have tried restarting the Router and also resetting it but the problem continues.
I have interrogated the Hub 3 and the Network Log which is shown below and I don't understand the results.
Answered! Go to Answer
on 17-05-2024 10:19
Don’t post pictures, follow these instructions:
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 17-05-2024 09:05
on 17-05-2024 09:19
Hi,
Your pictures have been declined, can you please copy and paste the logs (the first time it will fail, but the second time it will post).
on 17-05-2024 09:59
I'll try again
on 17-05-2024 10:08
How about this
on 17-05-2024 10:19
Don’t post pictures, follow these instructions:
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 17-05-2024 10:34
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 30 | 5120 | 64 qam | 11 |
2 | 23600000 | 30 | 5120 | 64 qam | 12 |
3 | 39400000 | 30 | 5120 | 64 qam | 8 |
4 | 46200000 | 30 | 5120 | 64 qam | 7 |
5 | 53700000 | 30.5 | 5120 | 64 qam | 6 |
6 | 60300000 | 30.8 | 5120 | 64 qam | 5 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 2 | 0 |
3 | ATDMA | 0 | 0 | 1 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
6 | ATDMA | 0 | 0 | 1 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 202750000 | 1 | 37 | 256 qam | 9 |
2 | 210750000 | 1.2 | 36 | 256 qam | 10 |
3 | 218750000 | 1.4 | 36 | 256 qam | 11 |
4 | 226750000 | 1.2 | 36 | 256 qam | 12 |
5 | 234750000 | 1.2 | 36 | 256 qam | 13 |
6 | 242750000 | 1 | 37 | 256 qam | 14 |
7 | 250750000 | 0.9 | 37 | 256 qam | 15 |
8 | 258750000 | 0.5 | 37 | 256 qam | 16 |
9 | 266750000 | 0.5 | 37 | 256 qam | 17 |
10 | 274750000 | 0.2 | 36 | 256 qam | 18 |
11 | 282750000 | 0.2 | 36 | 256 qam | 19 |
12 | 290750000 | 0.2 | 36 | 256 qam | 20 |
13 | 298750000 | 0.2 | 36 | 256 qam | 21 |
14 | 306750000 | 0.5 | 37 | 256 qam | 22 |
15 | 314750000 | 0.7 | 36 | 256 qam | 23 |
16 | 322750000 | 1 | 36 | 256 qam | 24 |
17 | 330750000 | 1.5 | 36 | 256 qam | 25 |
18 | 338750000 | 1.9 | 36 | 256 qam | 26 |
19 | 346750000 | 1.7 | 37 | 256 qam | 27 |
20 | 354750000 | 2 | 37 | 256 qam | 28 |
21 | 362750000 | 1.7 | 37 | 256 qam | 29 |
22 | 370750000 | 2 | 37 | 256 qam | 30 |
23 | 378750000 | 1.9 | 36 | 256 qam | 31 |
24 | 386750000 | 2 | 37 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.3 | 831 | 0 |
2 | Locked | 36.6 | 1424 | 0 |
3 | Locked | 36.3 | 1600 | 1 |
4 | Locked | 36.6 | 21 | 0 |
5 | Locked | 36.6 | 12 | 0 |
6 | Locked | 37.3 | 23 | 0 |
7 | Locked | 37.3 | 23 | 0 |
8 | Locked | 37.3 | 16 | 0 |
9 | Locked | 37.3 | 19 | 0 |
10 | Locked | 36.6 | 23 | 0 |
11 | Locked | 36.6 | 28 | 0 |
12 | Locked | 36.6 | 45 | 0 |
13 | Locked | 36.6 | 41 | 0 |
14 | Locked | 37.3 | 29 | 0 |
15 | Locked | 36.6 | 25 | 0 |
16 | Locked | 36.6 | 18 | 0 |
17 | Locked | 36.3 | 33 | 0 |
18 | Locked | 36.3 | 30 | 0 |
19 | Locked | 37.3 | 25 | 0 |
20 | Locked | 37.3 | 26 | 0 |
21 | Locked | 37.3 | 26 | 0 |
22 | Locked | 37.3 | 20 | 0 |
23 | Locked | 36.3 | 11 | 0 |
24 | Locked | 37.3 | 5 | 0 |
on 17-05-2024 10:35
Here's the res
Time Priority Description
17/05/2024 08:05:55 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2024 20:54:0 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2024 09:24:39 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2024 09:06:3 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2024 09:03:27 | notice | Unit has been restored to factory defaults from a software issued command;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2024 08:15:32 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/05/2024 02:56:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/05/2024 02:53:27 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/05/2024 17:21:3 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/05/2024 12:04:41 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/05/2024 22:15:12 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/05/2024 11:44:35 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2024 22:33:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2024 14:53:27 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2024 14:46:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2024 12:55:0 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2024 12:54:41 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2024 03:54:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/05/2024 02:53:27 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/05/2024 17:34:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 17-05-2024 11:13
Is there an attenuator (forward path type) attached to the rear of your hub? I ,would have expected the upstream power to be around the 40 dBmv mark. There’s nothing wrong with 30 dBmv on the upstream - the VM end commands the power it needs to successfully read the data. Inn the absence of an attenuator, I would have expected the downstream power level to exceed 15 dBmv.
on 17-05-2024 11:24
Upstream power levels are too low and some T3s. Unless there is a local area problem you will need a technician’s visit to rectify.
Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page status, but this is not recommended as it only covers issues that affect a very large number of customers.
VM will not dispatch any technicians while an area fault exists.
If no area faults found:
The primary place to report faults or for service requests is Customer Services on 0345 454 1111/150 if you have a VM landline or wait two or three days for a VM staff member to get to your post.