- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: CM1000 not getting Gigabit speed with Xfinity
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CM1000 not getting Gigabit speed with Xfinity
The Xfinity tech showed upwards of 1 Gig from the wall but I can't get a gig connected directly to the CM1000 modem. Please help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
What speed are you getting?
What device are you testing on?
What website are you using for test? (if its speedtest.com, try several of their servers, they don't always pick one that can max out the speed). Try speedtest.xfinity.com
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
I am having similar issues. I recently upgraded to gig speed through comcast. The engineer came and tested with his equipment and he was getting gig speed whereas I was not able to through my CM1000.
The version of Firmware is V7.01.01
The connection says Good
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. | |
|
<tabindex=-1>Startup Procedure</tabindex=-1>
Procedure | Status | Comment |
Acquire Downstream Channel | 651000000 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 | 37 | 651000000 Hz | 3.5 dBmV | 39.7 dB | 35383176 | 0 | 0 |
2 | Locked | QAM256 | 10 | 483000000 Hz | 4.4 dBmV | 41.6 dB | 34227231 | 0 | 0 |
3 | Locked | QAM256 | 11 | 489000000 Hz | 4.6 dBmV | 41.6 dB | 34230641 | 0 | 0 |
4 | Locked | QAM256 | 12 | 495000000 Hz | 4.7 dBmV | 41.6 dB | 34234480 | 0 | 0 |
5 | Locked | QAM256 | 13 | 507000000 Hz | 5.6 dBmV | 41.8 dB | 34238224 | 0 | 0 |
6 | Locked | QAM256 | 14 | 513000000 Hz | 6.0 dBmV | 41.8 dB | 34242485 | 0 | 0 |
7 | Locked | QAM256 | 15 | 519000000 Hz | 6.6 dBmV | 42.0 dB | 34245954 | 0 | 0 |
8 | Locked | QAM256 | 16 | 525000000 Hz | 7.0 dBmV | 41.9 dB | 34249929 | 0 | 0 |
9 | Locked | QAM256 | 17 | 531000000 Hz | 7.5 dBmV | 42.0 dB | 34253520 | 0 | 0 |
10 | Locked | QAM256 | 18 | 537000000 Hz | 8.1 dBmV | 41.9 dB | 34257380 | 0 | 0 |
11 | Locked | QAM256 | 19 | 543000000 Hz | 8.4 dBmV | 41.9 dB | 34260139 | 0 | 0 |
12 | Locked | QAM256 | 20 | 549000000 Hz | 8.6 dBmV | 42.0 dB | 34264724 | 0 | 0 |
13 | Locked | QAM256 | 21 | 555000000 Hz | 8.3 dBmV | 41.6 dB | 34268838 | 0 | 0 |
14 | Locked | QAM256 | 22 | 561000000 Hz | 7.7 dBmV | 41.6 dB | 34272310 | 0 | 0 |
15 | Locked | QAM256 | 23 | 567000000 Hz | 7.0 dBmV | 41.5 dB | 34275633 | 0 | 0 |
16 | Locked | QAM256 | 24 | 573000000 Hz | 6.3 dBmV | 41.5 dB | 34279322 | 0 | 0 |
17 | Locked | QAM256 | 25 | 579000000 Hz | 5.8 dBmV | 41.5 dB | 34286435 | 0 | 0 |
18 | Locked | QAM256 | 26 | 585000000 Hz | 5.2 dBmV | 41.2 dB | 34289971 | 0 | 0 |
19 | Locked | QAM256 | 27 | 591000000 Hz | 4.8 dBmV | 41.2 dB | 34293616 | 0 | 0 |
20 | Locked | QAM256 | 28 | 597000000 Hz | 4.5 dBmV | 41.2 dB | 34297375 | 0 | 0 |
21 | Locked | QAM256 | 29 | 603000000 Hz | 4.3 dBmV | 40.8 dB | 34301046 | 0 | 0 |
22 | Locked | QAM256 | 30 | 609000000 Hz | 3.9 dBmV | 40.7 dB | 34304945 | 0 | 0 |
23 | Locked | QAM256 | 31 | 615000000 Hz | 3.7 dBmV | 40.5 dB | 34308735 | 0 | 0 |
24 | Locked | QAM256 | 32 | 621000000 Hz | 3.8 dBmV | 40.6 dB | 34312095 | 0 | 0 |
25 | Locked | QAM256 | 33 | 627000000 Hz | 3.8 dBmV | 40.5 dB | 34316098 | 0 | 0 |
26 | Locked | QAM256 | 34 | 633000000 Hz | 3.8 dBmV | 40.3 dB | 34319935 | 0 | 0 |
27 | Locked | QAM256 | 35 | 639000000 Hz | 3.6 dBmV | 39.9 dB | 34323590 | 0 | 0 |
28 | Locked | QAM256 | 36 | 645000000 Hz | 3.4 dBmV | 39.8 dB | 34326994 | 0 | 0 |
29 | Locked | QAM256 | 38 | 657000000 Hz | 3.6 dBmV | 39.9 dB | 34330852 | 0 | 0 |
30 | Locked | QAM256 | 39 | 663000000 Hz | 3.8 dBmV | 40.1 dB | 34332078 | 0 | 0 |
31 | Locked | QAM256 | 40 | 669000000 Hz | 3.7 dBmV | 40.3 dB | 34332913 | 0 | 0 |
32 | Not Locked | Unknown | 0 | 0 Hz | 0.0 dBmV | 0.0 dB | 0 | 0 | 0 |
<tabindex=-1>Upstream Bonded Channels</tabindex=-1>
Channel | Lock Status | Modulation | Channel ID | Frequency | Power |
1 | Locked | ATDMA | 1 | 35600000 Hz | 43.0 dBmV |
2 | Locked | ATDMA | 2 | 29200000 Hz | 43.0 dBmV |
3 | Locked | ATDMA | 3 | 22800000 Hz | 42.3 dBmV |
4 | Locked | ATDMA | 4 | 16400000 Hz | 40.8 dBmV |
5 | Locked | ATDMA | 9 | 40400000 Hz | 41.3 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, 1, 2, 3 | 41 | 722000000 Hz | 4.5 dBmV | 39.3 dB | 1228 ~ 2867 | 8573472 | 2928532 | 0 |
2 | Not Locked | 0 | 0 | 0 Hz | 4.8 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 |
Current System Time: Sun Oct 18 20:23:53 2020 System Up Time: 0:13:19
The event logs have the following issues
Time | Priority | Description |
2020-10-18, 20:11:17 | Notice (6) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=a0:04:60:fc:4f:50;CMTS-MAC=00:01:5c:b2:02:92;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Notice (6) | Honoring MDD; IP provisioning mode = IPv6 |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:4f:50;CMTS-MAC=00:01:5c:b2:02:92;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:4f:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | No Ranging Response received - T3 time-out;CM-MAC=a0:04:60:fc:4f:50;CMTS-MAC=00:01:5c:b2:02:92;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:4f:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Time Not Established | Critical (3) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=a0:04:60:fc:4f:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; |
Can someone help explain what the issue is with me not getting Gig speeds. I max out at 230 to 250 mpbs.
Please HELP.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
I tested directly hardwired through a laptop to my modem.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
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.
Be sure to power OFF the modem for 1 minute them back ON.
Factory reset the modem as well.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Mod...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
Furrye38,
The ISP provider in this case Comcast came home yesterday and checked the quality of the signal coming inside the home. The was able to remove some issues with some interference and was able to demonstrate through his equipment that the signal was strong and he was gettting more than 1 gig connection for download.
And he connected the modem directly to the incoming RG6 Coax. While debugging by connecting my laptop directly to the modem ethernet out I also did the following
(a) I rebooted the modem several times and tried the connection
(b) Factory reset
(c) Each time waited a few mins (powered off, removed the coax connection, removed power input)
Both did not solve the issue.
I had asked the ISP to reprovision the modem before the Tech came in yesterday and that was not successful either. The only thing I have not done is to as them to reprovision after the tech came to visit. I will try that today and repost and see if it that makes a difference.
Would love for someone more knowledgeable than me to look at the settings I posted and logs and see if there is something they see glaring that I might be able to work with Comcast to fix.
Thanks again to everyone who is helping me resolve this !
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
Seems like the ISP has checked everything. Seems like the the modem itself maybe the problem. I would get another modem put in place to see if the problem continutes...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
Do the logs indicate any issues?
Also I will see a reprovision helps from Comcast.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
I see some T3 time outs.
This one user had similar time outs with there modem. Replaced it and now there up and running:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
Thanks for the post. Read the post indicated two issues
(a) T3 issues with line or modem (have to check)
(b) Issues with modem rebooting (that surely needed a modem replacement).
Helps me narrow it down. Thanks again for your help. I will see what my ISP says about T3 timeout issues.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
Lets us know how it goes...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: CM1000 not getting Gigabit speed with Xfinity
Here is what I found out more for T3 Timeouts.
T3 ( Ranging Request Retries Exhausted )
Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.
T3 timeouts result when a Cable Modem, that is locked into the downstream, transmits a Ranging Request(RNG-REQ) to the CMTS(Cable Modem Termination System) and 200 milliseconds passes without the CM receiving a Ranging Response(RNG-RSP) from the CMTS. Indeed, maintaining a PING(Packet InterNet Groper) less than 200ms is important to a healthy DOCSIS network. When 10 T3s occur in succession (a period of 20 seconds passes without the CM receiving a Ranging Response, the CM will cease attempting to communicate with the HFC(Hybrid Fiber Optic Coaxial) network and reset its DOCSIS interface. In this case the RESET statistic on the modem log will increment but not all T3s will cause a reset if communication is restored within 10 T3 periods or 20 seconds. When T3 timeouts occur, but not enough occur in succession to trigger a reset, slow speeds are often a symptom as these timeouts slow down the TCP/IP handshakes necessary to maintain internet connections.
T3 Timeouts are typically caused by Upstream Noise causing Ranging Requests to not be clearly received by the CMTS. T3 problems can often be intermittant in nature as they may be the result of noise originating in any part of the plant that shares the same line card at the CMTS with the subscriber impacted. In fact, T3s can even be caused by noise originating on other neighboring nodes if resources are shared at the headend. Speed issues and intermittant connectivity issues are some of the most common problems encounted on our Trouble Calls.
T3 Timeouts can also be encountered when the plant's noise floor is so severe that the CM cannot overtalk it (SNR is bad and Noise power level is higher than your modem's signal). This can affect a single leg of the plant or even entire nodes. When a high noise floor results in several modems resetting their DOCSIS interface because 10 T3 timeouts have occured in succession, as we covered above, this is referred to as a noise outage. Noise outages frequently occur node-wide and while some may self-clear, many continue until a Plant Maintenence Technician locates and repairs the offending source of noise. This is why we ALL must be vigilant about preventing noise from entering the plant.
Occurrence: Extremely common in the customer homes
Symptom: Will cause intermittent disconnections. If you see couple of them, it is fine. If you quite a few of them consecutively, then it will lead to disconnections.
Example:
2017-6-14, 00:05:06 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=00:11:22:c1:db:09;CMTS-MAC=4c:00:82:ee:bd:62;CM-QOS=1.0;CM-VER=3.0
Fixes:
1. Check for the loose or Bad cables. This is by far most neglected and most common fix.
2. Remove extra splitters in house
3. Buy powered amplifier to boost your upstream power
4. Buy better coaxial cables
5. Call for a technician visit to inspect and fix cables outside and inside home (could be rain damage, fire damage, animal damage, construction damage, etc)
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more