cancel
Showing results for 
Search instead for 
Did you mean: 

SYNC Timing Synchronization failure - Loss of Sync & RCS Partial Service

NeedsCoffee
Tuning in

My M125 connection has been really unreliable recently, with occassionally really bad latency, slow speeds and sometimes complete loss of service. I've got a Hub3 in modem mode and my systems are experiencing problems through ethernet not just wifi.

Log shows a few criticals and warnings: RCS Partial Service and also SYNC Timing Synchronization failure - Loss of Sync

Research of similar issues here suggests I need an engineer visit as it's likely to be something between my hub and the cab. I've done all the usual things, full power-off for 10 minutes and restart, as well as checking for tight cable connections. None of that has helped so far.

Could I get some help from a support tech please? Here are my logs.

TimePriorityDescription
01/10/2023 11:43:00Warning!RCS Partial Service; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 11:43:00criticalSYNC Timing Synchronization failure - Loss of Sync; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 11:42:52Warning!RCS Partial Service; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 11:42:08criticalNo Ranging Response received - T3 time-out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 11:40:16criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0;
01/10/2023 11:38:07criticalNo Ranging Response received - T3 time-out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 11:38:07criticalUnicast Ranging Received Abort Response - initializing MAC; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 11:37:31criticalNo Ranging Response received - T3 time-out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
01/10/2023 09:15:02Warning!RCS Partial Service; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
29/09/2023 19:27:41criticalNo Ranging Response received - T3 time-out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
29/09/2023 11:33:22Warning!RCS Partial Service; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
29/09/2023 11:33:22criticalSYNC Timing Synchronization failure - Loss of Sync; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
29/09/2023 05:29:57Warning!RCS Partial Service; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
28/09/2023 22:09:03criticalNo Ranging Response received - T3 time-out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
28/09/2023 22:08:51Warning!RCS Partial Service; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
28/09/2023 16:59:52criticalNo Ranging Response received - T3 time-out; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
28/09/2023 09:36:29noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 
28/09/2023 09:36:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option; CM-MAC=48:d3:43:xx:xx:xx; CMTS-MAC=28:52:61:xx:xx:xx; CM-QOS=1.1; CM-VER=3.0; 

Thanks! Nick Clark.

NeedsCoffee - I always do...
Live BQM:
1 ACCEPTED SOLUTION

Accepted Solutions

NeedsCoffee
Tuning in

Ok my issue is resolved. In the end instead of just tightening the connections, this time I disconnected the cables coming in to the house, cleaned the connectors thoroughly as well as the connection box outside, used WD40 to ensure no water contamination, and re-tightened everything with spanners to ensure tightness. Finally i also disconnected the TV lead at the splitter and terminated that connection with a proper terminator. Not had a problem since. There was a marked drop in max latency as well as packet loss dropping to near 0. No disconnections since and speed has improved too!

NeedsCoffee - I always do...
Live BQM:

See where this Helpful Answer was posted

8 REPLIES 8

Tudor
Very Insightful Person
Very Insightful Person

Please post a full set of stats, it looks like a circuit problem. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

.

NeedsCoffee - I always do...
Live BQM:

Did you mean this stuff?

Downstream bonded channels

ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
1387000000-0.540256 qam32
22510000001.438256 qam15
32590000001.240256 qam16
42670000001.238256 qam17
5275000000138256 qam18
62830000000.738256 qam19
72910000000.238256 qam20
82990000000.438256 qam21
9307000000038256 qam22
10315000000-0.438256 qam23
11323000000-0.238256 qam24
12331000000-0.238256 qam25
13339000000038256 qam26
14347000000-0.238256 qam27
15355000000-0.438256 qam28
16363000000038256 qam29
17371000000040256 qam30
18379000000-0.438256 qam31
19395000000-0.740256 qam33
20403000000-0.938256 qam34
21411000000-0.938256 qam35
22419000000-1.438256 qam36
23523000000-5.237256 qam37
24531000000-5.737256 qam38

Downstream bonded channels

ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
1Locked40.350
2Locked38.970
3Locked40.360
4Locked38.940
5Locked38.950
6Locked38.960
7Locked38.990
8Locked38.990
9Locked38.9170
10Locked38.6190
11Locked38.9110
12Locked38.6170
13Locked38.6120
14Locked38.9130
15Locked38.9120
16Locked38.990
17Locked40.390
18Locked38.980
19Locked40.3130
20Locked38.690
21Locked38.640
22Locked38.940
23Locked37.62100
24Locked37.33570

Upstream bonded channels

ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
12360000043512064 qam5
23010000043.5512064 qam4
33660000043.5512064 qam3
44310000043.5512064 qam2
54960000045512064 qam1

Upstream bonded channels

ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0020
2ATDMA0010
3ATDMA0000
4ATDMA0000
5ATDMA0000
NeedsCoffee - I always do...
Live BQM:

Carley_S
Forum Team
Forum Team

Hi @NeedsCoffee 

Welcome to the community forums. 

Sorry to hear you're having issues with your service at this time. 

I have checked the systems at this side and all look good with your specs and I cannot find any issues within the area that might be causing this. 

I'm unable to run any further checks as your hub is in modem mode and we would need this in router mode to investigate anything else at our side. 

 

Are you able to place the hub into router mode and also set up and post a live broadband quality monitor on this forums and we'll support further with this issue. 

You can set up your live broadband quality monitor here

