Reply
Highlighted
Aspirant

CM1000 requiring rebooting several times a day (Comcast)

I recently purchased a Netgear CM1000 for use on Comcast and several times a day the internet just stops working despite all lights still showing green.  When this happens I can't even log into the web management app.  Turning the modem off and back on removes the problem, but this is really annoying to have to do multiple times a day!  Any advice is welcomed.  Here are some pertinent pieces of information:

 

Hardware Version2.02
 
Firmware VersionV2.01.14

 

Acquire Downstream Channel639000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnableBPI+
IP Provisioning ModeHonor MDDIPv6 only

 

 

Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
1LockedQAM25617639000000 Hz-1.7 dBmV39.1 dB10
2LockedQAM2561543000000 Hz-1.3 dBmV40.1 dB00
3LockedQAM2562549000000 Hz-1.2 dBmV40.1 dB20
4LockedQAM2563555000000 Hz-1.3 dBmV40.0 dB10
5LockedQAM2564561000000 Hz-1.4 dBmV39.9 dB20
6LockedQAM2565567000000 Hz-1.3 dBmV40.0 dB00
7LockedQAM2566573000000 Hz-1.5 dBmV39.9 dB30
8LockedQAM2567579000000 Hz-1.4 dBmV39.7 dB20
9LockedQAM2568585000000 Hz-1.5 dBmV39.7 dB20
10LockedQAM2569591000000 Hz-1.5 dBmV39.7 dB40
11LockedQAM25610597000000 Hz-1.7 dBmV39.6 dB70
12LockedQAM25611603000000 Hz-2.0 dBmV39.3 dB30
13LockedQAM25612609000000 Hz-2.5 dBmV39.3 dB50
14LockedQAM25613615000000 Hz-2.0 dBmV39.3 dB60
15LockedQAM25614621000000 Hz-1.7 dBmV39.3 dB40
16LockedQAM25615627000000 Hz-1.7 dBmV39.2 dB20
17LockedQAM25616633000000 Hz-1.7 dBmV39.3 dB10
18LockedQAM25618645000000 Hz-1.8 dBmV39.3 dB20
19LockedQAM25619651000000 Hz-1.7 dBmV39.1 dB30
20LockedQAM25620657000000 Hz-1.7 dBmV39.2 dB30
21LockedQAM25621663000000 Hz-1.6 dBmV39.1 dB30
22LockedQAM25622669000000 Hz-1.6 dBmV39.1 dB10
23LockedQAM25623675000000 Hz-1.5 dBmV39.1 dB00
24LockedQAM25624681000000 Hz-1.5 dBmV39.0 dB00
...        

Upstream Bonded Channels
ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
1LockedATDMA15120 Ksym/sec30100000 Hz45.5 dBmV
2LockedATDMA25120 Ksym/sec36500000 Hz45.5 dBmV
3LockedATDMA35120 Ksym/sec17300000 Hz43.5 dBmV
4LockedATDMA45120 Ksym/sec23700000 Hz45.5 dBmV
...      
 

 

TimePriorityDescription
2017-01-22, 21:03:53Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:03:58Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:04:05Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:04:49Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:04:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:05:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:05:10Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:05:28Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:05:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-22, 21:05:48Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 19:26:40Critical (3)No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:01:18Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:01:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:01:27Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:02:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:02:09Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:02:29Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:02:30Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:02:49Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:02:50Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 21:03:09Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 22:53:14Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:00:30Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:00:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:00:41Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:01:11Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:01:12Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:01:32Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:01:32Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:01:53Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:01:54Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
2017-01-24, 23:02:12Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:1d:45:70:69:60;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:8d:a0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6

 

This event log comes shortly after I had to restart my modem for the second time in the last 2 hours!

Message 1 of 67

Accepted Solutions
Highlighted
Aspirant

Re: CM1000 requiring rebooting several times a day (Comcast)

Interesting, the overall problem was solved for me and several neighbors.  Cox replaced a mini-amplifier in the box at the street. However, I found the item that had the largest impact to overall network stability was unplugging our Ac1200's extenders. interestingly, we each had one on our individual networks and removing them resolved the overall issues.

View solution in original post

Message 66 of 67

All Replies
Highlighted
NETGEAR Moderator

Re: CM1000 requiring rebooting several times a day (Comcast)

Hello bcassell

 

I see alot of T3 and T4 timeouts this usually is a issue with the connection to your home you may need to have your ISP tech come out and check the lines.

 

https://volpefirm.com/docsis_timout_descriptions/

 

DarrenM

 

Message 2 of 67
Highlighted
NETGEAR Employee

Re: CM1000 requiring rebooting several times a day (Comcast)

Hi,

 

NTGR observed this issue with specific users and working on FW fix and is currently under validation. 

 

we should have an update for you by 2/7. Hit us back and we will let you. 

 

Message 3 of 67
Highlighted

Re: CM1000 requiring rebooting several times a day (Comcast)

I am having the exact same issues with my CM1000, as well as slower download and upload speeds than my previous Arris SB6190. I sent an email to netgearteam@netgear.com and they replied they are going to work with Comcast to pull logs, etc., on my modem to see if they can figure out what is going on. The reply here from Netgear is also promising. I suspected these issues were due to a firmware bug, so am now hopeful Netgear will have a fix soon. I am subscribing to this thread to watch for any updates.

Message 4 of 67
Highlighted
Aspirant

Re: CM1000 requiring rebooting several times a day (Comcast)

Awesome to hear.
Message 5 of 67
Highlighted
Guide

Re: CM1000 requiring rebooting several times a day (Comcast)

