Menu
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
472 Views
Message 31 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub 2 logs.

Thank you. No problem.

Yes there's a galvanic isolator. I understand they drop the signal by a few dB (?)  and I shouldn't remove it - but I suspect   😉 the problem still happens if it isn't there...

I did also switch off a TV Tivo box and remove the splitter it was fed from to squeeze a little more signal from the co-ax and still have the issue.

 

The Superhub(3) network log is shoing:

 

 

ime Priority Description

06/05/2020 13:44:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:44:31criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:43:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:43:10criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:39:24Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:32:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:31:15criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:30:21noticeNOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:27:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:27:14criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:23criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:17Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:17criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:6noticeNOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
Eeeps
  • 737
  • 47
  • 118
Rising star
463 Views
Message 32 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub 2 logs.

Those logs really don't look good. I've never seen the 'NOTICE ATOM is restarted as part of Self Healing Mechanism'!

Can you also post the downstream and upstream logs. The 'SYNC Timing Synchronization failure - Loss of Sync' suggests a downstream problem.

Your signal levels during an outage may help.


@AnthonyW1 wrote:

Thank you. No problem.

Yes there's a galvanic isolator. I understand they drop the signal by a few dB (?)  and I shouldn't remove it - but I suspect   😉 the problem still happens if it isn't there...

I did also switch off a TV Tivo box and remove the splitter it was fed from to squeeze a little more signal from the co-ax and still have the issue.

 

The Superhub(3) network log is shoing:

 

 

ime Priority Description

06/05/2020 13:44:31Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:44:31criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:43:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:43:10criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:39:24Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:32:35criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:31:15criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:30:21noticeNOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:27:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:27:14criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:26:23criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:17Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:17criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:14Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2020 13:24:6noticeNOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 


 

0 Kudos
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
444 Views
Message 33 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub 2 logs.

f864714dec81519b9af4c83c07ea8e463cff6215.png

 

 

0 Kudos
Reply
Martin_N
  • 4.99K
  • 204
  • 282
Forum Team
Forum Team
430 Views
Message 34 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

Thank you for that AnthonyW1. 

 

Can you confirm from when this monitor is?

 

^Martin

0 Kudos
Reply
jem101
  • 1.52K
  • 216
  • 714
Very Insightful Person
Very Insightful Person
424 Views
Message 35 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

@Martin_N the date is on the BQM written along the vertical line. It's from 1pm yesterday (6th) to 1pm today ('ish)

0 Kudos
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
400 Views
Message 36 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

today.

 

and i got a few bits of log while it was going on..

 

 

 

Downstream bonded channels

 

ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID

1

459000000

3.5

35

256 qam

7



Downstream bonded channels

 

ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors

1

Locked

35.5

32

20

 

 

Upstream bonded channels

 

ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID



Upstream bonded channels

 

ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts

 

 

 

Cable Modem StatusItemStatusComments

Acquired Downstream Channel (Hz)

459000000

Ranging

Ranged Upstream Channel (Hz)

Update in progress

undefined

Provisioning State

Offline

 




ItemStatusComments

Acquired Downstream Channel (Hz)

459000000

Locked

Ranged Upstream Channel (Hz)

Update in progress

Locked

Provisioning State

Online

 


Downstream bonded channels

 

ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID

1

459000000

3.5

35

256 qam

7



Downstream bonded channels

 

ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors

1

Locked

35.5

32

20



Upstream bonded channels

 

ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID



Upstream bonded channels

 

ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts





 

0 Kudos
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
399 Views
Message 37 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

TimePriorityDescription

07/05/2020 12:00:50

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 12:00:15

critical

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:58:0

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:56:13

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:56:12

critical

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:56:12

critical

Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:55:57

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:55:53

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:55:53

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:55:53

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:55:29

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:54:26

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:54:26

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:40:53

critical

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:39:7

notice

NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:37:20

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:36:52

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:33:24

Warning!

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:33:24

critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

07/05/2020 11:32:11

critical

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
388 Views
Message 38 of 41
Flag for a moderator
Helpful Answer

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

 

Wouldn't it be great if the superhub3 had a plain text log you could pull instead of fishing around a tabbed interface during an outage while the rest of the family are complaining to you as the house tech...

So I poked around the structure of the superhub3 status pages and worked out:

http://192.168.100.1/getRouterStatus

outputs a large JQuery response with all the info in it for all the tabbed pages.

So I can now:

curl http://192.168.100.1/getRouterStatus > outage7.txt

from my linux box.  

And also

curl http://192.168.100.1/getRouterStatus | egrep -B1 -A1 "Ranging|SYNC|Partial|NOTICE|LAN"

 

Which gives:

 

