Logs from Hub 3, WiFi disconnects (usually at night)

[rjclark71]

Any Guru capable of understanding the below?

Or are fairly usual Error messages.

The wifi is OK usually 80% of the time.

Thanks in advance

15/10/2021 00:09:18 notice NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2021 00:09:4 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 19:09:5 notice NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 19:05:44 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 02:58:22 notice NOTICE ATOM is restarted as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 02:09:17 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/10/2021 02:19:43 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/10/2021 14:09:17 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 18:35:23 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 02:09:17 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/10/2021 23:48:12 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/10/2021 16:13:45 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/10/2021 10:44:51 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2021 09:06:18 critical TFTP Request Retries exceeded, CM unable to register
30/09/2021 09:06:18 critical TFTP failed - Request sent - No Response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2021 08:58:33 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2021 08:54:56 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2021 08:51:58 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2021 08:51:54 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/09/2021 08:51:54 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt062-b.cm

Primary Downstream Service Flow
SFID 89174
Max Traffic Rate 402500089
Max Traffic Burst 42600
Min Traffic Rate 0

Primary Upstream Service Flow
SFID 89173
Max Traffic Rate 38500089
Max Traffic Burst 42600
Min Traffic Rate 0
Max Concatenated Burst 42600

[Andrew-G · Accepted solution]

Most of the error messages are normal in terms of type and frequency for a cable connection, but the repeated "Atom is restarting" message isn't.  We've never got to the bottom of what and why, and VM have been asked and can't provide an answer.  Our best guess is a failing hub firmware process, and that could be the software needs resetting, or it could be a terminal fault on the hub caused by corrupt RAM, NAND or a processor fault.

Try a pinhole reset, any custom settings will be lost, and you'll need the eight digit settings password afterwards.  If you continue to poor connection and the "Atom is restarting" message reappears you'll need the hub replacing.  Best to stick with the forum to achieve that, VM's telephone customer support is **** and their script doesn't extend to network log messages.

[Martin_N]

Hi rjclark71,

Thank you for your post. I'm very sorry to hear about the issue you're having.

Have you been able to try the PIN hole reset as recommend?

^Martin