NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Retired_Member
Mar 10, 2017Internet Routinely Cuts Out, Upstream and Downstream LEDs switch to amber
I moved about two months ago, and got set up with comcast.
Since then, my modem seems to cut out multiple times a day. It doesn't fully reboot, it doesn't seem to lose power or anything, just the connection fails and the upstream and downstream LEDs switch from solid green to amber.
After a minute or two, the lights usually switch back to green and I am able to connect again. Sometimes it takes closer to 10 minutes.
I've talked to comcast and they say the signal is being sent from their end without issue. They told me to contact netgear, but the router is about 3 years old and I don't feel like paying for support at this point.
The device log shows various events happening on a regular basis, but I don't know what any of them mean, and I haven't been able to get any reall explanation either way. I'd post the log information here, but it won't load the page for me to collect the data right now. Multile different warning levels and event names and such. I just don't know how to interpret it.
Mostly I want to know whether my modem is dying. Or if there is something else I can do to fix this.
4 Replies
- DarrenMSr. NETGEAR Moderator
Hello creepsalsa
Are you able to get to the log page to post them?
DarrenM
- Retired_Member
Procedure Status Comment Acquire Downstream Channel 657000000 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 21 657000000 Hz 2.8 dBmV 38.2 dB 106 204 2 Locked QAM256 9 585000000 Hz 5.1 dBmV 39.6 dB 0 0 3 Locked QAM256 10 591000000 Hz 5.1 dBmV 39.6 dB 0 0 4 Locked QAM256 11 597000000 Hz 5.6 dBmV 39.9 dB 0 0 5 Locked QAM256 12 603000000 Hz 4.7 dBmV 39.4 dB 0 0 6 Locked QAM256 13 609000000 Hz 4.2 dBmV 39.1 dB 0 0 7 Locked QAM256 14 615000000 Hz 4.8 dBmV 39.4 dB 0 0 8 Locked QAM256 15 621000000 Hz 4.5 dBmV 39.3 dB 0 0 9 Locked QAM256 16 627000000 Hz 4.1 dBmV 39.1 dB 0 0 10 Locked QAM256 17 633000000 Hz 4 dBmV 39 dB 0 0 11 Locked QAM256 18 639000000 Hz 3.7 dBmV 38.7 dB 0 0 12 Locked QAM256 19 645000000 Hz 3.7 dBmV 38.8 dB 0 0 13 Locked QAM256 20 651000000 Hz 3.6 dBmV 38.7 dB 0 0 14 Locked QAM256 22 663000000 Hz 3.1 dBmV 38.3 dB 0 0 15 Locked QAM256 23 669000000 Hz 3.7 dBmV 38.7 dB 0 0 16 Locked QAM256 24 675000000 Hz 2.9 dBmV 37.1 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 35700000 Hz 39 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 39 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 22700000 Hz 38.4 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 16200000 Hz 36.7 dBmV Here's the levels. Some of the logs events I see on a regular basis:
Warning (5) Dynamic Range Window violation
Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out Critical (3) Unicast Ranging Received Abort Response - Re-initializing Notice (6) Honoring MDD; IP provisioning mode = IPv6
Also, over the course of 10 minutes earlier today, there are 41 event log entries. It pretty much goes Dynamic Range Window Violation, Unicast Ranging Received Abort Response, Dynamig Range Window violation, Received Response to Broadcase Maintenace Request..., and then just loops those over and over and over.
- fossianAspirant
I'm seeing the same problems with my C7000 on Comcast. Firmware is version 1.01.23.
The internet routinely cuts out as the OP described.
Here are the usual entries I see in my event logs:
- Critical (3): SYNC Timing Synchronization failure - Failed to acquire FEC framing;
- Critical (3): Started Unicast Maintenance Ranging - No Response received - T3 time-out;
- Critical (3): No Ranging Response received - T3 time-out;
- Warning (5): Dynamic Range Window violation
- Critical (3): Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;