Menu
Reply
Highlighted
  • 4
  • 0
  • 0
Joining in
265 Views
Message 1 of 8
Flag for a moderator

Packet drops/Latency

Hi all,

Getting an issue where our internet becomes unresponsive and we lose 4 out of 5 replies to 8.8.8.8 with 600-1500ms latency.

Internal network is fine <1ms across to any device until you leave the router (my own Netgear router, not VM's) and hit the superhub (in modem mode) where response time jumps to +500ms

A simple reboot will get me back online but the issue is now becoming more and more frequent and forces me to reboot the VM router daily.

Any advise would be appreciated.

0 Kudos
Reply
Highlighted
  • 3.5K
  • 566
  • 1.37K
Very Insightful Person
Very Insightful Person
254 Views
Message 2 of 8
Flag for a moderator

Re: Packet drops/Latency

Post the hub's status data for Downstream, Upstream, Network log here (text, not screenshots), and then setup a Broadband Quality Monitor.  The BQM will need to run for 24 hours before we can see if there's useful evidence there, and when you've got that post a link to shared graph (again, not an image).

Then we can see what we're dealing with, and whether there's easy fixes in terms of noise or power issues.

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
Highlighted
  • 4
  • 0
  • 0
Joining in
206 Views
Message 3 of 8
Flag for a moderator

Re: Packet drops/Latency

Thanks for your help @Andruser.

Logs below. Working on the BQM now, will post asap.

Network Log :

Time Priority Description
01/01/1970 00:01:30 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2020 16:59:58 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/09/2020 00:13:1 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2020 07:47:4 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/09/2020 07:46:59 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2020 21:09:57 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/08/2020 22:32:37 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/08/2020 20:34:27 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/08/2020 18:54:22 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/08/2020 15:02:34 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/08/2020 03:07:14 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 18:48:7 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/08/2020 18:31:50 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2020 12:46:39 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2020 01:32:22 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2020 18:58:22 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2020 18:53:47 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/08/2020 23:16:34 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:29 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/08/2020 18:59:42 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

DownStream :

1 331000000 2.2 38 256 qam 25
2 187000000 0.5 37 256 qam 7
3 195000000 0.4 37 256 qam 8
4 203000000 0 37 256 qam 9
5 211000000 0 37 256 qam 10
6 219000000 0 37 256 qam 11
7 227000000 -0.5 37 256 qam 12
8 235000000 -0.9 37 256 qam 13
9 243000000 -1.5 36 256 qam 14
10 251000000 -2 37 256 qam 15
11 259000000 -1.9 37 256 qam 16
12 267000000 -0.7 37 256 qam 17
13 275000000 0 37 256 qam 18
14 283000000 0.4 38 256 qam 19
15 291000000 0.7 38 256 qam 20
16 299000000 1.2 38 256 qam 21
17 307000000 1.2 38 256 qam 22
18 315000000 1.5 38 256 qam 23
19 323000000 2 38 256 qam 24
20 339000000 2.7 38 256 qam 26
21 347000000 2.7 38 256 qam 27
22 355000000 3 37 256 qam 28
23 363000000 3.2 38 256 qam 29
24 371000000 2.9 38 256 qam 30

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 29 0
2 Locked 37.3 25 0
3 Locked 37.3 27 0
4 Locked 37.3 40 0
5 Locked 37.3 58 0
6 Locked 37.6 42 0
7 Locked 37.6 37 14
8 Locked 37.3 62 0
9 Locked 36.6 99 0
10 Locked 37.3 130 0
11 Locked 37.3 132 0
12 Locked 37.3 49 0
13 Locked 37.3 33 0
14 Locked 38.6 30 0
15 Locked 38.6 24 0
16 Locked 38.6 38 0
17 Locked 38.6 37 0
18 Locked 38.6 35 0
19 Locked 38.9 52 0
20 Locked 38.6 28 0
21 Locked 38.6 24 0
22 Locked 37.6 15 0
23 Locked 38.6 47 0
24 Locked 38.6 22 0


Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 53700000 4.625 5120 64 qam 2
2 60300000 4.675 5120 64 qam 1
3 46200000 4.575 5120 64 qam 3
4 39400000 4.55 5120 64 qam 7

Upstream bonded channels
Channel

0 Kudos
Reply
Highlighted
  • 2.51K
  • 147
  • 323
Forum Team
Forum Team
202 Views
Message 4 of 8
Flag for a moderator

Re: Packet drops/Latency

Hi twofacedtrout, thanks for getting in touch.

 

Sorry to hear about the problems with your connection. I've taken a look from here and was unable to identify any issues everything appears to be OK really. As advised by Andruser please follow up with the BQM results when you can so we can try to get a better idea of what's going on at your end.

 

Tom 

0 Kudos
Reply
Highlighted
  • 4
  • 0
  • 0
Joining in
180 Views
Message 5 of 8
Flag for a moderator

Re: Packet drops/Latency

Link to BQM

Its been fairly good over the last 24 hours but you can still see the spikes

https://www.thinkbroadband.com/broadband/monitoring/quality/share/405ee2d89d9ea1227c26fccea66bdd7028...

Please let me know if there is anything else i can do

And thanks again for helping 🙂

0 Kudos
Reply
Highlighted
  • 464
  • 24
  • 47
Forum Team
Forum Team
174 Views
Message 6 of 8
Flag for a moderator

Re: Packet drops/Latency

Thanks for sharing the BQM @twofacedtrout 

 

I've had a check and that looks pretty good at the moment. If you can keep monitoring the BQM and let us know of any drops we'll go from there. Right now the account and the BQM are looking good. 

 

Thanks, 

 

 

Hollie - Forum Team


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
Highlighted
  • 4
  • 0
  • 0
Joining in
109 Views
Message 7 of 8
Flag for a moderator

Re: Packet drops/Latency

Its strange. Everything inside my router has no issues but when you go to the modem and out i have these issues randomly.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=1185ms TTL=116
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=2950ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=207ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=1099ms TTL=116
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=1124ms TTL=116
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=1106ms TTL=116
Reply from 8.8.8.8: bytes=32 time=2300ms TTL=116
Request timed out.
Reply from 8.8.8.8: bytes=32 time=666ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 8.8.8.8: bytes=32 time=328ms TTL=116

My Router

Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64

The VM in modem mode

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=419ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1342ms TTL=63
Reply from 192.168.100.1: bytes=32 time=390ms TTL=63
Reply from 192.168.100.1: bytes=32 time=575ms TTL=63
Reply from 192.168.100.1: bytes=32 time=433ms TTL=63
Reply from 192.168.100.1: bytes=32 time=32ms TTL=63
Reply from 192.168.100.1: bytes=32 time=65ms TTL=63
Reply from 192.168.100.1: bytes=32 time=521ms TTL=63
Reply from 192.168.100.1: bytes=32 time=174ms TTL=63

I've already changed cables and reset to factory default etc etc

Any ideas? 

0 Kudos
Reply
Highlighted
  • 4.2K
  • 168
  • 232
Forum Team
Forum Team
34 Views
Message 8 of 8
Flag for a moderator

Re: Packet drops/Latency

Hi twofacedtrout,

 

Thank you for the updated. I have taken a look on our side and cannot see anything that could be causing the issue. 

 

Can you confirm when you put the hub in modem mode do you attach a 3rd party hub?

 

^Martin

0 Kudos
Reply