Experiencing packet loss and loss connection

[yahdoneson1247]

Wed Sep 22 17:45:55 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 16:57:50 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 16:53:26 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 15:49:35 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 15:48:44 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 14:50:29 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 14:49:59 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 14:45:29 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 14:42:21 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 12:30:16 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 12:28:07 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 12:22:14 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 12:21:17 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 11:42:28 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 11:41:51 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 10:52:59 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 10:52:19 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 08:33:53 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 08:32:21 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 06:56:54 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 06:56:48 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 06:48:39 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Wed Sep 22 06:48:26 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 20:30:28 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 20:29:02 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 20:17:58 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 18:54:00 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 17:46:22 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 17:39:14 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 17:26:28 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 17:19:25 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 17:14:17 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 16:31:57 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 16:26:10 2021	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 16:26:05 2021	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 16:26:05 2021	Error (4)	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Tue Sep 21 16:26:05 2021	Error (4)	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;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=28:80:88:b3:ac:f0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

Good evening,

I am experiencing network packet loss and loss connections, I am wondering if my modem is what is causing. My ISP came out two days ago and everything up to the modem was checked out by them and no problems detected.

Are these errors causing my problem? 

[yahdoneson1247]

 
Apply               Cancel     
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency	
0
 
Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	759000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enabled	BPI+
IP Provisioning Mode	IPv6 Only	ipv6Only(1)
 
Downstream Bonded Channels
Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	20	759000000 Hz	5.7 dBmV	37.4 dB	46	0
2	Locked	QAM256	2	651000000 Hz	5.9 dBmV	38.4 dB	81	0
3	Locked	QAM256	3	657000000 Hz	5.8 dBmV	38.2 dB	77	0
4	Locked	QAM256	4	663000000 Hz	5.8 dBmV	38 dB	86	0
5	Locked	QAM256	5	669000000 Hz	6.1 dBmV	38.1 dB	78	0
6	Locked	QAM256	6	675000000 Hz	5.9 dBmV	37.8 dB	75	0
7	Locked	QAM256	7	681000000 Hz	5.9 dBmV	38 dB	100	0
8	Locked	QAM256	8	687000000 Hz	6 dBmV	38 dB	91	0
9	Locked	QAM256	9	693000000 Hz	5.8 dBmV	37.9 dB	85	0
10	Locked	QAM256	10	699000000 Hz	5.8 dBmV	38 dB	67	0
11	Locked	QAM256	11	705000000 Hz	5.9 dBmV	37.9 dB	69	0
12	Locked	QAM256	12	711000000 Hz	5.9 dBmV	37.9 dB	67	0
13	Locked	QAM256	13	717000000 Hz	6 dBmV	37.8 dB	80	0
14	Locked	QAM256	14	723000000 Hz	5.7 dBmV	37.6 dB	60	0
15	Locked	QAM256	15	729000000 Hz	5.7 dBmV	37.6 dB	64	0
16	Locked	QAM256	16	735000000 Hz	5.7 dBmV	37.6 dB	62	0
17	Locked	QAM256	17	741000000 Hz	5.8 dBmV	37.7 dB	56	0
18	Locked	QAM256	18	747000000 Hz	5.8 dBmV	37.7 dB	89	0
19	Locked	QAM256	19	753000000 Hz	5.8 dBmV	37.6 dB	65	0
20	Locked	QAM256	21	765000000 Hz	5.5 dBmV	37.5 dB	50	0
21	Locked	QAM256	22	771000000 Hz	5.5 dBmV	37.4 dB	66	0
22	Locked	QAM256	23	777000000 Hz	5.5 dBmV	37.6 dB	122	19
23	Locked	QAM256	24	783000000 Hz	5.4 dBmV	37.4 dB	158	8
24	Locked	QAM256	25	789000000 Hz	5.5 dBmV	37.3 dB	60	0
25	Locked	QAM256	26	795000000 Hz	5.4 dBmV	37.2 dB	52	0
26	Locked	QAM256	27	801000000 Hz	5.3 dBmV	37.2 dB	58	0
27	Locked	QAM256	28	807000000 Hz	5.2 dBmV	37.1 dB	48	0
28	Locked	QAM256	29	813000000 Hz	4.9 dBmV	37 dB	51	0
29	Locked	QAM256	30	819000000 Hz	4.9 dBmV	36.9 dB	46	0
30	Locked	QAM256	31	825000000 Hz	4.9 dBmV	36.8 dB	63	0
31	Locked	QAM256	32	831000000 Hz	5 dBmV	36.7 dB	77	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	5	5120 Ksym/sec	17800000 Hz	45.3 dBmV
2	Locked	ATDMA	6	5120 Ksym/sec	24200000 Hz	45.5 dBmV
3	Locked	ATDMA	7	5120 Ksym/sec	30600000 Hz	46.8 dBmV
4	Locked	ATDMA	8	5120 Ksym/sec	37000000 Hz	47.8 dBmV
5	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
6	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
7	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
8	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
 
