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 errorsSYNC 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-MACUnicast 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.

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 modeClick on the “> Check router status” buttonClick on the “Downstream” tab, copy the text and paste into your reply, do not take a screen shotClick on the “Upstream” tab, copy the text and paste into your replyClick 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.

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.

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 channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 253307500004.140.9QAM2562511387500006.639QAM256121467500006.440.4QAM256231547500006.340.4QAM256341627500006.340.9QAM256451707500006.240.9QAM256561787500006.240.4QAM256671867500006.140.9QAM256781947500005.840.4QAM256892027500005.740.4QAM2569102107500005.640.9QAM25610112187500005.640.4QAM25611122267500005.440.4QAM25612132347500005.140.4QAM2561314242750000540.4QAM2561415250750000540.4QAM2561516258750000540.4QAM25616172667500004.940.4QAM25617182747500005.240.4QAM25618192827500005.440.4QAM25619202907500005.440.9QAM25620212987500005.140.4QAM25621223067500004.740.4QAM25622233147500004.540.4QAM25623243227500004.340.4QAM25624263387500004.140.4QAM25626273467500004.240.4QAM25627283547500004.140.4QAM2562829362750000440.4QAM25629303707500003.940.4QAM25630313787500003.740.4QAM25631323867500003.840.4QAM256323.0 Downstream channelsChannel Lock Status RxMER (dB) Pre RS Errors Post RS Errors 25Locked40.946209001Locked38.983261002Locked40.366287003Locked40.366287004Locked40.946209005Locked40.946209006Locked40.366287007Locked40.946209008Locked40.366287009Locked40.3662870010Locked40.9462090011Locked40.3662870012Locked40.3662870013Locked40.3662870014Locked40.3662870015Locked40.3662870016Locked40.3662870017Locked40.3662870018Locked40.3662870019Locked40.3662870020Locked40.9462090021Locked40.3662870022Locked40.3662870023Locked40.3662870024Locked40.3662870026Locked40.3662870027Locked40.3662870028Locked40.3662870029Locked40.3662870030Locked40.3662870031Locked40.3662870032Locked40.366287003.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz) 159944K1800QAM40964243.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile) 159Locked424.440882321670

Refresh data3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 13010000040.35120 KSym/secQAM64422360000039.85120 KSym/secQAM64533660000040.85120 KSym/secQAM64344310000041.35120 KSym/secQAM64254960000041.85120 KSym/secQAM6413.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1ATDMA00002ATDMA00003ATDMA00004ATDMA00005ATDMA00003.1 Upstream channelsChannel Channel Width (MHz) Power (dBmV) FFT Type Modulation 610.045.02KQAM1283.1 Upstream channelsChannel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts 6OFDMA20053.900

Refresh dataNetwork LogTime Priority Description Mon 16/09/202405:55:243No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 16/09/202402:24:216US 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/202412:00:516DHCP 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/202412:00:514DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun 15/09/202409:46:016US 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/202403:48:463No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 13/09/202416:15:246US 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/202416:15:245DBC-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/202416:15:086CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 13/09/202416:15:085MIMO 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/202415:01:516US 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/202415:01:515DBC-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/202415:01:346CMSTATUS:US_Diplexer_Mode_Change_Ignore: (TLV-9) , (5-85) ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 13/09/202415:01:345MIMO 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/202412:45:313No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 10/09/202407:45:496DHCP 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/202407:45:494DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 07/09/202401:14:463No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 06/09/202419:45:486DHCP 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/202419:45:474DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed 04/09/202408:06:473No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 03/09/202407:45:476DHCP 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/202407:45:474DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 02/09/202422:42:313No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 02/09/202422:32:016US 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/202402:13:163No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 30/08/202419:45:476DHCP 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/202419:45:474DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 30/08/202411:11:443No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 29/08/202417:01:536US 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/202401:47:263No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 27/08/202407:45:476DHCP 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/202407:45:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 24/08/202404:51:013No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 24/08/202403:16:086US 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/202419:45:466DHCP 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/202419:45:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 20/08/202415:41:013No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 20/08/202407:45:466DHCP 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/202407:45:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat 17/08/202405:49:303No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 16/08/202419:45:466DHCP 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/202419:45:464DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu 15/08/202420:26:373No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue 13/08/202407:45:466DHCP 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/202407:45:454DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon 12/08/202414:05:446CM-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/202405:08:483No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri 09/08/202419:45:456DHCP 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/202419:45:454DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

23 Replies

Tudor

Very Insightful Person

