CM2000 event log

[Old_Soldier]

Only showing these eight entries, in the event log and the top one gets overwritten 2-3x a day. Anyone have any ideas?

Time Priority Description Sat Mar 16 05:20:47 2024 (Warning (5)) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1; Tue Mar 12 14:57:15 2024 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1; Tue Mar 12 14:57:09 2024 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;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=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;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=94:18:65:a5:69:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Tue Mar 12 14:56:01 2024 (Critical (3)) Resetting the cable modem due to docsDevResetNow Fri Mar 08 02:31:44 2024 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;

[plemans]

got a copy of the screensnip of the cable connections page? 

From the event log, your power level is going out of optimal range and then having signal issues back to the isp. 

Start with removing any amplifiers, signal attenuators, or splitters from the coax.
From there check the line for kinks, damage, moisture in the line.
Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.

[Old_Soldier]

I'm on Xfinity and have been going around and around with them to solve an intermitant problem, for the past month. I've had four techs out and one was here, twice. He's the one that actually did anything, that helped. He removed an unneeded splitter, connected a new underground cable, from the pedestal to the distribution boxes, after checking connections there. No ampifiers in use, either. Working theory is in wall coax is sketchy and since I live in an apartment complex, there's nothing more that can be done, as yet.

Just rebooted the modem, because of websites weren't loading completely.

Current log:

Sat Mar 16 10:57:28 2024	(Warning (5))	RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 16 10:42:15 2024	(Notice (6))	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 16 10:42:08 2024	(Notice (6))	TLV-11 - unrecognized OID;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;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=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;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=94:18:65:a5:69:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sat Mar 16 10:40:59 2024	(Critical (3))	Resetting the cable modem due to docsDevResetNow
Time Not Established	(Critical (3))	No Ranging Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;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=94:18:65:a5:69:13;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 14:56:01 2024	(Critical (3))	Resetting the cable modem due to docsDevResetNow
Fri Mar 08 02:31:44 2024	(Critical (3))	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=94:18:65:a5:69:13;CMTS-MAC=00:01:5c:a8:e0:4e;CM-QOS=1.1;CM-VER=3.1;

[Old_Soldier]

I've cleared the logs, twice, since 1 March. Number of log entries doesn't change much, except for the RNG-RSP entry continually overwriting the previous one.

[Old_Soldier]

Procedure Status Comment Acquire Downstream Channel 507000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD IPv6 only

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 5 507000000 Hz -0.1 dBmV 37.4 dB 0 0 2 Locked QAM256 2 489000000 Hz -0.3 dBmV 37.3 dB 0 0 3 Locked QAM256 3 495000000 Hz -0.2 dBmV 37.4 dB 0 0 4 Locked QAM256 4 501000000 Hz -0.1 dBmV 37.4 dB 0 0 5 Locked QAM256 6 513000000 Hz 0.0 dBmV 37.4 dB 0 0 6 Locked QAM256 7 519000000 Hz 0.0 dBmV 37.4 dB 0 0 7 Locked QAM256 8 525000000 Hz -0.1 dBmV 37.3 dB 0 0 8 Locked QAM256 9 531000000 Hz -0.1 dBmV 37.3 dB 0 0 9 Locked QAM256 10 537000000 Hz 0.0 dBmV 37.3 dB 0 0 10 Locked QAM256 11 543000000 Hz -0.1 dBmV 37.3 dB 0 0 11 Locked QAM256 12 549000000 Hz -0.1 dBmV 37.3 dB 0 0 12 Locked QAM256 13 555000000 Hz 0.0 dBmV 37.4 dB 0 0 13 Locked QAM256 14 561000000 Hz 0.1 dBmV 37.5 dB 0 0 14 Locked QAM256 15 567000000 Hz 0.2 dBmV 37.4 dB 0 0 15 Locked QAM256 16 573000000 Hz 0.2 dBmV 37.5 dB 0 0 16 Locked QAM256 17 579000000 Hz 0.1 dBmV 37.4 dB 0 0 17 Locked QAM256 18 585000000 Hz 0.1 dBmV 37.1 dB 0 0 18 Locked QAM256 19 591000000 Hz 0.2 dBmV 37.4 dB 0 0 19 Locked QAM256 20 597000000 Hz 0.1 dBmV 37.5 dB 0 0 20 Locked QAM256 21 603000000 Hz 0.1 dBmV 37.5 dB 0 0 21 Locked QAM256 22 609000000 Hz 0.2 dBmV 37.6 dB 0 0 22 Locked QAM256 23 615000000 Hz 0.0 dBmV 37.6 dB 0 0 23 Locked QAM256 24 621000000 Hz -0.1 dBmV 37.6 dB 0 0 24 Locked QAM256 25 627000000 Hz -0.2 dBmV 37.6 dB 0 0 25 Locked QAM256 26 633000000 Hz -0.5 dBmV 37.6 dB 0 0 26 Locked QAM256 27 639000000 Hz -0.6 dBmV 37.7 dB 0 0 27 Locked QAM256 28 645000000 Hz -0.6 dBmV 37.9 dB 0 0 28 Locked QAM256 29 651000000 Hz -1.2 dBmV 37.8 dB 0 0 29 Locked QAM256 30 657000000 Hz -1.3 dBmV 37.8 dB 0 0 30 Locked QAM256 31 663000000 Hz -1.6 dBmV 37.8 dB 0 0 31 Locked QAM256 32 669000000 Hz -2.0 dBmV 37.7 dB 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

