Intermittent connection loss.

Hello all,

I am seeing intermittent connection drops. Sometimes I notice it once daily, and sometimes (like today) it's once every 10-15 minutes. It seems like the drops happen more frequently when I'm doing video conferencing or streaming something, but this could just be my subjective experience and may not be related to the true root cause of the issue. This has been occurring for a little under a year. I have finally had more than enough of it, so I am trying to troubleshoot or at least better equip myself for an inevitable support case with Comcast. They sent a tech out last year when this first occurred, and the issue persisted after that. If I recall correctly, he removed a splitter that was in place from the previous owner here and he replaced it with a grounding block and GLF-1002 POE low-pass filter. Here are metrics from my modem today. The Event Log (at the bottom) includes some drops that occurred today. Any insight is appreciated. From what I've read on the forums it looks like my SNR ranges look okay, but another, more attuned set of eyes may see something I can't. I've redacted any personally identifiable information with Xs in the below data:

Device Information

Cable Specification Version	DOCSIS 3.1
Hardware Version	V1.0
Software Version	8611-19.2.18
Cable Modem MAC Address	XX:XX:XX:XX:XX:XX
Cable Modem Serial Number	XXXX-MB8611-XX-XXXX
CM Certificate	Installed
	Prod_19.2_d31

Connection

Startup Sequence

Startup Step	Status	Comment
Acquire Downstream Channel	441000000 Hz	Locked
Upstream Connection	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+

Connection Status

System Up Time	0 days 00h:24m:22s
Network Access	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	1	441.0	-14.6	38.1	21942	23315
2	Locked	QAM256	2	447.0	-15.1	37.6	24674	23595
3	Locked	QAM256	3	453.0	-15.3	37.6	18875	22917
4	Locked	QAM256	4	459.0	-15.7	37.2	87341	46087
5	Locked	QAM256	5	465.0	-15.4	37.6	296222	116947
6	Locked	QAM256	6	471.0	-15.8	37.3	232530	94048
7	Locked	QAM256	7	477.0	-15.6	37.3	273111	108980
8	Locked	QAM256	8	483.0	-15.6	37.4	314465	126462
9	Locked	QAM256	9	489.0	-15.9	37.3	233513	98759
10	Locked	QAM256	10	495.0	-15.7	37.5	309695	124946
11	Locked	QAM256	11	507.0	-16.1	37.4	316938	126039
12	Locked	QAM256	12	513.0	-16.0	37.3	369178	138927
13	Locked	QAM256	13	519.0	-16.3	37.1	331531	126402
14	Locked	QAM256	14	525.0	-16.2	37.2	294705	116728
15	Locked	QAM256	15	531.0	-16.4	37.0	284112	115211
16	Locked	QAM256	16	537.0	-15.9	37.5	252290	102161
17	Locked	QAM256	17	543.0	-15.9	37.2	316814	116212
18	Locked	QAM256	18	555.0	-15.4	37.6	186798	77905
19	Locked	QAM256	19	561.0	-15.5	37.6	250117	97668
20	Locked	QAM256	20	567.0	-14.7	38.0	226684	89325
21	Locked	QAM256	21	573.0	-15.1	37.8	243908	94693
22	Locked	QAM256	22	579.0	-14.7	38.0	258173	95356
23	Locked	QAM256	23	585.0	-14.0	38.4	208752	82416
24	Locked	QAM256	24	591.0	-14.2	37.9	208761	80320
25	Locked	QAM256	25	597.0	-13.6	38.5	207691	79900
26	Locked	QAM256	26	603.0	-13.8	38.4	230128	87654
27	Locked	QAM256	27	609.0	-13.4	38.6	208972	79792
28	Locked	QAM256	28	615.0	-13.3	38.6	209830	78215
29	Locked	QAM256	29	621.0	-13.8	38.1	228322	83747
30	Locked	QAM256	30	627.0	-13.1	38.6	198321	74211
31	Locked	QAM256	31	633.0	-13.3	38.4	206763	76676
32	Locked	OFDM PLC	33	693.0	-12.1	37.5	7864599	24290

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	2	5120	16.3	58.5
2	Locked	SC-QAM	3	5120	22.8	58.5
3	Locked	SC-QAM	4	5120	29.2	58.5
4	Locked	SC-QAM	5	5120	35.6	58.5
5	Locked	SC-QAM	6	2560	40.4	55.5

Downstream Frequency Setting

Downstream Frequency Select

Event Log

