Menu
Reply
WozDogs182
  • 4
  • 0
  • 0
Tuning in
305 Views
Message 1 of 7
Flag for a moderator

Is This Normal?

Hello Community Members,

I have recently upgraded to 200Mb fibre and I have a wired connection through to my Firestick.

The signal keeps dropping, and that is the same for the Wifi in the house, and over the last 48 hours the speed has been as follows:

IMG_0283.jpg

Not only does the speed rarely get to 200Mb, the consistency is terrible.

Is this normal?

Any helpful suggestions would be much appreciated.

Thank you,

Ian

0 Kudos
Reply
Andrew-G
  • 6.16K
  • 1.08K
  • 2.62K
Very Insightful Person
Very Insightful Person
290 Views
Message 2 of 7
Flag for a moderator
Helpful Answer

Re: Is This Normal?

No its not normal.

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 or images).  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.

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

0 Kudos
Reply
WozDogs182
  • 4
  • 0
  • 0
Tuning in
279 Views
Message 3 of 7
Flag for a moderator

Re: Is This Normal?

Thanks Andruser,

I will do this when I get home and post the results.

Ian

 

0 Kudos
Reply
WozDogs182
  • 4
  • 0
  • 0
Tuning in
244 Views
Message 4 of 7
Flag for a moderator

Re: Is This Normal?

Hello Andruser,

Here is the data:

Downstream Tab

Downstream bonded channels

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

1323000000837256 qam24
22190000007.437256 qam11
32270000007.137256 qam12
4235000000737256 qam13
52430000006.537256 qam14
6251000000637256 qam15
7259000000537256 qam16
8267000000637256 qam17
92750000006.537256 qam18
102830000006.937256 qam19
11291000000737256 qam20
122990000007.937256 qam21
13307000000837256 qam22
14315000000837256 qam23
153310000008.137256 qam25
163390000008.537256 qam26
173470000009.437256 qam27
183550000009.837256 qam28
193630000008.637256 qam29
203710000007.137256 qam30
213790000007.538256 qam31
223870000008.137256 qam32
233950000008.538256 qam33
244030000008.338256 qam34



Downstream bonded channels

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

1Locked37.66811393
2Locked37.6753399
3Locked37.3407339
4Locked37.3484409
5Locked37.6548334
6Locked37.36388528
7Locked37.36767974
8Locked37.35638132
9Locked37.65358398
10Locked37.6371341
11Locked37.6434406
12Locked37.36381169
13Locked37.67261164
14Locked37.66731229
15Locked37.68381794
16Locked37.67531865
17Locked37.65682395
18Locked37.66852191
19Locked37.62014617
20Locked37.61734192
21Locked38.62783915
22Locked37.613822773
23Locked38.910622792
24Locked38.6575

2586

 

Upstream Data:

Upstream bonded channels

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

14620000042512064 qam8
25370000042.5512064 qam7
33940000041.5512064 qam9
46030000043512064 qam6



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0030
2ATDMA0030
3ATDMA0030
4ATDMA0010

 

Thanks,

Ian

0 Kudos
Reply
WozDogs182
  • 4
  • 0
  • 0
Tuning in
242 Views
Message 5 of 7
Flag for a moderator

Re: Is This Normal?

2nd part

Hello Andruser,

Network Log:

Network Log

Time Priority Description

25/02/2021 20:04:43noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/02/2021 19:55:49Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/02/2021 17:37:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/02/2021 10:19:11ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/02/2021 01:53:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 17:21:49Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 17:21:49criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 17:21:49Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 16:49:20criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 16:49:20Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 16:49:19criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/02/2021 16:49:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/02/2021 09:12:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/02/2021 10:25:46ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/02/2021 10:25:44ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2021 20:00:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2021 17:37:24ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/02/2021 14:50:3criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/02/2021 13:47:47ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2021 08:26:1criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Thanks,

 

Ian

Tags (1)
0 Kudos
Reply
Andrew-G
  • 6.16K
  • 1.08K
  • 2.62K
Very Insightful Person
Very Insightful Person
191 Views
Message 6 of 7
Flag for a moderator

Re: Is This Normal?

Rather too many upstream T3 errors for my liking, the downstream post-RS error counts are poor (probably what's driving the slow speeds).  The range of downstream power levels also looks to be asking for trouble, in my inexpert opinion.  I'll flag this for the forum staff to take a look and advise.

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

0 Kudos
Reply
Lee_R
  • 2.56K
  • 136
  • 235
Forum Team
Forum Team
170 Views
Message 7 of 7
Flag for a moderator

Re: Is This Normal?

Hi @WozDogs182 , thanks for posting and welcome to our community.

I am really sorry to hear your signal is cutting out. I would like to take a closer look into this for you. I have located your account.  I cannot find any issues with the connection to the hub on our diagnostics screen, so therefore I will send you a private message.

Regards

 

Lee_R

0 Kudos
Reply