Suddenly, many log entries. What happened?

Hi markfilipak,

Good day!

Welcome to NETGEAR Community!

First of all, we do apologize for the inconvenience of not getting back to you immediately due to the backlog in the system. You may check the meaning of the error codes from this link https://highspeed.tips/docsis-events/

Please do not hesitate to let me know if you need further assistance. 

Regards,

Oliver
Community Team

Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
Be sure your using good quality RG6 coax cable up to the modem. 
Be sure to power OFF the modem for 1 minute them back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853

---

markfilipak wrote:

Howdy,

I occasionally check the gateway's internal log and find that 2 or 3 times a year, there's some entries. However, this is unusual. Got any ideas what happened?

 

 Mon Aug 24 23:34:38 2020    Error (4)   Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:34:38 2020    Error (4)   Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:34:25 2020    Critical (3)    DHCP FAILED - Requested Info not supported.;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.0;CM-VER=3.0; 
 Mon Aug 24 23:34:20 2020    Critical (3)    No Ranging Response received - T3 time-out;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.0;CM-VER=3.0; 
 Mon Aug 24 23:34:20 2020    Warning (5)   B-INIT-RNG Failure - Retries exceeded;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.0;CM-VER=3.0; 
 Mon Aug 24 23:31:27 2020    Critical (3)    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Mon Aug 24 23:30:52 2020    Critical (3)    SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Mon Aug 24 23:21:49 2020    Critical (3)    SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:21:49 2020    Critical (3)    Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:21:48 2020    Warning (5)   Lost MDD Timeout;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:21:48 2020    Warning (5)   MDD message timeout;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:21:20 2020    Critical (3)    SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:21:08 2020    Critical (3)    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:17:30 2020    Critical (3)    Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:17:30 2020    Critical (3)    16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 
 Mon Aug 24 23:16:21 2020    Critical (3)    16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:8e:f2:30:63:a8;CMTS-MAC=00:01:5c:9d:3c:62;CM-QOS=1.1;CM-VER=3.0; 

---