8 months ago

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.

Topgun

Dialled in

8 months ago

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
1	Locked	38.983261
2	Locked	40.366287
3	Locked	40.366287
4	Locked	40.946209
5	Locked	40.946209
6	Locked	40.366287
7	Locked	40.946209
8	Locked	40.366287
9	Locked	40.366287
10	Locked	40.946209
11	Locked	40.366287
12	Locked	40.366287
13	Locked	40.366287
14	Locked	40.366287
15	Locked	40.366287
16	Locked	40.366287
17	Locked	40.366287
18	Locked	40.366287
19	Locked	40.366287
20	Locked	40.946209
21	Locked	40.366287
22	Locked	40.366287
23	Locked	40.366287
24	Locked	40.366287
26	Locked	40.366287
27	Locked	40.366287
28	Locked	40.366287
29	Locked	40.366287
30	Locked	40.366287
31	Locked	40.366287
32	Locked	40.366287

3.1 Downstream channels

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

159

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

4.4

4088232167

Topgun
Dialled in
8 months ago
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

Sephiroth
Alessandro Volta
8 months ago
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.
Sephiroth
Alessandro Volta
8 months ago
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
  Dialled in
  8 months ago
  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.
  - Topgun
    Dialled in
    8 months ago
    Would the channel change issue be relevant, as I'm in modem mode?
Sephiroth
Alessandro Volta
8 months ago
No - the channel change issue is not relevant in modem mode - on the assumption that your router doesn't have comparable auto-channel-switch settings.
So that brings us back to the 2.4GHz question. Given that we're talking about a remote part of your house, served with an Ethernet backhaul to your main router, neighbour's 2.4GHz interference is less likely.
Are you in a position to do stuff wired in the remote location and report?
- Topgun
  Dialled in
  8 months ago
  So, coming off the Ethernet cable to the back of the house, is a switch, from which I have my TV, 360 box and X box all wired to. I have no issues at all with any of those. The download spread to the X box is very quick and solid.
Sephiroth
Alessandro Volta
8 months ago
Do the drop-outs occur when your switch is handling downloads? Remember, the WiFi is also being backhauled down the cable.
Otherwise, we're down to WiFi behaviour. What is the WiFI being used for when the glitches occur?
- Topgun
  Dialled in
  8 months ago
  The switch seems to work fine. It's steady when even doing large downloads to the Xbox. The dropouts all seem to be short and all do do with apps running, Spotify, my house alarm, the printer, Hive occasionally, all sorts of things like that. They'll just not respond for a minute and then burst back into life. TBH it's not the end of the world, just slightly irritating on occasion. I feel my 1 gig connection should be more than enough for everything in the house to run easily, there's only myself and my wife. Although she works from home and is constantly on Zoom, I wouldn't have thought that just the two of us would be maxing out our connection!
Sephiroth
Alessandro Volta
8 months ago
You're right. You aren't maxing your connection out, particularly when not doing downloads. If you want this bottoming out, you'll need to experiment and report. For example, when WiFi drops for a minute or so, get onto a wired device at the remote end and see if that's dropped as well. Then do the same with a wired device at the Hub end. Process of elimination.
I know I wouldn't want this happening during a video call.

GoNz0

Dialled in

8 months ago

3.0 Downstream channels

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

1	331000000	1.5	40	QAM 256	25
2	139000000	0.5	39	QAM 256	1
3	147000000	0.4	39	QAM 256	2
4	155000000	0.3	39	QAM 256	3
5	163000000	0.2	39	QAM 256	4
6	171000000	0.2	39	QAM 256	5
7	179000000	0.1	39	QAM 256	6
8	259000000	0.3	38	QAM 256	16
9	267000000	0.1	38	QAM 256	17
10	275000000	0.2	37	QAM 256	18
11	283000000	0.6	39	QAM 256	19
12	291000000	0.9	39	QAM 256	20
13	299000000	1.1	40	QAM 256	21
14	307000000	1.3	40	QAM 256	22
15	315000000	1.4	40	QAM 256	23
16	323000000	1.5	40	QAM 256	24
17	339000000	1.7	40	QAM 256	26
18	347000000	1.6	40	QAM 256	27
19	355000000	1.5	40	QAM 256	28
20	363000000	1.4	40	QAM 256	29
21	371000000	1	40	QAM 256	30
22	379000000	0.6	40	QAM 256	31
23	387000000	0.3	40	QAM 256	32
24	395000000	0.3	40	QAM 256	33
25	403000000	0.4	40	QAM 256	34
26	411000000	0.5	40	QAM 256	35
27	419000000	0.5	40	QAM 256	36
28	523000000	0.5	40	QAM 256	37
29	531000000	0.4	40	QAM 256	38
30	539000000	0.4	40	QAM 256	39
31	547000000	0.4	40	QAM 256	40

