Menu
Reply
  • 24
  • 0
  • 6
arthurhanlon
On our wavelength
497 Views
Message 21 of 45
Flag for a moderator

Re: Yet another poor speed problem

So engineer came first thing this morning, very helpful and friendly as always with Virgin engineers, tested the line and could find no issues however he did only have the diagnostic tools hooked up for 5 minutes. Second line(?) also could not find any issues so modem replaced. Will heed the engineer's advice and keep my own equipment off the hub for the next 24 to 48 hours and leave it in router mode but to be frank, BQM seems to now look worse than before with higher latency and what looks like more dropped packets (page 1 of this post).

Doesn't appear to be any post RS errors though but it's only been running for a few hours so I'll keep an eye on it for the remainder of the day.

Probably looking for some official Virgin feedback on this but if I still find that there is still an issues, what are my options given that neither support or engineering can find an issue?

Cheers

0 Kudos
Reply
  • 9
  • 0
  • 3
MJWMJW
Tuning in
484 Views
Message 22 of 45
Flag for a moderator

Re: Yet another poor speed problem

Why not run a Wireshark capture to get some idea of what's happening?

0 Kudos
Reply
  • 24
  • 0
  • 6
arthurhanlon
On our wavelength
476 Views
Message 23 of 45
Flag for a moderator

Re: Yet another poor speed problem

Wireshark is fine if you can read the output but I'm not confident I could meaningfully decipher it. I can kind of read it but not enough to know what's going on.

0 Kudos
Reply
  • 9
  • 0
  • 3
MJWMJW
Tuning in
468 Views
Message 24 of 45
Flag for a moderator

Re: Yet another poor speed problem

why not give it a go anyway.. in default if you see lots of black lines, they are generally bad... duplicate ACK, packets out of sequence, restransmissions that kind of thing.. I can give you a display filter to limit to traffic off your network only

  • 24
  • 0
  • 6
arthurhanlon
On our wavelength
473 Views
Message 25 of 45
Flag for a moderator

Re: Yet another poor speed problem

Already done, just run for under half an hour 🙂 Am now looking blankly at the screen lol

There's not a huge amount of black to be fair. Any help is appreciated at this stage.

Cheers

0 Kudos
Reply
  • 24
  • 0
  • 6
arthurhanlon
On our wavelength
443 Views
Message 26 of 45
Flag for a moderator

Re: Yet another poor speed problem

So yet again I cannot seem to access the Superhub web page to get at the logs as it's timing out, I am having to power cycle it which of course resets of the PostRS error counters. Last time I checked it and managed to get through I was still seeing multiple T1-4 timeouts and still a fair amount of PostRS errors on a few channels. I'd love to post updated logs but I simply cannot gain access to the hub on any device I have.

The timeouts are completely disconnecting my modem albeit for a few seconds. An engineer has diagnosed the line for all of 5 minutes and replaced the router which I assume now rules out an issue with the hardware itself so there MUST be something wrong with the signal. I could really do with some advice from a member of the Virgin Media team on what my next steps are with this as it's certainly not the quality of connection I have come to expect from Virgin Media over the years. Again the helpline have been utterly useless and if anything have been more of a barrier in getting some kind of resolution to this.

Thanks

  • 24
  • 0
  • 6
arthurhanlon
On our wavelength
434 Views
Message 27 of 45
Flag for a moderator

Re: Yet another poor speed problem

Finally in, see below:

Downstream bonded channels

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

12990000001.540256 qam21
2419000000-0.540256 qam30
3411000000-0.240256 qam29
4403000000-0.440256 qam28
53950000000.240256 qam27
63870000000.240256 qam26
73790000000.240256 qam25
83230000001.240256 qam24
93150000001.240256 qam23
103070000001.440256 qam22
112910000001.740256 qam20
122830000001.540256 qam19
132750000001.440256 qam18
14267000000140256 qam17
15259000000140256 qam16
162510000001.540256 qam15
172430000001.440256 qam14
182350000001.540256 qam13
192270000001.540256 qam12
202190000001.538256 qam11
212110000001.440256 qam10
222030000001.540256 qam9
231950000001.540256 qam8
241870000001.740256 qam7



Downstream bonded channels

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

1Locked40.315011
2Locked40.9810
3Locked40.3890
4Locked40.31420
5Locked40.9580
6Locked40.389657
7Locked40.9670
8Locked40.91650
9Locked40.95460
10Locked40.9790
11Locked40.3750
12Locked40.3940
13Locked40.33350
14Locked40.311970
15Locked40.916670
16Locked40.3197010
17Locked40.916970
18Locked40.96820
19Locked40.311429
20Locked38.6218822
21Locked40.324682
22Locked40.3251511
23Locked40.9133212
24Locked40.386211616
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
12580000047.8512064 qam76
25370000049.3512064 qam77
33260000048512064 qam75
43940000048.3512064 qam74


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0010
2ATDMA0030
3ATDMA0000
4ATDMA0030

 

Network Log
Time Priority Description
1970-01-01 00:01:26.00 Warning! Lost MDD Timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:26.00 Warning! MDD message timeout;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:40.00 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-19 08:28:51.00 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-19 08:28:55.00 notice SW Download INIT - Via Config file
2019-01-19 08:31:29.00 Error Disruption during SW download - Power Failure
2019-01-19 08:31:45.00 notice SW Download INIT - Via Config file
2019-01-19 08:36:30.00 notice SW download Successful - Via Config file
2019-01-19 18:00:20.00 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-22 10:47:07.00 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-22 13:15:43.00 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-22 14:31:37.00 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-22 21:11:52.00 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-23 07:48:07.00 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-23 10:33:27.00 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-24 06:06:35.00 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-24 12:30:51.00 Error DHCP RENEW sent - No response for IPv4;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
2019-01-25 14:59:38.00 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
  • 15.2K
  • 653
  • 32
Moderator (Retired) John_G
Moderator (Retired)
406 Views
Message 28 of 45
Flag for a moderator

Re: Yet another poor speed problem

Hi Arthurhanlon,

I've just checked your connection from here and can find no issues whatsoever. Your power levels, SNR and area contention are all healthy. The hub has been online for 2 days and 8 hours with no drop outs. Are you still seeing the same issues or has this been resolved since the last reboot?

 


The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
Reply
  • 24
  • 0
  • 6
arthurhanlon
On our wavelength
378 Views
Message 29 of 45
Flag for a moderator

Re: Yet another poor speed problem

Still seeing issues unfortunately.

How can the post rs errors and T3 timeouts be explained if everything looks ok?

0 Kudos
Reply
  • 2
  • 0
  • 1
Richielee909
Joining in
371 Views
Message 30 of 45
Flag for a moderator

Re: Yet another poor speed problem

Screenshot_20190203-102932.png

The top result is after a router restart. I give up. 

0 Kudos
Reply