Menu
Reply
Simulacra
  • 21
  • 0
  • 0
Tuning in
854 Views
Message 1 of 31
Flag for a moderator

22-25mbps instead of 107mbps promised for M200.

Simulacra_0-1609006672347.png

Since tomorrow... 

Called to CC, they unable even to identify the problem. 

No engineer sent to take a look and fix the issue this year. 

I have much time enough to change my mind and change ISP. 

I paid a fortune for VM cable; it becomes golden despite all possible deprication.

My initial contract was 27 GBP for 100Mbps. Now I pay more than 42 for 25mbps.

Where the progress came?

Tags (2)
0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.95K
Alessandro Volta
846 Views
Message 2 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

If possible can you set up a Broadband Quality Monitor (BQM) at thinkbroadband.com - this will give you an insight into what is happening with the signal at the other side of the Hub, it will take a few hours to get any kind of trend showing although you should post the link straight away.

Please post a 'Live Link' to your BQM on here.

Instructions for posting BQM Live Link

Under your BQM graph are two links in red.

Click the lower link (Share Live Graph) then click generate.

Copy the text in the Direct Link box, beware, there may be more text than you can see.

On here click the Link icon (2 links chain to the left of the camera icon)

In the URL box paste the link you copied and in the ‘text to display’ box write My BQM then click OK - you can post the link straight away.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.95K
Alessandro Volta
845 Views
Message 3 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Can you please

Type 192.168.0.1 (192.168.100.1 in Modem mode) into your browser URL bar and press enter. 

Hub 2 & 3 When the page appears DO NOT LOG IN but click ‘Check Router Status’.

Hub 4 When the page appears LOG IN then Advanced Settings > Tools > Network Status.

Copy and paste the contents of the Downstream, Upstream, Configuration and Network Log tabs onto here, if you get a yellow / straw box warning click the Post button again. Use one post for each tab if you wish.

Please do not use screen grabs.

A Guru will be along soon to decipher the info.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
Simulacra
  • 21
  • 0
  • 0
Tuning in
699 Views
Message 4 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Downstream  DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)139000000147000000155000000163000000171000000179000000187000000195000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID12345678
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)1.041.381.401.671.661.731.811.98
RxMER (dB)33.6034.0834.2134.6334.9335.0835.4235.60
Pre RS Errors2007043518624750179040291728130016719300163245111546870214886929
Post RS Errors74402003903044228293414787651139008862200453713282093

 

Upstream  US-1 US-2 US-3 US-4

Channel Type2.02.02.02.0
Channel ID6534
Frequency (Hz)25800000326000004620000039400000
Ranging StatusSuccessSuccessSuccessSuccess
Modulation64QAM64QAM64QAM64QAM
Symbol Rate (Sym/sec)5120000512000051200005120000
Mini-Slot Size2222
Power Level (dBmV)51.0051.0051.0051.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts9273
T4 Timeouts0000

 

General Configuration

Network AccessAllowed
Maximum Number of CPEs1
Baseline PrivacyEnabled
DOCSIS ModeEuroDOCSIS 3.0
Config File 

Primary Downstream Service Flow

SFID28816
Max Traffic Rate230000061 bps
Max Traffic Burst42600 bytes
Min Traffic Rate0 bps

Primary Upstream Service Flow

SFID28815
Max Traffic Rate22000061 bps
Max Traffic Burst42600 bytes
Min Traffic Rate0 bps
Max Concatenated Burst42600 bytes
Scheduling Type

 

Network Log

First TimeLast TimePriorityError NumberDescription
26/12/2020 18:41:12 GMT26/12/2020 18:41:12 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:40:29 GMT26/12/2020 18:40:29 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:39:06 GMT26/12/2020 18:39:06 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:38:07 GMT26/12/2020 18:38:07 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 17:13:32 GMT26/12/2020 17:13:32 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 17:13:31 GMT26/12/2020 17:13:31 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 16:59:56 GMT26/12/2020 16:59:56 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 16:59:55 GMT26/12/2020 16:59:55 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 16:59:44 GMT26/12/2020 16:59:44 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:59:10 GMT26/12/2020 16:59:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:57:15 GMT26/12/2020 16:57:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:53:26 GMT26/12/2020 16:53:26 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:47:44 GMT26/12/2020 16:47:44 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:46:43 GMT26/12/2020 16:46:43 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:38:46 GMT26/12/2020 16:38:46 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:34:26 GMT26/12/2020 16:34:26 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:34:00 GMT26/12/2020 16:34:00 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:24:56 GMT26/12/2020 16:24:56 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:24:29 GMT26/12/2020 16:24:29 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:20:41 GMT26/12/2020 16:20:41 GMTCritical (3)82000200No Ranging Response received - T3 time-out

 

 

 

 

0 Kudos
Reply
Simulacra
  • 21
  • 0
  • 0
Tuning in
822 Views
Message 5 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Downstream  DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8

Frequency (Hz)139000000147000000155000000163000000171000000179000000187000000195000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID12345678
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)1.001.461.401.721.611.761.842.04
RxMER (dB)33.6034.0834.2134.6334.9335.0835.4235.60
Pre RS Errors2014271118684977179594551733262316767394163705991551086514926421
Post RS Errors74520643906922228550214803081140174863095454093282271

 

Upstream  US-1 US-2 US-3 US-4

Channel Type2.02.02.02.0
Channel ID6534
Frequency (Hz)25800000326000004620000039400000
Ranging StatusSuccessSuccessSuccessSuccess
Modulation64QAM64QAM64QAM64QAM
Symbol Rate (Sym/sec)5120000512000051200005120000
Mini-Slot Size2222
Power Level (dBmV)51.0051.0051.0051.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts9273
T4 Timeouts0000

 

