19-12-2022 21:40 - edited 19-12-2022 21:44
upgraded from 350 ( 3 kids all XBOXing, downloading games , tv 4k streaming etc )
I used to get a solid 350 but after upgrading i get anything from 400 to 550, it fluctuates so much its a different result each time within a minute it can be 550 then its 420.
I do get a pretty solid upload of 50mpbs
I'm modem mode connected to an ASUS RT-AX88U.
50% of my stuff is connected to cat5 and i get from my nas to my pc a rock steady 97mb maxing my 1gb network when coping files so its not a local network issue.
using my pc with speedtest or the routers built in speedtest ( Ookla so a Direct router to isp link test ) getting on average 500mbps
anything strange here ?
Downstream bonded channels
1 | 227000000 | 4.8 | 42 | QAM 256 | 12 |
2 | 211000000 | 4.8 | 42 | QAM 256 | 10 |
3 | 219000000 | 4.8 | 42 | QAM 256 | 11 |
4 | 235000000 | 4.8 | 42 | QAM 256 | 13 |
5 | 243000000 | 5 | 42 | QAM 256 | 14 |
6 | 251000000 | 5.3 | 42 | QAM 256 | 15 |
7 | 259000000 | 5.6 | 42 | QAM 256 | 16 |
8 | 267000000 | 5.4 | 42 | QAM 256 | 17 |
9 | 275000000 | 5.5 | 42 | QAM 256 | 18 |
10 | 283000000 | 5.7 | 42 | QAM 256 | 19 |
11 | 291000000 | 5.7 | 42 | QAM 256 | 20 |
12 | 299000000 | 5.5 | 42 | QAM 256 | 21 |
13 | 307000000 | 5.5 | 42 | QAM 256 | 22 |
14 | 315000000 | 5.3 | 42 | QAM 256 | 23 |
15 | 323000000 | 4.7 | 42 | QAM 256 | 24 |
16 | 331000000 | 4.3 | 42 | QAM 256 | 25 |
17 | 339000000 | 4.2 | 41 | QAM 256 | 26 |
18 | 347000000 | 3.9 | 41 | QAM 256 | 27 |
19 | 355000000 | 3.5 | 42 | QAM 256 | 28 |
20 | 363000000 | 3.5 | 41 | QAM 256 | 29 |
21 | 371000000 | 3.5 | 41 | QAM 256 | 30 |
22 | 379000000 | 3.5 | 41 | QAM 256 | 31 |
23 | 387000000 | 3.3 | 41 | QAM 256 | 32 |
24 | 395000000 | 3.5 | 41 | QAM 256 | 33 |
25 | 403000000 | 3.4 | 41 | QAM 256 | 34 |
26 | 411000000 | 3.1 | 41 | QAM 256 | 35 |
27 | 419000000 | 2.6 | 41 | QAM 256 | 36 |
28 | 427000000 | 2.9 | 41 | QAM 256 | 37 |
29 | 435000000 | 2.8 | 41 | QAM 256 | 38 |
30 | 443000000 | 2.6 | 41 | QAM 256 | 39 |
31 | 451000000 | 2.5 | 41 | QAM 256 | 40 |
Downstream bonded channels
1 | Locked | 42 | 23 | 0 |
2 | Locked | 42 | 45 | 24 |
3 | Locked | 42 | 59 | 9 |
4 | Locked | 42 | 43 | 0 |
5 | Locked | 42 | 26 | 0 |
6 | Locked | 42 | 19 | 0 |
7 | Locked | 42 | 79 | 0 |
8 | Locked | 42 | 57 | 0 |
9 | Locked | 42 | 27 | 0 |
10 | Locked | 42 | 44 | 0 |
11 | Locked | 42 | 27 | 0 |
12 | Locked | 42 | 53 | 0 |
13 | Locked | 42 | 44 | 0 |
14 | Locked | 42 | 42 | 0 |
15 | Locked | 42 | 60 | 0 |
16 | Locked | 42 | 56 | 0 |
17 | Locked | 41 | 53 | 0 |
18 | Locked | 41 | 53 | 0 |
19 | Locked | 42 | 36 | 0 |
20 | Locked | 41 | 23 | 0 |
21 | Locked | 41 | 29 | 0 |
22 | Locked | 41 | 26 | 0 |
23 | Locked | 41 | 23 | 0 |
24 | Locked | 41 | 21 | 0 |
25 | Locked | 41 | 33 | 0 |
26 | Locked | 41 | 22 | 0 |
27 | Locked | 41 | 19 | 0 |
28 | Locked | 41 | 19 | 0 |
29 | Locked | 41 | 20 | 0 |
30 | Locked | 41 | 23 | 0 |
31 | Locked | 41 | 27 | 0 |
Upstream bonded channels
0 | 49600000 | 49.3 | 5120 | QAM 64 | 1 |
1 | 43100000 | 48.8 | 5120 | QAM 64 | 2 |
2 | 36600000 | 48.5 | 5120 | QAM 64 | 3 |
3 | 30100000 | 47.3 | 5120 | QAM 64 | 4 |
4 | 23600000 | 46.8 | 5120 | QAM 64 | 5 |
Upstream bonded channels
0 | ATDMA | 0 | 0 | 0 | 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 |
19-12-2022 21:07:50 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 16:37:01 | 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; |
19-12-2022 16:35:09 | 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; |
19-12-2022 16:24:57 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 16:22:57 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 16:19:40 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 16:17:10 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 16:13:20 | 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; |
19-12-2022 16:11:01 | 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; |
19-12-2022 04:22:55 | 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; |
19-12-2022 04:20:58 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 04:18:49 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-12-2022 04:18:39 | 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; |
18-12-2022 20:00:59 | 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; |
18-12-2022 19:58:32 | 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; |
18-12-2022 19:45:36 | 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; |
18-12-2022 19:43:44 | 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; |
18-12-2022 19:23:34 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 19:21:03 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 19:13:03 | 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; |
18-12-2022 19:11:15 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 19:07:36 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 19:07: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; |
18-12-2022 19:03:51 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 19:01:55 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 18:48:05 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 18:42:25 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 18:36:07 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 18:33:25 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 17:42:03 | 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; |
18-12-2022 17:40:05 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
18-12-2022 17:37:47 | 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; |
on 27-12-2022 11:31
Hi @sardine
We would need you to come out of modem mode please so we can run some checks on the service on our side.
Please let us know when you have done this and we can take a look for you.
Please pop back to us when you can.
Vikki - Forum Team
New around here? To find out more about the Community check out our Getting Started guide
on 27-12-2022 12:03
really!!
that would disabled every item in my home and take everyone offline.
on 29-12-2022 12:15
Unfortunately, sardine, if you're not able to go back into router mode, we are unable to perform further checks as we do not support 3rd party routers.
We fully understand if you do not want to do this, however this is the only way we can perform further checks for you.
Kind regards Jodi.
30-12-2022 00:16 - edited 30-12-2022 00:23
It would help to know what tests you can't do in modem mode? Or do you not know and just push a button to do a test?
A BQM would help show a problem.
Whats your download latency
Speedtest by Ookla - The Global Broadband Speed Test
on 30-12-2022 00:42
And by judging from the response times via this forum if i took the modem off modem mode were would Have no internet access to all our devices for 2 days
thats no ring cams
no ipads
no smart device controls
no xbox live
no netfilx
no access to online banks etc
all because you can’t talk to your own equipment with a feature that’s built in to enable 3rd party routers because yours cant handle the traffic over wifi or the amount of devices we have ( last count 48 )
this is ridiculous
you only need to talk to your equipment not mine
there is no need for you to have access to my equipment just talk to your modem I’ve been in modem mode for several years across 3 generations of modems and never once have i been asked to disable modem mode ever
on 30-12-2022 01:02
on 02-01-2023 09:41
Hi sardine, thanks for the message and welcome back to the forums.
I am sorry to hear that you are having an issue with the connection and this is not the experience which we want you to have.
I have looked at the connection and can see that you have not rebooted the hub for 15 days.
Would you be able to reboot and confirm if anything changes? ^Chris.
on 02-01-2023 13:31
Does the hub need to be rebooted on a regular basis? is this a VirginMedia hub thing? does it kind of slow down as i see the first thing tech support say is to restart as well.
on 04-01-2023 13:35
Absolutely - basically a reboot repairs connections and also, whilst your hub is online it stores data and a reboot help clears that.
Cheers,
Ryan.
on 19-01-2023 20:39
hi
keep getting strange 30 sec pauses could there be an issue ??
19-01-2023 20:35:48 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 20:35:48 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;
19-01-2023 20:35:23 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 20:35:23 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;
19-01-2023 20:34:59 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 20:34:59 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;
19-01-2023 20:03:14 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;
19-01-2023 20:03:14 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 20:02:50 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;
19-01-2023 20:02:50 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 20:02:25 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;
19-01-2023 20:02:25 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 19:31:52 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;
19-01-2023 19:31:52 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 19:31:27 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;
19-01-2023 19:31:27 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 19:31:03 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;
19-01-2023 19:31:03 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 19:00:29 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 19:00:29 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;
19-01-2023 19:00:05 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 19:00:05 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;
19-01-2023 18:59:41 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;
19-01-2023 18:59:41 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 18:28:47 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;
19-01-2023 18:28:47 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 18:28:23 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;
19-01-2023 18:28:23 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 18:27:59 notice US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 18:27:59 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;
19-01-2023 18:14:52 notice CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-01-2023 18:12:46 notice CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;