NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

GFT's avatar
GFT
Aspirant
Oct 28, 2022
Solved

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...
  • FURRYe38's avatar
    FURRYe38
    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. 

     

     

GFT's avatar
GFT
Aspirant
Oct 28, 2022

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 Channel507000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
SecurityEnabledBPI+
 
 
Downstream Bonded Channels 
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1LockedQAM25613507000000 Hz5.2 dBmV40.6 dB40
2LockedQAM2561417000000 Hz5.8 dBmV41.6 dB10
3LockedQAM2562423000000 Hz5.6 dBmV41.5 dB10
4LockedQAM2563435000000 Hz5.9 dBmV41.6 dB10
5LockedQAM2564447000000 Hz5.7 dBmV41.3 dB30
6LockedQAM2565453000000 Hz6.0 dBmV41.5 dB10
7LockedQAM2566459000000 Hz5.6 dBmV41.2 dB10
8LockedQAM2567465000000 Hz6.0 dBmV41.4 dB10
9LockedQAM2568471000000 Hz6.0 dBmV41.3 dB20
10LockedQAM2569477000000 Hz5.9 dBmV40.9 dB20
11LockedQAM25610483000000 Hz6.2 dBmV41.1 dB10
12LockedQAM25611489000000 Hz5.8 dBmV40.8 dB10
13LockedQAM25612495000000 Hz5.8 dBmV40.8 dB20
14LockedQAM25614513000000 Hz4.6 dBmV40.3 dB10
15LockedQAM25615519000000 Hz3.6 dBmV39.7 dB20
16LockedQAM25616525000000 Hz2.2 dBmV38.9 dB20
17LockedQAM25617531000000 Hz5.4 dBmV40.5 dB10
18LockedQAM25618537000000 Hz6.9 dBmV41.2 dB10
19LockedQAM25619543000000 Hz7.2 dBmV41.1 dB10
20LockedQAM25620549000000 Hz7.3 dBmV41.3 dB20
21LockedQAM25621555000000 Hz6.9 dBmV40.9 dB10
22LockedQAM25622561000000 Hz7.0 dBmV40.8 dB30
23LockedQAM25623567000000 Hz7.5 dBmV41.0 dB10
24LockedQAM25624573000000 Hz7.2 dBmV40.6 dB40
25LockedQAM25625579000000 Hz7.5 dBmV40.7 dB00
26LockedQAM25626585000000 Hz7.4 dBmV40.5 dB00
27LockedQAM25627591000000 Hz7.3 dBmV40.3 dB10
28LockedQAM25628597000000 Hz7.6 dBmV40.5 dB10
29LockedQAM25629603000000 Hz7.0 dBmV40.0 dB20
30LockedQAM25630609000000 Hz7.0 dBmV40.0 dB20
31LockedQAM25631615000000 Hz6.9 dBmV40.0 dB00
32LockedQAM25632621000000 Hz6.8 dBmV39.8 dB50
 
 
Upstream Bonded Channels 
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1LockedATDMA9256010400000 Hz34.8 dBmV
2LockedATDMA10512016400000 Hz34.3 dBmV
3LockedATDMA11512022800000 Hz34.3 dBmV
4LockedATDMA12512029200000 Hz34.8 dBmV
5LockedATDMA13512035600000 Hz34.8 dBmV
6LockedATDMA14256040400000 Hz34.8 dBmV
7Not LockedUnknown000 Hz0.0 dBmV
8Not LockedUnknown000 Hz0.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
1Locked0 ,1 ,2 ,3159722000000 Hz9.7 dBmV40.0 dB1186 ~ 290928012965218684270
2Not Locked000 Hz0 dBmV0.0 dB0 ~ 4095000
 
 
Upstream OFDMA Channels 
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1Not Locked000 Hz0 dBmV
2Not Locked000 Hz0 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's avatar
GFT
Aspirant
Oct 28, 2022
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's avatar
    FURRYe38
    Guru - Experienced User
    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. 

     

     

    • GFT's avatar
      GFT
      Aspirant
      Oct 28, 2022

      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.