Does this BQM look right?

[Tom_nock]

New customer on Gig1 (M500 with Volt) and a Hub 5. 

Connected in modem mode originally to a DrayTek 2962 and now an Edgerouter-X.

I originally stated out with M500 and a Hub 3. The BQM for that looked perfect when using the Edgerouter-X.

Does this BQM graph look right with my Hub5? It’s the yellow areas that don’t look right to me - the first earlier part of the graph is with the 2962 and the red areas are where I either rebooted or at around 10am this morning I swapped the 2962 out for the Edgerouter-X.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d11a49b057e580f068fd118ba0ec2fff76...

Speeds are ok, haven’t seen the full 1Gbps on Ethernet yet, more around the 700-800Mbps mark. Upload seems fine and consistent at 105Mbps. I can iPerf to my Raspberry Pi at 940Mbps so my local network seems OK. 

Looking for your thoughts please! Thank you. 

[legacy1]

Look fine some BQM look better then others but the question we can't answer is maybe your is worse but better under load in the area the key is min to max if the closer the better but if VM have to make that worse for better under load in the area the better till it come to a point where where the min and max are too far apart    

[carl_pearce]

No, the BQM doesn't look 'fine'.

Can you please post the HUB stats from the 'Check router status' section.

[Tom_nock]

3.0 Downstream channels

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

1	331000000	4.4	42	QAM 256	25
2	139000000	7.2	42	QAM 256	1
3	147000000	7	41	QAM 256	2
4	155000000	6.8	41	QAM 256	3
5	163000000	6.6	42	QAM 256	4
6	171000000	6.4	41	QAM 256	5
7	179000000	6.2	41	QAM 256	6
8	187000000	6.3	41	QAM 256	7
9	195000000	6.4	41	QAM 256	8
10	203000000	6.3	41	QAM 256	9
11	211000000	6.3	41	QAM 256	10
12	219000000	6.2	42	QAM 256	11
13	227000000	6.2	42	QAM 256	12
14	235000000	6.1	42	QAM 256	13
15	243000000	5.9	42	QAM 256	14
16	251000000	5.9	42	QAM 256	15
17	259000000	6.1	42	QAM 256	16
18	267000000	6.1	42	QAM 256	17
19	275000000	6.1	42	QAM 256	18
20	283000000	5.8	42	QAM 256	19
21	291000000	5.7	42	QAM 256	20
22	299000000	5.4	42	QAM 256	21
23	307000000	5.2	42	QAM 256	22
24	315000000	4.8	42	QAM 256	23
25	323000000	4.4	41	QAM 256	24
26	339000000	4.6	41	QAM 256	26
27	347000000	4.6	42	QAM 256	27
28	355000000	4.6	42	QAM 256	28
29	363000000	4.7	42	QAM 256	29
30	371000000	4.6	41	QAM 256	30
31	379000000	4.5	41	QAM 256	31
32	387000000	4.3	41	QAM 256	32

3.0 Downstream channels

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

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

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)

159

94

4K

1840

QAM 4096

1108

3.1 Downstream channels

Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)

159

Locked

40

-1.3

329773356

0

[Tom_nock]

3.0 Upstream channels

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

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

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

0	ATDMA	0	0	6	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

3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation

14

10

38.5

2K

QAM 256

3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts

14

OFDMA

200

74000000

0

0

[carl_pearce]

HUB stats look ok, anything in the log?

[Tom_nock]

Snippet of today and yesterday evening…

Network Log

Time Priority Description

05-03-2024 08:49:37	notice	US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:49:37	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;
05-03-2024 08:49:33	notice	REGISTRATION COMPLETE - Waiting for Operational status
05-03-2024 08:49:28	warning	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:49:28	warning	Dynamic Range Window violation
05-03-2024 08:49:27	warning	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:49:21	notice	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:49:18	notice	TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:49:16	warning	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:49:14	notice	Honoring MDD; IP provisioning mode = IPv4
05-03-2024 08:48:45	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:48:40	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
05-03-2024 08:48:39	critical	Cable Modem Reboot because of - HW or Power-On Reset
04-03-2024 19:31:13	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-03-2024 19:31:07	critical	Cable Modem Reboot because of - Reboot UI
04-03-2024 19:31:07	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-03-2024 18:38:21	critical	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-03-2024 18:38:20	critical	Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
04-03-2024 18:38:15	critical	Cable Modem Reboot because of - HW or Power-On Reset

[carl_pearce]

Although the downstream power levels are in spec, there is one entry that shows power levels are out of spec at some point.

May be worth waiting for VM to reply to see if they can see anything their side.

[Tom_nock]

I think I’ve figured that the blocks of yellow on the BQM are when my connection is idle. When I’m on a Teams call for instance, the graph will show “normal” as I’d expect. 

Can’t even think what would cause that? I even gave the hub a pin hole reset last night and it’s made no difference. 

[legacy1]

Maybe the Docsis scheduler can do idle scheduling then when the traffic rate goes up it allows for lower latency