dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
8547
share rss forum feed

rdarnutzer

join:2013-03-04
Lake Charles, LA

1 edit

[Connectivity] No Ranging Response received - T3 time-out

I recently upgraded to 30/2 from 15/1.5 in preparation for receiving my new Docsis 3 modem. Before I had a Motorola sb901 and now a sp6121. Before I received many t3 timeouts and contributed them to the sb901, but after upgrading to the new modem I still receive them. The only difference is it does not reboot as much. It still drops the internet conection about every 8 to 10 minutes. Below is a listing of info from the sb6121: Any ideas?

Model Name: SB6121
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.8-SCM01-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 5.0
Serial Number: ---------------------------
Firmware Build Time: Aug 30 2012 15:35:46

Downstream Bonding Channel Value
Channel ID 209 210 211 212
Frequency 561000000 Hz 567000000 Hz 573000000 Hz 579000000 Hz
Signal to Noise Ratio 36 dB 36 dB 36 dB 36 dB
Downstream Modulation 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 0 dBmV 0 dBmV 0 dBmV
Upstream Bonding Channel Value
Channel ID 3
Frequency 33000000 Hz
Ranging Service ID 7237
Symbol Rate 2.560 Msym/sec
Power Level 46 dBmV
Upstream Modulation [3] QPSK
[2] 16QAM

Ranging Status Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 209 210 211 212
Total Unerrored Codewords 38108051 37289645 37290345 37285989
Total Correctable Codewords 1769 1765 1746 2010
Total Uncorrectable Codewords 10448 8826 8289 12228

Mar 04 2013 13:47:55 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:35:40 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=---------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:02 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=-----------------;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:34:54 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=---------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:34:54 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=---------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:34:53 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=-----------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:27:02 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=--------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:01 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=--------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=---------------------;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:26:18 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=--------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:26:18 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=---------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 13:26:17 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=-----------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 12:22:17 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=---------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:01 5-Warning D04.1 ToD request sent - No Response received;CM-MAC=----------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:19 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=-----------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=--------------;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 12:21:31 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=---------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 12:21:31 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=-------------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;
Mar 04 2013 12:21:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=--------------;CMTS-MAC=00:21:d8:d1:95:74;CM-QOS=1.1;CM-VER=3.0;



gatorkram
Need for Speed
Premium
join:2002-07-22
Winterville, NC
kudos:3
Reviews:
·Suddenlink

Your power levels look good as far as I can see.

The first thing that comes to mind, is some type of noise / interference issue.

You might send SDL L3Tech See Profile a pm with your modem mac and your public ip address, and have them take a look.

By the way, your mac address is posted in that log entry you posted, not sure, but you might want to edit it out.
--
What the heck is a GatorKram? »www.gatorkram.com



moldypickle

join:2009-01-04
Haughton, LA
kudos:2

I get those errors a TON when my upstream power level spikes



Gaff
Just like the gypsy woman said

join:1999-09-05
North TX, US
Reviews:
·Suddenlink
reply to rdarnutzer

I get those a lot, too. Heck, this is just from today:

 Mon Mar 04 14:21:14 2013   Warning (5)  ToD request sent - No Response received;CM-MAC=... 
 Mon Mar 04 14:21:13 2013   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Mon Mar 04 14:21:01 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:21:00 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:20:35 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:20:34 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:20:08 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:20:06 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:19:40 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:19:38 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:19:11 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:19:10 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:18:44 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:18:42 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:18:17 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:18:16 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:17:49 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:17:48 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:17:21 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:17:20 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:16:55 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC f... 
 Mon Mar 04 14:16:54 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:16:26 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:15:54 2013   Warning (5)  ToD request sent - No Response received;CM-MAC=... 
 Mon Mar 04 14:15:53 2013   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Mon Mar 04 14:15:36 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:15:03 2013   Warning (5)  ToD request sent - No Response received;CM-MAC=... 
 Mon Mar 04 14:15:02 2013   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Mon Mar 04 14:14:42 2013   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Mon Mar 04 14:13:01 2013   Warning (5)  ToD request sent - No Response received;CM-MAC=... 
 Mon Mar 04 14:12:54 2013   Warning (5)  ToD request sent - No Response received;CM-MAC=... 
 Mon Mar 04 14:12:54 2013   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 

It doesn't seem to make any difference to my connection (always rock solid) but still, I worry...

--
My PC Gaming Blog
»www.gaffonline.com


moldypickle

join:2009-01-04
Haughton, LA
kudos:2
Reviews:
·Suddenlink

T3 issues seem to be tied to line maintenance, T4 issues are reboots (i know that much for sure, lol)

I have called motorola before and asked them what they meant and even though there is an error code, they had ZERO idea, told me to call the isp, lol