Forum Discussion

Alex_gregory_uk's avatar
Alex_gregory_uk
On our wavelength
2 months ago

CM-STATUS message sent. Event Type Code: 24 and 16

The Network Log of my Hub 5 has been filled with these notices and warnings over the past week. I am on 1GB which has been running fine but only seeing around 500mb for the last week. Whilst I don't appear to be losing my internet connection, I am noticing that particular devices are constantly being kicked off my Wi-Fi and having connection issues briefly over Ethernet. There don't seem to be any known issues in my area. I run my Hub 5 in Modem only mode. 

Information from my hub:

Primary Downstream Service Flow

SFID81394
Max Traffic Rate1230000450 bps
Max Traffic Burst42600bytes
Min Traffic Rate0 bps

Primary Upstream Service Flow

SFID81393
Max Traffic Rate110000274 bps
Max Traffic Burst42600bytes
Min Traffic Rate0 bps
Max Concatenated Burst42600bytes
Scheduling TypeBest Effort

Network Log:

Time  PriorityDescription
23-07-2025 16:36: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-M
23-07-2025 16:36:25notice 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=20:b8:2b:4a:87:be;CM
23-07-2025 16:36:13notice GUI Login Status - Login Success from LAN interface
23-07-2025 16:35:29notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-M
23-07-2025 16:33:07notice 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=2
23-07-2025 16:32:42notice 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=20:b8:2b:4a:87:be;CMTS-MAC=00:01:5c:73:3c:bd;CM-QOS=1.1;CM-VER=3.1;
23-07-2025 16:30:23notice 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
23-07-2025 16:28:23notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=20
23-07-2025 16:23:53notice 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=
23-07-2025 16:19:47notice 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=2
23-07-2025 16:16:53notice 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=2
23-07-2025 16:09:40notice 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=20
23-07-2025 16:06:31notice 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=20:
23-07-2025 16:05:07notice 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=20
23-07-2025 15:58:47notice 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=2
23-07-2025 15:38:03notice 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=2
23-07-2025 15:32:34notice 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=2
23-07-2025 15:32:28notice  US profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM-MAC=20:b8:2b:4a:87:be;CMTS-MAC=0
23-07-2025 15:29:45notice 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=20
23-07-2025 15:29:13notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC
23-07-2025 15:22:49notice 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=20:
23-07-2025 15:22:08notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=20:
23-07-2025 15:17:29notice 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=20
23-07-2025 15:14:34notice 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=20:
23-07-2025 15:00:33notice 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=20:b
23-07-2025 14:48:30notice 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=2
23-07-2025 14:46:27notice 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=20
23-07-2025 14:28:38notice US profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;CM-MAC=20:b8:2b:4a:87:be;CMTS-MAC=00:0
23-07-2025 13:39:25notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC
23-07-2025 13:38:52notice 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=20
23-07-2025 13:08:23notice 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=2
23-07-2025 12:20:19notice 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=20
23-07-2025 12:10:20notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=20:b

   [Mod - MACS removed]

