Netgear CM2000 modem downstream light blinking and status "BAD"
I got Gigabit internet, since a week ago, the download speed fluctuates a lot, sometimes only 0.2 mbps, sometimes 50 mbps, I found that the Netgear CM2000 modem downstream light keep blinking, Here is the Netgear CM2000 log, any help is greatly appreciated.
Cable Connection
Cancel Apply
Cable Diagnostic
Status: Poor
Action: [Partial Service] If the Partial Service mode does not go away within a few hours (Click the Refresh button after each step): 1) Make sure the coaxial cable is tightly connected. 2) Remove any unnecessary splitters. 3) Replace any required ones. 4) Contact your service provider for troubleshooting help. [Downstream Power Level/Downstream SNR] Try these actions (Click the Refresh button after each step): 1) Make sure the coaxial cable is tightly connected. 2) Remove any unnecessary splitters. 3) Replace any required splitters. 4) Contact your service provider for troubleshooting help.
CM Status:
Downstream Status:
Upstream Status:
Refresh Save Cable Diagnostic Info
Advanced Information
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.
Please redact all of the CM MAC and the CMTS MAC addresses from your second post of the error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".
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? Please mark an Accepted Answer!
Well that's true. Downstream power is out of spec. Should be -7 to +7 dBmV (in a perfect world that doesn't happen it would be 0dBmV), and SNR (signal to noise) really does need to be over 35dB. OFDM uncorrectables are never good and signal is really low there. It's a mess there.
If you want to look at it yourself, take a look here: https://forums.xfinity.com/conversations/your-home-network/internet-troubleshooting-tips/602dae4ac5375f08cde52ea0 Splitters/bad cable/bad connectors. A powered amp perhaps that isn't plugged in if you have one, etc. If you can get to were the service enters the residence from the street, bypass your house wiring entirely for a test and try the coax there. Then you'll know if there is anything you can do about it, or if that's what it looks like coming in from the street.
You could try doing a "factory default" reset on the CM2000 if something got wrapped around the axle with a firmware/config file push, but the signal you are seeing is pretty ugly. That's probably not going to be it.
user_zqts3p
2 Messages
1 year ago
Here is the event log:
(edited)
2
0
flatlander3
Problem Solver
•
1.5K Messages
1 year ago
Well that's true. Downstream power is out of spec. Should be -7 to +7 dBmV (in a perfect world that doesn't happen it would be 0dBmV), and SNR (signal to noise) really does need to be over 35dB. OFDM uncorrectables are never good and signal is really low there. It's a mess there.
If you want to look at it yourself, take a look here: https://forums.xfinity.com/conversations/your-home-network/internet-troubleshooting-tips/602dae4ac5375f08cde52ea0 Splitters/bad cable/bad connectors. A powered amp perhaps that isn't plugged in if you have one, etc. If you can get to were the service enters the residence from the street, bypass your house wiring entirely for a test and try the coax there. Then you'll know if there is anything you can do about it, or if that's what it looks like coming in from the street.
You could try doing a "factory default" reset on the CM2000 if something got wrapped around the axle with a firmware/config file push, but the signal you are seeing is pretty ugly. That's probably not going to be it.
(edited)
0
0