NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Kitsap
Feb 20, 2025Master
Netgear CM2050V Modem Firmware Update to V10.01.03
Some reports earlier today out of PA, updated firmware for the CM2050V modem has been pushed. No indications this is a test case or a slow roll example. This firmware should be mid-split capable. ...
FURRYe38
Mar 06, 2025Guru - Experienced User
Cable connections looks good, Please post the event logs data as well.
Try a power OFF for 1 minute then back ON. A reboot may not be enough.
Miked2
Mar 06, 2025Apprentice
Power cycled modem and router. No change in speed 720/42.
Here is the event log:
Thanks!
Time | Priority | Description |
Thu Mar 06 13:41:20 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 13:40:25 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 13:40:24 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 13:40:18 2025 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 10:37:33 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 10:37:31 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 10:37:25 2025 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 08:24:31 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 08:24:30 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 08:24:24 2025 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 03:22:58 2025 | (Notice (6)) | SW download Successful - Via Config file |
Thu Mar 06 03:22:03 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 03:21:49 2025 | (Notice (6)) | SW Download INIT - Via Config file d11_v_cm2050vims_fast_c02.cm |
Thu Mar 06 03:21:44 2025 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 03:21:38 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 03:21:36 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Thu Mar 06 03:21:31 2025 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;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=08:36:c9:3c:90:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 07:18:38 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 07:14:35 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 07:14:25 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 07:08:02 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 07:03:17 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 06:16:01 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 06:13:07 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 06:00:39 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 05:59:48 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Wed Mar 05 00:21:32 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sat Mar 01 08:27:30 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sat Mar 01 08:27:15 2025 | (Critical (3)) | UCD invalid or channel unusable;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sat Mar 01 08:27:09 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sat Mar 01 08:27:07 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3c:90:30;CMTS-MAC=00:90:f0:30:00:00;CM-QOS=1.1;CM-VER=3.1; |
- FURRYe38Mar 06, 2025Guru - Experienced User
Some criticals in there but not many. 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.
I'd get with the ISP and have them check everything up to the modem.
Be sure to test with a ethernet connected PC behind the modem with out a wifi router in the mix.
Test with a 2nd ethernet connected PC to compare results.