Menu
Reply
  • 13
  • 0
  • 0
Mavo
Tuning in
344 Views
Message 1 of 8
Flag for a moderator

Insane Packet loss

Been noticed a lot of lag spikes while listening to music / gaming.

Upon checking with the BQM I set up last time I was having issues, I saw this and I am rather alarmed!

https://www.thinkbroadband.com/broadband/monitoring/quality/share/3a76172f334b3d07b681ae40e4ab27b4da... 

0 Kudos
Reply
  • 12.63K
  • 483
  • 1.13K
legacy1
Alessandro Volta
337 Views
Message 2 of 8
Flag for a moderator

Re: Insane Packet loss

The hub 3 blocks BQM at times because it thinks its a flood you can try and disable flood detection in the hub to see if that helps or use modem mode and get your own router with 1Gb ports.

Aside from that when BQM is working you still have packet loss happening so can you post your downstream and upstream with T# timeout counters.

  • 13
  • 0
  • 0
Mavo
Tuning in
333 Views
Message 3 of 8
Flag for a moderator

Re: Insane Packet loss

Network Log

Time Priority Description

31/05/2019 11:55:41Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 11:56:19criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 11:56:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:49:22criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:49:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:50:22criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:50:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:50:42criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:50:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:51:2criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:51:2criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:51:22criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 19:51:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 20:19:53Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 21:03:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2019 22:14:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2019 09:02:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/06/2019 09:33:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2019 11:44:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2019 12:06:18Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels

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

1299000000-12.535256 qam21
2139000000-5.737256 qam1
3147000000-638256 qam2
4155000000-6.237256 qam3
5163000000-6.737256 qam4
6171000000-7.437256 qam5
7179000000-837256 qam6
8187000000-937256 qam7
9195000000-1037256 qam8
10203000000-10.736256 qam9
11211000000-11.936256 qam10
12219000000-12.536256 qam11
13227000000-12.935256 qam12
14235000000-13.435256 qam13
15243000000-13.835256 qam14
16251000000-13.735256 qam15
17259000000-13.835256 qam16
18267000000-13.335256 qam17
19275000000-12.735256 qam18
20283000000-12.236256 qam19
21291000000-12.236256 qam20
22307000000-12.536256 qam22
23315000000-12.535256 qam23
24323000000-12.535256 qam24

 

0 Kudos
Reply
  • 13
  • 0
  • 0
Mavo
Tuning in
332 Views
Message 4 of 8
Flag for a moderator

Re: Insane Packet loss

Downstream bonded channels

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

1Locked35.71092021651
2Locked37.6297952966
3Locked38.659925770
4Locked37.3103512509
5Locked37.6250902858
6Locked37.628073330
7Locked37.3248965212
8Locked37.3176794499
9Locked37.37948015546
10Locked36.6706916060
11Locked36.6140254106
12Locked36.3334813375
13Locked35.51841803376
14Locked35.51924093302
15Locked35.51937192483
16Locked35.52491642412
17Locked353363482175
18Locked35.71195551668
19Locked35.7376621538
20Locked36.3169701763
21Locked36.3182251443
22Locked36.3791591909
23Locked35.7535062279
24Locked35.7729902364

 

Upstream bonded channels

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

1394000294.75512064 qam4



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
0 Kudos
Reply
  • 618
  • 98
  • 325
Very Insightful Person
Very Insightful Person
321 Views
Message 5 of 8
Flag for a moderator

Re: Insane Packet loss

Your downstream power levels are all over the place, only one of the 24 is actually within spec (and then only just). You have lost three out the four upstream channels and you have far too many Pre and Post RS errors - it's all a bit of a mess really!

You'll definitely need an engineer visit, either call it in and request one - although they'll probably make you jump through hoops first restarting the hub and checking wifi etc. or wait for one of the forum team to find this thread (may take a day or so) and they'll contact you to arrange things.

  • 13
  • 0
  • 0
Mavo
Tuning in
314 Views
Message 6 of 8
Flag for a moderator

Re: Insane Packet loss

Thanks for the reply jem.

I'm glad there's a visible issue then, I'll wait for the forum team to chime in.

 

0 Kudos
Reply
  • 1.37K
  • 74
  • 97
Forum Team
Forum Team
257 Views
Message 7 of 8
Flag for a moderator

Re: Insane Packet loss

Hi Mavo, 

 

Thanks for your post, sorry to see you're having a few issues with the broadband.

 

I've found your account so popped you over a private message (little purple envelope in the top right hand corner) so I can help.

 

Get back to me when you can,

 

Alex_Rm

0 Kudos
Reply
  • 13
  • 0
  • 0
Mavo
Tuning in
250 Views
Message 8 of 8
Flag for a moderator

Re: Insane Packet loss

All replied to, the help is appreciated.

0 Kudos
Reply