cancel
Showing results for 
Search instead for 
Did you mean: 

Repeated failed hub update attempts causing downtime

NotMushy
Joining in

Hi all,

For the past few months I have been having issues with my hub 3 attempting to update multiple times a day. The internet connection drops and the lights on the hub indicate it is attempting an update, this usually lasts a few minutes before returning to normal functionality.

From the advice on another post here is my network log:

Network Log

Time Priority Description

06-04-2024 14:15:21 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:11 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:11 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:11 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:11 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:08 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:08 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:08 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:08 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:13:01 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:11:32 notice Illegal - Dropped FORWARD packet: src=2a01:b740:0a18:f000:0000:0000:0000:0001 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:11:32 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:53 notice Illegal - Dropped FORWARD packet: src=2a01:b740:0a18:f000:0000:0000:0000:0001 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:52 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:47 notice Illegal - Dropped FORWARD packet: src=2a01:b740:0a18:f000:0000:0000:0000:0001 MAC=**:**:**:**:**:**;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:42 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:21 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:21 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:20 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

06-04-2024 14:10:20 critical Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

03-04-2024 13:40:54 warning [**:**:**:**:**:**][DFS] Radar signal detected, DFS sequence applied, channel changed from 116 to 44

02-04-2024 14:19:37 warning [**:**:**:**:**:**][DFS] Radar signal detected, DFS sequence applied, channel changed from 116 to 44

31-03-2024 15:42:40 warning [**:**:**:**:**:**][DFS] Radar signal detected, DFS sequence applied, channel changed from 116 to 44

 

 

 

5 REPLIES 5

Client62
Legend

Hub 3 are usually on Software version: 9.1.2208.100 & have been for 12+ months.

Might be an idea to set the 5GHz Wi-Fi out of the DFS channels, refer to the bottom 3 log entries.

Im not sure if im missing something but my hub admin info page shows this instead of the plain numbers software version, I assume I should factory reset to try and update my software version.

Hardware version : 5.01
Software version : CH7465LG-NCIP-6.15.31p1-NOSH

Client62
Legend

We are Essex in the UK & our Hub 3 is a Hardware version 10,
some in the UK have HW v11 but the same software.

Are you a customer of VM in the UK or the ROI ?


In the ROI

Client62
Legend

You are going to have to contact the VM ROI support service for proper assistance.
This forum is focuses only on the UK service.  Bonne chance, mon ami !