Forum Discussion

Tom_nock's avatar
Tom_nock
Tuning in
2 years ago

Does this BQM look right?

New customer on Gig1 (M500 with Volt) and a Hub 5. 

Connected in modem mode originally to a DrayTek 2962 and now an Edgerouter-X.

 

I originally stated out with M500 and a Hub 3. The BQM for that looked perfect when using the Edgerouter-X.

Does this BQM graph look right with my Hub5? It’s the yellow areas that don’t look right to me - the first earlier part of the graph is with the 2962 and the red areas are where I either rebooted or at around 10am this morning I swapped the 2962 out for the Edgerouter-X.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d11a49b057e580f068fd118ba0ec2fff7605360c-05-03-2024


Speeds are ok, haven’t seen the full 1Gbps on Ethernet yet, more around the 700-800Mbps mark. Upload seems fine and consistent at 105Mbps. I can iPerf to my Raspberry Pi at 940Mbps so my local network seems OK. 

Looking for your thoughts please! Thank you. 

11 Replies

Sort By
  • legacy1's avatar
    legacy1
    Alessandro Volta
    2 years ago

    Look fine some BQM look better then others but the question we can't answer is maybe your is worse but better under load in the area the key is min to max if the closer the better but if VM have to make that worse for better under load in the area the better till it come to a point where where the min and max are too far apart    

  • carl_pearce's avatar
    carl_pearce
    Superstar
    2 years ago

    No, the BQM doesn't look 'fine'.

    Can you please post the HUB stats from the 'Check router status' section.

    • Tom_nock's avatar
      Tom_nock
      Tuning in
      2 years ago

      3.0 Downstream channels

      Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
      13310000004.442QAM 25625
      21390000007.242QAM 2561
      3147000000741QAM 2562
      41550000006.841QAM 2563
      51630000006.642QAM 2564
      61710000006.441QAM 2565
      71790000006.241QAM 2566
      81870000006.341QAM 2567
      91950000006.441QAM 2568
      102030000006.341QAM 2569
      112110000006.341QAM 25610
      122190000006.242QAM 25611
      132270000006.242QAM 25612
      142350000006.142QAM 25613
      152430000005.942QAM 25614
      162510000005.942QAM 25615
      172590000006.142QAM 25616
      182670000006.142QAM 25617
      192750000006.142QAM 25618
      202830000005.842QAM 25619
      212910000005.742QAM 25620
      222990000005.442QAM 25621
      233070000005.242QAM 25622
      243150000004.842QAM 25623
      253230000004.441QAM 25624
      263390000004.641QAM 25626
      273470000004.642QAM 25627
      283550000004.642QAM 25628
      293630000004.742QAM 25629
      303710000004.641QAM 25630
      313790000004.541QAM 25631
      323870000004.341QAM 25632

      3.0 Downstream channels

      Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
      1Locked4200
      2Locked4200
      3Locked4100
      4Locked4100
      5Locked4200
      6Locked4100
      7Locked4100
      8Locked4100
      9Locked4100
      10Locked4100
      11Locked4100
      12Locked4200
      13Locked4200
      14Locked4200
      15Locked4200
      16Locked4200
      17Locked4200
      18Locked4200
      19Locked4200
      20Locked4200
      21Locked4200
      22Locked4200
      23Locked4200
      24Locked4200
      25Locked4100
      26Locked4100
      27Locked4200
      28Locked4200
      29Locked4200
      30Locked4100
      31Locked4100
      32Locked4100

      3.1 Downstream channels

      Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
      159944K1840QAM 40961108

      3.1 Downstream channels

      Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
      159Locked40-1.33297733560
  • Tom_nock's avatar
    Tom_nock
    Tuning in
    2 years ago

    3.0 Upstream channels

    Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
    049600000445120QAM 649
    143100000445120QAM 6410
    23660000043.85120QAM 6411
    33010000043.35120QAM 6412
    423600000435120QAM 6413

    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
    0ATDMA0060
    1ATDMA0000
    2ATDMA0000
    3ATDMA0000
    4ATDMA0000

    3.1 Upstream channels

    Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
    141038.52KQAM 256

    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    14OFDMA2007400000000
    • Tom_nock's avatar
      Tom_nock
      Tuning in
      2 years ago

      Snippet of today and yesterday evening…

      Network Log

      Time Priority Description
      05-03-2024 08:49:37noticeUS profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-03-2024 08:49:37warningDBC-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;
      05-03-2024 08:49:33noticeREGISTRATION COMPLETE - Waiting for Operational status
      05-03-2024 08:49:28warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-03-2024 08:49:28warningDynamic Range Window violation
      05-03-2024 08:49:27warningREG-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;
      05-03-2024 08:49:21noticeDS 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;
      05-03-2024 08:49:18noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-03-2024 08:49:16warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-03-2024 08:49:14noticeHonoring MDD; IP provisioning mode = IPv4
      05-03-2024 08:48:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-03-2024 08:48:40criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-03-2024 08:48:39criticalCable Modem Reboot because of - HW or Power-On Reset
      04-03-2024 19:31:13criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      04-03-2024 19:31:07criticalCable Modem Reboot because of - Reboot UI
      04-03-2024 19:31:07criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      04-03-2024 18:38:21criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      04-03-2024 18:38:20criticalUnicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      04-03-2024 18:38:15criticalCable Modem Reboot because of - HW or Power-On Reset
  • carl_pearce's avatar
    carl_pearce
    Superstar
    2 years ago

    Although the downstream power levels are in spec, there is one entry that shows power levels are out of spec at some point.

    May be worth waiting for VM to reply to see if they can see anything their side.

  • Tom_nock's avatar
    Tom_nock
    Tuning in
    2 years ago

    I think I’ve figured that the blocks of yellow on the BQM are when my connection is idle. When I’m on a Teams call for instance, the graph will show “normal” as I’d expect. 

    Can’t even think what would cause that? I even gave the hub a pin hole reset last night and it’s made no difference. 

    • legacy1's avatar
      legacy1
      Alessandro Volta
      2 years ago

      Maybe the Docsis scheduler can do idle scheduling then when the traffic rate goes up it allows for lower latency

    • Martin_N's avatar
      Martin_N
      Icon for Forum Team rankForum Team
      2 years ago

      Hi Tom_nock,

      Thank you for your post. I'm very sorry to hear about the issue with your broadband service.

      I am happy to take a look into this for you. 

      I will private message you now to confirm your details. 

      ^Martin