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

Forum Discussion

TrunkMonkey's avatar
Mar 10, 2022

Does the CM2050V have a a more stable upstream threshold than the CM1150V

I currently have the CM1150V for my Comcast Gig service (plus voice) but it's consistently given me problems where when the upstream signal reaches 48 dBmV, packet loss of 75% on average starts occuring just before it drops all traffic, then either recovers on it's own after a 10 minutes or as much as an hour after or I powercycle it to get it back to an immediate operational state.  Comcast's XB7 modem doesn't have this low upstream threshold problem but I don't need the "features" of the XB7, is the CM2050V more stable and reliable than the CM1150V?

 

 

4 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User

    48dbmv isn't that big a deal on the upstream. 

    But what helps us more is a full screen snip of the whole cable connections page and the event logs. That can help us check the line. What you can do in the mean time is. 

    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, bad/old/cheap connectors, or corroded connections. Replace them if you do.
    If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

  • This is the current event log and  signal page, but everything is working at the moment.  When the upstream LED goes dark (happens several times a day), I'm no longer able to log into the web interface to capture the logs.

     

    Currently, there is only one splitter and that is at the PoE, installed by Comcast, no amplifiers or other devices between the PoE and the cable modem except the coax in the wall.  

     

    Unfortunately, I work at home so moving the cable modem to directly connect to the splitter at PoE isn't possible and would take the rest of my network offline (e.g. firewall, router, switches, WAPs)

     

    TimePriorityDescription
    Thu Mar 10 12:55:31 2022Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:55:17 2022Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:55:16 2022Notice (6)TLV-11 - unrecognized OID;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:55:07 2022Notice (6)Honoring MDD; IP provisioning mode = IPv6
    Thu Mar 10 12:54:53 2022Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:54:52 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:52:57 2022Notice (6)CM-STATUS message sent. Event Type Code: 7; Chan ID: 5 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:52:54 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:52:27 2022Notice (6)CM-STATUS message sent. Event Type Code: 7; Chan ID: 5 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:52:26 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:51:56 2022Notice (6)CM-STATUS message sent. Event Type Code: 7; Chan ID: 5 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:51:47 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:51:26 2022Notice (6)CM-STATUS message sent. Event Type Code: 7; Chan ID: 5 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:51:25 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:56 2022Notice (6)CM-STATUS message sent. Event Type Code: 7; Chan ID: 5 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:55 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:53 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:53 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:53 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:53 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:47 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:46 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:41 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:41 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:38 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:38 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:37 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:37 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:37 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:26 2022Notice (6)CM-STATUS message sent. Event Type Code: 7; Chan ID: 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:21 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:13 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:11 2022Critical (3)No Ranging Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:08 2022Critical (3)16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:08 2022Critical (3)Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:50:08 2022Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:22:35 2022Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:22:20 2022Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:22:19 2022Notice (6)TLV-11 - unrecognized OID;CM-MAC=28:80:88:;CMTS-MAC=00:01:5c:;CM-QOS=1.1;CM-VER=3.1;
    Thu Mar 10 12:22:11 2022Notice (6)Honoring MDD; IP provisioning mode = IPv6
    • TrunkMonkey's avatar
      TrunkMonkey
      Tutor
      Startup Procedure
      ProcedureStatusComment
      Acquire Downstream Channel579000000 HzLocked
      Connectivity StateOKOperational
      Boot StateOKOperational
      SecurityEnabledBPI+
      IP Provisioning ModeHonor MDDhonorMdd(4)
       
      Downstream Bonded Channels
      ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
      1LockedQAM25632579000000 Hz-0.6 dBmV40.9 dB4156
      2LockedQAM2564405000000 Hz2 dBmV42.5 dB191162
      3LockedQAM2565411000000 Hz1.8 dBmV42.5 dB138231
      4LockedQAM2566417000000 Hz2.1 dBmV42.5 dB159105
      5LockedQAM2567423000000 Hz2 dBmV42.4 dB130170
      6LockedQAM2568429000000 Hz2.3 dBmV42.6 dB76111
      7LockedQAM2569435000000 Hz2 dBmV42.5 dB136174
      8LockedQAM25610441000000 Hz1.5 dBmV42.3 dB138124
      9LockedQAM25611447000000 Hz1.6 dBmV42.3 dB4089
      10LockedQAM25612453000000 Hz1.8 dBmV42.4 dB98195
      11LockedQAM25613459000000 Hz1.9 dBmV42.3 dB7178
      12LockedQAM25614465000000 Hz2 dBmV42.4 dB153138
      13LockedQAM25615471000000 Hz1.9 dBmV42.4 dB95124
      14LockedQAM25616477000000 Hz1.5 dBmV42.3 dB6453
      15LockedQAM25617483000000 Hz1.5 dBmV42.3 dB5189
      16LockedQAM25618489000000 Hz1.3 dBmV42.2 dB8587
      17LockedQAM25619495000000 Hz1.3 dBmV42.2 dB5093
      18LockedQAM25620507000000 Hz1.1 dBmV42.1 dB7185
      19LockedQAM25621513000000 Hz0.8 dBmV42 dB6243
      20LockedQAM25622519000000 Hz0.4 dBmV42 dB22113
      21LockedQAM25623525000000 Hz0 dBmV41.8 dB7578
      22LockedQAM25624531000000 Hz0.1 dBmV41.8 dB4875
      23LockedQAM25625537000000 Hz-0.1 dBmV41.8 dB6358
      24LockedQAM25626543000000 Hz-0.4 dBmV41.6 dB4874
      25LockedQAM25627549000000 Hz-0.5 dBmV41.5 dB5753
      26LockedQAM25628555000000 Hz-0.6 dBmV41.3 dB5644
      27LockedQAM25629561000000 Hz-0.7 dBmV41.3 dB5777
      28LockedQAM25630567000000 Hz-0.8 dBmV41.2 dB5860
      29LockedQAM25631573000000 Hz-0.9 dBmV40.7 dB3729
      30LockedQAM25633585000000 Hz-0.1 dBmV41.3 dB3547
      31LockedQAM25634591000000 Hz0 dBmV41.3 dB4351
      32Not LockedUnknown00 Hz0.0 dBmV0.0 dB00
       
      Upstream Bonded Channels
      ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
      1LockedATDMA55120 Ksym/sec16400000 Hz41 dBmV
      2LockedATDMA65120 Ksym/sec22800000 Hz40.5 dBmV
      3LockedATDMA75120 Ksym/sec29200000 Hz40.8 dBmV
      4LockedATDMA85120 Ksym/sec35600000 Hz41 dBmV
      5Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
      6Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
      7Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
      8Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
       
      Downstream OFDM Channels
      ChannelLock
      Status
      Modulation /
      Profile ID
      Channel
      ID
      FrequencyPowerSNR /
      MER
      Active Subcarrier
      Number Range
      Unerrored
      Codewords
      Correctable
      Codewords
      Uncorrectable
      Codewords
      1Locked0 ,1 ,2 ,348850000000 Hz1.1 dBmV40.9 dB1108 ~ 2987588231347148880153350
      2Not Locked000 Hz0 dBmV0.0 dB0 ~ 4095000
       
      Upstream OFDMA Channels
      ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
      1Not Locked000 Hz0 dBmV
      2Not Locked000 Hz0 dBmV
    • plemans's avatar
      plemans
      Guru - Experienced User

      POE-power over ethernet. 

      Why is your coax powered? 

      Your logs are indicating a lot of signal issue. 

      But you didn't include your cable connections page. But from the logs, you have line issues.