on 27-07-2021 18:03
No Ranging Response; Frequent Drop outs; RCS Partial Service - daily.
Hoping someone can help.
27/07/2021 16:25:27 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 07:56:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 06:02:50 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/07/2021 06:02:50 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/07/2021 17:37:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:16:6 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:16:1 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:56 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:55 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:55 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:53 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:53 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 09:15:39 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/07/2021 00:44:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 03:27:57 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/07/2021 03:27:57 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/07/2021 13:09:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/07/2021 07:21:46 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/07/2021 21:48:16 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 402750000 | -4.2 | 37 | 256 qam | 30 |
2 | 202750000 | -2.7 | 37 | 256 qam | 9 |
3 | 210750000 | -2.7 | 37 | 256 qam | 10 |
4 | 218750000 | -2.7 | 37 | 256 qam | 11 |
5 | 226750000 | -2.7 | 38 | 256 qam | 12 |
6 | 234750000 | -2.7 | 37 | 256 qam | 13 |
7 | 242750000 | -2.9 | 37 | 256 qam | 14 |
8 | 250750000 | -3 | 37 | 256 qam | 15 |
9 | 258750000 | -2.7 | 37 | 256 qam | 16 |
10 | 266750000 | -2.7 | 37 | 256 qam | 17 |
11 | 274750000 | -2.7 | 38 | 256 qam | 18 |
12 | 282750000 | -2.9 | 37 | 256 qam | 19 |
13 | 290750000 | -3 | 37 | 256 qam | 20 |
14 | 298750000 | -3.2 | 37 | 256 qam | 21 |
15 | 306750000 | -3.2 | 37 | 256 qam | 22 |
16 | 314750000 | -3 | 37 | 256 qam | 23 |
17 | 322750000 | -3.2 | 37 | 256 qam | 24 |
18 | 330750000 | -3.4 | 37 | 256 qam | 25 |
19 | 370750000 | -3.7 | 37 | 256 qam | 26 |
20 | 378750000 | -3.9 | 37 | 256 qam | 27 |
21 | 386750000 | -4.2 | 37 | 256 qam | 28 |
22 | 394750000 | -4.2 | 37 | 256 qam | 29 |
23 | 410750000 | -4 | 37 | 256 qam | 31 |
24 | 418750000 | -4.2 | 37 | 256 qam | 32 |
1 | Locked | 37.3 | 13 | 0 |
2 | Locked | 37.3 | 13 | 0 |
3 | Locked | 37.6 | 15 | 0 |
4 | Locked | 37.6 | 6 | 0 |
5 | Locked | 38.6 | 10 | 0 |
6 | Locked | 37.6 | 7 | 0 |
7 | Locked | 37.6 | 10 | 0 |
8 | Locked | 37.6 | 8 | 0 |
9 | Locked | 37.3 | 9 | 0 |
10 | Locked | 37.3 | 14 | 0 |
11 | Locked | 38.6 | 9 | 0 |
12 | Locked | 37.9 | 8 | 0 |
13 | Locked | 37.6 | 16 | 0 |
14 | Locked | 37.6 | 24 | 0 |
15 | Locked | 37.6 | 23 | 0 |
16 | Locked | 37.6 | 24 | 0 |
17 | Locked | 37.3 | 21 | 0 |
18 | Locked | 37.6 | 12 | 0 |
19 | Locked | 37.6 | 9 | 0 |
20 | Locked | 37.6 | 11 | 0 |
21 | Locked | 37.3 | 9 | 0 |
22 | Locked | 37.6 | 9 | 0 |
23 | Locked | 37.6 | 15 | 0 |
24 | Locked | 37.6 | 10 | 0 |
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 44.8 | 5120 | 64 qam | 5 |
2 | 25799961 | 43.3 | 5120 | 64 qam | 4 |
3 | 32599996 | 43.3 | 5120 | 64 qam | 3 |
4 | 39399998 | 44.8 | 5120 | 64 qam | 2 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 13-08-2021 17:09
So I plugged my TP-link router back in to the Hub3 via Ethernet with the Hub still in router mode and with the TP-link broadcasting as a separate SSID so that I had two separate WiFi networks running from different devices albeit both fed from the same Hub.
Today I had another complete loss of Hub3 WiFi, the SSID just disappeared from the available connections as though someone had stopped and restarted the WiFi. I switched my laptop connection instantly to the TP-link and that still had a broadband connection.
So to me it definitely seems to be a problem with the Hub itself, what else would cause the Hub to stop broadcasting WiFi in this way? The BQM for today looks absolutely rock solid.
on 16-08-2021 09:09
Hi @thebands,
I am very sorry to hear about this. Is this issue ongoing for you today?
If so, can you try performing a factory reset of the Hub 3 to see if that helps at all?
Thanks,