NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
sparky0721
Jun 16, 2017Aspirant
Firmware Update for CM500
Hi, I need to update my firmware for my CM500 modem. Per Netgear, it should be V1.01.05 but mine is still V1.01.04 (according to modem when I log in from home network). Because Netgear says I need...
sparky0721
Jun 21, 2017Aspirant
Below is everything listed in the log. Definitely seems to have some errors and problems but I have no clue what any of it means and/or what i can do to fix it.
Thanks for the help.
Time Priority Description
2017-6-18, 09:13:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:13:43 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:13:43 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:13:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:13:50 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:13:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:13:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:14:30 Notice (6) Honoring MDD; IP provisioning mode = IPv4
2017-6-18, 17:14:34 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:14:34 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:14:34 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:14:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 17:14:47 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2017-6-18, 17:14:55 Warning (5) ToD request sent - No Response received;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 17:14:56 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:14:56 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:25 Warning (5) MDD message timeout;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:32 Warning (5) MDD message timeout;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:33 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:33 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:36 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:45 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:50 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 09:26:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:26:59 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 09:27:02 Notice (6) Honoring MDD; IP provisioning mode = IPv4
2017-6-18, 17:27:05 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:27:05 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:27:05 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:27:08 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 17:27:13 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 17:27:18 Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2017-6-18, 17:27:30 Warning (5) ToD request sent - No Response received;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.0;CM-VER=3.0;
2017-6-18, 17:27:31 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
2017-6-18, 17:27:31 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=50:6a:03:f6:6c:f0;CMTS-MAC=00:01:5c:6b:f6:53;CM-QOS=1.1;CM-VER=3.0;
DarrenM
Jun 22, 2017Sr. NETGEAR Moderator
Hello Sparky0721
Yea I see you are getting T3 and T4 timeouts which indicated there is signal issues you will have to contact your ISP and have them come check you lines and the lines in the area.
DarrenM
- lm8Aug 19, 2017Initiate
Hi. I am having the exact same problems as described above. When I called my ISP, Spectrum/Time Warner, they said that there have been no internet outages in my area in weeks, so it must be my modem. Netgear indicates there is a firmware upgrade, v1.01.05. This is in the troubleshooting advice to upgrade firmware. However, the ISP says they can't do it, and Netgear says they can't do it. How am I supposed to upgrade the firmware?
- lm8Aug 19, 2017Initiate
And this was the last error listed in my event log: Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=2c:30:33:6d:93:70;CMTS-MAC=00:17:10:88:37:06;CM-QOS=1.1;CM-VER=3.0;
There are many other errors listed in the log. Synch timing syncronization failure is another common one. It would seem obvious to ugrade firmware, just not possible....