Netgear cd3000dv2rg on twc, what do they mean?

[Skeetwales]

Error codes

Time Priority Description
Tue Feb 16 18:08:59 2016 Warning (5) Admin login authentication fail
Tue Feb 16 09:23:30 2016 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 09:23:30 2016 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:30:03 2016 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:29:56 2016 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:29:47 2016 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:28:39 2016 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:27:04 2016 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:25:48 2016 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:24:34 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:22:17 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:22:16 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:19:38 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:19:37 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Tue Feb 16 04:19:22 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:19:21 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:18:51 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:18:51 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:18:49 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:18:49 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 16 04:18:41 2016 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 12 12:40:24 2016 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=c4:04:15:37:d1:50;CMTS-MAC=00:01:5c:64:92:66;CM-QOS=1.0;CM-VER=3

[Skeetwales · Accepted solution]

Thanks

thats helpful

[DarrenM]

Hello Skeetwales

I see some T3 timeouts are typically a noise issues on the lines of the cable signal so a cable tech may need to come out and adjust some signals. Here is a link on the meanings of these timeouts.

https://docsismodem.wordpress.com/2010/08/13/t1t2t3-t4-timeouts-descriptions/

DarrenM

[Skeetwales · Accepted solution]

Thanks

thats helpful