CM2000 multiple events and unicast error

[kerNol]

So I’ve had the CM2000 in operation for about a year with no issues. My local ISP has been doing massive upgrades recently and these began, they’ve been out multiple times and can’t seem to find any answers. I periodically have massive slow downs and drops. Here’s the most recent log, there was a restart in there somewhere when I moved some equipment around.

Fri Dec 02 20:32:03 2022 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Fri Dec 02 16:30:21 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Fri Dec 02 16:29:58 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Fri Dec 02 14:50:18 2022 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 01 23:37:28 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 01 23:37:04 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 01 19:00:26 2022 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 01 13:12:18 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 4; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Thu Dec 01 13:12:00 2022 (Warning (5)) MDD message timeout;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 21:46:22 2022 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 15:38:41 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 15:37:52 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 14:44:52 2022 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 14:44:30 2022 (Error (4)) Improper Configuration File CVC Format
Wed Nov 30 14:44:28 2022 (Warning (5)) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 14:44:25 2022 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 14:44:21 2022 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 30 14:44:20 2022 (Warning (5)) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv4
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 13:06:23 2022 (Critical (3)) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 13:06:19 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 13:05:44 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 13:05:12 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 13:01:07 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 13:00:30 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:58:08 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:57:08 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:56:53 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:56:44 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 23; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:56:44 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:55:45 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:55:36 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:55:18 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:52:14 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 22; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:52:01 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 20; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:05:10 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 12:04:12 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 10:23:26 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 24; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;
Sun Nov 27 10:22:38 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 16; Chan ID: 25; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=80:cc:9c:ad:0b:f8;CMTS-MAC=00:01:5c:7b:3a:56;CM-QOS=1.1;CM-VER=3.1;

[plemans]

Its much easier to read a screen snip. 

Also include your cable connections page. 

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.