<html><head></head><body bgcolor="#FFFFFF"><div>Make sure ipv6 redirects are off on each interface. Cisco hides that default and can cause this trouble. </div><div><br></div><div>Saw a significant issue in the past related to this. <br><br>Jared Mauch</div><div><br>On Jun 1, 2012, at 6:41 AM, "Eric Vyncke (evyncke)" <<a href="mailto:evyncke@cisco.com">evyncke@cisco.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Comic Sans MS";
panose-1:3 15 7 2 3 3 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Comic Sans MS";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--><div class="WordSection1"><p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Comic Sans MS";color:#1F497D">By any chance, can you check whether the ‘broken’ router receives a lot of IPv6 traffic already? Or if there are some ‘multicast’ storm between this ‘broken’ router and another device?<o:p></o:p></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Comic Sans MS";color:#1F497D"><o:p> </o:p></span></p><div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt"><div><div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"><p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:ipv6-ops-bounces+evyncke=cisco.com@lists.cluenet.de">ipv6-ops-bounces+evyncke=cisco.com@lists.cluenet.de</a> [mailto:ipv6-ops-bounces+evyncke=<a href="mailto:cisco.com@lists.cluenet.de">cisco.com@lists.cluenet.de</a>] <b>On Behalf Of </b>Jim Trotz<br><b>Sent:</b> vendredi 1 juin 2012 02:47<br><b>To:</b> <a href="mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de</a><br><b>Subject:</b> enabling IPv6 on Cisco 6500 breaks IPv4 Internet connectivity.<o:p></o:p></span></p></div></div><p class="MsoNormal"><o:p> </o:p></p><p class="MsoNormal">We have a pair of Cat6500s with sup720XL supervisors running 12.2(33)SXJ1 IOS that are configured as enterprise Edge routers. These routers have a VRF for Internet "outside" connections and the global table is used for "Inside" connections. The outside VRF has full BGP routing tables with 406K V4 routes. <br><br>Cisco ASAs are connected on ports associated each routing table. Named mode EIGRP is used for IGP both inside and in the external VRF to communicate with our 2 Internet Hub routers (also 6500s, dual stacked, working fine).<br><br>The problem we have is that when we try to configure IPV6 on the edge routers we loose the ability to pass IPv4 traffic as soon as the "ipv6 unicast routing" command is entered - no IPV6 addresses have been applied at that point, no interfaces enabled for IPv6 and no ipv6 routing configured either.<br><br>Cisco TAC seems to be stumped. The logs don't show anything, Eigrp & BGP neighbors stay up and the CPU rises to 99% utilization.<br><br>The odd thing is that when we apply the "ipv6 unicast routing" command to the other router it works fine. The only thing we could think of thats different between the two is the "broken" router's ASA firewall is in active state and the "good" router's ASA is in standby. We plan to fail them over to see if thats really the difference.<br><br>I have tried duplicating the problem in the lab without luck so far.<br><br>Has anyone had a similar problem or have any suggestions? <o:p></o:p></p></div></div></div></blockquote></body></html>