on 23-07-2024 12:09
Please check the account associated with the IP Address of this post.
Having issues with the hub restarting between the hours of 02:00~2:30am. Strange thing is it seems to only be happening on Monday/Tuesday/Wednesday/Thursday. Other days are random. Happening for a few weeks now. At first thought it might be a firmware update issue, so performed a full hard reset, but didn't fix, carried on happening. Checked all connections inside to make sure nothing is loose.
Network logs don't seem to have any timestamps around the time it happens.
Check service status sometimes say there's an issue, check back in 24hours, then says ok, then says check back in 24hours, but never gives a reason.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 203000000 | 5.9 | 40 | 256 qam | 9 |
2 | 211000000 | 5.8 | 38 | 256 qam | 10 |
3 | 219000000 | 5.8 | 40 | 256 qam | 11 |
4 | 227000000 | 5.8 | 40 | 256 qam | 12 |
5 | 235000000 | 5.8 | 40 | 256 qam | 13 |
6 | 243000000 | 5.9 | 40 | 256 qam | 14 |
7 | 251000000 | 5.6 | 40 | 256 qam | 15 |
8 | 259000000 | 5.8 | 40 | 256 qam | 16 |
9 | 267000000 | 6 | 40 | 256 qam | 17 |
10 | 275000000 | 6 | 40 | 256 qam | 18 |
11 | 283000000 | 6.1 | 40 | 256 qam | 19 |
12 | 291000000 | 6 | 40 | 256 qam | 20 |
13 | 299000000 | 6.3 | 38 | 256 qam | 21 |
14 | 307000000 | 6.1 | 40 | 256 qam | 22 |
15 | 315000000 | 6.1 | 40 | 256 qam | 23 |
16 | 323000000 | 6 | 40 | 256 qam | 24 |
17 | 331000000 | 6.3 | 40 | 256 qam | 25 |
18 | 339000000 | 6 | 40 | 256 qam | 26 |
19 | 347000000 | 5.8 | 40 | 256 qam | 27 |
20 | 355000000 | 5.5 | 40 | 256 qam | 28 |
21 | 363000000 | 5.5 | 40 | 256 qam | 29 |
22 | 371000000 | 5.9 | 40 | 256 qam | 30 |
23 | 379000000 | 5.9 | 40 | 256 qam | 31 |
24 | 387000000 | 5.6 | 40 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 7 | 0 |
2 | Locked | 38.9 | 9 | 0 |
3 | Locked | 40.9 | 8 | 0 |
4 | Locked | 40.3 | 8 | 0 |
5 | Locked | 40.3 | 11 | 0 |
6 | Locked | 40.3 | 6 | 0 |
7 | Locked | 40.9 | 8 | 0 |
8 | Locked | 40.3 | 8 | 0 |
9 | Locked | 40.3 | 10 | 0 |
10 | Locked | 40.3 | 6 | 0 |
11 | Locked | 40.3 | 6 | 0 |
12 | Locked | 40.3 | 11 | 0 |
13 | Locked | 38.9 | 19 | 0 |
14 | Locked | 40.3 | 7 | 0 |
15 | Locked | 40.3 | 10 | 0 |
16 | Locked | 40.3 | 10 | 0 |
17 | Locked | 40.3 | 5 | 0 |
18 | Locked | 40.3 | 8 | 0 |
19 | Locked | 40.3 | 7 | 0 |
20 | Locked | 40.3 | 8 | 0 |
21 | Locked | 40.3 | 10 | 0 |
22 | Locked | 40.3 | 10 | 0 |
23 | Locked | 40.3 | 6 | 0 |
24 | Locked | 40.3 | 8 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 23600030 | 42.3 | 5120 | 64 qam | 11 |
2 | 36599995 | 43.3 | 5120 | 64 qam | 7 |
3 | 30100000 | 42.8 | 5120 | 64 qam | 8 |
4 | 43100000 | 43.8 | 5120 | 64 qam | 6 |
5 | 49600000 | 44.5 | 5120 | 64 qam | 5 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
Time Priority Description
01/01/1970 00:01:45 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
21/07/2024 13:20:59 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:41 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
17/07/2024 23:20:5 | notice | LAN login Success;CM-QOS=1.1;CM-VER=3.0; |
14/07/2024 16:47:14 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
14/07/2024 13:05:5 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:42 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
12/07/2024 00:28:16 | notice | LAN login Success;CM-QOS=1.1;CM-VER=3.0; |
12/07/2024 00:27:29 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-QOS=1.1;CM-VER=3.0; |
05/07/2024 22:44:33 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
04/07/2024 17:45:2 | notice | LAN login Success;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:44 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
04/07/2024 17:00:45 | notice | LAN login Success;CM-QOS=1.1;CM-VER=3.0; |
02/07/2024 04:56:56 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
01/07/2024 19:04:12 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-QOS=1.1;CM-VER=3.0; |
29/06/2024 02:48:2 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
28/06/2024 07:04:12 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-QOS=1.1;CM-VER=3.0; |
25/06/2024 10:47:45 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
24/06/2024 19:04:12 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-QOS=1.1;CM-VER=3.0; |
22/06/2024 14:02:1 | critical | No Ranging Response received - T3 time-out;CM-QOS=1.1;CM-VER=3.0; |
Please check the account associated with the IP Address of this post.
on 21-11-2024 17:26
Yes it has the same days Tuesday Wednesday Thursday at 2am... however not last night I have had this before strangely no discussions this time and no advice. last time was September and STILL nobody has replied on my post about this that is two weeks old... in September I had to have an engineer out to do nothing other than raise it with networks as you can't.....
on 21-11-2024 17:27
on 24-11-2024 12:02
Hi @fizz thanks for your reply here.
If you've mentioned it's been resolved now that's great news! Please let me know if you need any further help 😊
Many thanks
on 24-11-2024 20:46
on 24-11-2024 20:47
a month ago
a month ago
.@Sabrina_B well nothing now but nobody even looked at my thread about the 2am reboots that I raised three weeks ago but I had plenty of replies to this one This stopped last Thursday..
4 weeks ago
Glad to hear that this seems to be resolved for you now.
We would try and keep support within one thread, so if you've started being supported on another thread we'd look to keep that support within one area to save any confusion, repeated questions and multiple requests.
Please let us know if you are having any further issues or have any questions at all. We'll be here to help on the community forums if needed.