Forum Discussion

jh0's avatar
jh0
Joining in
11 months ago

Gig1 HFC dropping out 5-10 times per day with T3 timeouts, timing sync failure

Starting last Sunday night (3rd June) I have been losing connectivity for about 3-10 minutes at a time, between 5-10 times a day with a bunch of T3 timeouts being the event seemingly kickstarting the timing synchronization failure leading to the whole Internet connection dropping. 

I have Gig1 HFC with a Hub5 (HW rev 1.1) in modem mode, in Area 14, and VM has been working well for the last 6 months, no changes to cables, configurations, everything as it was when installed 18 months ago behind a closed cupboard door. 

It may just be coincidence, but on Sunday night there was an update to the Hub 5 software (LG-RDK_7.6.20-2306.5) - which I noticed because the Hub had been taken out of modem mode and I woke up Monday morning to find this and it wouldn't let me select Modem mode again so had to do a pinhole reset in order to get it back into Modem mode (as the UI simply wouldn't allow me to switch it, even after rebooting.) 

Also, the Hub5 web admin UI stops responding as well as internal LAN pings during for a few minutes from about the time of the "SYNC Timing Synchronization failure - Loss of Sync" item in the log - maybe this is expected if it's doing a reset of it's network interfaces, but I found this interesting, not sure if others experience this also:

Any help would be greatly appreciated.

Full logs below:

Network Log

Time Priority Description
05-06-2024 17:33:10criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:31:56criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:31: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=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:31:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:31:32criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:31:32critical16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:30:49criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:30:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:30:24criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:30:09noticeCM-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;
05-06-2024 17:27:10noticeCM-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;
05-06-2024 17:24:49noticeCM-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;
05-06-2024 17:21:58noticeCM-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;
05-06-2024 17:19:42noticeCM-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;
05-06-2024 17:11:36noticeCM-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;
05-06-2024 17:08:47noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-06-2024 17:06:32noticeCM-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;
05-06-2024 17:05:43noticeCM-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;
 

8 Replies

Sort By
  • jh0's avatar
    jh0
    Joining in
    11 months ago

    Hub 5 device information

    The information below shows current status of this Hub 5.

    Standard specification compliant
    :
    DOCSIS 3.1
    Hardware version
    :
    1.1
    Software version
    :
    LG-RDK_7.6.20-2306.5
     

    Cable Modem StatusItem Status TypeChannel Overview Downstream Upstream

    Cable Modem StatusOnlineDOCSIS 3.0
    Primary downstream channelLockedSC-QAM
    DOCSIS 3.0 channels315
    DOCSIS 3.1 channels11

    3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
    1331000000-1.941QAM 25625
    2147000000240QAM 2562
    31550000001.940QAM 2563
    41630000001.740QAM 2564
    51710000001.440QAM 2565
    61790000001.240QAM 2566
    71870000001.140QAM 2567
    81950000001.140QAM 2568
    92030000000.840QAM 2569
    102110000000.639QAM 25610
    112190000000.539QAM 25611
    122270000000.339QAM 25612
    13235000000039QAM 25613
    142430000000.339QAM 25614
    152510000000.539QAM 25615
    162590000000.540QAM 25616
    172670000000.240QAM 25617
    182750000000.240QAM 25618
    192830000000.140QAM 25619
    202910000000.240QAM 25620
    212990000000.340QAM 25621
    223070000000.540QAM 25622
    233150000000.940QAM 25623
    24323000000-1.440QAM 25624
    25339000000-2.241QAM 25626
    26347000000-2.841QAM 25627
    27355000000-3.441QAM 25628
    28363000000-3.540QAM 25629
    29371000000-3.341QAM 25630
    30379000000-2.641QAM 25631
    31387000000-2.141QAM 25632

    3.0 Downstream channels

    Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
    1Locked416103286422
    2Locked4000
    3Locked4010
    4Locked4030
    5Locked4000
    6Locked4000
    7Locked4040
    8Locked40270
    9Locked40600
    10Locked392251
    11Locked3965622
    12Locked391290103
    13Locked392519367
    14Locked394500797
    15Locked3979961900
    16Locked40135394096
    17Locked40213938864
    18Locked403509021284
    19Locked405867048713
    20Locked4010516491700
    21Locked4014558665742
    22Locked404630547555
    23Locked40121754111613
    24Locked40169031106090
    25Locked4199087904
    26Locked4112640891550
    27Locked412970927596
    28Locked404197746375
    29Locked413026323023
    30Locked412395715157
    31Locked41156526810

    3.1 Downstream channels

    Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
    33944K1840QAM 40961108

    3.1 Downstream channels

    Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
    33Locked42-1.12345278794671

     

    3.0 Upstream channels

    Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
    04960000049.35120QAM 641
    143100000495120QAM 642
    236600000495120QAM 643
    33010000048.85120QAM 644
    42360000048.85120QAM 645

    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
    0ATDMA00180
    1ATDMA00180
    2ATDMA00180
    3ATDMA00180
    4ATDMA00180

    3.1 Upstream channels

    Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
    610.444.52KQAM 256

    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    6OFDMA20874000000180
     

    General Configuration

    Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
    Allowed
    3
    Enabled
    3.1
    cmreg-vmdg660-bbt076+voc-b.cm

    Primary Downstream Service Flow

    SFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
    37010
    1230000450 bps
    42600bytes
    0 bps
    37012
    128000 bps
    3044bytes
    0 bps

    Primary Upstream Service Flow

    SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
    37009
    110000274 bps
    42600bytes
    0 bps
    42600bytes
    Best Effort
    37011
    128000 bps
    3044bytes
    0 bps
    1522bytes
    Best Effort
    • jh0's avatar
      jh0
      Joining in
      11 months ago

      Another 8 dropouts since the previous post yesterday:

      Network Log

      Time Priority Description
      07-06-2024 10:05:24noticeCM-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;
      07-06-2024 10:05:24criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 10:05:18criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 10:05:01criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:31:14noticeCM-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;
      07-06-2024 09:30:25criticalReceived 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;
      07-06-2024 09:28:37noticeCM-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;
      07-06-2024 09:12:59noticeCM-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;
      07-06-2024 09:11:14noticeUS 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;
      07-06-2024 09:10:36criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:10: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=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:05:40criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:05:40critical16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:05:40criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:05:25critical16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:05:25criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:05:01criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:54criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:54criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:54critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:53noticeCM-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;
      07-06-2024 09:04:24critical16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:24criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:24criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:21criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:21criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:04:21critical16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:03:13criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:03:09critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:03:09criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:02:01criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      07-06-2024 09:00:47errorDBC-ACK not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      06-06-2024 15:33:09noticeGUI Login Status - Login Success from LAN interface
      • jh0's avatar
        jh0
        Joining in
        11 months ago

        And further to the last post an hour ago, a longer and slightly different outage just happened with some stuff in the log I've not seen before. The Hub5 web interface and pinging it was not possible during this time. 

        Any help would be greatly appreciated. 

        Network Log

        Time Priority Description
        07-06-2024 11:15:50noticeCM-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;
        07-06-2024 11:13:54noticeCM-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;
        07-06-2024 11:02:07noticeREGISTRATION COMPLETE - Waiting for Operational status
        07-06-2024 11:02:03noticeUS 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;
        07-06-2024 11:01:58noticeDS 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;
        07-06-2024 11:01:57noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 11:01:53warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 11:01:51noticeHonoring MDD; IP provisioning mode = IPv4
        07-06-2024 11:01:39warningToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 11:01:36criticalReceived 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;
        07-06-2024 10:57:53critical16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:53criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:53criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:51criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:50critical16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:50criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:42noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:57:42criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:55:41criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:55:19criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:55:17criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:55:17critical16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:54:52criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:54:46warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:54:46noticeUS 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;
        07-06-2024 10:54:42criticalReceived 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;
        07-06-2024 10:53:55criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:53:54criticalReceived 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;
        07-06-2024 10:53:45criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:53:27criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:53:27criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
        07-06-2024 10:53:27critical16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;