Community Forum

T3 time out - Frequent disconnects

Highlighted
New Poster

T3 time out - Frequent disconnects

Hello,

 

I've been experiencing several disconnects a day due to T3 timeouts according to the cable modem log.  I've tried moving the modem to different outlets and even connected the modem straight to the feed cable to the house with little change.  I only have internet and do not have any splitters installed.  Any ideas on what is wrong?

 

The below is what I currently get.  The downstream SNR usually goes from 32-34dB.  The power level on upstream goes from 44-47dBmv.  

 

Downstream Bonding Channel Value
Channel ID10 11 12 13 14 15 
Frequency453000000 Hz 459000000 Hz 465000000 Hz 471000000 Hz 477000000 Hz 483000000 Hz 489000000 Hz 495000000 Hz 
Signal to Noise Ratio34 dB 34 dB 34 dB 34 dB 34 dB 34 dB 34 dB 34 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-1 dBmV  -1 dBmV  -2 dBmV  -1 dBmV  -2 dBmV  -2 dBmV  -1 dBmV  -2 dBmV  

 

Upstream Bonding Channel Value
Channel ID
Frequency29600000 Hz 16500000 Hz 23000000 Hz 36100000 Hz 
Ranging Service ID9017 9017 9017 9017 
Symbol Rate5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec 
Power Level45 dBmV 45 dBmV 45 dBmV 46 dBmV 
Upstream Modulation[2] QPSK
[1] 32QAM
[3] 64QAM
 
[2] QPSK
[1] 32QAM
[3] 64QAM
 
[2] QPSK
[1] 32QAM
[3] 64QAM
 
[2] QPSK
[1] 32QAM
[3] 64QAM
 
Ranging StatusSuccess Success Success Success 

 

Signal Status (Codewords) Bonding Channel Value
Channel ID10 11 12 13 14 15 
Total Unerrored Codewords69993983 69182832 69190666 69199292 69171840 69175812 69176000 69177504 
Total Correctable Codewords17 15 19 15 
Total Uncorrectable Codewords610 590 1394 1417 1591 726 1554 1524 

 

Jul 31 2020 14:32:015-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:186-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 14:20:015-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:186-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 14:09:113-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:54:455-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:243-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:186-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:53:473-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:49:473-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:513-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:513-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:503-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:503-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:353-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:353-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 31 2020 13:48:263-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 30 2020 23:11:553-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 30 2020 23:11:553-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;
Jul 30 2020 23:11:513-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:fa:17:b4;CMTS-MAC=00:01:5c:a2:78:7c;CM-QOS=1.1;CM-VER=3.0;