Discussion stats
  • 15 replies
  • 17496 views
  • 6 kudos
  • 8 in conversation
Announcements

Top Contributors
Reply
Highlighted
Initiate

CM1000 RNG-RSP Issues

Since the new firmware update of V3.01.02 that was pushed out to Comcast I have been receiving "RNG-RSP CCAP Commanded Power in Excess of 6db Below the Value Correstponding to the Top of the DRW" errors constantly. After so many, it will start throwing T3 and T4 timeouts and go into a reboot cycle until it is happy again. Sometimes it will come back and be fine for an hour or 2, sometimes it comes back and only has one upload channel, other times I have to go, manually shut it off, and turn it on again. I have called comcast and been dealing with them for 2 weeks now. They sent someone out, he said the signal couldnt be any more perfect which I believe because this issue didnt happen until AFTER the new firmware. In talking to the person from comcast I have been talking to, she stated there has been only one other person with the same issues as me that has talked to her. She doesnt know if anyone else has called in and talked to other people. She has also been talking to co-workers to try and figure out things to try. As of right now, the last thing we thought of would be to post here. This issue has made it to the point I cant use my home network for internet and I have been using my cellphone's 4G to get things done.

Message 1 of 16
Highlighted

Re: CM1000 RNG-RSP Issues

I'm having the exact same issue. My new CM1000 modem is logging dozens of the following message triplets per day and a simple ping shows that I'm dropping lots of packets because of it, which obviously is messing up my throughput and general internet usability (MAC value intentionally masked):

 

RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

RNG-RSP CCAP Commanded Power Exceeds Value for Pmax;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Dynamic Range Window violation

 

I also have Comcast/Xfinity (West Palm Beach, FL area) and have been frustrated with this. The closest info I've been able to find is some other forum where someone posted a similar problem and stated that that after some advanced troubleshooting, they eventually determined it was an issue with the software running on the box on the pole, and had nothing to do with his wiring to or within the home.

So I'm not sure if that issue is related, or if there is a mismatch between the software installed on the external hardware vs the software being pushed to these new consumer modems, but I can tell you its frustrating. I pay for 150MB and I just ran a speed test and it returned a fraction of 1MB download speed. So once again I am rebooting everything to see if that will temporarily "heal" the issue -- until another hour or two where it happens again.

Model: CM1000|DOCSIS® 3.1
Message 2 of 16
Highlighted
NETGEAR Moderator

Re: CM1000 RNG-RSP Issues

I would contact the ISP could be a issue with the power levels or the lines causing these errors.

 

DarrenM

Message 3 of 16
Highlighted
Initiate

Re: CM1000 RNG-RSP Issues

I did contact Comcast and they said the levels in my area look fine. Had a tech come out and he checked the line going into the house and his words were "it couldnt be any more perfect than this, if it started after the new firmware, thats all I can think of" which, he is right, it started after the new firmware was pushed. So either this firmware is telling me theres something wrong with the modem and its not happy with the levels for whatever reason, or theres another issue, its related to this firmware. I am still talking with comcast to see if they have any other ideas on what to try. As it stands the modem either reboots on its own or I have to do it by hand to get a connection again.

Message 4 of 16
Highlighted

Re: CM1000 RNG-RSP Issues

My CM1000 also suffers the same thing, except the auto-reboots, ever since the firmware update - it's been fine with few error messages for months until this firmware. I'm on Comcast in Seattle. I'd have to say that this is one of the most fussy, problematic modems I've ever owned.

Message 5 of 16
Highlighted

Re: CM1000 RNG-RSP Issues

2 weeks later and no change. Still getting the errors. 

Message 6 of 16
Highlighted

Re: CM1000 RNG-RSP Issues

Just an update from my earlier post:  Same issue, same firmware version with no update. I'm only typing this now because I've been having to reset my modem several times a day (at least) to have any decent throughput (I pay for 150MB) until it craps out again and takes my internet speed down to a drip-drip rate.

 

