Skip to content
Yong's profile

Visitor

 • 

4 Messages

Sunday, October 7th, 2018 4:00 PM

Intermittent connectivity/drops

Certain time of day, this occurs on my modem. Logs are filled with T3 timeouts and none of the people that I talk to seemed to understand that there is an issue. Had a scheduled appointment on 10/6/2018 but no one ever showed up. I just need someone to check the line outside on the pole at this point. I've tested both the splitter and multiple different coax lines with the same result. Also, attaching the modem to the main coax line produces the same results on the modem. I just need someone to come out and actually fix the issue on the line.

 

Here's an image during what I think may be peak in my neighborhood: 64cb0e6b9797c81d18185c4315cba77f.png

Here's the logs I get spammed with:

Oct 07 2018 17:42:17	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:42:16	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:41:37	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:41:36	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:40:57	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:40:56	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:40:17	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:40:17	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:39:37	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:39:37	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:38:57	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:38:57	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:38:17	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:38:17	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:37:37	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 17:37:37	3-Critical	R07.0	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 10:37:22	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 10:17:48	3-Critical	R06.0	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 10:17:48	3-Critical	R03.0	Ranging Request Retries exhausted;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;
Oct 07 2018 10:17:46	3-Critical	R02.0	No Ranging Response received - T3 time-out;CM-MAC=20:3d:66:0b:a7:52;CMTS-MAC=00:38:df:08:f5:cb;CM-QOS=1.1;CM-VER=3.0;

After multiple modems and multiple tests..been suffering from random disconnects since 9/27/2018.

Accepted Solution

New problem solver

 • 

163 Messages

6 years ago

Hello, I just wanted to follow up with you. I see that our maintenance team has completed some repairs in the area. How is everything working for you? 

Problem solver

 • 

348 Messages

6 years ago

Hi there, I would be more than happy to help with your service concerns. Can you please send a private message with the phone number, full address of the account, and your name? 

Visitor

 • 

4 Messages

6 years ago

The schedule between 10AM-12PM will work. Can no longer send private messages.