Network connectingdropping out every few minutes

[reck]

Can someone assist please as this has been going on for a few days now and makes working from home difficult when the connection (and work vpn) keeps dropping out every few minutes.

Started a ping up and left it running today and could see where it was dropping off very few minutes, normally for just a few seconds. 

This is on a wired connection via home plugs but we've been having problems with wifi as well along with the tv that's plugged directly into the route - Hub5.

I've put the downstream and network logs below and no idea what they mean, do the figures look ok? 

Downstream bonded channels

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

1	211000000	10.1	38	QAM 256	10
2	139000000	9.9	37	QAM 256	1
3	147000000	10.3	37	QAM 256	2
4	155000000	9.6	37	QAM 256	3
5	163000000	9.5	38	QAM 256	4
6	171000000	9.3	38	QAM 256	5
7	179000000	9.4	38	QAM 256	6
8	187000000	9.4	38	QAM 256	7
9	195000000	9.6	38	QAM 256	8
10	203000000	9.5	38	QAM 256	9
11	219000000	9.9	38	QAM 256	11
12	227000000	10	38	QAM 256	12
13	235000000	10	38	QAM 256	13
14	243000000	10	38	QAM 256	14
15	251000000	9.8	38	QAM 256	15
16	259000000	9.9	38	QAM 256	16
17	267000000	10.1	39	QAM 256	17
18	275000000	10.2	39	QAM 256	18
19	283000000	10.4	39	Unknown	19
20	291000000	10.6	39	QAM 256	20
21	299000000	10.6	39	QAM 256	21
22	307000000	10.7	39	QAM 256	22
23	315000000	10.6	39	QAM 256	23
24	323000000	10.4	39	QAM 256	24
25	331000000	10.2	39	QAM 256	25
26	339000000	10.1	39	Unknown	26
27	347000000	10.3	39	QAM 256	27
28	355000000	10.1	39	QAM 256	28
29	363000000	10.5	39	QAM 256	29
30	371000000	10.1	39	QAM 256	30
31	379000000	10.3	39	QAM 256	31

Downstream bonded channels

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

1	Locked	38	0	0
2	Locked	37	1056	126615
3	Locked	37	44771	23981
4	Locked	37	59760	70384
5	Locked	38	50173	41507
6	Locked	38	55586	32589
7	Locked	38	58890	27717
8	Locked	38	54642	25248
9	Locked	38	40169	18743
10	Locked	38	47709	20389
11	Locked	38	51255	21305
12	Locked	38	51406	21565
13	Locked	38	48236	20671
14	Locked	38	47938	21210
15	Locked	38	48611	22812
16	Locked	38	46498	24698
17	Locked	39	45229	24667
18	Locked	39	44641	24532
19	Unlocked	39	42021	23379
20	Locked	39	39465	22315
21	Locked	39	45781	24556
22	Locked	39	41499	22163
23	Locked	39	43344	23003
24	Locked	39	43067	22801
25	Locked	39	44357	24821
26	Unlocked	39	4933863	9108110
27	Locked	39	41564	22328
28	Locked	39	48124	24249
29	Locked	39	61720	19751
30	Locked	39	76232	25693
31	Locked	39	117160	19617

Network Log

Time Priority Description

28-01-2022 15:28:08	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 14:55:41	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 14:40:44	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 09:27:04	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 07:40:29	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 07:26:40	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 06:42:12	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
28-01-2022 06:25:36	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 23:44:40	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 23:37:27	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 20:46:36	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 20:38:09	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 18:13:55	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 17:50:31	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 17:36:16	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 16:40:21	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 15:33:40	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 12:21:38	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 10:14:26	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 07:18:35	error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 05:09:44	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 04:56:33	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 01:41:43	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
27-01-2022 01:09:14	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 22:47:44	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 19:52:46	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 17:30:39	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 11:37:27	warning	Dynamic Range Window violation
26-01-2022 11:37:27	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 11:36:07	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 08:23:27	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 08:23:27	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thanks

[gary_dexter]

Still too high. Reboot the hub the post the levels again after an hour or so. 

[reck]

Is it the power numbers that are too high or the RS errors, or both?

These are the logs after turning off the hub and leaving for about an hour. Power leves still around 10.

I'm still not clear what impoact having high power levels has, does it make the connection less reliable or make my speed slower or something else? What are the next steps to resolve these issues? Thanks

