Menu
Reply
Highlighted
  • 2
  • 0
  • 0
Joining in
148 Views
Message 1 of 2
Flag for a moderator

Hub 3.0 (modem mode) restarting itself frequently

Multiple times per day for the past week our Hub 3.0 (Which is kept firmly in modem mode, with an RT-AC88U as router) has been dropping and, as far as I can tell, restarting itself.
Downstream & Upstream can be found below.

Any advice would be appreciated. Will be trying phone again tomorrow, was given "factory reset" advice today :)))

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1331000000-538256 qam25
2203000000-1.540256 qam9
3211000000-1.740256 qam10
4219000000-240256 qam11
5227000000-338256 qam12
6235000000-2.438256 qam13
7243000000-1.940256 qam14
8251000000-1.740256 qam15
9259000000-1.540256 qam16
10267000000-1.540256 qam17
11275000000-1.740256 qam18
12283000000-1.740256 qam19
13291000000-240256 qam20
14299000000-2.738256 qam21
15307000000-3.538256 qam22
16315000000-4.538256 qam23
17323000000-538256 qam24
18371000000-2.240256 qam26
19379000000-240256 qam27
20387000000-1.940256 qam28
21395000000-1.740256 qam29
22403000000-1.740256 qam30
23411000000-1.738256 qam31
24419000000-1.740256 qam32

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.900
2Locked40.360
3Locked40.350
4Locked40.350
5Locked38.600
6Locked38.950
7Locked40.350
8Locked40.360
9Locked40.350
10Locked40.360
11Locked40.350
12Locked40.350
13Locked40.360
14Locked38.960
15Locked38.9110
16Locked38.600
17Locked38.600
18Locked40.300
19Locked40.350
20Locked40.360
21Locked40.9120
22Locked40.3100
23Locked38.950
24Locked40.900

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1394000854.075512016 qam2
2258000923.925512016 qam4
3325999254.075512016 qam3
4461999054.075512016 qam1

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000



Network log is also full of these
29/06/2020 19:04:52 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2020 18:40:48 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2020 18:15:23 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2020 15:23:0 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2020 11:03:48 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/06/2020 07:31:17 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/06/2020 19:02:43 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/06/2020 18:19:20 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/06/2020 04:33:25 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/06/2020 20:03:52 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/06/2020 04:27:29 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/06/2020 17:58:7 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/06/2020 17:55:1 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/06/2020 17:55:1 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Today has been particularly bad.
Superhub has "red"/magenta light which I thought was indicative of overheating  at first (thanks Phone person) but it's just the light for modem mode.
However all lights cycle and the hub page is unavailable during the outage.
It's dropped twice again now while writing this post 🙂

There have been no changes in the network setup, or position of the hub etc (Other than a good clean since being told it was overheating)

0 Kudos
Reply
Highlighted
  • 2.99K
  • 166
  • 278
Forum Team
Forum Team
36 Views
Message 2 of 2
Flag for a moderator

Re: Hub 3.0 (modem mode) restarting itself frequently

Hello Falcorz,

 

I'm sorry to hear about your broadband issues. I've had a look at your network details and as you're still in modem mode, I couldn't see all the details. However I've noticed that there is a local fault in your area with the estimated fix time of 10/07. It's for SNR and may explain why you're having problems. I'm sorry about this but at least we're aware of it and are working on a fix. Please wait till after that date and let us know if you still have issues so we can take another look.

 

Thanks,

 

Lisa

0 Kudos
Reply