NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
CM1000 Xfinity issues
I am quite frustrated at this point. I had a CM600 modem to support Comcast's Extreme 150 service. I've had it for a few years and was consistently getting 160 to 170mbps speed from it. About thre...
Well it is finally fixed. The tech showed up today and I showed him the two frequencies that were having the problem. He checked outside, and then at the tap. He came into the house and said he needed to call a bucket truck in to fix it. I got a recorded call from Comcast that they were working to fix the issue. I got a second call an hour later that the issue was fixed. I ran a speed test and got a consistent 160mbps (yay!). I used the reset button on the modem and let it re-provision. All the signal/noise and power levels were good and there were no uncorrectable codewords. They didn't tell me what they fixed, but at long last, it is fixed.
I ran into the same problem and spent 4 hours with both Netgear and comcast rep. It doesnt go anywhere as comcast said it's modem and netgear said comcast with cable line with noises/traffic. reset model, power up/down.... not sure I want to go with diffent brand of modem
| 2018-04-20, 22:50:18 | Notice (6) | CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: ; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 22:50:18 | Warning (5) | Unicast DSID PSN startup error |
| 2018-04-20, 22:47:41 | Warning (5) | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 22:41:33 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 18:31:17 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:55:24 | Critical (3) | Resetting the cable modem due to docsDevResetNow |
| 2018-04-20, 08:45:06 | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:34:41 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:34:36 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:34:17 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:34:16 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:33:57 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:33:56 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:33:37 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:33:36 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:32:58 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:32:52 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 08:32:49 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:31:38 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:31:33 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:31:13 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:31:13 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:30:53 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:30:53 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:30:33 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:30:33 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
| 2018-04-20, 07:29:59 | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:39:56:9c:67:41;CMTS-MAC=00:9e:1e:58:d4:ef;CM-QOS=1.1;CM-VER=3.1; |
Post your modem connection page. Look at the downstream power levels. Are there any channels with a very high number of uncorrectable codewords? By high I mean millions or billions. If you can post that full page here, the community can better assist. BTW, these issues seem to be almost always COMCAST issues not NetGear issues, but you have to tell them specifically what is wrong. It will usually mean a trip to the house by a tech. I work at home so it's no big deal but for others, that can be a pain in the butt.
jgnoonan wrote:Post your modem connection page. Look at the downstream power levels. Are there any channels with a very high number of uncorrectable codewords? By high I mean millions or billions. If you can post that full page here, the community can better assist. BTW, these issues seem to be almost always COMCAST issues not NetGear issues, but you have to tell them specifically what is wrong. It will usually mean a trip to the house by a tech. I work at home so it's no big deal but for others, that can be a pain in the butt.
I have mine posted above, but here they are again:
I don't know to get them to show inline with the post.
CM1000 statusIs this right after a boot and a reset of the modem? Because mine looks nothing like that.
DarrenM wrote:
Hello NBCGLX
You levels seem to be off a little low on the downstream and high on the upstream do you have any splitter connected
Mrgoodall You look to have some uncorrectables are you seeing any timeouts in your logs.
DarrenM
One splitter where the main line comes into the garage that feeds 4 coax outlets in the house. One of the outlets feeds another splitter, which feeds the modem and a MoCA 2.0 bonded adapter for our MoCA network.
You may want a ISP tech to come out and check the levels on your lines.
DarrenM
they dispatched a tech, he looked and saw it was a indeed a line quality issue, had to scheudle a line tech to complete maintence. based solely on signal quality, he showed me his readings, they showed "DOCSIS Failure". 7-10 business days until line tech completes work.
I wonder why these cable modems are not smart enough to detect line signal issues and let the user know? Seems like an easy to add feature that would be useful for customer.
- It could be that different cable systems provision via different methods and systems. Adding features like automated reporting to non-compatible systems could real havoc on an ever changing platform. Remember, each isp provisions the modems to their system. It may not be in their interest to support a product that they don’t sell/bill for.
