NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Frizzel's avatar
Frizzel
Initiate
Oct 19, 2017

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" err...
Firmware
Troubleshooting
OrbiWANKenobi's avatar
OrbiWANKenobi
Star
Dec 06, 2017

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.

n4cho's avatar
n4cho
Apprentice
Dec 09, 2017

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

  • n4cho's avatar
    n4cho
    Apprentice
    Dec 09, 2017

    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;