7 Messages
Started Unicast Maintenance Ranging - No Response received - T3 time-out
I've been dealing with connection drops for months. We've had 4 service calls but they keep saying everything is fine even though we keep getting notices from Xfinity about service disruption. We've had every TV in the house except one and the cable modem unhooked at the box. But still we get numerous T3 and T4 errors which results in the internet drop or slowing.
The Tech mentioned the router but I've replaced the router to test still have the same results. Our drops correspond to when we're seeing the errors in the modem log as seen below.
I don't know why they can't find the problem. I really don't want to switch to FIOS but I can't have unstable internet like this.
Event Log
Status > Event Log
The table below contains the log of events that the SB8200 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur.
Date Time Event ID Event Level Description
03/24/2025 07:45 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 07:45 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 07:45 84020300 5 "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:46 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:45 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 04:45 84020300 5 "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 03:04 84020300 5 "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:46 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:45 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/24/2025 02:45 84020300 5 "MDD message timeout;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 18:03 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 17:59 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:50 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:35 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:26 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:23 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:22 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:21 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:16 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:13 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:12 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:10 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:09 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:09 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:03 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:02 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:01 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:01 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:00 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 16:00 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:29 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:29 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:23 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:18 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:18 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:16 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:15 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:14 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 14:13 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:36 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:32 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:32 74010100 6 "CM-STATUS message sent. Event Type Code: 16; Chan ID: 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:31 74010100 6 "CM-STATUS message sent. Event Type Code: 24; Chan ID: 193 194; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=*:*:*:*:*:*;CMTS-MAC=*:*:*:*:*:*;CM-QOS=1.1;CM-VER=3.1;"
03/23/2025 13:30 74010100 6 "C
OliverM3
7 Messages
9 days ago
Today was really bad with the rain it always seems worse when it's raining.
0
0
EG
Expert
•
109.5K Messages
9 days ago
Please also copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.
3
0
EG
Expert
•
109.5K Messages
9 days ago
The signal status values looked OK at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is intermittent noise ingress into the line(s) / an upstream channel / return path impairment somewhere.
There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and check those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
1
0
EG
Expert
•
109.5K Messages
9 days ago
@OliverM3
My pleasure !!
1
0
EG
Expert
•
109.5K Messages
7 days ago
Your latest post shows that the upstream power has spiked up to being too high / 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.
Here's some things that you can try. In an effort to try to obtain better connection quality, check to see if there are 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-1002 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 !
1
0