Community Forum

No Ranging Response received - T3

New Poster

No Ranging Response received - T3

Good morning -

 

Upgraded our service about 2 weeks ago to "Blast Pro" and have been noticing intermittent issues since, with our modem showing a bunch of items in the event log and resetting 3 times yesterday alone.

 

Tried to call customer service this morning, but after spending 45 unproductive minutes on the phone, the rep had no way to even view or have me send my event log to her (*sigh*). At one point, she texted me a link to schedule a service call that would have also roped me into a modem rental agreement, without even knowing what my issue was.

 

Anyone have any clues? As far as I can tell, my stats all seem to look good?

 

Have a tech scheduled for Wednesday, but seems like such a  waste to roll a truck without even looking at, or considering, my event logs...

 

Thanks!

 

Modem - Motorola mb8600
Software Version - 8600-18.2.12

 

Event Log

22:55:50
Sun Jul 21 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:55:50
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:01
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:08
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:08
Sun Jul 21 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:08
Sun Jul 21 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:13
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:14
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:14
Sun Jul 21 2019 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:14
Sun Jul 21 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:32
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:36
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:37
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:38
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:47
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:47
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:56:54
Sun Jul 21 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:57:08
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:57:33
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:57:59
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:58:36
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:59:52
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:59:52
Sun Jul 21 2019 Critical (3) Ranging Request Retries exhausted;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
22:59:52
Sun Jul 21 2019 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
23:00:51
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
23:00:54
Sun Jul 21 2019 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
23:01:24
Sun Jul 21 2019 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
04:45:00
Mon Jul 22 2019 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:01:5c:86:7c:77;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=00:40:36:4e:94:f3;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established
Notice (6) Honoring MDD; IP provisioning mode = IPv6

 

upstream.jpgconnection.jpg

Andy Gradel
Expert

Re: No Ranging Response received - T3

Can't see your pics. Only see the error log entries. Since you are a new poster, they likely need to be approved by a Forum Admin. Or you may need to make a minimum number of posts.

You could try hosting them at one of those free third-party pic hosting sites like Imgur or Photobucket and post the link to them here.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
New Poster

Re: No Ranging Response received - T3

Good catch @EG 

 

Here they are in Google Photos:

 

Upstream
https://photos.app.goo.gl/4kFHeXpEmHSA3y8D8

 

Downstream
https://photos.app.goo.gl/rictZWfqneJs71Mg6

Andy Gradel
New Poster

Re: No Ranging Response received - T3

And here come the uncorrected errors, about 2 hours after my last reboot.

 

Updated downstream w/errors
https://photos.app.goo.gl/PRXEkz1foXWGr6Z78

Andy Gradel
Expert

Re: No Ranging Response received - T3

You're right. The signal stats looked o/k at that snapshot in time, but the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.


There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.

 

The tech can poll the system for them. See what he has to say when he comes out. Good luck with it !

 



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!