Could I get a quick diagnosis based on these logs? Lost MDD Timeout

[gvh1234]

Hi there

I've woken up to no connection from my Hub3 here in Southampton.
I've rebooted, then done a Reset button. Still no good.

I've had this Hub and M200 for over a year and have woken up about 5 times to no connection. A reboot has always solved it but this time I'm dead in the water.
Hopefully I've pasted everything an expert would need.
Many Many thanks for any help

Gareth

Lost MDD Timeout

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)	330750000	Locked
Ranged Upstream Channel (Hz)	39400000	Locked
Provisioning State	Online

Downstream bonded channels

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

1	330750000	2.2	35	256 qam	25
2	218750000	4.1	33	256 qam	11
3	226750000	4	33	256 qam	0
4	234750000	3.9	34	256 qam	13
5	242750000	3.5	33	256 qam	14
6	250750000	3.2	32	256 qam	15
7	258750000	3	34	256 qam	16
8	266750000	3	32	256 qam	17
9	274750000	2.9	32	256 qam	18
10	282750000	3	33	256 qam	19
11	290750000	3	32	256 qam	20
12	298750000	2.7	32	256 qam	21
13	306750000	2	33	256 qam	22
14	314750000	1.7	32	256 qam	23
15	322750000	2	33	256 qam	24
16	370750000	2.4	34	256 qam	26
17	378750000	2.4	33	256 qam	27
18	386750000	2.5	32	256 qam	28
19	394750000	2.9	32	256 qam	29
20	402750000	2.9	33	256 qam	30
21	410750000	2.9	32	256 qam	31
22	418750000	2.4	32	256 qam	0
23	426750000	2.2	33	256 qam	33
24	434750000	2	34	256 qam	34

Downstream bonded channels

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

1	Locked	35	83841750	2321424
2	Locked	33.3	798533	84223695
3	Locked	33.4	554858	84468583
4	Locked	34.4	76176508	8693359
5	Locked	33	960783	84071075
6	Locked	32.9	463389	84569609
7	Locked	34.3	71137876	13793705
8	Locked	32.6	1966330	83067433
9	Locked	32.5	204979	84824489
10	Locked	33.9	68991531	14489211
11	Locked	32.5	270989	84765597
12	Locked	32.6	193483	84844133
13	Locked	33.8	65049654	18592516
14	Locked	32.6	230273	84808773
15	Locked	33.8	71864604	11066947
16	Locked	34.3	24533893	3144109
17	Locked	33.8	69829106	14713612
18	Locked	32.6	235706	84789421
19	Locked	32.6	178192	84863876
20	Locked	33.8	64988139	19124272
21	Locked	32.6	264288	84768392
22	Locked	32.5	156294	84888440
23	Locked	33.8	55245460	21891870
24	Locked	34.3	74978384	8397521

Upstream bonded channels

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

1	39400000	41	5120	64 qam	4
2	53700000	42	5120	64 qam	2
3	46200000	41.5	5120	64 qam	3
4	32600000	41.3	5120	64 qam	5

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	2	0
4	ATDMA	0	0	0	0

[gvh1234]

Primary Downstream Service Flow

SFID	43218
Max Traffic Rate	230000061
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	43217
Max Traffic Rate	22000061
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	42600
Scheduling Type	BestEffort

[mpmc]

I'm no expert but holy RS errors batman. RS errors are a normal thing to see but i'm pretty sure they shouldn't be that high, yikes!

[Z92]

Can you post the network log as well as it seems that something is seriously wrong with your connection if that's just been rebooted.

Check all connections inside and out are tight also.

[jpeg1]

That's all coax connections including those to TV box/es.

[gvh1234]

The only reason I haven't replied is that a few hours ago my account page said there was a known fault in the area.
Now I await news.

Meanwhile the router is in limbo with a green light on and it's web site says it's Updating, not sure I believe it though. So I can't even get you the logging!

Thanks for the replies

[-tony-]

as said above the rs errors are off the scale but to make sure they are not historical reboot the hub or zero them [possible on some hubs] and see if the rise again - post the new levels in a few hours

[jem101]

Forget about the errors, they are just symptomatic of the real problem which is the S/N ratio is too low across the downstream channels for a reliable connection. And the reason for that is a bad cable joint, damaged cable, failing amp in the cabinet or a more general area fault which seems to be in play now. Unfortunately other than check the cabling, there's very little you can do until the fault is cleared - then if you still have issues, VM can take it from there.

[gvh1234]

Network Log

Time Priority Description

23/08/2021 11:55:9	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:55:6	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:55:6	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:54:34	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:54:31	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:53:29	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:53:26	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:51:49	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:51:47	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:51:27	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:51:22	Warning!	LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:49:1	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:49:1	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:48:53	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:48:51	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:45:31	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:45:27	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:45:3	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:45:0	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2021 11:44:10	Warning!	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[gvh1234]

...aaand we're back