> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:cisco-nsp- > [EMAIL PROTECTED] On Behalf Of Mikael Abrahamsson > Sent: Friday, July 04, 2008 1:42 AM > To: [email protected] > Subject: Re: [c-nsp] IPv6 Migration with ISIS (was Route Reflector > Design) > > On Thu, 3 Jul 2008, Vinny Abello wrote: > > > While on this topic, if anyone has figured out a non-disruptive > strategy > > to deploying IPv6 in a core with a mix of Cisco and Foundry routers > > running ISIS, any pointers would be appreciated. Foundry currently > > We had multitopology problems between platforms/vendors as well, we > ended > up "solving" the issue by using OSPFv3 as IPv6 IGP (and ISIS for > IPv4/VPNv4), this gave us a completely different control plane for IPv6 > and pretty much guaranteed to be non-intrusive to devices not running > IPv6 > or needing the information. > > Multitopology ISIS is a great idea and I would really like to run it, > but > it just didn't work with our mix of platforms and vendors.
Thanks Mikael. I hadn't considered running OSPFv3 for IPv6. I'll have to see if that is a viable possibility in our network. Did you run into any challenges in doing this such as administrative distances of the routing protocols and things defaulting to using IPv6 instead of IPv4 or other unexpected results? In theory if you're only doing the IPv6 address family, I wouldn't expect any problems, but firsthand experience is always better than theory. :) By the way, what other vendor's or vendors' equipment were you working with besides Cisco where you had the same ISIS multi-topology challenges? -Vinny _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
