Green Arrows flashing - Really slow internet speeds

[themuel1]

(M600 Service) For the past three weeks, we've had really slow speeds (6.4 MBPS - 22 MBPS if we're lucky, upload 1 MBPS - 10 MBPS) and the green arrows on the router have been flashing continuously the entire time.

The router has been reset a number of times, we've spoken to customer services and they advised there was an issue in our area, although the service checker and the service checker phone line haven't at any point displayed/advised of faults in the local area. We were told it would be a 7-day fix. That was 7 days ago and still no fix or improvement. This all started around the same time Openreach turned up (no notice) and dug the road up to install cables for BT. Customer Services didn't think that was relevant, just thought I'd mention it in case it could be. We've never got anywhere near the speeds we should get, even wired, but these current speeds are ridiculous. 

Router Logs - 

Downstream bonded channels

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

1

418750000

-2.4

40

256 qam

36

Downstream bonded channels

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

1

Locked

40.9

18

0

Upstream bonded channels

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

1

53700000

51

5120

64 qam

1

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1

ATDMA

0

0

0

0

Primary Downstream Service Flow

SFID	145508
Max Traffic Rate	690000278
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	145507
Max Traffic Rate	44000278
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	42600
Scheduling Type	BestEffort

Network Log

Time Priority Description

08/10/2021 17:07:39	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:26	Warning!	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:26	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/10/2021 00:46:53	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/10/2021 19:48:49	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/10/2021 09:03:48	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:25	Warning!	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:25	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/10/2021 14:15:18	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/10/2021 14:12:42	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:27	Warning!	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:27	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:28	Warning!	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:28	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/09/2021 11:46:4	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:27	Warning!	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:27	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/09/2021 18:13:51	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:27	Warning!	MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:27	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[jbrennand · Accepted solution]

Thats not a full data set - or is it ? Should be data for 24 down channels and 4 up channels - if they arent there then you need to pinhole reset as below. If they are there - post the full data set
________________________-
Note that a pinhole reset on a Hub3/4 can be a bit problematic - so do it (again) EXACTLY this way (not as the VM website says!).

Firstly, make sure the Hub's sticker/card with the two passwords on it is still there and legible or you will be stuffed ! If its not – DON’T DO IT !

With the Hub switched "on", disconnect any ethernet connections (leave the co-ax connected) and then push in the “reset pin” with the end of a paperclip/thin nail/SIM tray “tool” or similar (bigger items like ball point pen ends may not press it in far enough) until you feel it at the “stop point” and hold it there firmly for a "timed" minimum of 60 seconds do NOT manually restart the Hub at any time. Leave it 10' or so to stabilise and then your passwords/passphrase for both the Hub settings and the Wifi networks will revert to the two printed on the Hub sticker on its base/side/card. Make sure you use the wifi one for devices connecting to the wifi and the settings/admin one to access the Hub

See if that sorts it.

[themuel1]

Thanks John - That was the entire data set prior to your reply. We'd tried pinhole resetting last week (with the customer service rep on the phone) and saw no change when it rebooted, with the green lights still flashing. After this reset, we seem to be back with some decent speed - 90 MBPS wireless. Do these logs look OK now? 

Downstream bonded channels

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

1	138750000	-0.7	40	256 qam	1
2	146750000	-0.9	40	256 qam	2
3	154750000	-0.7	40	256 qam	3
4	162750000	-0.7	40	256 qam	4
5	170750000	-0.5	40	256 qam	5
6	178750000	-0.5	40	256 qam	6
7	186750000	-0.4	40	256 qam	7
8	194750000	-0.5	40	256 qam	8
9	202750000	-0.7	40	256 qam	9
10	210750000	-1	40	256 qam	10
11	218750000	-1.4	40	256 qam	11
12	226750000	-1.5	40	256 qam	12
13	234750000	-1	40	256 qam	13
14	242750000	-1	40	256 qam	14
15	250750000	-1.2	40	256 qam	15
16	258750000	-1	40	256 qam	16
17	266750000	-0.5	40	256 qam	17
18	274750000	0.4	40	256 qam	18
19	282750000	0.5	40	256 qam	19
20	290750000	0.7	40	256 qam	20
21	298750000	0.5	40	256 qam	21
22	306750000	0.7	40	256 qam	22
23	314750000	0.5	40	256 qam	23
24	322750000	0.5	40	256 qam	24

Downstream bonded channels

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

1	Locked	40.3	55	0
2	Locked	40.3	53	0
3	Locked	40.3	78	0
4	Locked	40.3	112	0
5	Locked	40.3	136	0
6	Locked	40.3	133	0
7	Locked	40.3	98	0
8	Locked	40.9	100	0
9	Locked	40.9	131	0
10	Locked	40.3	129	0
11	Locked	40.9	108	0
12	Locked	40.9	53	0
13	Locked	40.3	23	0
14	Locked	40.9	45	0
15	Locked	40.3	70	0
16	Locked	40.3	76	0
17	Locked	40.3	80	0
18	Locked	40.9	105	0
19	Locked	40.9	114	0
20	Locked	40.3	118	0
21	Locked	40.3	114	0
22	Locked	40.3	109	0
23	Locked	40.3	109	0
24	Locked	40.3	128	0

Upstream bonded channels

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

1	39400000	50.3	5120	64 qam	3
2	32600000	50	5120	64 qam	4
3	46200000	50.3	5120	64 qam	2
4	53700000	50.8	5120	64 qam	1

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[jbrennand]

Ok but not perfect. If problems start appearing I would say its because you up power levels are at the top of the recommended range of between 35 dBmV and 51 dBmV.

Keep your eye on it