Time	Priority	Description
10:37:11 Fri Jul 14 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:37:25 Fri Jul 14 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;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:XX;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
10:50:00 Fri Jul 14 2023	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:50:08 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:50:22 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:50:44 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:50:55 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:50:57 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:51:07 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:51:44 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:52:13 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:52:14 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:52:27 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:53:26 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:54:06 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:55:30 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:55:36 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:55:37 Fri Jul 14 2023	Warning (5)	MDD message timeout;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:56:03 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 21 23 24 28; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:56:16 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:57:02 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
10:59:39 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:00:26 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:01:11 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:01:40 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:03:01 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:03:22 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:06:47 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:10:51 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:18:30 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;

Responses

EG

Expert

•

110.4K Messages

2 years ago

The downstream power and the upstream levels are way out of spec. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

Good luck with it !

stuntmachine

Visitor

•

3 Messages

2 years ago

I just had another intermittent outage, and here's the associated Event Log and connection info (while it was happening):

Event Log

Time	Priority	Description
11:41:31 Fri Jul 14 2023	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:41:33 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:41:34 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:41:39 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:41:45 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:41:52 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:41:56 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 8; Chan ID: 3 5 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:42:23 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:42:27 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 8; Chan ID: 3 5 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:42:34 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:43:57 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 8; Chan ID: 3 5 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:23 Fri Jul 14 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:31 Fri Jul 14 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:32 Fri Jul 14 2023	Critical (3)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:33 Fri Jul 14 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:36 Fri Jul 14 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:38 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:38 Fri Jul 14 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:38 Fri Jul 14 2023	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:39 Fri Jul 14 2023	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:45:53 Fri Jul 14 2023	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
11:46:02 Fri Jul 14 2023	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:07 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:12 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:29 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:34 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:34 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:38 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:39 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:45 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:47 Fri Jul 14 2023	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;
11:46:47 Fri Jul 14 2023	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=00:01:5c:85:7e:66;CM-QOS=1.1;CM-VER=3.1;

Connection

Startup Sequence

Startup Step	Status	Comment
Acquire Downstream Channel	441000000 Hz	Locked
Upstream Connection	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+

Connection Status

System Up Time	0 days 00h:51m:55s
Network Access	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	1	441.0	-12.9	39.2	26239	26584
2	Locked	QAM256	2	447.0	-13.3	38.9	29450	27869
3	Locked	QAM256	3	453.0	-13.6	38.8	25861	32860
4	Locked	QAM256	4	459.0	-14.1	38.4	95006	58884
5	Locked	QAM256	5	465.0	-13.9	38.7	308819	142937
6	Locked	QAM256	6	471.0	-14.5	38.2	245114	119377
7	Locked	QAM256	7	477.0	-14.6	38.1	280652	122342
8	Locked	QAM256	8	483.0	-14.8	38.0	326450	151309
9	Locked	QAM256	9	489.0	-15.4	37.6	245904	124025
10	Locked	QAM256	10	495.0	-15.5	37.6	321996	150034
11	Locked	QAM256	11	507.0	-15.8	37.5	329108	151453
12	Locked	QAM256	12	513.0	-15.5	37.7	381164	163587
13	Locked	QAM256	13	519.0	-15.5	37.8	343427	150919
14	Locked	QAM256	14	525.0	-15.1	38.0	306312	139937
15	Locked	QAM256	15	531.0	-15.0	38.0	295833	138968
16	Locked	QAM256	16	537.0	-14.3	38.5	263640	125059
17	Locked	QAM256	17	543.0	-14.3	38.4	328558	140426
18	Locked	QAM256	18	555.0	-13.9	38.6	197933	101532
19	Locked	QAM256	19	561.0	-14.1	38.6	261214	121455
20	Locked	QAM256	20	567.0	-13.3	38.8	237115	111133
21	Locked	QAM256	21	573.0	-13.8	38.6	255026	118673
22	Locked	QAM256	22	579.0	-13.3	38.8	269177	117939
23	Locked	QAM256	23	585.0	-12.7	39.1	219547	104495
24	Locked	QAM256	24	591.0	-13.0	39.0	219280	101772
25	Locked	QAM256	25	597.0	-12.5	39.1	215394	96255
26	Locked	QAM256	26	603.0	-12.7	38.9	240718	109887
27	Locked	QAM256	27	609.0	-12.3	39.2	219485	100778
28	Locked	QAM256	28	615.0	-12.3	39.2	217618	95000
29	Locked	QAM256	29	621.0	-12.8	38.7	239053	105687
30	Locked	QAM256	30	627.0	-12.2	39.1	208538	94722
31	Locked	QAM256	31	633.0	-12.4	38.9	217114	97315
32	Locked	OFDM PLC	33	693.0	-11.6	37.7	22984872	39289

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	2	5120	16.3	58.5
2	Locked	SC-QAM	3	5120	22.8	58.5
3	Locked	SC-QAM	4	5120	29.2	58.5
4	Locked	SC-QAM	5	5120	35.6	58.5
5	Not Locked	SC-QAM	6	2560	40.4	55.5

