Menu
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
156 Views
Message 1 of 14
Flag for a moderator

Messy connection - latency and packet loss (Hub 4)

I'm hoping the good folk on here will be able to help. I'm having some problems with the stability of my broadband connection, affecting wired and wireless connections. All standard checks in terms of cables being in securely etc have been done.

I've had a BQM running for over a month now and it's showing some problematic trends:

BQM Live Graph 

I don't honestly understand the causes of the spikes in the graphs, but I've become somewhat of an expert in understanding the effects of packet loss!

As you can see from the BQM graphs, the trend is for a few days of fairly clear connection (albeit high latency) before the packet loss starts to build and I inevitably reboot the Hub. Sometimes that can clear it for a few days, sometimes just a few hours (see Sunday 25th and Monday 26th).

As I note in the title, we're on the Hub 4 having had a free upgrade about 5 weeks ago now. Is the supply of the Hub 4 an indication that the network in the area has capacity issues?

I'd love to know what's going on with my connection as it's affecting my work - MS Teams calls with 20% packet loss are not fun.

0 Kudos
Reply
Highlighted
  • 24.56K
  • 1.41K
  • 3.12K
Alessandro Volta
146 Views
Message 2 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Post the network, upstream and downstream logs from the hubs admin pages please

*****
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
Highlighted
  • 9
  • 0
  • 0
Tuning in
142 Views
Message 3 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Downstream:

3.0 Downstream channels

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

11387500004.40000240.946209QAM2561
21467500004.09999840.366287QAM2562
31547500003.90000240.366287QAM2563
41627500003.40000240.366287QAM2564
51707500003.09999838.983261QAM2565
61787500002.59999838.983261QAM2566
71867500002.70000138.983261QAM2567
81947500002.79999938.605377QAM2568
92027500003.00000038.605377QAM2569
102107500003.09999838.983261QAM25610
112187500003.20000140.366287QAM25611
122267500003.29999940.366287QAM25612
132347500003.09999838.983261QAM25613
142427500003.09999840.366287QAM25614
152507500003.29999940.366287QAM25615
162587500003.09999840.366287QAM25616
172667500003.20000140.366287QAM25617
182747500003.59999840.366287QAM25618
192827500003.70000140.366287QAM25619
202907500003.50000040.366287QAM25620
212987500003.00000040.366287QAM25621
223067500002.40000240.366287QAM25622
233147500002.00000038.983261QAM25623
243227500001.70000138.983261QAM25624
253307500001.70000138.605377QAM25625
263707500001.50000040.366287QAM25626
273787500001.40000238.605377QAM25627
283867500001.20000138.983261QAM25628
293947500001.09999838.605377QAM25629
304027500001.20000138.605377QAM25630
314107500001.29999938.605377QAM25631



3.0 Downstream channels

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

1Locked000
2Locked13349599800
3Locked354818609000
4Locked11957739200
5Locked13238179400
6Locked13321339100
7Locked11373809300
8Locked11152846500
9Locked12366849200
10Locked12367620300
11Locked11124127100
12Locked11009592300
13Locked12300659300
14Locked12275098800
15Locked3753198800
16Locked3778354300
17Locked4021304100
18Locked4021525100
19Locked3766626400
20Locked3811417400
21Locked3945165300
22Locked3949336000
23Locked3768926600
24Locked350434505800
25Locked5689885700
26Locked5667452100
27Locked5690997300
28Locked5526741000
29Locked5650497700
30Locked5601537400
31Locked285966181300



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)
159Locked 0.214887523060
0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
141 Views
Message 4 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Upstream:

3.0 Upstream channels

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

15370000047.0205995120 KSym/sec64QAM10
23260000044.7705995120 KSym/sec64QAM13
33940000045.2705995120 KSym/sec64QAM12
44620000045.7705995120 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
Highlighted
  • 9
  • 0
  • 0
Tuning in
134 Views
Message 5 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Network Log:

Network Log

Time Priority Description

Thu 15/10/2020 06:48:143SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:48:246CM-STATUS message sent. Event Type Code: 2; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:48:253SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:48:286CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:51:115Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:51:186CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:51:195Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:51:356CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:59:375Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:59:386CM-STATUS message sent. Event Type Code: 5; Chan ID: 26; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:59:455Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:59:516CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:59:525Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 06:59:566CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:01:305Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:01:466CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:03:135Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:03:166CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:03:285Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:03:356CM-STATUS message sent. Event Type Code: 4; Chan ID: 24; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:03:395Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:03:436CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:04:055Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 07:04:066CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 15/10/2020 21:03:163No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:13:346CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:21:565MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:35:005Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:35:033SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:37:003Received 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;
Thu 01/01/1970 00:05:374Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:43:475MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 08:43:513No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 09:32:386CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 11:20:535Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 11:20:553SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 11:22:533Received 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;
Fri 16/10/2020 11:24:243No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 11:24:525MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 11:24:553No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 16/10/2020 11:26:116CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 17/10/2020 10:22:523SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 17/10/2020 10:23:006CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 17/10/2020 11:18:505MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 20/10/2020 23:18:364DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 20/10/2020 23:18:366DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 22/10/2020 04:55:383No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 24/10/2020 11:18:374DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 24/10/2020 11:18:376DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 25/10/2020 18:23:055MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
0 Kudos
Reply
Highlighted
  • 24.56K
  • 1.41K
  • 3.12K
Alessandro Volta
126 Views
Message 6 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Your levels etc. all look fine.

Have you checked to make sure all the coax cables are seated correctly and are nice and tight?

*****
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
Highlighted
  • 9
  • 0
  • 0
Tuning in
121 Views
Message 7 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Yes, a few times. All cables are in properly and finger tight

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
110 Views
Message 8 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

In relation to the BQM, I hadn't realised you wouldn't be able to see the whole BQM history as I can, so here are links for 25th and 26th Oct which are indicative of the problem:

BQM 25th October 

BQM 26th October 

0 Kudos
Reply
Highlighted
  • 9
  • 0
  • 0
Tuning in
67 Views
Message 9 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Compared to 21st October which shows no packet loss:

BQM 21st October 

Any thoughts?

0 Kudos
Reply
Highlighted
  • 24.56K
  • 1.41K
  • 3.12K
Alessandro Volta
60 Views
Message 10 of 14
Flag for a moderator

Re: Messy connection - latency and packet loss (Hub 4)

Are you running in router mode with the hub?

Apparently it’s one of the “quirks” of the Hub4 being up for so long, as myself and many others have experienced the same thing. 


*****
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