Menu
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
310 Views
Message 1 of 11
Flag for a moderator

Upgraded to hub 4....awful speed.

I upgraded last week to gigabit and since upgrading to hub 4, the connection has been awful. Constantly bad network messages and trying to get through to virgin media is like pulling teeth. Never had any issues with previous hub or internal wifi...now cannot connect to sky Q, or my office. The connect app doesn't support this equipment so it cant help.

Please can someone help..

0 Kudos
Reply
Anonymous
Not applicable
302 Views
Message 2 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.


@shannonj wrote:

I upgraded last week to gigabit and since upgrading to hub 4, the connection has been awful. Constantly bad network messages and trying to get through to virgin media is like pulling teeth. Never had any issues with previous hub or internal wifi...now cannot connect to sky Q, or my office. The connect app doesn't support this equipment so it cant help.

Please can someone help..


Could you access your router using http://192.168.0.1/ or http://192.168.100.1 for modem mode. Log in, select the 'Advanced settings / Tools / Network status' option and paste your 'Downstream', 'Upstream', and 'Network Log' tabs? Please copy/paste this data as text, split between multiple posts (Sometimes you have to click 'Post' twice due to an error message).

Could you please create a BQM (Broadband Quality Monitor) here, and post the live link?

0 Kudos
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
284 Views
Message 3 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

3.0 Downstream channels

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

253307500001.59999838.983261QAM25625
11387500006.90000240.946209QAM2561
21467500006.80000340.366287QAM2562
31547500006.59999840.366287QAM2563
41627500006.09999840.366287QAM2564
51707500005.59999840.366287QAM2565
61787500005.09999840.366287QAM2566
71867500005.00000040.366287QAM2567
81947500005.00000040.366287QAM2568
92027500004.90000240.366287QAM2569
102107500004.69999740.366287QAM25610
112187500004.59999840.366287QAM25611
122267500004.40000240.366287QAM25612
132347500004.40000240.366287QAM25613
142427500004.40000240.366287QAM25614
152507500004.40000240.366287QAM25615
162587500004.40000238.983261QAM25616
172667500003.90000238.983261QAM25617
182747500003.29999938.983261QAM25618
192827500002.79999940.366287QAM25619
202907500002.50000038.983261QAM25620
212987500001.70000138.983261QAM25621
223067500001.00000037.636276QAM25622
233147500002.20000138.983261QAM25623
243227500001.90000238.983261QAM25624
263707500001.40000238.983261QAM25626
273787500001.40000238.983261QAM25627
283867500001.50000038.983261QAM25628
293947500001.50000038.983261QAM25629
304027500001.59999838.983261QAM25630
314107500001.59999838.983261QAM25631



3.0 Downstream channels

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

25Locked000
1Locked336500
2Locked336500
3Locked336500
4Locked336500
5Locked336500
6Locked336500
7Locked336500
8Locked336500
9Locked336500
10Locked336500
11Locked336500
12Locked336500
13Locked336500
14Locked336500
15Locked336500
16Locked336500
17Locked336500
18Locked336500
19Locked336500
20Locked336500
21Locked336500
22Locked336500
23Locked336500
24Locked336500
26Locked336500
27Locked336500
28Locked336500
29Locked336500
30Locked336500
31Locked143905600



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159864K1680QAM4096424


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked 2.820114290
0 Kudos
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
283 Views
Message 4 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

3.0 Upstream channels

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

16030000033.5205995120 KSym/sec64QAM1
23260000032.0205995120 KSym/sec64QAM5
33940000032.0205995120 KSym/sec64QAM4
44620000033.0205995120 KSym/sec64QAM3



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0049
2US_TYPE_STDMA0049
3US_TYPE_STDMA0049
4US_TYPE_STDMA0049
0 Kudos
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
281 Views
Message 5 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

Network Log

Time Priority Description

Sat 14/11/2020 12:20:003Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 12:20:004T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 12:20:003REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 12:20:525MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 12:21:046SW Download INIT - Via Config file dsfd;kfoA,.iyewrkldJKDHSU
Sat 14/11/2020 12:22:216SW download Successful - Via Config file
Sat 14/11/2020 12:24:525MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 12:37:085DBC-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;
Sat 14/11/2020 12:52:124DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 12:52:126DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 13:51:004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 13:51:006DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 18:38:425MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 14/11/2020 18:50:595DBC-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;
Sat 14/11/2020 21:24:106CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; 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;
Wed 18/11/2020 04:14:434DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 18/11/2020 04:14:436DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 19/11/2020 07:48:543No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 19/11/2020 09:30:205MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 19/11/2020 09:42:355DBC-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;
Thu 19/11/2020 09:42:363No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 19/11/2020 22:57:165MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 19/11/2020 23:09:325DBC-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;
Sun 22/11/2020 06:40:543No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 22/11/2020 12:54:004DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 22/11/2020 12:54:006DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 22/11/2020 18:07:283No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/11/2020 14:23:446CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; 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;
Mon 23/11/2020 14:23:495Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/11/2020 14:24:316CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; 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;
Mon 23/11/2020 14:24:323Received 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;
Mon 23/11/2020 14:24:406CM-STATUS message sent. Event Type Code: 4; Chan ID: 1; 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;
Mon 23/11/2020 14:24:523Received 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;
Mon 23/11/2020 14:24:556CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; 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;
Mon 23/11/2020 14:25:123Received 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;
Mon 23/11/2020 14:25:266CM-STATUS message sent. Event Type Code: 5; Chan ID: 25; 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;
Mon 23/11/2020 14:25:323Received 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;
Mon 23/11/2020 14:25:396CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; 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;
Mon 23/11/2020 14:26:315MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/11/2020 14:38:435DBC-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;
Mon 23/11/2020 14:53:475Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/11/2020 14:53:476CM-STATUS message sent. Event Type Code: 1; Chan ID: 1; 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;
Mon 23/11/2020 14:53:475Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/11/2020 14:54:203No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 23/11/2020 14:54:233Received 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;
Mon 23/11/2020 14:54:246CM-STATUS message sent. Event Type Code: 4; Chan ID: 1; 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;
Mon 23/11/2020 14:54:433Received 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;
Mon 23/11/2020 14:54:476CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Anonymous
Not applicable
274 Views
Message 6 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.


@shannonj wrote:

3.0 Upstream channels

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

16030000033.5205995120 KSym/sec64QAM1
23260000032.0205995120 KSym/sec64QAM5
33940000032.0205995120 KSym/sec64QAM4
44620000033.0205995120 KSym/sec64QAM3



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0049
2US_TYPE_STDMA0049
3US_TYPE_STDMA0049
4US_TYPE_STDMA0049

Your upstream power levels are very low and should be adjusted really (An engineer visit would be required).

You also have a number of timeouts (Highlighted).

Lots of errors in your network log.

We can check over your BQM once you create it.

0 Kudos
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
265 Views
Message 7 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

shannonj_1-1606145815526.png

 

0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.94K
Alessandro Volta
257 Views
Message 8 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

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.

Post a 'Live Link' to your BQM on here.

Instructions for posting BQM 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.
0 Kudos
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
252 Views
Message 9 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

My BQM 

0 Kudos
Reply
shannonj
  • 7
  • 0
  • 0
Joining in
205 Views
Message 10 of 11
Flag for a moderator

Re: Upgraded to hub 4....awful speed.

any update on what can be done? 

0 Kudos
Reply