Cax30 Poor cable connection status downstream

Question

Can anyone help me find what the issue is here? Brand new modem/router combo Nighthawk and comcast is no help. I have tried different coaxial cables along with cat6 cords. I switched out the coaxial cable 2 days ago and got 300 gb wifi connection. Accidently unplugged the power cord and now I'm back to 25 or below. No amount of power cycling is helping.

Frequency start Value

This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.

Starting Frequency

<tabindex=-1>Startup Procedure</tabindex=-1>

<tabindex=-1>Downstream Bonded Channels (Partial Service)</tabindex=-1>

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR	Correctables	Uncorrectabables
1	Locked	256 QAM	17	513000000 Hz	-19.6 dBmV	33.1 dB	105	29
2	Locked	256 QAM	14	489000000 Hz	-17.8 dBmV	34.2 dB	658	246
3	Locked	256 QAM	15	495000000 Hz	-18.0 dBmV	33.7 dB	1139	285
4	Locked	256 QAM	16	507000000 Hz	-18.2 dBmV	33.9 dB	171	67
5	Locked	256 QAM	18	519000000 Hz	-18.8 dBmV	33.4 dB	119	22
6	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0
7	Locked	256 QAM	20	531000000 Hz	-18.9 dBmV	0.0 dB	1168	0
8	Locked	256 QAM	21	537000000 Hz	-19.0 dBmV	28.0 dB	28469793	4161607
9	Locked	256 QAM	22	543000000 Hz	-18.9 dBmV	33.3 dB	79	34
10	Locked	256 QAM	23	549000000 Hz	-20.1 dBmV	29.3 dB	5755	213
11	Locked	256 QAM	24	555000000 Hz	-19.9 dBmV	29.8 dB	1777	295
12	Locked	256 QAM	25	561000000 Hz	-20.0 dBmV	0.0 dB	1025762	0
13	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0
14	Locked	256 QAM	27	573000000 Hz	-19.9 dBmV	32.3 dB	127	158
15	Locked	256 QAM	28	579000000 Hz	-20.4 dBmV	31.9 dB	45	23
16	Locked	256 QAM	29	585000000 Hz	-20.7 dBmV	31.8 dB	107	121
17	Locked	256 QAM	30	591000000 Hz	-20.1 dBmV	31.8 dB	123	34
18	Locked	256 QAM	31	597000000 Hz	-20.4 dBmV	31.8 dB	123	4
19	Locked	256 QAM	32	603000000 Hz	-20.8 dBmV	31.5 dB	141	133
20	Locked	256 QAM	33	609000000 Hz	-21.2 dBmV	31.3 dB	758	321
21	Locked	256 QAM	34	615000000 Hz	-21.9 dBmV	27.5 dB	7047718	25274118
22	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0
23	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0
24	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0
25	Locked	256 QAM	39	639000000 Hz	-21.0 dBmV	0.0 dB	111459	0
26	Locked	256 QAM	40	645000000 Hz	-21.1 dBmV	31.6 dB	234	259
27	Locked	256 QAM	41	651000000 Hz	-22.2 dBmV	30.6 dB	380	283
28	Locked	256 QAM	42	657000000 Hz	-21.5 dBmV	31.3 dB	485	300
29	Locked	256 QAM	43	663000000 Hz	-22.3 dBmV	30.6 dB	659	296
30	Locked	256 QAM	44	669000000 Hz	-21.3 dBmV	31.3 dB	247	223
31	Locked	256 QAM	45	675000000 Hz	-21.8 dBmV	30.8 dB	813	27
32	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>

Channel	Lock Status	US Channel Type	Channel ID	Symbol Rate	Frequency	Power
1	Locked	ATDMA	2	5120 Ksym/sec	16300000 Hz	53.3 dBmV
2	Locked	ATDMA	3	5120 Ksym/sec	22800000 Hz	49.0 dBmV
3	Locked	ATDMA	4	5120 Ksym/sec	29200000 Hz	51.5 dBmV
4	Locked	ATDMA	9	5120 Ksym/sec	35600000 Hz	49.3 dBmV
5	Locked	ATDMA	10	5120 Ksym/sec	40400000 Hz	52.3 dBmV
6	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV
7	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV
8	Not Locked	Unknown	0	0 Ksym/sec	0 Hz	0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>

