[c-nsp] changing from ospf to eigrp

[TJ]

Is EIGRP multiprotocol?
Yes, and no.  

Cisco says yes mostly because ... well, just because it can route for IP,
IPv6, IPX, AppleTalk.
Some argue that point and insist that the fact that it runs as multiple
independent processes ("protocol depended modules") means it is closer to a
ships in the night approach than the term "multiprotocol" tag implies.  Also
- EIGRP for IPv6 is not supported by Catalyst devices as of today, IIRC.



/TJ

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Adam Armstrong
> Sent: Monday, April 07, 2008 12:34 PM
> To: Gert Doering; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] changing from ospf to eigrp
> 
> 
> >> Also, if you ever want to buy a non-Cisco router for your network,
> you
> >> can't since you now run EIGRP.
> >>
> >
> > Which is a strong argument indeed.
> >
> > OTOH, EIGRP *is* a fairly nice protocol - easy to understand and
> debug,
> > much nicer knobs to tweak for TE things ("make this link bad for
> *this*
> > prefix only"), fairly fast convergence "out of the box", etc.
> >
> How's V6 on EIGRP? (I know little about EIGRP, does it need a new
> version for V6 like OSPF? Does it exist?) Not having to dual IGP for V6
> is one of the main plus points of ISIS imo.
> 
> We do ISIS for loopbacks/router links and BGP for all other prefixes.
> 
> Sadly the ISIS does lock us out of using some hardware properly (like
> the 3750).
> 
> adam.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/