Poor connection to network low db power with sync timing issues

[davejs2021]

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;

1	202750000	-6.9	38	256 qam	9
2	138750000	-7.9	36	256 qam	1
3	146750000	-7.4	36	256 qam	2
4	154750000	-7	37	256 qam	3
5	162750000	-7	37	256 qam	4
6	170750000	-7.4	37	256 qam	5
7	178750000	-7	37	256 qam	6
8	186750000	-6.7	37	256 qam	7
9	194750000	-6.9	37	256 qam	8
10	210750000	-6.7	37	256 qam	10
11	218750000	-6.5	38	256 qam	11
12	226750000	-6.7	38	256 qam	12
13	234750000	-6.9	37	256 qam	13
14	242750000	-7.5	37	256 qam	14
15	250750000	-7.2	37	256 qam	15
16	258750000	-7.4	37	256 qam	16
17	266750000	-7.4	37	256 qam	17
18	274750000	-7.5	37	256 qam	18
19	282750000	-7.4	37	256 qam	19
20	290750000	-7.4	37	256 qam	20
21	298750000	-7.2	37	256 qam	21
22	306750000	-7.2	37	256 qam	22
23	314750000	-7.2	37	256 qam	23
24	322750000	-7.5	37	256 qam	24

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

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

1	Locked	38.9	3672	16
2	Locked	36.1	145536708	71587394
3	Locked	36.6	18569119	367318
4	Locked	37.6	5882	28
5	Locked	37.6	5250	23
6	Locked	37.3	5133	17
7	Locked	37.6	4856	12
8	Locked	37.3	4312	5
9	Locked	37.6	4263	19
10	Locked	37.6	3083	9
11	Locked	38.6	3076	58
12	Locked	38.6	2910	18
13	Locked	37.6	2369	4
14	Locked	37.3	2488	0
15	Locked	37.6	2415	1
16	Locked	37.9	2189	0
17	Locked	37.6	2012	0
18	Locked	37.6	1949	0
19	Locked	37.6	1901	0
20	Locked	37.6	1831	0
21	Locked	37.6	1963	0
22	Locked	37.6	1781	0
23	Locked	37.6	1639	0
24	Locked	37.6	2026	0

[jbrennand]

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.

[davejs2021]

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

[davejs2021]

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

[lotharmat · Accepted solution]

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!

[jbrennand]

May be quicker to call CS and point out the errors

[Adduxi]

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

[davejs2021]

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

[Tudor]

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

[davejs2021]

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?