Channel	Channel ID	Frequency	Power	SNR/MER	Active Subcarrier Number Range	Total Codewords	Uncorrectable Codewords
1	37	708000000 Hz	-21.7 dBmV	0.0 dB	1108 ~ 2987	4342104	0
2	0	0 Hz	0 dBmV	0 dB	0 ~ 0	0	0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>

Channel	UpstreamIsMuted	Ranging Status	Subcarrier Zero Frequency	Active Subcarrier Number Range	Symbols Per Frame	Tx Power
1		Other	0 MHz	0 ~ 0	0	0 dBmV
2		Other	0 MHz	0 ~ 0	0	0 dBmV

FURRYe38 · Answer

Power levels are way too low:
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
&nbsp;
Please post a copy and paste of the modems event log page.https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
&nbsp;
Lots of correctables and uncorrectables that should be zeros.
Have the ISP check the signal and line quality UP to the modem.&nbsp;Be sure the ISP provisions the modem correctly.Be sure there are no coax cable line splitters in the between the modem and ISP service box.&nbsp;Be sure your using good quality RG6 coax cable up to the modem.&nbsp;Start with removing any amplifiers, signal attenuators, or splitters from the coax.From there check the line for kinks, damage, moisture in the line.Check the connectors for improperly made ends, foil touching the copper coax line, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.Be sure to power OFF the modem for 1 minute then back ON.https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-routerhttps://www.duckware.com/tech/solving-intermittent-cable-modem-issues.htmlhttps://highspeed.tips/docsis-events/

FURRYe38 · Answer

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP.&nbsp;Indicates a signal issue on the ISP line up to the modem.

WitchyGirl · Answer

2024-09-01 18:39:45Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:39:24Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:39:21Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:36:20Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:36:18Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:36:13Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:35:35Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:35:25Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:35:05Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:57Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:29Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:25Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:09Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:07Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:04Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 34 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:34:02Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:53Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:42Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:40Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 34 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:37Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 34 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:37Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:34Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:33Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:33Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:29Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:23Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:15Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:08Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:33:07Notice (6)CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:31:29Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 34 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:31:26Notice (6)CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 34 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:31:07Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:31:04Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:31:03Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:30:53Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:30:28Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:30:18Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 34 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:30:07Warning (5)MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:29:56Notice (6)CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;2024-09-01 18:29:49Notice (6)CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;

WitchyGirl · Answer

Is there any way to change the power? I update the starting frequency and reboot the modem but it always reverts back to&nbsp;657000000.

FURRYe38 · Answer

You'll need to contact the ISP. They need to raise the power.&nbsp;

Forum Discussion

Cax30 Poor cable connection status downstream

5 Replies

2024-09-01 18:39:45	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:39:24	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:39:21	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:36:20	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:36:18	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:36:13	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:35:35	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:35:25	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:35:05	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:57	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:29	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:25	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:09	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:07	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:04	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 34 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:34:02	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:53	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:42	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:40	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 34 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:37	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 34 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:37	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:34	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:33	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:33	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:29	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:23	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:15	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:08	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:33:07	Notice (6)	CM-STATUS message sent. Event Type Code: 5; Chan ID: 20 25 34 35; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:31:29	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 34 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:31:26	Notice (6)	CM-STATUS message sent. Event Type Code: 2; Chan ID: 26 34 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:31:07	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:31:04	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:31:03	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:30:53	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:30:28	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:30:18	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 34 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:30:07	Warning (5)	MDD message timeout;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:29:56	Notice (6)	CM-STATUS message sent. Event Type Code: 4; Chan ID: 34; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;
2024-09-01 18:29:49	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 25 26 35 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:43:cf:6b;CMTS-MAC=00:01:5c:6a:7e:7d;CM-QOS=1.1;CM-VER=3.1;