Menu
Reply
xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
248 Views
Message 1 of 12
Flag for a moderator

Packet Loss Is Becoming A 'Thing'

Hi all!

New to the VM Community forums - please be gentle 🙂

I've currently got the Gig1 Fibre package, but recently have noticed what I suspected was increased levels of packet loss. The main giveaway was rising levels of lag & rubber banding whilst online gaming.

In order to check this I setup a BQM via thinkbroadband - and here are a selection of graphs from the last 2 weeks...

7-7-21.png

 

9-7-21.png

 

17-7-21.png

 

18-7-21.png

 

21-7-21.png

 

Does this look normal? I know you will always get the occasional loss, but this seems more than that, and happening fairly regularly.

Any help appreciated.

Many thanks!

0 Kudos
Reply
lotharmat
  • 2.54K
  • 188
  • 462
Trouble shooter
209 Views
Message 2 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

Can you post your Hub status and logs?
Someone should be spot if there is a problem
Navigate to http://192.168.0.1 (or http://192.168.100.1 - if in modem mode)
Don't log in!
Click on 'router status'
Copy/paste the data from each of the tabs. The forum software will remove the MAC addresses for you (you may need to click the 'post' button again).



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

0 Kudos
Reply
xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
177 Views
Message 3 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status
Online
DOCSIS 3.1
Primary downstream channel
Locked
SC-QAM
DOCSIS 3.0 channels
31
4
DOCSIS 3.1 channels
1
0
0 Kudos
Reply
xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
176 Views
Message 4 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

3.0 Downstream channels

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

11390000000.20000138.983261QAM2561
21470000000.29999938.605377QAM2562
31550000000.29999938.605377QAM2563
41630000000.29999938.605377QAM2564
51710000000.09999838.605377QAM2565
61790000000.09999838.605377QAM2566
71870000000.09999838.605377QAM2567
81950000000.00000038.983261QAM2568
92030000000.09999838.605377QAM2569
102110000000.09999838.605377QAM25610
11219000000-0.09999838.605377QAM25611
12227000000-0.09999838.605377QAM25612
132350000000.00000038.605377QAM25613
14243000000-0.20000138.605377QAM25614
15251000000-0.40000237.636276QAM25615
16259000000-0.40000237.636276QAM25616
17267000000-0.79999937.636276QAM25617
18275000000-1.00000037.636276QAM25618
19283000000-1.09999838.605377QAM25619
20291000000-1.20000137.636276QAM25620
21299000000-1.00000037.636276QAM25621
22307000000-0.70000137.355988QAM25622
23315000000-0.70000137.636276QAM25623
24323000000-1.29999937.636276QAM25624
25331000000-1.40000237.636276QAM25625
26339000000-1.00000038.605377QAM25626
27347000000-1.20000137.355988QAM25627
28355000000-1.40000238.605377QAM25628
29363000000-1.09999837.636276QAM25629
30371000000-1.20000137.636276QAM25630
31379000000-1.70000137.636276QAM25631



3.0 Downstream channels

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

1Locked38.98326100
2Locked38.60537700
3Locked38.60537700
4Locked38.60537700
5Locked38.60537700
6Locked38.60537700
7Locked38.60537700
8Locked38.98326100
9Locked38.60537700
10Locked38.60537700
11Locked38.60537700
12Locked38.60537700
13Locked38.60537700
14Locked38.60537700
15Locked37.63627600
16Locked37.63627600
17Locked37.63627600
18Locked37.63627600
19Locked38.60537700
20Locked37.63627600
21Locked37.63627600
22Locked37.35598800
23Locked37.63627600
24Locked37.63627600
25Locked37.63627600
26Locked38.60537700
27Locked37.35598800
28Locked38.60537700
29Locked37.63627600
30Locked37.63627600
31Locked37.63627600



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


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked400.0465798520
0 Kudos
Reply
xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
175 Views
Message 5 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

3.0 Upstream channels

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

13940000032.0205995120 KSym/sec64QAM12
24620000032.5205995120 KSym/sec64QAM11
35370000032.5205995120 KSym/sec64QAM10
46030000032.5205995120 KSym/sec64QAM9



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0020
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000
0 Kudos
Reply
xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
174 Views
Message 6 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

General Configuration

Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
oA,.iyewrkldJKDHSUBsgvca69834



Primary Downstream Service Flow

SFID
14977
Max Traffic Rate
1200000450
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow

SFID
4498
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
16320
Scheduling Type
bestEffort
0 Kudos
Reply
xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
173 Views
Message 7 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

Network Log

Time Priority Description

Fri Jun 11 15:22:00 20215DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 17:42:08 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jun 13 20:46:05 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun Jun 13 20:46:05 20216DHCP 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 Jun 15 02:29:03 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jun 16 18:04:18 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Jun 16 18:04:18 20216DHCP 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 Jun 17 07:17:20 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
lotharmat
  • 2.54K
  • 188
  • 462
Trouble shooter
168 Views
Message 8 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

Your upstream power looks to be too low and your QAM for the DOCSIS3.1 should be 4096 not 1024.

Vm ned to take a look at it and possibly send a tech out to heck things over!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

xoxShwingxox
  • 8
  • 0
  • 0
Tuning in
163 Views
Message 9 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

Many thanks for your feedback 👍

Will someone from VM pick up on this thread?

0 Kudos
Reply
lotharmat
  • 2.54K
  • 188
  • 462
Trouble shooter
153 Views
Message 10 of 12
Flag for a moderator

Re: Packet Loss Is Becoming A 'Thing'

Aye - can take a day or so though!

May be worth checking the fault line if you haven't already.

0800 561 0061 - usually more up-to-date than the web service and more granular!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

0 Kudos
Reply