NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
GFT
Oct 28, 2022Aspirant
Netgear CM2050V connection type
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 SB...
- Oct 28, 2022
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
Oct 28, 2022Guru - Experienced User
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-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router
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-Modems/m-p/1530376#M12853
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
Oct 28, 2022Aspirant
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
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Startup Procedure | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream Bonded Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream Bonded Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Downstream OFDM Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Upstream OFDMA Channels | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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.
- GFTOct 28, 2022AspirantEvent 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 - FURRYe38Oct 28, 2022Guru - Experienced User
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.
- GFTOct 28, 2022Aspirant
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.