Menu
Reply
davejs2021
  • 8
  • 0
  • 0
Tuning in
225 Views
Message 1 of 17
Flag for a moderator

Poor connection to network low db power with sync timing issues

My wired and W-iFi connections constantly drop using a Hub3.

Reading other users posts about the "SYNC Timing Synchronization failure - Loss of Sync" logs, I too have the same issue:

What is the cause?  It's a real nuisance and telephone support say all is well.  It's definitely not:

Time Priority Description

Time

Priority

Description

05/07/2021 12:11:3

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

03/07/2021 23:00:52

Warning!

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

02/07/2021 16:48:33

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

02/07/2021 15:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

02/07/2021 09:57:10

critical

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

01/07/2021 19:23:34

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2021 18:18:11

notice

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

29/06/2021 04:24:21

critical

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

29/06/2021 03:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

28/06/2021 14:51:22

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/06/2021 15:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/06/2021 08:55:55

critical

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

24/06/2021 01:52:14

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

23/06/2021 16:27:41

Warning!

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

23/06/2021 16:27:36

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

23/06/2021 16:27:34

Warning!

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

23/06/2021 13:51:39

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

22/06/2021 03:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

19/06/2021 17:58:46

critical

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

18/06/2021 14:34:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

1202750000-6.938256 qam9
2138750000-7.936256 qam1
3146750000-7.436256 qam2
4154750000-737256 qam3
5162750000-737256 qam4
6170750000-7.437256 qam5
7178750000-737256 qam6
8186750000-6.737256 qam7
9194750000-6.937256 qam8
10210750000-6.737256 qam10
11218750000-6.538256 qam11
12226750000-6.738256 qam12
13234750000-6.937256 qam13
14242750000-7.537256 qam14
15250750000-7.237256 qam15
16258750000-7.437256 qam16
17266750000-7.437256 qam17
18274750000-7.537256 qam18
19282750000-7.437256 qam19
20290750000-7.437256 qam20
21298750000-7.237256 qam21
22306750000-7.237256 qam22
23314750000-7.237256 qam23
24322750000-7.537256 qam24

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

 

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.9367216
2Locked36.114553670871587394
3Locked36.618569119367318
4Locked37.6588228
5Locked37.6525023
6Locked37.3513317
7Locked37.6485612
8Locked37.343125
9Locked37.6426319
10Locked37.630839
11Locked38.6307658
12Locked38.6291018
13Locked37.623694
14Locked37.324880
15Locked37.624151
16Locked37.921890
17Locked37.620120
18Locked37.619490
19Locked37.619010
20Locked37.618310
21Locked37.619630
22Locked37.617810
23Locked37.616390
24Locked37.620260
0 Kudos
Reply
jbrennand
  • 23.79K
  • 2.52K
  • 4.31K
Very Insightful Person
Very Insightful Person
211 Views
Message 2 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

Can you post the upstream data too but before that can you reset the RS errors to 0 by doing the below.

that said your down power levels are all outside of the recommended range -6dBmV being the minimum. And postRS errors are suggesting a noise issue that will need a tech visit
___________

Switch the Hub off and unplug it for a few minutes and then start up. When done, check back in the settings and ensure that the RS error counts have all reset to 0. Then check every hour or two to see if they start reappearing - they shouldn't. If they do (particularly the postRS ones) you have a problem (noise) that only a Tech visit will sort.

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router +2 Airport Express's. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
davejs2021
  • 8
  • 0
  • 0
Tuning in
155 Views
Message 3 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

Hi John,

Thank you for responding.  I have followed your steps and although the RS port errors have reset to 0, the DB is still low.  Please see updates below:

Time Priority Description

ime

Priority

Description

06/07/2021 11:42:10

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06/07/2021 03:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

05/07/2021 17:06:3

critical

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

05/07/2021 13:03:49

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

05/07/2021 12:53:53

critical

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

05/07/2021 12:44:13

Warning!

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

05/07/2021 12:11:3

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

03/07/2021 23:00:52

Warning!

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

02/07/2021 16:48:33

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

02/07/2021 15:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

02/07/2021 09:57:10

critical

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

01/07/2021 19:23:34

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

01/07/2021 18:18:11

notice

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

29/06/2021 04:24:21

critical

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

29/06/2021 03:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

28/06/2021 14:51:22

notice

LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/06/2021 15:04:5

Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

25/06/2021 08:55:55

critical

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

24/06/2021 01:52:14

Warning!

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

