NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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.
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.
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 dBSo 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 connectSo 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.
some of your downstreams are a little high they should be -7 to +7 dBmV. for the best connection.
DarrneM
I just started receiving the same errors and issues, reboots and disconnects multiple times a day. Just started yesterday.. real bummer :( 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
Procedure Status Comment Acquire Downstream Channel 729000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv6 only <tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 21 729000000 Hz 6.2 dBmV 40.3 dB 48754675 0 0 2 Locked QAM256 1 609000000 Hz 8.1 dBmV 41.0 dB 47253420 0 0 3 Locked QAM256 2 615000000 Hz 7.7 dBmV 40.9 dB 47261941 0 0 4 Locked QAM256 3 621000000 Hz 7.9 dBmV 41.0 dB 47271046 0 0 5 Locked QAM256 4 627000000 Hz 7.4 dBmV 40.9 dB 47280141 0 0 6 Locked QAM256 5 633000000 Hz 7.4 dBmV 40.6 dB 47285916 0 0 7 Locked QAM256 6 639000000 Hz 7.2 dBmV 40.7 dB 47299161 0 0 8 Locked QAM256 7 645000000 Hz 7.1 dBmV 40.6 dB 47307951 0 0 9 Locked QAM256 8 651000000 Hz 6.9 dBmV 40.5 dB 47317712 0 0 10 Locked QAM256 9 657000000 Hz 6.9 dBmV 40.5 dB 47326996 0 0 11 Locked QAM256 10 663000000 Hz 6.9 dBmV 40.4 dB 47336669 0 0 12 Locked QAM256 11 669000000 Hz 7.0 dBmV 40.6 dB 47345598 0 0 13 Locked QAM256 12 675000000 Hz 7.1 dBmV 40.1 dB 47355716 0 0 14 Locked QAM256 13 681000000 Hz 6.9 dBmV 40.3 dB 47363949 0 0 15 Locked QAM256 14 687000000 Hz 7.2 dBmV 40.6 dB 47373438 0 0 16 Locked QAM256 15 693000000 Hz 6.9 dBmV 40.2 dB 47382707 0 0 17 Locked QAM256 16 699000000 Hz 6.8 dBmV 40.2 dB 47380079 0 0 18 Locked QAM256 17 705000000 Hz 6.7 dBmV 40.5 dB 47410399 0 0 19 Locked QAM256 18 711000000 Hz 6.4 dBmV 40.4 dB 47419980 0 0 20 Locked QAM256 19 717000000 Hz 6.2 dBmV 40.3 dB 47428801 0 0 21 Locked QAM256 20 723000000 Hz 5.9 dBmV 40.3 dB 47430581 0 0 22 Locked QAM256 22 735000000 Hz 5.5 dBmV 40.2 dB 47438250 0 0 23 Locked QAM256 23 741000000 Hz 5.9 dBmV 40.2 dB 47444370 0 0 24 Locked QAM256 24 747000000 Hz 5.3 dBmV 40.1 dB 47449904 0 0 25 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 26 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 27 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 28 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 29 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 30 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 <tabindex=-1>Upstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 1 35800000 Hz 49.5 dBmV 2 Locked ATDMA 2 29400000 Hz 50.0 dBmV 3 Locked ATDMA 3 23000000 Hz 50.0 dBmV 4 Not Locked Unknown 0 0 Hz 0.0 dBmV 5 Not Locked Unknown 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV <tabindex=-1>Downstream OFDM Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Not Locked Unknown 0 0 Hz 0 dBmV 0 dB 0 ~ 0 0 0 0 2 Not Locked Unknown 0 0 Hz 0 dBmV 0 dB 0 ~ 0 0 0 0 <tabindex=-1>Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV 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.
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
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 Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 21 615000000 Hz 5.7 dBmV 40.9 dB -2095552163 30 0 2 Locked QAM256 1 483000000 Hz 9.4 dBmV 43.4 dB -2096788438 2 0 3 Locked QAM256 2 489000000 Hz 9.4 dBmV 43.4 dB -2096781228 0 0 4 Locked QAM256 3 495000000 Hz 9.2 dBmV 43.1 dB -2096769579 0 0 5 Locked QAM256 4 501000000 Hz 9.4 dBmV 43.4 dB -2096761459 2 0 6 Locked QAM256 5 507000000 Hz 9.1 dBmV 43.3 dB -2096751948 0 0 7 Locked QAM256 6 513000000 Hz 8.8 dBmV 43.2 dB -2096742665 1 0 8 Locked QAM256 7 525000000 Hz 8.1 dBmV 43.0 dB -2096734065 1 0 9 Locked QAM256 8 531000000 Hz 7.7 dBmV 43.0 dB -2096606626 0 0 10 Locked QAM256 9 537000000 Hz 7.8 dBmV 42.6 dB -2096597326 0 0 11 Locked QAM256 10 543000000 Hz 7.5 dBmV 42.7 dB -2096587983 1 0 12 Locked QAM256 11 555000000 Hz 7.4 dBmV 42.5 dB -2096577850 5 0 13 Locked QAM256 12 561000000 Hz 7.4 dBmV 42.4 dB -2096568755 6 0 14 Locked QAM256 13 567000000 Hz 7.2 dBmV 42.4 dB -2096558194 6 0 15 Locked QAM256 14 573000000 Hz 7.4 dBmV 42.5 dB -2096551065 8 0 16 Locked QAM256 15 579000000 Hz 6.9 dBmV 42.1 dB -2096539758 10 0 17 Locked QAM256 16 585000000 Hz 6.8 dBmV 41.8 dB -2096394327 8 0 18 Locked QAM256 17 591000000 Hz 6.5 dBmV 41.9 dB -2096383960 23 0 19 Locked QAM256 18 597000000 Hz 6.3 dBmV 41.4 dB -2096374142 19 0 20 Locked QAM256 19 603000000 Hz 6.2 dBmV 41.4 dB -2096365796 18 0 21 Locked QAM256 20 609000000 Hz 5.9 dBmV 41.3 dB -2096356192 27 0 22 Locked QAM256 22 621000000 Hz 5.4 dBmV 40.4 dB -2096347005 51 0 23 Locked QAM256 23 627000000 Hz 5.4 dBmV 40.6 dB -2096336737 35 0 24 Locked QAM256 24 633000000 Hz 5.5 dBmV 40.6 dB -2096326700 37 0 25 Locked QAM256 25 639000000 Hz 5.5 dBmV 40.3 dB -2096288747 35 0 26 Locked QAM256 26 645000000 Hz 5.5 dBmV 40.3 dB -2096279344 36 0 27 Locked QAM256 27 651000000 Hz 5.3 dBmV 40.3 dB -2096269879 35 0 28 Locked QAM256 28 657000000 Hz 5.0 dBmV 40.2 dB -2096260893 71 0 29 Locked QAM256 29 663000000 Hz 4.9 dBmV 40.0 dB -2096251374 71 0 30 Locked QAM256 30 669000000 Hz 4.8 dBmV 40.0 dB -2096244899 72 0 31 Locked QAM256 31 675000000 Hz 4.9 dBmV 38.7 dB -2096238828 67 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
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
I forgot to post some log fun;
Time Priority Description 2017-12-08, 18:53:09 Warning (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:09 Warning (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:04 Notice (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 Established Notice (6) Honoring MDD; IP provisioning mode = IPv6 Time Not Established Critical (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 Established Critical (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:24 Critical (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:42 Critical (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:03 Critical (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:58 Critical (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:39 Critical (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:38 Critical (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:19 Critical (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:18 Critical (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:59 Critical (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:58 Critical (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:11 Critical (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:05 Critical (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:01 Critical (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:13 Critical (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:04 Critical (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:04 Critical (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:54 Critical (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:53 Critical (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:44 Critical (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:44 Critical (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:34 Critical (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:33 Critical (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:14 Critical (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:13 Critical (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:25 Critical (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:35 Critical (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:34 Critical (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:35 Critical (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:45 Critical (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:55 Critical (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:46 Critical (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:44 Critical (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:49 Critical (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:47 Critical (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;
