Menu
Reply
hgndl
  • 6
  • 0
  • 0
Joining in
408 Views
Message 1 of 9
Flag for a moderator

Small amounts of packet loss

I am getting consistent small amount of packet loss and high tail latencies, not sure why this is the case. I have the Gig1 package and I am running my SH4 in modem mode with an EdgeRouter 4. Below is my BQM to demonstrate my point. The initial packet loss isn't related, ICMP was disabled.

8e2cc0f4961259ec986360bd721f205f74d248ca

 

 

0 Kudos
Reply
gary_dexter
  • 31.33K
  • 1.94K
  • 4.22K
Alessandro Volta
386 Views
Message 2 of 9
Flag for a moderator

Re: Small amounts of packet loss

Post the Network, Upstream and Downstream logs from the hubs admin pages 


*****
If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!!
I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences.
Office 365, Dynamics CRM and Cloud Computing Jedi
0 Kudos
Reply
legacy1
  • 17.07K
  • 731
  • 1.71K
Alessandro Volta
385 Views
Message 3 of 9
Flag for a moderator

Re: Small amounts of packet loss

Likely noise on the Docsis line can you ping -n 200 194.168.4.100 to see if you get packet loss?

Other tests you can do is change the Ethernet cable power off the hub in modem mode for 2mins connect a PC to the hub and power on setup a new BQM see if you get packet loss like that.

---------------------------------------------------------------
0 Kudos
Reply
hgndl
  • 6
  • 0
  • 0
Joining in
369 Views
Message 4 of 9
Flag for a moderator

Re: Small amounts of packet loss

Network Log

Time Priority Description

Sun 08/11/2020 00:34:576DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 09/11/2020 01:34:063No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 11/11/2020 12:34:574DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 11/11/2020 12:34:576DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 12/11/2020 13:49:023No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 15/11/2020 00:34:574DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 15/11/2020 00:34:576DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 15/11/2020 11:09:033No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 18/11/2020 12:34:574DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 18/11/2020 12:34:576DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 22/11/2020 00:34:584DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 22/11/2020 00:34:586DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 24/11/2020 01:18:546SW Download INIT - Via NMS
Tue 24/11/2020 01:20:426SW download Successful - Via NMS
Tue 24/11/2020 01:23:265MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 24/11/2020 13:45:373No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 26/11/2020 12:59:094DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 26/11/2020 12:59:096DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 28/11/2020 22:12:363No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 29/11/2020 13:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 29/11/2020 13:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 03/12/2020 01:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 03/12/2020 01:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 05/12/2020 05:15:083No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 06/12/2020 13:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 06/12/2020 13:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 06/12/2020 17:38:593No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 10/12/2020 01:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 10/12/2020 01:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 11/12/2020 22:41:003No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 13/12/2020 13:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 13/12/2020 13:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 14/12/2020 21:58:113No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 17/12/2020 01:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 17/12/2020 01:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 17/12/2020 12:57:093No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 20/12/2020 13:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 20/12/2020 13:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 24/12/2020 01:17:074DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 24/12/2020 01:17:076DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/12/2020 11:17:143No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/12/2020 18:14:353SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 25/12/2020 18:17:215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 26/12/2020 18:24:263No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 28/12/2020 09:47:144DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 28/12/2020 09:47:146DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 30/12/2020 17:44:383No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 31/12/2020 12:02:184DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
hgndl
  • 6
  • 0
  • 0
Joining in
367 Views
Message 5 of 9
Flag for a moderator

Re: Small amounts of packet loss

3.0 Downstream channels

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

304027500006.240.4QAM25630
11387500006.540.4QAM2561
21467500006.740.9QAM2562
31547500006.840.9QAM2563
41627500006.740.9QAM2564
51707500006.640.4QAM2565
61787500006.640.4QAM2566
71867500006.740.4QAM2567
81947500006.940.4QAM2568
92027500006.940.9QAM2569
102107500006.840.9QAM25610
112187500006.840.4QAM25611
122267500006.840.4QAM25612
132347500006.840.9QAM25613
142427500006.740.4QAM25614
152507500006.540.9QAM25615
162587500006.240.4QAM25616
172667500005.840.4QAM25617
182747500005.740.9QAM25618
192827500005.840.4QAM25619
20290750000640.9QAM25620
212987500006.140.4QAM25621
223067500006.340.9QAM25622
233147500006.240.9QAM25623
243227500006.240.4QAM25624
253307500006.140.4QAM25625
263707500006.340.4QAM25626
27378750000640.9QAM25627
283867500006.340.4QAM25628
29394750000640.4QAM25629
314107500006.340.4QAM25631



3.0 Downstream channels

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

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



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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked427.9690708490
0 Kudos
Reply
hgndl
  • 6
  • 0
  • 0
Joining in
366 Views
Message 6 of 9
Flag for a moderator

Re: Small amounts of packet loss

3.0 Upstream channels

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

15370000031.55120 KSym/sec64QAM10
23260000031.55120 KSym/sec64QAM13
33940000031.55120 KSym/sec64QAM12
44620000031.55120 KSym/sec64QAM11



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
0 Kudos
Reply
hgndl
  • 6
  • 0
  • 0
Joining in
358 Views
Message 7 of 9
Flag for a moderator

Re: Small amounts of packet loss

Ping statistics for 194.168.4.100:
    Packets: Sent = 200, Received = 199, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 5ms, Maximum = 26ms, Average = 7ms

I did this test a few times and I am losing around 0-2 packets every time.

0 Kudos
Reply
Beth_G
  • 3.97K
  • 234
  • 405
Forum Team
Forum Team
262 Views
Message 8 of 9
Flag for a moderator

Re: Small amounts of packet loss

Hi hgndl,

 

Welcome to the Community Forums, and thank you for posting.

 

I'm sorry to see you've been experiencing some broadband issues recently. I have been able to locate your account and can see that there are some signal level issues, that we require an engineer visit to resolve.

 

I've arranged the earliest engineer appointment for you. Please sign into your My Virgin Media account here and head over to 'Help' > 'My orders and appointment' to view your appointment time slot.

 

If you need anything else in the meantime give us a shout and let us know how the appointment goes.

 

Beth

0 Kudos
Reply
hgndl
  • 6
  • 0
  • 0
Joining in
250 Views
Message 9 of 9
Flag for a moderator

Re: Small amounts of packet loss

It seems like I accidentally cancelled the appointment, would you mind rebooking it please?
0 Kudos
Reply