NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Ryan-F
Feb 26, 2023Aspirant
CM2050V Spotty internet connection
Hi everyone, I replaced my XB7 with a CM2050V about 20 days ago. Ever since then the internet has been highly unreliable. All power levels are within spec and SNR is above 45db. There are no errors e...
Ryan-F
Feb 26, 2023Aspirant
Event Log:
Sun Feb 26 13:14:26 2023 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:14:17 2023 | (Warning (5)) | MDD message timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:14:13 2023 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:14:01 2023 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:55 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:55 2023 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:53 2023 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:45 2023 | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
Sun Feb 26 13:13:37 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:35 2023 | (Warning (5)) | Lost MDD Timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:28 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:27 2023 | (Warning (5)) | Lost MDD Timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:20 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:13:11 2023 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08: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:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:09:17 2023 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:09:17 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:09:13 2023 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:09:13 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:08:29 2023 | (Warning (5)) | MDD message timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:08:29 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:08:23 2023 | (Warning (5)) | MDD message timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:08:22 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:05:56 2023 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:05:55 2023 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:05:39 2023 | (Warning (5)) | MDD message timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:05:21 2023 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:05:20 2023 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:05:11 2023 | (Notice (6)) | Honoring MDD; IP provisioning mode = IPv6 |
Sun Feb 26 13:05:02 2023 | (Warning (5)) | Lost MDD Timeout;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:04:53 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:53 2023 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:53 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:49 2023 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:49 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:48 2023 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:48 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:45 2023 | (Critical (3)) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
Sun Feb 26 13:03:45 2023 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b4:7b:c0;CMTS-MAC=00:90:f0:6f:08:00;CM-QOS=1.1;CM-VER=3.1; |
FURRYe38
Feb 26, 2023Guru - Experienced User
I see lots of Criticals in the events log that the ISP needs to review and resolve.
Lets take a look at the cable connections page please...
- Ryan-FFeb 26, 2023Aspirant
I do not know why the connections post keeps disappearing on me. I've posted it 3 times now.
- FURRYe38Feb 26, 2023Guru - Experienced User
Put it in a PDF file then attach it using the Choose File button on your next post.
- FURRYe38Feb 26, 2023Guru - Experienced User
Is there any number values seen under the Corretables and Un-Correctables columns? Or they all zeros?
Power levels are in spec however go from 4 on lower channels up to 7 on higher..I guess thats ok. All channels should be near each other across all channels.
- Ryan-FFeb 26, 2023Aspirant
Sorry to use pastebin but the connections post keeps deleting: https://pastebin.com/ychzHBip