on 11-07-2024 19:01
So since June 25th it's when I started noticing it, i've been getting consistant packet loss small amounts but I could notice it during gaming.
I was Monitoring with Boardband quality monitor and was getting consistant pack loss, I had an engineer visit who replaced some parts to noavail, he said he thinks it might be their network as my Upload speed (20mbps/40mbps) was faster on my device than the actual hub, he said he'll speak to the networking team to see if they can see anything on their end.
couple of days later a fault had been identfied in my area so I signed up for fault updates, 2days ago I got an email saying F011378835 had been fixed, and I hadn't experianced any packet loss my upload speeds went back to normal (100mbps+), and 0 packet loss on all test for 2days.
but today it seems to have started again upload speed dropped right down to 20-40mbps from 100mbps and notice odd behaviour in games.
I've reset the hub but still experiancing the same - I will post Boardband quality Monitor tomorrow after several hours but this is just short period (the MS spike is probably me running tests)
these are the hub stats (which honeslty I have no idea about other than seeing critical errors & Timeouts)
any help would be great, ive tried all the usual fixes, complete reset, turned off all devices, made sure all connections were tight & engineer also replaced some parts and made sure everything was clean etc.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 171000000 | 4.1 | 41 | QAM 256 | 5 |
2 | 139000000 | 4.2 | 41 | QAM 256 | 1 |
3 | 147000000 | 4.3 | 42 | QAM 256 | 2 |
4 | 155000000 | 4.1 | 41 | QAM 256 | 3 |
5 | 163000000 | 4.2 | 41 | QAM 256 | 4 |
6 | 179000000 | 4.3 | 41 | QAM 256 | 6 |
7 | 187000000 | 4.4 | 41 | QAM 256 | 7 |
8 | 195000000 | 4.5 | 41 | QAM 256 | 8 |
9 | 203000000 | 4.6 | 41 | QAM 256 | 9 |
10 | 211000000 | 4.8 | 42 | QAM 256 | 10 |
11 | 219000000 | 4.5 | 42 | QAM 256 | 11 |
12 | 227000000 | 4.7 | 42 | QAM 256 | 12 |
13 | 235000000 | 4.5 | 42 | QAM 256 | 13 |
14 | 243000000 | 4.6 | 42 | QAM 256 | 14 |
15 | 251000000 | 4.4 | 42 | QAM 256 | 15 |
16 | 259000000 | 4.1 | 42 | QAM 256 | 16 |
17 | 267000000 | 4.1 | 42 | QAM 256 | 17 |
18 | 275000000 | 4 | 42 | QAM 256 | 18 |
19 | 283000000 | 4 | 42 | QAM 256 | 19 |
20 | 291000000 | 3.7 | 42 | QAM 256 | 20 |
21 | 299000000 | 3.5 | 42 | QAM 256 | 21 |
22 | 307000000 | 3.5 | 42 | QAM 256 | 22 |
23 | 315000000 | 3.4 | 42 | QAM 256 | 23 |
24 | 323000000 | 3.4 | 42 | QAM 256 | 24 |
25 | 331000000 | 3 | 41 | QAM 256 | 25 |
26 | 339000000 | 3.4 | 42 | QAM 256 | 26 |
27 | 347000000 | 3.6 | 42 | QAM 256 | 27 |
28 | 355000000 | 3.6 | 42 | QAM 256 | 28 |
29 | 363000000 | 3.9 | 42 | QAM 256 | 29 |
30 | 371000000 | 3.8 | 42 | QAM 256 | 30 |
31 | 379000000 | 3.9 | 42 | QAM 256 | 31 |
32 | 387000000 | 4 | 42 | QAM 256 | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 41 | 0 | 0 |
2 | Locked | 41 | 0 | 0 |
3 | Locked | 42 | 0 | 0 |
4 | Locked | 41 | 0 | 0 |
5 | Locked | 41 | 0 | 0 |
6 | Locked | 41 | 0 | 0 |
7 | Locked | 41 | 1 | 0 |
8 | Locked | 41 | 0 | 0 |
9 | Locked | 41 | 0 | 0 |
10 | Locked | 42 | 0 | 0 |
11 | Locked | 42 | 0 | 0 |
12 | Locked | 42 | 0 | 0 |
13 | Locked | 42 | 0 | 0 |
14 | Locked | 42 | 0 | 0 |
15 | Locked | 42 | 0 | 0 |
16 | Locked | 42 | 0 | 0 |
17 | Locked | 42 | 0 | 0 |
18 | Locked | 42 | 0 | 0 |
19 | Locked | 42 | 0 | 0 |
20 | Locked | 42 | 0 | 0 |
21 | Locked | 42 | 0 | 0 |
22 | Locked | 42 | 0 | 0 |
23 | Locked | 42 | 0 | 0 |
24 | Locked | 42 | 0 | 0 |
25 | Locked | 41 | 0 | 0 |
26 | Locked | 42 | 0 | 0 |
27 | Locked | 42 | 0 | 0 |
28 | Locked | 42 | 0 | 0 |
29 | Locked | 42 | 0 | 0 |
30 | Locked | 42 | 0 | 0 |
31 | Locked | 42 | 0 | 0 |
32 | Locked | 42 | 0 | 0 |
3.1 Downstream channels
159 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
159 | Locked | 43 | 5.3 | 34448580 | 203 |
3.0 Upstream channels
0 | 60300000 | 38.3 | 5120 | QAM 64 | 9 |
1 | 53700000 | 38.3 | 5120 | QAM 64 | 10 |
2 | 46200000 | 38.3 | 5120 | QAM 64 | 11 |
3 | 39400000 | 38.3 | 5120 | QAM 64 | 12 |
4 | 32600000 | 38.3 | 5120 | QAM 64 | 13 |
5 | 23600000 | 38.8 | 5120 | QAM 64 | 14 |
3.0 Upstream channels
0 | ATDMA | 0 | 0 | 5 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
General Configuration
Allowed |
3 |
Enabled |
3.1 |
UBsgvca69834ncxv9873254k;fg87 |
Primary Downstream Service Flow
2747 |
128000 bps |
4000bytes |
0 bps |
31122 |
1200000450 bps |
42600bytes |
0 bps |
Primary Upstream Service Flow
2746 |
128000 bps |
4000bytes |
0 bps |
1522bytes |
Best Effort |
31121 |
110000274 bps |
42600bytes |
0 bps |
42600bytes |
Best Effort |
on 11-07-2024 19:02
Logs after a reboot
11-07-2024 18:38:14 | notice | GUI Login Status - Login Success from LAN interface |
11-07-2024 17:27:44 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:27:43 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:21:25 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:19:12 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:16:40 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
11-07-2024 17:16:34 | warning | Dynamic Range Window violation |
11-07-2024 17:16:34 | warning | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:16:34 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:16:29 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:16:28 | notice | TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:16:21 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:16:18 | notice | Honoring MDD; IP provisioning mode = IPv4 |
11-07-2024 17:15:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:15:51 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
11-07-2024 17:15:51 | critical | Cable Modem Reboot because of - Reboot UI |
on 11-07-2024 19:09
post your full live BQM
any spikes on BQM can be caused by you like speed tests without your own QoS/BWM or VM running tests and any spikes when your idle is a problem.
on 11-07-2024 19:52
Hi legacy1.
I've only just recently restarted BQM after I'd experienced no packet loss for couple of days I've only just restarted it and even when idle I'm seeing packet loss.
This image is what I was experiencing before.
ignore the big red blotch that's a HUB 5 reset.
I haven't saved any previous ones just deleted them so I'll repost my new one tomorrow once its had several hours running.
While this is minimal packet loss I could tell.
on 12-07-2024 04:58
on 12-07-2024 07:45
a bit of low level packet loss that might be hard for VM to track down
on 12-07-2024 08:38
Yeah it's definitely small amounts but noticeable and upload speed completely tanked vs normal operations
Soon as we get some sort of traffic happens more.
Something clearly isn't right I've never had this constant packet loss with VM for awhile only ever had it once in 5 years and that was fixed pretty quick but this has been happening two weeks.
on 12-07-2024 10:39
you can run these tests to see if its upstream or downstream
Packet Loss Test – Test Your Connection Quality
Packet Loss Test - Test Your Connection Online | DeviceTests
on 12-07-2024 11:49
I've ran the top URL several times the past week or so and it's always losing then on received ill run more this afternoon when I'm back home.
12-07-2024 16:06 - edited 12-07-2024 16:08
Your Docsis downstream shows fine so must be routing past that.
you can run on wire for more info
ping -t -w 200 194.168.4.100
and
ping -t -w 1000 WAN gateway IP
CTRL + Pause to show the current loss