cancel
Showing results for 
Search instead for 
Did you mean: 

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

MrJoeFitzsimons
Tuning in

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
14959993051512064 qam1
23660003451512064 qam3
34310002951512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0030
2ATDMA006522
3ATDMA0050

 

1 ACCEPTED SOLUTION

Accepted Solutions

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.

See where this Helpful Answer was posted

11 REPLIES 11

MrJoeFitzsimons
Tuning in

Downstream bonded channels

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

1635000000038256 qam29
24110000003.238256 qam1
34190000002.438256 qam2
44270000002.538256 qam3
54350000002.538256 qam4
6443000000338256 qam5
7451000000338256 qam6
84590000003.738256 qam7
9467000000338256 qam8
104750000002.938256 qam9
114830000001.938256 qam10
12491000000238256 qam11
134990000001.738256 qam12
14507000000238256 qam13
155150000001.738256 qam14
165230000002.538256 qam15
175310000002.238256 qam16
186030000001.738256 qam25
196110000000.538256 qam26
206190000000.938256 qam27
216270000000.538256 qam28
22643000000037256 qam30
236510000000.738256 qam31
246590000000.538256 qam32



Downstream bonded channels

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

1Locked38.9341684809
2Locked38.6227021881
3Locked38.938181015
4Locked38.95794946
5Locked38.6230151497
6Locked38.6244682458
7Locked38.6192502219
8Locked38.6127411867
9Locked38.9149411062
10Locked38.63603504
11Locked38.94896779
12Locked38.623511116
13Locked38.925571396
14Locked38.630121562
15Locked38.6255731264
16Locked38.9330862425
17Locked38.6291731859
18Locked38.9275021038
19Locked38.6323191786
20Locked38.6316871487
21Locked38.6335172816
22Locked37.6310641284
23Locked38.63603244
24Locked38.93463209

Upstream bonded channels

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

14959993051512064 qam1
23660003451512064 qam3
34310002951512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0030
2ATDMA006522
3ATDMA0050

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

SFID1871
Max Traffic Rate575000085
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID1868
Max Traffic Rate55000085
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

Network Log

Time Priority Description

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

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
Legend

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
On our wavelength

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
Alessandro Volta

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

--
Hub 5, TP-Link TL-SG108S 8-port gigabit switch, 360
My Broadband Ping - Roger's VM hub 5 broadband connection

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