Hub5 no longer seeing 3.1 channels?

[BroadbandHog]

Hi All,

Just checking in to see if my Hub5 is operating as it should be. On the Hub4 i'm pretty sure it would show OFDMA and both 3.0 and 3.1 channels.

With the hub5 i see ATDMA and no 3.1 channels, i do not have any throughput issues at the moment and it appears to be working fine other than higher latency on the hub5 vs the hub4 but it's minimal.

I'm on the 1Gig service and would like to know if the below looks "normal" and is operating correctly. Last time i power cycled the modem was Monday 17th Oct. I have also included some of the network log.

Thanks.

Cable Modem StatusItem Status Comments

Acquired Downstream Channel(Hz)	339000000	Locked
Ranged Upstream Channel(Hz)	49600000	Ranged
Provisioning State	Online	Operational

Downstream bonded channels

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

1	339000000	5.9	40	QAM 256	26
2	139000000	7.4	39	QAM 256	1
3	147000000	7.1	39	QAM 256	2
4	155000000	6.8	39	QAM 256	3
5	163000000	6.4	39	QAM 256	4
6	171000000	6.3	39	QAM 256	5
7	179000000	6.4	39	QAM 256	6
8	187000000	6.3	39	QAM 256	7
9	195000000	6.1	39	QAM 256	8
10	203000000	5.8	39	QAM 256	9
11	211000000	5.6	39	QAM 256	10
12	219000000	5.2	39	QAM 256	11
13	227000000	4.9	39	QAM 256	12
14	235000000	4.5	39	QAM 256	13
15	243000000	4.5	39	QAM 256	14
16	251000000	4.3	39	QAM 256	15
17	259000000	4.2	39	QAM 256	16
18	267000000	4.3	39	QAM 256	17
19	275000000	4.4	39	QAM 256	18
20	283000000	4.7	39	QAM 256	19
21	291000000	5.1	39	QAM 256	20
22	299000000	5.2	39	QAM 256	21
23	307000000	5.5	39	QAM 256	22
24	315000000	5.7	39	QAM 256	23
25	323000000	5.9	39	QAM 256	24
26	331000000	5.9	39	QAM 256	25
27	347000000	6	40	QAM 256	27
28	355000000	5.8	40	QAM 256	28
29	363000000	5.6	40	QAM 256	29
30	371000000	5.3	40	QAM 256	30
31	379000000	4.9	39	QAM 256	31

Downstream bonded channels

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

1	Locked	40	17	0
2	Locked	39	6	0
3	Locked	39	12	0
4	Locked	39	12	0
5	Locked	39	9	0
6	Locked	39	15	0
7	Locked	39	11	0
8	Locked	39	12	0
9	Locked	39	12	0
10	Locked	39	22	0
11	Locked	39	12	0
12	Locked	39	15	0
13	Locked	39	9	0
14	Locked	39	10	0
15	Locked	39	12	0
16	Locked	39	12	0
17	Locked	39	14	0
18	Locked	39	10	0
19	Locked	39	14	0
20	Locked	39	9	0
21	Locked	39	21	0
22	Locked	39	9	0
23	Locked	39	7	0
24	Locked	39	19	0
25	Locked	39	24	0
26	Locked	39	9	0
27	Locked	40	13	0
28	Locked	40	14	0
29	Locked	40	14	0
30	Locked	40	13	0
31	Locked	39	13	0

Upstream bonded channels

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

0	49600000	44	5120	QAM 64	9
1	43100000	43.5	5120	QAM 64	10
2	36600000	43	5120	QAM 64	11
3	30100000	42.5	5120	QAM 64	12
4	23600000	42.8	5120	QAM 64	13

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	0	0
1	ATDMA	0	0	0	0
2	ATDMA	0	0	0	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0

General Configuration

Network accessMaximum Number of CPEsBaseline PrivacyDOCSIS ModeConfig file

Allowed

1

Enabled

3.1

REDACTED

Primary Downstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic Rate

4670

1200000450 bps

42600bytes

0 bps

Primary Upstream Service Flow

SFIDMax Traffic RateMax Traffic BurstMin Traffic RateMax Concatenated BurstScheduling Type

4669

55000270 bps

42600bytes

0 bps

16320bytes

Best Effort

Network Log
Time	Priority	Description
18/10/2022 16:57	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 16:57	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 15:16	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 15:16	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 14:56	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 14:56	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 14:46	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 14:46	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 13:56	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 13:56	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 13:15	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 13:15	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 12:45	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 12:45	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 12:25	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 12:25	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
18/10/2022 12:15	warning	DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[jb66]

Perhaps try a reboot today to see if it comes back

[BroadbandHog]

Hey thanks, I doubt that will make any change, I've rebooted it many times by this point, but will try it again.

It's been installed since end of September.

[Jon22]

I’ve received a Hub 5 today and I’m also seeing this. I know the area has a 3.1 down and upstream channel as the Hub 4 showed this. The Hub 5 doesn’t seem to display either. Just wondering what software version yours is on? Not sure if it’s just not displayed or not. Mines on LG-RDK_3.18.30-2112.12

[Roger_Gooner]

What's your speed coming into the hub according to SamKnows?

[BroadbandHog]

Hi,

I'm not sure on SamKnows as I have the Hub5 in modem mode.

I do see maximum throughput for down and up to my hosted server using iperf though. 

 

 

[Roger_Gooner]

If you've got 1Gbps coming into your hub it shows that you have a working downstream DOCSIS 3.1 channel and nothing to worry about.

[Tudor]

"If you've got 1Gbps coming into your hub it shows that you have a working downstream DOCSIS 3.1 channel and nothing to worry about."
Not necessarily so.

Well I’m in the same situation, I have only 31 downstream channels and NO DOCSIS 3.1 channel. I get full speed on a Speedtest run on my router.

[Roger_Gooner]

Are you saying you have 32 downstream DOCSIS 3.0 channels?

[Tudor]

No, 31.

I suspect a Hub5 firmware problem, either it’s not recognising the 3.1 stream or it’s just the display mechanism not displaying correctly and the 3.1 channel is really there.