Menu
Reply
helloitsdec
  • 4
  • 0
  • 0
Tuning in
568 Views
Message 1 of 9
Flag for a moderator

Packet burst/loss and complete loss of connection

Hello,

I keep having these spells of patchy connection with disconnects, packet burst and a complete loss of connection. I started researching the problem last night when I kept getting disconnected from WarZone and came across these forums. I checked the service status site and ran tests to my equipment but VM didn't seem to think anything was wrong. I gathered from other threads that I need to setup a BQM and post some info from the router so please find that info below, if there is anything else please let me know.

I appreciate any help with this.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/7f432159926366cad4907c3284c6b09440...

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
253307500002.09999840.946209QAM25625
81947500002.00000040.946209QAM2568
92027500001.90000240.366287QAM2569
102107500001.90000240.366287QAM25610
112187500002.09999840.366287QAM25611
122267500002.20000140.946209QAM25612
132347500002.20000140.366287QAM25613
142427500002.20000140.366287QAM25614
152507500002.40000240.946209QAM25615
162587500002.70000140.366287QAM25616
172667500002.90000240.946209QAM25617
182747500003.29999940.946209QAM25618
192827500003.00000040.946209QAM25619
202907500002.70000140.946209QAM25620
212987500002.40000240.946209QAM25621
223067500002.50000040.366287QAM25622
233147500002.50000040.946209QAM25623
243227500002.50000040.366287QAM25624
263387500002.09999840.366287QAM25626
273467500002.00000040.366287QAM25627
283547500001.90000240.946209QAM25628
293627500001.70000140.366287QAM25629
303707500001.59999840.366287QAM25630
313787500001.59999840.946209QAM25631
323867500001.59999840.366287QAM25632
333947500001.59999840.366287QAM25633
344027500001.70000140.946209QAM25634
354107500002.00000040.366287QAM25635
364187500002.20000140.946209QAM25636
374267500002.00000040.366287QAM25637
384347500002.50000040.366287QAM25638
0 Kudos
Reply
helloitsdec
  • 4
  • 0
  • 0
Tuning in
567 Views
Message 2 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

3.0 Downstream channels

Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25Locked40.94620900
8Locked40.94620900
9Locked40.36628700
10Locked40.36628700
11Locked40.36628700
12Locked40.94620900
13Locked40.36628700
14Locked40.36628700
15Locked40.94620900
16Locked40.36628700
17Locked40.94620900
18Locked40.94620900
19Locked40.94620900
20Locked40.94620900
21Locked40.94620900
22Locked40.36628700
23Locked40.94620900
24Locked40.36628700
26Locked40.36628700
27Locked40.36628700
28Locked40.94620900
29Locked40.36628700
30Locked40.36628700
31Locked40.94620900
32Locked40.36628710
33Locked40.36628700
34Locked40.94620900
35Locked40.36628700
36Locked40.94620900
37Locked40.36628700
38Locked40.36628710

3.1 Downstream channels

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

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked420.0364876630

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13260000049.7705995120 KSym/sec64QAM13
23940000049.2705995120 KSym/sec64QAM12
34620000049.7705995120 KSym/sec64QAM11
45370000050.2705995120 KSym/sec64QAM10

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_STDMA0000
2US_TYPE_STDMA002819
3US_TYPE_STDMA001519
4US_TYPE_STDMA001818

Network Log

Time Priority DescriptionThis appears to now be blank but I'm sure had stuff here when I was poking around yesterday?
 
Thank you,
0 Kudos
Reply
Adduxi
  • 6.1K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
507 Views
Message 3 of 9
Flag for a moderator
Helpful Answer

Re: Packet burst/loss and complete loss of connection

Your BQM is fine, as are your stats, apart from the Upstream being near the upper limit of 51.

However there are far too many T3's and this may point to something amiss on the Upstream channels.  VM would need to check this out.

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

John_GS
  • 14.43K
  • 737
  • 1.34K
Forum Team
Forum Team
470 Views
Message 4 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

Hi helloitsdec

Thanks for posting and welcome to the community. Sorry to hear of the broadband issues. I've not been able to locate your account from the forum information provided, so I shall pop you a PM now to get some details and assist further.

Best,

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill

John_GS
  • 14.43K
  • 737
  • 1.34K
