Im back, yet again. Dropouts HUB5

[BaronVonStrudel]

I had resurrected my last thread but i think its been lost.

Anyway.  Im back again, same problem.

Ever since November when i switched to a HUB5, i have been getting dropouts.

I have a couple of threads on this problem. An engineer was sent out at the end of November stuck and attenuator on the back of my router did some checks and left.

It was ok for a few weeks and then it started to drop out.

I think i need to go back to my old router , how would i go about this as i no longer have it?

Ill post all my usual logs and BQM link 

Downstream bonded channels

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

1	155000000	6.7	40	QAM 256	3
2	139000000	6.9	40	QAM 256	1
3	147000000	6.7	40	QAM 256	2
4	163000000	6.8	40	QAM 256	4
5	171000000	6.7	40	QAM 256	5
6	179000000	6.6	41	QAM 256	6
7	187000000	6.8	41	QAM 256	7
8	195000000	7	41	QAM 256	8
9	203000000	6.9	41	QAM 256	9
10	211000000	7.3	41	QAM 256	10
11	219000000	7.4	41	QAM 256	11
12	227000000	7.5	41	QAM 256	12
13	235000000	7.4	41	QAM 256	13
14	243000000	7.3	41	QAM 256	14
15	251000000	7.4	41	QAM 256	15
16	259000000	7.4	41	QAM 256	16
17	267000000	7.2	41	QAM 256	17
18	275000000	7.3	41	QAM 256	18
19	283000000	7.5	41	QAM 256	19
20	291000000	7.5	41	QAM 256	20
21	299000000	7.2	41	QAM 256	21
22	307000000	7.3	41	QAM 256	22
23	315000000	7.4	41	QAM 256	23
24	323000000	7.2	41	QAM 256	24
25	331000000	7	41	QAM 256	25
26	339000000	7.1	40	QAM 256	26
27	347000000	7.1	41	QAM 256	27
28	355000000	6.9	41	QAM 256	28
29	363000000	6.7	41	QAM 256	29
30	371000000	6.8	41	QAM 256	30
31	379000000	7	41	QAM 256	31

Downstream bonded channels

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

1	Locked	40	317649	329445
2	Locked	40	122365	971888
3	Locked	40	99570	69281
4	Locked	40	212590	607460
5	Locked	40	226196	244723
6	Locked	41	74	413435
7	Locked	41	0	95
8	Locked	41	0	0
9	Locked	41	0	0
10	Locked	41	0	0
11	Locked	41	0	0
12	Locked	41	0	0
13	Locked	41	0	3
14	Locked	41	0	6
15	Locked	41	0	4
16	Locked	41	0	2
17	Locked	41	0	0
18	Locked	41	0	1
19	Locked	41	0	0
20	Locked	41	0	0
21	Locked	41	0	0
22	Locked	41	0	0
23	Locked	41	0	0
24	Locked	41	0	0
25	Locked	41	0	0
26	Locked	40	0	0
27	Locked	41	0	0
28	Locked	41	0	0
29	Locked	41	0	0
30	Locked	41	0	0
31	Locked	41	0	0

Upstream bonded channels

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

1	60300000	44.3	5120	QPSK	1
2	53700000	43.8	5120	QPSK	2
3	46200000	43.5	5120	QPSK	3
4	39400000	43.5	5120	QPSK	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

02-02-2022 05:12:37	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
02-02-2022 01:56:05	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;
01-02-2022 23:33:37	notice	CM-STATUS message sent. Event Type Code: 5; Chan ID: 37; 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;
01-02-2022 23:33:25	notice	REGISTRATION COMPLETE - Waiting for Operational status
01-02-2022 23:33:19	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:33:16	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:33:14	notice	Honoring MDD; IP provisioning mode = IPv4
01-02-2022 23:33:05	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:33:04	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:33:00	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:30:57	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:30: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.1;
01-02-2022 23:26:53	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:26:53	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
01-02-2022 23:26:18	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;
01-02-2022 22:03:52	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

BGM

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0199012695d6ccb421fd15ac11dc128e9b...

[Adduxi]

Your BB circuit needs attention.  There are many SYNC errors, PostRS errors and your US channels should all be 64QAM.  Bit of a mess really.

Phone it in or wait here a day or two for a VM Mod to pick this up.

[Carley_S]

Hi @BaronVonStrudel

Sorry to hear the issue is still ongoing. I can see on our systems that there are issues that would need a technician to attend. 

I will continue this in private messages so we ca discuss. Please look out for my PM in your inbox.

[Carley_S]

Thank you for joining me on private message @BaronVonStrudel

Hopefully this will all be resolved for you now. Let us know if you have any other issues. We'll be here to help. 

All the best,