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 except on the ODFM channels (but all correctable). Seemingly randomly, websites and other services in general will take *minutes* to connect but once they load it's fine. Speediest.net will be "connecting" for almost 40 seconds and then run at my full gig connection. Streaming apps will buffer for almost 2 minutes before starting to play, but then be completely fine. The issue is so confusing. I'm running Velop MX5300 as my router/access point, and have had no issues with the Xfinity modem in the past. I thought it might be a DNS issue, so I switched from the Comcast DNS to Cloudflare (1.1.1.1, 1.0.0.1) and Google (8.8.8.8) as my tertiary. Restarting the modem will usually fix the issue, but it will reappear soon enough. Netgear support is adament it's not the modems fault and it's my acesspoint's fault, but I've had no issues at all until I added this modem. Any ideas will be helpful!

Ryan-F wrote: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 except on the ODFM channels (but all correctable). Seemingly randomly, websites and other services in general will take *minutes* to connect but once they load it's fine. Speediest.net will be "connecting" for almost 40 seconds and then run at my full gig connection. Streaming apps will buffer for almost 2 minutes before starting to play, but then be completely fine. The issue is so confusing. I'm running Velop MX5300 as my router/access point, and have had no issues with the Xfinity modem in the past. I thought it might be a DNS issue, so I switched from the Comcast DNS to Cloudflare (1.1.1.1, 1.0.0.1) and Google (8.8.8.8) as my tertiary. Restarting the modem will usually fix the issue, but it will reappear soon enough. Netgear support is adament it's not the modems fault and it's my acesspoint's fault, but I've had no issues at all until I added this modem. Any ideas will be helpful!Hardware vendor/ISP finger pointing is a way of life in the home network world. It is here to stay. Your description of the problem leads me to look at DNS issues in the router configuration. Xfinity DNS does not have the best reputation. On your MX5300, do your have IPv6 enabled? Do you have options to configure IPv6 DNS addresses? Another third party DNS is NextDNS. My configuration uses NextDNS as primary DNS for both IPv4 and IPv6 and Xfinity primary addresses as secondary for both. Different areas are going to have different configurations that perform better.

I don't think I have the option to change the IPV6 address itself. The only DNS options I get are for local network settings.

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 = IPv6Sun 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 = IPv6Time 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 = IPv6Sun 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;

I am using a CAT6 cable connecting to a Linksys Velop MX5300

CM2050V Spotty internet connection

16 Replies

Kitsap
Master
Feb 26, 2023
Ryan-F wrote:
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 except on the ODFM channels (but all correctable).

Seemingly randomly, websites and other services in general will take *minutes* to connect but once they load it's fine. Speediest.net will be "connecting" for almost 40 seconds and then run at my full gig connection. Streaming apps will buffer for almost 2 minutes before starting to play, but then be completely fine. The issue is so confusing.

I'm running Velop MX5300 as my router/access point, and have had no issues with the Xfinity modem in the past. I thought it might be a DNS issue, so I switched from the Comcast DNS to Cloudflare (1.1.1.1, 1.0.0.1) and Google (8.8.8.8) as my tertiary. Restarting the modem will usually fix the issue, but it will reappear soon enough. Netgear support is adament it's not the modems fault and it's my acesspoint's fault, but I've had no issues at all until I added this modem.

Any ideas will be helpful!
Hardware vendor/ISP finger pointing is a way of life in the home network world. It is here to stay.

Your description of the problem leads me to look at DNS issues in the router configuration. Xfinity DNS does not have the best reputation.

On your MX5300, do your have IPv6 enabled? Do you have options to configure IPv6 DNS addresses?

Another third party DNS is NextDNS.

My configuration uses NextDNS as primary DNS for both IPv4 and IPv6 and Xfinity primary addresses as secondary for both.

Different areas are going to have different configurations that perform better.
- Ryan-F
  Aspirant
  Feb 26, 2023
  I don't think I have the option to change the IPV6 address itself. The only DNS options I get are for local network settings.

FURRYe38

Guru - Experienced User

Feb 26, 2023

Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router

Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended.
What is the brand and model of the host wifi router connected to the modem?

Ryan-F

Aspirant

Feb 26, 2023

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
Guru - Experienced User
Feb 26, 2023
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-F
Aspirant
Feb 26, 2023
I am using a CAT6 cable connecting to a Linksys Velop MX5300

Forum Discussion

CM2050V Spotty internet connection