Forum Discussion

mgilbert3's avatar
mgilbert3
Tuning in
5 months ago

Frequent packet loss, high pre/post RS error counts etc

https://www.thinkbroadband.com/broadband/monitoring/quality/share/7ea541f8314f0f8347708ae1d3c4c63207e4d95a

Prior to 30th August I had reported:
Downstream - high power levels. Often a lot of pre and post RS errors
Upstream - gone to often 1 or 2 only. Power level is high

30th August - engineer visited and placed a 6db forward path on to the cable. This restored the number of upstream channels

Between 30th August and 14th August I found that apart from a few latency peaks and small amount of packet loss I wasn't experiencing hte loss of service.

14th September - replacement Hub 3 > Hub 5. Prior to replacement no change in upstream channel signal power from prior validation. After the install of the Hub 5 there was a short period of packet loss after 19:00. High number of errors in downstream post and pre RS; small number of T3 timeouts on the upstream channels
Below is what I have been experiencing since:
15th September - packet loss
16th September - high latency in the evening
17th September - whilst no loss of service experienced, did get high latency and packet loss in the evening
18th September - whilst no loss of service experienced, did get some packet loss
19th September - whilst no loss of service experienced, did get high latency and packet loss
20th September - upstream power levels have increased to min 45.5 to max 50.5. Packet loss experienced leading to some buffering and short loss of service
21st September - restarted Hub 5 to reset error counts etc. Can see earlier in the afternoon packet loss and latency spikes
22nd September - packet loss for a period of time overnight. High number of pre/post RS counts and T3 timeouts. No latency or packet loss during the day
23rd September - no packet loss, odd latemcy peaks
24th September - packet loss in the evening
25th September - restarted Hub 5 to reset error counts etc. Hub was off from c. 08:20 to c. 10:00

These are the log messages I have had this morning since the restart and I'll post the downstream/upstream info in an updated post
25-09-2024 11:40: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;
25-09-2024 11:35:46noticeUS 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;
25-09-2024 11:35:45warningRNG-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;
25-09-2024 11:35:19criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:23:24noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:21:25noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:21:14warningRNG-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;
25-09-2024 11:19:33noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:18:00noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:15:49noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:08:27noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:06:42noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:05:29noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:03:14noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 11:01:50noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 10:46:08noticeCM-STATUS message sent. Event Type Code: 24; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 10:42:48noticeCM-STATUS message sent. Event Type Code: 16; Chan ID: 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
25-09-2024 09:56:29noticeREGISTRATION COMPLETE - Waiting for Operational status
 
  • 3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
    14110000008.440QAM 2561
    24190000008.340QAM 2562
    34990000008.140QAM 25612
    45070000008.240QAM 25613
    55150000008.441QAM 25614
    65230000008.341QAM 25615
    75310000008.440QAM 25616
    85390000008.540QAM 25617
    95470000008.640QAM 25618
    105550000008.540QAM 25619
    115630000008.440QAM 25620
    125710000008.340QAM 25621
    13579000000840QAM 25622
    14587000000840QAM 25623
    155950000008.240QAM 25624
    166030000008.240QAM 25625
    176110000008.340QAM 25626
    186190000008.340QAM 25627
    196270000008.540QAM 25628
    206350000008.440QAM 25629
    216430000008.440QAM 25630
    226510000008.440QAM 25631
    236590000008.440QAM 25632
    246990000008.740QAM 25633
    256670000008.640QAM 25634
    266750000008.840QAM 25635
    276830000008.840QAM 25636
    286910000008.940QAM 25637
    297070000008.540QAM 25638
    307150000008.340QAM 25639
    317230000008.240QAM 25640

    3.0 Downstream channels

    Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
    1Locked4056074449
    2Locked4081415403
    3Locked40118513162
    4Locked40102123145
    5Locked418127899
    6Locked4169558105
    7Locked4074549103
    8Locked4063779123
    9Locked4062340101
    10Locked4072187125
    11Locked4080284128
    12Locked4087696107
    13Locked40106525107
    14Locked40104227127
    15Locked4088529101
    16Locked407460893
    17Locked406092177
    18Locked405188685
    19Locked4042513177
    20Locked403016896
    21Locked402407992
    22Locked4024656104
    23Locked402189986
    24Locked408054100
    25Locked4013639103
    26Locked401126691
    27Locked40818393
    28Locked40701595
    29Locked40763096
    30Locked406108108
    31Locked404093101

    3.1 Downstream channels

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

    3.1 Downstream channels

    Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
    41Locked407.093778472540442
    • mgilbert3's avatar
      mgilbert3
      Tuning in

      3.0 Upstream channels

      Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
      04960000046.55120QAM 641
      14310000046.55120QAM 642
      23660000046.35120QAM 643
      330100000465120QAM 644
      423600000465120QAM 645

      3.0 Upstream channels

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

      3.1 Upstream channels

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

      3.1 Upstream channels

      Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
      6OFDMA2087400000000
      • Kath_P's avatar
        Kath_P
        Forum Team

        Hi mgilbert3,

        Thanks for taking the time to contact us via the Community. It's lovely having you on board with us in the Forums.

        We're sorry to hear you're having an issue with your connection. Running some tests this end, we can see a number of your downstream power levels are too high. We won't be able to fix this remotely so I would like to arrange for an engineer to come to take a look at this for you. 

        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,

  • To close this post. The engineer visited last week and replaced the isolator. This was in the box that is on the inside of the connection coming from the outside, the output of which is the cable that goes into the router.

    Since then there have been no postRS errors on the downstream, no T3 timeouts on the upstream, no packet loss.

    My broadband connection was put in during the ntlworld days and I don't believe has had the isolator replaced since. That certainly appears to have resolved any issues I had been experiencing over the last few weeks and months.

    So thanks Kath_F for arranging the engineer visit.

    • Daniel_Et's avatar
      Daniel_Et
      Forum Team

      Hi mgilbert3, thank you for the update.

      We're glad to hear the issues now appear to be resolved.

      If you have any issues or queries in the future, please don't hesitate to contact us.

      Regards,
      Daniel