Virgin Media Community

[axel4ever]

Hi There,

I'm looking for some support, as this takes way too long.

I had my router replaced twice, every engineer was tweaking power levels back and forth saying that they a right. All connectors and filters replaced. Recently (December 21st) I had new cable ran to my house and today cabling inside replaced.

The long story short, problem is still here, and nobody know what to do...

I have started logging the router data and some screenshots of the upload and download tabs.

Download link https://we.tl/t-tqOMQmYmMq

1 item

T3-T4_log.xlsx 3.15 MB

[Client62]

Hmm ... a 1st Post with a WeTransfer payload

[axel4ever]

Do what you want...

Excel spreadsheet got no macros enabled to deploy anything.

I'm not aware of any 0 day exploits ATM.

You can download and open this using any VM if you suspect anything malicious.

I came here for help.

I can paste 2219 lines of data here if you want?

But it will be difficult to match it with the screenshots i took during the issue.

[axel4ever]

So... Mr. Client 62.

Would you like me to video stream this data over the Discord or maybe via other means?

I'm open for your suggestions, as you dropped the bomb accusing me of being the bad actor.

[Matthew_ML]

Hey axel4ever, thank you for reaching out and I am sorry to hear you are having some connection problems.

I have taken a look at my side and I can see there is a short term connection issue.

This is due to last 24 hours if there isn't an improvement this time tomorrow, please can you give us a message back. Thanks 

[Andrew-G]

---

@axel4ever wrote:

Do what you want...

Excel spreadsheet got no macros enabled to deploy anything.

I'm not aware of any 0 day exploits ATM.

You can download and open this using any VM if you suspect anything malicious.

I came here for help.

I can paste 2219 lines of data here if you want?

But it will be difficult to match it with the screenshots i took during the issue.

---

The problem is that the people who can help here are tech savvy, and we're suspicious of third party links to documents.  Like Client62, I saw your post and decided I wasn't clicking on the link.  I'd hope that VM's systems are sufficiently well set up that their staff can't download that sort of document.  Why not just paste some sample data (not the lot, it'll be too long) as a table in a post here?

You'll note that the forum staff haven't addressed the two years of poor connection, they've fobbed you off with something about a short term area fault.  A fault of this duration with T3 and 4 faults would (at first guess) imply to me a faulty drop cable, which would need a re-pull from cabinet to house.  If you have got the data recorded, and you've made attempts before to get this resolved, then it's (well past) time to make a formal complaint to VM, asking for compensation for the persistently poor connection (say perhaps 30% of bills over the period in question), a sum to reflect the failure to own, acknowledge and resolve the problem over a period of months or years (say £200), and for VM to assign a senior technician to investigate and resolve the fault.

The complaint will be fobbed off, but then you take the matter to Ombudsman Services who will impose a settlement on VM.  Note that you'll need to explain how the recorded faults affect you and the quality of your connection.  Ombudsman Services have only recently taken on VM, they won't yet be familiar with the problems of VM's cable technology, so simply referring to T3 & T4 faults alone may not explain to them why there is a problem.

[axel4ever]

@Andrew-G

Thank you for coming back to me, this is much appreciated.

I will most likely follow your advice, as this issue is present multiple times a day.

@Matthew_ML

As I previously stated problem is over 2 years old...

check todays log sample below...

15/02/2023 15:46	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:50	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:50	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:53	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:53	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:54	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	Dynamic Range Window violation
15/02/2023 15:56	warning	Dynamic Range Window violation
15/02/2023 15:56	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	Dynamic Range Window violation
15/02/2023 15:56	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	Dynamic Range Window violation
15/02/2023 15:56	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:56	warning	Dynamic Range Window violation
15/02/2023 15:58	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:58	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:58	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:58	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:58	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:58	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 15:59	warning	Dynamic Range Window violation
15/02/2023 15:59	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:01	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:08	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:14	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:14	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:15	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:23	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:25	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;

I also have screen shots of the signal levels during the incident.

I'm really frustrated at this point and very close to taking this to social media and further.

[Andrew-G]

I'm really frustrated at this point and very close to taking this to social media and further.

Unfortunately there's more than a few moans on social media about VM, so that's very unlikely to create any additional pressure.  If you hope that VM take notice of customer feedback, then take a look at VM's entry on Trustpilot.

Your options are to accept it for what it is (ie not very good), to use the complaint and adjudication channel and hope that works (it might, but we may be talking a couple of months or more), or to take your business elsewhere.  

[axel4ever]

And it happened just after posted the previous one...

I guess today is one of those days where it will fck about every 30min or so...

New log from where I left off last time:

15/02/2023 16:25	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=00:01XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:31	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:33	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; 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;
15/02/2023 16:39	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; 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;
15/02/2023 16:41	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:42	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; 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;
15/02/2023 16:44	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:46	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:46	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:46	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; 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;
15/02/2023 16:46	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	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.1;
15/02/2023 16:50	notice	Honoring MDD; IP provisioning mode = IPv4
15/02/2023 16:50	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	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;
15/02/2023 16:50	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;
15/02/2023 16:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	warning	Dynamic Range Window violation
15/02/2023 16:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	warning	Dynamic Range Window violation
15/02/2023 16:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	warning	Dynamic Range Window violation
15/02/2023 16:50	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	warning	Dynamic Range Window violation
15/02/2023 16:50	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50	warning	Dynamic Range Window violation
15/02/2023 16:51	notice	REGISTRATION COMPLETE - Waiting for Operational status

As previously said, I got much, much more of this in way friendlier format if anyone would like to see that.

If so, please advise on the way of sharing it?

[axel4ever]

And again...

@Matthew_ML

Is there still an issue in my area?

15/02/2023 16:52	warning	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:52	notice	CM-STATUS message sent. Event Type Code: 4; Chan ID: 31; 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;
15/02/2023 16:52	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; 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;
15/02/2023 16:52	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;
15/02/2023 16:52	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:54	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:54	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:54	warning	Dynamic Range Window violation
15/02/2023 16:54	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;
15/02/2023 16:54	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:56	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:02	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:02	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:03	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; 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;
15/02/2023 17:05	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:06	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; 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;
15/02/2023 17:06	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:06	warning	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:06	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:08	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;
15/02/2023 17:08	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 17:11	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;