My Motorola SB6120, purchased in 2010, may be due for a replacement. A few weeks ago, I started having problems with download/upload speed, and dropped packets.
Normally, my connection is awesome, I get speedtest.net results in the range of 120-130 mbps down, 12 mbps up. I'm on the Premium package, which is capped at 150 down/10 up. When I'm experiencing the speed problem, I first notice streaming video stuttering, and web pages seem to take a long time waiting on the server before anything loads. When I run a speedtest, if it completes at all, it will be in the rand of 1-2 mbps down, sometimes as much as 10-15 mbps down, and 0-1 mbps up.
Rebooting the modem helps, for a while, but within a day or so the problem returns.
The modem log shows some errors, as follows:
Time Priority Code Message
Jul 06 2017 14:19:15 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jul 06 2017 14:19:15 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:27 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 14:07:10 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 14:07:10 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:23 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:56 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:56 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:55 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:55 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:55 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:55 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:54 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:54 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:53 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:53 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:52 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Jun 28 2017 11:45:52 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:23:74:f6:59:14;CMTS-MAC=c4:71:fe:76:d4:c6;CM-QOS=1.1;CM-VER=3.0;
Cox support tells me that they are not seeing a problem with the signal, and they suspect that if rebooting the modem temporarily alleviates the slow speed problems, then probably the modem is slowly dying, and should be replaced.
I'm curious if anyone can confirm from the logged events that the modem is indeed at fault, and what the Unicast Ranging Received Abort Response and No Ranging Response received errors mean.
If it is a problem with the modem, and I should replace it, I'm not sure whether to buy a SB6190, which is DOCSIS 3.0, or a DOCSIS 3.1 SB8200 which is about 2x the cost. I've been reading and it sounds like Cox is rolling out DOCSIS 3.1 now or in the near future, and if so I'd like to be using 3.1-compliant hardware so I can take advantage of speed bumps in the service tiers if and when they come.
↧