Participant

Re: No IPv6 for Me

Woudl an inline attenuator do the same thing?

Expert

Re: No IPv6 for Me

the 75 ohm  term resistors come in packs of 2 and 10...

You need a jumper because the splitters have female connectors on all ports.

 

 or you can call twc and have them send out a tech to look at this... especially since there's also a seperate IPv6 issue....

 

Highlighted
Participant

Re: No IPv6 for Me

I just got in touch with Tier-3.  They said my signal is of such poor quality, they can only intermitantly reach my modem, and they cannot enumerate it completely because its "ping state" is unknown.

 

They said my signal levels are WAY off.

 

Tomorrow, a tech is comming out to fix that.  I also ordered a new Linksys EA6400 Router as a good measure...

 

I will follow-up

Expert

Re: No IPv6 for Me

Ok, good. Sometimes they just toss up their hands... . I don't consider +10 way off, it's a little high, +15 would be way off

 

Yes a 3 or 5 db attenuator would work but you can't get them locally

 

 Don't go throwing modems at a line issue

Woman Sad

 

Participant

Re: No IPv6 for Me

 

A Tech came and adjusted my signal...  It didn't help in that I still have no IPv6, but he said my signal is absolutely perfect now.

 

DownstreamBonding Channel Value

Channel ID
Frequency573000000 Hz 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 603000000 Hz 609000000 Hz 615000000 Hz 
Signal to Noise Ratio37 dB 37 dB 38 dB 38 dB 39 dB 39 dB 39 dB 39 dB 
Downstream ModulationQAM256 QAM256 QAM256 QAM256 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  5 dBmV  6 dBmV  6 dBmV  6 dBmV  6 dB

 

 

 

UpstreamBonding Channel Value

Channel ID
Frequency24200000 Hz 19400000 Hz 30600000 Hz 37000000 Hz 
Ranging Service ID2105 2105 2105 2105 
Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec 
Power Level43 dBmV 43 dBmV 43 dBmV 45 dBmV 
Upstream Modulation[3] QPSK
[3] 16QAM
 
[3] QPSK
[2] 16QAM
 
[3] QPSK
[3] 16QAM
 
[3] QPSK
[3] 16QAM
 
Ranging StatusSuccess Success Success Success 
Established Sharer

Re: No IPv6 for Me

The signal levels are better, yes, but not "perfect".  Post your event log as well, let's see if it "looks better", too.

Participant

Re: No IPv6 for Me

Woud another three db help?  If yes, I can just buy one.

 

Here is what hte current logs show...  Keep in mind the tech came 4/19 around 5 PM EDT

 

TimePriorityCodeMessage

Apr 20 2016 19:43:046-NoticeI502.0Received REG-RSP while in REG-HOLD1 state;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 20 2016 19:42:006-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 20 2016 19:42:005-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 20 2016 19:41:326-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 20 2016 19:41:325-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot from GUI/Configuration page ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Apr 20 2016 13:37:473-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:50:386-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:50:385-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:50:096-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:50:095-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:49:223-CriticalR04.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:49:185-WarningT202.0Lost MDD Timeout;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 15:48:533-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 19 2016 06:46:533-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 18 2016 13:43:433-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 17 2016 22:44:056-NoticeI502.0Received REG-RSP while in REG-HOLD1 state;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 17 2016 22:43:026-NoticeI401.0TLV-11 - unrecognized OID;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Apr 17 2016 22:43:015-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:88:1a:76;CMTS-MAC=00:17:10:8e:68:d0;CM-QOS=1.1;CM-VER=3.0;
Established Sharer

Re: No IPv6 for Me

Yes, that's better, you've had no T3 or T4 timeouts since the tech left.  Try not to reboot the cable modem, then paste in another signal page/event log combination tomorrow.  If everything still looks good, and your service is working properly, we'd call it good.

Participant

Re: No IPv6 for Me

Well,l still have no IPv6 support for some reason.  Any ideas?

Seasoned Contributor

Re: No IPv6 for Me


@NETWizz wrote:

Well,l still have no IPv6 support for some reason.  Any ideas?


Sniff the interface for inbound IPv6.  There should be some ICMP6 traffic.  Check your DHCP6 (error) logs.  Restart DHCP6 while monitoring the external interface.

 

For now  troubleshooting  native IPv6 means being able to do the above. And you should have  another IPv6 capable CM, preferably a different brand, for testing.