Community Forum
Top

disproportionate amount of t3 / t4 errors

tlust302
Frequent Visitor
‎06-14-2020 04:29 PM

disproportionate amount of t3 / t4 errors

Began having internet issues (AGAIN) once it started to warm up just like every year. Calling for assistance appears to be futile as everyone has me recycle my modem and when that reestablishes connection for an hour (or maybe 10 minutes) they feel the issue is resolved. The problem is the issue continues as the root cause is not discovered and remedied. To date this issue has never been the equipment inside the house, but it's like pulling teeth to have someone come out and check the line and outside box.

 

Any help is appreciated.

 

Single Strength - please note the packets show as they do because the modem was recycled

 Startup Sequence
 

 

    
   Startup Step Status Comment
 

 



  
   Acquire Downstream Channel 459000000 Hz Locked
 

 


  
   Upstream Connection OK Operational
 

 


  
   Boot State OK Operational
 

 



  
   Configuration File OK  
 

 


  
   Security Enabled BPI+
 

 


  



   Connection Status
 

 

    
   System Up Time 0 days 00h:14m:17s  
 

 


  
   Network Access Allowed  
 

 


  



   Downstream Bonded Channels
 

 

  
 

 


  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
1 Locked QAM256 6 459.0 -10.1 39.7 0 0
2 Locked QAM256 1 429.0 -10.0 39.8 0 0
3 Locked QAM256 2 435.0 -10.4 39.6 0 0
4 Locked QAM256 3 441.0 -10.5 39.7 0 0
5 Locked QAM256 4 447.0 -10.5 39.5 0 0
6 Locked QAM256 5 453.0 -9.9 39.9 0 0
7 Locked QAM256 7 465.0 -9.7 39.8 0 0
8 Locked QAM256 8 471.0 -9.8 39.8 0 0
9 Locked QAM256 9 477.0 -9.7 39.8 0 0
10 Locked QAM256 10 483.0 -9.7 39.7 0 0
11 Locked QAM256 11 489.0 -10.0 39.5 0 0
12 Locked QAM256 12 495.0 -9.8 39.5 0 0
13 Locked QAM256 13 519.0 -9.0 39.9 0 0
14 Locked QAM256 14 525.0 -9.5 39.6 0 0
15 Locked QAM256 15 531.0 -8.6 40.0 0 0
16 Locked QAM256 16 537.0 -9.3 39.6 0 0
Total             0 0



   Upstream Bonded Channels
 

 

  
 

 


  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
1 Locked ATDMA 3 5120 23.7 54.0
2 Locked ATDMA 1 5120 36.5 54.0
3 Locked ATDMA 2 5120 30.1 54.0
4 Locked ATDMA 4 5120 17.3 54.0



   Downstream Frequency Setting

 

Below is the latest log:

Sun Jun 14 06:18:33 2020   Critical (3)  Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 06:18:33 2020   Critical (3)  16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 06:22:40 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 06:24:34 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:26:18 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:27:29 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:33:15 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:36:25 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:38:54 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:40:31 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:44:55 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:45:26 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 06:45:58 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:03:13 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 14:07:33 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 14:13:47 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:15:38 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:16:44 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:22:46 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:26:09 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:31:42 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:32:40 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:37:25 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:42:59 2020   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 14:44:07 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.0;CM-VER=3.0; 
Sun Jun 14 15:04:13 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 15:04:13 2020   Critical (3)  Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 15:04:13 2020   Critical (3)  16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 15:04:44 2020   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Sun Jun 14 15:09:04 2020   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:3f:a7:5e;CMTS-MAC=00:01:5c:b1:f0:46;CM-QOS=1.1;CM-VER=3.0; 
Time Not Established  Notice (6)  Honoring MDD; IP provisioning mode = IPv6 
0 Likes
Reply
BruceW
Gold Problem Solver
‎06-14-2020 04:47 PM

Re: disproportionate amount of t3 / t4 errors

The downstream power levels are too low and the upstream levels are too high. Problems like this are often due to poor coax connections, usually in or near your home.

If you want to troubleshoot this yourself, please see Connection Troubleshooting Tips. 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/. You'll need to try to persuade them to 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.

0 Likes
Reply
Visit Our Help Communities