Hub 4 Issues - Gig1

[Raident10]

Hello everyone hope you’re well,

For the past week or so, I’ve noticed some issues with my Hub 4 Connection.

I’ve seen it reboot twice within the space of a week, once at around exactly 00:00 and this morning at around 3AM. As I also work night shifts at home, this affects my ability to work and this is happening whilst the hub is in Modem Mode (I use my own UDM Pro Router and another access point connected to it).

I have also set up a BQM Graph and there are some random ping spikes. Can someone from VM please check my Hub to see if it is in spec first of all?

The BQM Graph is below and I’ll copy the hub config for you.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/97d5ba5ab6574ba3534abb2ab2b0d00d96...

[Raident10]

3.0 Downstream channels

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

25	331000000	3.1	39	QAM256	25
1	139000000	4.2	39	QAM256	1
2	147000000	3.9	40.4	QAM256	2
3	155000000	4	40.4	QAM256	3
4	163000000	4.1	40.4	QAM256	4
5	171000000	4	39	QAM256	5
6	179000000	4.3	40.4	QAM256	6
7	187000000	4.3	39	QAM256	7
8	195000000	4.4	39	QAM256	8
9	203000000	4.6	39	QAM256	9
10	211000000	4.6	40.4	QAM256	10
11	219000000	4.5	40.4	QAM256	11
12	227000000	4.6	40.4	QAM256	12
13	235000000	4.4	40.4	QAM256	13
14	243000000	4.3	40.4	QAM256	14
15	251000000	4.3	39	QAM256	15
16	259000000	3.8	39	QAM256	16
17	267000000	3.4	39	QAM256	17
18	275000000	3.1	39	QAM256	18
19	283000000	2.9	38.6	QAM256	19
20	291000000	3	38.6	QAM256	20
21	299000000	4	38.6	QAM256	21
22	307000000	3.4	39	QAM256	22
23	315000000	2.9	38.6	QAM256	23
24	323000000	2.8	39	QAM256	24
26	339000000	3.1	39	QAM256	26
27	347000000	3.4	39	QAM256	27
28	355000000	3.7	38.6	QAM256	28
29	363000000	3.5	39	QAM256	29
30	371000000	3.7	38.6	QAM256	30
31	379000000	3.7	39	QAM256	31

3.0 Downstream channels

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

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

3.1 Downstream channels

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

159

96

4K

1880

QAM2048

759

3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)

159

Locked

40

4.4

59541822

3

[Raident10]

3.0 Upstream channels

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

1	60300000	32	5120 KSym/sec	64QAM	1
2	39400000	32	5120 KSym/sec	64QAM	4
3	46200000	31.5	5120 KSym/sec	64QAM	3
4	53700000	32	5120 KSym/sec	64QAM	2

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_STDMA	0	0	0	0
2	US_TYPE_STDMA	0	0	0	0
3	US_TYPE_STDMA	0	0	0	0
4	US_TYPE_STDMA	0	0	0	0

[Raident10]

• General Configuration

Network access	true
Maximum Number of CPEs	1
Baseline Privacy	true
DOCSIS Mode	3.1
Config file	;kfoA,.iyewrkldJKDHSUBsgvca69

Primary Downstream Service Flow

SFID	28217
Max Traffic Rate	1200000450
Max Traffic Burst	42600
Min Traffic Rate	0

Primary Upstream Service Flow

SFID	28354
Max Traffic Rate	55000270
Max Traffic Burst	42600
Min Traffic Rate	0
Max Concatenated Burst	16320
Scheduling Type	bestEffort

[Raident10]

Network Log

Time Priority Description

Wed 20/07/2022 18:48:27	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 20/07/2022 19:00:43	5	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;
Wed 20/07/2022 19:08:10	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 20/07/2022 22:54:12	5	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;
Thu 21/07/2022 00:50:52	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 23/07/2022 04:58:42	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 23/07/2022 07:48:20	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/07/2022 10:14:56	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/07/2022 10:14:57	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 24/07/2022 13:48:55	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 27/07/2022 22:14:57	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 27/07/2022 22:14:57	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 28/07/2022 19:34:48	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 29/07/2022 15:55:49	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 30/07/2022 23:47:55	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 31/07/2022 00:07:09	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 31/07/2022 00:19:24	5	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;
Sun 31/07/2022 01:32:39	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/08/2022 23:10:58	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 01/08/2022 23:10:58	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 02/08/2022 11:47:29	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/08/2022 12:11:28	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 03/08/2022 15:12:51	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 04/08/2022 17:13:01	4	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 04/08/2022 17:13:01	6	DHCP Renew - lease parameters tftp file-cmreg-vmdg640-bbt076+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 04/08/2022 20:07:58	6	CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri 05/08/2022 22:04:55	3	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 06/08/2022 03:37:35	5	MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 06/08/2022 03:49:50	5	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;

[Tudor]

Upstream on the low side, but I expect it’s just VM doing some quick overnight work. Do you know if your WAN address has changed?

[Raident10]

Hey Tudor,

It definitely has at some point but I have no idea when - I had a previous Graph set up (since deleted as it was disabled) but I think that was a few months ago now. I had a different WAN IP for it than what I have now.

[Matthew_ML]

Hey Raident10, thank you for reaching out and I am sorry to hear you are having some connection issues.

I have taken a look from our side and I cannot see no issues everything is running the way it should be.

How was the connection over the weekend, any improvement at all?

Please do let me know. Thanks 

[Raident10]

Hey Matt I hope you’re well,

Mainly things seem fine, however looking at that graph I linked, I’m still getting ping spikes on the WAN Interface and it looks like a little bit of packet loss as well.

It seems every so often it shoots up.

Take care,

[Ashleigh_C]

Hi there @Raident10

Thank you so much for popping back to us. 

I have checked diagnostics again and there do not seem to be any issues at all with the Hub specs, and everything is performing as we would expect. 

How have things been looking since your last message? Have you noticed any issues at all when using devices connected?

Thanks again.