Downstream OFDM Channels
Channel	Lock
Status	Modulation /
Profile ID	Channel
ID	Frequency	Power	SNR /
MER	Active Subcarrier
Number Range	Unerrored
Codewords	Correctable
Codewords	Uncorrectable
Codewords
1	Locked	0 ,1 ,2	1	338000000 Hz	5.0 dBmV	40.7 dB	148 ~ 3947	1513168518	1444509750	52297
2	Not Locked	0	0	0 Hz	0 dBmV	0.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
Enable Extended Upstream Transmit Power
 
Current System Time:Wed Sep 22 18:54:26 2021
System Up Time:1 day 02:28:57

Here are my other values from cable connection. 

[plemans]

do you also have a screen snip of the cable connections page? 

The logs are indicating a line issue.

They don't always do the greatest job whent they check a line the first time. 

And if they say it isn't a line issue, it could be a modem issue. You could always try renting one of theirs for a month. If it has issues, then they can't argue that its a modem issue. 

[yahdoneson1247]

So last night I responded to my thread with the cable connections page, however the Netgear website was sturggling quite a bit and it said that it posted, apparently it did not. 

I will post when I get home tonight, from what I do know, 31/32 downstream channels are locked and one is considered unknown. For my upstream channels, 4/8 are active. I am not too versed in understanding what any of that means and searching last night didn't really give me an idea as well. 

Before my ISP showed up I went ahead and got their modem and was going to fiddle with mine a little more before plugging theirs in to see if my modem is causing the problem. The interesting thing for me is that I was running this hardware for around ~45days in this house before we started to see internet problems. Since then, the last month, it's every day. 

I think I may have been lucky last night when I ran a speedtest on my LAN while I was experiencing some issues, and came back with 4mpbs downstream signal. I immediately got on ISP website and was working through the support line and ran the speedtest they needed me to run and we were magically back up to 420-450mbps downstream. 

I appreciate the reply and will post the cable logs. I did check the FW and that is current. If it means anything, my modem then connects to an Asus GT-AX11000 which at this point, I feel like the problem is before my router. 

Thank you

[plemans]

Line issues can be challenging. Even the connections page doesn't always help that much as it takes a brief snip when the page is opened. the logs help because they show longer term (which indicate line issues by the t3 errors). but if there's something obvious on there it helps. 

If the isp's checked the line, try moving the modem to right where the coax enters the home. they rarely look at anything in the home and just ensure the signal is good up to where it goes into the home. After that its on the home owner to ensure the cables/splitters/etc are all in good condition. 

[yahdoneson1247]

The tech checked the lines from the box outside, junction box attached to house, my tele box in garage, and then the line all the way through the house to the modem. He stated, which in previous experience could have been just to get done, that the lines were clean. He even said that testing past the modem was clean, however, same story same dance scenario. 

 
Apply               Cancel     
Frequency start Value
This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
Starting Frequency	
0
 
