Menu
Reply
  • 16
  • 0
  • 2
AndyKay
On our wavelength
230 Views
Message 1 of 5
Flag for a moderator

Hub3 failing

My Hub3 has been working fine since installation (getting on for a year I think) but now it keeps dropping out in the evenings (maybe at other times when I'm not at home). Both wired and wireless connections are lost. I tried resetting by holding down the reset button for 40s, and I tried turning off and back on again, but it just seems to keep trying to get off its knees and failing. I've taken to turning it off until the next day when it seems to come on okay. Is this an overheating issue?

0 Kudos
Reply
  • 19.07K
  • 1.67K
  • 4.18K
Superuser
Superuser
218 Views
Message 2 of 5
Flag for a moderator

Re: Hub3 failing

Would need to check the signal levels if could go to http://192.168.0.1 or if using modem mode http://192.168.100.1 clicking router status top right or bottom of page depending on hub [no need to login - depending on hub] and if could copy/paste the downstream, upstream, network log, don't worry about the formatting we can easily read it.. try and avoid using screen shots..




--------------------------------------------------------
If someone's helped you out say thanks by clicking on the thumbs up on kudos. If someone's solved your problem, why not mark their message as an Accepted Solution, but only do this once issue has been resolved.
  • 16
  • 0
  • 2
AndyKay
On our wavelength
191 Views
Message 3 of 5
Flag for a moderator

Re: Hub3 failing

Thanks Paul.

Downstream:

 

Downstream bonded channels
Channel
Frequency (Hz)
Power (dBmV)
SNR (dB)
Modulation
Channel ID
1
283000000
0.5
38
256 qam
19
2
187000000
3.5
38
256 qam
7
3
195000000
3
38
256 qam
8
4
203000000
2.5
38
256 qam
9
5
211000000
2.2
38
256 qam
10
6
219000000
2
38
256 qam
11
7
227000000
1.7
38
256 qam
12
8
235000000
1.4
38
256 qam
13
9
243000000
1
38
256 qam
14
10
251000000
0.7
38
256 qam
15
11
259000000
0.7
38
256 qam
16
12
267000000
0.7
38
256 qam
17
13
275000000
0.5
38
256 qam
18
14
291000000
0.5
38
256 qam
20
15
299000000
0.7
38
256 qam
21
16
307000000
0.7
38
256 qam
22
17
315000000
0.7
38
256 qam
23
18
323000000
0.7
38
256 qam
24
19
443000000
0
38
256 qam
25
20
451000000
0
38
256 qam
26
21
459000000
0
38
256 qam
27
22
467000000
0
38
256 qam
28
23
475000000
-0.2
38
256 qam
29
24
483000000
-0.5
38
256 qam
30


Downstream bonded channels
Channel
Locked Status
RxMER (dB)
Pre RS Errors
Post RS Errors
1
Locked
38.9
6
0
2
Locked
38.6
5
0
3
Locked
38.6
4
0
4
Locked
38.6
5
0
5
Locked
38.6
7
0
6
Locked
38.6
5
0
7
Locked
38.9
5
0
8
Locked
38.6
6
0
9
Locked
38.6
5
0
10
Locked
38.6
0
0
11
Locked
38.6
5
0
12
Locked
38.9
12
0
13
Locked
38.9
13
0
14
Locked
38.9
5
0
15
Locked
38.6
5
0
16
Locked
38.9
5
0
17
Locked
38.6
4
0
18
Locked
38.9
0
0
19
Locked
38.6
0
0
20
Locked
38.6
19
0
21
Locked
38.6
12
0
22
Locked
38.9
7
0
23
Locked
38.6
4
0
24
Locked
38.6
5
0

 

Upstream:

 

Refresh data
Upstream bonded channels
Channel
Frequency (Hz)
Power (dBmV)
Symbol Rate (ksps)
Modulation
Channel ID
1
32600009
3.9
5120
64 qam
3
2
25800000
3.75
5120
64 qam
4
3
39400009
3.9
5120
64 qam
2
4
46200046
3.9
5120
64 qam
1


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 Status:

 

Refresh data
Network Log
Time
Priority
Description
12/07/2019 21:23:29
Warning!
TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:30
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:30
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:31
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:31
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:40
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:40
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:41
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:41
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:42
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:42
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:43
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:23:43
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:24:25
notice
Received REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:30:26
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:30:26
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:30:27
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:30:27
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:30:28
critical
Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/07/2019 21:30:28
critical
No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

0 Kudos
Reply
  • 16
  • 0
  • 2
AndyKay
On our wavelength
168 Views
Message 4 of 5
Flag for a moderator

Re: Hub3 failing

To my mind there's a difference between "helpful answer" and "accepted solution". I acknowledged you reply as helpful without intending to accept it as a solution.
0 Kudos
Reply
Highlighted
  • 979
  • 46
  • 87
Forum Team (Retired) Tom_S
Forum Team (Retired)
85 Views
Message 5 of 5
Flag for a moderator
Helpful Answer

Re: Hub3 failing

Hi AndyKay,

 

I'm going to drop you a PM so I can take a closer look for you.

 

Thanks,
Tom_S