on 23-05-2020 15:54
Hi folks.
So i previously had the Superhub 2.0 (had it for about 7 years) and i encountered an issue where the wifi networks would randomly vanish maybe once a day (even though connection via ethernet is fine) and i would have to restart the Hub to get the wifi networks to show again. I rang VM and explained the issue and the person i spoke to changed some settings apparently and asked me to see if the issue persists. 3-4 days went by and I had the same issue so I rang back and a new Superhub 3.0 was sent out. I connected this up and everything is ok with the wifi now.
However now the Hub reboots at nearly dead on midnight every night now and ive never had this issue before! I've rang up today and I have an engineer coming out in 2 weeks but to be honest i dont have any faith that this is a hardware or connection issue as my broadband is rock solid speed wise and doesnt drop out at all so im convinced this is a setting somewhere thats causing the midnight reboots.
on 23-05-2020 15:56
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 187000000 | 4.3 | 38 | 256 qam | 7 |
2 | 195000000 | 4 | 38 | 256 qam | 8 |
3 | 203000000 | 4.4 | 38 | 256 qam | 9 |
4 | 211000000 | 4 | 38 | 256 qam | 10 |
5 | 235000000 | 5 | 38 | 256 qam | 13 |
6 | 243000000 | 4 | 38 | 256 qam | 14 |
7 | 251000000 | 5.5 | 38 | 256 qam | 15 |
8 | 259000000 | 4 | 38 | 256 qam | 16 |
9 | 267000000 | 5.6 | 38 | 256 qam | 17 |
10 | 275000000 | 4.9 | 38 | 256 qam | 18 |
11 | 283000000 | 5.8 | 38 | 256 qam | 19 |
12 | 291000000 | 5.5 | 38 | 256 qam | 20 |
13 | 299000000 | 5.6 | 38 | 256 qam | 21 |
14 | 307000000 | 6.4 | 40 | 256 qam | 22 |
15 | 315000000 | 5.5 | 40 | 256 qam | 23 |
16 | 323000000 | 6.3 | 40 | 256 qam | 24 |
17 | 443000000 | 5 | 38 | 256 qam | 25 |
18 | 451000000 | 4.6 | 38 | 256 qam | 26 |
19 | 459000000 | 4.9 | 38 | 256 qam | 27 |
20 | 467000000 | 4.8 | 38 | 256 qam | 28 |
21 | 475000000 | 4.5 | 38 | 256 qam | 29 |
22 | 483000000 | 4.5 | 38 | 256 qam | 30 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 1122 | 1851 |
2 | Locked | 38.6 | 969 | 236 |
3 | Locked | 38.6 | 763 | 217 |
4 | Locked | 38.6 | 1905 | 351 |
5 | Locked | 38.9 | TV | 122 |
6 | Locked | 38.9 | 291 | 18 |
7 | Locked | 38.9 | 345 | 21 |
8 | Locked | 38.9 | 334 | 21 |
9 | Locked | 38.9 | 258 | 4 |
10 | Locked | 38.9 | 106 | 7 |
11 | Locked | 38.9 | 115 | 0 |
12 | Locked | 38.9 | 240 | 29 |
13 | Locked | 38.9 | 226 | 0 |
14 | Locked | 40.3 | 117 | 15 |
15 | Locked | 40.3 | 150 | 16 |
16 | Locked | 40.3 | 137 | 16 |
17 | Locked | 38.6 | 449 | 0 |
18 | Locked | 38.9 | 337 | 0 |
19 | Locked | 38.9 | 300 | 0 |
20 | Locked | 38.9 | 477 | 0 |
21 | Locked | 38.9 | 468 | 0 |
22 | Locked | 38.6 | 416 | 0 |
on 23-05-2020 15:56
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 4.45 | 5120 | 64 qam | 1 |
2 | 32600000 | 4.65 | 5120 | 64 qam | 3 |
3 | 25800000 | 4.4 | 5120 | 64 qam | 4 |
4 | 39400000 | 4.475 | 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 | 0 | 0 |
Network Log
Time Priority Description
23/05/2020 14:32:55 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:32:53 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:30:1 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:30:1 | notice | LAN login Success;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:28:4 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:28:3 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:19:59 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:19:58 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:19:49 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:19:48 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:05:53 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:05:52 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:02:57 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 14:02:56 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 12:46:10 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 12:46:10 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 11:55:15 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=00:01:***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 11:55:14 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 11:53:54 | Warning! | RCS Partial Service;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
23/05/2020 11:53:53 | Warning! | Lost MDD Timeout;CM-MAC=***Redacted***;CMTS-MAC=***Redacted***;CM-QOS=1.1;CM-VER=3.0; |
General Configuration
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | cmreg-vmdg505-rtsxl20016u-b.cm |
Primary Downstream Service Flow
SFID | 495220 |
Max Traffic Rate | 230000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Primary Upstream Service Flow
SFID | 495219 |
Max Traffic Rate | 22000061 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | BestEffort |
on 23-05-2020 16:14
on 23-05-2020 17:58
You hub is not rebooting every night. What it happening is it is losing connection with the VM CMTS at the other end of your cable. It then go into a loop trying to regain the connection and it eventually succeeds. So don’t think the Pre & Post RS error will reset every night, they will not. The only way to reset them is to power cycle your hub.
on 23-05-2020 18:18
Thanks for your reply. Any idea what the resolution would be then?
on 24-05-2020 00:48
Went down again 12:20 - 12:45 No connection at all and couldnt even interact with the router via http://192.168.0.1 as it refused to even take me to the login page or acknowledge the router was there
on 25-05-2020 18:01
Again last night at 12:20 it went down.... It seems a bit too conistant
on 25-05-2020 18:16
I presume you are testing the connection and logging on to the Hub3 from a cable connected devices. The only other explanation, other than VM maintenance, is perhaps someone on your street box is doing “something funny” on the internet at that time, although I think this is very remote.
on 25-05-2020 18:25
I am connecting via Ethernet and it seems this issue has only started since i changed the Hub from the 2.0 to 3.0 and it wouldnt expect that VM have been doing maintainance 4 days in a row just after midnight. I never had this issue with the 2.0 Hub, other than recently the wifi disappearing (but not the connection via ethernet) which is why i asked for a new Hub.
Call it rational or not im convinced that the first person who I spoke to, before i got the new Hub, "changed some settings" in their own words which I believe is causing the issues