Community Forum

Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier

Regular Visitor

Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier

I have been calling into tech support all day today. Paid for Gig internet and have had nothing but "reset your modem" let us send another signal.  I think the boot file is wrong. Keep getting Critical on my log. I have a tech coming thursday AM. Anyway would love to get your guys thoughts. Here are my signals as well as my log.

 

 

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 621000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 621000000 Hz 8.8 dBmV 43.6 dB 0 0
2 Locked QAM256 1 507000000 Hz 5.8 dBmV 40.3 dB 0 0
3 Locked QAM256 2 513000000 Hz 5.8 dBmV 41.3 dB 0 0
4 Locked QAM256 3 519000000 Hz 5.7 dBmV 41.3 dB 10 23
5 Locked QAM256 4 525000000 Hz 5.7 dBmV 41.2 dB 0 0
6 Locked QAM256 5 531000000 Hz 6 dBmV 41.5 dB 0 0
7 Locked QAM256 6 537000000 Hz 6.3 dBmV 41.8 dB 0 0
8 Locked QAM256 7 543000000 Hz 6.8 dBmV 42.3 dB 15 0
9 Locked QAM256 8 549000000 Hz 7.2 dBmV 42.7 dB 29 0
10 Locked QAM256 9 555000000 Hz 7 dBmV 42.6 dB 0 0
11 Locked QAM256 10 561000000 Hz 7.1 dBmV 42.8 dB 0 0
12 Locked QAM256 11 567000000 Hz 7.2 dBmV 42.9 dB 24 0
13 Locked QAM256 13 579000000 Hz 7.7 dBmV 43.1 dB 0 0
14 Locked QAM256 14 585000000 Hz 7.9 dBmV 43.5 dB 0 0
15 Locked QAM256 15 591000000 Hz 8.2 dBmV 43.6 dB 0 0
16 Locked QAM256 16 597000000 Hz 8.3 dBmV 43.6 dB 10 0
17 Locked QAM256 18 609000000 Hz 8.8 dBmV 44.5 dB 0 0
18 Locked QAM256 23 639000000 Hz 9.6 dBmV 44.6 dB 0 0
19 Locked QAM256 25 651000000 Hz 9.7 dBmV 44.6 dB 0 0
20 Locked QAM256 27 663000000 Hz 10 dBmV 44.6 dB 0 0
21 Locked QAM256 28 669000000 Hz 10 dBmV 44.6 dB 0 0
22 Locked QAM256 29 675000000 Hz 10.1 dBmV 44.6 dB 0 0
23 Locked QAM256 30 681000000 Hz 9.9 dBmV 44.6 dB 0 0
24 Locked QAM256 32 693000000 Hz 10.2 dBmV 44.9 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 36 5120 Ksym/sec 17300000 Hz 36.8 dBmV
2 Locked ATDMA 33 5120 Ksym/sec 36500000 Hz 36.5 dBmV
3 Locked ATDMA 34 5120 Ksym/sec 30100000 Hz 37 dBmV
4 Locked ATDMA 35 5120 Ksym/sec 23700000 Hz 37.3 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
 
Current System Time:Tue Jan 08 15:56:41 2019


Expert

Re: Netgear C7000 getting topping out at 300mbps down/12mbs up Speeds wired on Gig tier

You are not going to be able to get gig speed with that DOCSIS 3.0 modem. You need a DOCSIS 3.1 capable modem for that;

 

https://www.amazon.com/Next-Generation-ARRIS-SURFboard-SB8200-DOCSIS/dp/B01N6SKK1G

 

https://www.amazon.com/Motorola-MB8600-Certified-Comcast-Communications/dp/B0723599RQ

 

https://www.amazon.com/NETGEAR-CM1000-DOCSIS-Ultra-High-download/dp/B01I5TJGSE

 



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!
Regular Visitor

Re: Netgear C7000 getting topping out at 300mbps down/12mbs up Speeds wired on Gig tier

how so? It is an approved modem and not only that it says it can go up to 865mbps...i dont care if i dont get the full gig speeds, but id like to get better speeds than 300mbps.

 

 

Regular Visitor

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier

