Forum Discussion

carl_pearce's avatar
carl_pearce
Superstar
10 months ago

T3 and T4 timeouts after outage

After a recent outage I've been seeing a lot of T3 and T4 errors.

The below is following a reboot of the HUB (5) two days ago:

 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/f456cb37eb5964be55ad4b06a2cd7bb8604b6d51

The connection itself appears 'ok', however, something is amiss.

Service status shows ok sometimes, and local issues occasionally.

Would be useful to know if VM are are aware and looking into it.

Thanks.

43 Replies

Show More
  • carl_pearce's avatar
    carl_pearce
    Superstar
    9 months ago

    3.1 Upstream channels

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

    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    6OFDMA20074000000109646


    Network Log

    Time Priority Description
    09-10-2024 19:03:01criticalReceived 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;
    09-10-2024 18:59:45criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 18:58:44noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 18:58:44warningDBC-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;
    09-10-2024 18:58:44warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 18:48:38noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 18:48:38warningDBC-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;
    09-10-2024 18:38:32noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 18:38:32warningDBC-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;
    09-10-2024 17:53:09criticalReceived 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;
    09-10-2024 17:49:53criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:48:09noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:48:09warningDBC-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;
    09-10-2024 17:48:09warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:38:07warningDBC-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;
    09-10-2024 17:38:07noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:07:49noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:07:49warningDBC-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;
    09-10-2024 17:03:38criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:03:38criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:03:38critical16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:03:18criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:03:18criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:03:18critical16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:01:58critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 17:01:58criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 16:58:47criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 16:57:45warningDBC-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;
    09-10-2024 16:57:45noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 16:57:45warningTCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 16:17:19noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-10-2024 16:17:19warningDBC-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;
  • carl_pearce's avatar
    carl_pearce
    Superstar
    9 months ago

    I'm getting a bit fed up now as it's starting to affect my connection on occasion:

    Please can an engineer investigate the issue at the local cabinet and replace the hardware that was replaced on the initial outage?

    Clearly there is something wrong.

    • Kath_P's avatar
      Kath_P
      Icon for Forum Team rankForum Team
      8 months ago

      Hi carl_pearce, 

      Thanks for coming back to us on this one. 

      We're sorry to hear these issues are continuing. As it stands, there is nothing to suggest a wider area fault so we would need to continue on this being an individual issue. We'll need to look at booking an engineer to come and check things out at your property and the local cabinet that you're connected to. I just need to confirm the address to ensure we are booking the visit on the correct account. I have sent you a direct message to allow us to do this with you in a private space. If you are using a PC/Laptop then you can just click on the little ✉ at the top right-hand side of the page to access your inbox. If you are on a mobile/tablet device then instead click on the little circle icon in the top right then select 'Messages'. 😊

      Thanks,

    • Kath_P's avatar
      Kath_P
      Icon for Forum Team rankForum Team
      8 months ago

      Hi carl_pearce,

      Thanks for coming back to via private message to confirm your information. 🤩

      I have booked you in for the next available appointment. To view this please sign in to My Virgin Media here 👉 My VM. Once you log in scroll down to Orders & appointments then click on View your orders. Please note it can take up to 24 hours to show but you should also receive a text message with the details. You can also view this in the My VM app. If you have any issues with accessing your account or unable to see your visit, please do let us know and we’ll pop you a message to pass data protection and confirm the appointment details.

      Just to confirm, there will be no charge for this visit unless:

      • âž¡ The technician diagnoses the faults as not being caused by our network/equipment 
      • âž¡ The technician discovers that the fault or problem relates to your equipment
      • âž¡ The technician discovers that the fault or problem relates to any system that we are not responsible for
      • âž¡ The technician will confirm during their visit if any of these instances apply, and if so, a £25 charge will be applied to your account.

      Please ensure there is someone over the age of 18 present at the time of the visit. If you need to change or cancel your appointment you can do this online or via the MyVM app by 4pm the day before the appointment. If you do miss an agreed appointment for any reason, a £25 missed appointment charge will be applied to your account on the day of the appointment.

      We will continue to monitor your services and if we can see that the fault has cleared and the visit is no longer required we will cancel the appointment and let you know by text and email.

      Let us know how the appointment goes. ðŸ˜Š

      Take care.

      • carl_pearce's avatar
        carl_pearce
        Superstar
        7 months ago

        After the most recent engineer visit all was ok for a while and how the power levels on the DOCSIS 3.1 downstream channel have dropped out of spec, and over the last few days I'm seeing uncorrectable errors. I'm not sure if its the line or the HUB 5 at this stage (The below stats are around 10 minutes after rebooting the HUB):

        3.0 Downstream channels

        Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
        13310000000.738QAM 25625
        21390000003.639QAM 2561
        31470000003.339QAM 2562
        41550000003.339QAM 2563
        51630000002.739QAM 2564
        61710000002.639QAM 2565
        71790000002.639QAM 2566
        81870000002.540QAM 2567
        91950000002.440QAM 2568
        102030000002.140QAM 2569
        11211000000240QAM 25610
        122190000001.440QAM 25611
        132270000001.340QAM 25612
        142350000001.540QAM 25613
        152430000000.840QAM 25614
        16251000000040QAM 25615
        172590000000.340QAM 25616
        182670000000.340QAM 25617
        192750000000.840QAM 25618
        202830000000.539QAM 25619
        212910000000.439QAM 25620
        222990000000.738QAM 25621
        233070000001.438QAM 25622
        243150000001.538QAM 25623
        253230000000.638QAM 25624
        263390000001.338QAM 25626
        273470000001.338QAM 25627
        283550000000.539QAM 25628
        293630000000.140QAM 25629
        303710000000.940QAM 25630
        313790000000.940QAM 25631
        323870000000.140QAM 25632

        3.0 Downstream channels

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

        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)
        159Locked33-13.531499394747269
         
  • carl_pearce's avatar
    carl_pearce
    Superstar
    8 months ago

    3.1 Upstream channels

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

    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    6OFDMA20074000000132250
     
  • carl_pearce's avatar
    carl_pearce
    Superstar
    7 months ago

    Network Log

    Time Priority Description
    04-12-2024 22:57:58noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:48noticeUS profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:48warningDBC-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;
    04-12-2024 22:57:43noticeREGISTRATION COMPLETE - Waiting for Operational status
    04-12-2024 22:57:37warningDynamic Range Window violation
    04-12-2024 22:57:37warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:37warningREG-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;
    04-12-2024 22:57:37warningRNG-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;
    04-12-2024 22:57:37warningDynamic Range Window violation
    04-12-2024 22:57:37warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:37warningDynamic Range Window violation
    04-12-2024 22:57:31noticeDS 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;
    04-12-2024 22:57:28noticeTLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:25warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:23noticeHonoring MDD; IP provisioning mode = IPv4
    04-12-2024 22:57:09criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:03criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-12-2024 22:57:02criticalCable Modem Reboot because of - Reboot UI
    26-11-2024 02:34:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-11-2024 02:34:26criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-11-2024 02:34:25criticalCable Modem Reboot because of - unknown
    23-11-2024 20:07:06critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 20:07:06criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 20:04:46criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 18:38:14criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 18:38:14critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 18:33:55criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 16:26:47criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 16:26:47critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-11-2024 16:22:47criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    22-11-2024 21:27:16critical16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    22-11-2024 21:27:16criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
  • carl_pearce's avatar
    carl_pearce
    Superstar
    7 months ago

    I've just tried removing the 10dB Attenuator which has increased the power for the DOCSIS 3.1 channel, however, it's still reporting uncorrected errors and the DOCSIS 3.0 channels are mostly out of spec!

    3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
    133100000010.638QAM 25625
    213900000013.339QAM 2561
    314700000013.139QAM 2562
    41550000001339QAM 2563
    516300000012.339QAM 2564
    617100000012.239QAM 2565
    717900000012.339QAM 2566
    818700000012.440QAM 2567
    919500000012.440QAM 2568
    1020300000011.940QAM 2569
    1121100000011.741QAM 25610
    122190000001140QAM 25611
    1322700000011.141QAM 25612
    1423500000011.340QAM 25613
    1524300000010.740QAM 25614
    162510000009.740QAM 25615
    172590000009.340QAM 25616
    182670000009.840QAM 25617
    1927500000010.540QAM 25618
    2028300000010.439QAM 25619
    2129100000010.239QAM 25620
    2229900000010.339QAM 25621
    2330700000010.939QAM 25622
    2431500000011.239QAM 25623
    2532300000010.538QAM 25624
    263390000001138QAM 25626
    2734700000010.939QAM 25627
    2835500000010.239QAM 25628
    293630000001040QAM 25629
    3037100000010.940QAM 25630
    3137900000010.940QAM 25631
    323870000009.840QAM 25632

    3.0 Downstream channels

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

    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)
    159Locked35-3.257644701572
    • Kath_P's avatar
      Kath_P
      Icon for Forum Team rankForum Team
      7 months ago

      Hi carl_pearce, 

      Thanks for coming back to us on this. We're sorry to hear there's been further disruption after the engineer visit. 

      Checking here, the downstream levels are out. We would advise popping the attenuator back on as this would have been given based on the levels at the time. Once it's back to how it was, please reboot the hub and let us know how things go. 

      We can then re-check things here and take further steps then based on the results. 

      Many thanks, 

      • carl_pearce's avatar
        carl_pearce
        Superstar
        7 months ago

        A few days ago if I started using the attenuator the power level on the DOCSIS 3.1 downstream channel would go out of spec, however, for some reason the power levels have started increasing on that channel over the last 24 hours (It was, at worse, -4.7 (Minus 4.7) dBmV:

        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)
        159Locked385.724838441281983475918
         
        I'll try with the attenuator now the power level has returned.
  • carl_pearce's avatar
    carl_pearce
    Superstar
    7 months ago

    I've added a 6dB attenuator and the power level is -0.2 (I'll keep an eye on it to see if it drops again).

    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)
    159Locked38-0.278308390
     
    • Kath_P's avatar
      Kath_P
      Icon for Forum Team rankForum Team
      7 months ago

      Morning carl_pearce, 

      Thanks for coming back to us on this. 

      Checking things here today, the levels show very slightly outside of optimal however still in the accepted range. 

      Are you having issues with the connection? If so, let us know what issues you're having so we can help further. 

      Thanks, 

      • carl_pearce's avatar
        carl_pearce
        Superstar
        7 months ago

        Hi Kath,

        Yes, it has been more stable this week.

        Hopefully it stays that way.