on 17-06-2021 21:47
Have recently upgraded to M600 but not getting anywhere near the guaranteed speeds - typically in range 190-260.
I have followed all instructions to check cabling, reboot, restart, etc and ring on numerous occasions as well as registering a complaint.
on occasions the speed has improved by whatever the person on the end of the phone has done, however this soon reverts back to the lower speeds
no offer of beginner to look at this however virgin happy to have taken the additional payments for the upgrade, and part of sales pitch was with the home works service you will get next day service for any broadband issues.
any thoughts how I can get someone to take notice and own the fact I have a problem?
Answered! Go to Answer
on 18-06-2021 08:53
Hi Andrew,
Downstream
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 411000000 | 4.6 | 38 | 256 qam | 1 |
2 | 419000000 | 4.5 | 38 | 256 qam | 2 |
3 | 427000000 | 4.5 | 38 | 256 qam | 3 |
4 | 435000000 | 4.5 | 38 | 256 qam | 4 |
5 | 443000000 | 4.5 | 38 | 256 qam | 5 |
6 | 451000000 | 4.4 | 38 | 256 qam | 6 |
7 | 459000000 | 4.4 | 38 | 256 qam | 7 |
8 | 467000000 | 4.3 | 38 | 256 qam | 8 |
9 | 475000000 | 4 | 38 | 256 qam | 9 |
10 | 483000000 | 3.7 | 38 | 256 qam | 10 |
11 | 491000000 | 3.7 | 38 | 256 qam | 11 |
12 | 499000000 | 3.4 | 38 | 256 qam | 12 |
13 | 507000000 | 3.4 | 38 | 256 qam | 13 |
14 | 515000000 | 3.7 | 38 | 256 qam | 14 |
15 | 523000000 | 3.7 | 38 | 256 qam | 15 |
16 | 531000000 | 3.7 | 38 | 256 qam | 16 |
17 | 539000000 | 3.7 | 38 | 256 qam | 17 |
18 | 547000000 | 3.7 | 38 | 256 qam | 18 |
19 | 555000000 | 3.9 | 38 | 256 qam | 19 |
20 | 563000000 | 3.9 | 38 | 256 qam | 20 |
21 | 571000000 | 4 | 38 | 256 qam | 21 |
22 | 579000000 | 3.7 | 38 | 256 qam | 22 |
23 | 587000000 | 3.7 | 38 | 256 qam | 23 |
24 | 595000000 | 3.4 | 38 | 256 qam | 24 |
UPSTREAM
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60300000 | 49.3 | 5120 | 64 qam | 1 |
2 | 39400000 | 48.5 | 5120 | 64 qam | 4 |
3 | 46200000 | 48.5 | 5120 | 64 qam | 3 |
4 | 53700000 | 48.8 | 5120 | 64 qam | 2 |
Upstream bonded channels
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 | 0 | 0 |
Network Log
Network Log
Time Priority Description
18/06/2021 08:43:8 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:41:35 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:40:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:23:22 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:21:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:15:5 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 05:02:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 04:36:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2021 14:21:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2021 10:38:35 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2021 16:34:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 19:28:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 14:28:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 11:20:40 | notice | Touchstone SW Upgrade Reboot Delayed due to Call in Progress;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2021 21:37:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2021 19:41:52 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2021 10:31:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2021 09:34:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/06/2021 02:33:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2021 21:34:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 04-07-2021 11:21
Hi stuchop,
Thanks for getting back to us,
I've had a close look and there are still a level or two on the hub that are showing out of specification.
I can see it's been around a week since the last reboot, can you please do this and let me know if there is any improvement?
I'll then check the hub stats again.
Alex_Rm
on 18-06-2021 06:53
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 18-06-2021 08:53
Hi Andrew,
Downstream
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 411000000 | 4.6 | 38 | 256 qam | 1 |
2 | 419000000 | 4.5 | 38 | 256 qam | 2 |
3 | 427000000 | 4.5 | 38 | 256 qam | 3 |
4 | 435000000 | 4.5 | 38 | 256 qam | 4 |
5 | 443000000 | 4.5 | 38 | 256 qam | 5 |
6 | 451000000 | 4.4 | 38 | 256 qam | 6 |
7 | 459000000 | 4.4 | 38 | 256 qam | 7 |
8 | 467000000 | 4.3 | 38 | 256 qam | 8 |
9 | 475000000 | 4 | 38 | 256 qam | 9 |
10 | 483000000 | 3.7 | 38 | 256 qam | 10 |
11 | 491000000 | 3.7 | 38 | 256 qam | 11 |
12 | 499000000 | 3.4 | 38 | 256 qam | 12 |
13 | 507000000 | 3.4 | 38 | 256 qam | 13 |
14 | 515000000 | 3.7 | 38 | 256 qam | 14 |
15 | 523000000 | 3.7 | 38 | 256 qam | 15 |
16 | 531000000 | 3.7 | 38 | 256 qam | 16 |
17 | 539000000 | 3.7 | 38 | 256 qam | 17 |
18 | 547000000 | 3.7 | 38 | 256 qam | 18 |
19 | 555000000 | 3.9 | 38 | 256 qam | 19 |
20 | 563000000 | 3.9 | 38 | 256 qam | 20 |
21 | 571000000 | 4 | 38 | 256 qam | 21 |
22 | 579000000 | 3.7 | 38 | 256 qam | 22 |
23 | 587000000 | 3.7 | 38 | 256 qam | 23 |
24 | 595000000 | 3.4 | 38 | 256 qam | 24 |
UPSTREAM
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60300000 | 49.3 | 5120 | 64 qam | 1 |
2 | 39400000 | 48.5 | 5120 | 64 qam | 4 |
3 | 46200000 | 48.5 | 5120 | 64 qam | 3 |
4 | 53700000 | 48.8 | 5120 | 64 qam | 2 |
Upstream bonded channels
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 | 0 | 0 |
Network Log
Network Log
Time Priority Description
18/06/2021 08:43:8 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:41:35 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:40:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:23:22 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:21:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:15:5 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 05:02:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 04:36:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2021 14:21:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2021 10:38:35 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2021 16:34:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 19:28:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 14:28:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 11:20:40 | notice | Touchstone SW Upgrade Reboot Delayed due to Call in Progress;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2021 21:37:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2021 19:41:52 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2021 10:31:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2021 09:34:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/06/2021 02:33:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2021 21:34:14 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 18-06-2021 09:15
on 18-06-2021 09:25
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 205 | 225 |
2 | Locked | 38.9 | 199 | 208 |
3 | Locked | 38.9 | 228 | 198 |
4 | Locked | 38.6 | 199 | 207 |
5 | Locked | 38.6 | 211 | 213 |
6 | Locked | 38.9 | 207 | 197 |
7 | Locked | 38.9 | 186 | 194 |
8 | Locked | 38.6 | 235 | 188 |
9 | Locked | 38.6 | 198 | 203 |
10 | Locked | 38.6 | 193 | 178 |
11 | Locked | 38.6 | 222 | 179 |
12 | Locked | 38.6 | 251 | 197 |
13 | Locked | 38.6 | 223 | 197 |
14 | Locked | 38.6 | 228 | 169 |
15 | Locked | 38.9 | 244 | 195 |
16 | Locked | 38.6 | 290 | 195 |
17 | Locked | 38.9 | 284 | 194 |
18 | Locked | 38.6 | 264 | 142 |
19 | Locked | 38.9 | 220 | 170 |
20 | Locked | 38.6 | 338 | 192 |
21 | Locked | 38.9 | 271 | 196 |
22 | Locked | 38.6 | 213 | 162 |
23 | Locked | 38.6 | 212 | 145 |
24 | Locked | 38.6 | 258 | 192 |
on 18-06-2021 12:10
Downstream error counts look high, and would affect speed. Whilst upstream power's a bit high, it is within the accepted range, and there's little else that looks out of kilter. What we need you to do now is to reboot the hub in order to zero the error counters, leave the hub to its own devices and use normally for 12 or 24 hours, and then re-post the downstream error counts (may as well do the rest of the hub status data while you're at it).
That'll show if the errors were a historic event, or whether they're a continuing issue. The other thing is to describe how you're measuring speed (device and connection).
on 18-06-2021 12:31
Thanks I have rebooted; I have also been round and checked all connections again - there are a lot between entering the house and modem which may of course impact
will leave and run again
so I have been measuring speed using ookla through mobile devices daily but also Ethernet cabled to a laptop weekly
i have also set up a broadband checker on think broadband; it’s my day off and wet so have the time to look at these things
thanks for your help so far
on 19-06-2021 14:30
So update 24 hours on as below
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 411000000 | 5 | 38 | 256 qam | 1 |
2 | 419000000 | 4.8 | 38 | 256 qam | 2 |
3 | 427000000 | 4.9 | 38 | 256 qam | 3 |
4 | 435000000 | 4.6 | 38 | 256 qam | 4 |
5 | 443000000 | 4.8 | 38 | 256 qam | 5 |
6 | 451000000 | 4.6 | 38 | 256 qam | 6 |
7 | 459000000 | 4.6 | 38 | 256 qam | 7 |
8 | 467000000 | 4.5 | 38 | 256 qam | 8 |
9 | 475000000 | 4.3 | 38 | 256 qam | 9 |
10 | 483000000 | 4 | 38 | 256 qam | 10 |
11 | 491000000 | 3.7 | 38 | 256 qam | 11 |
12 | 499000000 | 3.5 | 38 | 256 qam | 12 |
13 | 507000000 | 3.7 | 38 | 256 qam | 13 |
14 | 515000000 | 4 | 38 | 256 qam | 14 |
15 | 523000000 | 3.9 | 38 | 256 qam | 15 |
16 | 531000000 | 3.9 | 38 | 256 qam | 16 |
17 | 539000000 | 4 | 38 | 256 qam | 17 |
18 | 547000000 | 4 | 38 | 256 qam | 18 |
19 | 555000000 | 4 | 38 | 256 qam | 19 |
20 | 563000000 | 4 | 38 | 256 qam | 20 |
21 | 571000000 | 4 | 38 | 256 qam | 21 |
22 | 579000000 | 3.9 | 38 | 256 qam | 22 |
23 | 587000000 | 3.7 | 38 | 256 qam | 23 |
24 | 595000000 | 3.5 | 38 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 111 | 0 |
2 | Locked | 38.9 | 111 | 0 |
3 | Locked | 38.9 | 107 | 0 |
4 | Locked | 38.9 | 128 | 0 |
5 | Locked | 38.6 | 147 | 0 |
6 | Locked | 38.6 | 147 | 0 |
7 | Locked | 38.9 | 181 | 0 |
8 | Locked | 38.6 | 174 | 0 |
9 | Locked | 38.6 | 198 | 0 |
10 | Locked | 38.9 | 232 | 0 |
11 | Locked | 38.6 | 253 | 0 |
12 | Locked | 38.9 | 316 | 0 |
13 | Locked | 38.9 | 356 | 0 |
14 | Locked | 38.9 | 298 | 0 |
15 | Locked | 38.6 | 314 | 0 |
16 | Locked | 38.9 | 323 | 0 |
17 | Locked | 38.9 | 360 | 0 |
18 | Locked | 38.6 | 458 | 0 |
19 | Locked | 38.9 | 373 | 0 |
20 | Locked | 38.9 | 409 | 0 |
21 | Locked | 38.6 | 387 | 0 |
22 | Locked | 38.6 | 430 | 0 |
23 | Locked | 38.6 | 409 | 0 |
24 | Locked | 38.9 | 536 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60300000 | 49.8 | 5120 | 64 qam | 1 |
2 | 39400000 | 48.8 | 5120 | 64 qam | 4 |
3 | 46200000 | 48.8 | 5120 | 64 qam | 3 |
4 | 53700000 | 49.3 | 5120 | 64 qam | 2 |
Upstream bonded channels
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 | 1 | 0 |
on 19-06-2021 14:31
Network Log
Time Priority Description
18/06/2021 14:04:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 13:55:5 | 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; |
18/06/2021 13:55:4 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 13:54:59 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 13:54:59 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 13:54:58 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 13:54:58 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 10:23:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:43:8 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:41:35 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 08:40:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:23:22 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:21:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 06:15:5 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 05:02:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 04:36:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2021 14:21:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/06/2021 10:38:35 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2021 16:34:22 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2021 19:28:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 19-06-2021 14:41
Latest hub stats look OK, but the network log is very poor, and the time distribution makes it look unlikely that they're all due to you fiddling with connections. I'll mark this for staff to take a look and advise.