[c-nsp] Fw: Re: IOS-XR BCP for EIGRP default route

Randy randy_94108 at yahoo.com
Mon Jun 3 10:25:33 EDT 2013


replying to my own post- i meant ip default-network...sorry

--- On Sun, 6/2/13, Randy <randy_94108 at yahoo.com> wrote:

> From: Randy <randy_94108 at yahoo.com>
> Subject: Re: [c-nsp] IOS-XR BCP for EIGRP default route
> To: "cisco-nsp at puck.nether.net NSP" <cisco-nsp at puck.nether.net>, "Jason Lixfeld" <jason at lixfeld.ca>
> Date: Sunday, June 2, 2013, 8:43 PM
> IIRC default-info originate for eigrp
> was introduced in nx-os. ios and ios-xr don't have it.
> ios for eigrp had this idiotic concept carried-over from
> IGRP of default-gateway.
> 
> <end rant>
> ./Randy
> 
> --- On Sun, 6/2/13, Jason Lixfeld <jason at lixfeld.ca>
> wrote:
> 
> > From: Jason Lixfeld <jason at lixfeld.ca>
> > Subject: [c-nsp] IOS-XR BCP for EIGRP default route
> > To: "cisco-nsp at puck.nether.net
> NSP" <cisco-nsp at puck.nether.net>
> > Date: Sunday, June 2, 2013, 12:26 PM
> > Hi,
> > 
> > In reading the documentation for EIGRP default route
> > advertisement into EIGRP, I'm finding only a few ways
> to
> > accomplish this, based on my current topology.
> > 
> > In vrf foo, I have a default route redistributed from
> static
> > on an upstream PE router.  I want to get that default
> > route sent towards a CE router downstream of my
> EIGRP-PE.
> > 
> > Near as I can tell, I can do one of the following to
> > accomplish that:
> > 
> > 1. Redistribute BGP into EIGRP on EIGRP-PE
> > 2. Create a summary address on the CE facing interface
> on
> > EIGRP-PE
> > 3. Create a static default on EIGRP-PE and
> redistribute
> > static into EIGRP.
> > 
> > Option 1 seems a little heavy handed relative to the
> very
> > simple method of default-information originate in a
> protocol
> > like ISIS.
> > Option 2 seems a little administratively prohibitive in
> the
> > sense of having to add summary-address 100 0.0.0.0
> 0.0.0.0
> > 250 on each and every CE interface.
> > Option 3 would require lots of peripheral configuration
> to
> > ensure that default didn't somehow make it's way back
> > upstream.
> > 
> > Is there something a little more elegant or am I faced
> with
> > one of these three options?  In a perfect world,
> > isis-like default-information originate would be
> loverly,
> > but I'm not sure if that's possible in EIGRP land.
> > 
> > Thanks in advance.
> > _______________________________________________
> > 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/
> > 
> 
> _______________________________________________
> 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/
>



More information about the cisco-nsp mailing list