Observer

Cable modem randomly reboots when I setup IPv6 on my router

I was trying to set up IPv6 on my Asus AC88U router.  

 

I currently have my Time Warner Cable Modem (TG1672) set to bridge mode so that my router controls everything (plus it allows my Xbox One to have an Open NAT).

 

After setting up IPv6 on the router, it was working ok and even passed all the IPv6 tests except for one test, which was asking for a Host name, which I don't know where I would enter that (or even what the host name is supposed to be).

 

But the cable modem is randomly rebooting on its own, sometimes a few hours later even.  I first notice before it happens,  the internet has a long pause when browsing, then I can see all the lights go out on the cable modem and it slowly reboots.  

 

Does anyone have any idea why this is happening?  I had to disable IPv6 because I can't use it when it does that.

14 REPLIES
Expert

Re: Cable modem randomly reboots when I setup IPv6 on my router

Copy and paste the modems signal level and error log pages....

 

DO YOU HAVE THE NTS TURNED ON AND SET TO THE CORRECT TIME ZONE IN YOUR ROUTER?

 

Observer

Re: Cable modem randomly reboots when I setup IPv6 on my router

Not sure if this is what you are asking for or not.  I originally set up IPv6 during early morning on 8/6/2017.  I am currently back to using IPv4 for now, I changed back around 10:30am or so.

 

Downstream
 DCIDFreqPowerSNRModulationOctetsCorrectedsUncorrectables
Downstream 132645.00 MHz-16.30 dBmV33.83 dB256QAM19762894110
Downstream 218561.00 MHz-15.60 dBmV33.38 dB256QAM6311931547395579
Downstream 319567.00 MHz-15.70 dBmV33.38 dB256QAM611907540060
Downstream 420573.00 MHz-16.00 dBmV33.06 dB256QAM614449152140
Downstream 521579.00 MHz-15.80 dBmV33.06 dB256QAM633028627950
Downstream 622585.00 MHz-15.50 dBmV33.16 dB256QAM613023039220
Downstream 723591.00 MHz-14.70 dBmV33.83 dB256QAM612896411200
Downstream 824597.00 MHz-13.90 dBmV34.48 dB256QAM612116100
Downstream 925603.00 MHz-13.70 dBmV34.93 dB256QAM613825600
Downstream 1026609.00 MHz-15.00 dBmV33.83 dB256QAM622877200
Downstream 1127615.00 MHz-15.00 dBmV33.83 dB256QAM642242900
Downstream 1228621.00 MHz-14.60 dBmV34.35 dB256QAM618576800
Downstream 1329627.00 MHz-14.90 dBmV34.35 dB256QAM614567070
Downstream 1430633.00 MHz-14.70 dBmV34.48 dB256QAM634893600
Downstream 1531639.00 MHz-15.50 dBmV34.35 dB256QAM601972400
Downstream 1617555.00 MHz-15.70 dBmV33.38 dB256QAM6343382461573
Reset FEC Counters
Upstream
 UCIDFreqPowerChannel TypeSymbol RateModulation
Upstream 1730.60 MHz45.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM
Upstream 2837.00 MHz45.25 dBmVDOCSIS2.0 (ATDMA)2560 kSym/s16QAM
Upstream 3519.40 MHz45.25 dBmVDOCSIS1.x (TDMA)2560 kSym/s16QAM
Upstream 4624.20 MHz45.25 dBmVDOCSIS2.0 (ATDMA)5120 kSym/s64QAM

 Status
System Uptime:0 d: 1 h: 34 m
Computers Detected:staticCPE(2), dynamicCPE(2)
CM Status:Telephony-Reg Complete
Time and Date:Sun 2017-08-06 11:42:16

 Interface Parameters
Interface NameProvisionedStateSpeed (Mbps)MAC address
LAN Port 1EnabledDown-----D4:05:98:3F:42:E1
LAN Port 2EnabledDown-----D4:05:98:3F:42:E1
LAN Port 3EnabledDown-----D4:05:98:3F:42:E1
LAN Port 4EnabledUp1000(Full)D4:05:98:3F:42:E1
CABLEEnabledUp-----D4:05:98:3F:42:E2
MTAPassUp-----D4:05:98:3F:42:E3

 

 

DOCSIS(CM) Events

 

Date TimeEvent IDEvent LevelDescription
7/26/2017 18:32820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/27/2017 1:44840202005Lost MDD Timeout;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/27/2017 10:04820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/27/2017 11:57840202005Lost MDD Timeout;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/27/2017 13:16820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/27/2017 14:13840202005Lost MDD Timeout;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/27/2017 14:20820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/30/2017 1:27830102004Service Change Response rejected - Invalid transaction ID;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/30/2017 20:15820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/31/2017 12:03840202005Lost MDD Timeout;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
7/31/2017 20:23820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/1/2017 0:02680106006DHCP Renew - lease parameters tftp file-?BiABGZgIwAEAAAAAAAAAAGTUBZg_QuImBqAADAAAQgyubv598F9+@AAAAAIqDJIJJVKewimwDa5C_edM9PH+u modified;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/1/2017 4:12820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 1:52850102005TCS Partial Service;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 4:01820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 7:52840007005RCS Partial Service;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 7:52850102005TCS Partial Service;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 9:17840007005RCS Partial Service;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 9:17850102005TCS Partial Service;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;
8/6/2017 10:55820002003No Ranging Response received - T3 time-out;CM-MAC=d4:05:98:3f:42:e2;CMTS-MAC=00:17:10:8b:33:9d;CM-QOS=1.1;CM-VER=3.0;

 

 PacketCable(MTA) Events

 