23/06/2021 16:27:41

Warning!

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

 

Channel

Frequency (Hz)

Power (dBmV)

SNR (dB)

Modulation

Channel ID

1

202750000

-7

37

256 qam

9

2

138750000

-8

36

256 qam

1

3

146750000

-7.5

36

256 qam

2

4

154750000

-7.2

37

256 qam

3

5

162750000

-7.5

37

256 qam

4

6

170750000

-7.7

37

256 qam

5

7

178750000

-7.2

37

256 qam

6

8

186750000

-7.2

37

256 qam

7

9

194750000

-7.2

37

256 qam

8

10

210750000

-7

37

256 qam

10

11

218750000

-6.9

37

256 qam

11

12

226750000

-7

37

256 qam

12

13

234750000

-7.2

37

256 qam

13

14

242750000

-7.7

37

256 qam

14

15

250750000

-7.5

37

256 qam

15

16

258750000

-7.5

37

256 qam

16

17

266750000

-7.5

37

256 qam

17

18

274750000

-7.5

37

256 qam

18

19

282750000

-7.5

37

256 qam

19

20

290750000

-7.7

37

256 qam

20

21

298750000

-7.4

37

256 qam

21

22

306750000

-7.5

37

256 qam

22

23

314750000

-7.4

37

256 qam

23

24

322750000

-7.5

37

256 qam

24

 

Channel

Locked Status

RxMER (dB)

Pre RS Errors

Post RS Errors

1

Locked

37.6

21

0

2

Locked

36.3

4818

0

3

Locked

36.6

15

0

4

Locked

37.6

14

0

5

Locked

37.3

9

0

6

Locked

37.3

10

0

7

Locked

37.6

26

0

8

Locked

37.6

21

0

9

Locked

37.6

23

0

10

Locked

37.3

7

0

11

Locked

37.6

7

0

12

Locked

37.6

9

0

13

Locked

37.6

9

0

14

Locked

37.6

5

0

15

Locked

37.6

9

0

16

Locked

37.6

11

0

17

Locked

37.6

9

0

18

Locked

37.6

8

0

19

Locked

37.6

9

0

20

Locked

37.6

7

0

21

Locked

37.6

9

0

22

Locked

37.6

6

0

23

Locked

37.6

8

0

24

Locked

37.6

5

0



So with the above information, would you suggest a VM engineer visit?

Thanks in advance.

Dave

0 Kudos
Reply
davejs2021
  • 8
  • 0
  • 0
Tuning in
154 Views
Message 4 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

More info

Channel

Frequency (Hz)

Power (dBmV)

Symbol Rate (ksps)

Modulation

Channel ID

1

25800015

46.5

5120

64 qam

8

2

46200000

46.5

5120

64 qam

5

3

39400000

46.3

5120

64 qam

6

4

32600000

46.3

5120

64 qam

7

0 Kudos
Reply
lotharmat
  • 2.54K
  • 188
  • 458
Trouble shooter
150 Views
Message 5 of 17
Flag for a moderator
Helpful Answer

Re: Poor connection to network low db power with sync timing issues

Downstream power is too low - SHould be between -6 and +10 dBmV

VM will need to arrange an engineer to rectify! - They should pick this up soon!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

jbrennand
  • 23.79K
  • 2.52K
  • 4.31K
Very Insightful Person
Very Insightful Person
147 Views
Message 6 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

May be quicker to call CS and point out the errors

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router +2 Airport Express's. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
Adduxi
  • 3.16K
  • 248
  • 685
Very Insightful Person
Very Insightful Person
136 Views
Message 7 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

Also check if you have any attenuators fitted in the circuit?  If so remove it and re-check the power levels.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

davejs2021
  • 8
  • 0
  • 0
Tuning in
113 Views
Message 8 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

The us no attenuator but there is a splitter.  This is 4.5db on each channel so shouldn't effect the low power.

 

VM Splitter.jpg

0 Kudos
Reply
Tudor
  • 8.45K
  • 674
  • 1.51K
Very Insightful Person
Very Insightful Person
104 Views
Message 9 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

A splitter like that will certainly affect the downstream power levels.


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
davejs2021
  • 8
  • 0
  • 0
Tuning in
93 Views
Message 10 of 17
Flag for a moderator

Re: Poor connection to network low db power with sync timing issues

Thank you, yes, one goes to the router and the other to the Virging Media Tivo unit... I'm assuming that all installs are this way or is just mine?

0 Kudos
Reply