Community Forum

Unicast Maintenance Ranging attempted - No response - Retries exhausted... 16 consecutive T3 timeout

Highlighted
New Poster

Unicast Maintenance Ranging attempted - No response - Retries exhausted... 16 consecutive T3 timeout

I have moved to a new address and since then I am struggling with my internet connection... This is the same Modem that I had at the previous address... Netgear Nighthawk C7800, so I am not "Yet" ready to accept that Modem is bad. 

 

My issue is every 2 hours my internet gets disconnected and when I check logs I can see various errors.. Smiley Sad 

 

Time Priority Description
2019-08-20, 15:33:56 Warning (5) MDD message timeout;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:12:48 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;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:aa:fa:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:06:00 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:06:00 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:05:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:05:31 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:05:31 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 14:04:23 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:07:22 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;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:aa:fa:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:05:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:05:25 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:05:24 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:04:44 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:04:42 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:04:15 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:04:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 13:01:24 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:33:37 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;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:aa:fa:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:14:42 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;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:aa:fa:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:12:58 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:12:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:12:17 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:11:49 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:11:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:11:20 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 12:11:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 11:41:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;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:aa:fa:e0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 11:32:23 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 11:27:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 10:17:00 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;
2019-08-20, 08:40:31 Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=28:80:88:aa:fa:e0;CMTS-MAC=00:01:5c:67:4e:56;CM-QOS=1.1;CM-VER=3.1;

 

Current Cable Connection status is ok.. 

 

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

<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure Status Comment
Acquire Downstream Channel 483000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security ENABLED BPI+
IP Provisioning Mode Honor MDD IPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectabables
1 Locked QAM256 2 483000000 Hz 6.7 dBmV 38.5 dB 353 319
2 Locked QAM256 3 489000000 Hz 6.6 dBmV 38.4 dB 1758 2354
3 Locked QAM256 4 495000000 Hz 6.7 dBmV 38.3 dB 1979 2508
4 Locked QAM256 5 507000000 Hz 6.8 dBmV 38.2 dB 1944 2492
5 Locked QAM256 6 513000000 Hz 6.9 dBmV 38.4 dB 1775 2587
6 Locked QAM256 7 519000000 Hz 6.8 dBmV 38.3 dB 1778 2487
7 Locked QAM256 8 525000000 Hz 6.8 dBmV 38.2 dB 2083 2479
8 Locked QAM256 9 531000000 Hz 6.4 dBmV 38.3 dB 1908 2464
9 Locked QAM256 10 537000000 Hz 6.5 dBmV 38.2 dB 1724 2393
10 Locked QAM256 11 543000000 Hz 6.4 dBmV 38.1 dB 1931 2505
11 Locked QAM256 12 549000000 Hz 6.3 dBmV 38.0 dB 2002 2368
12 Locked QAM256 13 555000000 Hz 6.5 dBmV 38.0 dB 1987 2583
13 Locked QAM256 14 561000000 Hz 6.6 dBmV 38.0 dB 1788 2720
14 Locked QAM256 15 567000000 Hz 6.7 dBmV 37.9 dB 2012 2430
15 Locked QAM256 16 573000000 Hz 6.6 dBmV 38.0 dB 2044 2638
16 Locked QAM256 17 579000000 Hz 6.7 dBmV 37.9 dB 1912 2659
17 Locked QAM256 18 585000000 Hz 6.4 dBmV 37.8 dB 2109 2467
18 Locked QAM256 19 591000000 Hz 6.6 dBmV 37.3 dB 2109 2441
19 Locked QAM256 20 597000000 Hz 6.4 dBmV 37.5 dB 2127 2423
20 Locked QAM256 21 603000000 Hz 6.6 dBmV 37.4 dB 2055 2593
21 Locked QAM256 22 609000000 Hz 6.7 dBmV 37.5 dB 2502 2515
22 Locked QAM256 23 615000000 Hz 6.6 dBmV 37.6 dB 2138 2737
23 Locked QAM256 24 621000000 Hz 6.7 dBmV 37.6 dB 2122 2508
24 Locked QAM256 25 627000000 Hz 6.8 dBmV 37.5 dB 2211 2539
25 Locked QAM256 26 633000000 Hz 6.8 dBmV 37.4 dB 2123 2530
26 Locked QAM256 27 639000000 Hz 6.7 dBmV 37.4 dB 2090 2504
27 Locked QAM256 28 645000000 Hz 7.1 dBmV 37.5 dB 2227 2579
28 Locked QAM256 29 651000000 Hz 6.8 dBmV 37.4 dB 2326 2477
29 Locked QAM256 30 657000000 Hz 7.2 dBmV 37.3 dB 2222 2726
30 Locked QAM256 31 663000000 Hz 7.3 dBmV 37.4 dB 2314 2652
31 Locked QAM256 32 669000000 Hz 7.1 dBmV 37.2 dB 2270 2742
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 3 5120 Ksym/sec 23000000 Hz 43.5 dBmV
2 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 43.0 dBmV
3 Locked ATDMA 2 5120 Ksym/sec 29400000 Hz 43.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16600000 Hz 43.5 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
Channel Channel ID Indicator Subcarrier Zero Frequency Active Subcarrier Number Range Total Codewords Uncorrectable Codewords
1 33 Non-Primary 611600000 Hz 1228 ~ 2867 46166 0
2 0 Other 0 Hz 0 ~ 0 0 0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
Channel UpstreamIsMuted Ranging Status Subcarrier Zero Frequency Active Subcarrier Number Range Symbols Per Frame Tx Power
1   Other 0 Hz 0 ~ 0 0 0 dBmV
2   Other 0 Hz 0 ~ 0 0 0 dBmV

 

 

I had 2 Technitians visit and check the cable from the Pole to my home... they did find the cut/damage in the cable outside which they replaced, however the only thing it did is "Nothing" from the issue prespective. 

 

I contacted Netgear.. they say the Device is ok... its an issue on xfinity side.. xfinity says .. your cabling is ok ... Not sure what to do.. Smiley Sad 

 

Regards

 

 

Expert

Re: Unicast Maintenance Ranging attempted - No response - Retries exhausted... 16 consecutive T3 tim

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 !



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: Unicast Maintenance Ranging attempted - No response - Retries exhausted... 16 consecutive T3 ...

AnuAlok, thank you for reaching out here on the forums! I definitely understand how important it is to have reliable service, and I'm here to help! Let's review this a bit further together. To get started, please send me a PM with your first and last name. 

To send me a Private Message, please click my name “ComcastAlly” and click “Send a message.”


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!