Date TimeEvent IDDescription
5/17/2017 11:2926MTA PROV: Successful!
5/17/2017 11:293Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
6/2/2017 0:0216MTA TFTP: Successful
6/2/2017 0:0226MTA PROV: Successful!
6/2/2017 0:023Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
6/2/2017 0:0214Power Supply Telemetry Log - BATTERY MISSING
6/13/2017 11:4065508SIP Message Unexpected - line 1 BYE request is rejected
6/14/2017 8:1665508SIP Message Unexpected - line 1 BYE request is rejected- Cleared
8/6/2017 0:0816MTA TFTP: Successful
8/6/2017 0:0826MTA PROV: Successful!
8/6/2017 0:083Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/6/2017 0:0814Power Supply Telemetry Log - BATTERY MISSING
8/6/2017 0:1116MTA TFTP: Successful
8/6/2017 0:1126MTA PROV: Successful!
8/6/2017 0:113Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/6/2017 0:1114Power Supply Telemetry Log - BATTERY MISSING
8/6/2017 1:5314Power Supply Telemetry Log - BATTERY MISSING
8/6/2017 1:5316MTA TFTP: Successful
8/6/2017 1:5326MTA PROV: Successful!
8/6/2017 1:533Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/6/2017 7:5316MTA TFTP: Successful
8/6/2017 7:5326MTA PROV: Successful!
8/6/2017 7:533Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/6/2017 7:5314Power Supply Telemetry Log - BATTERY MISSING
8/6/2017 9:1814Power Supply Telemetry Log - BATTERY MISSING
8/6/2017 9:1816MTA TFTP: Successful
8/6/2017 9:1826MTA PROV: Successful!
8/6/2017 9:183Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/6/2017 10:1016MTA TFTP: Successful
8/6/2017 10:1026MTA PROV: Successful!
8/6/2017 10:103Voice Line State Change, Line Number = 1, Prev State = OOS, New State = IS
8/6/2017 10:1014Power Supply Telemetry Log - BATTERY MISSING
Expert

Re: Cable modem randomly reboots when I setup IPv6 on my router

YOU HAVE A MAJOR SIGNAL LEVEL PROBLEM...

 -16 DbMV WILL NOT WORK, MODEM IS NOT ON THE FIRST 2 WAY SPLITTER!

If you are internet only, there should be no splitters in line.

if cable tv, modem is on the first 2 way and the cable boxes split off the second port. There  is also broadcast tv ingress due to corroded or loose connectors or unterminated splitter ports. bet you have a local ch 28-29, what's your zipcode?

 

 This could also be chewed up outside line that's full of water...

it is not a modem, router or IPv6 issue and can't be fixed over the phone!

 

Observer

Re: Cable modem randomly reboots when I setup IPv6 on my router

Our cable line is in our attic,  the cable company has a splitter that splits the wire to the cable modem location and a separate wire that goes to its own powered splitter for the cable tv's.

 

We have another family living here, so we have like 7 cable boxes.  We used to get garbled tv often, but the last cable guy put a new splitter on because he said the previous one was wrong, and that fixed our TV garbled picture problem.

 

I haven't noticed any internet problem either, as we get over 200Mbps download speed.

 

I don't know though, you very well may be right.  The cable tv guys don't really seem to know a whole lot when they do come here.  The previous excuse they gave us for the garbled tv was that it was due to the weather.

 

Observer

Re: Cable modem randomly reboots when I setup IPv6 on my router

We live in the 28120 zipcode.

Expert

Re: Cable modem randomly reboots when I setup IPv6 on my router


tcoolong wrote:

We live in the 28120 zipcode.


you have a really strong ch 27,28,30 there.

So there is confirmed ingress.

 something is corroded, loose or chewed up allowing it.

 

Expert

Re: Cable modem randomly reboots when I setup IPv6 on my router

Reexamine the connection from the outside grounding block to the supposed only single 2 way splitter in the attic and then between that splitter and the modem... something is wrong between the pole and the modem. This looks like more than an  8 way split or  3- 2ways in series

 

Expert

Re: Cable modem randomly reboots when I setup IPv6 on my router

uhhh, there's only one possibility of a wrong splitter... more than likely a bad splitter.  Can you post the model number of what's there now as well as the amplifier model number?

"last cable guy put a new splitter on because he said the previous one was wrong,"

Observer

Re: Cable modem randomly reboots when I setup IPv6 on my router

The line in first goes to a two way splitter:  

"Commscope Digital Splitter" SV-2G 5-1002MHZ

 

Then one line from that splitter goes to the cable modem.

 

The other line from that splitter goes out to the 8 way powered splitter:  

- Antronix Forward/Return Residential Amplifier FRA8-0400  

500mA    FWD: 54-1002MHz +4dB,    RTN:5-42MHz +0dB

 

 

I did try the IPv6 last night, but only for a couple hours and it didn't reboot then.  I did make a change in my router for  a setting, I don't know if that helped or not.  I didn't want to leave it on all day because my nephew plays his xbox most of the day and I didn't want to upset him if it goes down.  I have to test it some more.