100 18257"1.3.6.1.2.1.69.1.5.8.1.5.1":"3", 0 0:00:07 0:00:01 0:00:06 2290
100 182"1.3.6.1.2.1.69.1.5.8.1.7.1":"No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
57 0"1.3.6.1.2.1.69.1.5.8.1.2.2":"07/05/2020 11:58:0",
"1.3.6.1.2.1.69.1.5.8.1.5.2":"5",
"1.3.6.1.2.1.69.1.5.8.1.7.2":"RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
0 "1.3.6.1.2.1.69.1.5.8.1.2.3":"07/05/2020 12:00:15",
--
"1.3.6.1.2.1.69.1.5.8.1.5.4":"6",
15"1.3.6.1.2.1.69.1.5.8.1.7.4":"NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
176"1.3.6.1.2.1.69.1.5.8.1.2.5":"07/05/2020 12:10:22",
"1.3.6.1.2.1.69.1.5.8.1.5.5":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.5":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.6":"07/05/2020 12:10:22",
"1.3.6.1.2.1.69.1.5.8.1.5.6":"5",
"1.3.6.1.2.1.69.1.5.8.1.7.6":"RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.7":"07/05/2020 12:11:37",
"1.3.6.1.2.1.69.1.5.8.1.5.7":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.7":"No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.8":"07/05/2020 12:12:21",
"1.3.6.1.2.1.69.1.5.8.1.5.8":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.8":"Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.9":"07/05/2020 12:12:21",
"1.3.6.1.2.1.69.1.5.8.1.5.9":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.9":"Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.10":"07/05/2020 12:12:21",
"1.3.6.1.2.1.69.1.5.8.1.5.10":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.10":"Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.11":"07/05/2020 12:12:21",
"1.3.6.1.2.1.69.1.5.8.1.5.11":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.11":"Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.12":"07/05/2020 12:12:22",
"1.3.6.1.2.1.69.1.5.8.1.5.12":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.12":"No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.13":"07/05/2020 12:12:38",
"1.3.6.1.2.1.69.1.5.8.1.5.13":"5",
"1.3.6.1.2.1.69.1.5.8.1.7.13":"RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
0 0:00:01 0:00:01 --:--:-- 15176
"1.3.6.1.2.1.69.1.5.8.1.2.14":"07/05/2020 12:12:41",
"1.3.6.1.2.1.69.1.5.8.1.5.14":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.14":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.15":"07/05/2020 12:12:41",
"1.3.6.1.2.1.69.1.5.8.1.5.15":"5",
"1.3.6.1.2.1.69.1.5.8.1.7.15":"RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.16":"07/05/2020 12:13:10",
"1.3.6.1.2.1.69.1.5.8.1.5.16":"3",
"1.3.6.1.2.1.69.1.5.8.1.7.16":"SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.17":"07/05/2020 12:13:10",
"1.3.6.1.2.1.69.1.5.8.1.5.17":"5",
"1.3.6.1.2.1.69.1.5.8.1.7.17":"RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.18":"07/05/2020 12:17:5",
"1.3.6.1.2.1.69.1.5.8.1.5.18":"6",
"1.3.6.1.2.1.69.1.5.8.1.7.18":"NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.2.1.69.1.5.8.1.2.19":"07/05/2020 12:17:11",
--
"1.3.6.1.2.1.69.1.5.8.1.5.20":"5",
"1.3.6.1.2.1.69.1.5.8.1.7.20":"RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;",
"1.3.6.1.4.1.4115.1.20.1.1.1.7.1.3.1":"0.0.0.0",

 

 

Which is a start at least..

0 Kudos
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
383 Views
Message 39 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

and that bad day of many outages that matches the log pull looks like this

 

Screenshot from 2020-05-07 20-00-45.png

0 Kudos
Reply
AnthonyW1
  • 37
  • 3
  • 0
On our wavelength
340 Views
Message 40 of 41
Flag for a moderator

Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub ...

So.

 

Engineer came. Nice guy. Very helpful (Gerrard).

Checked the house junction box and the cable in the street cabinet.

Street cab connector was loose and also the "stinger" the fat copper wire inside was bent and close to the surrounding.

Chopped and put on new connector. Moved to the top tap on the street cab. Made tight.

Also refreshed the connector into the house.

Reboot Superhub. and so far zero postRSErrors on the downstream. Before this with 3 days uptime, I had between 5 thousand and fifteen thousand postRSerrors per each of the 24 channels.

So looking promising the root cause has been found and fixed.

Will monitor the hub stats for a next week - look out for our of range numbers and postRSErrors in particular and upload the BQM charts.

 

If stable then I'll upgrade to 350Mb.....

0 Kudos
Reply