Forum Team
Forum Team
452 Views
Message 5 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

Hi @helloitsdec

Thanks for providing me those details. I've checked on the system and no issues are showing. No outages. All levels are in spec and no issues with the SNR (signal to noise ratio) or congestion. 

Can you repost your logs for us please?

Kind regards,

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill

nothappywithu
  • 52
  • 0
  • 6
On our wavelength
448 Views
Message 6 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

theres that script virgin media claim they do not read from

0 Kudos
Reply
helloitsdec
  • 4
  • 0
  • 0
Tuning in
433 Views
Message 7 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

Hello,

Things have certainly improved as can be seen on the live BQM. When I made the thread however it looked like this;

https://www.thinkbroadband.com/broadband/monitoring/quality/share/305d1516a7a90a1af7bea1b0d2f509dfb81404ef-27-12-2021

As long as nothing appears to be off at my end I don't suppose there is much else I can do.

3.0 Downstream channels

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

253307500002.29999940.946209QAM25625
81947500002.40000240.946209QAM2568
92027500002.40000240.946209QAM2569
102107500002.40000240.366287QAM25610
112187500002.50000040.946209QAM25611
122267500002.59999840.946209QAM25612
132347500002.59999840.946209QAM25613
142427500002.70000140.366287QAM25614
152507500002.79999940.946209QAM25615
162587500003.09999840.946209QAM25616
172667500003.29999940.366287QAM25617
182747500003.70000140.946209QAM25618
192827500003.40000240.366287QAM25619
202907500003.09999840.946209QAM25620
212987500002.70000140.946209QAM25621
223067500002.79999940.946209QAM25622
233147500002.79999940.946209QAM25623
243227500002.70000140.366287QAM25624
263387500002.29999940.946209QAM25626
273467500002.20000140.366287QAM25627
283547500002.09999840.946209QAM25628
293627500001.90000240.946209QAM25629
303707500001.70000140.946209QAM25630
313787500001.70000140.366287QAM25631
11387500003.50000040.946209QAM2561
21467500003.29999940.946209QAM2562
31547500003.00000040.946209QAM2563
41627500002.70000140.946209QAM2564
51707500002.50000040.946209QAM2565
61787500002.40000240.366287QAM2566
71867500002.40000240.366287QAM2567



3.0 Downstream channels

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

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



3.1 Downstream channels

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


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
159Locked42-0.29181995920
0 Kudos
Reply
helloitsdec
  • 4
  • 0
  • 0
Tuning in
431 Views
Message 8 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

3.0 Upstream channels

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

13260000049.0205995120 KSym/sec64QAM13
23940000049.2705995120 KSym/sec64QAM12
34620000049.2705995120 KSym/sec64QAM11
45370000049.2705995120 KSym/sec64QAM10



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0010
4US_TYPE_STDMA0000

 

Network Log

Time Priority Description

Mon Dec 27 08:57:04 20213Received 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;
Mon Dec 27 08:57:05 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:57:14 20213Received 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;
Mon Dec 27 08:57:24 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:57:34 20213Received 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;
Mon Dec 27 08:58:04 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:58:24 20213Received 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;
Mon Dec 27 08:58:24 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:58:34 20213Received 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;
Mon Dec 27 08:58:44 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:58:54 20213Received 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;
Mon Dec 27 08:59:01 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;
Mon Dec 27 08:59:03 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:59:03 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:59:04 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:59:04 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:59:06 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:59:06 20215TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 08:59:36 20213Received 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;
Mon Dec 27 09:00:00 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:00:00 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:00:20 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:00:20 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:00:25 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:02:40 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:02:40 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:03:04 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:03:59 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:04:00 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:04:24 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:05:19 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:05:19 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:05:44 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:06:39 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:06:39 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:06:59 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:06:59 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:07:04 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:07:59 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:07:59 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:08:19 20213Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:08:19 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:08:24 20213Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon Dec 27 09:21:43 20213Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Adduxi
  • 6.1K
  • 512
  • 1.57K
Very Insightful Person
Very Insightful Person
414 Views
Message 9 of 9
Flag for a moderator

Re: Packet burst/loss and complete loss of connection

Yes the live BQM is showing a fairly decent connection now, and your stats are looking good.  Not much else to say at this time.

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