I would like to chime in and add that I am also experiencing this exact same issue with the same log entries. I had to power cycle today to get my internet access back. I am hopeful we will get a firmware update soon as I would prefer not to have to return the modem.

Message 6 of 67
Highlighted
NETGEAR Employee

Re: CM1000 requiring rebooting several times a day (Comcast)

thank for your patience. Will let you know our validation results soon. 

Message 7 of 67
Highlighted
Aspirant

Re: CM1000 requiring rebooting several times a day (Comcast)

Any update?

I'm experiencing the same issues stated above PLUS if I change the modem login password, I can no longer hardwire my laptop to the cm1000 for speed test purposes.

Message 8 of 67
Highlighted
Aspirant

Re: CM1000 requiring rebooting several times a day (Comcast)

Also desperate here for an update on this as I am having the exact same issues and almost ready to return the modem to the store unless something is very very close to being done about this.

Message 9 of 67
Highlighted

Re: CM1000 requiring rebooting several times a day (Comcast)

Also having the same problem, works great when it works but I'm having to reset it two and three times a day. Unlike the original poster I don't have all green lights. Mine drops the UPSTREAM and INTERNET lights and a blinking DOWNSTREAM light likes it's searching for a signal. A quick power cycle and it's back up and running so I'm sure it's not a problem at the cable company. I also recently had a service call from Comcast that checked out signal strength and noise and they gave me a clean bill of health. Rather disappointed that I replaced a rock solid SB6141 with this.
Message 10 of 67
Highlighted

Re: CM1000 requiring rebooting several times a day (Comcast)

I am having the same problems and have the same type of logs. Comcast has been here several times in the last 2 weeks and replaced cable lines from the pole to the modem also installed a powered amplifier and am now on my second test modem. They checked the nodes in my area and found a large amount of noise. It has been escalated up to a regional customer service manager and no one even seems to know that this is a known issue with the CM1000.

 

Message 11 of 67
Highlighted
NETGEAR Employee

Re: CM1000 requiring rebooting several times a day (Comcast)

FW is certified by the ISP. Just waiting for deployment. Will confirm soon. 

Message 12 of 67
Highlighted
Aspirant
Aspirant

Re: CM1000 requiring rebooting several times a day (Comcast)

Is FW coming to Cox as well? I'm having similar issues on Cox.

Message 13 of 67
Highlighted
Guide

Re: CM1000 requiring rebooting several times a day (Comcast)

That's great news, vkdelta. Please keep us updated.

Message 14 of 67
Highlighted

Re: CM1000 requiring rebooting several times a day (Comcast)

What version should we be looking for when the ISPs start pusing it out?

 

I'm currently showing V2.01.14

Message 15 of 67
Highlighted
Guide

Re: CM1000 requiring rebooting several times a day (Comcast)

A response from a Netgear engineer by email on another forum indicated it would be 2.01.15 for those of us on Comcast, since we are on 2.01.14 right now. I assume Cox will be going to .14 since they are apparently on .13.

Message 16 of 67
Highlighted
Guide

Re: CM1000 requiring rebooting several times a day (Comcast)

Any update? I had another "incident" last night.

Message 17 of 67

Re: CM1000 requiring rebooting several times a day (Comcast)

I have a feeling Comcast isn't pushing the new firmware out yet. I have power-cycled my modem several times in the hope I would receive the new firmware, with no luck.

Message 18 of 67
Highlighted
Guide

Re: CM1000 requiring rebooting several times a day (Comcast)

Comcast apparently hasn't pushed it yet (according to my own experience as well as that of others on DSLReports) but Cox is pushing it out, and they're getting .15. Comcast fails us again.

Message 19 of 67
Highlighted
NETGEAR Employee

Re: CM1000 requiring rebooting several times a day (Comcast)

Comcast should happen early next week. 

COX will directly go to .15 as well. (no need to go .14). no ETA but should happen soon.

Message 20 of 67
Highlighted
Guide

Re: CM1000 requiring rebooting several times a day (Comcast)

Two more dropouts today, one yesterday. I really hope early next week means tomorrow. This is beyond frustrating.

Message 21 of 67
Highlighted

Re: CM1000 requiring rebooting several times a day (Comcast)

Try having this many disconnects in the last 5 hors.....

 

 
 
 
TimePriorityDescription
2017-02-12, 15:02:52Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:02:58Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:03:43Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:03:50Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:04:32Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:04:38Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:05:22Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:05:27Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:06:11Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:06:15Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:06:57Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:07:02Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:07:45Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:07:50Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:08:32Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:09:32Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:11:11Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:11:18Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:12:04Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:12:10Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:12:55Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:13:00Critical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
2017-02-12, 15:13:42Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:66:d6:38;CMTS-MAC=00:01:5c:7f:a0:61;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
 

Help Center
 
Message 22 of 67
Highlighted

Re: CM1000 requiring rebooting several times a day (Comcast)

The people here have no idea about any firmware update!
Message 23 of 67
Highlighted
Luminary

Re: CM1000 requiring rebooting several times a day (Comcast)

Dropouts from CM1000 are now increasing to several times a day for me - this is now well past being an annoyance...

 

Oh mighty Netgear and Comcast gods - please release v .15 firmware asap!!!

Message 24 of 67
Highlighted
NETGEAR Employee

Re: CM1000 requiring rebooting several times a day (Comcast)

One last step to go...almost getting there. I can understand your situation..

Just waiting for ISP to deploy new config files.

 

Message 25 of 67
Top Contributors
Discussion stats
Announcements