Hi,
I have seen several posts with Started Unicast Maintenance Ranging - No Response received - T3 time·out issue but am not getting resolution from reading or from technicians. Pretty much same as this one https://forums.xfinity.com/t5/Your-Home-Network/Connectivity-issues-Started-Unicast-Maintenance-Rang...
Had a tech change some cabling and suggest that if it persisted, that it may be my router/modem so I even tried a new one. Same issue with losing connection.
Here my current info:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Please post the RF error / event log entries as well.
Time Priority Description
Mon Oct 14
09:44:08 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
09:44:24 2019
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities
received - T4 time out;CM-MAC=00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CMQOS=
1.1;CM-VER=3.0;
Mon Oct 14
09:48:30 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
09:48:44 2019
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities
received - T4 time out;CM-MAC=00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CMQOS=
1.1;CM-VER=3.0;
Mon Oct 14
09:52:54 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
09:53:04 2019
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities
received - T4 time out;CM-MAC=00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CMQOS=
1.1;CM-VER=3.0;
Mon Oct 14
09:54:55 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
09:57:23 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
09:57:24 2019
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities
received - T4 time out;CM-MAC=00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CMQOS=
1.1;CM-VER=3.0;
Mon Oct 14
09:57:26 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
10:01:46 2019
Critical (3)
Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities
received - T4 time out;CM-MAC=00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CMQOS=
1.1;CM-VER=3.0;
Mon Oct 14
10:01:57 2019
Critical (3)
No Ranging Response received - T3 time-out;CM-MAC=00:40:36:5a:34:b0;CMTSMAC=
00:01:5c:6f:76:5e;CM-QOS=1.0;CM-VER=3.0;
Mon Oct 14
10:02:05 2019
Notice (6) Honoring MDD; IP provisioning mode = IPv6
Mon Oct 14
10:03:05 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
10:19:55 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
10:49:28 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
10:49:28 2019
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
10:49:28 2019
Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 0;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
12:07:33 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
12:07:38 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
12:11:10 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
12:11:10 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
12:44:02 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
12:45:50 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
13:02:29 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
13:02:29 2019
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
13:02:29 2019
Critical (3)
16 consecutive T3 timeouts while trying to range on upstream channel 0;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
13:07:16 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
13:12:55 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
13:19:56 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Mon Oct 14
13:35:29 2019
Warning (5) Dynamic Range Window violation
Mon Oct 14
13:37:07 2019
Critical (3)
Started Unicast Maintenance Ranging - No Response received - T3 time-out;CMMAC=
00:40:36:5a:34:b0;CMTS-MAC=00:01:5c:6f:76:5e;CM-QOS=1.1;CM-VER=3.0;
Clear
Even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.
There are other signal stat figures 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 that are available to these boards. They can check the CMTS (Cable Modem Termination System) 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 poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
Thanks!
I will add that this has been happening for a while but our service was reliable for years. We did not change anything that might have caused the issue. Our first tech did switch our cabling and tightened everything and thought it would work, but clearly has not.
Hello @budgie99, thanks for reaching out to our Forums! I would be more than happy to further investigate and look into these connection drops you're experiencing. I can also get a tech back out if needed as well. Can you please send a private message including the full name as it appears on the account and your full name if different?
To send a Private Message, please click “Comcast_Support” and click “send a message".