Forum Discussion

orchyRG's avatar
orchyRG
Tuning in
18 days ago

New Hub 5, got some serious issues

Hey all,

 

I've got a serious broadband issue which is causing me to not have internet.

I've been sent a new Hub 5 which is replacing a Hub 3. It was meant to arrive on December 20th but didn't arrive till yesterday. My internet connection disappeared on my old router last night. So I thought that was normal and I'd set up the new router in the morning.

Set up the hub 5 this morning and it doesn't want to work. It turns on, and seems to keep just rebooting over and over. I've done multiple 60 seconds factory resets and power cycles. It just does the same.

I briefly see the SSID but it will either disappear or hang around for a minute. When I can see it. It will not authenticate me trying to connect to the WiFi with the correct password.

 

This has been happening all day.

Has anyone experienced this or can offer anything I haven't tried yet?

  • I have an update!

    What the engineer thinks happened.

    The box outside was connected but loose. With the bad weather we've had over the last week it would have made the hard line intermittent. The router was trying to update/get activation and it failed. Essentially killed the router.

    So he has tightened up all the connections, some were very loose. Removed an old splitter. Connected up a new router.

    All seems good now.

  • legacy1's avatar
    legacy1
    Alessandro Volta

    Call VM to activate hub it should work auto but if the time you get the hub late it can not work 

      • newapollo's avatar
        newapollo
        Very Insightful Person

        Have you tried factory resetting the hub 5? 

        Remove all ethernet cables from the hub and then press the press the reset button on the base of the hub for 60 seconds and allow the Hub around 5 minutes to reboot

    • orchyRG's avatar
      orchyRG
      Tuning in

      I suspect it will be a bigger problem though as I've noticed in the logs it keeps restarting due to a kernel panic.

      • newapollo's avatar
        newapollo
        Very Insightful Person

        Hi again orchyRG 

        The picture you posted of the network logs was automatically rejected by the forum systems as it contained your MAC address. It's also very difficult to actually read the info when it's in that format as it's too small.

        When you go to Advanced Settings > Tools > Network Status, You need to copy paste the info from the Downstream, Upstream, Configuration and Network logs.  This will aid VM forum staff and the fantastic forum guru's to help you get a working connection.

         

  • Tudor's avatar
    Tudor
    Very Insightful Person

    Try connecting to it via an Ethernet cable, you should be able to get to the settings, if not it’s not activated. Don’t use WiFi. 

  • General Configuration

    Network access

    Allowed

    Maximum Number of CPEs

    1

    Baseline Privacy

    Enabled

    DOCSIS Mode

    3.1

    Config file

    UBsgvca69834ncxv9873254k;

    Primary Downstream Service Flow

    SFID

    30492

    Max Traffic Rate

    402500089 bps

    Max Traffic Burst

    42600bytes

    Min Traffic Rate

    0 bps

    Primary Upstream Service Flow

    SFID

    30493

    Max Traffic Rate

    38500089 bps

    Max Traffic Burst

    42600bytes

    Min Traffic Rate

    0 bps

    Max Concatenated Burst

    42600bytes

    Scheduling Type

    Best Effort

     

  • Network Log

    Time

    Priority

    Description

    02-01-2025 22:23:16

    notice

    GUI Login Status - Login Success from LAN interface

    02-01-2025 22:18:26

    notice

    GUI Login Status - Login Success from LAN interface

    02-01-2025 22:14:07

    notice

    US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:14:07

    warning

    DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:14:03

    notice

    REGISTRATION COMPLETE - Waiting for Operational status

    02-01-2025 22:13:57

    warning

    RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:57

    warning

    REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:57

    warning

    Dynamic Range Window violation

    02-01-2025 22:13:51

    notice

    DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:50

    notice

    TLV-11 - unrecognized OID;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:44

    warning

    DHCP WARNING - Non-critical field invalid in response ;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:42

    notice

    Honoring MDD; IP provisioning mode = IPv4

    02-01-2025 22:13:24

    critical

    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:23

    critical

    Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:15

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:13:13

    warning

    B-INIT-RNG Failure - Retries exceeded;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:11:12

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:11:11

    warning

    B-INIT-RNG Failure - Retries exceeded;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:08:57

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:08:57

    warning

    B-INIT-RNG Failure - Retries exceeded;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:06:45

    warning

    B-INIT-RNG Failure - Retries exceeded;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:06:45

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:05:01

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:04:56

    critical

    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 22:04:56

    critical

    Cable Modem Reboot because of - kernel-panic

    02-01-2025 21:59:57

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 21:59:50

    critical

    Cable Modem Reboot because of - kernel-panic

    02-01-2025 21:59:50

    critical

    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 21:55:14

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 21:55:09

    critical

    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 21:55:08

    critical

    Cable Modem Reboot because of - kernel-panic

    02-01-2025 21:42:31

    critical

    No Ranging Response received - T3 time-out;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 21:42:24

    critical

    SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=omitted;CMTS-MAC=omitted;CM-QOS=1.1;CM-VER=3.1;

    02-01-2025 21:42:23

    critical

    Cable Modem Reboot because of - kernel-panic

    Hopefully this will help?

    Thanking you

  • I have an update!

    What the engineer thinks happened.

    The box outside was connected but loose. With the bad weather we've had over the last week it would have made the hard line intermittent. The router was trying to update/get activation and it failed. Essentially killed the router.

    So he has tightened up all the connections, some were very loose. Removed an old splitter. Connected up a new router.

    All seems good now.

    • orchyRG's avatar
      orchyRG
      Tuning in

      Thanks everyone for your help and suggestions 😀

    • newapollo's avatar
      newapollo
      Very Insightful Person

      Thanks for updating the thread orchyRG  Glad to see you now have a working connection.

      Keep an eye on how things go and any problems just holler.