cancel
Showing results for 
Search instead for 
Did you mean: 

Hub 3 keeps rebooting

John_SC
Joining in

Over the last couple of weeks, most days (and starting to become more frequent), I have to reboot my Hub 3.

I've not experienced this before.

I see from other similar posts you want to see the info from the hub, so here goes.

Status:

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
203000000
Locked
Ranged Upstream Channel (Hz)
36600000
Locked
Provisioning State
Online

Downstream:

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

12030000003.740256 qam9
22110000003.538256 qam10
32190000003.540256 qam11
4227000000338256 qam12
52350000002.538256 qam13
62430000002.438256 qam14
72510000002.938256 qam15
82590000003.238256 qam16
92670000003.738256 qam17
102750000003.740256 qam18
112830000003.740256 qam19
122910000003.738256 qam20
13299000000438256 qam21
143070000004.338256 qam22
153150000004.640256 qam23
16323000000540256 qam24
17331000000540256 qam25
183390000005.440256 qam26
193470000005.538256 qam27
203550000005.540256 qam28
213630000005.540256 qam29
223710000005.538256 qam30
233790000005.438256 qam31
243870000004.940256 qam

32

Downstream bonded channels

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

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

 

18 REPLIES 18

John_SC
Joining in

Upstream bonded channels

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

13660000048.3512064 qam3
22360005447.8512064 qam5
34960000049.3512064 qam1
43010000048512064 qam4
54310000048.8512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0010
3ATDMA0020
4ATDMA0000
5ATDMA0000

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt060+voc-b.cm



Primary Downstream Service Flow

SFID7998
Max Traffic Rate287500061
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID7997
Max Traffic Rate27500061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

Network Log

Time Priority Description

22/06/2023 17:28:24noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 17:28:13Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 17:09:48noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 15:58:14criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 15:55:49noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 15:37:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 15:37:34noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 07:52:26noticeNOTICE 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;
22/06/2023 07:52:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/06/2023 07:14:53noticeNOTICE 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;
22/06/2023 00:12:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/06/2023 10:47:57noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/06/2023 15:24:38noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/06/2023 05:22:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2023 08:23:55ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2023 07:44:21noticeNOTICE 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;
14/06/2023 22:27:25criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Some help would be appreciated - thanks in advance.

Natalie_L
Forum Team (Retired)
Forum Team (Retired)

Hello John_SC, 

Welcome to the Community and thank you for posting. 

We are very sorry to hear of the issues you have been experiencing with the service, we will do all we can to help. 

Checks have been ran on our side and we can confirm there are no outages in the area and your Hub appears to be running within specification. 

Can you please expand on what is happening that is causing you to need to reboot?

Thanks, 

 

Nat

John_SC
Joining in

Hi - apologies, have been away for a little while.

Today, my router has just stopped working twice (no internet, can't even connect to the router to get a status update) and only becomes operational again following turning it off/on.

This is what the various parts of the router status says when it is operational:

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
203000000
Locked
Ranged Upstream Channel (Hz)
36600000
Locked
Provisioning State
Online

John_SC
Joining in

Downstream bonded channels

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

1203000000440256 qam9
21390000003.938256 qam1
31470000003.938256 qam2
4155000000438256 qam3
5163000000440256 qam4
6171000000440256 qam5
71790000004.140256 qam6
8187000000440256 qam7
9195000000440256 qam8
102110000003.938256 qam10
112190000003.940256 qam11
122270000003.538256 qam12
132350000002.938256 qam13
142430000002.738256 qam14
152510000003.238256 qam15
162590000003.738256 qam16
17267000000438256 qam17
18275000000440256 qam18
192830000004.140256 qam19
20291000000438256 qam20
212990000004.438256 qam21
223070000004.538256 qam22
23315000000540256 qam23
243230000005.340256 qam24

John_SC
Joining in

Downstream bonded channels

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

1Locked40.350
2Locked38.950
3Locked38.940
4Locked38.950
5Locked40.350
6Locked40.330
7Locked40.360
8Locked40.360
9Locked40.940
10Locked38.960
11Locked40.330
12Locked38.950
13Locked38.900
14Locked38.900
15Locked38.950
16Locked38.950
17Locked38.950
18Locked40.340
19Locked40.340
20Locked38.940
21Locked38.950
22Locked38.650
23Locked40.350
24Locked40.360

John_SC
Joining in

Upstream bonded channels

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

13660000048.3512064 qam3
24960000048.8512064 qam1
32360000047.5512064 qam5
43010000047.8512064 qam4
54310000048.5512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0000
3ATDMA0000
4ATDMA0000
5ATDMA0000

John_SC
Joining in

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt060+voc-b.cm



Primary Downstream Service Flow

SFID14944
Max Traffic Rate287500061
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID14943
Max Traffic Rate27500061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

John_SC
Joining in

Network Log

Time Priority Description

18/07/2023 16:22:51noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2023 15:53:12noticeNOTICE 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;
18/07/2023 12:51:12noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/07/2023 05:47:16ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2023 17:52:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2023 15:06:6noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/07/2023 00:45:37criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2023 22:46:7noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2023 22:13:12noticeNOTICE 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;
01/01/1970 00:01:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/07/2023 20:00:37noticeNOTICE 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;
13/07/2023 12:40:11noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/07/2023 03:33:31ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/07/2023 03:34:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/07/2023 23:56:43ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;