Upload Speed Flucuations

[Uli]

Just got the new HUB 5 to replace my old HUB 4, I might have had the problem on the old hub but didn't notice.  Got it in modem mode and done reboots (5 minute off then on) and hasn't fixed the problem, called the automated number and theres no faults in the area.

Currently my upload flucates massively between 18mbps and 36mbps (On the M350 Package), upload is a solid 360mbps+

What I've noticed is in the router stats a lot of the time the upstream modulation is QAM 16, during the day today for a few hours it was QAM 32, for a whole 2 minutes at one point today it was QAM 64.

Router Stats

Downstream bonded channels

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

1	330000000	6.4	42	QAM 256	25
2	178000000	4.7	42	QAM 256	6
3	186000000	4.9	42	QAM 256	7
4	194000000	5.4	42	QAM 256	8
5	202000000	5.6	42	QAM 256	9
6	210000000	6	42	QAM 256	10
7	218000000	6	42	QAM 256	11
8	226000000	6	42	QAM 256	12
9	234000000	6	42	QAM 256	13
10	242000000	6	42	QAM 256	14
11	250000000	5.9	42	QAM 256	15
12	258000000	5.8	42	QAM 256	16
13	266000000	5.9	42	QAM 256	17
14	274000000	6	42	QAM 256	18
15	282000000	6.2	42	QAM 256	19
16	290000000	6.3	42	QAM 256	20
17	298000000	6.4	42	QAM 256	21
18	306000000	6.1	42	QAM 256	22
19	314000000	6.1	42	QAM 256	23
20	322000000	6.2	42	QAM 256	24
21	338000000	6.6	42	QAM 256	26
22	346000000	6.7	42	QAM 256	27
23	354000000	6.7	42	QAM 256	28
24	362000000	6.7	42	QAM 256	29
25	370000000	7	43	QAM 256	30
26	378000000	7.4	43	QAM 256	31
27	386000000	7.6	43	QAM 256	32
28	394000000	7.7	43	QAM 256	33
29	402000000	7.9	43	QAM 256	34
30	410000000	7.8	43	QAM 256	35
31	418000000	7.9	43	QAM 256	36

Downstream bonded channels

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

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

Upstream bonded channels

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

1	46200000	45.3	5120	QAM 16	3
2	39400000	45	5120	QAM 16	4
3	32600000	45	5120	QAM 16	5
4	25800000	44.8	5120	QAM 16	6

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

25-01-2022 18:00:12	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;
25-01-2022 17:59:44	notice	REGISTRATION COMPLETE - Waiting for Operational status
25-01-2022 17:59:38	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;
25-01-2022 17:58:34	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 17:58:32	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 17:58:30	notice	Honoring MDD; IP provisioning mode = IPv4
25-01-2022 17:58:26	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 17:58:17	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 17:58:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 17:58:12	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 17:58:12	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-01-2022 17:58:11	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 17:58:07	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:33:54	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:33:52	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:33:12	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:33:02	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:52	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:51	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:43	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:43	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:43	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:42	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:42	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:39	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:37	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:31	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:28	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:26	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:25	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-01-2022 19:32:15	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

ThinkBroadBand Quality monitor, only set it up today so don't have that long on it.  The outage was when I did a reboot.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/e09fbb91af67a848e6e5349e3a8685a0812f9379-25-01-2022

[Uli]

Sadly engineer wasn't able to help but hes putting in a report to try get the networks team to check out the box to go more indepth to see if they can find the issue.

All cables got checked and they were all tight, he reconnected me in the box to check to see if that was the problem.  Sadly he wasn't able to try a hub swap because they don't carry hub5's and he was a bit unsure what to do/try because they haven't been trained to deal with the hub5 yet.

Showed him the upstream flucuation problem and agreed there was some problem, he called his manager to see if there was anything else he could try and his manager just said "If he wants faster upload he needs to get the better package", which I found funny because if the router on 36mbps can only push 15mbps when it has problems then it won't change even if I was on the 50mbps upload.  Was thinking about upgrading to the faster upload because I'm out of contract but decided to try get this problem fixed first.  Their manager also said apparently 16 QAM for the modulation is "normal" and so is the flucations of 14mbps to 36mbps in the course of 10 minutes despite 380mbps download every time.

He couldnt find any noise ingress in the cab but thinks theres potentially some further down the line somewhere and the networks team would be able to investigate it.

So stuck like this until hopefully the networks team find the issue.  Technician was great did everything he could, his manager uhhh, made him try pass on the bad news lol

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

