(Hub 5) CM-STATUS messages 16 & 24 showing in Network Log.

[MacmillaN]

Seeing the above constant messages within the network log of the hub 5, just wondering if anything was a cause for concern.

Thanks for your time!

3.0 Downstream channels

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

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

3.0 Downstream channels

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

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

3.1 Downstream channels

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

33

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)

33

Locked

41

1.0

275097797

421

3.0 Upstream channels

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

0	49600000	46.3	5120	QAM 64	1
1	43100000	46.3	5120	QAM 64	2
2	36600000	46	5120	QAM 64	3
3	30100000	46.3	5120	QAM 64	4
4	23600000	46.3	5120	QAM 64	5

3.0 Upstream 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

3.1 Upstream channels

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

12

10.4

41.7

2K

QAM 256

3.1 Upstream channels

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

12

OFDMA

208

74000000

0

0

[Cardiffman282]

Stats look good to me. Check for local faults on 0800 561 0061. 

[MacmillaN]

Just realised i forgot to post the actual log.

09-08-2024 02:34:48	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 01:13:24	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 01:11:07	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:42:57	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:40:17	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:38:29	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:27:36	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:21:00	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:13:19	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:09:12	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
09-08-2024 00:05:11	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:48:59	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:46:49	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:33:01	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:30:59	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:13:47	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:10:09	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:08:30	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 23:06:39	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:55:40	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:25:23	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:21:35	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:18:52	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:18:17	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:15:15	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:12:51	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 22:05:22	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 21:57:23	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 21:55:04	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 21:47:20	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 21:44:44	notice	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
08-08-2024 21:39:06	notice	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Tudor]

They are only "Notice" category and can be safety ignored.

[pete_at_home]

Probably spikes of interference on the OFDM channel.  As Tudor said nothing to worry about.   Might be worth checking all your coax connectors are tightened correctly, especially the one in the wall box outside your property. 

[MacmillaN]

I couldn’t locate any loose connections within the property!

[David_Bn]

Thanks for reaching out to us @MacmillaN, and welcome back to our Community Forums!

Sorry to hear of the recent issues experienced.

There doesn't appear to be any cause for concern from what we see on our side - with only one registered drop in connection.

How has the service performed since your most recent post?

Thanks

David_Bn