Community Forum

CM1000 and Gigabit Service

Regular Visitor

CM1000 and Gigabit Service

Hello,

Recently moved into our new house and activated our Gigabit internet service last night.   When directly plugged into my Netgear CM1000 modem (using Cat 6 cables) with my laptop, the max speed I've been able to download has been 500Mbps;

I chatted with a Comcast rep earlier today and they said they've updated the modem to the latest firmware/boot file, but I'm still unable to achieve anything above 500Mbps when directly connected to the modem via ethernet cable;

I have attached the error codes and upstream/downstream info that I was able to copy/paste from the Netgear modem page.

Thank you

<tabindex=-1>Startup Procedure</tabindex=-1>
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 IPv6 only

<tabindex=-1>Downstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 29 663000000 Hz 0.0 dBmV 38.8 dB 1685296256 110 0
2 Locked QAM256 1 483000000 Hz -1.1 dBmV 39.8 dB 1683084745 47 0
3 Locked QAM256 2 489000000 Hz -1.0 dBmV 39.8 dB 1683089177 45 0
4 Locked QAM256 3 495000000 Hz -1.1 dBmV 39.8 dB 1683092598 51 0
5 Locked QAM256 4 507000000 Hz -0.6 dBmV 40.0 dB 1683096429 35 0
6 Locked QAM256 5 513000000 Hz -0.8 dBmV 39.9 dB 1683099590 54 0
7 Locked QAM256 6 519000000 Hz -0.8 dBmV 39.5 dB 1683104739 50 0
8 Locked QAM256 7 525000000 Hz -0.5 dBmV 39.9 dB 1683108288 33 0
9 Locked QAM256 8 531000000 Hz -0.6 dBmV 39.6 dB 1683117136 59 0
10 Locked QAM256 9 543000000 Hz -0.4 dBmV 39.9 dB 1683120219 71 0
11 Locked QAM256 10 549000000 Hz -0.6 dBmV 39.6 dB 1683124974 61 0
12 Locked QAM256 11 555000000 Hz -0.4 dBmV 39.7 dB 1683128442 59 0
13 Locked QAM256 12 561000000 Hz -0.3 dBmV 39.7 dB 1683131795 58 0
14 Locked QAM256 13 567000000 Hz -0.5 dBmV 39.5 dB 1683135976 78 0
15 Locked QAM256 14 573000000 Hz -0.6 dBmV 39.5 dB 1683139407 71 0
16 Locked QAM256 15 579000000 Hz -0.1 dBmV 39.6 dB 1683143524 35 0
17 Locked QAM256 16 585000000 Hz -0.3 dBmV 39.5 dB 1683149604 63 0
18 Locked QAM256 17 591000000 Hz -0.3 dBmV 39.4 dB 1683153278 82 0
19 Locked QAM256 18 597000000 Hz -0.4 dBmV 39.3 dB 1683157023 87 0
20 Locked QAM256 19 603000000 Hz -0.6 dBmV 39.2 dB 1683160704 125 0
21 Locked QAM256 20 609000000 Hz -0.8 dBmV 38.9 dB 1683164541 106 0
22 Locked QAM256 21 615000000 Hz -0.5 dBmV 39.1 dB 1683168320 75 0
23 Locked QAM256 22 621000000 Hz -0.7 dBmV 39.0 dB 1683171458 108 0
24 Locked QAM256 23 627000000 Hz -0.6 dBmV 39.1 dB 1683175548 111 0
25 Locked QAM256 24 633000000 Hz -0.3 dBmV 39.1 dB 1683184728 122 0
26 Locked QAM256 25 639000000 Hz -0.2 dBmV 39.0 dB 1683188956 141 0
27 Locked QAM256 26 645000000 Hz 0.0 dBmV 38.9 dB 1683191698 112 0
28 Locked QAM256 27 651000000 Hz 0.4 dBmV 39.0 dB 1683195909 109 0
29 Locked QAM256 28 657000000 Hz 0.0 dBmV 38.8 dB 1683199866 107 0
30 Locked QAM256 30 669000000 Hz 0.4 dBmV 38.9 dB 1683203394 113 0
31 Locked QAM256 31 675000000 Hz 0.5 dBmV 38.7 dB 1683203981 106 0
32 Locked QAM256 32 681000000 Hz 0.4 dBmV 38.6 dB 1683204344 112 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 1 30100000 Hz 50.8 dBmV
2 Locked ATDMA 2 36500000 Hz 49.8 dBmV
3 Locked ATDMA 3 17300000 Hz 50.3 dBmV
4 Locked ATDMA 4 23700000 Hz 50.3 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

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>
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 159 722000000 Hz 1.5 dBmV 35.5 dB 1126 ~ 2969 1435096011 44720379 3
2 Not Locked 0 0 0 Hz -4.9 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>
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

 

 

2019-08-02, 19:06:26 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 19:06:01 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 19:04:12 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 19:03:46 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 19:01:11 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 19:00:48 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 18:46:23 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 18:45:58 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 18:29:25 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 18:29:00 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 18:23:24 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 18:22:59 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 17:44:34 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 17:44:05 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 17:06:22 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 17:05:57 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 17:03:21 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 17:02:40 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 16:58:22 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 16:57:45 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 16:55:11 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 16:54:21 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 16:53:42 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 16:51:05 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 14:19:09 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 14:18:42 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 14:00:38 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 14:00:14 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 13:59:56 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 13:59:33 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 13:56:43 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 13:56:20 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 13:42:41 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 13:42:18 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 12:50:57 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 12:50:32 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 12:40:09 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 12:38:54 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 12:37:34 Notice (6) CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
2019-08-02, 12:35:54 Notice (6) CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=3c:37:86:ea:23:e0;CMTS-MAC=2c:86:d2:88:56:b3;CM-QOS=1.1;CM-VER=3.1;
Expert

Re: CM1000 and Gigabit Service

Not certain that this is the root cause of the problem but it should be addressed nevertheless. The upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, and latency problems.

In a self troubleshooting effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage types like GE, RadioShack, RCA, Philips, Leviton, Magnavox, and Rocketfish from big box stores like Home Depot, Lowes, Target, Wal-Mart etc. Splitters should be swapped with known to be good / new ones to test

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two way splitter connected directly off of the drop from the street/pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed, and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!