Community Forum

Connection drops T3 errors in log

Highlighted
Regular Visitor

Connection drops T3 errors in log

My connection drops multiple times throughout the day. I have a log full of T3 timeouts. I replaced the wire coming from the amplifier/splitter on the outside of the house that goes to the modem. I replaced the coax going to the amplifier power also. We used to have X1 but have only internet now so there is only the modem on the connection. When the connection drops its out anywhere between 1 minute and 45 minutes. I'm at a loss of what to do, also got a brand new modem thinking it was the old modem and now I'm thinking it wasn't. The link below is a screenshot of the connection page from the modem and the error log is pasted below. 

 

https://ibb.co/wM2nVx1 

 

 

 

19:05:47
Tue Apr 7 2020
  Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:06:46
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:06:46
Tue Apr 7 2020
  Critical (3)   Ranging Request Retries exhausted;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:06:46
Tue Apr 7 2020
  Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:06:58
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:02
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:02
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:02
Tue Apr 7 2020
  Critical (3)   Ranging Request Retries exhausted;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:02
Tue Apr 7 2020
  Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:03
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:06
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:07
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:07
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:08
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:09
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:09
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:10
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:10
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:19
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:19
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:20
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:20
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:07:21
Tue Apr 7 2020
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:11:00
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:11:00
Tue Apr 7 2020
  Critical (3)   Ranging Request Retries exhausted;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:11:00
Tue Apr 7 2020
  Critical (3)   16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:11:19
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:11:21
Tue Apr 7 2020
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:13:02
Tue Apr 7 2020
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;
    19:13:11
Tue Apr 7 2020
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    19:13:23
Tue Apr 7 2020
  Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    19:16:05
Tue Apr 7 2020
  Critical (3)  

No Ranging Response received - T3 time-out;CM-MAC=00:40:36:61:42:a9;CMTS-MAC=00:01:5c:75:78:62;CM-QOS=1.1;CM-VER=3.1;

 

Highlighted
Expert

Re: Connection drops T3 errors in log

Please also post the upstream channel power levels.



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!
Highlighted
Regular Visitor

Re: Connection drops T3 errors in log

Screen Shot 2020-04-08 at 7.04.07 PM.png

Highlighted
Regular Visitor

Re: Connection drops T3 errors in log

Highlighted
Expert

Re: Connection drops T3 errors in log

The upstream power is on the low side and is out of spec on channel 3. You could try bypassing that amp altogether and see. Still no joy ? Book a tech visit for this one. Good luck with it !



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!
Highlighted
Regular Visitor

Re: Connection drops T3 errors in log

Yea this is what I figured. I contacted them but they won't send someone to the pole to check because of the Corona they tell me.