NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
C6300 and Cable signal drops
Hello. Trying to resolve recurring issues with Medicom and my C6300, firmware version v1.02.21. My cable connection and internet access randomly drops. Here are the symptoms.
1) Modem connection light always stays solid green.
2) Login into modem (sometimes it takes a power cycle to get the web interface to display anything)
3) Modem says RF connecdtion is dropped. But after the power cycle the modem is reconnected.
4) My Event log is full of the following (latest event only shown)
| Nov 30 01:14:01 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:09 2015 | Critical (3) | Unicast Ranging Received Abort Response - initializing MAC |
| Nov 30 01:14:09 2015 | Critical (3) | No Ranging Response received - T3 time-out |
5) The logs show a DoS attack (sometimes simultaneously with above, sometimes not)
| [DoS attack] AIF:Dropped INPUT packet: PROTO:ICMPv6 SPT: DPT: | 1 | Monday, 30 Nov 2015 10:47:47 | ff02:0000:0000:0000:0000:0000:0000:0001 | fe80:0000:0000:0000:1edf:0fff:fe02:63d9 |
6) Using both 2.4GHz and 5GHz. All signals are blocked including wired ethernet from all devices in house.
7) 2.4GHz is on Auto, which selected Channel 6, which has no strong interfering signals. 5GHz wanders a bit, also on Auto, no interfering signals shown in Wireless survey map.
8) According to Mediacom, my signal at the Cable modem is +3dB, within their specs (and close to the upper limit).
9) According to speedtest.net, using an Ethernet connection to the modem/router with all other devices shutdown except the computer running the test, I see speeds varying as low as 15Mbps down and 1Mbps up to the rated 150Mbps down and 25Mbps up.
10) Checking cable status I'm looking at 8 channels bonded down and 2 up. Although 'correctable' packets seems to become high on some of the channels, at least before C6300 power cycle.
11) I tried a Motorola Arris and found mediacom had a problem with signal strenght bouncing—which Mediacom has apparenlty fixed as the Motorola modems lights consistenly showed high speed bonded channels. (I returned the Motorola modem as return period from Best Buy had passed for the C6300).
So where's the issue? Is there a problem with PLL tracking in this modem and it's defective? Is the problem with the infrastructure from Mediacom?
8 Replies
Hi,
Can you please post the power values? and full event log?
How do I obtain the event logs from a NETGEAR cable modem/modem router?
Link: http://kb.netgear.com/app/answers/detail/a_id/30008
How do I obtain the cable connection information from a NETGEAR cable modem/modem router?
Link: http://kb.netgear.com/app/answers/detail/a_id/30007
as soon as I see this message "Unicast Ranging Received Abort Response" , I see that reset was initiated from ISP side (Mediacom). also, if you have lot of uncorretables, that is another sign of RF issue from ISP.
We had a another community user from the same ISP with similar issue. he resolved the issue by removing unnecessary splitter(s) in his home.
DoS attack info is ok as it is an internal packet. You can ignore it.
Time stamp is apparently central time (1 hour ahead of local) despite being physcially located in AZ.
Power readings:
Apply 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 111000000 Hz Locked Connectivity State Ok Operational Boot State -- -- Configuration File -- -- Security Disabled Disabled Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables 1 Locked QAM 256 97 93000000 Hz 4.5 dBmV 40.3 dB 696507 764 2 Locked QAM 256 98 105000000 Hz 4.4 dBmV 38.9 dB 989711 300326 3 Locked QAM 256 99 111000000 Hz 4.1 dBmV 40.3 dB 819420 137 4 Locked QAM 256 100 117000000 Hz 3.9 dBmV 40.3 dB 855097 117 5 Locked QAM 256 101 123000000 Hz 3.5 dBmV 40.3 dB 963707 126 6 Locked QAM 256 102 135000000 Hz 3.9 dBmV 40.3 dB 18 0 7 Locked QAM 256 103 141000000 Hz 3.9 dBmV 40.3 dB 35 0 8 Locked QAM 256 104 147000000 Hz 4.0 dBmV 40.9 dB 32 0 9 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 10 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 11 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 12 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 13 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 14 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 15 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 16 Not Locked N/A N/A 0 Hz 0.0 dBmV 0.0 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 Ksym/sec 30600000 Hz 47.8 dBmV 2 Locked ATDMA 1 5120 Ksym/sec 37000000 Hz 49.3 dBmV 3 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV 4 Not Locked N/A Unknown 0 Ksym/sec 0 Hz 0.0 dBmV Current System Time: Mon Nov 30 23:04:19 2015 Event Log part 1
Time Priority Description Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out
Event Log Part 2
Nov 30 01:14:01 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:01 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:02 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:02 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:02 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:02 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:03 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:03 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:03 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:03 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:04 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:04 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:04 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:04 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:05 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:05 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:06 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:06 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:06 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:06 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:07 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:07 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:07 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:07 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:08 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:08 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:09 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:09 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:09 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:09 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:10 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:10 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:10 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:10 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:14:38 2015 Critical (3) Unicast Ranging Received Abort Response - initializing MAC Nov 30 01:14:52 2015 Critical (3) No Ranging Response received - T3 time-out Nov 30 01:15:38 2015 Warning (5) MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 Nov 30 01:15:38 2015 Notice (6) TLV-11 - unrecognized OID Nov 30 15:40:18 2015 Critical (3) No Ranging Response received - T3 time-out there are so many timeouts and ranging abort messages request coming from ISP makes me believe this is an ISP issue rather than device issue.
which device were you using before?
