NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 occur...
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)
| Time | Priority | Description |
| Thu Mar 10 12:55:31 2022 | Notice (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 2022 | Notice (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 2022 | Notice (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 2022 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
| Thu Mar 10 12:54:53 2022 | Critical (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 2022 | Critical (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 2022 | Notice (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 2022 | Critical (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 2022 | Notice (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 2022 | Critical (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 2022 | Notice (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 2022 | Critical (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 2022 | Notice (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 2022 | Critical (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 2022 | Notice (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Notice (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Critical (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 2022 | Notice (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 2022 | Notice (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 2022 | Notice (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 2022 | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Startup Procedure Procedure Status Comment Acquire Downstream Channel 579000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD honorMdd(4) Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 32 579000000 Hz -0.6 dBmV 40.9 dB 41 56 2 Locked QAM256 4 405000000 Hz 2 dBmV 42.5 dB 191 162 3 Locked QAM256 5 411000000 Hz 1.8 dBmV 42.5 dB 138 231 4 Locked QAM256 6 417000000 Hz 2.1 dBmV 42.5 dB 159 105 5 Locked QAM256 7 423000000 Hz 2 dBmV 42.4 dB 130 170 6 Locked QAM256 8 429000000 Hz 2.3 dBmV 42.6 dB 76 111 7 Locked QAM256 9 435000000 Hz 2 dBmV 42.5 dB 136 174 8 Locked QAM256 10 441000000 Hz 1.5 dBmV 42.3 dB 138 124 9 Locked QAM256 11 447000000 Hz 1.6 dBmV 42.3 dB 40 89 10 Locked QAM256 12 453000000 Hz 1.8 dBmV 42.4 dB 98 195 11 Locked QAM256 13 459000000 Hz 1.9 dBmV 42.3 dB 71 78 12 Locked QAM256 14 465000000 Hz 2 dBmV 42.4 dB 153 138 13 Locked QAM256 15 471000000 Hz 1.9 dBmV 42.4 dB 95 124 14 Locked QAM256 16 477000000 Hz 1.5 dBmV 42.3 dB 64 53 15 Locked QAM256 17 483000000 Hz 1.5 dBmV 42.3 dB 51 89 16 Locked QAM256 18 489000000 Hz 1.3 dBmV 42.2 dB 85 87 17 Locked QAM256 19 495000000 Hz 1.3 dBmV 42.2 dB 50 93 18 Locked QAM256 20 507000000 Hz 1.1 dBmV 42.1 dB 71 85 19 Locked QAM256 21 513000000 Hz 0.8 dBmV 42 dB 62 43 20 Locked QAM256 22 519000000 Hz 0.4 dBmV 42 dB 22 113 21 Locked QAM256 23 525000000 Hz 0 dBmV 41.8 dB 75 78 22 Locked QAM256 24 531000000 Hz 0.1 dBmV 41.8 dB 48 75 23 Locked QAM256 25 537000000 Hz -0.1 dBmV 41.8 dB 63 58 24 Locked QAM256 26 543000000 Hz -0.4 dBmV 41.6 dB 48 74 25 Locked QAM256 27 549000000 Hz -0.5 dBmV 41.5 dB 57 53 26 Locked QAM256 28 555000000 Hz -0.6 dBmV 41.3 dB 56 44 27 Locked QAM256 29 561000000 Hz -0.7 dBmV 41.3 dB 57 77 28 Locked QAM256 30 567000000 Hz -0.8 dBmV 41.2 dB 58 60 29 Locked QAM256 31 573000000 Hz -0.9 dBmV 40.7 dB 37 29 30 Locked QAM256 33 585000000 Hz -0.1 dBmV 41.3 dB 35 47 31 Locked QAM256 34 591000000 Hz 0 dBmV 41.3 dB 43 51 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 5 5120 Ksym/sec 16400000 Hz 41 dBmV 2 Locked ATDMA 6 5120 Ksym/sec 22800000 Hz 40.5 dBmV 3 Locked ATDMA 7 5120 Ksym/sec 29200000 Hz 40.8 dBmV 4 Locked ATDMA 8 5120 Ksym/sec 35600000 Hz 41 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Downstream OFDM Channels Channel Lock
StatusModulation /
Profile IDChannel
IDFrequency Power SNR /
MERActive Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 ,3 48 850000000 Hz 1.1 dBmV 40.9 dB 1108 ~ 2987 5882313471 4888015335 0 2 Not Locked 0 0 0 Hz 0 dBmV 0.0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV 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.
