on 05-09-2024 12:26
I’m experiencing an issue with my WiFi connection. My Ethernet connection works perfectly, but I can’t seem to get my WiFi to work, it's not showing on the list. I'm using hub 3 m500.
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz) | 331000000 | Locked |
Ranged Upstream Channel (Hz) | 49600000 | Locked |
Provisioning State | Online |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 5.5 | 38 | 256 qam | 25 |
2 | 139000000 | 7.3 | 38 | 256 qam | 1 |
3 | 147000000 | 6.5 | 37 | 256 qam | 2 |
4 | 155000000 | 5.9 | 38 | 256 qam | 3 |
5 | 163000000 | 6 | 37 | 256 qam | 4 |
6 | 171000000 | 5.8 | 37 | 256 qam | 5 |
7 | 179000000 | 5.9 | 37 | 256 qam | 6 |
8 | 187000000 | 5.8 | 37 | 256 qam | 7 |
9 | 195000000 | 5.8 | 38 | 256 qam | 8 |
10 | 203000000 | 5.8 | 38 | 256 qam | 9 |
11 | 211000000 | 5.5 | 37 | 256 qam | 10 |
12 | 219000000 | 5.5 | 38 | 256 qam | 11 |
13 | 227000000 | 5.4 | 37 | 256 qam | 12 |
14 | 235000000 | 5.3 | 37 | 256 qam | 13 |
15 | 243000000 | 5 | 38 | 256 qam | 14 |
16 | 251000000 | 5 | 38 | 256 qam | 15 |
17 | 259000000 | 5.1 | 38 | 256 qam | 16 |
18 | 339000000 | 6 | 38 | 256 qam | 26 |
19 | 347000000 | 6 | 38 | 256 qam | 27 |
20 | 355000000 | 6 | 38 | 256 qam | 28 |
21 | 363000000 | 5.6 | 38 | 256 qam | 29 |
22 | 371000000 | 5.5 | 38 | 256 qam | 30 |
23 | 379000000 | 5.5 | 38 | 256 qam | 31 |
24 | 387000000 | 5.9 | 38 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 300 | 56 |
2 | Locked | 38.6 | 204 | 0 |
3 | Locked | 37.6 | 238 | 0 |
4 | Locked | 38.6 | 228 | 13 |
5 | Locked | 37.6 | 172 | 25 |
6 | Locked | 37.6 | 229 | 13 |
7 | Locked | 37.6 | 213 | 0 |
8 | Locked | 37.6 | 197 | 0 |
9 | Locked | 38.6 | 222 | 0 |
10 | Locked | 38.6 | 230 | 0 |
11 | Locked | 37.6 | 290 | 0 |
12 | Locked | 38.6 | 251 | 0 |
13 | Locked | 37.6 | 275 | 11 |
14 | Locked | 37.3 | 278 | 0 |
15 | Locked | 38.6 | 324 | 0 |
16 | Locked | 38.6 | 260 | 0 |
17 | Locked | 38.6 | 300 | 0 |
18 | Locked | 38.6 | 416 | 47 |
19 | Locked | 38.6 | 399 | 2 |
20 | Locked | 38.6 | 471 | 12 |
21 | Locked | 38.9 | 391 | 0 |
22 | Locked | 38.6 | 402 | 13 |
23 | Locked | 38.9 | 364 | 14 |
24 | Locked | 38.6 | 352 | 32 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 49600000 | 40 | 5120 | 64 qam | 1 |
2 | 36600000 | 39.8 | 5120 | 64 qam | 3 |
3 | 23600000 | 38.8 | 5120 | 64 qam | 5 |
4 | 43100054 | 39.8 | 5120 | 64 qam | 2 |
5 | 30100000 | 39.3 | 5120 | 64 qam | 4 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 1 | 0 |
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | cmreg-vmdg505-bbt053-b.cm |
SFID | 4844 |
Max Traffic Rate | 575000085 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 4843 |
Max Traffic Rate | 55000085 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
Answered! Go to Answer
06-09-2024 12:40 - edited 06-09-2024 12:41
Check the Wireless Signal page of the Hub 3 this is at :
Hub 3 menu : Advanced settings >> Wireless >> Wireless signal
For comparison below are our settings and these are working
on 05-09-2024 12:32
Time Priority Description
05/09/2024 09:45:50 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:45:7 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:44:42 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:10:24 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:05:31 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 03:44:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/09/2024 07:41:14 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 19:29:43 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 15:32:23 | notice | Unit has been restored to factory defaults from a software issued command;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 12:48:49 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 12:17:53 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 12:11:44 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 12:09:32 | critical | TLV-11 - Failed to set duplicate elements;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 11:10:20 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 10:52:17 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/09/2024 09:58:35 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 06-09-2024 12:21
no wifi still for almost a week now
06-09-2024 12:40 - edited 06-09-2024 12:41
Check the Wireless Signal page of the Hub 3 this is at :
Hub 3 menu : Advanced settings >> Wireless >> Wireless signal
For comparison below are our settings and these are working
on 06-09-2024 13:32
Hub 3 state of health of the Intel Atom processor.
The "NOTICE ATOM" family of messages refer to the Intel Atom processor used in the Hub 3.
The "restarted due to" various reasons, are not seen in our Hub 3 log and may indicate the Hub 3 needs to be replaced especially as in the log clip below the restarts occurred three times in under one hour.
5/09/2024 08:45:7 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:44:42 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:10:24 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 06-09-2024 17:18
the settings you show me worked thank you
here's today's logs
06/09/2024 16:13:56 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/09/2024 16:13:21 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/09/2024 15:53:43 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/09/2024 14:07:18 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/09/2024 08:47:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 21:51:40 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 21:34:7 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 21:18:53 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 21:13:58 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 20:54:38 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 16:27:49 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 15:50:13 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 09:45:50 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:45:7 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:44:42 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:10:24 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 08:05:31 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/09/2024 03:44:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 06-09-2024 20:33
Good that you've got WiFi restored but, as @Client62 has said, your Hub 3 needs replacing. Have a read of this:
It can happen to any Hub 3 and what you've got will cause breaks in service.
on 06-09-2024 21:54
yeah WiFi's gone again, how do I get my hub 3 replaced?
on 06-09-2024 22:00
Through this thread, ask the Forum Team to arrange a replacement for the Hub 3 because of the the ATOM panics. They'll arrange a technician - he'll likely swap in a Hub 3 and pretend that he doesn't have a Hub 4 or Hub 5 on the van. Resist that - the whole point is to come off that Hub 3. Keep us posted.
on 07-09-2024 11:10
I need a replacement for my hub3 because of the ATOM panics