Hub 3.0 Internet(Partial Service (US only)) - lower number of Upstream bonded channels

[MrJoeFitzsimons]

I have a Hub 3.0 in router mode with WIFI OFF.   I notice that sometimes but not always the router status will show Internet(Partial Service (US only)

Hub 3.0 status overview

Your Hub 3.0 status
	Wireless(Off)   Internet(Partial Service (US only))   Telephony(Disabled)

Wireless connected devices: 0

Ethernet Connected devices: 18

I sometime see only two to three Upstream Channels.    What do i need to do to get this regular intermittent issue fixed?

thank you in advance!

some of the ROUTER STATUS tabs:

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)	635000000	Locked
Ranged Upstream Channel (Hz)	49599930	Locked
Provisioning State	Online

Upstream bonded channels

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

1	49599930	51	5120	64 qam	1
2	36600034	51	5120	64 qam	3
3	43100029	51	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	3	0
2	ATDMA	0	0	65	22
3	ATDMA	0	0	5	0

[MrJoeFitzsimons]

Downstream bonded channels

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

1	635000000	0	38	256 qam	29
2	411000000	3.2	38	256 qam	1
3	419000000	2.4	38	256 qam	2
4	427000000	2.5	38	256 qam	3
5	435000000	2.5	38	256 qam	4
6	443000000	3	38	256 qam	5
7	451000000	3	38	256 qam	6
8	459000000	3.7	38	256 qam	7
9	467000000	3	38	256 qam	8
10	475000000	2.9	38	256 qam	9
11	483000000	1.9	38	256 qam	10
12	491000000	2	38	256 qam	11
13	499000000	1.7	38	256 qam	12
14	507000000	2	38	256 qam	13
15	515000000	1.7	38	256 qam	14
16	523000000	2.5	38	256 qam	15
17	531000000	2.2	38	256 qam	16
18	603000000	1.7	38	256 qam	25
19	611000000	0.5	38	256 qam	26
20	619000000	0.9	38	256 qam	27
21	627000000	0.5	38	256 qam	28
22	643000000	0	37	256 qam	30
23	651000000	0.7	38	256 qam	31
24	659000000	0.5	38	256 qam	32

Downstream bonded channels

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

1	Locked	38.9	34168	4809
2	Locked	38.6	22702	1881
3	Locked	38.9	3818	1015
4	Locked	38.9	5794	946
5	Locked	38.6	23015	1497
6	Locked	38.6	24468	2458
7	Locked	38.6	19250	2219
8	Locked	38.6	12741	1867
9	Locked	38.9	14941	1062
10	Locked	38.6	3603	504
11	Locked	38.9	4896	779
12	Locked	38.6	2351	1116
13	Locked	38.9	2557	1396
14	Locked	38.6	3012	1562
15	Locked	38.6	25573	1264
16	Locked	38.9	33086	2425
17	Locked	38.6	29173	1859
18	Locked	38.9	27502	1038
19	Locked	38.6	32319	1786
20	Locked	38.6	31687	1487
21	Locked	38.6	33517	2816
22	Locked	37.6	31064	1284
23	Locked	38.6	3603	244
24	Locked	38.9	3463	209

[MrJoeFitzsimons]

Upstream bonded channels

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

1	49599930	51	5120	64 qam	1
2	36600034	51	5120	64 qam	3
3	43100029	51	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	3	0
2	ATDMA	0	0	65	22
3	ATDMA	0	0	5	0

[MrJoeFitzsimons]

General Configuration

Network access	Allowed
Maximum Number of CPEs	1
Baseline Privacy	Enabled
DOCSIS Mode	Docsis30
Config file	fd;kfoA,.iyewrkldJKDHSUBs

Primary Downstream Service Flow

SFID	1871
Max Traffic Rate	575000085
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	1868
Max Traffic Rate	55000085
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	42600
Scheduling Type	BestEffort

[MrJoeFitzsimons]

Network Log

Time Priority Description

11/06/2024 16:14:14	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:14:14	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:13:32	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:12:35	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:12:34	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:11:15	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:11:15	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:09:55	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 16:09:55	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:58:16	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;
11/06/2024 15:56:16	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:56:16	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:54:56	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:54:56	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:53:36	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:53:36	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:51:37	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:51:36	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:49:57	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2024 15:49:57	critical	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[phonic2k · Accepted solution]

The critical T3 and T4 timeouts in your network log indicate an upstream communication problem that needs to be addressed. While your downstream signal levels are good, the upstream issues are likely causing the instability. 

You would need to contact support to book an engineer to resolve this one. Best of luck.

[Client62]

Downstream signals are plagued by high numbers of errors ( line noise ) across all channels.

Try 0800 561 0061 to see if there is a known fault in your street. 

[phonic2k]

Missed that😀. I was just looking at the log file only and noticed T3 and T4 upstream issues, but scrolling back yes, the power levels and SNR for your downstream channels are generally good, but the Pre-RS and Post-RS error counts are somewhat concerning. High Pre-RS errors, followed by noticeable Post-RS errors, would indeed suggest noise or interference affecting the downstream channels.

[Roger_Gooner]

Your upstream power levels are too high and probably contribute to there being only three upstream channels.

[David_Bn]

Thanks for reaching out to us @MrJoeFitzsimons, and a very warm welcome to you!

Sorry to hear of the recent connection issues you've been experiencing.

Can you please provide us with any updates available? 

Have any local area issues become apparent?

Thanks

David_Bn