cancel
Showing results for 
Search instead for 
Did you mean: 

Wifi goes down frequently - DHCP renew, No response T3 and ATOM self healing

Noobify
On our wavelength

Hi Experts,

I'm on Hub 3. Experiencing terrible wifi stability which disappears almost twice a day and comes back up once restarted The technician who visited couldn't resolve with usual cable check, replace with another Hub 3 splitter check etc. Here are the logs: - any solutions or advice ? 

19 REPLIES 19

legacy1
Alessandro Volta

Your BQM is fine I suggest you look at getting your own wifi router with 1Gb ports and use hub in modem mode 

---------------------------------------------------------------

There is a hardware fault with the HUB, so putting it in modem mode probably won't resolve the issue.

Noobify
On our wavelength

The second technician came today and changed the upstream power levels, said the Hub is fine. Fingers crossed, let's see. In any case planning to use the modem mode in future

Noobify
On our wavelength

"ATOM is restarted" continues, it must be the processor in the Hub. Third technician booked, then I can get freedom from this amazingly reliable service !

Hi @Noobify 👋.

Thanks for reaching out to us. Apologies for the issues that you have had with your hub, I can see you have stated you will be having another engineer, and have spoken about modem mode, could you please on the day that you have the engineer, should you get a replacement Hub, do not switch into modem mode straight away. We would need the Hub to complete its initial set up as well as any and all updates as it has been in storage since we have released updates. This would need to be in router mode for 24 hours to allow for it to be at maximum performance, 

Sabrina

Noobify
On our wavelength

Moved to a Mesh with Hub 3 in modem mode, the stability has improved but issue still exists, here are the network log again, in case any one can find a cause, may be @Sabrina_B ?

Time Priority Description

05/04/2024 20:59:47noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/04/2024 08:28:40noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/04/2024 08:28:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/04/2024 07:14:32criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/03/2024 01:48:22noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/03/2024 01:48:22ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/03/2024 12:45:42criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/03/2024 12:29:3noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/03/2024 12:29:3ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/03/2024 09:36:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2024 22:35:47noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/03/2024 22:35:47ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 14:30:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 13:43:58noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 13:33:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 10:35:47noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 10:35:47ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 09:46:1noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 09:45:48Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/03/2024 09:18:21noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Noobify
On our wavelength

Upstream bonded channels

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

13660000035512064 qam11
22360000031512064 qam13
33010000033512064 qam12
44310000036.5512064 qam10
54960000038512064 qam9



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0010
3ATDMA0000
4ATDMA0010
5ATDMA0010

Noobify
On our wavelength

Downstream bonded channels

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

1291000000336256 qam20
21390000007.937256 qam1
31470000007.137256 qam2
41550000006.637256 qam3
5163000000637256 qam4
6171000000637256 qam5
71790000005.637256 qam6
81870000005.537256 qam7
9195000000537256 qam8
102030000004.536256 qam9
11211000000436256 qam10
122190000003.537256 qam11
132270000003.536256 qam12
142350000003.536256 qam13
152430000002.536256 qam14
16251000000236256 qam15
17259000000236256 qam16
182670000002.437256 qam17
192750000002.536256 qam18
202830000002.936256 qam19
212990000003.536256 qam21
223070000003.537256 qam22
233150000003.537256 qam23
243230000003.737256 qam24



Downstream bonded channels

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

1Locked36.6530
2Locked37.359192
3Locked37.3610
4Locked37.3840
5Locked37.3750
6Locked37.3490
7Locked37.6610
8Locked37.3590
9Locked37.3450
10Locked36.6660
11Locked36.6690
12Locked37.3660
13Locked36.6520
14Locked36.6790
15Locked36.6770
16Locked36.61200
17Locked36.61010
18Locked37.31080
19Locked36.61040
20Locked36.6560
21Locked36.6680
22Locked37.3520
23Locked37.6630
24Locked37.6830

Sephiroth
Alessandro Volta

The upstream power is fine, actually.  The power level from Hub is commanded by the VM end and is contingent on whether or not the VM end can read the keep-alive messages from the Hub.  In modem mode, the ATOM messages are unlikely to occur because the (wretched) Hub 3 has nothing to do other than act as a bridge to your router.

The DHCP Renew messages are passive and you don’t need to worry about them.

So, in terms of your experience, what is going wrong now?

Seph - ( DEFROCKED - My advice is at your risk)

Noobify
On our wavelength

Thanks so much !