on 30-05-2022 15:27
Hi, I’m on the VM200 package and trying to use ZScaler as part of my employers software. I’m on a hub 3.0
for almost 2 years now on the VM100 package I’ve worked from home with no issues. Now over the last month it’s become unbearable with low connectivity speeds (Wi-Fi and cable) frequent disconnects. Even being the only one in the house.
work IT blame VM saying if I had more upload it would be fine. But I’ve gone from VM100 to VM200 and it’s still trash.
can anyone suggest where I should start looking to get this sorted. Thanks.
Answered! Go to Answer
on 30-05-2022 16:32
Ignore that advice from legacy1, that won't improve the broadband connection quality, which looks ropey judging by the high post-RS error counts. Restart the hub, wait 12 or 24 hours, repost the downstream stats that show the error counts. If that shows the post-RS counts are rising, then chances are you'll need a technician. The only thing within your control to check is (before restating the hub!) to undo and remake the coax connections between the hub and the wall box, since high post-RS counts are sometimes a sign of faulty connection allowing radio frequency noise ingress.
on 30-05-2022 15:50
Connect to the hub by clicking on this link http://192.168.0.1/ That should pull up the log in page for the hub. But don't log in, just click on the link "Check router status" That'll bring up a window with five tabs. Open the Downstream tab. Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots. Post that, do the same for the Upstream and Network log. You'll get an error message when you post the Network log, just click on "post" a second time. Then we can check for any obvious problems with power, noise or error counts.
on 30-05-2022 16:10
1 | 275000000 | 6.6 | 38 | 256 qam | 18 |
2 | 203000000 | 7.4 | 40 | 256 qam | 9 |
3 | 211000000 | 6.9 | 38 | 256 qam | 10 |
4 | 219000000 | 6.5 | 38 | 256 qam | 11 |
5 | 227000000 | 6.3 | 38 | 256 qam | 12 |
6 | 235000000 | 5.6 | 38 | 256 qam | 13 |
7 | 243000000 | 5.5 | 38 | 256 qam | 14 |
8 | 251000000 | 5.5 | 38 | 256 qam | 15 |
9 | 259000000 | 6.4 | 38 | 256 qam | 16 |
10 | 267000000 | 6.5 | 38 | 256 qam | 17 |
11 | 283000000 | 6.6 | 40 | 256 qam | 19 |
12 | 291000000 | 6.6 | 40 | 256 qam | 20 |
13 | 299000000 | 6.9 | 38 | 256 qam | 21 |
14 | 307000000 | 7 | 38 | 256 qam | 22 |
15 | 315000000 | 7.6 | 40 | 256 qam | 23 |
16 | 323000000 | 7.8 | 40 | 256 qam | 24 |
17 | 331000000 | 8 | 40 | 256 qam | 25 |
18 | 339000000 | 8 | 40 | 256 qam | 26 |
19 | 347000000 | 7.9 | 40 | 256 qam | 27 |
20 | 355000000 | 7 | 38 | 256 qam | 28 |
21 | 363000000 | 6.8 | 40 | 256 qam | 29 |
22 | 371000000 | 6.5 | 38 | 256 qam | 30 |
23 | 379000000 | 6.5 | 38 | 256 qam | 31 |
24 | 387000000 | 6.6 | 40 | 256 qam | 32 |
1 | Locked | 38.9 | 98 | 7756 |
2 | Locked | 40.3 | 128 | 7411 |
3 | Locked | 38.9 | 107 | 7909 |
4 | Locked | 38.9 | 92 | 7801 |
5 | Locked | 38.9 | 95 | 7805 |
6 | Locked | 38.6 | 100 | 7855 |
7 | Locked | 38.9 | 97 | 7852 |
8 | Locked | 38.9 | 137 | 7650 |
9 | Locked | 38.9 | 172 | 7486 |
10 | Locked | 38.9 | 114 | 7923 |
11 | Locked | 40.3 | 206 | 7580 |
12 | Locked | 40.3 | 259 | 7334 |
13 | Locked | 38.9 | 136 | 7966 |
14 | Locked | 38.9 | 694 | 4756 |
15 | Locked | 40.9 | 572 | 4592 |
16 | Locked | 40.3 | 542 | 4608 |
17 | Locked | 40.3 | 590 | 4514 |
18 | Locked | 40.3 | 571 | 4444 |
19 | Locked | 40.9 | 159 | 7109 |
20 | Locked | 38.9 | 670 | 4056 |
21 | Locked | 40.3 | 1247 | 4166 |
22 | Locked | 38.9 | 922 | 3570 |
23 | Locked | 38.9 | 1488 | 4408 |
24 | Locked | 40.3 | 603 | 4643 |
on 30-05-2022 16:11
1 | 53700002 | 45.8 | 5120 | 64 qam | 2 |
2 | 39399981 | 44.3 | 5120 | 64 qam | 4 |
3 | 46200004 | 45.8 | 5120 | 64 qam | 3 |
4 | 60299991 | 45.8 | 5120 | 64 qam | 1 |
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 30-05-2022 16:12
30/05/2022 15:57:38 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:5 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:5 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:4 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:54:18 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:07:1 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:03:20 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:01:58 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:01:4 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:00:46 | 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:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 14:36:28 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/05/2022 00:48:45 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/05/2022 22:21:1 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/05/2022 22:21:1 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/05/2022 21:49:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/05/2022 18:37:30 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/05/2022 00:08:34 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/05/2022 20:48:37 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/05/2022 20:48:37 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30-05-2022 16:22 - edited 30-05-2022 16:45
Put hub in modem mode test by wire should be fine.
on 30-05-2022 16:32
Ignore that advice from legacy1, that won't improve the broadband connection quality, which looks ropey judging by the high post-RS error counts. Restart the hub, wait 12 or 24 hours, repost the downstream stats that show the error counts. If that shows the post-RS counts are rising, then chances are you'll need a technician. The only thing within your control to check is (before restating the hub!) to undo and remake the coax connections between the hub and the wall box, since high post-RS counts are sometimes a sign of faulty connection allowing radio frequency noise ingress.
on 30-05-2022 18:04
I've turned everything off, reconnected everything and turned it all back on.
1 | 275000000 | 7.1 | 38 | 256 qam | 18 |
2 | 203000000 | 7.6 | 40 | 256 qam | 9 |
3 | 211000000 | 7.3 | 38 | 256 qam | 10 |
4 | 219000000 | 7 | 38 | 256 qam | 11 |
5 | 227000000 | 6.6 | 38 | 256 qam | 12 |
6 | 235000000 | 6.1 | 38 | 256 qam | 13 |
7 | 243000000 | 6 | 38 | 256 qam | 14 |
8 | 251000000 | 6.1 | 38 | 256 qam | 15 |
9 | 259000000 | 6.8 | 38 | 256 qam | 16 |
10 | 267000000 | 7 | 38 | 256 qam | 17 |
11 | 283000000 | 7.1 | 40 | 256 qam | 19 |
12 | 291000000 | 7.1 | 40 | 256 qam | 20 |
13 | 299000000 | 7.4 | 38 | 256 qam | 21 |
14 | 307000000 | 7.5 | 40 | 256 qam | 22 |
15 | 315000000 | 8 | 40 | 256 qam | 23 |
16 | 323000000 | 8.3 | 40 | 256 qam | 24 |
17 | 331000000 | 8.4 | 40 | 256 qam | 25 |
18 | 339000000 | 8.4 | 40 | 256 qam | 26 |
19 | 347000000 | 8 | 40 | 256 qam | 27 |
20 | 355000000 | 7.5 | 40 | 256 qam | 28 |
21 | 363000000 | 7.1 | 38 | 256 qam | 29 |
22 | 371000000 | 7 | 38 | 256 qam | 30 |
23 | 379000000 | 7 | 38 | 256 qam | 31 |
24 | 387000000 | 7 | 38 | 256 qam | 32 |
1 | Locked | 38.9 | 6 | 0 |
2 | Locked | 40.3 | 6 | 0 |
3 | Locked | 38.9 | 6 | 0 |
4 | Locked | 38.9 | 7 | 0 |
5 | Locked | 38.9 | 4 | 0 |
6 | Locked | 38.9 | 6 | 0 |
7 | Locked | 38.9 | 3 | 0 |
8 | Locked | 38.9 | 7 | 0 |
9 | Locked | 38.9 | 6 | 0 |
10 | Locked | 38.9 | 6 | 0 |
11 | Locked | 40.3 | 4 | 0 |
12 | Locked | 40.3 | 6 | 0 |
13 | Locked | 38.9 | 6 | 0 |
14 | Locked | 40.3 | 6 | 0 |
15 | Locked | 40.3 | 18 | 0 |
16 | Locked | 40.3 | 18 | 0 |
17 | Locked | 40.3 | 18 | 0 |
18 | Locked | 40.3 | 19 | 0 |
19 | Locked | 40.3 | 4 | 0 |
20 | Locked | 40.3 | 5 | 0 |
21 | Locked | 38.9 | 6 | 0 |
22 | Locked | 38.9 | 5 | 0 |
23 | Locked | 38.9 | 4 | 0 |
24 | Locked | 38.9 | 0 | 0 |
on 30-05-2022 18:05
1 | 53700063 | 45.8 | 5120 | 64 qam | 2 |
2 | 39400007 | 43.8 | 5120 | 64 qam | 4 |
3 | 46200021 | 44.3 | 5120 | 64 qam | 3 |
4 | 60300068 | 45.8 | 5120 | 64 qam | 1 |
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 30-05-2022 18:06
30/05/2022 17:13:0 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 16:40:35 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 16:30:41 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 16:30:14 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 16:27:26 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 16:26:7 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 16:11:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:38 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:5 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:5 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:57:4 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:54:18 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:07:1 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:03:20 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:01:58 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:01:4 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 15:00:46 | 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:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/05/2022 14:36:28 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/05/2022 00:48:45 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |