Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Virgin Media Community
- Broadband
- Gaming Support
- Constant packet burst issue
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Constant packet burst issue
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 24-08-2023 01:12
I have been dealing with a constant packet burst issue while gaming this happens mainly in Call of Duty titles but I have also experienced it in another title as well.
I have set up a BCM here:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/c5133010dcb1272541ca25368cb69fb45d...
Ill also post my router logs below:
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
| 1 | 306000000 | 12.8 | 43 | QAM 256 | 22 |
| 2 | 138000000 | 13.5 | 42 | QAM 256 | 1 |
| 3 | 146000000 | 13.7 | 42 | QAM 256 | 2 |
| 4 | 154000000 | 13.6 | 42 | QAM 256 | 3 |
| 5 | 162000000 | 13.4 | 42 | QAM 256 | 4 |
| 6 | 170000000 | 13.4 | 42 | QAM 256 | 5 |
| 7 | 178000000 | 13.5 | 42 | QAM 256 | 6 |
| 8 | 186000000 | 13.5 | 42 | QAM 256 | 7 |
| 9 | 194000000 | 13.7 | 42 | QAM 256 | 8 |
| 10 | 202000000 | 13.4 | 42 | QAM 256 | 9 |
| 11 | 210000000 | 13.6 | 42 | QAM 256 | 10 |
| 12 | 218000000 | 13.4 | 42 | QAM 256 | 11 |
| 13 | 226000000 | 13.4 | 42 | QAM 256 | 12 |
| 14 | 234000000 | 13.3 | 42 | QAM 256 | 13 |
| 15 | 242000000 | 13.2 | 42 | QAM 256 | 14 |
| 16 | 250000000 | 13.1 | 42 | QAM 256 | 15 |
| 17 | 258000000 | 12.9 | 42 | QAM 256 | 16 |
| 18 | 266000000 | 13.1 | 42 | QAM 256 | 17 |
| 19 | 274000000 | 12.8 | 42 | QAM 256 | 18 |
| 20 | 282000000 | 12.9 | 42 | QAM 256 | 19 |
| 21 | 290000000 | 13 | 42 | QAM 256 | 20 |
| 22 | 298000000 | 12.8 | 42 | QAM 256 | 21 |
| 23 | 314000000 | 12.6 | 42 | QAM 256 | 23 |
| 24 | 322000000 | 12.5 | 42 | QAM 256 | 24 |
| 25 | 330000000 | 12.5 | 43 | QAM 256 | 25 |
| 26 | 338000000 | 12.3 | 42 | QAM 256 | 26 |
| 27 | 346000000 | 12.4 | 42 | QAM 256 | 27 |
| 28 | 354000000 | 12.1 | 42 | QAM 256 | 28 |
| 29 | 362000000 | 12.2 | 42 | QAM 256 | 29 |
| 30 | 370000000 | 12.1 | 42 | QAM 256 | 30 |
| 31 | 378000000 | 11.9 | 42 | QAM 256 | 31 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
| 1 | Locked | 43 | 19 | 0 |
| 2 | Locked | 42 | 57 | 0 |
| 3 | Locked | 42 | 42 | 0 |
| 4 | Locked | 42 | 38 | 0 |
| 5 | Locked | 42 | 15 | 0 |
| 6 | Locked | 42 | 1 | 0 |
| 7 | Locked | 42 | 1 | 0 |
| 8 | Locked | 42 | 1 | 0 |
| 9 | Locked | 42 | 3 | 0 |
| 10 | Locked | 42 | 6 | 0 |
| 11 | Locked | 42 | 9 | 0 |
| 12 | Locked | 42 | 9 | 0 |
| 13 | Locked | 42 | 9 | 0 |
| 14 | Locked | 42 | 8 | 0 |
| 15 | Locked | 42 | 13 | 0 |
| 16 | Locked | 42 | 11 | 0 |
| 17 | Locked | 42 | 11 | 0 |
| 18 | Locked | 42 | 7 | 0 |
| 19 | Locked | 42 | 6 | 0 |
| 20 | Locked | 42 | 9 | 0 |
| 21 | Locked | 42 | 11 | 0 |
| 22 | Locked | 42 | 11 | 0 |
| 23 | Locked | 42 | 19 | 0 |
| 24 | Locked | 42 | 15 | 0 |
| 25 | Locked | 43 | 16 | 0 |
| 26 | Locked | 42 | 21 | 0 |
| 27 | Locked | 42 | 21 | 0 |
| 28 | Locked | 42 | 17 | 0 |
| 29 | Locked | 42 | 27 | 0 |
| 30 | Locked | 42 | 22 | 0 |
| 31 | Locked | 42 | 32 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
| 0 | 49600000 | 34.3 | 5120 | QAM 64 | 1 |
| 1 | 43100000 | 34 | 5120 | QAM 64 | 2 |
| 2 | 36600000 | 33.8 | 5120 | QAM 64 | 3 |
| 3 | 30100000 | 33.3 | 5120 | QAM 64 | 4 |
| 4 | 23600000 | 33 | 5120 | QAM 64 | 5 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
| 0 | ATDMA | 0 | 1 | 0 | 0 |
| 1 | ATDMA | 0 | 1 | 0 | 0 |
| 2 | ATDMA | 0 | 1 | 0 | 0 |
| 3 | ATDMA | 0 | 1 | 1 | 1 |
| 4 | ATDMA | 0 | 1 | 0 | 0 |
General Configuration
Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file
| Allowed |
| 3 |
| Enabled |
| 3.1 |
| cmreg-vmdg660-bbt076+voc-b.cm |
7 REPLIES 7
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 24-08-2023 01:12
Primary Downstream Service Flow
SFIDMax Traffic RateMax Traffic BurstMin Traffic RateSFIDMax Traffic RateMax Traffic BurstMin Traffic Rate
| 17956 |
| 1230000450 bps |
| 42600bytes |
| 0 bps |
| 17958 |
| 128000 bps |
| 3044bytes |
| 0 bps |
Primary Upstream Service Flow
SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling TypeSFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type
| 17955 |
| 110000274 bps |
| 42600bytes |
| 0 bps |
| 42600bytes |
| Best Effort |
| 17957 |
| 128000 bps |
| 3044bytes |
| 0 bps |
| 1522bytes |
| Best Effort |
Network Log
Time Priority Description
| 22-08-2023 17:59:30 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 22-08-2023 17:59:30 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 22-08-2023 17:58:22 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 22-08-2023 13:10:21 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 23:56:30 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:52:42 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:48:17 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:48:13 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:43:10 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:43:04 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:38:01 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:37:51 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 22:32:48 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 21:48:53 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 17:33:39 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 17:04:26 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 16:57:31 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 16:56:58 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 16:29:52 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 13:18:25 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 11:10:48 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 07:59:22 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 06:55:34 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 04:47:56 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 03:44:08 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 21-08-2023 02:40:19 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 19-08-2023 01:10:18 | error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 18-08-2023 10:51:46 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 18-08-2023 10:43:40 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 18-08-2023 10:38:37 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 18-08-2023 10:36:36 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
| 18-08-2023 10:31:33 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thanks in advance for looking
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 24-08-2023 10:06
Do the these packet burst happen to when BQM shows a spike?
Run a ping -t 194.168.4.100 and check how stable that is vs BQM
---------------------------------------------------------------
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
24-08-2023 20:49 - edited 24-08-2023 21:43
When the BQM shows a spike is actually a time when my router starts flashing a green light, jjust before 1am and around 9am.
The packet bursting is constant, any time of day. Might be worse during peak hours.
Pinging 194.168.4.100 with 32 bytes of data:
Reply from 194.168.4.100: bytes=32 time=18ms TTL=61
Reply from 194.168.4.100: bytes=32 time=13ms TTL=61
Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=12ms TTL=61
Reply from 194.168.4.100: bytes=32 time=16ms TTL=61
Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
Reply from 194.168.4.100: bytes=32 time=18ms TTL=61
Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=14ms TTL=61
Reply from 194.168.4.100: bytes=32 time=21ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
Reply from 194.168.4.100: bytes=32 time=14ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
Reply from 194.168.4.100: bytes=32 time=7ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=10ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=16ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=14ms TTL=61
Reply from 194.168.4.100: bytes=32 time=5ms TTL=61
Reply from 194.168.4.100: bytes=32 time=13ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Reply from 194.168.4.100: bytes=32 time=9ms TTL=61
Reply from 194.168.4.100: bytes=32 time=11ms TTL=61
Reply from 194.168.4.100: bytes=32 time=12ms TTL=61
Reply from 194.168.4.100: bytes=32 time=8ms TTL=61
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 25-08-2023 12:52
Your Downstream power is too high and the Upstream is too low. Also your Upstream profile is "flapping" around too much, You need an engineer to sort that out.
The DS range should be -6 to +10 and US 34 to 51, just in case you are interested. 😉
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
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 26-08-2023 19:08
thanks, thats very insightful. Seems my levels are out of whack, and those ranges are for gig1?
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
27-08-2023 10:23 - edited 27-08-2023 10:26
The ranges are for all tiers on VM co-ax Hubs. I don't think they will apply to the newer XGS-PON fibre 5x Hub, as it's a completely different infrastructure.
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
Options
- Mark as New
- Bookmark this message
- Subscribe to this message
- Mute
- Subscribe to this message's RSS feed
- Highlight this message
- Print this message
- Flag for a moderator
on 29-08-2023 10:40
Hey SClark90,
Welcome to the community and thanks for taking the time to post here on the forums.
I’m sorry to hear of the issues that you’re having with your connection at the moment, looking at the issues that you're having, you will need a technician visit to get them resolved.
I can arrange the appointment from here but would need to confirm a few details via a private message, that I will drop over in a moment. Please look out for the private message and we can get started.
Kind Regards,
Steven_L