21 Replies

  • legacy1's avatar
    legacy1
    Alessandro Volta

    Connect a PC to the hub in modem mode and test your speed power off hub for 2mins when you make the change over.

    your Max Traffic Rate is correct for 1Gb

  • Thanks for sharing — I’ve been seeing the same Event Type 24 (Ranging Request Retries Exhausted) and 16 (Loss of Sync; retries exhausted) in my logs too. These usually point to upstream signal or sync issues.

  • I am now seeing the following errors:

    29-07-2025 09:02:44noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;[REMOVED]
    29-07-2025 06:12:09errorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
    29-07-2025 04:47:29noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;[REMOVED]
    29-07-2025 03:43:41noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    29-07-2025 02:39:52noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    29-07-2025 00:32:16noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13;[REMOVED]
    28-07-2025 22:24:39noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    28-07-2025 21:20:50noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    28-07-2025 20:17:01noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    28-07-2025 14:48:18noticeGUI Login Status - Login Success from LAN interface
    28-07-2025 09:38:57noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    28-07-2025 08:35:08noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13;[REMOVED]
    28-07-2025 08:12:48noticeGUI Login Status - Login Success from LAN interface
    28-07-2025 07:31:19noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    28-07-2025 05:23:42noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    28-07-2025 04:19:53noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    28-07-2025 03:16:05noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13;[REMOVED]
    28-07-2025 02:12:16noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    27-07-2025 23:00:50noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13;[REMOVED]
    27-07-2025 22:55:01noticeGUI Login Status - Login Success from LAN interface
    27-07-2025 08:07:28noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    27-07-2025 05:59:51noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    27-07-2025 04:56:02noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13;[REMOVED]
    27-07-2025 02:48:25noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    26-07-2025 23:37:00noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    26-07-2025 09:47:27noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    26-07-2025 07:39:50noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; [REMOVED]
    26-07-2025 00:13:10noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; [REMOVED]
    25-07-2025 18:12:08errorDHCP RENEW WARNING - Field invalid in response v4 option;[REMOVED]
    25-07-2025 10:28:42noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 11 13;[REMOVED]
    25-07-2025 10:28:37noticeREGISTRATION COMPLETE - Waiting for Operational status
    25-07-2025 10:28:32warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;[REMOVED]
    25-07-2025 10:28:25noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; [REMOVED]
    25-07-2025 10:28:21noticeTLV-11 - unrecognized OID;[REMOVED]
    25-07-2025 10:28:19warningDHCP WARNING - Non-critical field invalid in response ;[REMOVED]
    • Tudor's avatar
      Tudor
      Very Insightful Person

      I get them all the time and it’s does not affect the service. They are only ‘Notice’ messages and can be safely ignored.

      • Nednats's avatar
        Nednats
        Joining in

        If you’re seeing alternating CM‑STATUS message sent: Event Type Code 16 and 24 entries in your Hub 5 network log. Here's what those codes mean and what they usually indicate:

        • Event Type Code 16: Loss of Sync — this happens when your modem’s OFDM (DOCSIS 3.1) downstream profile fails or is lost. Often triggered by issues in demodulating the signal.

        • Event Type Code 24: Profile Recovery — this shows the modem successfully re‑establishing the OFDM downstream channel after a failure.

          In short, your modem is losing and then regaining its downstream profile repeatedly—sometimes very rapidly—as these codes alternate. Other users have been seeing similar patterns.

         

        This behaviour is generally associated with:

        • High noise or ingress on the fibre/coax network (e.g., interference, water ingress, degraded cables).

        • Signal level issues—commonly too‐high downstream power or poor SNR.



         

        Sometimes the logs also include dynamic range violations or T3 time‑outs, both of which suggest upstream/downstream channel instability or poor line quality.

  • Adduxi's avatar
    Adduxi
    Very Insightful Person

    Please post ALL the power level stats from the Hub.  This is needed to get a full picture of your incoming circuit.  Also setup a BQM here  http://www.thinkbroadband.com/ping

    What is the make and model of your 3rd party Router?

    Note VM will request you to put the Hub back to Router mode before they can run tests.

    • Alex_gregory_uk's avatar
      Alex_gregory_uk
      On our wavelength

      3.0 Downstream channels

      Channel

      Frequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
      13060000005.539QAM 25622
      21460000007.940QAM 2562
      31540000007.740QAM 2563
      41620000007.740QAM 2564
      51700000007.740QAM 2565
      61780000007.640QAM 2566
      71860000007.440QAM 2567
      81940000007.340QAM 2568
      92020000006.939QAM 2569
      102100000006.439QAM 25610
      112180000005.339QAM 25611
      122260000004.639QAM 25612
      132340000004.839QAM 25613
      142420000004.939QAM 25614
      152500000004.939QAM 25615
      162580000004.839QAM 25616
      172660000004.839QAM 25617
      182740000004.839QAM 25618
      192820000004.839QAM 25619
      202900000005.139QAM 25620
      212980000005.240QAM 25621
      223140000005.940QAM 25623
      233220000006.240QAM 25624
      24330000000640QAM 25625
      253380000005.840QAM 25626
      263460000005.340QAM 25627
      273540000004.640QAM 25628
      283620000004.340QAM 25629
      293700000004.240QAM 25630
      303780000004.440QAM 25631
      31386000000440QAM 25632


      3.0 Downstream channels

      Channel

      Locked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
      1Locked39290
      2Locked40120
      3Locked40150
      4Locked40100
      5Locked4080
      6Locked40110
      7Locked40110
      8Locked40100
      9Locked39100
      10Locked39110
      11Locked39330
      12Locked39340
      13Locked39360
      14Locked39310
      15Locked39310
      16Locked39220
      17Locked39200
      18Locked39300
      19Locked39190
      20Locked39390
      21Locked40280
      22Locked40270
      23Locked40300
      24Locked40260
      25Locked40300
      26Locked40300
      27Locked40430
      28Locked40590
      29Locked40590
      30Locked40790
      31Locked401490

      3.1 Downstream channels

      ChannelChannel Width (MHz)FFT TypeNumber of Active SubcarriersModulation (Active Profile)First Active Subcarrier (Hz)
      33944K1840QAM 40961108

      3.1 Downstream channels

      Channel IDLocked StatusRxMER Data (dB)PLC Power (dBmV)Corrected errors (Active Profile)Uncorrectable errors (Active Profile)
      33Locked39-3379711123719626
    • Alex_gregory_uk's avatar
      Alex_gregory_uk
      On our wavelength

      3.0 Upstream channels

      Channel

      Frequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
      04960000043.35120QAM 165
      143100000435120QAM 166
      23660000042.85120QAM 167
      33010000042.55120QAM 168
      42360000042.55120QAM 1611

      3.0 Upstream channels

      Channel

      Channel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
      0ATDMA0000
      1ATDMA0000
      2ATDMA0000
      3ATDMA0010
      4ATDMA0000

      3.1 Upstream channels

      ChannelChannel Width (MHz)Power (dBmV)FFT TypeModulation
      1210.438.22KQAM 256

      3.1 Upstream channels

      ChannelChannel TypeNumber of Active SubcarriersFirst Active Subcarrier (Hz)T3 TimeoutsT4 Timeouts
      12OFDMA2087400000000

       

    • Alex_gregory_uk's avatar
      Alex_gregory_uk
      On our wavelength

      This is for the last 24 hours with the following from the network log:


      TimePriorityDescription
      01/08/2025 19:42noticeGUI Login Status - Login Success from LAN interface
      01/08/2025 18:12  
      01/08/2025 16:46noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-QOS=1.1;CM-VER=3.1;
      01/08/2025 16:44noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=20:
      01/08/2025 10:23noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 13.;CM
      01/08/2025 09:19noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New Profile: 13.;C
      01/08/2025 07:12noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 13; New Profile: 12 1
      01/08/2025 01:52noticeUS profile assignment change. US Chan ID: 12; Previous Profile: 12 13; New P

      [Mod - MACS removed for security]

       

  • Adduxi's avatar
    Adduxi
    Very Insightful Person

    Your Upstream should all be QAM64.  That's a problem for VM to fix.  The rest of the power levels look to be in spec and having no Downstream PostRS errrors is also a good thing. 

    • Alex_gregory_uk's avatar
      Alex_gregory_uk
      On our wavelength

      Upstreams are now showing as QAM64 except in this section:

      ChannelChannel Width (MHz)Power (dBmV)FFT TypeModulation
      1210.438.02KQAM 256
      • Adduxi's avatar
        Adduxi
        Very Insightful Person

        That's okay as it's the 3.1 US channel, it's the 3.0 US channels that should be 64 QAM. 

  • Client62's avatar
    Client62
    Alessandro Volta

    Have you checked the internal coax cable are all secure on all the VM kit and wall sockets ?

    Note the 3.1 Downstream has hard errors reported in the right hand column, 
    monitor if that number is still increasing, it is another sign of noise ingress.

    3.1 Downstream channels

    Channel IDLocked StatusRxMER Data (dB)PLC Power (dBmV)Corrected errors (Active Profile)Uncorrectable errors (Active Profile)
    33Locked39-3379711123719626
    • Alex_gregory_uk's avatar
      Alex_gregory_uk
      On our wavelength

      Thanks for this. I'll double check all connections.

      I've had a look and hard errors appear to be still going up.

      Channel IDLocked StatusRxMER Data (dB)PLC Power (dBmV)Corrected errors (Active Profile)Uncorrectable errors (Active Profile)
      33Locked39-3.06701450142263
  • Just to keep this thread updated to help anyone else out in future...

    An engineer visited on Thursday morning. He ran a test and the levels weren't great so he changed the old internal wiring and plugs on the end of the wires in the external box. He ran another test on the line which still weren't great so he went to the box in the street to boost the power. He came back to say it was already on maximum so would request a new line is pulled through from the box to the house. He advised that it would be one to two weeks as the internet was still working which was fine by me.

    I left home for a long weekend on Friday morning when I received a phonecall at 12.24 from a guy to say he was outside my house to fix Virgin. He said he was going to pull a new line through and could do it all externally that he would get it sorted. It got to 5pm and hadn't heard anything so tried ringing the mobile number back but it rang through to his voicemail saying to contact OCU. I phoned the help desk who found my details and it said that work was due to start on the 3rd August (not possible since the initial engineer only came out on the 7th) and work was due to be completed by the 12th August. No notes on what was going on though. The call centre took my details and was going to investigate and call me back last night and if he had no update I should receive a call on Monday.

    I know I'm still not online as my CCTV is offline, my Broadband Quality Monitor is showing offline and my modem is offline. I therefore called my neighbour who updated me that the engineers had a problem as he's spoken to them. He said they tried to pull the cable through but there's a blockage and the cable snapped. He said further engineers were due to come out either Saturday or Monday.

    I understand these things happen and it's not the end of the world, especially since I'm away for the weekend. Just a shame OCU haven't contacted me or updated me about this problem.

    I'm also slightly annoyed noone contacted me to advise me they were coming in the first place. The original engineer suggested when the work was going to be done that it would be good to move the car away from the wall box on the house which I'd have happily done if I'd known the engineers were coming but it will have been in there way I'm sure. Sadly noone can move it till I'm back on Monday afternoon.

    Anyway, just thought I'd update the thread that Virgin have been very efficient, the first engineer was really good and explained everything. Just feel a little let down by lack of contact from the contractor, OCU. I'll update this further as I get more info and fingers crossed for a better line at the end of all this!!!

  • Just a further update. I've returned home today with no internet / TV as the cable is still damaged. Still had no contact from anyone at Virgin or OCU group who cut us off. I've wasted an hour trying to speak to Virgin for someone to finally tell me on webchat that it's logged and booked for an engineer visit on the 14th. Really frustrated with how this has turned out and the lack of contact.

    • Matthew_ML's avatar
      Matthew_ML
      Icon for Forum Team rankForum Team

      Hey Alex_greory-uk, thank you for reaching out and we are so sorry to hear about this damaged cable.

      We can see you are currently in DM with my colleague please do go back to this if you need any further information.