Started Unicast Maintenance Ranging - No Response received - T3 time-out

Hi,

I have been having some connection issues with my home network recently. I have been experiencing a number of symptoms: high pack loss, connection drops, slow speeds.

I had a technician out yesterday that said the line connection was working. So I thought it might be my router since that was the oldest hardware on my network. I replaced it and I am still having issues. So I now suspect my 3 month old modem might be the culprit. I logged in and see a number of critical errors in the event log.

The router is a netgear nighthawk CM1200. It has firmware version 3.12.03 which is the latest and greatest supported.Here is a dump of the event log.

Please let me know what I can do next to fix this issue.

Time	Priority	Description
Fri Mar 22 09:20:03 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:10:46 2024	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; 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;
Fri Mar 22 09:10:44 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:10:16 2024	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; 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;
Fri Mar 22 09:10:14 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:47 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:46 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:46 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:44 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:44 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:42 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:42 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:40 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:40 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:38 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:38 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:36 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:36 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:35 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:34 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:34 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:33 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:31 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:31 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:31 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:30 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:29 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:29 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:28 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:28 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:28 2024	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:27 2024	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:22 2024	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:08:17 2024	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv6
Time Not Established	Critical (3)	UCD invalid or channel unusable;CM-MAC=::::;;CMTS-MAC=:::::;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=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 22 09:07:08 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
Thu Mar 21 19:54:25 2024	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; 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;
Thu Mar 21 19:54:24 2024	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=::::;;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

Help Center

Show/Hide Hel

Responses

EG

Expert

•

110K Messages

1 year ago

The error log entries have been edited out of your post because they contain CM MAC and the CMTS MAC addresses. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. Please re-post them but you'll need to redact all of the CM MAC and CMTS MAC addresses.

While you are at it, please also copy all of the text in its entirety of the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers and paste them into your next post.

EG

Expert

•

110K Messages

1 year ago

Ok, so even though the signal status values were within specs 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 !

kemper51

5 Messages

Thank you I look forward from hearing from The Digital Care Team! I hope to get a resolution quickly on this.

1 year ago

XfinityKei

Official Employee

•

1.4K Messages

Hello and happy Friday @kemper51. Outside of your connection concerns how's your day going? Thanks for reaching out and reporting your concerns of high pack loss, connection drops, slow speeds. You're with the right team to help. Can you tell us more about when this is happening and what you're doing when you experience those connection issues. Is the packet loss limited, to gaming?

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer. tick

1 year ago

kemper51

5 Messages

I am not a gamer. I measure the pkg loss from my home computer while doing a simple dns ping. the packet loss has ranged from 14 to 40%.

There are two of us working out of the house so the service is important to us.

Generally I notice this most while using my computer. We aren't streaming or doing any real high bandwidth type activities during work hours so I don't think its that.

1 year ago

XfinityKei

Official Employee

•

1.4K Messages

Ok @kemper51 I would like to take a closer look at your account especially with a tech being out there yesterday and the issue is ongoing. Can you please direct message me your first and last name along with your full service address so that I can assist you further?
Here's the detailed steps to direct message us:
• Click "Sign In" if necessary
• Click the "Direct Message” icon (upper right corner of this page)
• Click the "New message" (pencil and paper) icon
• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list
• Type your message in the text area near the bottom of the window
• Press Enter to send your message

1 year ago

kemper51

5 Messages

sent the DM with the info you requested

1 year ago

Damone17

Visitor

•

1 Message

7 months ago

I too have had these issues for years. Since 2018. Reported the problem, the dude comes out, says he will personally follow-up with me, then ghosts me. That was 2019. I've just learned to deal with it. However it appears that Comcast is monitoring these posts and summarily gets someone involved at a local level. Is it my turn for them to fix this issue once and for all? I guess we will see in time.

EG

Expert

•

110K Messages

7 months ago

@Damone17

Please create a new topic of your own here on this board detailing your issue. Thanks. The original poster has not returned. 6-month-old dead thread is now being closed.

For future reference, it is better to submit your own post as it creates a ticket to get help, and posting on someone else's older thread can delay getting help.

(edited)

Your Home Network

kemper51

Started Unicast Maintenance Ranging - No Response received - T3 time-out

EG

EG

kemper51

XfinityKei

kemper51

XfinityKei

kemper51

Damone17

EG

New to the Community?