Netgear CM2050V connection type

[GFT]

I have been using a Netgear C7100V DOCSIS3.0 modem for several years and have found find that it consistently runs at about 10% of the rates that Comcast hypes to me. I borrowed an Arris SURFboard SB8200 DOCSIS3.1 modem and found that it tripled my download speeds (no change to upload). Liking that result I purchased a Netgear CM2050V modem (its label says both DOCSIS3.0 and DOCSIS3.1) and installed it. Testing it I found that it delivers results that are identical to the C7100V (within the repeatability of the test).

I've looked at the CM2050V status, but it doesn't say much. Is there a way to tell if it is connecting to Comcast using DOCSIS3.0 or DOCSIS3.1? If so is there a way to modify the connection type or is that auto-negotiated and beyond my influence?

[FURRYe38 · Accepted solution]

Yes, criticals needs to be reviewed by the ISP and resolved with there help. 

I see some correct and un-correctables but not really enough to be worried about. 
Check all cabling and coas line fittings and besure they are snug. 

Power is a tad bit high. MIght ask the ISP if they could lower it some maybe. 

CAT5 IS NOT rated for 1000Mbps, You should be using CAT6 UTP between the modem and RBR and RBR to RBS if they are ethernet connected. IF you had the 8 series, then you would use CAT6A STP between the modem and RBR. 

[FURRYe38]

Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-m...
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-mode...

Be sure your using a good quality LAN cable between the modem and router. CAT6 is recommended. 
What is the brand and model of the host wifi router connected to the modem?

Have the ISP check the signal and line quality UP to the modem. 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. 
Be sure your using good quality RG6 coax cable up to the modem. 
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-Mod...
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

[GFT]

I've using the same cables with both the SB8200 and the CM2050V, I just pulled one out and inserted the other. The Coax is from Comcast, labeled "TFC-T10" and "6 series". I don't know how to interpret those.

The LAN cable between the modem (on one end of the house) and router (an Orbi RBR750 in the middle of the house) has a pair of connectors and 10+ meters of cat5 cable behind the wall. The other runs in the house (including some that are twice as long) seem to support 1000baseT. The transfers between computers with wired connections are definitely faster than using WiFi (when I unplug their cables and use WiFi the data rate drops 5 to 10x). While I could see this cabling impacting the speed test, I wouldn't expect the cat5 cables to impact the communications from the cable head to the modem. And all of this wiring was used with both the SB8200 and the CM2050V. That routing also was in place before the Orbi was installed. I could move the router to the wiring closet with the modem and rearrange the satellites, but I'll connect a computer directly to the modem and test that before I take that step.

The Modem Status is:

Cable Connection

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
Startup Procedure
Procedure Status Comment Acquire Downstream Channel 507000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 13 507000000 Hz 5.2 dBmV 40.6 dB 4 0 2 Locked QAM256 1 417000000 Hz 5.8 dBmV 41.6 dB 1 0 3 Locked QAM256 2 423000000 Hz 5.6 dBmV 41.5 dB 1 0 4 Locked QAM256 3 435000000 Hz 5.9 dBmV 41.6 dB 1 0 5 Locked QAM256 4 447000000 Hz 5.7 dBmV 41.3 dB 3 0 6 Locked QAM256 5 453000000 Hz 6.0 dBmV 41.5 dB 1 0 7 Locked QAM256 6 459000000 Hz 5.6 dBmV 41.2 dB 1 0 8 Locked QAM256 7 465000000 Hz 6.0 dBmV 41.4 dB 1 0 9 Locked QAM256 8 471000000 Hz 6.0 dBmV 41.3 dB 2 0 10 Locked QAM256 9 477000000 Hz 5.9 dBmV 40.9 dB 2 0 11 Locked QAM256 10 483000000 Hz 6.2 dBmV 41.1 dB 1 0 12 Locked QAM256 11 489000000 Hz 5.8 dBmV 40.8 dB 1 0 13 Locked QAM256 12 495000000 Hz 5.8 dBmV 40.8 dB 2 0 14 Locked QAM256 14 513000000 Hz 4.6 dBmV 40.3 dB 1 0 15 Locked QAM256 15 519000000 Hz 3.6 dBmV 39.7 dB 2 0 16 Locked QAM256 16 525000000 Hz 2.2 dBmV 38.9 dB 2 0 17 Locked QAM256 17 531000000 Hz 5.4 dBmV 40.5 dB 1 0 18 Locked QAM256 18 537000000 Hz 6.9 dBmV 41.2 dB 1 0 19 Locked QAM256 19 543000000 Hz 7.2 dBmV 41.1 dB 1 0 20 Locked QAM256 20 549000000 Hz 7.3 dBmV 41.3 dB 2 0 21 Locked QAM256 21 555000000 Hz 6.9 dBmV 40.9 dB 1 0 22 Locked QAM256 22 561000000 Hz 7.0 dBmV 40.8 dB 3 0 23 Locked QAM256 23 567000000 Hz 7.5 dBmV 41.0 dB 1 0 24 Locked QAM256 24 573000000 Hz 7.2 dBmV 40.6 dB 4 0 25 Locked QAM256 25 579000000 Hz 7.5 dBmV 40.7 dB 0 0 26 Locked QAM256 26 585000000 Hz 7.4 dBmV 40.5 dB 0 0 27 Locked QAM256 27 591000000 Hz 7.3 dBmV 40.3 dB 1 0 28 Locked QAM256 28 597000000 Hz 7.6 dBmV 40.5 dB 1 0 29 Locked QAM256 29 603000000 Hz 7.0 dBmV 40.0 dB 2 0 30 Locked QAM256 30 609000000 Hz 7.0 dBmV 40.0 dB 2 0 31 Locked QAM256 31 615000000 Hz 6.9 dBmV 40.0 dB 0 0 32 Locked QAM256 32 621000000 Hz 6.8 dBmV 39.8 dB 5 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 9 2560 10400000 Hz 34.8 dBmV 2 Locked ATDMA 10 5120 16400000 Hz 34.3 dBmV 3 Locked ATDMA 11 5120 22800000 Hz 34.3 dBmV 4 Locked ATDMA 12 5120 29200000 Hz 34.8 dBmV 5 Locked ATDMA 13 5120 35600000 Hz 34.8 dBmV 6 Locked ATDMA 14 2560 40400000 Hz 34.8 dBmV 7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
Downstream OFDM Channels
Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0 ,1 ,2 ,3 159 722000000 Hz 9.7 dBmV 40.0 dB 1186 ~ 2909 28012965 21868427 0 2 Not Locked 0 0 0 Hz 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 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV
Current System Time:Fri Oct 28 11:47:06 2022
System Up Time:00:16:48

