Forum Discussion

spudandbeanz's avatar
spudandbeanz
Tuning in
16 hours ago

Upstream power too high?

I've been having connection drop-out issues for the past few months (~180 reconnects within the last month according to VM, though I only saw a drop 1-2 a day for 5-90 mins at a time). I'd been mostly away from home so didn't bother about it until this week, when VM sent out an engineer to investigate (10th July).

The engineer removed an old NTL attenuator/splitter, along with the splitter for the broadband and TV (as I plan to ditch the TV). He also switched out my Hub 3 for a Hub 5, which has an inline attenuator on its cable feed.

Annoyingly I didn't note the full line stats before the changes, but the engineer said the downstream was reporting as -8 dBmV, and after these changes is now 0 to -5 dBmV with an SNR of 40 dB.

I'm still having drop-outs (and T2 and T3 timeouts), though less frequent (1 time a day for 1-5 mins at a time), and from doing some research I suspect my upstream power is still too high. It's currently sitting at 52 dBmV, but I've seen it get as high as 59 dBmV immediately after the modem reconnected (it drops back down to 52 dBmV over a span of ~20 mins once the connection is back up).

I just wanted to confirm my understanding is correct before requesting another engineer visit to correct the upstream power.

I tried to add the full line stats and log into this post, but the forums report "Your post contains invalid HTML." if I do... that used to work.

