Forum Discussion

cje85's avatar
cje85
Trouble shooter
18 days ago

Poor upload speeds and BQM at peak times

Hi,

I've noticed over recent weeks my BQM graph is looking awful at peak times (weekday evenings, and especially weekends).

To me it looks like upstream utilisation as the 50Mb upload is sometimes struggling to reach 25Mbps in the evening, are the team able to check and see if there are any problems? Utilisation was a big problem years ago in this area and these graphs look much like back then.

Here is a week's worth of BQM graphs to illustrate the problem covering Monday 17th-Sunday 23rd Feb:

 

  • Adduxi's avatar
    Adduxi
    Very Insightful Person

    Yes, agree.  Looks like over subscription in the area.  Or some other area problem whereby your node is taking the strain for somewhere that's failed ?

  • jbrennand's avatar
    jbrennand
    Very Insightful Person

    Has all the hallmarks of a utilisation issue.  You will need to wait here for a few days for VM to comment on whether that is your issue.

    In the meantime can we look at the quality of the connection - can you do this.

    ------------------------------------

    Post up your Hub/network connection details in the format below and someone will check to see if there is a problem there.  In your browser’s URL type in 192.168.0.1  if in router mode or 192.168.100.1 if in modem mode.     No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.

         Then… Navigate to these “data pages” and just copy/paste the normal  “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, &  the Network Logs pages.  Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts

    • cje85's avatar
      cje85
      Trouble shooter

      I think everything looks good here but just for reference here are the hub stats:

       

      Channel    Frequency (Hz)    Power (dBmV)    SNR (dB)    Modulation    Channel ID
      1    491000000    4.9    40    256 qam    45
      2    163000000    3.2    38    256 qam    4
      3    171000000    3.2    38    256 qam    5
      4    195000000    3.2    38    256 qam    8
      5    203000000    3.2    38    256 qam    9
      6    227000000    3    38    256 qam    12
      7    235000000    3    38    256 qam    13
      8    259000000    2.9    38    256 qam    16
      9    267000000    3    38    256 qam    17
      10    291000000    3.4    38    256 qam    20
      11    299000000    3.7    38    256 qam    21
      12    323000000    5.1    38    256 qam    24
      13    331000000    5.3    40    256 qam    25
      14    355000000    5    40    256 qam    28
      15    363000000    5    40    256 qam    29
      16    387000000    4.6    38    256 qam    32
      17    395000000    4.9    40    256 qam    33
      18    419000000    4.4    38    256 qam    36
      19    427000000    4.3    38    256 qam    37
      20    451000000    3.9    38    256 qam    40
      21    459000000    4.3    38    256 qam    41
      22    483000000    4.6    40    256 qam    44
      23    507000000    4.9    40    256 qam    47
      24    515000000    5    40    256 qam    48


      Downstream bonded channels
      Channel    Locked Status    RxMER (dB)    Pre RS Errors    Post RS Errors
      1    Locked    40.3    106    0
      2    Locked    38.9    72    0
      3    Locked    38.6    60    0
      4    Locked    38.9    57    0
      5    Locked    38.6    53    0
      6    Locked    38.9    51    0
      7    Locked    38.6    46    0
      8    Locked    38.9    65    0
      9    Locked    38.6    45    0
      10    Locked    38.9    43    0
      11    Locked    38.6    57    0
      12    Locked    38.9    40    0
      13    Locked    40.3    72    0
      14    Locked    40.3    71    0
      15    Locked    40.3    68    0
      16    Locked    38.9    64    0
      17    Locked    40.3    68    0
      18    Locked    38.9    66    0
      19    Locked    38.9    80    0
      20    Locked    38.9    88    0
      21    Locked    38.9    62    0
      22    Locked    40.3    92    0
      23    Locked    40.3    148    0
      24    Locked    40.3    135    0

       

      Upstream bonded channels
      Channel    Frequency (Hz)    Power (dBmV)    Symbol Rate (ksps)    Modulation    Channel ID
      1    36600000    47.5    5120    64 qam    3
      2    23600000    47.5    5120    64 qam    5
      3    30100000    47.5    5120    64 qam    4
      4    43100000    47.5    5120    64 qam    2
      5    49600000    47.5    5120    64 qam    1


      Upstream bonded channels
      Channel    Channel Type    T1 Timeouts    T2 Timeouts    T3 Timeouts    T4 Timeouts
      1    ATDMA    0    0    0    0
      2    ATDMA    0    0    0    0
      3    ATDMA    0    0    0    0
      4    ATDMA    0    0    0    0
      5    ATDMA    0    0    0    0

       

      24/02/2025 09:31:11    notice    DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      24/02/2025 09:31:11    Error    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      21/02/2025 07:49:55    critical    No Ranging Response received - T3 time-out;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      20/02/2025 21:31:11    notice    DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      20/02/2025 21:31:11    Error    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      19/02/2025 23:20:42    critical    No Ranging Response received - T3 time-out;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      17/02/2025 09:31:10    notice    DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      17/02/2025 09:31:10    Error    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      13/02/2025 22:46:30    critical    No Ranging Response received - T3 time-out;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      13/02/2025 21:31:10    notice    DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      13/02/2025 21:31:10    Error    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      12/02/2025 03:20:59    critical    No Ranging Response received - T3 time-out;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      11/02/2025 15:31:37    notice    LAN login Success;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      10/02/2025 09:31:11    notice    DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      10/02/2025 09:31:11    Error    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      10/02/2025 00:40:24    critical    No Ranging Response received - T3 time-out;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      06/02/2025 21:31:11    notice    DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      06/02/2025 21:31:11    Error    DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;
      04/02/2025 21:08:28    critical    No Ranging Response received - T3 time-out;CM-MAC=(Removed);CMTS-MAC=(Removed);CM-QOS=1.1;CM-VER=3.0;

  • legacy1's avatar
    legacy1
    Alessandro Volta

    VM have given too much upload speed to ones on high packages and they are using it.

    VM have known about the upstream for years and the one who made Docsis work for the internet know about yet why is it still happening? 

    One can look at it like "well it happens therefor we need to add more upstream" the other is "if we QoS/BWM we will never know we need to add more upstream" however you be redlining will high ping vs redlining with low ping

  • jpeg1's avatar
    jpeg1
    Alessandro Volta

    @cje85  The simple truth is that your VM connection is not fit for purpose. 

  • cje85's avatar
    cje85
    Trouble shooter

    Is there anything further the forum team can add to this because although everything "looks great" it obviously isn't and I still suspect the Upstream is badly congested in this area. Pings were awful again over the weekend, causing problems with gaming and video calls. 

    I renewed my contract in December (before this problem began) after getting a good deal to stay with VM, but am hoping i'm not stuck with this level of service until June 2026. 

    Saturday

    Sunday

     

    • Cardiffman282's avatar
      Cardiffman282
      Trouble shooter

      As per jpeg1 the connection is unfit for purpose and you should be able to terminate without an EDF. Speak to Citizens Advice. 

    • Steven_L's avatar
      Steven_L
      Forum Team

      Thanks for coming back to us cje85. How have things been since you last posted, any signs of improvement at all. I've looked into your connection using all the systems that we have available and they aren't showing any issues at all, I've checked the network in the local area and thats not showing any issues with congestion at the moment. I'm going to refer this to our second line team to have a further look into this and see if they can pick anything up that we can't from here. The faults team should get in touch with you directly to have the issues looked into further. 

      Kind Regards,

      Steven_L

      • cje85's avatar
        cje85
        Trouble shooter

        Hi Steven,

        Thanks for raising the issue, this week started off quite bad but yesterday looked a bit better than usual. However Saturday/Sunday are always the worst so i'll see how it goes this weekend and get back to you.

        Here are the graphs so far this week:

        Monday

         

        Tuesday

         

        Wednesday

         

        Thursday