NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Old_Soldier
Mar 16, 2024Apprentice
CM2000 event log
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 (Warn...
plemans
Mar 16, 2024Guru - Experienced User
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
Mar 16, 2024Apprentice
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; |