14-07-2021 18:06 - edited 14-07-2021 18:09
Yet again the Hub3 is dying.
it will randomly reboot, often this factory resets the device, so I have to set up the wifi & passwords again. but worse is the fact the time from it turning off until I can log in is 19 mins!!!
that is unacceptable, if I upload the config it has to reboot to take effect making it 40 mins before I can reconnect with wifi.
the hub 3 is obviously not up to the job, so I am looking for a replacement, what can I use to connect from the Coax to my switch?
The Wifi, DNS & DHCP is all been offloaded to other systems, but the hardware still can't keep the connection alive.
this is the second Hub 3 to take 20 mins to boot, this one is 2 months old.
Answered! Go to Answer
on 14-07-2021 19:26
14-07-2021 19:35 - edited 14-07-2021 19:41
@-tony- wrote:most of what you have connected is way beyond me but i am puzzled when you say you have offloaded the DHCP from the hub - maybe i have that wrong - with the hub in router mode it is controlling DHCP - whatever you have down the line is in effect double nat and that can give problems
i say again its way beyond me but thats just seems wrong - happy to have it explained
In settings > advanced > DHCP > DHCPv4 server - Disabled.
This way I can set the DHCP lease time to 6 hrs, & have static entries for the local devices (my devices that may not be on at the time etc).
When I build a Mobile, I build configure, package & send, so a 24hr IP lease is not needed & I can control the DHCP leases via RSAT controller.
I did have the hub (old one) in modem mode.
Remove all cables, turn off power & wait till white solid light & no green or green flashing 19-20 mins.
just 1 device connected via cat6 running ping -t response after a min but time jumping from 2ms to 958ms & periods of time out. until around 17 mins.
if I open the landing page I either get "someone is already logged in" or the blue wallpaper version until around the 15 min mark, but attempts to log in are met with "page not responding".
on 14-07-2021 19:46
@jbrennand wrote:
So is there a Tech visit tomorrow?
If so, they will disconnect all your 3d party equipment (none of that is their concern or within their balliwick) and test the Hub's initiation parameters and when done,its network connection status on their laptop/phone. Interesting to see what they say about that.
Completely understandable, I strip tested down to 0 connections & 1 device cable only. to rule out my systems, checked the logs on the firewall, switch & server to look for any related issues.
Last time I noted the settings then powered down the Router for 12 hrs, factory reset & reapplied the settings, worked for about 2 weeks then it rebooted again.
on 14-07-2021 19:50
on 14-07-2021 19:52
@Riffraffs wrote:
@-tony- wrote:most of what you have connected is way beyond me but i am puzzled when you say you have offloaded the DHCP from the hub - maybe i have that wrong - with the hub in router mode it is controlling DHCP - whatever you have down the line is in effect double nat and that can give problems
i say again its way beyond me but thats just seems wrong - happy to have it explained
In settings > advanced > DHCP > DHCPv4 server - Disabled.
This way I can set the DHCP lease time to 6 hrs, & have static entries for the local devices (my devices that may not be on at the time etc).
When I build a Mobile, I build configure, package & send, so a 24hr IP lease is not needed & I can control the DHCP leases via RSAT controller.
I did have the hub (old one) in modem mode.
Remove all cables, turn off power & wait till white solid light & no green or green flashing 19-20 mins.
just 1 device connected via cat6 running ping -t response after a min but time jumping from 2ms to 958ms & periods of time out. until around 17 mins.
if I open the landing page I either get "someone is already logged in" or the blue wallpaper version until around the 15 min mark, but attempts to log in are met with "page not responding".
ok - i am leaning or i think i am so go with me - if the DHCP server is turned off how can you have 3 devices connected to the hub3 - surely they cannot get ip addresses from the hub
not sure i am going to understand but try me
as to the 20 min reboot time - not sure on that - there are posts that say power on and leave the hub 20min to half an hour but thats usually on first install when the hub updates its firmware - i can only postulate that a setting is wrong - if you are in a testing mood reste the hub to defaults and try a power up again
on 14-07-2021 20:00
@-tony- wrote:
@Riffraffs wrote:
@-tony- wrote:most of what you have connected is way beyond me but i am puzzled when you say you have offloaded the DHCP from the hub - maybe i have that wrong - with the hub in router mode it is controlling DHCP - whatever you have down the line is in effect double nat and that can give problems
i say again its way beyond me but thats just seems wrong - happy to have it explained
In settings > advanced > DHCP > DHCPv4 server - Disabled.
This way I can set the DHCP lease time to 6 hrs, & have static entries for the local devices (my devices that may not be on at the time etc).
When I build a Mobile, I build configure, package & send, so a 24hr IP lease is not needed & I can control the DHCP leases via RSAT controller.
I did have the hub (old one) in modem mode.
Remove all cables, turn off power & wait till white solid light & no green or green flashing 19-20 mins.
just 1 device connected via cat6 running ping -t response after a min but time jumping from 2ms to 958ms & periods of time out. until around 17 mins.
if I open the landing page I either get "someone is already logged in" or the blue wallpaper version until around the 15 min mark, but attempts to log in are met with "page not responding".ok - i am leaning or i think i am so go with me - if the DHCP server is turned off how can you have 3 devices connected to the hub3 - surely they cannot get ip addresses from the hub
not sure i am going to understand but try me
as to the 20 min reboot time - not sure on that - there are posts that say power on and leave the hub 20min to half an hour but thats usually on first install when the hub updates its firmware - i can only postulate that a setting is wrong - if you are in a testing mood reste the hub to defaults and try a power up again
Correct, they do not get the IP's from the Hub, the 3 devices have static IP addresses assigned (in windows or dashboard), rest of the network gets their IP from Windows Server running DHCP, Domain Controller & DNS.
the Hub is listed as the gateway IP address, nothing more.
3 reboots today, none under 18 mins, all were power removed wait 5 mins. 2 caused a factory reset.
on 14-07-2021 20:09
aaaaaaahhhhhh - i understand - well i think i do - i had no idea you could do that - i know you can set static ip addys in windows etc but i just thought that over rode any that were given by the hub
its down to the tech tomorrow i guess - maybe its as simple as a faulty hub - you can push for a hub4 - i have one and just checked the setting is there in advanced - thats always worth knowing as VM tend to change things
so will read with interest as things go forward
on 14-07-2021 20:14
I WAS getting the logs, but the router rebooted & is now showing update in progress & a family pic rather than the red virgin logo
on 14-07-2021 20:18
well for what its worth i think its unhappy - read faulty if you want - thats a first install thing - it would explain the 20min reboot time as its going back to the VM servers for the latest firmware every time it boots
its not as bad as one that a user had the other week - that had managed to dump the VM firmware and booted up with the Arris firmware logo
on 14-07-2021 20:20
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 419000000 -2 38 256 qam 32
2 203000000 -0.5 38 256 qam 9
3 211000000 -0.5 38 256 qam 10
4 219000000 -0.7 38 256 qam 11
5 227000000 -0.7 38 256 qam 12
6 235000000 -1 38 256 qam 13
7 243000000 -1.2 38 256 qam 14
8 251000000 -1.5 38 256 qam 15
9 259000000 -1.5 38 256 qam 16
10 267000000 -2 38 256 qam 17
11 275000000 -2.2 38 256 qam 18
12 283000000 -2.2 38 256 qam 19
13 291000000 -2.5 38 256 qam 20
14 299000000 -2.2 38 256 qam 21
15 307000000 -2.2 38 256 qam 22
16 315000000 -2.2 38 256 qam 23
17 323000000 -2.2 38 256 qam 24
18 363000000 -2 38 256 qam 25
19 371000000 -2.2 38 256 qam 26
20 379000000 -1.7 38 256 qam 27
21 387000000 -1.9 38 256 qam 28
22 395000000 -1.9 38 256 qam 29
23 403000000 -1.9 38 256 qam 30
24 411000000 -1.7 38 256 qam 31
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 2 0
2 Locked 38.6 6 0
3 Locked 38.9 6 0
4 Locked 38.9 5 0
5 Locked 38.6 20 0
6 Locked 38.9 10 0
7 Locked 38.9 6 0
8 Locked 38.9 5 0
9 Locked 38.9 5 0
10 Locked 38.9 8 0
11 Locked 38.9 6 0
12 Locked 38.6 13 0
13 Locked 38.9 5 0
14 Locked 38.6 6 0
15 Locked 38.9 6 0
16 Locked 38.9 5 0
17 Locked 38.6 4 0
18 Locked 38.6 1 0
19 Locked 38.6 7 0
20 Locked 38.9 0 0
21 Locked 38.6 5 0
22 Locked 38.6 6 0
23 Locked 38.9 5 0
24 Locked 38.9 6 0
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32600021 38 5120 64 qam 5
2 39400004 38 5120 64 qam 4
3 46199932 38 5120 64 qam 3
4 53699988 38 5120 64 qam 2
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 1 0
TimePriorityDescription14/07/2021 20:13:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 20:13:8Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 20:06:35noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 14:46:23noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 14:31:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 12:15:22noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 12:12:3Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 12:08:38noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 12:05:51Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;14/07/2021 01:31:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;13/07/2021 23:39:39noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;13/07/2021 23:39:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;13/07/2021 23:39:37ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;09/07/2021 07:58:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;09/07/2021 04:09:38noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;09/07/2021 04:09:38ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;06/07/2021 12:37:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;06/07/2021 11:45:13noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;05/07/2021 16:09:37noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;