3.0 Downstream channels

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

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

3.1 Downstream channels

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

1840

QAM 4096

1108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

Locked

-2.1

1469326374

GoNz0
Dialled in
8 months ago

Router status
Status
Downstream
Upstream
Configuration
Network Log
Refresh data
3.0 Upstream channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
0 49600000 51 5120 QAM 64 1
1 43100000 51.3 5120 QAM 64 2
2 36600000 51.5 5120 QAM 64 3
3 30100000 52 5120 QAM 64 4
4 23600000 53 5120 QAM 64 5
3.0 Upstream channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0 ATDMA 0 0 0 0
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0
3.1 Upstream channels
Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
6 10.4 46.5 2K QAM 256
3.1 Upstream channels
Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6 OFDMA 208 74000000 0 0
- Sephiroth
  Alessandro Volta
  8 months ago
  @G0Nz0 - as you might have understood, your upstream is struggling. The stats managed to capture the condition where the VM end cannot read what your Hub is sending in response to the keep-alive requests that it sends to the Hub. When that happens, the VM end commands a step up in upstream power from your Hub in the hope that it can then read the data. When it reached 51dBmv, the Hub is maxed out for upstream power and the VM end commands a reset - a T4 event (not shown in the stats). So presumably, the VM end can read what the Hub sends when it's at full power.
  I'll bet that all your dropouts occur when the upstream power is maxed and a T4 reset occurs. This will definitely need a tech and you should hope that the tech can see this issue - your earlier stats showed nothing wrong.
  - GoNz0
    Dialled in
    8 months ago
    Thanks for the reply, oh well, here we go again. It's been a couple of years since the last load of issues. I thought I was doing well.

GoNz0

Dialled in

8 months ago

Router status

Refresh data

Network Log

Time Priority Description

18-09-2024 00:49:35	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 00:47:52	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 00:42:49	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 00:31:09	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
18-09-2024 00:26:06	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 23:26:30	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 23:21:27	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 10:05:28	notice	GUI Login Status - Login Success from LAN interface
17-09-2024 10:05:09	notice	GUI Login Status - Login Fail from LAN interface
17-09-2024 10:04:19	notice	REGISTRATION COMPLETE - Waiting for Operational status
17-09-2024 10:04:15	notice	US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 10:04:09	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;
17-09-2024 10:04:06	notice	TLV-11 - unrecognized OID;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 10:04:03	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 10:04:01	notice	Honoring MDD; IP provisioning mode = IPv4
17-09-2024 10:03:41	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
17-09-2024 10:03:38	critical	Cable Modem Reboot because of - Reboot UI
03-09-2024 20:08:50	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
03-09-2024 20:08:48	critical	Cable Modem Reboot because of - Reboot UI
03-09-2024 16:15:05	critical	16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
03-09-2024 16:15:05	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
03-09-2024 16:13:57	critical	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
02-09-2024 06:37:09	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;
30-08-2024 18:04:29	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:14	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;
28-08-2024 12:11:14	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:13	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:11	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:11	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:09	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:09	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:06	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:05	critical	No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;
28-08-2024 12:11:03	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.1;

Log out Language

Home
Connected devices
Modem mode
Advanced settings
Admin

GoNz0
Dialled in
8 months ago
Thanks, hope that's everything you need for now, appreciate the help.
Needless to say, since rebooting yesterday it's now had an issue as the lack of uncorrectable errors shows.

Forum Discussion

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

23 Replies

3.0 Downstream channels

3.0 Downstream channels

3.1 Downstream channels

3.1 Downstream channels

3.0 Upstream channels

3.0 Upstream channels

3.1 Upstream channels

3.1 Upstream channels

Router status

Router status

Related Content

Dropouts

Virgin Media SH3 Daily dropouts- RCS Partial Service/SYNC Timing Errors

Intermittent Broadband dropouts and latency

Frequent connectivity dropout using GlobalProtect VPN

CS2217 error

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

0	49600000	51	5120	QAM 64	1
1	43100000	51.3	5120	QAM 64	2
2	36600000	51.5	5120	QAM 64	3
3	30100000	52	5120	QAM 64	4
4	23600000	53	5120	QAM 64	5

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

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