Question Netgear CM1000 DOCSIS 3.1 Power Levels

MM80 · Jun 17, 2023

Can someone review my power levels? Optimum is telling me my modem is going bad?? I never had an issue until ATT started digging up the neighborhood for fiber lines. I pay for the 1G plan and am now getting maybe 90 down and still 50 up. Used to get 900 down. TIA

Procedure	Status	Comment
Acquire Downstream Channel	663000000 Hz	Locked
Connectivity State	OK	Operational
Boot State	OK	Operational
Security	Enable	BPI+
IP Provisioning Mode	Honor MDD	APM

Downstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power	SNR / MER	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	QAM256	19	663000000 Hz	3.9 dBmV	39.3 dB	2073675126	6544	2742
2	Locked	QAM256	2	561000000 Hz	5.0 dBmV	39.9 dB	2072427335	7129	3163
3	Locked	QAM256	3	567000000 Hz	4.7 dBmV	39.8 dB	2072435975	7159	3150
4	Locked	QAM256	4	573000000 Hz	4.7 dBmV	39.7 dB	2072432043	7017	3109
5	Locked	QAM256	5	579000000 Hz	4.5 dBmV	39.7 dB	2072454004	7093	3120
6	Locked	QAM256	6	585000000 Hz	4.2 dBmV	39.7 dB	2072474610	6892	3081
7	Locked	QAM256	7	591000000 Hz	4.3 dBmV	39.7 dB	2072484823	6998	2997
8	Locked	QAM256	8	597000000 Hz	4.2 dBmV	39.7 dB	2072489579	6936	3065
9	Locked	QAM256	9	603000000 Hz	4.6 dBmV	39.8 dB	2072513440	6865	2998
10	Locked	QAM256	10	609000000 Hz	4.4 dBmV	39.6 dB	2072532530	6836	2981
11	Locked	QAM256	11	615000000 Hz	4.8 dBmV	39.6 dB	2072541668	6837	2925
12	Locked	QAM256	12	621000000 Hz	4.6 dBmV	39.4 dB	2072552580	6852	2976
13	Locked	QAM256	13	627000000 Hz	4.6 dBmV	39.4 dB	2072561310	6915	2929
14	Locked	QAM256	14	633000000 Hz	4.1 dBmV	39.4 dB	2072570921	6815	2893
15	Locked	QAM256	15	639000000 Hz	4.2 dBmV	39.5 dB	2072577250	6684	2887
16	Locked	QAM256	16	645000000 Hz	3.6 dBmV	39.2 dB	2072587133	6666	2858
17	Locked	QAM256	17	651000000 Hz	3.9 dBmV	39.2 dB	2072600023	6658	2739
18	Locked	QAM256	18	657000000 Hz	4.0 dBmV	39.3 dB	2072610125	6596	2736
19	Locked	QAM256	20	669000000 Hz	4.4 dBmV	39.5 dB	2072618981	6532	2682
20	Locked	QAM256	21	675000000 Hz	4.2 dBmV	38.9 dB	2072625275	6555	2603
21	Locked	QAM256	22	681000000 Hz	4.6 dBmV	39.5 dB	2072637536	6481	2538
22	Locked	QAM256	23	687000000 Hz	4.0 dBmV	39.5 dB	2072647004	6651	2522
23	Locked	QAM256	24	693000000 Hz	3.8 dBmV	39.5 dB	2072655994	6477	2562
24	Locked	QAM256	25	699000000 Hz	3.4 dBmV	39.4 dB	2072663741	6349	2494
25	Locked	QAM256	26	705000000 Hz	3.4 dBmV	39.1 dB	2072674521	6258	2491
26	Locked	QAM256	27	711000000 Hz	3.1 dBmV	39.1 dB	2072683575	6322	2431
27	Locked	QAM256	28	717000000 Hz	3.5 dBmV	39.1 dB	2072695293	6217	2405
28	Locked	QAM256	29	723000000 Hz	3.4 dBmV	39.3 dB	2072703397	6298	2388
29	Locked	QAM256	30	729000000 Hz	3.8 dBmV	39.0 dB	2072713065	6231	2378
30	Locked	QAM256	31	735000000 Hz	3.7 dBmV	39.3 dB	2072734995	6176	2324
31	Locked	QAM256	32	741000000 Hz	3.5 dBmV	39.5 dB	2072726086	6000	2410
32	Not Locked	Unknown	0	0 Hz	0.0 dBmV	0.0 dB	0	0	0

Upstream Bonded Channels

Channel	Lock Status	Modulation	Channel ID	Frequency	Power
1	Locked	ATDMA	41	37500000 Hz	49.5 dBmV
2	Locked	ATDMA	42	30700000 Hz	47.8 dBmV
3	Locked	ATDMA	43	25000000 Hz	46.3 dBmV
4	Locked	ATDMA	44	21400000 Hz	45.5 dBmV
5	Not Locked	Unknown	0	0 Hz	0.0 dBmV
6	Not Locked	Unknown	0	0 Hz	0.0 dBmV
7	Not Locked	Unknown	0	0 Hz	0.0 dBmV
8	Not Locked	Unknown	0	0 Hz	0.0 dBmV

Downstream OFDM Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power	SNR / MER	Active Subcarrier Number Range	Unerrored Codewords	Correctable Codewords	Uncorrectable Codewords
1	Locked	0, 1, 2	33	795000000 Hz	2.6 dBmV	37.8 dB	1588 ~ 2507	1503879443	1238028049	317
2	Not Locked	0	0	0 Hz	-49.0 dBmV	0.0 dB	0 ~ 4095	0	0	0

Upstream OFDMA Channels

