Community Forum

Several T3 Timeouts daily for the past 6-8 weeks.

Frequent Visitor

Several T3 Timeouts daily for the past 6-8 weeks.

I am having horrific uptime with my CM600 modem and comcast as of the past 6-8 weeks. Daily my modem seems to be disconnecting due to T3 timeouts every 2-3  hours. Below is a log of my issues for just the past day.

 

Time Priority Description
2018-08-04, 11:34:32 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-08-04, 11:34:26 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-04, 11:34:01 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-04, 11:32:34 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-04, 11:30:54 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-04, 11:28:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 11:28:55 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 11:28:55 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 11:28:40 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 11:28:40 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 11:28:40 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 04:05:51 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-08-04, 04:05:45 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-04, 04:05:18 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-04, 04:02:41 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 03:58:21 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 03:57:55 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 03:57:55 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-04, 03:57:55 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.1;CM-VER=3.0;
2018-08-03, 22:27:47 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2018-08-03, 22:27:38 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:27:06 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:26:16 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:24:14 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:23:08 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:20:46 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:19:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:18:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:17:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:16:27 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:14:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:13:36 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:13:07 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:11:37 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:11:05 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:10:07 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:08:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:07:46 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:06:36 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
2018-08-03, 22:04:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=2c:30:33:95:03:70;CMTS-MAC=00:01:5c:a8:b2:66;CM-QOS=1.0;CM-VER=3.0;
Diamond Problem Solver

Re: Several T3 Timeouts daily for the past 6-8 weeks.

Also post the signal status.

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


Frequent Visitor

Re: Several T3 Timeouts daily for the past 6-8 weeks.

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 465000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv6 only
 
<tabindex=-1>Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 1 465000000 Hz 2.7 dBmV 39.2 dB 68 71
2 Locked QAM256 2 471000000 Hz 2.8 dBmV 39.2 dB 96 43
3 Locked QAM256 3 477000000 Hz 2.7 dBmV 39.2 dB 117 62
4 Locked QAM256 4 483000000 Hz 2.8 dBmV 39.2 dB 98 57
5 Locked QAM256 5 489000000 Hz 2.9 dBmV 39.2 dB 100 115
6 Locked QAM256 6 495000000 Hz 3.3 dBmV 39.4 dB 63 44
7 Locked QAM256 7 501000000 Hz 3.3 dBmV 39.4 dB 86 26
8 Locked QAM256 8 507000000 Hz 3.5 dBmV 37.3 dB 71 51
9 Locked QAM256 11 525000000 Hz 3.5 dBmV 39.4 dB 104 34
10 Locked QAM256 13 537000000 Hz 3.5 dBmV 39.3 dB 83 66
11 Locked QAM256 14 543000000 Hz 3.7 dBmV 39.4 dB 74 80
12 Locked QAM256 15 549000000 Hz 3.8 dBmV 39.4 dB 66 29
13 Locked QAM256 19 573000000 Hz 4.0 dBmV 39.3 dB 57 107
14 Locked QAM256 20 579000000 Hz 4.1 dBmV 39.3 dB 64 15
15 Locked QAM256 21 585000000 Hz 4.1 dBmV 39.3 dB 40 67
16 Locked QAM256 22 591000000 Hz 4.0 dBmV 39.2 dB 30 55
17 Locked QAM256 23 597000000 Hz 3.6 dBmV 39.8 dB 0 0
18 Locked QAM256 24 603000000 Hz 3.5 dBmV 39.9 dB 0 0
19 Locked QAM256 26 615000000 Hz 3.9 dBmV 39.9 dB 0 0
20 Locked QAM256 27 621000000 Hz 4.3 dBmV 39.9 dB 0 0
21 Locked QAM256 28 627000000 Hz 4.4 dBmV 39.8 dB 0 0
22 Locked QAM256 29 633000000 Hz 4.3 dBmV 39.9 dB 0 0
23 Locked QAM256 30 639000000 Hz 4.2 dBmV 39.8 dB 0 0
24 Locked QAM256 31 645000000 Hz 4.2 dBmV 39.9 dB 0 0
 
<tabindex=-1>Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 17300000 Hz 52.3 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 23700000 Hz 50.5 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 30100000 Hz 50.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 36500000 Hz 49.5 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
Diamond Problem Solver

Re: Several T3 Timeouts daily for the past 6-8 weeks.

The upstream power is borderline / too high and may be intermittently fluctuating even higher out of spec. That can cause random disconnects, spontaneous re-booting of the modem, and speed and latency problems.

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.