Multiple Errors on my Docsis 3.0 model with Cox

Question

I have noticed some speed issues with my Cox Internet connection so I logged in to look at the logs on the modem and found the following errors which are repeating every day. &nbsp; Before I call support and get told nothing is wrong I was hoping for some expert direction from the collective within the forum.

Apr 13 2017 07:17:29
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:12:30
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:12:30
3-Critical
R03.0
Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:12:15
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:11:45
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:11:45
3-Critical
R03.0
Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:11:30
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:10:15
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:10:15
3-Critical
R03.0
Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 07:09:45
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:56:33
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:56:33
3-Critical
R03.0
Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:56:18
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:55:48
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:55:48
3-Critical
R03.0
Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:55:33
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:54:18
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:54:18
3-Critical
R03.0
Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:53:48
3-Critical
R02.0
No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

Apr 13 2017 06:40:36
3-Critical
R06.0
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;

chrisl · Answer

@AZ_Internet_User

The signal levels reported look good but the T3 error counts are elevated suggesting the modem is having trouble communicating back to us.  Are there any cable splitters you can try bypassing and seeing if that helps?

Forum Discussion

Multiple Errors on my Docsis 3.0 model with Cox

1 Reply

Related Content

Trouble with Motorola SB6141 Docsis 3.0 modem and T3 errors.

Preferred Service getting 10Mbps w/3.0 DOCSIS

Arris SB6183 Docsis 3.0 consistently rebooting multiple times

Multiple connection timeouts happening every few minutes

Critical T3 Errors - Multiple

Recent Discussions

Welcome to the Archives

Gigablast

Beeping Noise

mic/status led on contour 2 remote

Internet connectivity frustrations

Apr 13 2017 07:17:29	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:12:30	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:12:30	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:12:15	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:11:45	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:11:45	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:11:30	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:10:15	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:10:15	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 07:09:45	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:56:33	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:56:33	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:56:18	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:55:48	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:55:48	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:55:33	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:54:18	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:54:18	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:53:48	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;
Apr 13 2017 06:40:36	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=d0:39:b3:f8:ed:dd;CMTS-MAC=00:1b:54:c9:87:c7;CM-QOS=1.1;CM-VER=3.0;