Event Log

               
 
 
 
 
Time Priority Description
2018-12-18, 01:05:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:16 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:16 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:21 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:47 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:49 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:51 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:05:57 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2018-12-18, 01:06:30 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.1;CM-VER=3.0;
2018-12-19, 02:56:29 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.1;CM-VER=3.0;
2018-12-20, 14:52:17 Critical (3) Resetting the cable modem due to docsDevResetNow
1970-1-1, 00:00:41 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2018-12-21, 00:17:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.1;CM-VER=3.0;
2019-1-1, 18:24:10 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.1;CM-VER=3.0;
2019-1-1, 18:24:39 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2019-1-2, 05:34:13 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.1;CM-VER=3.0;
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2019-1-8, 12:57:57 Critical (3) Resetting the cable modem due to docsDevResetNow
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:46 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
2019-1-8, 13:38:43 Critical (3) Resetting the cable modem due to docsDevResetNow
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:45 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:39 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2019-1-8, 15:10:55 Critical (3) Resetting the cable modem due to docsDevResetNow
1970-1-1, 00:00:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl0] set to Channel 9 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:42 Notice (6) WiFi Interface [wl1] set to Channel 153 (Side-Band Channel:N/A) - Reason:INTERFERENCE
1970-1-1, 00:00:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:b9:8a:87:2b:00;CMTS-MAC=00:01:5c:63:f2:4a;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:51 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Expert

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier

I stand by what I posted. Sorry, they will only deliver the gig speed tier via a DOCSIS 3.1 modem that has an OFDM / PLC downstream channel.

 

When using a non DOCSIS 3.1 modem, they will push a lower speed tier / default speed configuration file to it..



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!
Regular Visitor

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier

So they are forcing me to upgrade to use their service even though my modem is more than capable of getting 900+mbs speeds.
Silver Problem Solver

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier


@Jthiel83 wrote:
So they are forcing me to upgrade to use their service even though my modem is more than capable of getting 900+mbs speeds.

The speed is not the issue; you have to have the correct hardware in the modem in order to support gigabit.

I am not a Comcast Employee.
I am just a customer, volunteering my time to help other customers here in the Forums.
Was your question answered? Mark the post as best answer!
Expert

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier


@Jthiel83 wrote:
So they are forcing me to upgrade to use their service even though my modem is more than capable of getting 900+mbs speeds.

That is a typical BLOATED manufacturer's speed claim gotten under pristine laboratory conditions. You would never get that under real world conditions....



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!
Regular Visitor

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier

Not pointing any fingers, but this seems a little fishy. Why would he be able to get 800-900mbps speeds when he hooks up his old c7000 router but because Comcast thinks it’s the xb6. I’m just saying bloated numbers are the 1.9 gigabit speeds, but it should handle easily 800-900 and what this guy did proves it. Now I’m going to just bite the bullet and buy a CM1000 modem because I’m tired of dealing with lies and deception.

https://www.reddit.com/r/Comcast_Xfinity/comments/6lr00j/wanting_to_upgrade_to_the_docsis_31_gigabit...
Expert

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier


@Jthiel83 wrote:
Not pointing any fingers, but this seems a little fishy. Why would he be able to get 800-900mbps speeds when he hooks up his old c7000 router but because Comcast thinks it’s the xb6. I’m just saying bloated numbers are the 1.9 gigabit speeds, but it should handle easily 800-900 and what this guy did proves it. Now I’m going to just bite the bullet and buy a CM1000 modem because I’m tired of dealing with lies and deception.

https://www.reddit.com/r/Comcast_Xfinity/comments/6lr00j/wanting_to_upgrade_to_the_docsis_31_gigabit...

There are no "lies and deception" here. Comcast has always mandated that you use an approved device for your speed tier on their network, and if you go to https://mydeviceinfo.xfinity.com you'll see that the Netgear C7000 gateway isn't rated for gigabit.

 

It's certainly *possible* to get near gigabit speeds on DOCSIS 3.0; a few small scale cable companies are able to do this. However, that kind of usage would tax the bandwidth on the DOCSIS channels to the point where they would be practically unusable for the rest of the customers being served by the CMTS. That would be tantamount to opening your own water theme park in your home and using all the water pressure for it, depriving your neighbors of water use. The customer's modem there probably got an incorrect configuration file, then got flagged and deactivated for excessive bandwidth use. 

 

There's a reason for Comcast's deployment of DOCSIS 3.1 .

 

Seeing as you've gotten yourself a CM1000, which is an excellent modem, you should easily achieve the speeds your're paying for. 

 

 


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!
Expert

Re: Netgear C7000 topping out at 300mbps down/12mbs up Speeds wired on Gig tier


@darkangelic wrote:

if you go to https://mydeviceinfo.xfinity.com you'll see that the Netgear C7000 gateway isn't rated for gigabit.

It's certainly *possible* to get near gigabit speeds on DOCSIS 3.0; a few small scale cable companies are able to do this. 

 

Yeah and certainly not with only having 24 downstream channels that the C7000 offers. The 32 channel option would be needed.


 



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!