Channel	Lock Status	Modulation / Profile ID	Channel ID	Frequency	Power
1	Not Locked	Unknown	0	0 Hz	0 dBmV
2	Not Locked	Unknown	0	0 Hz	0 dBmV

2023-06-17, 13:04:31	Notice (6)	CM-STATUS message sent. Event Type Code: 24; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 .;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 13:03:58	Notice (6)	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=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 13:03:47	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 2 .;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 13:02:42	Notice (6)	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=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 13:02:10	Notice (6)	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=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 13:00:41	Notice (6)	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=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 12:59:53	Notice (6)	CM-STATUS message sent. Event Type Code: 16; Chan ID: 33 ; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 .;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-17, 11:55:43	Error (4)	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-16, 02:10:19	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 .;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-16, 02:10:10	Error (4)	Primary address failed, secondary active;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-16, 02:10:10	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = APM
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 22:09:24	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-15, 21:48:26	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-13, 16:59:09	Critical (3)	Resetting the cable modem due to docsDevResetNow
2023-06-13, 16:56:18	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
2023-06-13, 16:55:58	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-06-13, 16:53:32	Critical (3)	Resetting the cable modem due to docsDevResetNow
Time Not Established	Critical (3)	DHCP failed - RS sent, no RA received;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:01:5c:b4:c8:98;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:c8:e7:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;

<Moderator Note: Do not post long log listings without using the "[ spoiler ] [ /spoiler]" tags>

bill001g · Jun 17, 2023

Your upstream power is not real good especially on the channel that gets 49.5. I forget the exact recommended values but when you get close to 50 you start having issues.

Key here is you are getting a lot of uncorrected code words....ie packet loss. Now if this has been running for a month then it is not bad but I suspect this only a couple days.

Sync errors are bad they many times cause the modem to retrain.

What this generically means is the ISP is having issues hearing your modem even though your modem can hear the ISP fine....you have good numbers on the downstream. This generally is a cable issue....most times outside your house. You can check all the cable you have access to. You are looking maybe for dirt or water in a connection. Maybe move the modem to connect to directly to the cable coming from the outside of the house without splitters or other stuff connected.

After that only the ISP can check stuff. Can be as simple as a small bit of water got into one of the connectors in one of the boxes on the street.

MM80 · Jun 17, 2023

bill001g said:
Your upstream power is not real good especially on the channel that gets 49.5. I forget the exact recommended values but when you get close to 50 you start having issues.

Key here is you are getting a lot of uncorrected code words....ie packet loss. Now if this has been running for a month then it is not bad but I suspect this only a couple days.

Sync errors are bad they many times cause the modem to retrain.

What this generically means is the ISP is having issues hearing your modem even though your modem can hear the ISP fine....you have good numbers on the downstream. This generally is a cable issue....most times outside your house. You can check all the cable you have access to. You are looking maybe for dirt or water in a connection. Maybe move the modem to connect to directly to the cable coming from the outside of the house without splitters or other stuff connected.

After that only the ISP can check stuff. Can be as simple as a small bit of water got into one of the connectors in one of the boxes on the street.

Thanks for the advice. I have a feeling the ATT fiber guys did something. The dug in my yard to bury their fiber lines. I'm wondering if they hit my cable line in the process. So you don't see anything wrong with the modem? (besides what you mentioned) I should probably just have a tech come out.

bill001g · Jun 18, 2023

If it is the main ATT fiber run where they are boring that they have all kinds of little flags so they don't hit power,water,gas phone lines etc. It was quite a show when they were doing it near me. Now the runs from the new boxes on the street to the house that they just use a shovel and cut a slot. They still have everything located so they don't for example hit a even a sprinkler system or in theory the phone and cable lines.

It would be a massive pain if they damaged the coax cable under the ground going to the box. They would have to run a new one and they would take the chance of cutting att fiber who would send a tech to replace that.

Hopefully it is something simple.

Now after it is all fixed you likely should check att rates. For me they were almost $40 a month lower for faster services and that was even after the first year. The first year they have larger discounts plus you can get like $150 for using their online thing to sign up rather than calling a phone number. There 5gbit plan though is kinda expensive.

For me comcast could care less, they were already more than att and then they increased the rates and when I called the best they would do is remove the new increase for 1 year even though they were $40 more before the increase.

MM80 · Jun 19, 2023

bill001g said:
If it is the main ATT fiber run where they are boring that they have all kinds of little flags so they don't hit power,water,gas phone lines etc. It was quite a show when they were doing it near me. Now the runs from the new boxes on the street to the house that they just use a shovel and cut a slot. They still have everything located so they don't for example hit a even a sprinkler system or in theory the phone and cable lines.

It would be a massive pain if they damaged the coax cable under the ground going to the box. They would have to run a new one and they would take the chance of cutting att fiber who would send a tech to replace that.

Hopefully it is something simple.

Now after it is all fixed you likely should check att rates. For me they were almost $40 a month lower for faster services and that was even after the first year. The first year they have larger discounts plus you can get like $150 for using their online thing to sign up rather than calling a phone number. There 5gbit plan though is kinda expensive.

For me comcast could care less, they were already more than att and then they increased the rates and when I called the best they would do is remove the new increase for 1 year even though they were $40 more before the increase.

Thanks for the help. I'm actually getting Optimums 1gig plan for a good price ($59) as the newly advertised fiber from ATT out here is $80 for the same speed. I've also been with them many years. You would think they would help a brother out!

Search

Question Netgear CM1000 DOCSIS 3.1 Power Levels

MM80

bill001g

Titan

MM80

bill001g

Titan

MM80

TRENDING THREADS

Latest posts

Moderators online

Share this page