I would really like to see someone in an official capacity comment on this from Netgear, instead of this "community" just standing around scratching our heads and talking into a void. There is someone somewhere over in Netgear engineering who knows exactly what types of things might trigger this issue. That information, in turn, could then be used to inform Comcast techs on how to fix it. Or Netgear themselves could issues a patch that would bring back some reasonable stability to these units until further research can be done to correct it. Perhaps they could add a software option to enable/disable something that would make the modem operate more like my older Netgear modems did.

Message 7 of 16
Highlighted
Apprentice

Re: CM1000 RNG-RSP Issues

I need to say that my modem has started acting up also.  Its not giving out an address to my router, my speed it cut in half, when it is working the speed is so slow I cant pull email.  I have had to reboot my router 5 times and reset it once since I have been home just to get an IP address to type this.  My speed is significantly reducted (300/30 at 100/5).  I just started having issues today and my firmware is the same as what is listed here.

 

Feeds an Orbi for what its worth.....

 

-Jack

Model: CM1000|DOCSIS® 3.1
Message 8 of 16
Highlighted
Apprentice

Re: CM1000 RNG-RSP Issues

I forgot to post some log fun;

 

TimePriorityDescription
2017-12-08, 18:53:09Warning (5)RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-08, 18:53:09Warning (5)REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-08, 18:53:04Notice (6)DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 .;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
Time Not EstablishedNotice (6)Honoring MDD; IP provisioning mode = IPv6
Time Not EstablishedCritical (3)No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;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:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:47:24Critical (3)No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:44:42Critical (3)No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:40:03Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:39:58Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:39:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:39:38Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:39:19Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:39:18Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:38:59Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:38:58Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:38:11Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:38:05Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-07, 07:38:01Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:31:13Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:31:04Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:31:04Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:54Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:53Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:44Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:44Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:34Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:33Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:14Critical (3)Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 05:30:13Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:07:25Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:06:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:06:34Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:04:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:03:45Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:02:55Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:02:46Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:02:44Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:01:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2017-12-06, 04:01:47Critical (3)DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=a0:04:60:fc:0b:c8;CMTS-MAC=2c:86:d2:88:48:e9;CM-QOS=1.1;CM-VER=3.1;
Message 9 of 16
Highlighted
NETGEAR Moderator

Re: CM1000 RNG-RSP Issues

Hello N4cho 

 

You have quite a few T4 timeouts have you looked on your power level screen and see if any of the channels have alot of uncorrectables? This could be some type of line issue in the area of your home.

 

DarrenM

Message 10 of 16
Highlighted
Apprentice

Re: CM1000 RNG-RSP Issues

Thanks for the reply!

 

Uncorrectable Codewords are at 0.  Does my power look okay?

 

Version:1.0 StartHTML:000000200 EndHTML:000017769 StartFragment:000011979 EndFragment:000017683 StartSelection:000011979 EndSelection:000017641 SourceURL:http://192.168.100.1/DocsisStatus.aspNETGEAR Modem CM1000

