Cox_User_Who_Ne's profile

Cox_User_Who_Ne

Contributor

 • 

50 Messages

Closed

Cox Packet Loss ever since the GIGABLAST update came (100/10) plan.

I've had packet loss for 3 months now and the only thing I see correlated to most people with the same issue of me is the big updates they did with Gigablast. 
How can i get a technician who actually knows things about internet to fix this instead of one of these technicians who just do a bunch of simple random stuff that clearly won't do anything!

Discussions

 • 

Updated 

3.6K

1

0

0

C

Cox_User_Who_Ne

Contributor

 • 

50 Messages

I've been getting these errors for a long time

Dec 05 2018 07:47:17 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 05 2018 07:30:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 05 2018 07:29:17 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 05 2018 07:19:04 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 05 2018 07:18:57 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 02 2018 13:44:43 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 02 2018 13:44:43 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:29 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:17 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Dec 02 2018 13:38:51 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Dec 02 2018 13:38:51 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:17 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Dec 01 2018 13:02:00 6-Notice D106.0 DHCP Renew - lease parameters tftp file-^1/00077A1F/141/001 modified;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Nov 20 2018 16:01:48 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Nov 17 2018 13:02:01 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Nov 17 2018 13:02:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:17 6-Notice N/A Cable Modem Reboot from SNMP ;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Nov 17 2018 12:57:01 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;
Nov 17 2018 12:57:01 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:3d:66:09:28:a1;CMTS-MAC=00:7e:95:40:0c:ec;CM-QOS=1.1;CM-VER=3.0;

3

0

C
Cox_User_Who_Ne

Contributor

 • 

50 Messages

No the issue is not the router I have tried to run it directly to the modem and get the same issue

Like

Reply

0

B
Becky

+2 more

Moderator

 • 

4.3K Messages

Hi User, all your modem metrics are well within our preferred specifications; I'm not able to detect any issues. Nor have any of your traceroutes shown issues on the Cox network. MIMO events are an indicator that the modem has reset. For comparison purposes, it might be beneficial for you to test a different modem. I'm curious to see if the constant resets continue when using a different device. Cox will pro-rate the monthly rental fee if you'd like to test a different modem for a week or two. You can also get a modem from any other retailer, as long as it is on the list of compatible devices at www.cox.com/.../cox-certified-cable-modems.html. -Becky, Cox Support Forums Moderator

Like

Reply

0

C
Cox_User_Who_Ne

Contributor

 • 

50 Messages

So the issue is on your side, but I have to keep wasting my time to fix it? 

Like

Reply

0

Related Content

Recent Discussions