The event log has lots of warnings and 6 critical entries. There are at least 3 power up events in there. It's also too long to post in this message so I'll put it in another reply.

[GFT]

Event Log

Time Priority Description Fri Oct 28 11:43:23 2022 (Warning (5)) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 11:43:21 2022 (Critical (3)) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 11:31:25 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 11:31:15 2022 (Warning (5)) Dynamic Range Window violation Fri Oct 28 11:31:15 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 11:31:15 2022 (Warning (5)) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 11:31:10 2022 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 11:31:05 2022 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:22:14 2022 (Warning (5)) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:22:12 2022 (Critical (3)) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:10:15 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:10:07 2022 (Warning (5)) Dynamic Range Window violation Fri Oct 28 10:10:07 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:10:06 2022 (Warning (5)) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:10:01 2022 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 10:09:56 2022 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:32:14 2022 (Warning (5)) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:32:12 2022 (Critical (3)) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:20:16 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:20:08 2022 (Warning (5)) Dynamic Range Window violation Fri Oct 28 09:20:08 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:20:08 2022 (Warning (5)) Dynamic Range Window violation Fri Oct 28 09:20:08 2022 (Warning (5)) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:20:08 2022 (Warning (5)) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:20:03 2022 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:19:58 2022 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:14:02 2022 (Notice (6)) CM-STATUS message sent. Event Type Code: 5; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:13:53 2022 (Warning (5)) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:13:47 2022 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:13:42 2022 (Notice (6)) TLV-11 - unrecognized OID;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=dc:eb:94:b5:45:5d;CM-QOS=1.1;CM-VER=3.1; Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6 Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:b3:55:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Fri Oct 28 09:12:25 2022 (Notice (6)) SW download Successful - Via Config file Fri Oct 28 09:11:23 2022 (Notice (6)) SW Download INIT - Via Config file d11_v_cm2050vims_walledgarden.cm

[FURRYe38 · Accepted solution]

Yes, criticals needs to be reviewed by the ISP and resolved with there help. 

I see some correct and un-correctables but not really enough to be worried about. 
Check all cabling and coas line fittings and besure they are snug. 

Power is a tad bit high. MIght ask the ISP if they could lower it some maybe. 

CAT5 IS NOT rated for 1000Mbps, You should be using CAT6 UTP between the modem and RBR and RBR to RBS if they are ethernet connected. IF you had the 8 series, then you would use CAT6A STP between the modem and RBR. 

[GFT]

I agree that cat5 is not rated for 1000baseT, but it seems that I sometimes get away with it on shorter lengths that need less equalization.

I moved the Orbi next to the modem and connected them with the cat5e (not cat6) cable that came in the modem box. The multi-gig light on the modem indicates that it established a 1 Gbps connection with the Orbi (it did that inconsistently through the old wiring). That improved my download speed 10x over the C7100V, to 947 Mbps! This is in spite of the fact that the connection from the Orbi to the computer running the speed test is still the same old behind the walls cat5 cable. But if I update the router to a series 8 with a 2.5Gbps WAN connection maybe I'd be able to deliver that same rate over more than one LAN channel in parallel. That's something for another day.

Moving the Orbi next to the modem didn't do anything for the upload speed, but I wasn't expecting that it would. This is more than good enough for now.