CM2000 event log

Question

Only showing these eight entries, in the event log and the top one gets overwritten 2-3x a day. Anyone have any ideas?&nbsp;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 = IPv6Time 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 docsDevResetNowFri 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 · Answer

Your logs indicate line issues.&nbsp;
So it can be any number of things.&nbsp;
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.&nbsp;
&nbsp;
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 · Answer

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 · Answer

Old_Soldier&nbsp;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?&nbsp;
Could be if a couple people are having the same issue, it might put additional pressure on them to recheck the line/hub

plemans · Answer

got a copy of the screensnip of the cable connections page?&nbsp;
From the event log, your power level is going out of optimal range and then having signal issues back to the isp.&nbsp;
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 · Answer

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;

Forum Discussion

CM2000 event log

10 Replies