Here to help 🙂
Virgin Media Forums Agent
Carley

NeedsCoffee
Tuning in

Thanks for responding Carley. The live BQM is in my signature I'm pleased to say.

I will investigate switching to router mode tomorrow, however it would be a somewhat disruptive change and interfere with work so might not happen for a bit.
Here's an updated stats table in case it's useful, seem to be a lot of pre- and post- rs errors in the downstream.

Downstream bonded channels   
ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
1387000000-0.938256 qam32
22510000001.238256 qam15
32590000001.240256 qam16
4267000000138256 qam17
52750000000.738256 qam18
62830000000.738256 qam19
7291000000038256 qam20
82990000000.238256 qam21
9307000000-0.238256 qam22
10315000000-0.738256 qam23
11323000000-0.538256 qam24
12331000000-0.538256 qam25
13339000000-0.438256 qam26
14347000000-0.538256 qam27
15355000000-0.738256 qam28
16363000000-0.538256 qam29
17371000000-0.440256 qam30
18379000000-0.738256 qam31
19395000000-138256 qam33
20403000000-138256 qam34
21411000000-1.238256 qam35
22419000000-1.738256 qam36
23523000000-5.537256 qam37
24531000000-637256 qam38
      
Downstream bonded channels   
ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors 
1Locked38.9352486 
2Locked38.9485425 
3Locked40.34942239 
4Locked38.9429723 
5Locked38.9412676 
6Locked38.9434604 
7Locked38.6488611 
8Locked38.9428605 
9Locked38.9462596 
10Locked38.6455640 
11Locked38.9446675 
12Locked38.6432758 
13Locked38.6425737 
14Locked38.9390703 
15Locked38.9396654 
16Locked38.6380689 
17Locked40.3381705 
18Locked38.6354653 
19Locked38.9331673 
20Locked38.9350601 
21Locked38.9373662 
22Locked38.6403769 
23Locked37.61640778 
24Locked37.62393711 
      
Upstream bonded channels   
ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
12360000043.5512064 qam5
23010000045512064 qam4
33660000045512064 qam3
44310000045512064 qam2
54960000045512064 qam1
      
      
Upstream bonded channels   
ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0020
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0000

Here are some monitoring graphs for the last few days...

Mon 2nd October
Mon 2nd OctMon 2nd Oct

 Tue 3rd October
Tue 3rd OctoberTue 3rd October

 Wed 4th October
Wed 4th OctoberWed 4th October

 Thank you for your help!

NeedsCoffee - I always do...
Live BQM:

Thank you for replying Carley.
My live BQM is in my profile I'm pleased to say.

I'll investigate switching back to router mode tomorrow. It'll be a bit disruptive for my work so might be a while before I can do that.

Here are some up to date stats from the Hub3, getting loads of Rs errors in the downstream...

Downstream bonded channels   
ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
1387000000-0.938256 qam32
22510000001.238256 qam15
32590000001.240256 qam16
4267000000138256 qam17
52750000000.738256 qam18
62830000000.738256 qam19
7291000000038256 qam20
82990000000.238256 qam21
9307000000-0.238256 qam22
10315000000-0.738256 qam23
11323000000-0.538256 qam24
12331000000-0.538256 qam25
13339000000-0.438256 qam26
14347000000-0.538256 qam27
15355000000-0.738256 qam28
16363000000-0.538256 qam29
17371000000-0.440256 qam30
18379000000-0.738256 qam31
19395000000-138256 qam33
20403000000-138256 qam34
21411000000-1.238256 qam35
22419000000-1.738256 qam36
23523000000-5.537256 qam37
24531000000-637256 qam38
      
Downstream bonded channels   
ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
1Locked38.9352486 
2Locked38.9485425 
3Locked40.34942239 
4Locked38.9429723 
5Locked38.9412676 
6Locked38.9434604 
7Locked38.6488611 
8Locked38.9428605 
9Locked38.9462596 
10Locked38.6455640 
11Locked38.9446675 
12Locked38.6432758 
13Locked38.6425737 
14Locked38.9390703 
15Locked38.9396654 
16Locked38.6380689 
17Locked40.3381705 
18Locked38.6354653 
19Locked38.9331673 
20Locked38.9350601 
21Locked38.9373662 
22Locked38.6403769 
23Locked37.61640778 
24Locked37.62393711 
      
Upstream bonded channels   
ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
12360000043.5512064 qam5
23010000045512064 qam4
33660000045512064 qam3
44310000045512064 qam2
54960000045512064 qam1
      
      
Upstream bonded channels   
ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0020
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0000

Things were pretty glitchy on Tuesday 3rd Oct:

e005d89efcf30efe51a8deac5e39792b3ad59c22-03-10-2023

NeedsCoffee - I always do...
Live BQM:

NeedsCoffee
Tuning in

Ok my issue is resolved. In the end instead of just tightening the connections, this time I disconnected the cables coming in to the house, cleaned the connectors thoroughly as well as the connection box outside, used WD40 to ensure no water contamination, and re-tightened everything with spanners to ensure tightness. Finally i also disconnected the TV lead at the splitter and terminated that connection with a proper terminator. Not had a problem since. There was a marked drop in max latency as well as packet loss dropping to near 0. No disconnections since and speed has improved too!

NeedsCoffee - I always do...
Live BQM:

Thanks for coming back to us NeedsCoffee and I'm glad to hear that your issues have now been resolved.

Kind Regards,

Steven_L