Community Forum

16 consecutive T3 timeouts while trying to range on upstream channel 3

Highlighted
New Poster

16 consecutive T3 timeouts while trying to range on upstream channel 3

 

 Downstream Bonded Channels		 	
  
   Channel	Lock Status	Modulation	Channel ID	Freq. (MHz)	Pwr (dBmV)	SNR (dB)	Corrected	Uncorrected
1	Locked	QAM256	38	471.0	4.4	42.6	559	806
2	Locked	QAM256	39	477.0	4.3	42.5	539	656
3	Locked	QAM256	40	483.0	3.9	42.3	717	792
4	Locked	QAM256	41	489.0	4.0	42.4	435	465
5	Locked	QAM256	33	495.0	3.8	42.3	398	405
6	Locked	QAM256	34	501.0	3.2	42.1	481	352
7	Locked	QAM256	35	507.0	3.3	40.0	513	356
8	Locked	QAM256	36	513.0	2.9	41.9	577	345
9	Locked	QAM256	1	519.0	2.8	41.9	638	407
10	Locked	QAM256	2	525.0	2.6	41.8	557	424
11	Locked	QAM256	3	531.0	2.7	41.8	530	424
12	Locked	QAM256	4	537.0	2.8	41.7	505	1412
13	Locked	QAM256	5	543.0	2.5	41.3	3793	18767
14	Locked	QAM256	6	555.0	2.5	41.4	1474	3288
15	Locked	QAM256	7	561.0	2.6	41.5	633	1021
16	Locked	QAM256	8	567.0	3.0	41.0	1509	3971
Total	 	 	 	 	 	 	13858	33891


   Upstream Bonded Channels		 	
  
   Channel	Lock Status	Channel Type	Channel ID	Symb. Rate (Ksym/sec)	Freq. (MHz)	Pwr (dBmV)
1	Locked	ATDMA	77	5120	35.8	50.5
2	Locked	ATDMA	78	5120	29.4	53.8
3	Locked	ATDMA	79	5120	23.0	53.8
4	Locked	ATDMA	80	5120	16.6	52.0
  Log		 	
  
 Time 	 Priority 	 Description 
 Thu Apr 23 05:58:01 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:05:14 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:05:14 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:05:14 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:12:26 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:12:26 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:12:26 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:19:38 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:19:38 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:19:38 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:26:51 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:26:51 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:26:51 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:34:03 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:34:03 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:34:03 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:41:16 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:41:16 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:41:16 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:48:28 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:48:28 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:48:28 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:55:41 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:55:41 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 06:55:41 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:02:54 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:02:54 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:02:54 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:10:06 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:10:06 2020  	 Critical (3) 	 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:10:06 2020  	 Critical (3) 	 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0; 
 Thu Apr 23 07:12:54 2020  	 Critical (3) 	 Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:5c:d3:36;CMTS-MAC=00:01:5c:80:dc:69;CM-QOS=1.1;CM-VER=3.0;

Please advise. I've already reached out to chat support and they suggest this is a modem issue. My modem is less than a few months old.

Highlighted
Gold Problem Solver

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

All of the upstream channels power levels are borderline/too high.

If you want to troubleshoot this yourself, please see Connection Troubleshooting Tips. If you still need help, please post your modems signal information, especially downstream power levels and SNR, upstream power levels, and error log.

If you can't find the problem or you'd rather have Comcast take care of it, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. If they can't fix the problem remotely (unlikely), insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit unless you have their Service Protection Plan (https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device, or anything outside your home, you shouldn't be charged.