10 Replies

  • Apologies for the formatting below. It would only let me post it when pasted as plain text.

    3.0 Downstream channels

    Channel    Frequency (Hz)    Power (dBmV)    SNR (dB)    Modulation    Channel ID
    1    306000000    -3.3    39    QAM 256    22
    2    138000000    0.8    41    QAM 256    1
    3    146000000    0.4    41    QAM 256    2
    4    154000000    0.1    40    QAM 256    3
    5    162000000    0.3    40    QAM 256    4
    6    170000000    0.5    40    QAM 256    5
    7    178000000    0.7    40    QAM 256    6
    8    186000000    -1.1    40    QAM 256    7
    9    194000000    -1.2    40    QAM 256    8
    10    202000000    -1.3    40    QAM 256    9
    11    210000000    -1.3    40    QAM 256    10
    12    218000000    -1.6    40    QAM 256    11
    13    226000000    -1.8    40    QAM 256    12
    14    234000000    -2.2    40    QAM 256    13
    15    242000000    -2    40    QAM 256    14
    16    250000000    -2    40    QAM 256    15
    17    258000000    -2.3    40    QAM 256    16
    18    266000000    -2.5    40    QAM 256    17
    19    274000000    -2.7    40    QAM 256    18
    20    282000000    -2.5    40    QAM 256    19
    21    290000000    -2.5    40    QAM 256    20
    22    298000000    -2.7    40    QAM 256    21
    23    314000000    -3.4    39    QAM 256    23
    24    322000000    -3.8    39    QAM 256    24
    25    330000000    -4    39    QAM 256    25
    26    338000000    -4    39    QAM 256    26
    27    346000000    -4.4    39    QAM 256    27
    28    354000000    -4.4    39    QAM 256    28
    29    362000000    -4.3    39    QAM 256    29
    30    370000000    -4.3    39    QAM 256    30
    31    378000000    -4.5    39    QAM 256    31
    32    386000000    -4.7    39    QAM 256    32

    3.0 Downstream channels

    Channel    Locked Status    RxMER (dB)    Pre RS Errors    Post RS Errors
    1    Locked    39    71    0
    2    Locked    41    46    0
    3    Locked    41    60    5
    4    Locked    40    60    0
    5    Locked    40    65    0
    6    Locked    40    59    0
    7    Locked    40    45    0
    8    Locked    40    63    0
    9    Locked    40    37    0
    10    Locked    40    55    0
    11    Locked    40    46    0
    12    Locked    40    56    0
    13    Locked    40    58    0
    14    Locked    40    62    0
    15    Locked    40    64    0
    16    Locked    40    57    0
    17    Locked    40    64    0
    18    Locked    40    59    0
    19    Locked    40    58    0
    20    Locked    40    55    0
    21    Locked    40    71    0
    22    Locked    40    76    0
    23    Locked    39    77    0
    24    Locked    39    67    0
    25    Locked    39    59    0
    26    Locked    39    72    0
    27    Locked    39    68    0
    28    Locked    39    73    0
    29    Locked    39    89    0
    30    Locked    39    78    0
    31    Locked    39    77    0
    32    Locked    39    74    0

    3.1 Downstream channels

    Channel    Channel Width (MHz)    FFT Type    Number of Active Subcarriers    Modulation (Active Profile)    First Active Subcarrier (Hz)
    159    92    4K    1800    QAM 4096    1128

    3.1 Downstream channels

    Channel ID    Locked Status    RxMER Data (dB)    PLC Power (dBmV)    Corrected errors (Active Profile)    Uncorrectable errors (Active Profile)
    159    Locked    40    -4.7    3934885581    0

    3.0 Upstream channels

    Channel    Frequency (Hz)    Power (dBmV)    Symbol Rate (ksps)    Modulation    Channel ID
    0    36600000    51.8    5120    QAM 64    11

    3.0 Upstream channels

    Channel    Channel Type    T1 Timeouts    T2 Timeouts    T3 Timeouts    T4 Timeouts
    0    ATDMA    0    4    0    0

    Network Log

    Time    Priority    Description
    13-07-2025 12:44:18    warning    DBC-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;
    13-07-2025 12:44:17    critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:33:15    notice    REGISTRATION COMPLETE - Waiting for Operational status
    13-07-2025 12:33:10    warning    REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:33:04    notice    DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:33:03    notice    TLV-11 - unrecognized OID;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:55    warning    DHCP WARNING - Non-critical field invalid in response ;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:53    notice    Honoring MDD; IP provisioning mode = IPv4
    13-07-2025 12:32:40    warning    ToD request sent - No Response received;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:40    critical    No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:30    warning    REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:25    notice    DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:23    notice    TLV-11 - unrecognized OID;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:16    warning    DHCP WARNING - Non-critical field invalid in response ;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:32:14    notice    Honoring MDD; IP provisioning mode = IPv4
    13-07-2025 12:32:02    critical    Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    13-07-2025 12:31:35    warning    ToD request sent - No Response received;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:59:03    warning    DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:59:03    critical    SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:48:20    critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:48:00    notice    REGISTRATION COMPLETE - Waiting for Operational status
    12-07-2025 09:47:54    warning    REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:47:48    notice    DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:47:47    notice    TLV-11 - unrecognized OID;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:47:38    warning    DHCP WARNING - Non-critical field invalid in response ;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:47:36    notice    Honoring MDD; IP provisioning mode = IPv4
    12-07-2025 09:46:59    critical    Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:46:56    critical    Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:46:10    critical    Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=****;CMTS-MAC=****:cd;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:45:39    critical    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:45:38    warning    Lost MDD Timeout;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;
    12-07-2025 09:45:27    critical    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=****;CMTS-MAC=****;CM-QOS=1.1;CM-VER=3.1;

    • Cardiffman282's avatar
      Cardiffman282
      Wise owl

      The upstream power level is too high but more importantly you only seem to have one upstream channel. Is that correct? 

      Also check for local faults on 0800 561 0061. 

      • spudandbeanz's avatar
        spudandbeanz
        Tuning in

        One channel is indeed what the router shows. This is a M125 connection FWIW.

        The online fault checker has just been switching between "There is intermittent signal in your area" and "We need to send an engineer" for the past few months, though now it says "No broadband issues found".

        Given this connection had been stable for years, and given nothing changed on my side, I do suspect I got moved to a different tap or something a few months back.

  • legacy1's avatar
    legacy1
    Alessandro Volta

    The attenuator was likely need when the amp was working correctly removing a attenuator don't not fix this.

  • Anonymous's avatar
    Anonymous

    Firstly ”...180 reconnects within the last month according to VM”; yeah firstly ignore that, they have just made that figure up, means nothing.

    Now yes, your logs are a complete mess, so yes not surprised that your upstream power is at that level and also, really you only have one locked upstream channel?

    The way that it works is this, the hub increases the upstream power in an attempt to communicate with the CMTS (that’s the device which is ultimately at the other end of the cable). It keeps ramping up the power until either it gets a stable connection or it hits its upper limits (which oddly enough is 59 dBmV, after which it reboots).

    High upstream power is not a problem it itself which needs to be fixed, it's an indication that something else is wrong. Mostly likely a bad cable connection between your hub and the street cabinet, possibly also a faulty amp in said cabinet or an upstream cabinet.

    “....but the engineer said the downstream was reporting as -8 dBmV, and after these changes is now 0 to -5 dBmV with an SNR of 40 dB."

    Great, good, but irrelevant, you have a cable issue which is allowing noise ingress and killing your upstream connection. Sorry but, good luck getting VM to either understand or deal with it.

    • spudandbeanz's avatar
      spudandbeanz
      Tuning in

      High upstream power is not a problem it itself which needs to be fixed, it's an indication that something else is wrong

      I understand, though by "correct the upstream power" I really meant "fix whatever is causing the modem to have to shout so loud to be heard".

      you only have one locked upstream channel?

      Yes, and I've also seen that drop down to QAM 32 at times. I'm pretty sure I had 4 before these issues started.

      • Anonymous's avatar
        Anonymous

        "I understand, though by "correct the upstream power" I really meant "fix whatever is causing the modem to have to shout so loud to be heard”."

        Fine yes, you get it, alas some people who respond to similar threads, don’t necessarily do and just crash in with a generic ‘make a BQM’ (although oddly the people who request this, often don’t respond to what it says, almost as if they don't actually understand what they’ve asked for)!

        OK look you are not an idiot are you? Your upstream connection is shot, you have a really bad noise ingress, somewhere. Now the problem is getting VM to acknowledge this and deal with it.

  • Client62's avatar
    Client62
    Alessandro Volta

    There is only one 3.0 Upstream channel in the stats above,
    it is normal to have between four and six channels connected and all at QAM 64.

    Downstream Power Levels of -7 to +7 dBmV are preferred, +10dBmV is the max acceptable, with a SNR of 33dB or higher across all DOCSIS 3.0 channels. Rising error counts across many channels is a current service noise fault.

    Upstream
    Power Levels of 35 to 49 dBmV are preferred, with QAM 64 Modulation mode across four to six DOCSIS 3.0 channels.  Seeing QAM 32/16/QPSK is a current service noise fault.  Seeing less than four DOCSIS 3.0 channels is usually a signal level fault.