Startup Procedure
Procedure	Status	Comment
Acquire Downstream Channel	759000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enabled	BPI+
IP Provisioning Mode	IPv6 Only	ipv6Only(1)
 
Downstream Bonded Channels
Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	20	759000000 Hz	5.6 dBmV	37.5 dB	105	0
2	Locked	QAM256	2	651000000 Hz	5.7 dBmV	38.4 dB	140	0
3	Locked	QAM256	3	657000000 Hz	5.5 dBmV	38.2 dB	160	0
4	Locked	QAM256	4	663000000 Hz	5.5 dBmV	38.1 dB	151	0
5	Locked	QAM256	5	669000000 Hz	5.8 dBmV	38.1 dB	155	0
6	Locked	QAM256	6	675000000 Hz	5.6 dBmV	37.7 dB	139	0
7	Locked	QAM256	7	681000000 Hz	5.5 dBmV	38 dB	177	0
8	Locked	QAM256	8	687000000 Hz	5.7 dBmV	38 dB	162	0
9	Locked	QAM256	9	693000000 Hz	5.5 dBmV	38 dB	145	0
10	Locked	QAM256	10	699000000 Hz	5.6 dBmV	37.9 dB	138	0
11	Locked	QAM256	11	705000000 Hz	5.6 dBmV	37.9 dB	132	0
12	Locked	QAM256	12	711000000 Hz	5.6 dBmV	37.9 dB	147	0
13	Locked	QAM256	13	717000000 Hz	5.7 dBmV	37.8 dB	135	0
14	Locked	QAM256	14	723000000 Hz	5.6 dBmV	37.7 dB	124	0
15	Locked	QAM256	15	729000000 Hz	5.7 dBmV	37.7 dB	121	0
16	Locked	QAM256	16	735000000 Hz	5.8 dBmV	37.7 dB	129	0
17	Locked	QAM256	17	741000000 Hz	5.8 dBmV	37.8 dB	109	0
18	Locked	QAM256	18	747000000 Hz	5.8 dBmV	37.7 dB	145	0
19	Locked	QAM256	19	753000000 Hz	5.8 dBmV	37.6 dB	128	0
20	Locked	QAM256	21	765000000 Hz	5.4 dBmV	37.5 dB	99	0
21	Locked	QAM256	22	771000000 Hz	5.4 dBmV	37.5 dB	121	0
22	Locked	QAM256	23	777000000 Hz	5.3 dBmV	37.6 dB	165	19
23	Locked	QAM256	24	783000000 Hz	5.2 dBmV	37.4 dB	209	8
24	Locked	QAM256	25	789000000 Hz	5.2 dBmV	37.4 dB	122	0
25	Locked	QAM256	26	795000000 Hz	5.1 dBmV	37.2 dB	97	0
26	Locked	QAM256	27	801000000 Hz	5.1 dBmV	37.2 dB	107	0
27	Locked	QAM256	28	807000000 Hz	4.9 dBmV	37.1 dB	105	0
28	Locked	QAM256	29	813000000 Hz	4.9 dBmV	37 dB	97	0
29	Locked	QAM256	30	819000000 Hz	4.9 dBmV	36.9 dB	95	0
30	Locked	QAM256	32	831000000 Hz	4.8 dBmV	36.7 dB	120	0
31	Locked	QAM256	33	645000000 Hz	6 dBmV	38.6 dB	134	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	5	5120 Ksym/sec	17800000 Hz	45 dBmV
2	Locked	ATDMA	6	5120 Ksym/sec	24200000 Hz	45.3 dBmV
3	Locked	ATDMA	7	5120 Ksym/sec	30600000 Hz	46.3 dBmV
4	Locked	ATDMA	8	5120 Ksym/sec	37000000 Hz	47 dBmV
5	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
6	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
7	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
8	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0.0 dBmV
 
