C6220 dropped connection

Question

C6220, firmware&nbsp;V1.01.26&nbsp;Just had an eisode where the connection (both wired and wireless) dropped for several minutes. Checked the logs when I was able to connect to tthe rouer and found this:&nbsp;2022-06-18, 08:43:57.0Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-06-18, 08:43:57.0Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-06-17, 18:12:10.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-06-13, 21:45:41.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-06-08, 07:08:24.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-06-06, 20:35:27.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-06-03, 21:53:55.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-05-27, 20:23:44.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-05-25, 22:42:07.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-05-21, 17:20:12.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-05-13, 18:50:13.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-05-12, 10:57:47.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;2022-05-10, 23:57:07.0Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;&nbsp;…and it continues in a similar vein for many pages.Which, if any of these should I be concerned with, and what should I do about itt?

FURRYe38 · Answer

Lots of errors and criticals. Your ISP will need to check into this with you.
&nbsp;
Please post a copy and paste of the modems connection status page.
Have the ISP check the signal and line quality UP to the modem.&nbsp;Be sure the ISP provisions the modem correctly.Be sure there are no coax cable line splitters in the between the modem and ISP service box.&nbsp;Be sure your using good quality RG6 coax cable up to the modem.&nbsp;Be sure to power OFF the modem for 1 minute then back ON.https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router?article=24311https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

JohnDThompson · Answer

No splitters on the cable. Using the cable Spectrum provided when they hooked it up. I'll ask Spectrum to take a look.

Here's the "Connection" details:

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

Startup Procedure

Procedure	Status	Comment
Acquire Downstream Channel	537000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Configuration File	OK
Security	Enable	BPI+
IP Provisioning Mode	Override MDD	IPv6 only

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectables
1	Locked	QAM256	9	537000000 Hz	-6.5 dBmV	38.7 dB	0	0
2	Locked	QAM256	10	543000000 Hz	-6.2 dBmV	39.0 dB	1	0
3	Locked	QAM256	11	549000000 Hz	-6.7 dBmV	38.6 dB	2	0
4	Locked	QAM256	12	555000000 Hz	-6.5 dBmV	38.6 dB	1	0
5	Locked	QAM256	13	561000000 Hz	-6.3 dBmV	38.9 dB	0	0
6	Locked	QAM256	14	567000000 Hz	-5.8 dBmV	39.2 dB	1	0
7	Locked	QAM256	15	573000000 Hz	-6.3 dBmV	38.6 dB	0	0
8	Locked	QAM256	16	579000000 Hz	-7.0 dBmV	38.2 dB	1	0

Upstream Bonded Channels

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	89	5120 Ksym/sec	17600000 Hz	40.8 dBmV
2	Locked	ATDMA	90	5120 Ksym/sec	24000000 Hz	41.0 dBmV
3	Locked	ATDMA	91	5120 Ksym/sec	30400000 Hz	41.8 dBmV
4	Locked	ATDMA	92	5120 Ksym/sec	36800000 Hz	43.0 dBmV

Current System Time: Sat Jun 18 09:26:31 2022

FURRYe38 · Answer

The power is a bit too low. I would have the ISP see if they can increase the power up into middle range.&nbsp;

plemans · Answer

Your power levels aren't actually to low. They should be from -7.5dbmv to 7.5dbmv. You're in that range. So saying yours is to low, isn't accurate.
But that's just a general overview or power levels as you're modem only connects to 8 channels. there's a wide range of channels and there can be issues on other channels that aren't showing up that it might be switching around from. That's where the actual logs help. (and show you have issues with the t3 errors)
I'm suspecting this because your upstream to downstream power levels don't align. If the downstream is where yours is at, we'd expect your upstream to be higher than what it is. So there's something causing signal interference.&nbsp;
Whether its a cheap rb6 cable, splitters, a signal attenuators, etc. There's something in line thats causing signal issues.
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, 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. If none of that helps, the ISP needs to check the line.&nbsp;

Forum Discussion

C6220 dropped connection

4 Replies

2022-06-18, 08:43:57.0	Error (4)	Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-06-18, 08:43:57.0	Error (4)	Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-06-17, 18:12:10.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-06-13, 21:45:41.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-06-08, 07:08:24.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-06-06, 20:35:27.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-06-03, 21:53:55.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-05-27, 20:23:44.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-05-25, 22:42:07.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-05-21, 17:20:12.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-05-13, 18:50:13.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-05-12, 10:57:47.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;
2022-05-10, 23:57:07.0	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:03:78:90;CMTS-MAC=00:01:5c:69:06:5d;CM-QOS=1.1;CM-VER=3.0;