<tabindex=-1>Downstream Bonded Channels
ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25621615000000 Hz5.7 dBmV40.9 dB-2095552163300
2LockedQAM2561483000000 Hz9.4 dBmV43.4 dB-209678843820
3LockedQAM2562489000000 Hz9.4 dBmV43.4 dB-209678122800
4LockedQAM2563495000000 Hz9.2 dBmV43.1 dB-209676957900
5LockedQAM2564501000000 Hz9.4 dBmV43.4 dB-209676145920
6LockedQAM2565507000000 Hz9.1 dBmV43.3 dB-209675194800
7LockedQAM2566513000000 Hz8.8 dBmV43.2 dB-209674266510
8LockedQAM2567525000000 Hz8.1 dBmV43.0 dB-209673406510
9LockedQAM2568531000000 Hz7.7 dBmV43.0 dB-209660662600
10LockedQAM2569537000000 Hz7.8 dBmV42.6 dB-209659732600
11LockedQAM25610543000000 Hz7.5 dBmV42.7 dB-209658798310
12LockedQAM25611555000000 Hz7.4 dBmV42.5 dB-209657785050
13LockedQAM25612561000000 Hz7.4 dBmV42.4 dB-209656875560
14LockedQAM25613567000000 Hz7.2 dBmV42.4 dB-209655819460
15LockedQAM25614573000000 Hz7.4 dBmV42.5 dB-209655106580
16LockedQAM25615579000000 Hz6.9 dBmV42.1 dB-2096539758100
17LockedQAM25616585000000 Hz6.8 dBmV41.8 dB-209639432780
18LockedQAM25617591000000 Hz6.5 dBmV41.9 dB-2096383960230
19LockedQAM25618597000000 Hz6.3 dBmV41.4 dB-2096374142190
20LockedQAM25619603000000 Hz6.2 dBmV41.4 dB-2096365796180
21LockedQAM25620609000000 Hz5.9 dBmV41.3 dB-2096356192270
22LockedQAM25622621000000 Hz5.4 dBmV40.4 dB-2096347005510
23LockedQAM25623627000000 Hz5.4 dBmV40.6 dB-2096336737350
24LockedQAM25624633000000 Hz5.5 dBmV40.6 dB-2096326700370
25LockedQAM25625639000000 Hz5.5 dBmV40.3 dB-2096288747350
26LockedQAM25626645000000 Hz5.5 dBmV40.3 dB-2096279344360
27LockedQAM25627651000000 Hz5.3 dBmV40.3 dB-2096269879350
28LockedQAM25628657000000 Hz5.0 dBmV40.2 dB-2096260893710
29LockedQAM25629663000000 Hz4.9 dBmV40.0 dB-2096251374710
30LockedQAM25630669000000 Hz4.8 dBmV40.0 dB-2096244899720
31LockedQAM25631675000000 Hz4.9 dBmV38.7 dB-2096238828670
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
Model: CM1000|DOCSIS® 3.1
Message 11 of 16
Highlighted
NETGEAR Moderator

Re: CM1000 RNG-RSP Issues

some of your downstreams are a little high they should be  -7 to +7 dBmV. for the best connection.

 

DarrneM

Message 12 of 16
Highlighted
Aspirant

Re: CM1000 RNG-RSP Issues

I just started receiving the same errors and issues, reboots and disconnects multiple times a day. Just started yesterday.. real bummer Smiley Sad Otherwise I've really enjoyed the modem. Here are some of my stats if it will help.. I've posted on Xfinity as well, waiting for some feedback.

 

2017-12-23, 08:40:56

Warning (5)

REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 17:53:40

Critical (3)

Resetting the cable modem due to docsDevResetNow

2017-12-22, 17:49:50

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 14:14:06

Critical (3)

Resetting the cable modem due to docsDevResetNow

2017-12-22, 14:11:15

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 14:07:01

Critical (3)

REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 13:23:26

Critical (3)

REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 07:11:59

Critical (3)

REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:10;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 07:08:13

Critical (3)

REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 07:06:49

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 07:05:34

Critical (3)

REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2017-12-22, 07:04:01

Critical (3)

REG RSP not received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Critical (3)

DHCP failed - DHCP Solicit sent, No DHCP Advertise received;CM-MAC=xx:xx:xx:xx:xx:10;CMTS-MAC=xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

 
 

 

Note: I removed the MAC addresses, but the CM-MAC and CMTS-MAC do not match.

 

Latest Log after a factory reset on the modem:

 

2017-12-23, 09:01:46

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx;CMTS-MAC=00:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2017-12-23, 09:00:19

Notice (6)

CM-STATUS message sent. Event Type Code: 3; Chan ID: N/A; DSID: E; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xx:xx:xx:xx:xx;CMTS-MAC=00:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

2017-12-23, 09:00:19

Warning (5)

Unicast DSID PSN startup error

2017-12-23, 08:59:49

Warning (5)

REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=xx:xx:xx:xx:xx;CMTS-MAC=00:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv6

Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx;CMTS-MAC=00:xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

 

