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

Forum Discussion

IcedTea's avatar
IcedTea
Aspirant
Apr 30, 2024

CAX30 Poor Cable Connection Status

Hi, I have Xfinitys Gig internet speed plan and recently purchased a CAX30S. The cable connection is poor and I've tried swapping out coax cables. According to the downstream status, it says Downstre...
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Apr 30, 2024

Please post a copy and paste of the modems event log page. This differs from the normal logs. Those are the router logs.

IcedTea's avatar
IcedTea
Aspirant
Apr 30, 2024

 oh sorry, I was on the wrong tab. Here is the event log

TimePriorityDescription
2024-04-30 15:11:14Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 15:10:58Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 15:02:27Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 15:02:21Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:43:05Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:42:51Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:48Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:31Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:24Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:19Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:19Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:41:16Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:40:59Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:40:58Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:30:52Critical (3)UCD invalid or channel unusable;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:22:29Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:56Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:48Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:46Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:33Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:21:32Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:57Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:53Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:52Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:52Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:20:37Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:19:51Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:19:42Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:19:31Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:33Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:26Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:15Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:15Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:18:12Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:59Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:42Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:21Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:17:15Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:16:55Warning (5)MDD message timeout;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
2024-04-30 14:16:08Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 32; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:41:f7:83;CMTS-MAC=00:90:f0:4f:0a:00;CM-QOS=1.1;CM-VER=3.1;
  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Apr 30, 2024

    Lots of warning entries. 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.

     

    Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
    Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
    Be sure your using good quality RG6 coax cable up to the modem. 
    Start with removing any amplifiers, signal attenuators, or splitters from the coax.
    From there check the line for kinks, damage, moisture in the line.
    Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
    Be sure to power OFF the modem for 1 minute then back ON.
    https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
    https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
    https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
    https://highspeed.tips/docsis-events/

    • IcedTea's avatar
      IcedTea
      Aspirant
      Apr 30, 2024

      I already purchased new coax cables and powered off my modem. I'll check in with my ISP about this now, thank you.

      • IcedTea's avatar
        IcedTea
        Aspirant
        May 01, 2024
        I talked to my isp and they said “your modem is not capable for the upgraded signals that is the bootfile is getting timed out”, they’re sending an xfinity modem because they said it’ll be compatible. If things go smoothly with the new modem then I’ll just return the CAX30S that I bought.