Downstream Frequency Setting

Downstream Frequency Select

EG

Expert

•

110.4K Messages

2 years ago

Posting that stuff again is unnecessary at this point. The signal / connection quality problem is quite clear. See if any of those self-troubleshooting tips apply.

stuntmachine

Visitor

•

3 Messages

@EG I ended up resolving this (at least it seems so for now) in the most interesting way. I don't have a lot of complex wiring here, it's just coax from the pole outside straight into my house, into a joiner, and to the modem. I don't have TV service or anything of that nature necessitating any other splits. So I disconnected each terminal and sprayed a Deoxit D5 onto the copper, wiped the copper with a cotton swab, and while I was at it, hit the threads on each connector with a cloth. I shook each connection out and dried them one last time before reconnecting. I did this at the coax from the outside to the low-pass filter, low-pass filter to the joiner, and joiner to the connection to the modem. At the modem, I did the same in the house. Now I'm getting the following connection metrics (note the number of Corrected and Uncorrected errors is now at 0 (it's been this way for about 13 minutes). I want to say I solved this with a can of contact cleaner solution, but that seems far too simple. I am posting here in case this helps others with similar issues. @EG if you think there is anything else in the originally posted logs that could be part of the problem, please let me know so we don't mislead folks here into thinking they need to run out and buy a can of spray.

Connection

Startup Sequence

Startup Step	Status	Comment
Acquire Downstream Channel	621000000 Hz	Locked
Upstream Connection	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enabled	BPI+

Connection Status

System Up Time	0 days 00h:13m:38s
Network Access	Allowed

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	29	621.0	4.2	41.6	0	0
2	Locked	QAM256	1	441.0	4.8	42.2	0	0
3	Locked	QAM256	2	447.0	4.5	42.2	0	0
4	Locked	QAM256	3	453.0	4.4	42.3	0	0
5	Locked	QAM256	4	459.0	4.5	42.3	0	0
6	Locked	QAM256	5	465.0	4.7	42.2	0	0
7	Locked	QAM256	6	471.0	4.4	42.2	0	0
8	Locked	QAM256	7	477.0	3.8	42.0	0	0
9	Locked	QAM256	8	483.0	3.6	41.9	0	0
10	Locked	QAM256	9	489.0	3.1	41.7	0	0
11	Locked	QAM256	10	495.0	2.6	41.5	0	0
12	Locked	QAM256	11	507.0	2.7	41.6	0	0
13	Locked	QAM256	12	513.0	3.0	41.8	0	0
14	Locked	QAM256	13	519.0	3.2	41.7	0	0
15	Locked	QAM256	14	525.0	3.4	41.6	0	0
16	Locked	QAM256	15	531.0	3.8	41.8	0	0
17	Locked	QAM256	16	537.0	4.1	41.9	0	0
18	Locked	QAM256	17	543.0	4.3	41.7	0	0
19	Locked	QAM256	18	555.0	4.3	41.8	0	0
20	Locked	QAM256	19	561.0	4.5	41.9	0	0
21	Locked	QAM256	20	567.0	4.4	41.8	0	0
22	Locked	QAM256	21	573.0	4.3	41.6	0	0
23	Locked	QAM256	22	579.0	4.5	41.7	0	0
24	Locked	QAM256	23	585.0	4.7	41.8	0	0
25	Locked	QAM256	24	591.0	4.8	41.7	0	0
26	Locked	QAM256	25	597.0	4.6	41.6	0	0
27	Locked	QAM256	26	603.0	4.6	41.7	0	0
28	Locked	QAM256	27	609.0	4.7	41.8	0	0
29	Locked	QAM256	28	615.0	4.5	41.7	0	0
30	Locked	QAM256	30	627.0	4.1	41.6	0	0
31	Locked	QAM256	31	633.0	4.2	41.7	0	0
32	Locked	OFDM PLC	33	693.0	3.9	41.0	6459895	0

Upstream Bonded Channels

Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	SC-QAM	2	5120	16.3	39.5
2	Locked	SC-QAM	3	5120	22.8	39.3
3	Locked	SC-QAM	4	5120	29.2	39.0
4	Locked	SC-QAM	5	5120	35.6	38.3
5	Locked	SC-QAM	6	2560	40.4	38.3

(edited)

2 years ago

EG

Expert

•

110.4K Messages

2 years ago

Looks good ! The cleaner may or may not have been the answer. Just disturbing / refreshing / re-tightening the connections / hardware may have done it. Or it could have been both or neither. Possibly a coincidence ? There may be something intermittent going on farther up the line somewhere.

Hope it holds up for you. Good like. Please post back here if the problem returns.

Your Home Network

stuntmachine

Intermittent connection loss.

EG

stuntmachine

EG

stuntmachine

EG

New to the Community?