on 07-11-2021 15:13
Afternoon, I have a hub 3. We've been getting intermittent WiFi drop outs for a couple of months now. It's usually 1 device at a time, so the rest still work. This ranges from smart phones, Alexa devices, Xbox etc. We've also had issues with streaming Netflix and Prime. The picture becomes distorted or simply stops quite frequently which should happen with a 200mb connection. I tethered my firestick to my phone yesterday when having issues trying to watch Prime and it worked fine. My son's Xbox cannot connect to the router, however can connect to my phone. I'm guessing there's an issue with the router broadcasting WiFi. I've done all the usual, reset router, reset devices etc. Any ideas?
on 07-11-2021 22:30
The T3 timeouts and high Pre & Post RS errors look bad, but they are accumulative since the hub was last power cycled, so please power cycle you hub and after a least 2 hours post a new set of figures. This will let us see the current state of your circuit.
on 08-11-2021 21:28
Status Tab
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 203000000 | Locked |
Ranged Upstream Channel (Hz) | 53700132 | Locked |
Provisioning State | Online |
on 08-11-2021 21:30
After about 3 hours since power cycle.
Downstream Tab
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 203000000 | 7.1 | 38 | 256 qam | 9 |
2 | 211000000 | 7.3 | 38 | 256 qam | 10 |
3 | 219000000 | 7.3 | 40 | 256 qam | 11 |
4 | 227000000 | 7 | 38 | 256 qam | 12 |
5 | 235000000 | 6.9 | 38 | 256 qam | 13 |
6 | 243000000 | 6.6 | 38 | 256 qam | 14 |
7 | 251000000 | 6.6 | 38 | 256 qam | 15 |
8 | 259000000 | 6.4 | 40 | 256 qam | 16 |
9 | 267000000 | 6.3 | 40 | 256 qam | 17 |
10 | 275000000 | 6 | 38 | 256 qam | 18 |
11 | 283000000 | 6 | 38 | 256 qam | 19 |
12 | 291000000 | 6 | 38 | 256 qam | 20 |
13 | 299000000 | 6 | 38 | 256 qam | 21 |
14 | 307000000 | 5.9 | 38 | 256 qam | 22 |
15 | 315000000 | 5.9 | 38 | 256 qam | 23 |
16 | 323000000 | 5.9 | 38 | 256 qam | 24 |
17 | 331000000 | 5.8 | 38 | 256 qam | 25 |
18 | 339000000 | 5.8 | 38 | 256 qam | 26 |
19 | 347000000 | 5.6 | 38 | 256 qam | 27 |
20 | 355000000 | 5.5 | 38 | 256 qam | 28 |
21 | 363000000 | 5.6 | 38 | 256 qam | 29 |
22 | 371000000 | 5.8 | 38 | 256 qam | 30 |
23 | 379000000 | 5.5 | 38 | 256 qam | 31 |
24 | 387000000 | 5.3 | 38 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 93 | 0 |
2 | Locked | 38.9 | 110 | 0 |
3 | Locked | 40.3 | 131 | 0 |
4 | Locked | 38.9 | 151 | 0 |
5 | Locked | 38.9 | 189 | 0 |
6 | Locked | 38.9 | 215 | 0 |
7 | Locked | 38.9 | 256 | 0 |
8 | Locked | 40.3 | 284 | 0 |
9 | Locked | 40.3 | 305 | 0 |
10 | Locked | 38.9 | 347 | 0 |
11 | Locked | 38.9 | 444 | 0 |
12 | Locked | 38.9 | 486 | 0 |
13 | Locked | 38.9 | 602 | 0 |
14 | Locked | 38.9 | 563 | 0 |
15 | Locked | 38.9 | 783 | 0 |
16 | Locked | 38.6 | 833 | 0 |
17 | Locked | 38.9 | 1140 | 0 |
18 | Locked | 38.6 | 1211 | 0 |
19 | Locked | 38.9 | 1495 | 0 |
20 | Locked | 38.9 | 1693 | 0 |
21 | Locked | 38.9 | 1875 | 0 |
22 | Locked | 38.9 | 2067 | 0 |
23 | Locked | 38.6 | 2384 | 0 |
24 | Locked | 38.9 | 2748 | 0 |
on 08-11-2021 21:31
Upstream Tab
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700132 | 39 | 5120 | 64 qam | 6 |
2 | 39400000 | 39 | 5120 | 64 qam | 8 |
3 | 46200141 | 39 | 5120 | 64 qam | 7 |
4 | 60299907 | 39 | 5120 | 64 qam | 5 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 08-11-2021 21:32
Configuration Tab
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | cmreg-vmdg505-bbt060-b.cm |
SFID | 5076 |
Max Traffic Rate | 230000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 5075 |
Max Traffic Rate | 22000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
on 08-11-2021 21:34
Network Log Tab
Time Priority Description
08/11/2021 04:56:21 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/11/2021 15:09:15 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/11/2021 10:21:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/11/2021 06:56:30 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/11/2021 03:08:45 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/11/2021 18:56:30 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/10/2021 14:22:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/10/2021 11:24:59 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/10/2021 09:08:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/10/2021 03:12:20 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/10/2021 21:25:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/10/2021 22:28:31 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/10/2021 07:03:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/10/2021 21:40:44 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/10/2021 20:19:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/10/2021 14:52:47 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2021 14:21:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2021 12:40:34 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/10/2021 12:57:15 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/10/2021 08:02:25 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 09-11-2021 14:15
Doesn’t look too bad.
Maybe a touch noisy.
A bqm may help see what’s going on.
Or just go get a nice Wi-Fi router and put the hub in modem mode.
By the way for your sons xbox he should really use and Ethernet cable. It’s a way better way to do it.
on 09-11-2021 18:39
Cheers, have already run a bqm. Pretty sure it's the router. Tim
on 12-11-2021 09:35
Hi timcymru1982,
Thanks for your post and apologies to hear that you are having an issue with your broadband connection.
Our diagnostics on your home network and Hub have not found any issues that could account for issues you're having. All power levels and signal levels are at optimal levels, I'm not seeing any errors and there are no open faults in your area either.
Looking at the Wifi side of the network, there is some congestion which could account for dropouts. You can try these tips and hints to optimise the WiFi as much as possible. You may also benefit from downloading the VM Connect App. You can use this to run scans to see what the issue may be. It will identify any dead spots and show you how to resolve them too.
Keep us posted with how you get on.