Forum Discussion

LONETK's avatar
LONETK
Tuning in
2 years ago

Gig one fiber losing packets

Hi there.

I`ve been on gig1 for probably around 2 years. I`ve had issues in the past and after a lot of toing and froing with virgin they came and replaced the line but it didn`t remedy the problem. It turned out to be a faulty superhub 4.

All was well until a few days ago when I noticed lag in my online games along with random disconnects. 

I still have my monitor set up from before so decided to check it. It seems to go off or lost packets every 30 mins. 

I`ll add my bqm and my logs if I can remember how to do it 🙂

Thanks in advance

Broadband Quality Monitor | thinkbroadband

13 Replies

  • 3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
    25331000000640.4QAM25625
    11390000007.740.4QAM2561
    21470000007.740.4QAM2562
    31550000007.540.9QAM2563
    41630000007.140.4QAM2564
    51710000006.740.4QAM2565
    61790000006.540.4QAM2566
    71870000006.440.9QAM2567
    81950000006.340.4QAM2568
    92030000006.340.4QAM2569
    102110000006.340.9QAM25610
    112190000006.440.4QAM25611
    122270000006.440.4QAM25612
    132350000006.540.9QAM25613
    142430000006.840.9QAM25614
    152510000006.540.4QAM25615
    162590000006.740.9QAM25616
    17267000000740.4QAM25617
    182750000006.140.9QAM25618
    192830000006.640.9QAM25619
    202910000006.340.4QAM25620
    212990000006.140.4QAM25621
    223070000006.340.4QAM25622
    233150000006.840.4QAM25623
    243230000006.240.4QAM25624
    26339000000640.4QAM25626
    273470000005.840.4QAM25627
    283550000005.840.4QAM25628
    29363000000640.4QAM25629
    303710000006.540.4QAM25630
    313790000005.940.9QAM25631


    3.0 Downstream channels

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


    3.1 Downstream channels

    Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
    159964K1840QAM4096759


    3.1 Downstream channels

    Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
    159Locked404.815902795600
    • LONETK's avatar
      LONETK
      Tuning in

      3.0 Upstream channels

      Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

      130100000405120 KSym/secQAM644
      22360000039.55120 KSym/secQAM645
      33660000040.55120 KSym/secQAM643
      44310000040.55120 KSym/secQAM642
      54960000040.55120 KSym/secQAM641



      3.0 Upstream channels

      Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

      1ATDMA0000
      2ATDMA0000
      3ATDMA0000
      4ATDMA0000
      5ATDMA0000



      3.1 Upstream channels

      Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
      610.039.02KQAM8


      3.1 Upstream channels

      Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
      6OFDMA20053.900
  • General Configuration

    Network access
    true
    Maximum Number of CPEs
    1
    Baseline Privacy
    true
    DOCSIS Mode
    3.1
    Config file
    87dsfd;kfoA,.iyewrkldJKDH



    Primary Downstream Service Flow

    SFID
    743
    Max Traffic Rate
    1200000450
    Max Traffic Burst
    42600
    Min Traffic Rate
    0



    Primary Upstream Service Flow

    SFID
    742
    Max Traffic Rate
    110000274
    Max Traffic Burst
    42600
    Min Traffic Rate
    0
    Max Concatenated Burst
    42600
    Scheduling Type
    bestEffort
  • Network Log

    Time Priority Description

    Sat 13/01/2024
    13:09:07
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    13:09:07
    5DBC-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;
    Sat 13/01/2024
    13:08:43
    6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    12:15:49
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    12:15:49
    3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    12:10:29
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    12:10:29
    3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    12:09:52
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    11:37:07
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    11:37:07
    5DBC-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;
    Sat 13/01/2024
    11:36:40
    6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    11:36:40
    5DBC-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;
    Sat 13/01/2024
    11:08:41
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    10:06:38
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    10:06:38
    5DBC-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;
    Sat 13/01/2024
    09:50:09
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    09:50:09
    5DBC-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;
    Sat 13/01/2024
    09:09:03
    6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    09:09:03
    5DBC-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;
    Sat 13/01/2024
    09:08:38
    6US profile assignment change. US Chan ID: 6; Previous Profile: ; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    09:08:38
    5DBC-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;
    Sat 13/01/2024
    05:39:01
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat 13/01/2024
    05:04:13
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Fri 12/01/2024
    22:04:44
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Fri 12/01/2024
    21:28:02
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Fri 12/01/2024
    18:01:34
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Fri 12/01/2024
    18:01:34
    5DBC-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;
    Fri 12/01/2024
    18:01:16
    5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Fri 12/01/2024
    09:22:29
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Fri 12/01/2024
    09:02:39
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu 11/01/2024
    18:05:21
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu 11/01/2024
    16:20:31
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    23:52:24
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    23:38:21
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    20:30:51
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    19:21:13
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    15:18:12
    6US profile assignment change. US Chan ID: 6; Previous Profile: 11; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    14:00:19
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    02:31:57
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    01:31:55
    6DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    01:31:55
    4DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Wed 10/01/2024
    01:31:53
    4DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Tue 09/01/2024
    18:18:08
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Tue 09/01/2024
    16:52:01
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Tue 09/01/2024
    09:39:57
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Tue 09/01/2024
    08:09:29
    6CM-STATUS message sent. Event Type Code: 5; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 08/01/2024
    15:54:10
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 08/01/2024
    15:33:47
    3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 08/01/2024
    11:32:11
    6US profile assignment change. US Chan ID: 6; Previous Profile: 12; New Profile: 11.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon 08/01/2024
    11:32:11
    5DBC-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;
  • jpeg1's avatar
    jpeg1
    Alessandro Volta

    The dropped packets show clearly on your BQM, but there is nothing in the Hub data to explain them. It looks very like a external network problem.

    You could try reporting this as a fault, but it may be difficult to convince them. 

  • Thanks for your reply @jpeg1.

    I`ve no idea what I`m looking at in the logs so thanks for shedding some light on it for me. I use the router in modem mode with an asus router. I`ve had it for around 4 or 5 years so maybe that could be on it`s way out.

    Thanks again

  • Looks like some noise on the DOCSIS 3.1 upstream channel (QAM should be 256, not 8).

    • LONETK's avatar
      LONETK
      Tuning in

      Thanks for your reply @carl_pearce. 

      Do you know if that`s something that is easily remedied?

      • carl_pearce's avatar
        carl_pearce
        Superstar

        I suppose it depends if:

        • VM acknowledge it as a fault.
        • The fault can be traced by the engineers called out.
  • jpeg1's avatar
    jpeg1
    Alessandro Volta

    But I don't think that's the cause of the packet loss, there are no timeout errors. 

      • jpeg1's avatar
        jpeg1
        Alessandro Volta

        On the 3.1 channel, yes.   It's still going to need a technician visit to make any progress.