ThatsLANtastic
New Around Here
I've had the RT-AC66 for about a month now after replacing what I thought was a dying router. I'm suffering from sporadic internet outages that last 5-10-15min. I'm not sure how often they happen, but I was able to run a few pings and tracert during one last night.
First, here are my variables:
-*Just moved
-New modem (Moto SB6121)
-New ISP (Time Warner)
-*New RT-AC66
-Tried stock FW (3626)
-Now on latest Merlin (376.49_2) (Cleared NVRAM after flashing)
Symptoms:
-*Internet not accessible/very slow for 10-15min
-*Can access router config page during outage (No abnormal CPU usage)
Here are pings/tracerts done during the 'wierdness':
Modem signal page during the event:
I am not at all well versed in troubleshooting these types of issues, and I was hoping someone far smarter than I could weigh in as to my next logical troubleshooting step. Am I chasing my tail trying to fix this? (Could it be TWC?)
First, here are my variables:
-*Just moved
-New modem (Moto SB6121)
-New ISP (Time Warner)
-*New RT-AC66
-Tried stock FW (3626)
-Now on latest Merlin (376.49_2) (Cleared NVRAM after flashing)
Symptoms:
-*Internet not accessible/very slow for 10-15min
-*Can access router config page during outage (No abnormal CPU usage)
Here are pings/tracerts done during the 'wierdness':
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Windows\system32>ping google.com
Pinging google.com [74.125.227.200] with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 74.125.227.200: bytes=32 time=781ms TTL=51
Reply from 74.125.227.200: bytes=32 time=27ms TTL=51
Ping statistics for 74.125.227.200:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 781ms, Average = 404ms
C:\Windows\system32>ping google.com
Pinging google.com [74.125.227.200] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 74.125.227.200:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Windows\system32>ping google.com
Ping request could not find host google.com. Please check the name and try again
.
C:\Windows\system32>ping google.com
Pinging google.com [74.125.227.229] with 32 bytes of data:
Request timed out.
Reply from 74.125.227.229: bytes=32 time=3110ms TTL=51
Reply from 74.125.227.229: bytes=32 time=92ms TTL=51
Request timed out.
Ping statistics for 74.125.227.229:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 92ms, Maximum = 3110ms, Average = 1601ms
C:\Windows\system32>tracert google.com
Tracing route to google.com [74.125.227.229]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * 1039 ms 38 ms cpe-70-121-192-1.satx.res.rr.com [70.121.192.1]
3 * * * Request timed out.
4 * 628 ms 64 ms tge0-10-0-3.snaptx1901r.texas.rr.com [24.175.33.74]
5 14 ms 13 ms 14 ms agg22.snavtxuu02r.texas.rr.com [24.175.32.160]
6 471 ms 806 ms 663 ms agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
7 1233 ms 822 ms 19 ms 107.14.17.138
8 3795 ms 1175 ms 63 ms 107.14.19.218
9 18 ms 24 ms 21 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
10 23 ms 19 ms 31 ms 207.86.210.125
11 30 ms 22 ms 19 ms 207.88.14.182.ptr.us.xo.net [207.88.14.182]
12 29 ms 24 ms 25 ms 207.88.14.189.ptr.us.xo.net [207.88.14.189]
13 21 ms 27 ms 25 ms ip65-47-204-58.z204-47-65.customer.algx.net [65.47.204.58]
14 * * 44 ms 72.14.233.77
15 22 ms 21 ms 23 ms 209.85.254.111
16 22 ms 24 ms 26 ms dfw06s38-in-f5.1e100.net [74.125.227.229]
Trace complete.
C:\Windows\system32>tracert google.com
Tracing route to google.com [74.125.227.229]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 11 ms 15 ms 11 ms cpe-70-121-192-1.satx.res.rr.com [70.121.192.1]
3 9 ms 10 ms 13 ms tge1-0-0.snantx2000-10k1.satx.rr.com [24.28.133.33]
4 16 ms 15 ms 14 ms tge0-10-0-3.snaptx1901r.texas.rr.com [24.175.33.74]
5 10 ms 14 ms 13 ms agg22.snavtxuu02r.texas.rr.com [24.175.32.160]
6 19 ms 22 ms 25 ms agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
7 19 ms 31 ms 27 ms 107.14.17.138
8 29 ms 30 ms 30 ms 107.14.19.218
9 22 ms 22 ms 33 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
10 22 ms 23 ms 20 ms 207.86.210.125
11 29 ms 25 ms 21 ms 207.88.14.182.ptr.us.xo.net [207.88.14.182]
12 21 ms 37 ms 21 ms 207.88.14.189.ptr.us.xo.net [207.88.14.189]
13 24 ms 23 ms 24 ms ip65-47-204-58.z204-47-65.customer.algx.net [65.47.204.58]
14 21 ms 19 ms * 72.14.233.77
15 20 ms 17 ms 22 ms 209.85.254.111
16 19 ms 18 ms 24 ms dfw06s38-in-f5.1e100.net [74.125.227.229]
Trace complete.
C:\Windows\system32>tracert google.com
Tracing route to google.com [74.125.227.229]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 799 ms 845 ms 610 ms cpe-70-121-192-1.satx.res.rr.com [70.121.192.1]
3 111 ms 117 ms 108 ms tge1-0-0.snantx2000-10k1.satx.rr.com [24.28.133.33]
4 139 ms 135 ms 128 ms tge0-10-0-3.snaptx1901r.texas.rr.com [24.175.33.74]
5 120 ms 127 ms 145 ms agg22.snavtxuu02r.texas.rr.com [24.175.32.160]
6 141 ms 139 ms 146 ms agg23.hstqtxl301r.texas.rr.com [24.175.32.156]
7 43 ms 30 ms 30 ms 107.14.17.138
8 1827 ms 902 ms 31 ms 107.14.19.218
9 * 1417 ms 26 ms ae2.pr1.dfw10.tbone.rr.com [107.14.17.236]
10 20 ms 22 ms 22 ms 207.86.210.125
11 18 ms 17 ms 27 ms 207.88.14.182.ptr.us.xo.net [207.88.14.182]
12 50 ms 34 ms 24 ms 207.88.14.189.ptr.us.xo.net [207.88.14.189]
13 19 ms 18 ms 22 ms ip65-47-204-58.z204-47-65.customer.algx.net [65.47.204.58]
14 20 ms 28 ms 24 ms 72.14.233.77
15 19 ms 34 ms 18 ms 209.85.254.111
16 23 ms 23 ms 17 ms dfw06s38-in-f5.1e100.net [74.125.227.229]
Trace complete.
C:\Windows\system32>tracert google.com
Tracing route to google.com [74.125.227.192]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 17 ms 21 ms 13 ms cpe-70-121-192-1.satx.res.rr.com [70.121.192.1]
3 27 ms 17 ms 10 ms cpe-70-121-192-1.satx.res.rr.com [70.121.192.1]
4 17 ms 11 ms 12 ms tge1-0-0.snantx2000-10k2.satx.rr.com [24.28.133.37]
5 15 ms 16 ms 11 ms tge0-10-0-2.snaptx1902r.texas.rr.com [24.175.33.76]
6 14 ms 16 ms 14 ms agg22.snantxvy01r.texas.rr.com [24.175.32.168]
7 28 ms 19 ms 23 ms agg23.dllatxl301r.texas.rr.com [24.175.32.146]
8 28 ms 23 ms 22 ms 107.14.19.92
9 17 ms 23 ms 20 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]
10 24 ms 15 ms 24 ms 207.86.210.125
11 23 ms 24 ms 20 ms 207.88.14.182.ptr.us.xo.net [207.88.14.182]
12 19 ms 23 ms 30 ms 207.88.14.189.ptr.us.xo.net [207.88.14.189]
13 20 ms 23 ms 21 ms ip65-47-204-58.z204-47-65.customer.algx.net [65.47.204.58]
14 19 ms 16 ms 22 ms 72.14.233.85
15 19 ms 23 ms 20 ms 64.233.174.139
16 22 ms 21 ms 21 ms dfw06s33-in-f0.1e100.net [74.125.227.192]
Trace complete.
Modem signal page during the event:
Code:
Downstream Bonding Channel Value
Channel ID 1 2 3 4
Frequency 555000000 Hz 561000000 Hz 567000000 Hz 573000000 Hz
Signal to Noise Ratio 36 dB 36 dB 36 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-3 dBmV -4 dBmV -5 dBmV -4 dBmV
Upstream Bonding Channel Value
Channel ID 7 6 5 8
Frequency 30600000 Hz 24200000 Hz 19400000 Hz 37000000 Hz
Ranging Service ID 2615 2615 2615 2615
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 2.560 Msym/sec
Power Level 45 dBmV 45 dBmV 44 dBmV 46 dBmV
Upstream Modulation [3] QPSK
[1] 16QAM
[2] 64QAM
[3] QPSK
[1] 16QAM
[2] 64QAM
[3] QPSK
[2] 16QAM
[3] QPSK
[3] 16QAM
Ranging Status Success Success Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 1 2 3 4
Total Unerrored Codewords 35211210054 35210568981 35210568018 35210568376
Total Correctable Codewords 2300 2281 2166 2179
Total Uncorrectable Codewords 710 559 1611 1561
(Log page)
Time Priority Code Message
Dec 24 2014 07:00:49 6-Notice D106.0 DHCP Renew - lease parameters tftp file-?BEWGlx2wd6wrXNgK9GJJ@CvRiSZ6BfDNybRwmLNpIkPP1Xa_A3_l7 modified;CM-MAC=b0:77:ac:2b:5c:d8;CMTS-MAC=00:17:10:87:5b:0e;CM-QOS=1.1;CM-VER=3.0;
Dec 17 2014 19:36:12 6-Notice I401.0 TLV-11 - unrecognized OID;CM-MAC=b0:77:ac:2b:5c:d8;CMTS-MAC=00:17:10:87:5b:0e;CM-QOS=1.1;CM-VER=3.0;
Dec 17 2014 19:36:12 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=b0:77:ac:2b:5c:d8;CMTS-MAC=00:17:10:87:5b:0e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:25 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b0:77:ac:2b:5c:d8;CMTS-MAC=00:17:10:87:5b:0e;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:13 6-Notice N/A Cable Modem Reboot from GUI/Configuration page ;CM-MAC=b0:77:ac:2b:5c:d8;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
I am not at all well versed in troubleshooting these types of issues, and I was hoping someone far smarter than I could weigh in as to my next logical troubleshooting step. Am I chasing my tail trying to fix this? (Could it be TWC?)