on 28-09-2022 09:24
Since moving to the hub 5, the power levels have been out of range, having issues with latency, dynamic range violations, and getting event codes 16 & 24.
Had a visit from an engineer who put two 3db attenuators on. At first this made the latency AWFUL, and I've mixed removing, just having one, etc. then due to work in the area things got a lot worse recently so I've got them both back currently.
Downstream all seems kinda fine, now getting regular 16 & 24 event codes on chan 49 - which I assume is upstream as there's no downstream channel 49.
Upstream is definitely at the top end of the range for power now (47ish across all) so just in range, however I'm only getting QPSK modulation.
Everything seems pretty stable recently, but seeing lots of events in the logs. Do I just leave it as is?
on 28-09-2022 09:25
Time Priority Description
27-09-2022 23:11:06 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 22:45:15 | 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; |
27-09-2022 22:45:15 | warning | Dynamic Range Window violation |
27-09-2022 19:31:33 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:29:11 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:21:52 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:19:13 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:13:29 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:11:12 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:07:41 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:05:21 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 19:01:19 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:59:11 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:56:16 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:54:03 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:53:40 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:51:23 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:49:33 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:48:58 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:44:04 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:40:07 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:37:24 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:36:08 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:34:03 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:31:57 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:29:33 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:27:39 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:26:15 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:23:43 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:20:58 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:19:06 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
27-09-2022 18:17:59 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 28-09-2022 09:26
Downstream bonded channels
1 | 331000000 | 7.7 | 42 | QAM 256 | 25 |
2 | 275000000 | 8 | 42 | QAM 256 | 18 |
3 | 283000000 | 8 | 42 | QAM 256 | 19 |
4 | 291000000 | 8 | 42 | QAM 256 | 20 |
5 | 299000000 | 7.9 | 42 | QAM 256 | 21 |
6 | 307000000 | 7.9 | 42 | QAM 256 | 22 |
7 | 315000000 | 7.9 | 42 | QAM 256 | 23 |
8 | 323000000 | 7.8 | 42 | QAM 256 | 24 |
9 | 339000000 | 7.7 | 42 | QAM 256 | 26 |
10 | 347000000 | 7.6 | 42 | QAM 256 | 27 |
11 | 355000000 | 7.6 | 42 | QAM 256 | 28 |
12 | 363000000 | 7.8 | 42 | QAM 256 | 29 |
13 | 371000000 | 7.8 | 42 | QAM 256 | 30 |
14 | 379000000 | 7.8 | 42 | QAM 256 | 31 |
15 | 387000000 | 7.9 | 42 | QAM 256 | 32 |
16 | 395000000 | 7.8 | 42 | QAM 256 | 33 |
17 | 403000000 | 7.7 | 42 | QAM 256 | 34 |
18 | 411000000 | 7.9 | 42 | QAM 256 | 35 |
19 | 419000000 | 8 | 42 | QAM 256 | 36 |
20 | 427000000 | 7.9 | 42 | QAM 256 | 37 |
21 | 435000000 | 8 | 42 | QAM 256 | 38 |
22 | 443000000 | 8 | 42 | QAM 256 | 39 |
23 | 451000000 | 8.2 | 42 | QAM 256 | 40 |
24 | 459000000 | 8.2 | 42 | QAM 256 | 41 |
25 | 467000000 | 8.2 | 42 | QAM 256 | 42 |
26 | 475000000 | 8.2 | 42 | QAM 256 | 43 |
27 | 483000000 | 8.2 | 42 | QAM 256 | 44 |
28 | 491000000 | 8.3 | 42 | QAM 256 | 45 |
29 | 499000000 | 8.2 | 42 | QAM 256 | 46 |
30 | 507000000 | 8 | 42 | QAM 256 | 47 |
31 | 515000000 | 7.8 | 42 | QAM 256 | 48 |
Downstream bonded channels
1 | Locked | 42 | 61 | 0 |
2 | Locked | 42 | 123 | 0 |
3 | Locked | 42 | 110 | 0 |
4 | Locked | 42 | 99 | 0 |
5 | Locked | 42 | 89 | 0 |
6 | Locked | 42 | 78 | 0 |
7 | Locked | 42 | 82 | 0 |
8 | Locked | 42 | 63 | 0 |
9 | Locked | 42 | 55 | 0 |
10 | Locked | 42 | 44 | 0 |
11 | Locked | 42 | 59 | 0 |
12 | Locked | 42 | 46 | 0 |
13 | Locked | 42 | 47 | 0 |
14 | Locked | 42 | 32 | 0 |
15 | Locked | 42 | 27 | 0 |
16 | Locked | 42 | 27 | 0 |
17 | Locked | 42 | 33 | 0 |
18 | Locked | 42 | 30 | 0 |
19 | Locked | 42 | 38 | 0 |
20 | Locked | 42 | 38 | 0 |
21 | Locked | 42 | 54 | 0 |
22 | Locked | 42 | 46 | 19 |
23 | Locked | 42 | 27 | 43 |
24 | Locked | 42 | 35 | 57 |
25 | Locked | 42 | 34 | 63 |
26 | Locked | 42 | 38 | 32 |
27 | Locked | 42 | 124 | 64 |
28 | Locked | 42 | 212 | 445 |
29 | Locked | 42 | 277 | 582 |
30 | Locked | 42 | 100 | 143 |
31 | Locked | 42 | 29 | 40 |
Upstream bonded channels
0 | 60300000 | 47.5 | 5120 | QPSK | 1 |
1 | 53700000 | 47.5 | 5120 | QPSK | 2 |
2 | 46200000 | 47.8 | 5120 | QPSK | 3 |
3 | 39400000 | 47.5 | 5120 | QPSK | 4 |
on 28-09-2022 10:55
Looking at those stats it would seem to me that you would need a 6dB attenuator not a 3dB one. There is an anomaly with the upstream power levels, they are too high and I wonder if the attenuator is a full path one, not a forward path only one. There is are also a lot of Post RS errors on the downstream. You definitely need the technician back. Call customer services or wait a couple of days for a VM staff member to get to your post.
on 28-09-2022 11:00
Thanks Tudor, yes good shout I think you're right that they're forward path so prob need replacing with full. Thanks again 🙂
on 28-09-2022 11:43
Other way around, full path needs replacing with a forward path only attenuator.
on 30-09-2022 13:17
Hi Alex_p99
Thanks for coming back to the thread.
I have done a system check here and your upstream levels are in spec, they're currently sat between 47-48 which are fine. The downstream ones are high but in spec. Please could you go round all connections and ensure they are finger tight for me. Then reboot the router and then upload a fresh set of stats?
Best,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill