NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

ijerez's avatar
ijerez
Aspirant
Nov 09, 2024

CM30000 Conn drop -Started Unicast Maintenance Ranging - No Response received

Hi 
I am getting the drop intermetly drop from comcast.

They have check and replaced the following:
Cables outside.
Checked inside cable
The latest firmware

The device started intermittently dropping after a few weeks.

I attached the logs. They claim it's the device and I a stuck between Netgear and the carrier.

I have attached the logs. Can you please assist and let me know if it's truly the device?

Thank

Here is the log info:

Friday it dropped again and the Saturday logs are from Comcast trying to verify if the problem was on their end.

Sat Nov 09 10:25:12 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Warning (5))Dynamic Range Window violation
Sat Nov 09 09:44:34 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Warning (5))Dynamic Range Window violation
Sat Nov 09 09:44:34 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Warning (5))Dynamic Range Window violation
Sat Nov 09 09:44:34 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Warning (5))Dynamic Range Window violation
Sat Nov 09 09:44:34 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Warning (5))Dynamic Range Window violation
Sat Nov 09 09:44:34 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Warning (5))Dynamic Range Window violation
Sat Nov 09 09:44:34 2024(Warning (5))RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 09:44:34 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 08:57:45 2024(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 08:57:40 2024(Notice (6))TLV-11 - unrecognized OID;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Nov 09 08:56:18 2024(Critical (3))Resetting the cable modem due to docsDevResetNow
Fri Nov 08 13:09:27 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:09 2024(Critical (3))16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:09 2024(Critical (3))Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:09 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:09 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:07 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:02 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:09:02 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:51 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:33 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:21 2024(Critical (3))16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:21 2024(Critical (3))Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:21 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:20 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:20 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:19 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:18 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:18 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:17 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 08 13:08:10 2024(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;

 

7 Replies

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Nov 09, 2024

    Please post a copy and paste of the modems connection status page.
    https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router

    Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.
    Be sure your using a good quality LAN cable between the modem and router. CAT6A STP  is recommended. 
    What is the brand and model of the host wifi router connected to the modem? 

    • ijerez's avatar
      ijerez
      Aspirant
      Nov 09, 2024

      It's a CM3000. 
      Comcast put a new line out from the house. They tested that line as well.

      I've gone over it with Comcast.

      Not sure what other action I can do between Netgear and Comast.

      • ijerez's avatar
        ijerez
        Aspirant
        Nov 09, 2024

        Cable Diagnostic

        Status: Good

        Action:
        Your setup looks fine. If you can't access the internet, make sure you properly activated the modem. If modem has been activated and you still can't access the internet, contact your service provider for troubleshooting help.
        If you can access the internet but has other internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.

        CM Status: Good

        Downstream Status: Good

        Downstream Power Level: Good

        Downstream SNR Level: Good

        Upstream Status: Good

        Upstream Power Level: Good


        Current Time: Sat Nov 09 14:51:44 2024

        Startup Procedure
        Acquire Downstream Channel: 459000000 Hz Locked
        Connectivity State: OK Operational
        Boot State: OK Operational
        Security: Enabled BPI+
        IP Provisioning Mode: Honor MDD IPv6 only


        Downstream Bonded Channels
        Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
        1 Locked QAM256 20 459000000 Hz 3.3 38.6 13838 29578
        2 Locked QAM256 17 441000000 Hz 3.3 38.5 13013 29232
        3 Locked QAM256 18 447000000 Hz 3.3 38.5 12938 29685
        4 Locked QAM256 19 453000000 Hz 3.4 38.7 13002 28925
        5 Locked QAM256 21 465000000 Hz 3.2 38.5 13049 29106
        6 Locked QAM256 22 471000000 Hz 3.2 38.5 13124 29892
        7 Locked QAM256 23 477000000 Hz 3.3 38.6 13374 29434
        8 Locked QAM256 24 483000000 Hz 3.2 38.5 2401 4841
        9 Locked QAM256 25 489000000 Hz 3.2 38.5 13301 29800
        10 Locked QAM256 26 495000000 Hz 3.4 38.7 13442 29498
        11 Locked QAM256 27 501000000 Hz 3.2 38.8 13607 29170
        12 Locked QAM256 28 507000000 Hz 3.3 38.8 13578 29538
        13 Locked QAM256 29 513000000 Hz 3.1 38.8 13779 30146
        14 Locked QAM256 30 519000000 Hz 3.2 38.7 13644 29758
        15 Locked QAM256 31 525000000 Hz 3.1 38.7 13450 30094
        16 Locked QAM256 32 531000000 Hz 3.3 38.9 13787 29968
        17 Locked QAM256 33 537000000 Hz 3.4 39 14157 29676
        18 Locked QAM256 34 543000000 Hz 3.2 38.9 14126 31084
        19 Locked QAM256 35 549000000 Hz 3.1 38.9 14169 30054
        20 Locked QAM256 36 555000000 Hz 2.9 38.9 14332 30203
        21 Locked QAM256 37 561000000 Hz 2.9 39 14228 30035
        22 Locked QAM256 38 567000000 Hz 2.9 39 14288 29910
        23 Locked QAM256 39 573000000 Hz 3 39.1 14489 29660
        24 Locked QAM256 40 579000000 Hz 3.1 39.1 14383 30556
        25 Locked QAM256 41 585000000 Hz 3.3 39.2 14676 29277
        26 Locked QAM256 42 591000000 Hz 3.3 39.1 14634 29887
        27 Locked QAM256 43 597000000 Hz 3.3 39.1 14549 30592
        28 Locked QAM256 44 603000000 Hz 3.4 39.1 14539 29741
        29 Locked QAM256 45 609000000 Hz 3.7 39.3 14543 30159
        30 Locked QAM256 46 615000000 Hz 3.7 39.4 14345 30550
        31 Locked QAM256 47 621000000 Hz 3.9 39.5 14621 29246
        32 Not Locked Unknown 0 0 Hz 0.0 0.0 0 0

        Upstream Bonded Channels
        Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
        1 Locked ATDMA 11 2560 Ksym/sec 40400000 Hz 42.5 dBmV
        2 Locked ATDMA 1 2560 Ksym/sec 10400000 Hz 40.3 dBmV
        3 Locked ATDMA 2 5120 Ksym/sec 16400000 Hz 40.5 dBmV
        4 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 41.0 dBmV
        5 Locked ATDMA 4 5120 Ksym/sec 29200000 Hz 41.5 dBmV
        6 Locked ATDMA 5 5120 Ksym/sec 35600000 Hz 41.5 dBmV
        7 Not Locked Unknown 0 0 0 0.0
        8 Not Locked Unknown 0 0 0 0.0

        Downstream OFDM Channels
        Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
        1 Locked 0 ,1 ,2 ,3 48 685000000 Hz 4.38 dBmV 39.2 dB 988 ~ 3107 772892940 733973804 8089
        2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0

        Upstream OFDMA Channels
        Channel LockedStatus ProfileID ChannelID Frequency Power
        1 Not Locked 0 0 0 Hz 0 dBmV
        2 Not Locked 0 0 0 Hz 0 dBmV

        Event Log
        Time Priority Description
        Sat Nov 09 14:43:08 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:43:07 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:58 2024 Notice (6) Honoring MDD; IP provisioning mode = IPv6
        Sat Nov 09 14:42:49 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:39 2024 Warning (5) ToD request sent - No Response received;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:39 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:39 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:39 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:35 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:34 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:27 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:10 2024 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 4 5 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:09 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:03 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 5;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:03 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:03 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:03 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:01 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:01 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:01 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:42:01 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:52 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:40 2024 Notice (6) CM-STATUS message sent. Event Type Code: 7; Chan ID: 1 2 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:33 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:29 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:29 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:29 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:28 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:27 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:26 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:26 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:26 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:25 2024 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:25 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:24 2024 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:24 2024 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:41:24 2024 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:09:19 2024 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:07:30 2024 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 1 2 5 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;
        Sat Nov 09 14:06:43 2024 Notice (6) CM-STATUS message sent. Event Type Code: 8; Chan ID: 1 2 5; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:01:45:e8;CMTS-MAC=00:01:5c:63:12:5e;CM-QOS=1.1;CM-VER=3.1;

         

         

        I have RAX45 router but I have seen the middle light on the cable modem flash right when it dropped.

  • plemans's avatar
    plemans
    Guru - Experienced User
    Nov 10, 2024

    Your logs are still indicating line issues. The dynamic range window violation is the power level going out of spec. And you've got other errors indicative of line issues. It can get complicated with line issues. And replacing the line doesn't always fix the issue as it could be a hub, loose connector at the pole, etc. You can read through this users difficulty with it. 

    https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

     

    What I've done and seen users do is rent the xfinity modem for a month. its like $15 or something. If it has issues, it means they can't blame your "third party modem". So that only leaves the line/hub/connections. And puts them responsible for fixing it. If it does fix the problem, its proof the cm3000 has issues 

    • ijerez's avatar
      ijerez
      Aspirant
      Nov 10, 2024

      Thanks!

      I'm returning the modem since today it my last day to return it back to Amazon.

      I going to do just that. Rent a modem and/or see if I can switch to ATT as a backup plan.

      Line drops I can't deal with for long. They replaced the line and had someone came out again to confirm it and run tests.

      Thanks for all your help and prompt response!