1	46200000	44.3	5120	QAM 16	3
2	39400000	44.3	5120	QAM 16	4
3	32600000	44.3	5120	QAM 16	5
4	25800000	44	5120	QAM 16	6

[Uli]

Just to show how wild the fluctuations are, partially wished the 5mbps and 9mbps upload happened when the tech was here so he could have told the manager that one.

[Uli]

Couple of these warnings last night which then lead to Pre and Post RS Errors

Network Log

Time Priority Description

05-02-2022 09:22:04	warning	Dynamic Range Window violation
05-02-2022 09:22:04	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;
05-02-2022 06:04:35	warning	Dynamic Range Window violation
05-02-2022 06:04:35	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;
05-02-2022 01:17:44	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;
05-02-2022 01:17:44	warning	Dynamic Range Window violation

Downstream bonded channels

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

1	Locked	42	0	0
2	Locked	41	0	106
3	Locked	41	0	72
4	Locked	41	10	64
5	Locked	41	12	52
6	Locked	42	0	64
7	Locked	42	0	44
8	Locked	42	0	50
9	Locked	42	0	40
10	Locked	41	0	40
11	Locked	42	0	14
12	Locked	42	0	10
13	Locked	42	0	4
14	Locked	41	0	9
15	Locked	42	0	8
16	Locked	42	0	4
17	Locked	42	0	6
18	Locked	41	0	1
19	Locked	41	0	0
20	Locked	42	0	0
21	Locked	41	0	1
22	Locked	42	0	1
23	Locked	42	0	1
24	Locked	42	0	1
25	Locked	42	0	0
26	Locked	42	0	1
27	Locked	42	0	5
28	Locked	42	0	1
29	Locked	42	0	4
30	Locked	42	0	1
31	Locked	42	0	0

Downstream bonded channels

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

1	330000000	6.6	42	QAM 256	25
2	178000000	4.9	41	QAM 256	6
3	186000000	5.2	41	QAM 256	7
4	194000000	5.6	41	QAM 256	8
5	202000000	5.7	41	QAM 256	9
6	210000000	6.1	42	QAM 256	10
7	218000000	6.2	42	QAM 256	11
8	226000000	6.2	42	QAM 256	12
9	234000000	6.3	42	QAM 256	13
10	242000000	6.2	41	QAM 256	14
11	250000000	6.1	42	QAM 256	15
12	258000000	6.1	42	QAM 256	16
13	266000000	6.1	42	QAM 256	17
14	274000000	6.2	41	QAM 256	18
15	282000000	6.4	42	QAM 256	19
16	290000000	6.5	42	QAM 256	20
17	298000000	6.5	42	QAM 256	21
18	306000000	6.3	41	QAM 256	22
19	314000000	6.3	41	QAM 256	23
20	322000000	6.4	42	QAM 256	24
21	338000000	6.8	41	QAM 256	26
22	346000000	6.9	42	QAM 256	27
23	354000000	6.9	42	QAM 256	28
24	362000000	6.9	42	QAM 256	29
25	370000000	7.2	42	QAM 256	30
26	378000000	7.6	42	QAM 256	31
27	386000000	7.9	42	QAM 256	32
28	394000000	8.1	42	QAM 256	33
29	402000000	8.2	42	QAM 256	34
30	410000000	8.2	42	QAM 256	35
31	418000000	8.2	42	QAM 256	36

Upstream doesn't look great either, the power levels were higher but are dropping.  Its like they spike hard during the night, might make a python script and run it on my NAS to pull the router stats so I can plot a graph of everything.

Upstream bonded channels

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

1	46200000	46.3	5120	QAM 16	3
2	39400000	46.8	5120	QAM 16	4
3	32600000	47.5	5120	QAM 16	5
4	25800000	48.8	5120	QAM 16	6

[Uli]

Did a router reboot today, channel id's for upstream have changed and now on QPSK?  Not sure how that compares to what its normally meant to be.

Upstream bonded channels

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

1	60300000	45.5	5120	QPSK	1
2	53700000	46	5120	QPSK	2
3	46200000	46.5	5120	QPSK	3
4	39400000	47	5120	QPSK	4

[Uli]

Router rebooted last night since I got upgraded to 1gbps.  Upstreams are still on IDs 1/2/3/4 and are currently on QAM 64 and haven't changed, will continue to monitor it but I feel like whatever was done the other day to change what channels were used has fixed it, fingers crossed.

[Zak_M]

Keep us updated on how things go Uli.

Kind regards,

Zak_M