Forum Discussion

NinjaAndy's avatar
NinjaAndy
Tuning in
2 years ago

Hub 3.0 crashing

Hi,

Since December, my Hub 3.0 crashes every day. Sometimes it recovers / restarts itself, sometimes I have to restart it using the rocker switch on the back. It takes ~10 minutes to get back online each time. I'm not sure how to troubleshoot this...

I don't believe it's overheating, as it's not in a small space, its in fresh air on top of a cupboard. 

The last time it happened was today, around 2:30pm (I think..)

I'll post my log files, in case they're useful. 

Thanks in advance! 

Andy

7 Replies

Sort By
  • NinjaAndy's avatar
    NinjaAndy
    Tuning in
    2 years ago

    Cable Modem StatusItem Status Comments

    Acquired Downstream Channel (Hz)
    203000000
    Locked
    Ranged Upstream Channel (Hz)
    23600000
    Locked
    Provisioning State
    Online

     

     

    Downstream bonded channels

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

    12030000007.140256 qam9
    2211000000740256 qam10
    3219000000740256 qam11
    42270000006.840256 qam12
    52350000006.840256 qam13
    62430000006.540256 qam14
    72510000006.340256 qam15
    8259000000640256 qam16
    9267000000640256 qam17
    10275000000640256 qam18
    112830000005.940256 qam19
    12291000000640256 qam20
    132990000005.940256 qam21
    14307000000640256 qam22
    15315000000640256 qam23
    16323000000640256 qam24
    17331000000640256 qam25
    18339000000640256 qam26
    19347000000640256 qam27
    20355000000640256 qam28
    213630000005.940256 qam29
    223710000005.840256 qam30
    233790000005.640256 qam31
    243870000005.940256 qam32



    Downstream bonded channels

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

    1Locked40.350
    2Locked40.360
    3Locked40.900
    4Locked40.360
    5Locked40.340
    6Locked40.980
    7Locked40.350
    8Locked40.360
    9Locked40.950
    10Locked40.960
    11Locked40.960
    12Locked40.350
    13Locked40.360
    14Locked40.350
    15Locked40.360
    16Locked40.970
    17Locked40.310
    18Locked40.950
    19Locked40.900
    20Locked40.360
    21Locked40.360
    22Locked40.950
    23Locked40.950
    24Locked40.300
  • NinjaAndy's avatar
    NinjaAndy
    Tuning in
    2 years ago

    Upstream bonded channels

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

    12360000040512064 qam9
    23660000040.8512064 qam3
    33010000040.3512064 qam4
    44310000041512064 qam2
    54960000041.5512064 qam1



    Upstream bonded channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

    1ATDMA0010
    2ATDMA0000
    3ATDMA0000
    4ATDMA0000
    5ATDMA0000
  • NinjaAndy's avatar
    NinjaAndy
    Tuning in
    2 years ago

    General Configuration

    Network access
    Allowed
    Maximum Number of CPEs
    1
    Baseline Privacy
    Enabled
    DOCSIS Mode
    Docsis30
    Config file
    cmreg-vmdg505-bbt057+voc-b.cm



    Primary Downstream Service Flow

    SFID255980
    Max Traffic Rate143750047
    Max Traffic Burst42600
    Min Traffic Rate0



    Primary Upstream Service Flow

    SFID255979
    Max Traffic Rate22000047
    Max Traffic Burst42600
    Min Traffic Rate0
    Max Concatenated Burst42600
    Scheduling TypeBestEffort
  • NinjaAndy's avatar
    NinjaAndy
    Tuning in
    2 years ago

    Network Log

    Time Priority Description

    29/03/2024 15:04:40noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    01/01/1970 00:01:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    29/03/2024 14:54:32noticeNOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    29/03/2024 02:16:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    28/03/2024 08:15:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    27/03/2024 14:25:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:59:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:59:12Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:52:15Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:52:11ErrorService Add Response rejected - Invalid transaction ID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:50:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:49:1Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:33:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 14:32:54Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 13:52:12Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 13:52:10Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 13:50:41Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 13:50:40Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 13:48:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    25/03/2024 13:48:48Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
    • Kath_P's avatar
      Kath_P
      Icon for Forum Team rankForum Team
      2 years ago

      Hi NinjaAndy, 

      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've been having issues with your hub. We've done some checks on the hub from this end and have not found any issues that could account for hub rebooting and connection drop-outs.

      We need you to complete a Pin hole reset of the Hub in an attempt to resolve any unfound issues. Do this by holding a pen in the reset hole on the back of the Hub for 30 seconds. This will reboot the Hub and reset all Hub settings to default. If you have made any changes to the Hub's wireless settings you may need to reconnect your wireless devices to the Hub as the WiFi settings will now be back to default.

      Please let us know how this goes or if you have any further issues. 

      Thanks,

  • Client62's avatar
    Client62
    Alessandro Volta
    2 years ago

    Check the log entry for : 29/03/2024 14:54:32   that could be a clue as to the problem with the Hub 3.

  • NinjaAndy's avatar
    NinjaAndy
    Tuning in
    2 years ago

    Great spot, thank you. I've read that this can be related to a CPU failure. Any idea how I go about getting a new hub?

    I tried pin hole resetting in Jan, and it hasn't fixed the problem.