Upstream Bonded Channels

Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 35600000 Hz 42.5 dBmV 2 Locked ATDMA 4 5120 Ksym/sec 16400000 Hz 41.8 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 42.5 dBmV 4 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 42.3 dBmV 5 Locked ATDMA 9 1280 Ksym/sec 39600000 Hz 42.5 dBmV 6 Not Locked Unknown 0 0 0 0.0 dBmV 7 Not Locked Unknown 0 0 0 0.0 dBmV 8 Not Locked Unknown 0 0 0 0.0 dBmV

Downstream OFDM Channels

Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0 ,1 ,2 ,3 37 690000000 Hz -0.02 dBmV 37.7 dB 1108 ~ 2987 46148216 46121477 0 2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0

Upstream OFDMA Channels

Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV

Extended Upstream Transmit Power

Current System Time:Sat Mar 16 11:25:12 2024 System Up Time:00:43:46

[Old_Soldier]

Cable status shows as good. CM, downstream and upstream show green.

[Old_Soldier]

@plemansHave you had a chance to look at the data, yet? Still getting the RNG-RSP error and waiting on Xfinity to do something constructive, aside from what's been done. TIA

[plemans]

Your logs indicate line issues. 

So it can be any number of things. 

1. It could be the modem. Always a chance but usually not

2. the line/connectors. Even if they replaced them, it could've been a poor job/technician doing it. Not the first time

3. the hub. I've seen them loose at the hub. 

You're a little caught. Xfinity isn't going to try very hard because you're not using their device. I've had to actually rent one of there devices to come check my line again (because it still had issues)

[Old_Soldier]

I had one of their xb8 gateways and still had the same problems. I'm convinced it's back up the line at the CMTS, whereever it is. Nobody wants to actually go there and have a look, though, from what I'm getting.

[plemans]

---

@Old_Soldier wrote:

I had one of their xb8 gateways and still had the same problems. I'm convinced it's back up the line at the CMTS, whereever it is. Nobody wants to actually go there and have a look, though, from what I'm getting.

---

If their XB8 and the CM2000 have the same issue, it reduces the odds of it being the modem. You're a little caught as ISP's fight not to do more than they have to.

Live by anyone else that is having the same issue? 

Could be if a couple people are having the same issue, it might put additional pressure on them to recheck the line/hub

[Old_Soldier]

Sorry about not replying sooner, dealing with family problems, right now. To answer your question, no, I don't know of anyone else in the building that is on Xfinity that is having trouble. I strongly suspect that they don't know, don't use the internet as much as I do or just haven't bothered to complain to Xfinity. Support is looking into why the event log has so few entries, compared to the Motorola MB8611 I have and its been elevated to tier 2. As far as Xfinity goes, they've done nothing at all, beyond sending three techs out, one twice and promised to contact the complex manager, which hasn't happened either.