Downstream OFDM Channels
Channel	Lock
Status	Modulation /
Profile ID	Channel
ID	Frequency	Power	SNR /
MER	Active Subcarrier
Number Range	Unerrored
Codewords	Correctable
Codewords	Uncorrectable
Codewords
1	Locked	0 ,1 ,2	1	338000000 Hz	4.9 dBmV	40.7 dB	148 ~ 3947	2942451253	2838745666	137732
2	Not Locked	0	0	0 Hz	0 dBmV	0.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
Enable Extended Upstream Transmit Power
 
Current System Time:Thu Sep 23 18:34:25 2021
System Up Time:2 days 02:08:54

[yahdoneson1247]

Here is the current event log that corresponds with the cable connection page. 

Also apparently my post from yesterday did come up and I can see it now in the thread showing yesterday. 

Thank you again. 

Time	Priority	Description
Thu Sep 23 18:42:12 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 17:32:52 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 17:32:14 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 16:46:13 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 16:45:34 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 16:18:10 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 16:17:36 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 15:06:12 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 15:01:59 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 14:15:58 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 14:15:51 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 12:20:21 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 12:20:01 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 11:59:18 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 11:58:46 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 10:13:53 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 10:12:43 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 09:34:51 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 09:33:37 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 08:05:26 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 08:04:55 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 07:13:09 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:22:56 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:38 2021	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:38 2021	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:37 2021	Error (4)	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:37 2021	Error (4)	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:28 2021	Notice (6)	Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Thu Sep 23 04:15:16 2021	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:15 2021	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:11 2021	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:15:10 2021	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:14:56 2021	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:14:56 2021	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:14:54 2021	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:12:15 2021	Notice (6)	CM-STATUS message sent. Event Type Code: 8; Chan ID: 6 7 8; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:11:16 2021	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:09:32 2021	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:09:18 2021	Critical (3)	16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 23 04:09:18 2021	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:b3:ac:f0;CMTS-MAC=00:01:5c:a6:46:59;CM-QOS=1.1;CM-VER=3.1;

[plemans]

Your powerlevels look pretty spot on. 

But your event logs are showing issues connecting back to the cmts. 

You're caught in a problem. 

The power levels do look good. but the logs dont. And the ISP has checked the line. 

so is it still the line or is it the modem?

Unless you have a backup modem, its tough to prove either way. 

I've actually rented a modem from an ISP for the $10 a month (only rented for a month) to check which is was. 

right now I've got enough backup modems that I don't have to do that anymore. 

[yahdoneson1247]

Lol, this is where I figured that I am. I do have the spectrum provided modem, picked up a few days ago. I have been too prideful to accept that my modem could be the problem and wanted to check on here first before fully accepting defeat. I do plan to commission the spectrum modem to see if things become more stable which in turn will tell me I just need to get another modem.

Last question, would factory reseting the modem do anything? Or is this more hardware malfunction kind of thing and its a lost cause? Of course this is assuming the modem is the actual culprit and nothing upstream. 

At this rate, I am just trying to find some piece of mind. 

Thank you again

[plemans]

---

@yahdoneson1247 wrote:

Last question, would factory reseting the modem do anything? ---doesn't hurt to try. It doesn't need to be reinstalled/reprovisioned when you do it. Or is this more hardware malfunction kind of thing and its a lost cause?---I'm not sure its a hardware failure. I'd still be betting on an issue connecting to the cmts.  Of course this is assuming the modem is the actual culprit and nothing upstream. 

At this rate, I am just trying to find some piece of mind. ---agreed. Its frustrating when you're stuck between the ISP and your own hardware. is the modem still in warranty? If the spectrum device does work fine, you could get it replaced. click on "Mynetgear" at the top. register an account and the device. from there you can check warranty status. 

Thank you again

---