Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

T3 and T4 problem over 2 years now...

axel4ever
On our wavelength

on ‎06-02-2023 20:08

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

 

 

0 Kudos
24 REPLIES 24

Client62
Legend

‎07-02-2023 08:28 - edited ‎07-02-2023 08:29

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

0 Kudos

axel4ever
On our wavelength
In response to Client62

on ‎07-02-2023 17:09

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.

0 Kudos

axel4ever
On our wavelength
In response to Client62

on ‎07-02-2023 20:22

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.

 

0 Kudos

Matthew_ML
Forum Team
Forum Team

on ‎10-02-2023 08:04

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 

Matt - Forum Team


New around here?

0 Kudos

Andrew-G
Alessandro Volta
In response to axel4ever

on ‎10-02-2023 08:23

@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
On our wavelength
In response to Andrew-G

on ‎15-02-2023 16:38

@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:46noticeCM-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:50noticeCM-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:50noticeCM-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:53noticeCM-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:53noticeCM-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:54noticeCM-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:56warningRNG-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:56warningDynamic Range Window violation
15/02/2023 15:56warningDynamic Range Window violation
15/02/2023 15:56warningRNG-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:56warningDynamic Range Window violation
15/02/2023 15:56warningRNG-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:56warningRNG-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:56warningRNG-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:56warningDynamic Range Window violation
15/02/2023 15:56warningRNG-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:56warningDynamic Range Window violation
15/02/2023 15:58criticalStarted 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:58noticeCM-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:58criticalStarted 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:58noticeUS 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:58noticeCM-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:58noticeCM-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:59warningDynamic Range Window violation
15/02/2023 15:59warningRNG-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:01noticeCM-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:08noticeUS 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:14noticeCM-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:14noticeCM-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:15noticeCM-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:23noticeCM-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:25noticeCM-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.

0 Kudos

Andrew-G
Alessandro Volta
In response to axel4ever

on ‎15-02-2023 16:50

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
On our wavelength
In response to axel4ever

on ‎15-02-2023 16:57

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:25noticeCM-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:31noticeCM-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:33noticeCM-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:39noticeCM-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:41noticeCM-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:42noticeCM-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:44criticalStarted 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:46warningRNG-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:46criticalStarted 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:46noticeCM-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:46criticalStarted 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:50criticalReceived 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:50noticeHonoring MDD; IP provisioning mode = IPv4
15/02/2023 16:50warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50noticeDS 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:50noticeUS 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:50warningRNG-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:50warningDynamic Range Window violation
15/02/2023 16:50warningRNG-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:50warningRNG-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:50warningDynamic Range Window violation
15/02/2023 16:50warningRNG-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:50warningDynamic Range Window violation
15/02/2023 16:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:50warningDynamic Range Window violation
15/02/2023 16:50warningRNG-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:50warningDynamic Range Window violation
15/02/2023 16:51notice

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?

Picture1.pngPicture2.pngPicture3.png

 

Picture4.png

0 Kudos

axel4ever
On our wavelength
In response to axel4ever

on ‎15-02-2023 17:14

And again...

@Matthew_ML

Is there still an issue in my area?

 

15/02/2023 16:52warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
15/02/2023 16:52noticeCM-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:52noticeCM-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:52noticeUS 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:52noticeCM-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:54warningRNG-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:54criticalStarted 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:54warningDynamic Range Window violation
15/02/2023 16:54warningRNG-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:54warningRNG-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:56noticeCM-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:02noticeCM-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:02noticeUS 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:03noticeCM-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:05criticalStarted 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:06noticeCM-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:06criticalStarted 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:06warningRNG-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:06criticalStarted 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:08noticeUS 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:08noticeCM-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:11criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Top