Forum Discussion

padeath's avatar
padeath
On our wavelength
8 months ago

High latency, low upload speed, and can't login to hub4

For the last 4 or 5 day, I've noticed high pings and when I checked thinkbroadband's BMQ I see this:

After rebooting the hub the pings drop back down as you can see from the start and end of the graph.

Also I can't login to the hub, I can get the status without logging in, but once I try logging in, thats it I can't access even the status page anymore until I reboot it again.

I've reset the hub to factory defaults by pressing the reset button on it for 15 seconds, and everyday I'm still getting the high latency and low upload speeds.  I tested with samknows realspeed and I get around 30mbit upload, I'm on the 1g package so this should be around 100mbit.  Download speeds dont seem to be affected though.

I've just rebooted the hub again so I'm able to get the status from it.  I did see that the Correcteds (Active Profile) was way higher than it is now before the reboot, like it was in the billions!

 

  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

    253307500009.69999738.605377QAM25625
    113875000010.19999738.605377QAM2561
    21467500009.30000337.355988QAM2562
    31547500009.00000038.605377QAM2563
    41627500009.09999837.636276QAM2564
    51707500009.09999838.605377QAM2565
    61787500009.19999738.605377QAM2566
    71867500009.09999838.983261QAM2567
    81947500009.00000038.605377QAM2568
    92027500009.00000038.605377QAM2569
    102107500009.09999838.983261QAM25610
    112187500008.80000338.605377QAM25611
    122267500008.30000338.983261QAM25612
    132347500008.09999838.605377QAM25613
    142427500008.19999738.605377QAM25614
    152507500008.30000338.605377QAM25615
    162587500008.19999738.605377QAM25616
    172667500008.59999838.983261QAM25617
    182747500008.80000338.605377QAM25618
    192827500008.69999738.983261QAM25619
    202907500009.00000038.983261QAM25620
    212987500009.50000038.983261QAM25621
    223067500009.40000238.605377QAM25622
    233147500008.80000338.983261QAM25623
    243227500009.00000038.983261QAM25624
    2633875000010.09999838.983261QAM25626
    273467500009.90000238.983261QAM25627
    283547500009.80000340.366287QAM25628
    2936275000010.09999840.366287QAM25629
    3037075000010.00000038.983261QAM25630
    313787500009.30000338.983261QAM25631

    3.0 Downstream channels

    Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

    25Locked38.60537700
    1Locked38.60537700
    2Locked37.35598800
    3Locked38.60537700
    4Locked37.63627600
    5Locked38.60537700
    6Locked38.60537700
    7Locked38.98326100
    8Locked38.60537700
    9Locked38.60537700
    10Locked38.98326100
    11Locked38.60537700
    12Locked38.98326100
    13Locked38.60537700
    14Locked38.60537700
    15Locked38.60537700
    16Locked38.60537700
    17Locked38.98326100
    18Locked38.60537700
    19Locked38.98326100
    20Locked38.98326100
    21Locked38.98326100
    22Locked38.60537700
    23Locked38.98326100
    24Locked38.98326100
    26Locked38.98326100
    27Locked38.98326100
    28Locked40.36628700
    29Locked40.36628700
    30Locked38.98326100
    31Locked38.98326100
  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    3.1 Downstream channels

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

    491924K3736QAM4096759



    3.1 Downstream channels

    Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

    49Locked427.330427670
  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    3.0 Upstream channels

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

    12360000041.2705995120 KSym/sec64QAM11
    23660000041.2705995120 KSym/sec64QAM7
    34310000041.5205995120 KSym/sec64QAM6
    44960000042.0205995120 KSym/sec64QAM5
    53010000041.2705995120 KSym/sec64QAM8



    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

    1US_TYPE_ATDMA0000
    2US_TYPE_ATDMA0000
    3US_TYPE_ATDMA0000
    4US_TYPE_ATDMA0000
    5US_TYPE_ATDMA0000



    3.1 Upstream channels

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


    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    12OFDMA20853.400
  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    Time Priority Description

    Mon Jun
    17    		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon Jun
    17    		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat Jun
    15    		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
  • Anonymous's avatar
    Anonymous
    8 months ago

    The log and the numbers don't really reveal anything, at least not right after a reboot. You are the first to show such a big downstream 3.1 channel, though. 🙂

    A note: You must be on the old firmware, which always shows the lowest modulation (QAM8) for the 3.1 upstream. Also indicated by the frequency of 3.1 upstream. The new firmware shows 74 MHz (a bug).

  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    So after the reboot yesterday, the BMQ graph looked ok until about just after 9pm last night.

    I've not rebooted the modem this time which seems to always clear the high latency. So here are the stats from it now.

    There are now 1.3Billion Correcteds!

    3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

    2533075000010.00000038.605377QAM25625
    113875000010.69999737.636276QAM2561
    21467500009.69999737.636276QAM2562
    31547500009.59999838.983261QAM2563
    41627500009.59999837.636276QAM2564
    51707500009.40000238.605377QAM2565
    61787500009.59999838.605377QAM2566
    71867500009.50000038.605377QAM2567
    81947500009.30000338.605377QAM2568
    92027500009.30000338.605377QAM2569
    102107500009.50000038.605377QAM25610
    112187500009.30000338.605377QAM25611
    122267500008.90000238.605377QAM25612
    132347500008.59999838.605377QAM25613
    142427500008.69999738.605377QAM25614
    152507500008.69999738.983261QAM25615
    162587500008.59999838.605377QAM25616
    172667500009.19999738.983261QAM25617
    182747500009.30000338.605377QAM25618
    192827500009.19999738.983261QAM25619
    202907500009.50000038.983261QAM25620
    2129875000010.00000038.605377QAM25621
    223067500009.80000338.983261QAM25622
    233147500009.09999838.605377QAM25623
    243227500009.40000238.983261QAM25624
    2633875000010.59999838.983261QAM25626
    2734675000010.59999838.605377QAM25627
    2835475000010.69999738.983261QAM25628
    2936275000011.30000340.366287QAM25629
    3037075000011.30000338.983261QAM25630
    3137875000010.59999838.983261QAM25631
    • legacy1's avatar
      legacy1
      Alessandro Volta
      8 months ago

      Mabe your causing this with something downloading or uploading?

      Change to modem mode with a PC allow ICMP from 80.249.99.164 on firewall setup a new BQM and see what it shows

      • padeath's avatar
        padeath
        On our wavelength
        8 months ago

        Nope I'm not downloading or uploading anything.

        I used to have the modem in modem mode and it did the same thing then, granted that was with my own router connected to it, but changing it between modem and router mode hasn't changed anything, it still does it at random times. Currently the BQM graph shows the following and the latency has gone away, and as per my reply to gitty, the QAM is back to QAM32 on the upstream.

        I did nothing at 10am this morning and the high spikes went away all on their own.

  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    3.0 Downstream channels

    Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors

    25Locked38.60537700
    1Locked37.63627600
    2Locked37.63627600
    3Locked38.98326100
    4Locked37.63627600
    5Locked38.60537700
    6Locked38.60537700
    7Locked38.60537700
    8Locked38.60537700
    9Locked38.60537700
    10Locked38.60537700
    11Locked38.60537700
    12Locked38.60537700
    13Locked38.60537700
    14Locked38.60537700
    15Locked38.98326100
    16Locked38.60537700
    17Locked38.98326100
    18Locked38.60537700
    19Locked38.98326100
    20Locked38.98326100
    21Locked38.60537700
    22Locked38.98326100
    23Locked38.60537700
    24Locked38.98326100
    26Locked38.98326100
    27Locked38.60537700
    28Locked38.98326100
    29Locked40.36628700
    30Locked38.98326100
    31Locked38.98326100



    3.1 Downstream channels

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


    3.1 Downstream channels

    Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
    49Locked438.6136897931532
  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    3.0 Upstream channels

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

    12360000039.7705995120 KSym/sec64QAM11
    23660000040.0205995120 KSym/sec64QAM7
    34310000040.0205995120 KSym/sec64QAM6
    44960000040.5205995120 KSym/sec64QAM5
    53010000040.0205995120 KSym/sec64QAM8



    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

    1US_TYPE_ATDMA0000
    2US_TYPE_ATDMA0000
    3US_TYPE_ATDMA0000
    4US_TYPE_ATDMA0000
    5US_TYPE_ATDMA0000



    3.1 Upstream channels

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


    3.1 Upstream channels

    Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
    12OFDMA20853.400
  • padeath's avatar
    padeath
    On our wavelength
    8 months ago

    Network Log

    Time Priority Description

    Mon Jun
    17    		6US profile assignment change. US Chan ID: 12; Previous Profile: 12; New Profile: .;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon Jun
    17    		6CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon Jun
    17    		6US profile assignment change. US Chan ID: 12; Previous Profile: ; New Profile: 12.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon Jun
    17    		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Mon Jun
    17    		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Sat Jun
    15    		5MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    Thu Jan
    		3No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
  • Anonymous's avatar
    Anonymous
    8 months ago

    Do you know, if the upstream modulation changes when your latency goes haywire? That could add to a possible congestion issue.

    The 3.1 channel works differently and is operated differently, so the large amount of corrected codewords is to be expected. Don't worry about that. 🙂

    • padeath's avatar
      padeath
      On our wavelength
      8 months ago

      Yep I have actually noticed that, when I get a bad BQM graph and high latency, and my upload speed drops to 30mbit, the upstream modulation changes to QAM8 instead of QAM32.

      When it goes back to QAM32, the upstream corrected codewords actually stop going up too.