Here are my current connection stats:

 

Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency

<tabindex=-1>Startup Procedure

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

<tabindex=-1>Downstream Bonded Channels

ChannelLock StatusModulationChannel IDFrequencyPowerSNR / MERUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1LockedQAM25621729000000 Hz6.2 dBmV40.3 dB4875467500
2LockedQAM2561609000000 Hz8.1 dBmV41.0 dB4725342000
3LockedQAM2562615000000 Hz7.7 dBmV40.9 dB4726194100
4LockedQAM2563621000000 Hz7.9 dBmV41.0 dB4727104600
5LockedQAM2564627000000 Hz7.4 dBmV40.9 dB4728014100
6LockedQAM2565633000000 Hz7.4 dBmV40.6 dB4728591600
7LockedQAM2566639000000 Hz7.2 dBmV40.7 dB4729916100
8LockedQAM2567645000000 Hz7.1 dBmV40.6 dB4730795100
9LockedQAM2568651000000 Hz6.9 dBmV40.5 dB4731771200
10LockedQAM2569657000000 Hz6.9 dBmV40.5 dB4732699600
11LockedQAM25610663000000 Hz6.9 dBmV40.4 dB4733666900
12LockedQAM25611669000000 Hz7.0 dBmV40.6 dB4734559800
13LockedQAM25612675000000 Hz7.1 dBmV40.1 dB4735571600
14LockedQAM25613681000000 Hz6.9 dBmV40.3 dB4736394900
15LockedQAM25614687000000 Hz7.2 dBmV40.6 dB4737343800
16LockedQAM25615693000000 Hz6.9 dBmV40.2 dB4738270700
17LockedQAM25616699000000 Hz6.8 dBmV40.2 dB4738007900
18LockedQAM25617705000000 Hz6.7 dBmV40.5 dB4741039900
19LockedQAM25618711000000 Hz6.4 dBmV40.4 dB4741998000
20LockedQAM25619717000000 Hz6.2 dBmV40.3 dB4742880100
21LockedQAM25620723000000 Hz5.9 dBmV40.3 dB4743058100
22LockedQAM25622735000000 Hz5.5 dBmV40.2 dB4743825000
23LockedQAM25623741000000 Hz5.9 dBmV40.2 dB4744437000
24LockedQAM25624747000000 Hz5.3 dBmV40.1 dB4744990400
25Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
26Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
27Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
28Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
29Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
30Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
31Not LockedUnknown00 Hz0.0 dBmV0.0 dB000
32Not LockedUnknown00 Hz0.0 dBmV0.0 dB000

<tabindex=-1>Upstream Bonded Channels

ChannelLock StatusModulationChannel IDFrequencyPower
1LockedATDMA135800000 Hz49.5 dBmV
2LockedATDMA229400000 Hz50.0 dBmV
3LockedATDMA323000000 Hz50.0 dBmV
4Not LockedUnknown00 Hz0.0 dBmV
5Not LockedUnknown00 Hz0.0 dBmV
6Not LockedUnknown00 Hz0.0 dBmV
7Not LockedUnknown00 Hz0.0 dBmV
8Not LockedUnknown00 Hz0.0 dBmV

<tabindex=-1>Downstream OFDM Channels

ChannelLock StatusModulation / Profile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier Number RangeUnerrored CodewordsCorrectable CodewordsUncorrectable Codewords
1Not LockedUnknown00 Hz0 dBmV0 dB0 ~ 0000
2Not LockedUnknown00 Hz0 dBmV0 dB0 ~ 0000

<tabindex=-1>Upstream OFDMA Channels

ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
1Not LockedUnknown00 Hz0 dBmV
2Not LockedUnknown00 Hz0 dBmV
Model: CM1000|DOCSIS® 3.1
Message 13 of 16
Highlighted

Re: CM1000 RNG-RSP Issues

