Intermittent Drops Before and After Receiving New Hub 3

[mossbell]

Hey all,

Got a new hub as it was (seemingly) turning on and off -- got a refurb hub delivered (very quickly, which was impressive) and issue remains. Don't want to call an engineer out for an issue I can't replicate. Service status shows no issue in area. Wondering if I just got unlucky with a refurb hub or something else is afoot, many thanks.

The refurb Hub I received was not receiving power for the first 30 minutes - I assumed this was like a "first time boot" deal so not sure if relevant to this issue.

Downstream goodness:

Downstream bonded channels

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

1	515000000	-1	40	256 qam	48
2	139000000	-2.4	38	256 qam	1
3	339000000	-1.2	38	256 qam	26
4	347000000	-1.4	38	256 qam	27
5	355000000	-2.2	38	256 qam	28
6	363000000	-2.4	40	256 qam	29
7	371000000	-1.7	38	256 qam	30
8	379000000	-1.5	40	256 qam	31
9	387000000	-1.2	40	256 qam	32
10	395000000	-1	40	256 qam	33
11	403000000	-1.2	40	256 qam	34
12	411000000	-2.2	38	256 qam	35
13	419000000	-1.7	40	256 qam	36
14	427000000	-1.7	38	256 qam	37
15	435000000	-1.7	40	256 qam	38
16	443000000	-1.5	40	256 qam	39
17	451000000	-1	40	256 qam	40
18	459000000	-1.5	40	256 qam	41
19	467000000	-2.5	38	256 qam	42
20	475000000	-2.5	38	256 qam	43
21	483000000	-3.2	38	256 qam	44
22	491000000	-2.7	38	256 qam	45
23	499000000	-2.5	40	256 qam	46
24	507000000	-1.5	40	256 qam	47

Downstream bonded channels

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

1	Locked	40.3	15	0
2	Locked	38.6	1338	17
3	Locked	38.9	14	0
4	Locked	38.9	35	0
5	Locked	38.9	11	0
6	Locked	40.3	17	0
7	Locked	38.9	28	0
8	Locked	40.3	44	0
9	Locked	40.3	37	0
10	Locked	40.3	19	0
11	Locked	40.9	42	0
12	Locked	38.9	75	0
13	Locked	40.3	69	0
14	Locked	38.9	48	0
15	Locked	40.3	39	0
16	Locked	40.3	35	0
17	Locked	40.3	31	0
18	Locked	40.3	28	0
19	Locked	38.9	15	0
20	Locked	38.9	11	0
21	Locked	38.9	8	0
22	Locked	38.6	11	0
23	Locked	40.9	7	0
24	Locked	40.3	8	0

Upstream:

Upstream bonded channels

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

1

43100109

57

5120

64 qam

2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1

ATDMA

0

0

0

0

Network Log

Time Priority Description

13/04/2024 19:42:23	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:59:9	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:59:8	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:58:21	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:58:21	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:57:13	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:57:12	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:56:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:56:36	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:56:1	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:56:0	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:55:13	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:55:13	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:54:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:54:31	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:49:6	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 18:49:5	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 14:16:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 14:16:15	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/04/2024 14:15:34	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[mossbell]

Engineer came earlier this week, I just waited a few days to make sure of no issues and I can say the issue has been resolved, thanks.

[John_GS]

Hi @mossbell 

Thanks for updating the thread that everything is now resolved :).

[mossbell]

It seems I was premature with my contentment, two more disconnects today. Exact same in nature; box seemingly turning off and back on. I noticed a nice crack in the hub case today covered by the (maybe strategically placed) WIFI details sticker - probably unrelated but it tickled me.

Upstream bonded channels

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

1	23599988	51	5120	64 qam	5
2	30099954	52.5	5120	64 qam	4

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

 

Downstream bonded channels

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

1	331000000	1.9	38	256 qam	25
2	163000000	0.5	38	256 qam	4
3	339000000	1.7	40	256 qam	26
4	347000000	1.9	40	256 qam	27
5	355000000	1.7	40	256 qam	28
6	363000000	1	40	256 qam	29
7	371000000	1.4	40	256 qam	30
8	379000000	1.7	40	256 qam	31
9	387000000	2	40	256 qam	32
10	395000000	1.9	40	256 qam	33
11	403000000	2	40	256 qam	34
12	411000000	1	38	256 qam	35
13	419000000	0.5	40	256 qam	36
14	427000000	1	40	256 qam	37
15	435000000	1.2	40	256 qam	38
16	443000000	1.7	40	256 qam	39
17	451000000	2.5	40	256 qam	40
18	459000000	1.9	40	256 qam	41
19	467000000	0.9	40	256 qam	42
20	475000000	0.7	40	256 qam	43
21	483000000	0.5	40	256 qam	44
22	491000000	0.9	40	256 qam	45
23	499000000	2	40	256 qam	46
24	507000000	2.5	40	256 qam	47

Downstream bonded channels

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

1	Locked	38.9	8	0
2	Locked	38.9	177	0
3	Locked	40.3	1	0
4	Locked	40.3	8	0
5	Locked	40.3	4	0
6	Locked	40.3	4	0
7	Locked	40.3	5	0
8	Locked	40.3	7	0
9	Locked	40.3	6	0
10	Locked	40.3	5	0
11	Locked	40.3	4	0
12	Locked	38.9	1	0
13	Locked	40.3	0	0
14	Locked	40.3	5	0
15	Locked	40.3	0	0
16	Locked	40.3	0	0
17	Locked	40.3	5	0
18	Locked	40.9	5	0
19	Locked	40.9	0	0
20	Locked	40.3	6	0
21	Locked	40.3	4	0
22	Locked	40.3	0	0
23	Locked	40.3	5	0
24	Locked	40.9	1	0

Network Log

Time Priority Description

30/04/2024 15:11:50	critical	REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:11:50	Error	T6 Timeout and retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:11:50	critical	Registration RSP rejected unspecified reason;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:11:50	critical	Registration RSP rejected message syntax error;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:10:56	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:10:56	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:10:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:10:36	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:10:16	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:10:16	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:09:56	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:09:56	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:09:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:09:36	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:08:16	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:08:16	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:05:27	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:02:57	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 15:02:56	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2024 14:24:40	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Sephiroth]

Well, it won't have been a "new hub" - rather a so-called refurbished Hub 3.  Btw, thjis isn't something that a field tech can solve.  

[Roger_Gooner]

You have only two instead of the usual four upstream channels, and I believe that this could be the result of upstream power levels being too high.

[Akua_A]

Sorry to hear the issue is ongoing @mossbell We have had a look into this and we can see the disconnections in your service. For this reason, we are sending a private message. Please keep an eye out for an envelope at the top right corner of your Forum page. Let me know if you have any issues locating this. I'll be in touch soon.

Thanks,