Lots of pre and post errors, dropouts etc, T3 timeouts, too many errors to put in the title

[GoNz0]

Can one of the staff please arrange to get the network checked and an engineer out, I've no idea if this is another cable from box to house error as it's been a few since you last ran new to the box but I get the feeling it's in the box up the road or from there back.

Power levels are ok but we are facing drop outs throughout the day, I'm having to reboot the hub 2-3 times a week to get things stable again.

Various logged errors

SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-

DHCP WARNING - Non-critical field invalid in response ;CM-MAC=

TLV-11 - unrecognized OID;CM-MAC=

16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC

Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-

No Ranging Response received - T3 time-out;CM-

SYNC Timing Synchronization failure - Loss of Sync

Most of the above repeat over and over looking at the logs. It's no longer stable and causing issues working from home.

Thanks.

[Tudor]

Please post full set of stats, details follow:

How to get stats from a VM hub (no need to logon to the hub)

Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode

• Click on the “> Check router status” button
• Click on the “Downstream” tab, copy the text and paste into your reply, do not take a screen shot
• Click on the “Upstream” tab, copy the text and paste into your reply
• Click on the “Networking” tab, copy the text and paste into your reply.
• Do NOT post photos or screen shots they will be rejected as they contain MAC addresses. The board software will automatically change MAC addresses to **:** if done as above.

[Sephiroth]

The reason that forum members ask for the stats, despite your calling on VM staff to assist, is that we members can provide insights for you that will never be disclosed by the VM bods.  There are many instances on here where our diagnostics have proved to be correct notwithstanding the “nothing wrong” words from VM staff on the phone or in the forum.

The VM bods would look at current status of your hub but would be unlikely to catch the stats during an event.  So do please capture your stats when things go wrong.

Keep us posted.

[Topgun]

Apologies if I'm hijacking this thread but I seem to be having issues with small drop outs regularly. Could someone please check this  for me please? I have 1 gig through my Hub 4, which is in modem mode connected to my Synology router.

Thanks.

3.0 Downstream channels

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

25	330750000	4.1	40.9	QAM256	25
1	138750000	6.6	39	QAM256	1
2	146750000	6.4	40.4	QAM256	2
3	154750000	6.3	40.4	QAM256	3
4	162750000	6.3	40.9	QAM256	4
5	170750000	6.2	40.9	QAM256	5
6	178750000	6.2	40.4	QAM256	6
7	186750000	6.1	40.9	QAM256	7
8	194750000	5.8	40.4	QAM256	8
9	202750000	5.7	40.4	QAM256	9
10	210750000	5.6	40.9	QAM256	10
11	218750000	5.6	40.4	QAM256	11
12	226750000	5.4	40.4	QAM256	12
13	234750000	5.1	40.4	QAM256	13
14	242750000	5	40.4	QAM256	14
15	250750000	5	40.4	QAM256	15
16	258750000	5	40.4	QAM256	16
17	266750000	4.9	40.4	QAM256	17
18	274750000	5.2	40.4	QAM256	18
19	282750000	5.4	40.4	QAM256	19
20	290750000	5.4	40.9	QAM256	20
21	298750000	5.1	40.4	QAM256	21
22	306750000	4.7	40.4	QAM256	22
23	314750000	4.5	40.4	QAM256	23
24	322750000	4.3	40.4	QAM256	24
26	338750000	4.1	40.4	QAM256	26
27	346750000	4.2	40.4	QAM256	27
28	354750000	4.1	40.4	QAM256	28
29	362750000	4	40.4	QAM256	29
30	370750000	3.9	40.4	QAM256	30
31	378750000	3.7	40.4	QAM256	31
32	386750000	3.8	40.4	QAM256	32

3.0 Downstream channels

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

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

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

94

4K

1800

QAM4096

424

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

42

4.4

4088232167

0

[Topgun]

Refresh data

3.0 Upstream channels

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

1	30100000	40.3	5120 KSym/sec	QAM64	4
2	23600000	39.8	5120 KSym/sec	QAM64	5
3	36600000	40.8	5120 KSym/sec	QAM64	3
4	43100000	41.3	5120 KSym/sec	QAM64	2
5	49600000	41.8	5120 KSym/sec	QAM64	1

