Have been seeing this for 40 mins
 

07/09/2020 11:52:58 critical No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;


07/09/2020 11:51:38 critical No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;

07/09/2020 11:51:38 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;

07/09/2020 11:49:58 critical No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;

No change to service, everything appears ok

---------- Post added at 12:54 ---------- Previous post was at 11:54 ----------

Re boot HUB 3, problem solved.

---------- Post added at 13:34 ---------- Previous post was at 12:54 ----------

Problem returned.
07/09/2020 13:30:50 critical No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;

07/09/2020 13:33:30 critical No Ranging Response received - T3 time-out;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;
07/09/2020 13:33:29 critical Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=18:35:d1:33:20:6b;CMTS-MAC=04:62:73:e4:db:1f;CM-QOS=1.1;CM-VER=3.0;

Re: Have been seeing this for 40 mins
 

I have been getting them for years. If it isn't affecting your performance don't worry about it. I think it is all to do with the cmts not responding to a shub's request within a set time period (e.g. 2ms).

Re: Have been seeing this for 40 mins
 

Thanks, this has only just started, not affecting performance, all other parameters look ok.

---------- Post added at 10:02 ---------- Previous post was at 09:45 ----------

Think I can now wrap this up, now appears to be all back to normal.