Menu
Reply
halifax1983
  • 75
  • 1
  • 3
On our wavelength
735 Views
Message 1 of 12
Flag for a moderator

Please check these stats. Getting terrible lag

Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz)
331000000
Locked
Ranged Upstream Channel (Hz)
53700004
Locked
Provisioning State
Online
0 Kudos
Reply
halifax1983
  • 75
  • 1
  • 3
On our wavelength
734 Views
Message 2 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

Downstream bonded channels

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

13310000002.438256 qam25
22030000003.538256 qam9
32110000003.438256 qam10
42190000003.438256 qam11
52270000003.238256 qam12
62350000003.238256 qam13
7243000000338256 qam14
8251000000338256 qam15
92590000002.938256 qam16
102670000002.938256 qam17
112750000002.538256 qam18
122830000002.538256 qam19
132910000002.538256 qam20
142990000002.738256 qam21
153070000002.538256 qam22
163150000002.438256 qam23
173230000002.438256 qam24
183390000002.538256 qam26
193470000002.538256 qam27
203550000002.438256 qam28
213630000002.538256 qam29
223710000002.438256 qam30
233790000002.538256 qam31
243870000002.538256 qam32



Downstream bonded channels

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

1Locked38.6376161
2Locked38.92345179
3Locked38.62833175
4Locked38.912310421
5Locked38.921765892
6Locked38.6447201
7Locked38.91173182
8Locked38.62037184
9Locked38.9780204
10Locked38.91181150
11Locked38.9394110
12Locked38.6474104
13Locked38.6761122
14Locked38.984696
15Locked38.991198
16Locked38.62712117
17Locked38.91262154
18Locked38.6354143
19Locked38.6372103
20Locked38.939983
21Locked38.9378113
22Locked38.638964
23Locked38.9345113
24Locked38.635790
0 Kudos
Reply
halifax1983
  • 75
  • 1
  • 3
On our wavelength
733 Views
Message 3 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

Upstream bonded channels

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

15370000438512064 qam10
23940000038512064 qam12
34619997638512064 qam11
46029999138512064 qam9



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0010
4ATDMA0000
0 Kudos
Reply
halifax1983
  • 75
  • 1
  • 3
On our wavelength
732 Views
Message 4 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
873254k;fg87dsfd;kfoA,.iy



Primary Downstream Service Flow

SFID15392
Max Traffic Rate575000000
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID15391
Max Traffic Rate38520000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort
0 Kudos
Reply
halifax1983
  • 75
  • 1
  • 3
On our wavelength
727 Views
Message 5 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

Network Log

Time Priority Description

11/11/2021 00:28:46noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/11/2021 00:28:46ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/11/2021 21:16:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/11/2021 14:54:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/11/2021 19:20:10noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/11/2021 14:35:40noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/11/2021 14:35:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/11/2021 05:49:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/10/2021 13:01:35noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/10/2021 13:01:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-
0 Kudos
Reply
halifax1983
  • 75
  • 1
  • 3
On our wavelength
726 Views
Message 6 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

https://www.thinkbroadband.com/broadband/monitoring/quality/share/4be84993a42db8ea66c54bac4dd5c2f6bbf13538
0 Kudos
Reply
Adduxi
  • 6.09K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
711 Views
Message 7 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

BQM is pretty much perfect, however too many PostRS errors.   Reboot the Hub to clear the counters and keep an eye on those.  If they increase quickly there is a fault and will need VMO2 to fix.

How are you connecting by the way, as a cabled connection is preferred over wifi to reduce latency.

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
halifax1983
  • 75
  • 1
  • 3
On our wavelength
698 Views
Message 8 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

Thank you for the reply.

Ethernet cable. I’ll reboot and report back later

0 Kudos
Reply
Akua_A
  • 4.09K
  • 105
  • 283
Forum Team
Forum Team
602 Views
Message 9 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

Hi @halifax1983,

Welcome back to our community forums and thank you for bringing this lag issue to our attention. 

How has service been since the reboot? Is the issue still ongoing?

Thanks,

 

Akua_A
Forum Team



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


0 Kudos
Reply
Andrew-G
  • 10.42K
  • 1.66K
  • 4.76K
Alessandro Volta
598 Views
Message 10 of 12
Flag for a moderator

Re: Please check these stats. Getting terrible lag

The downstream post-RS errors indicate a noise ingress problem across all channels, but particularly around 219 and 227 MHz.  I'd hazard a guess that the particular noise is probably due to DAB broadcasts on VHF band III, in particular sub-bands 11B and 12C, although internal signal reflections due to cable damage are a possibility.  Others may have better knowledge of the specific sources of noise in VHF Band III rather than my assumption of DAB, but regardless of source, there's a noise issue on those frequencies.

Whether noise ingress or reflections, they both suggest either a damaged coax cable (or an unsuitable self-supplied one, eg to move the hub), a poorly made connector, or an uncapped coax port, any of which could be on the same segment you're connected to.   When I say "same segment as you", it means that the source of the noise could be on a neighbour's connection, not necessarily yours, but in that case it's VM's problem to trace and resolve it. 

What you can do about this is limited, but includes the following:

1)  Check that all VM related coaxial cables are as supplied by the company, have the connectors properly made and tightened.  So undo each connector, give it a wipe on a tee shirt, damp rag, kitchen paper, reconnect, and do up any securing nuts finger tight.

2)  If you're able and willing, do the same in any brown plastic wall box on the outside of the property.  These joints tend to be tighter, and you'd probably need a small spanner or similar to undo and redo them, along with a screwdriver to get into the box.  If you're not confident to do this, don't attempt it. 

3) If there's any unused VM coax ports (eg from a now unused TV box, or previous hub location) they need any ports to have proper caps fitted.  Those are usually F-type male terminator caps that you can get for a few quid in any hardware shop.

4) Check for damage on the coax cable such as crushing, kinking, staples or cable clips that have gone through it.

When you've made those checks, turn the hub off and then on again - that will clear the error counters, so you'll soon see if the post-RS counts start rising (pre-RS can usually be ignored).  If after this the problems persist and post-RS counts are rising, then it's VM's problem to resolve, and you can ignore any daft advice about "wifi devices too close to the hub", that has no bearing whatsoever on the problems the hub's status data is indicating.