NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
duckware
Oct 18, 2021Prodigy
What does "CCAP Commanded Power in Excess of 6 dB Below..." mean?
"RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW" means exactly what? Often seen with "Dynamic Range Window violation" and "Started Unicast Maint...
- Jun 28, 2022
Finally, after a ton of tech visits, the ultimate problem causing this issue has been found: A bad cable from the top of the telephone pole (at the tap) running 15' to the base of the telephone pole (ground block). For full details (and more), visit: https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
duckware
Oct 18, 2021Prodigy
2021-10-16, 12:33:33 Warning (5) Dynamic Range Window violation
2021-10-16, 12:33:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 12:33:33 Warning (5) Dynamic Range Window violation
2021-10-16, 12:33:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 12:33:33 Warning (5) Dynamic Range Window violation
2021-10-16, 12:33:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 12:33:33 Warning (5) Dynamic Range Window violation
2021-10-16, 12:33:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 12:33:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 11:14:17 Warning (5) Dynamic Range Window violation
2021-10-16, 11:14:17 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 11:14:17 Warning (5) Dynamic Range Window violation
2021-10-16, 11:14:17 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-16, 11:14:17 Warning (5) Dynamic Range Window violation
2021-10-16, 11:14:17 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-14, 12:02:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-14, 11:52:11 Warning (5) Dynamic Range Window violation
2021-10-14, 11:52:11 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-14, 11:27:35 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-14, 11:27:33 Warning (5) Dynamic Range Window violation
2021-10-14, 11:27:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-14, 11:27:33 Warning (5) Dynamic Range Window violation
2021-10-14, 11:27:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
2021-10-14, 11:27:33 Warning (5) Dynamic Range Window violation
2021-10-14, 11:27:33 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=(MAC);CMTS-MAC=(MAC);CM-QOS=1.1;CM-VER=3.1;
duckware
Oct 18, 2021Prodigy
|
- duckwareOct 18, 2021Prodigy
Comcast has been at this location many times. Sadly, the contractors sometimes left things worse than when they arrived. In my own research, I have learned more than I ever wanted to know about the impact of bad F-connectors and loose connectors. I ended up doing a full 'audit' of every run, every connector, everywhere (even behind wall plates), etc. I found some very bad workmanship on connectors and fixed. I thought that had eliminated all problems, but something minor remains. Still looking to understand the true meaning of "RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW". I found a video by a couple of SCTE stating that this means the CMTS asked for the cable modem to transmit at too LOW a power level, but trying to verify.
- plemansOct 18, 2021Guru - Experienced User
Its in regards to a ranging request and the power levels. You can get indepth details at the cable labs spec site but its basically between the cmts/modem and what its calling for power levels and what those levels should be at.
https://www.cablelabs.com/specifications/search
do you have any errors in the downstream?
What does your docsis 3.1 ofdma channels look like?
(for testing) if you just direct connect to where the coax enters the home (without the splitter), do you still get the errors?
It definitely could be an issue with the modem. Especially if other modems don't have it.
Did you try any of netgears other docsis 3.1 modems?
- duckwareOct 18, 2021Prodigy
There are *zero* downstream "Correctable Codewords" and "Uncorrectable Codewords" -- until 'the event' happens. Then maybe 100 or so codeword issues per channel. And then no more codeword issues until the next event.
OFDMA download channel looks good. power=4.9 snr=39.5. No "Uncorrectable Codewords" until an event happens, then only a handful until the next event.
Yes, connected modem directly (via new 100' cable) to cable demarc location and still see the issue.
I see the same issue with two different CM1000V2 modems, at two different locations (one in FL and one in GA). Yes, I guess the modem could be bad, but seeing this in two different locations and two different ISP's makes me think something else is going on.
The issue is not seen with other vendor's D3.0 modems, as that message seems specific to this NG 3.1 modem. No, have not (yet) tried other D3.1 modems from Netgear.