Community Forum

16 consecutive T3 timeouts while trying to range on upstream channel

Regular Visitor

16 consecutive T3 timeouts while trying to range on upstream channel

We have been having intermitent outages almost daily with our internet since the end of march. If it does not cut out completely we'll experience intense lag for 30 or so seconds when streaming or gaming. We are currently using a Arris Surfboard SB6183 for our modem and a AmpliFi HD Mesh Router. Modem currently shows all things normal and we have not yet contacted Comcast as I figured dumping the event log here would probably prove mor productive. Any advice that can be gleaned?  The modem's event log is as follows:

 

Fri Mar 29 14:10:57 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 29 14:11:44 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 29 14:11:44 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Fri Mar 29 14:11:44 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 10:44:28 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 10:44:28 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 10:44:28 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 10:44:36 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 10:44:36 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 10:44:36 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:26 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:26 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:26 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:32 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:32 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:32 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:32 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:32 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:14:32 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:21:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:21:39 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Mar 31 13:21:39 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 03 20:06:49 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 04 13:28:58 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 04 13:33:18 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Thu Apr 04 13:33:38 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 04 13:34:11 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Fri Apr 05 01:00:04 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 06 18:35:38 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sat Apr 06 18:39:58 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 08:41:10 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 08:45:30 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 10:48:31 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 10:48:31 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 10:48:31 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 10:48:47 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 07 10:53:07 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Sun Apr 07 10:54:21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Wed Apr 10 01:49:16 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 01:49:16 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 01:49:16 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 01:49:18 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 01:49:18 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 01:49:18 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 03:02:19 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 03:02:19 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 03:02:19 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 03:02:59 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Wed Apr 10 03:07:20 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Thu Apr 11 08:10:29 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 11 08:10:29 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Thu Apr 11 08:10:29 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:14:55 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:14:55 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:14:55 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:01 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:01 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:01 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:01 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:01 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:01 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:15:21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Sun Apr 14 10:19:41 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Sun Apr 14 12:06:39 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 01:54:22 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:42:41 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:42:41 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:42:41 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:42:58 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:42:59 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:42:59 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:43:18 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:47:38 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Mon Apr 15 09:49:04 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:49:37 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Mon Apr 15 09:53:46 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Mon Apr 15 09:58:06 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) TFTP failed - Request sent - No Response;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) TFTP Request Retries exceeded, CM unable to register
Time Not Established Notice (6) Tftp Init Failed - Reinitialize MAC...
Time Not Established Warning (5) ToD request sent - No Response received;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Critical (3) No Ranging Response received - T3 time-out
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Mon Apr 15 17:36:28 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=bc:2e:48:d8:5c:59;CMTS-MAC=00:01:5c:66:24:6b;CM-QOS=1.1;CM-VER=3.0;
Expert

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

Please also post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.




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

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

Oops! They are currently as follows:

 

Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 14 561000000 Hz -4.1 dBmV 35.6 dB 145 229
2 Locked QAM256 5 507000000 Hz -4.5 dBmV 35.5 dB 213 223
3 Locked QAM256 6 513000000 Hz -4.7 dBmV 35.9 dB 142 287
4 Locked QAM256 7 519000000 Hz -4.8 dBmV 35.8 dB 186 346
5 Locked QAM256 8 525000000 Hz -5.2 dBmV 35.7 dB 152 325
6 Locked QAM256 9 531000000 Hz -4.6 dBmV 35.9 dB 140 239
7 Locked QAM256 10 537000000 Hz -5.0 dBmV 35.8 dB 171 176
8 Locked QAM256 11 543000000 Hz -4.7 dBmV 35.7 dB 177 282
9 Locked QAM256 12 549000000 Hz -4.7 dBmV 35.7 dB 164 278
10 Locked QAM256 13 555000000 Hz -4.5 dBmV 35.1 dB 141 215
11 Locked QAM256 15 567000000 Hz -4.8 dBmV 35.6 dB 167 348
12 Locked QAM256 16 573000000 Hz -4.4 dBmV 35.5 dB 113 239
13 Locked QAM256 17 579000000 Hz -4.4 dBmV 35.3 dB 121 254
14 Locked QAM256 18 585000000 Hz -4.4 dBmV 35.6 dB 131 314
15 Locked QAM256 24 621000000 Hz -4.9 dBmV 35.5 dB 141 162
16 Locked QAM256 32 669000000 Hz -6.1 dBmV 35.3 dB 96 217
Expert

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

The power levels are a bit weak but are in spec. The SNR's are marginal. What about the upstream 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!
Regular Visitor

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

Hello again, and thank you for replying! Here is what I'm showing for upstream:

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 11 5120 Ksym/sec 23700000 Hz 41.5 dBmV
2 Locked ATDMA 9 5120 Ksym/sec 36500000 Hz 40.5 dBmV
3 Locked ATDMA 10 5120 Ksym/sec 30100000 Hz 41.2 dBmV
4 Locked ATDMA 12 5120 Ksym/sec 17300000 Hz 41.0 dBmV



 
Regular Visitor

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

Hi @EG , I haven't heard from you in a few days. When you have a chance would you mind reviewing my upchannel infromation above to see it is at all revealing of an issue? I continue to have the same errors above daily.

 

I've noticed the power on my downstream is higher then when I last checked but I'm don't really know what that would indicate. Below is it's current status:

Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 14 561000000 Hz -5.1 dBmV 35.3 dB 3081 6724
2 Locked QAM256 5 507000000 Hz -5.0 dBmV 35.4 dB 3189 4450
3 Locked QAM256 6 513000000 Hz -5.2 dBmV 35.9 dB 3074 4057
4 Locked QAM256 7 519000000 Hz -5.5 dBmV 35.8 dB 2662 4128
5 Locked QAM256 8 525000000 Hz -5.8 dBmV 35.7 dB 2334 4495
6 Locked QAM256 9 531000000 Hz -5.2 dBmV 35.9 dB 2476 3294
7 Locked QAM256 10 537000000 Hz -5.6 dBmV 35.8 dB 3104 3608
8 Locked QAM256 11 543000000 Hz -5.6 dBmV 35.7 dB 2818 4092
9 Locked QAM256 12 549000000 Hz -5.8 dBmV 35.6 dB 2596 4077
10 Locked QAM256 13 555000000 Hz -5.7 dBmV 34.4 dB 2234 4238
11 Locked QAM256 15 567000000 Hz -5.7 dBmV 35.5 dB 3046 4785
12 Locked QAM256 16 573000000 Hz -5.3 dBmV 35.3 dB 2805 4549
13 Locked QAM256 17 579000000 Hz -5.4 dBmV 35.0 dB 2279 4447
14 Locked QAM256 18 585000000 Hz -5.4 dBmV 35.5 dB 2545 5060
15 Locked QAM256 24 621000000 Hz -6.0 dBmV 35.5 dB 1774 3043
16 Locked QAM256 32 669000000 Hz -7.0 dBmV 35.3 dB 1787 3043

 

 

 

 

Thank you for your help!

Expert

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

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.



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!