Community Forum

16 consecutive T3 timeouts while trying to range on upstream

New Poster

16 consecutive T3 timeouts while trying to range on upstream

I just upgraded my model to a netgear CM500V.

I have an Xfinity 400mbps connection but the latency and performance seems off.

 

I am looking at the modem event log and I see tons of critical errors:

 
 
Time Priority Description
Fri May 24 20:03:37 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:33 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:33 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:33 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:32 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:32 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:32 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:31 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:31 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:31 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:11 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:11 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:11 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:10 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:10 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:10 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:08 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:08 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:03:08 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:48 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:48 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:48 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:47 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:47 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:46 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:46 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:46 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:26 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:26 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:26 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:25 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:25 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:25 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:24 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:24 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:24 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:04 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:04 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;
Fri May 24 20:02:04 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=cc:40:d0:24:e3:30;CMTS-MAC=00:01:5c:96:36:73;CM-QOS=1.1;CM-VER=3.0;

 

 

HEre is my config

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 495000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 3 495000000 Hz -3.3 dBmV 37.4 dB 0 0
2 Locked QAM256 6 519000000 Hz 1.3 dBmV 38.3 dB 1 0
3 Locked QAM256 7 525000000 Hz 1 dBmV 38.3 dB 0 0
4 Locked QAM256 8 531000000 Hz 1.2 dBmV 38.2 dB 0 0
5 Locked QAM256 9 537000000 Hz 0.5 dBmV 37.9 dB 0 0
6 Locked QAM256 10 543000000 Hz 1 dBmV 37.9 dB 0 0
7 Locked QAM256 11 555000000 Hz 0.8 dBmV 37.5 dB 3 0
8 Locked QAM256 12 561000000 Hz 1.4 dBmV 37.4 dB 1 0
9 Locked QAM256 14 573000000 Hz 1.7 dBmV 37 dB 0 0
10 Locked QAM256 18 597000000 Hz 1.4 dBmV 36.7 dB 8 0
11 Locked QAM256 19 603000000 Hz 2.4 dBmV 36.9 dB 3 0
12 Locked QAM256 22 621000000 Hz 1.7 dBmV 36.3 dB 15 0
13 Locked QAM256 23 627000000 Hz 1.4 dBmV 36.2 dB 12 0
14 Locked QAM256 24 633000000 Hz 2.2 dBmV 36 dB 8 0
15 Locked QAM256 26 645000000 Hz 2.3 dBmV 36.2 dB 15 0
16 Locked QAM256 27 651000000 Hz 2.2 dBmV 35.8 dB 15 0
 
Upstream Bonded Channels (Partial Service)
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35800000 Hz 51.8 dBmV
2 Not Locked Unknown 2 0 Ksym/sec 29400000 Hz 0.0 dBmV
3 Not Locked Unknown 3 0 Ksym/sec 23000000 Hz 0.0 dBmV
4 Not Locked Unknown 4 0 Ksym/sec 16600000 Hz 0.0 dBmV
 

 

 

If anybody can tell me if these values are ok ?

 

My previous modem was much faster in terms of latency and download.. I did not change anything else but the modem

 

 

 

Diamond Problem Solver

Re: 16 consecutive T3 timeouts while trying to range on upstream

The only thing sticking out is only one upstream channel showing up. Depending on your area, there should be 3 or 4. Try resetting your modem. Did your previous modem have those present?

I am a Retired Official Comcast Employee
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark a post as the Best Answer!
Expert

Re: 16 consecutive T3 timeouts while trying to range on upstream

And that is high ! That can indicate an upstream / return path impairment. Noise in the return can cause the unbonding of upstream channels.


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: 16 consecutive T3 timeouts while trying to range on upstream

Philooo, thank you for reaching out here. Are you still having issues after resetting your modem? Please feel free to send me a PM with your first and last name for further troubleshooting. 

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!