M200 Hub3 Speed Test erratic

[crimsom]

Fast.com Speed Test results are erratic. Download jumps around between about 30 Mbps to 150 Mbps.

As a returning Virgin Broadband customer the M200 Hub3 kit was a self install to the legacy equipment and line. The scheduled install technician did not visit on 23rd November 2021.

When will the download speed settle down to give the advertised M200 download speeds?

Kind regards. 

[Andrew-G]

It won't "settle down" because VM use different technology to Openreach whose tech does have a bedding in period.

If the erratic speeds are down to a known area fault, things will miraculously improve with no obvious intervention, because the fault will be remote from you and fixed without a visit.

A somewhat more likely case is that your cable has been moved to a less suitable tap in the cabinet, and the power levels are out, or there's a faulty connector somewhere letting noise in.  You can phone it in (and find out how much VM customer service has changed whilst you've been away), or if you'd rather use the forum, then follow the note below to post the hub's status details.

Connect to the hub by clicking on this link http://192.168.0.1/  That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.  Then we can check for any obvious problems with power, noise or error counts.

[crimsom]

Hi @Andrew-G, thanks for the clarification. I was expecting the scheduled install technician visit to have checked my legacy green cabinet and line. The Hub3 Router status - Network Log has some interesting information. 

Time	Priority	Description
05/12/2021 07:09:14	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/12/2021 06:16:6	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/12/2021 13:51:0	Warning!	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/12/2021 13:51:0	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/12/2021 09:37:45	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/12/2021 09:37:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/12/2021 02:14:56	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/11/2021 21:37:45	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/11/2021 21:37:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2021 20:38:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2021 09:37:45	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/11/2021 09:37:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/11/2021 00:38:13	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 21:37:45	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 21:37:45	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 20:41:41	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 20:41:41	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/11/2021 20:09:0	notice	SW download Successful - Via Config file
23/11/2021 20:07:1	notice	SW Download INIT - Via Config file
01/01/1970 00:02:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[crimsom]

Downstream bonded channels

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

1	723000000	6.1	38	256 qam	40
2	539000000	4.1	37	256 qam	17
3	547000000	4.5	37	256 qam	18
4	555000000	5.1	37	256 qam	19
5	563000000	5.5	37	256 qam	20
6	571000000	5.5	38	256 qam	21
7	579000000	5.4	37	256 qam	22
8	587000000	5.3	38	256 qam	23
9	595000000	4.6	37	256 qam	24
10	603000000	4.5	37	256 qam	25
11	611000000	5.1	38	256 qam	26
12	619000000	5.5	38	256 qam	27
13	627000000	5.5	38	256 qam	28
14	635000000	5.1	37	256 qam	29
15	643000000	5	37	256 qam	30
16	651000000	5.4	38	256 qam	31
17	659000000	5.4	37	256 qam	32
18	667000000	6	38	256 qam	33
19	675000000	6.8	38	256 qam	34
20	683000000	6.6	38	256 qam	35
21	691000000	6.4	38	256 qam	36
22	699000000	5.8	38	256 qam	37
23	707000000	6	38	256 qam	38
24	715000000	6	38	256 qam	39

Downstream bonded channels

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

1	Locked	38.6	84	0
2	Locked	37.6	20	0
3	Locked	37.6	30	0
4	Locked	37.6	21	0
5	Locked	37.6	33	0
6	Locked	38.6	34	0
7	Locked	37.6	29	0
8	Locked	38.6	27	0
9	Locked	37.6	35	0
10	Locked	37.6	39	0
11	Locked	38.9	35	0
12	Locked	38.6	43	0
13	Locked	38.6	52	0
14	Locked	37.6	57	0
15	Locked	37.6	61	0
16	Locked	38.6	56	0
17	Locked	37.6	66	0
18	Locked	38.6	58	0
19	Locked	38.6	70	0
20	Locked	38.6	67	0
21	Locked	38.6	69	0
22	Locked	38.6	78	0
23	Locked	38.6	82	0
24	Locked	38.6	80	0

[crimsom]

Upstream bonded channels

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

1	53699971	45.8	5120	64 qam	10
2	39399930	45.8	5120	64 qam	12
3	46199927	45.8	5120	64 qam	11
4	60299988	45.8	5120	64 qam	9

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

[crimsom]

User Observations:

Checked the connector on the back of the Hub3, and internal wall to ensure super tight. Using legacy cable, not fibre cable that came in box, does this matter?. 

The Hub3 light is not pure white, slight orange hue.  Hub3 has been switched off, wait, switched back on. 

There are no reported local faults. Checking for in house faults alternates, between check device and check account, but never completes. Using WiFi or ethernet makes no difference. Evidently the WiFi signal is weak, test says move laptop towards Hub3, but signal continues to be weak. 

Is there anything else that user can report?

[Adduxi]

---

@crimsom wrote:

User Observations:

Checked the connector on the back of the Hub3, and internal wall to ensure super tight. Using legacy cable, not fibre cable that came in box, does this matter?. 

---

All connections internal to the Hubs are co-ax not fibre so the cable will not matter.

As for you wifi connections try splitting the SSID

• Access your Hub by navigating to 192.168.0.1
• Login with the default login info (on base of Hub) unless you've already updated it.
• Go to Advanced Settings > Wireless > Security
• Under Wireless Frequency 2.4GHz change the Wifi Network Name (SSID), suggest append _2 to the end.
• Repeat for the Wireless Frequency 5GHz, suggest append _5 to the end and click on Apply changes
• Try to avoid spaces and periods in the SSID names as they can cause issues with certain devices.

Also VM do not guarantee any wifi speeds, only speeds to the Hub.  Speed tests have to be done wired directly to the Hub, with a known good Cat 6a cable and a gigabit capable devices.

Consider setting up a BQM monitor here for recording your incoming circuit.   www.thinkbroadband.com/ping

[crimsom]

Hi Adduxi, thank you for clarification. M200 has only been live for a just over a week, and I am considering rejecting the order. Thank you for saying how to separate SSID into 2.4 and 5.0 GHz within Hub3 Settings. The 150Mbps download speed is now more likely to be SSID 5.0 GHz, but the fast M200 speeds remain elusive. Kind regards. 

[Andrew-G]

Can't say if it is the cause of poor speeds, but your downstream data shows a downstream power level of 4.1 dBmV at 539MHz, rising to 6.8 dBmV at 675 MHz.  That shows the amplifier in the street cabinet is not very well setup, and there comes a point where incorrect "slope" does affect speed and reliability.

No point ringing that in - the script elves wouldn't have a clue what you were on about, and would insist all was good.  Hopefully the forum staff will pick this up and get a technician assigned, if they can't see anything wrong can I ask that they escalate to the AFM or Networks for a second opinion?

[crimsom]

Hi @Andrew-G, thanks for keeping in touch. Agree with your review and add the following supporting text. 

Hub3 Router status - Network Log says SYNC Timing Synchronization failure - Loss of Sync. Note your comment in other thread "Synchronisation failure is where the hub can't maintain a lock on one or more of the 28 channels it uses to connect with the gear in the street cabinet.  And when it does lose synch, that loss of one or more channels becomes a "partial service".  What that means for the customer is slowdowns, disconnection and poor latency.  The hub does try and renegotiate the lost channel, but that takes time, and the problem will recur." 

Combine that with my earlier observation that VM application "Checking for in house faults alternates, between check device and check (My VM) account, but never completes." M200 order is still "new" and its payment set-up has not been finalised. 

Conclude more than one "stability" problem and M200 speeds will suffer. 

Kind regards.