Upstream Burst  Req(1) Init Maint(3) Per Maint(4) Adv Short(9) Adv Long(10) Adv UGS(11)

Modulation Type16QAMQPSK16QAM64QAM64QAM16QAM
Differential EncodingOFFOFFOFFOFFOFFOFF
Preamble Length56640384104104104
Preamble Value Offset65200716716716
FEC Error Correction (T)05510165
FEC Codeword Information Bytes (K)1634348122386
Maximum Burst Size0003255255
Guard Time Size84848888
Last Codeword LengthFixedFixedFixedShortenedShortenedShortened
Scrambler On/OffONONONONONON

 

General Configuration

Network AccessAllowed
Maximum Number of CPEs1
Baseline PrivacyEnabled
DOCSIS ModeEuroDOCSIS 3.0
Config File 

Primary Downstream Service Flow

SFID28816
Max Traffic Rate230000061 bps
Max Traffic Burst42600 bytes
Min Traffic Rate0 bps

Primary Upstream Service Flow

SFID28815
Max Traffic Rate22000061 bps
Max Traffic Burst42600 bytes
Min Traffic Rate0 bps
Max Concatenated Burst42600 bytes
Scheduling TypeBest Effort

 

Network Log

First TimeLast TimePriorityError NumberDescription
26/12/2020 18:52:35 GMT26/12/2020 18:52:35 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:41:12 GMT26/12/2020 18:41:12 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:40:29 GMT26/12/2020 18:40:29 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:39:06 GMT26/12/2020 18:39:06 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 18:38:07 GMT26/12/2020 18:38:07 GMTWarning (5)66050310Auth Success - Web login successful.
26/12/2020 17:13:32 GMT26/12/2020 17:13:32 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 17:13:31 GMT26/12/2020 17:13:31 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 16:59:56 GMT26/12/2020 16:59:56 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 16:59:55 GMT26/12/2020 16:59:55 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 16:59:44 GMT26/12/2020 16:59:44 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:59:10 GMT26/12/2020 16:59:10 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:57:15 GMT26/12/2020 16:57:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:53:26 GMT26/12/2020 16:53:26 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:47:44 GMT26/12/2020 16:47:44 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:46:43 GMT26/12/2020 16:46:43 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:38:46 GMT26/12/2020 16:38:46 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:34:26 GMT26/12/2020 16:34:26 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:34:00 GMT26/12/2020 16:34:00 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:24:56 GMT26/12/2020 16:24:56 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 16:24:29 GMT26/12/2020 16:24:29 GMTCritical (3)82000200No Ranging Response received - T3 time-out
0 Kudos
Reply
Simulacra
  • 21
  • 0
  • 0
Tuning in
818 Views
Message 6 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Direct Link to  Live Graph

0 Kudos
Reply
Simulacra
  • 21
  • 0
  • 0
Tuning in
810 Views
Message 7 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Screenshot 2020-12-26 191443.png

0 Kudos
Reply
Simulacra
  • 21
  • 0
  • 0
Tuning in
768 Views
Message 8 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Simulacra_0-1609022720022.png

 

0 Kudos
Reply
Simulacra
  • 21
  • 0
  • 0
Tuning in
750 Views
Message 9 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Network Log

First TimeLast TimePriorityError NumberDescription
26/12/2020 22:41:51 GMT26/12/2020 22:41:51 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:39:27 GMT26/12/2020 22:39:27 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:38:01 GMT26/12/2020 22:38:01 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:35:27 GMT26/12/2020 22:35:27 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:35:15 GMT26/12/2020 22:35:15 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:31:15 GMT26/12/2020 22:31:15 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:31:14 GMT26/12/2020 22:31:14 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:27:59 GMT26/12/2020 22:27:59 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:27:36 GMT26/12/2020 22:27:36 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:27:12 GMT26/12/2020 22:27:12 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:27:10 GMT26/12/2020 22:27:10 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:27:10 GMT26/12/2020 22:27:10 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:27:10 GMT26/12/2020 22:27:10 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:26:45 GMT26/12/2020 22:26:45 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:20:23 GMT26/12/2020 22:20:23 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:18:35 GMT26/12/2020 22:18:35 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:18:03 GMT26/12/2020 22:18:03 GMTCritical (3)82000200No Ranging Response received - T3 time-out
26/12/2020 22:17:35 GMT26/12/2020 22:17:35 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:15:23 GMT26/12/2020 22:15:23 GMTWarning (5)84020200Lost MDD Timeout
26/12/2020 22:15:18 GMT26/12/2020 22:15:18 GMTCritical (3)82000200No Ranging Response received - T3 time-out
0 Kudos
Reply
DJ_Shadow1966
  • 7.2K
  • 1.37K
  • 2.06K
Very Insightful Person
Very Insightful Person
706 Views
Message 10 of 31
Flag for a moderator

Re: 22-25mbps instead of 107mbps promised for M200.

Hello

Looking at the stats there is a problem with the upstream power levels these are close too above the maximum level and will cause some problems with downstream as well, looking at the downstream you have a high number of post RS errors now with all of the above one thing that can cause this is noise on the line and may be resolve by, going around and making sure all coaxial connections to all VM equipment are finger tight best way to do this is too loosen the connector and re-tighten, once that is done power off the hub for 30 secs and back, again check a couple of times in your downstream and if the Post RS errors are rising at a large rate then a VM staff member needs to have a closer look, and maybe you will need an engineer to fix this.

Regards Mike

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks