dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
7
share rss forum feed

HeinePaul

join:2003-07-18
Las Vegas, NV

1 edit
reply to Alan A

Re: [NV] Cox Internet continually dropping in Las Vegas area

Yeah, I've recently been given the "it must be your hardware inside the house.. it's not us" line by "Christopher" at Cox Support.

I'm guessing Cox is having trouble with the upstream my neighborhood is given, and as it is intermittent and mostly daytime. Amazing how those cable crimps keep such regular hours, huh?

Without their assistance, and despite the misdirection, I've noted:
the Docsis 3.0 cable modem tries to communicate with CMTS (10.65.0.1) with a MAC of MAC=64:00:f1:40:38:6a, it craps out.. but almost only between 11am and 8pm.

Here's what today has been like. What a joy...

Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to T4 timeout ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:16 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:16 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:01 3-Critical R06.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:01 3-Critical R03.0 Ranging Request Retries exhausted;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:09:01 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:06:01 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 11:03:10 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 10:12:37 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:51:26 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:39 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:49:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:38:55 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot from GUI/Configuration page ;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Feb 13 2013 09:37:09 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:22:10:2c:17:52;CMTS-MAC=64:00:f1:40:38:6a;CM-QOS=1.1;CM-VER=3.0;

My guess is the CMTS is failing and rebooting, or the filter built into the CMTS is improperly functioning.



CoxTech1
VIP
join:2002-04-25
Chesapeake, VA
kudos:77

Probably not a CMTS issue otherwise many thousands of others would be experiencing problems. Upstream ingress/noise is a more likely explanation although a failed modem is also possible. A technician would be able to help determine what could be going on.