3.0 Upstream 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
5	ATDMA	0	0	0	0

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

6

10.0

45.0

2K

QAM128

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts

6

OFDMA

200

53.9

0

0

[Topgun]

Refresh data

Network Log

Time Priority Description

Mon 16/09/2024 05:55:24	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 16/09/2024 02:24:21	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 15/09/2024 12:00:51	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 15/09/2024 12:00:51	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 15/09/2024 09:46:01	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/09/2024 03:48:46	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 13/09/2024 16:15:24	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 13/09/2024 16:15:24	5	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;
Fri 13/09/2024 16:15:08	6	CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 13/09/2024 16:15:08	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 13/09/2024 15:01:51	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 13/09/2024 15:01:51	5	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;
Fri 13/09/2024 15:01:34	6	CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 13/09/2024 15:01:34	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 10/09/2024 12:45:31	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 10/09/2024 07:45:49	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 10/09/2024 07:45:49	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 07/09/2024 01:14:46	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 06/09/2024 19:45:48	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 06/09/2024 19:45:47	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 04/09/2024 08:06:47	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 03/09/2024 07:45:47	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 03/09/2024 07:45:47	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 02/09/2024 22:42:31	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 02/09/2024 22:32:01	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 31/08/2024 02:13:16	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 30/08/2024 19:45:47	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 30/08/2024 19:45:47	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 30/08/2024 11:11:44	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 29/08/2024 17:01:53	6	US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 29/08/2024 01:47:26	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 27/08/2024 07:45:47	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 27/08/2024 07:45:46	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 24/08/2024 04:51:01	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 24/08/2024 03:16:08	6	US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 23/08/2024 19:45:46	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 23/08/2024 19:45:46	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 20/08/2024 15:41:01	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 20/08/2024 07:45:46	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 20/08/2024 07:45:46	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 17/08/2024 05:49:30	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/08/2024 19:45:46	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/08/2024 19:45:46	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/08/2024 20:26:37	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 13/08/2024 07:45:46	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 13/08/2024 07:45:45	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 12/08/2024 14:05:44	6	CM-STATUS message sent. Event Type Code: 5; Chan ID: 3; 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;
Sat 10/08/2024 05:08:48	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 09/08/2024 19:45:45	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 09/08/2024 19:45:45	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Sephiroth]

There are no clues in the stats - they are perfect from a nominal point of view.

So, what are talking about?  Wired or WiFi drop-outs?  What does a drop-out look like in terms of experience? Precisely what can't you do and how long does it last?

[Topgun]

Thanks for the rapid reply. It's tricky because it's lots of little different things. Spotify will randomly cut out on my wi-fi speaker for a couple of minutes, my house alarm, which we can set and unset via an app, will occasionally not pick up the wi-fi. The printer will drop out of the wi-fi every so often. It just seems to me that the wi-fi is dropping out every so often, albeit for short periods of time.

[Sephiroth]

In the absence of any report about a wired connection, we can assume for now that there is a WiFi issue and that your circuit is behaving correctly.

Do you have "Intelligent WiFi" or "Smart WiFi" or similar setting ON?  If so, does the problem disappear if you disable this useless setting (which causes glitches when the Hub switches to a different channel)?  Also when you turn this OFF (pls do that anyway) set your 2.4GHz channel fixed to any of 1, 6 or 11 which, though contended with neighbours, are not overlapping channels.

We could also look at how far away are those devices from the Hub?  Could the WiFi signal be if-ish which would trigger automatic channel changes?  Are these 2.4GHz or 5GHz devices? 

Also, do make sure that the CONNECT app is not running on any of your mobile devices - it takes control of your WiFi settings and only gives you grief.

Keep us posted.

[Topgun]

My set up is as follows, I have 1gig through my Hub 4, that is in modem mode and feeds my Synology RT2600AC router. Because my hub and router are in a far corner of the house, I have had an ethernet cable run to the opposite far corner of the house, where I have a Synology MR2200AC in a mesh set up with my main router.

This has served me very well for the last few years, except for recently when I've had the issues described. I haven't changed any settings at all, as far as I'm aware. When I do a speed check on my iPad at the far corner of the house away from the main router, I get a solid 550-600 download speed.