Final Update:  I wanted to provide a fair and acurate picture of what turned out to be causing my constant T3/T4 timeouts & the out of range errors in the CM1000 log. Whether the recent firmware update did or didn't increase the power level for some users, I do not know. But I didn't want to leave my contribution to this thread hanging with the impression that my issues were caused by a CM1000 firmware update. In fact, the unit was just reporting the true state of the signal it was receiving, and correctly timing out when that signal degraded so low that it could not hold sync.

 

A while back, I had suspected that my splitters and/or the original house cabling (circa 1998) might be the cultprit. So I replaced my splitters with properly rated (supposedly) higher quality ones. Saw little if any change. I even removed extra splitter down to just one and used termination caps on unused ends.

 

So I called out a Comcast tech who checked and replaced the cable line coming from the street to my house. While his external signal levels were much improved, I still had intermittent issues getting a good quality signal inside. Even after purchasing all new networking gear (Netgear CM1000 and Orbi RBK53 Router & 2 Sats), I was still having issues. So I knew something was still very wrong after continuing to see frequent T3/4 timeouts and out of range warnings, which a reset would only remedy for a short time.

 

So I decided to connect the cable line from the street directly into my CM1000 router and observe the status and signal levels myself. Sure enough, it immediately went from reporting terrible Power and so-so SNR levels to showing much improved numbers across all 24 bonded channels:

 

Reported ranges using home cabling & splitters:
Power : -13.2 to -10.4 dBmV <-- BAD!
  SNR :  37.5 to  39.6 dB


Reported ranges after direct cable connection:
Power : + 7.9 to +10.2 dBmV
  SNR :  40.4 to  41.5 dB

 

So then I began testing all the various splitters I had on hand, by directly adding each, one-by-one, between the cable line from the street and my CM1000 modem:

 

Rating Brand                       Comments
1/5    IDEAL 4 way splitter        Junk. Noticeable quality drop off above 700000000 Hz
2/5    Comscope (red) splitter     Poor, recommended and provided by last Comcast tech
3/5    TVC 3.5db / 7db splitter    Good, but not great; original equip, installed new in 1998
4/5    Using GE (square) splitter  Quite good, surprising since I see posts bashing these
5/5    Extreme (square) splitter   Very good, numbers were nearly the same as direct connect

 

So in the end, I discovered that my poor signal quality issues were primarily due to the splitters I was using (and by mistakenly trusting a Comcast tech to provide a good quality splitter which was crap). Even worse, I had been using two splitters in series--one at the main manifold in the attic, then another in the family room splitting a line between the cable TV box and the CM1000 modem--which further degrading the signal.

 

My "semi-scientific" testing also showed that just the original house cabling itself was dropping the signal a noticeable amount as well. I'm not sure if it was the run-length causing it or the quality of the cable used from 1998. Regardless, I now have the info I need to change out the inside components to effect a much better signal. So the CM1000 modem and its recent firmware were not a contributing factor in my particular case.

 

 

Message 14 of 16
Highlighted
Guide

Re: CM1000 RNG-RSP Issues

Whooooa!  All 3 upstream channels are at 50db.  THAT my friend is your issue.  CM is your Cable Modem.  CMTS is the Cable Modem Termination System at the Cable Company.  Your modem is SCREAMING to be heard by the CMTS.  The normal range is 30db to 45db.  You must have wiggle room.  When your modem cannot be heard, it reboots. 

Message 15 of 16
Highlighted
Aspirant

Re: CM1000 RNG-RSP Issues

I have the same issue. ISP= Mediacom

It seems that the DocSys 3.1 technology cannot be properly implemented by the ISP advertising that 1GB down stream service.  The line runs too hot the Node pops an error then you and a few neighbors lose signal for a few minutes to an hour and the cycle begins again.

It seems to have something to do witht he SYNC time Syncronization error. Aka the Timing that the ISP uses kind of like your PC clock.

3-17-2018, 9:37:27Critical(3)"SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:10:10:11:51:41;CM-QOS=1.1;CM-VER=3.1;"
Message 16 of 16