Menu
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
396 Views
Message 1 of 17
Flag for a moderator

High Latency Spikes

Hi all,

I've a problem with my broadband connection that seems to be showing up in the Network Log T3 Time-outs. It's seems it may be the root cause of my issues with cable channels freezing and reports of me dropping out during Skype calls.

 

Please could someone review the output below for any obvious issues?

 

Many thanks,

Shaun

 

Time Priority Description

26/06/2019 05:49:46ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/06/2019 18:25:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/06/2019 21:34:46ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/06/2019 21:37:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2019 05:27:16ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2019 07:14:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2019 09:23:31ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/06/2019 13:19:50ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/06/2019 20:44:20Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2019 10:08:46criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2019 23:49:55Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/06/2019 13:31:1ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/06/2019 18:53:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/06/2019 23:21:38ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/07/2019 09:12:19ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/07/2019 15:58:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/07/2019 17:14:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/07/2019 21:05:15Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 02:19:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/07/2019 07:39:0Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
395 Views
Message 2 of 17
Flag for a moderator

Re: High Latency Spikes

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

1323000000240256 qam24
2139000000440256 qam1
31470000003.940256 qam2
41550000003.740256 qam3
51630000003.540256 qam4
61710000004.340256 qam5
71790000002.740256 qam6
8187000000340256 qam7
91950000003.940256 qam8
102030000003.940256 qam9
112110000003.940256 qam10
122190000003.940256 qam11
132270000003.740256 qam12
142350000003.540256 qam13
152430000003.240256 qam14
16251000000340256 qam15
17259000000340256 qam16
182670000002.940256 qam17
192750000002.940256 qam18
202830000002.740256 qam19
212910000002.540256 qam20
222990000002.540256 qam21
233070000002.240256 qam22
243150000002.240256 qam23



Downstream bonded channels

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

1Locked40.94470
2Locked40.91770
3Locked40.91300
4Locked40.327936
5Locked40.97779319
6Locked40.98351909
7Locked40.926929
8Locked40.3447487
9Locked40.9313242
10Locked40.92080
11Locked40.33100
12Locked40.91530
13Locked40.92200
14Locked40.93320
15Locked40.93350
16Locked40.33550
17Locked40.94230
18Locked40.33340
19Locked40.33400
20Locked40.33840
21Locked40.32820
22Locked40.34220
23Locked40.93960
24Locked40.34980
0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
393 Views
Message 3 of 17
Flag for a moderator

Re: High Latency Spikes

Upstream bonded channels

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

1394000004.175512064 qam4
2462000004.25512064 qam3
3537000004.35512064 qam2
4603000004.425512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
391 Views
Message 4 of 17
Flag for a moderator

Re: High Latency Spikes

0 Kudos
Reply
  • 2.25K
  • 124
  • 277
Forum Team
Forum Team
361 Views
Message 5 of 17
Flag for a moderator

Re: High Latency Spikes

Hi shaunruk

How are things looking now?

Let me know if you need me to look into this

Gareth_L

0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
358 Views
Message 6 of 17
Flag for a moderator

Re: High Latency Spikes

Hi Gareth,

Thanks for replying. Things still seem pretty bad to me, if not worse. I've attached the latest BBQM graph below.

Could you possibly comment on the levels/errors please?

Many thanks,

Shaun

0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
346 Views
Message 7 of 17
Flag for a moderator

Re: High Latency Spikes

Here's a traceroute test to bbc.co.uk

Trace Statistics : traceroute to bbc.co.uk (151.101.128.81), 30 hops max, 38 byte packets
1 * * *
2 midd-core-2a-xe-123-0.network.virginmedia.net (62.254.65.41) 10.000 ms 10.000 ms 0.000 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 213.46.174.118 (213.46.174.118) 20.000 ms 30.000 ms 20.000 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17

0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
345 Views
Message 8 of 17
Flag for a moderator

Re: High Latency Spikes

And one to google.co.uk

Trace Statistics : traceroute to google.co.uk (216.58.211.163), 30 hops max, 38 byte packets
1 * * *
2 midd-core-2a-xe-123-0.network.virginmedia.net (62.254.65.41) 10.000 ms 10.000 ms 20.000 ms
3 * * *
4 tele-ic-8-ae5-0.network.virginmedia.net (62.252.224.94) 20.000 ms 10.000 ms 20.000 ms
5 86-14-250-212.static.virginm.net (212.250.14.86) 50.000 ms 126-14-250-212.static.virginm.net (212.250.14.126) 20.000 ms 86-14-250-212.static.virginm.net (212.250.14.86) 20.000 ms
6 74.125.242.65 (74.125.242.65) 30.000 ms * *
7 dub08s01-in-f163.1e100.net (216.58.211.163) 20.000 ms 172.253.68.211 (172.253.68.211) 0.000 ms 30.000 ms
Trace complete.

0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
346 Views
Message 9 of 17
Flag for a moderator

Re: High Latency Spikes

Trace Statistics : traceroute to google.com (216.58.213.110), 30 hops max, 38 byte packets
1 * * *
2 midd-core-2a-xe-123-0.network.virginmedia.net (62.254.65.41) 10.000 ms 10.000 ms 10.000 ms
3 * * *
4 tele-ic-8-ae5-0.network.virginmedia.net (62.252.224.94) 20.000 ms 110.000 ms 70.000 ms
5 86-14-250-212.static.virginm.net (212.250.14.86) 40.000 ms 126-14-250-212.static.virginm.net (212.250.14.126) 20.000 ms 86-14-250-212.static.virginm.net (212.250.14.86) 20.000 ms
6 108.170.246.129 (108.170.246.129) 20.000 ms 108.170.246.161 (108.170.246.161) 20.000 ms *
7 172.253.68.210 (172.253.68.210) 20.000 ms 172.253.68.218 (172.253.68.218) 20.000 ms 172.253.66.98 (172.253.66.98) 20.000 ms
8 lhr25s02-in-f14.1e100.net (216.58.213.110) 40.000 ms 0.000 ms 20.000 ms
Trace complete.

0 Kudos
Reply
  • 13
  • 0
  • 0
shaunruk
Joining in
342 Views
Message 10 of 17
Flag for a moderator

Re: High Latency Spikes

PING google.com (216.58.211.174): 64 data bytes
72 bytes from 216.58.211.174: seq=0 ttl=56 time=20.000 ms
72 bytes from 216.58.211.174: seq=1 ttl=56 time=20.000 ms
72 bytes from 216.58.211.174: seq=2 ttl=56 time=22960.000 ms
72 bytes from 216.58.211.174: seq=3 ttl=56 time=34060.000 ms
--- google.com ping statistics ---
10 packets transmitted, 4 packets received, 60% packet loss
round-trip min/avg/max = 20.000/14265.000/34060.000 ms

0 Kudos
Reply