Menu
Reply
Jonnyboybick
  • 116
  • 0
  • 5
On our wavelength
911 Views
Message 1 of 41
Flag for a moderator

Hub 5 Packet loss and latency

Hi there,

I used to have a hub 3 that would regularly disconnect and was impressed that for the first week my new hub 5 would be online 24/7. It was a miracle.

Now about 2 weeks later I am plagued with packet loss and random high latency every few seconds, see image attached.

I had a technician come round who had no idea how to test my internet other than speedtest on his phone. It was honestly embarassing, he didn't know what BQM was or even what I was doing when pinging google.

Please help.

Thanks,


Jon



My BQM 

Tags (2)
0 Kudos
Reply
Jonnyboybick
  • 116
  • 0
  • 5
On our wavelength
910 Views
Message 2 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Untitled.png

 

You can see my BQM in signature.



My BQM 

0 Kudos
Reply
legacy1
  • 18.22K
  • 761
  • 1.9K
Alessandro Volta
887 Views
Message 3 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

A bit of line noise by the looks of it.

---------------------------------------------------------------
0 Kudos
Reply
carl_pearce
  • 988
  • 59
  • 222
Well-informed
880 Views
Message 4 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Could you post your HUB stats?

0 Kudos
Reply
Jonnyboybick
  • 116
  • 0
  • 5
On our wavelength
833 Views
Message 5 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Thanks for the reply, unfortunately when I try and access my hub stats I get the below error:

 

Untitled.png



My BQM 

0 Kudos
Reply
Jonnyboybick
  • 116
  • 0
  • 5
On our wavelength
809 Views
Message 6 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Upstream I can view:

 

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

16030000031.35120QAM 641
25370000031.35120QAM 642
34620000030.85120QAM 643
43940000030.35120QAM 644

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed
1
Enabled
3.1
3254k;fg87dsfd;kfoA,.iyew

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

13287
230000061 bps
42600 bytes
0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

12801
22000061 bps
42600 bytes
0 bps
42600 bytes

Best Effort

 

 

 

Time Priority Description

19-12-2021 18:49:08noticeCM-STATUS message sent. Event Type Code: 5; Chan ID: 1 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1
19-12-2021 18:48:54noticeCM-STATUS message sent. Event Type Code: 4; Chan ID: 1 3 4 5 6 7 8 9 10 11 12 13 14 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;
19-12-2021 18:48:35warningDBC-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;
19-12-2021 18:48:31criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-12-2021 18:48:30warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-12-2021 18:48:30warningDBC-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;
19-12-2021 18:48:24criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-12-2021 03:07:33noticeCM-STATUS message sent. Event Type Code: 5; 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;
19-12-2021 03:07:10noticeREGISTRATION COMPLETE - Waiting for Operational status
19-12-2021 03:07:04warningREG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-12-2021 03:06:59noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-12-2021 03:06:55warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
19-12-2021 03:06:53noticeHonoring MDD; IP provisioning mode = IPv4
19-12-2021 03:06:44criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-12-2021 12:50:26criticalReceived 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;
16-12-2021 12:50:06criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-12-2021 12:50:06criticalReceived 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;
16-12-2021 12:49:46criticalReceived 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;
16-12-2021 12:49:46criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
16-12-2021 12:49:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;


My BQM 

0 Kudos
Reply
carl_pearce
  • 988
  • 59
  • 222
Well-informed
806 Views
Message 7 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Upstream power levels look low, unless you are in a FTTP area?

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

16030000031.35120QAM 641
25370000031.35120QAM 642
34620000030.85120QAM 643
43940000030.35120QAM 644
0 Kudos
Reply
Jonnyboybick
  • 116
  • 0
  • 5
On our wavelength
751 Views
Message 8 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Thanks for the reply. I think I'm in an FTTP area. I'm more concerned with not being able to access my downstream logs and have seen a couple of other posts about downstream issues with the hub 5.

I did ask the engineer to check my power levels when he came but he never did.



My BQM 

0 Kudos
Reply
Jonnyboybick
  • 116
  • 0
  • 5
On our wavelength
737 Views
Message 9 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

Can someone kindly review my message and book me in a technician as if I phone again the technician is going to be the same guy who uses his mobile to speedtest and confirm that my internet is ok.

Thanks



My BQM 

0 Kudos
Reply
Tudor
  • 10.84K
  • 840
  • 2.14K
Very Insightful Person
Very Insightful Person
700 Views
Message 10 of 41
Flag for a moderator

Re: Hub 5 Packet loss and latency

 If you are not a FTTP customer then those upstream power levels are too low. You can tell if you are FTTP customer if you have a VM power plug that takes a coax cable usually going to a white box. I do not mean a power plug for your VM hub or TV box.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos
Reply