on 08-08-2021 12:41
For the last few days I have started to get packet loss on my connection. Its fairly new (1 yr) FTTP connection and up until now had been flawless.
I started back on @27th and then stopped but seems to have returned on the 4th. Although not huge it very noticeable on Voip when working from home and gaming.
Speed tests seem to indicate issue is on the upstream side as then it kicks in upload halves.
Ookla reports between 2 and 5% loss and BQM is also showing it :
BQM
on 08-08-2021 12:41
Time Priority Description
08/08/2021 04:51:26 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/08/2021 23:19:11 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/08/2021 10:50:16 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/08/2021 09:58:18 | 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; |
04/08/2021 09:56:46 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/08/2021 09:56:20 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/08/2021 09:56:19 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/08/2021 02:01:0 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/08/2021 07:52:9 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/08/2021 07:52:9 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/08/2021 07:52:9 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/08/2021 07:52:8 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/07/2021 21:44:3 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/07/2021 14:20:57 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/07/2021 14:20:57 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/07/2021 17:04:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/07/2021 02:20:56 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/07/2021 02:20:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/07/2021 04:25:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/07/2021 14:20:55 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 08-08-2021 12:42
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 2.7 | 40 | 256 qam | 25 |
2 | 203000000 | 3.5 | 40 | 256 qam | 9 |
3 | 211000000 | 3.2 | 40 | 256 qam | 10 |
4 | 219000000 | 3 | 40 | 256 qam | 11 |
5 | 227000000 | 3.2 | 40 | 256 qam | 12 |
6 | 235000000 | 3 | 40 | 256 qam | 13 |
7 | 243000000 | 3 | 40 | 256 qam | 14 |
8 | 251000000 | 3 | 40 | 256 qam | 15 |
9 | 259000000 | 2.7 | 40 | 256 qam | 16 |
10 | 267000000 | 2.9 | 40 | 256 qam | 17 |
11 | 275000000 | 2.4 | 40 | 256 qam | 18 |
12 | 283000000 | 2.2 | 40 | 256 qam | 19 |
13 | 291000000 | 2.2 | 40 | 256 qam | 20 |
14 | 299000000 | 2.4 | 40 | 256 qam | 21 |
15 | 307000000 | 2.4 | 40 | 256 qam | 22 |
16 | 315000000 | 2.4 | 40 | 256 qam | 23 |
17 | 323000000 | 2.2 | 40 | 256 qam | 24 |
18 | 339000000 | 2.2 | 40 | 256 qam | 26 |
19 | 347000000 | 2.7 | 40 | 256 qam | 27 |
20 | 355000000 | 2 | 40 | 256 qam | 28 |
21 | 363000000 | 2.4 | 40 | 256 qam | 29 |
22 | 371000000 | 2.2 | 40 | 256 qam | 30 |
23 | 379000000 | 2.5 | 40 | 256 qam | 31 |
24 | 387000000 | 2.2 | 40 | 256 qam | 32 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 5 | 0 |
2 | Locked | 40.9 | 6 | 0 |
3 | Locked | 40.3 | 5 | 0 |
4 | Locked | 40.3 | 6 | 0 |
5 | Locked | 40.9 | 5 | 0 |
6 | Locked | 40.3 | 5 | 0 |
7 | Locked | 40.3 | 4 | 0 |
8 | Locked | 40.3 | 5 | 0 |
9 | Locked | 40.3 | 0 | 0 |
10 | Locked | 40.3 | 5 | 0 |
11 | Locked | 40.9 | 5 | 0 |
12 | Locked | 40.3 | 6 | 0 |
13 | Locked | 40.3 | 11 | 0 |
14 | Locked | 40.9 | 4 | 0 |
15 | Locked | 40.3 | 5 | 0 |
16 | Locked | 40.3 | 4 | 0 |
17 | Locked | 40.3 | 0 | 0 |
18 | Locked | 40.3 | 0 | 0 |
19 | Locked | 40.9 | 0 | 0 |
20 | Locked | 40.9 | 0 | 0 |
21 | Locked | 40.3 | 3 | 0 |
22 | Locked | 40.9 | 0 | 0 |
23 | Locked | 40.3 | 5 | 0 |
24 | Locked | 40.9 | 6 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700012 | 33 | 5120 | 64 qam | 10 |
2 | 39400078 | 33 | 5120 | 64 qam | 12 |
3 | 46199998 | 33 | 5120 | 64 qam | 11 |
4 | 60299986 | 33 | 5120 | 64 qam | 9 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
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 09-08-2021 08:55
on 11-08-2021 08:59
Hi there @recalluk
Thank you so much for your post and I am so sorry to see you have had these issues with your connection!
I'm very glad to hear it now appears to be back to normal, but are you able to monitor this for us over the next few days just to make sure? Should there be any further issues I'd be more than happy to take a look again for you!
Thank you