Downstream bonded channels

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

1	155000000	9.3	37	QAM 256	3
2	139000000	9.5	37	QAM 256	1
3	147000000	9.4	37	QAM 256	2
4	163000000	9.4	38	QAM 256	4
5	171000000	9.3	38	QAM 256	5
6	179000000	9.5	38	QAM 256	6
7	187000000	9.5	38	QAM 256	7
8	195000000	9.8	38	QAM 256	8
9	203000000	9.7	38	QAM 256	9
10	211000000	10	38	QAM 256	10
11	219000000	10.1	38	QAM 256	11
12	227000000	10.2	38	QAM 256	12
13	235000000	10.1	38	QAM 256	13
14	243000000	10.1	38	QAM 256	14
15	251000000	10	38	QAM 256	15
16	259000000	10.1	39	QAM 256	16
17	267000000	10.2	39	QAM 256	17
18	275000000	10.4	39	QAM 256	18
19	283000000	10.6	39	QAM 256	19
20	291000000	10.8	39	QAM 256	20
21	299000000	10.8	39	QAM 256	21
22	307000000	10.9	39	QAM 256	22
23	315000000	10.8	39	QAM 256	23
24	323000000	10.6	39	QAM 256	24
25	331000000	10.4	39	QAM 256	25
26	339000000	10.3	39	QAM 256	26
27	347000000	10.5	39	QAM 256	27
28	355000000	10.3	39	QAM 256	28
29	363000000	10.7	39	QAM 256	29
30	371000000	10.3	39	QAM 256	30
31	379000000	10.5	39	QAM 256	31

Downstream bonded channels

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

1	Locked	37	0	0
2	Locked	37	0	0
3	Locked	37	0	0
4	Locked	38	0	0
5	Locked	38	0	0
6	Locked	38	0	0
7	Locked	38	0	0
8	Locked	38	0	0
9	Locked	38	0	0
10	Locked	38	0	0
11	Locked	38	0	0
12	Locked	38	0	0
13	Locked	38	0	0
14	Locked	38	0	0
15	Locked	38	0	0
16	Locked	39	0	0
17	Locked	39	0	0
18	Locked	39	0	0
19	Locked	39	0	0
20	Locked	39	0	0
21	Locked	39	0	0
22	Locked	39	0	0
23	Locked	39	0	0
24	Locked	39	0	0
25	Locked	39	0	0
26	Locked	39	0	0
27	Locked	39	0	0
28	Locked	39	0	0
29	Locked	39	0	0
30	Locked	39	0	0
31	Locked	39	0	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	46200000	40.5	5120	QAM 64	1
2	39400000	40.5	5120	QAM 64	2
3	32600000	39.8	5120	QAM 64	3
4	25800000	39.3	5120	QAM 64	4

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

Network Log

Time Priority Description

04-02-2022 08:24:19	warning	Dynamic Range Window violation
04-02-2022 08:24:18	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:24:17	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:24:16	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:12:47	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:12:14	notice	REGISTRATION COMPLETE - Waiting for Operational status
04-02-2022 08:12:08	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:12:03	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:11:59	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-02-2022 08:11:57	notice	Honoring MDD; IP provisioning mode = IPv4
04-02-2022 08:11:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 08:23:27	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 08:23:27	critical	16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
26-01-2022 08:12:33	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 23:08:09	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 11:10:32	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 11:10:31	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:58:01	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:55:53	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:55:48	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.1;
25-01-2022 10:55:29	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:55:28	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.1;
25-01-2022 10:55:09	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.1;
25-01-2022 10:55:09	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:54:49	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:54:48	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.1;
25-01-2022 10:54:18	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:54:13	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:54:12	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:42:39	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:42:37	critical	SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 10:42:30	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[gary_dexter]

Levels are too high but no Post-RS errors is good.

You'll need an engineer to fix the levels. 

[reck]

Thanks Gary,

Can I book an engineer visit here or do I need to call (and wait on the phone for an hour)?

[gary_dexter]

---

@reck wrote:

Thanks Gary,

Can I book an engineer visit here or do I need to call (and wait on the phone for an hour)?

---

A forum rep will reply here but could take a few days 

[Ryan_N]

I am going to send you over a private message so I can take some details 🙂 

Cheers, 

Ryan.