Observer

Re: No Ranging Response received - T3 time-out

So the issue occurred again last night while we were sleeping.  This has been happening very often lately - I'd say almost every day.  The internet is working when we go to bed and when we wake up it isn't working.  My wife uses a WiFi baby monitor that she leaves running on her phone while we sleep - could that be part of this?  I don't think TWC has any data limits, but could it be that it's using so much data that we eventually get cut off?

 

Here are the logs that include the outage that occurred last night:

TimePriorityCodeMessage

Jun 18 2016 06:52:353-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 18 2016 06:52:346-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 18 2016 06:52:345-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:23:263-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:23:266-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 20:23:255-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 17:51:523-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 17:51:516-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 17:51:515-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 14:21:083-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 14:21:086-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 14:21:085-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to power reset ;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:536-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jun 17 2016 11:14:535-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:313-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=8c:7f:3b:90:24:ee;CMTS-MAC=00:01:5c:6b:dc:55;CM-QOS=1.1;CM-VER=3.0;
Expert

Re: No Ranging Response received - T3 time-out

Not a bandwidth issue, the router is getting confused when a T3 occurs, and locks up. You'll need to google the router model to see if others have a similar issue

  Solution I've found is to replace it with a non netgear product

 

Observer

Re: No Ranging Response received - T3 time-out

Thanks. I ordered a router/modem on Amazon so I'll try that on Monday and see how it goes.

I realized I forgot to mention that I also use a netgear range extender in the attic here. Could that have anything to do with the T3 lockup that's going on?
Expert

Re: No Ranging Response received - T3 time-out

More than likely the range extender is causing the routerissue.

 T2,T3,T4,T6 errors are coaxial network between your CM and the CMTS at the cable head end

 

Are you in a dense housing area? Someone might be deauthing you or trying to hack in

 Turn off WPS,

 Also make sure the DHCP lease is a day not an hour

 

Observer

Re: No Ranging Response received - T3 time-out

There's no way to change the DHCP lease length on the router page, I also googled and it appears that it isn't possible on this router. Folks in other forums did say that the default is 24 hours though, so that's good.

The Internet was down again this morning. When I checked the laptop that connects via the range extender, there was a popup that said there was an IP conflict with another device. Could that be related?

I unplugged the range extender and power cycled the modem and router. We'll see if the problem persists with the range extender unplugged.
Expert

Re: No Ranging Response received - T3 time-out

Address conflicts again point to a DHCP issue.

 Verify there's no guest wifi turned on, verify the DHCP lease  for wireless is a day not the wifi guest default of an hour.

Then change the DHCP start to 192.168.1.100 then repair in each device the internet connection, see if any are duplicate.

 

 

Observer

Re: No Ranging Response received - T3 time-out

Thanks. What should my IPv6 settings be? Auto-detect or something else?
Expert

Re: No Ranging Response received - T3 time-out

Autodetect... all wan settings.

 

 Do you have something running IPv6?

if not, disable IPv6, see if that clears the lockups.

 

Observer

Re: No Ranging Response received - T3 time-out

The modem says IPv6 only, which apparently is assigned by TWC. I don't think I have anything that requires IPv6, but wanted to be sure about my router's IPv6 settings given that's what the modem says.
Observer

Re: No Ranging Response received - T3 time-out

So this was the first morning in over 2 weeks or so that WiFi was still working when we woke up!  Pretty exciting...

 

But...I don't know the exact reason that this was the case.  Maybe it was due to some of the settings changes?  Changing the IP start to be 100?  Unplugging the range extender?

 

Since unplugging the range extender and doing the most recent settings changes that you recommended, there have been no additional records in the modem log file.