[RE: [RE: [nsp] Retaining EIGRP metrics when using BGP]]

Jim Brunetti jim.brunetti at usa.net
Tue Jan 6 16:27:15 EST 2004


Cool feature.  What if my Service Provider doesn't support it yet (or doesn't
use Cisco's as their PE's?  Any other options?

Siva Valliappan <svalliap at cisco.com> wrote:

> we do now support EIGRP for MPLS VPNs.
> 
>
http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080154db3.html
> 
> cheers
> .siva
> 
> On Tue, 6 Jan 2004, Temkin, David wrote:
> 
> > Ok, you made it sound like this was for a single site or something, not
> > for a large deployment.
> >
> > -----Original Message-----
> > From: Jim Brunetti [mailto:jim.brunetti at usa.net]
> > Sent: Tuesday, January 06, 2004 1:37 PM
> > To: Temkin, David; Jim Brunetti; cisco-nsp at puck.nether.net
> > Subject: Re: [RE: [nsp] Retaining EIGRP metrics when using BGP]
> >
> >
> > Can't do that.  This is an MPLS VPN with many sites running parallel to
> > a bunch of point-to-points.  Running a full mesh of GRE tunnels negates
> > the benefits of the VPN.
> >
> > "Temkin, David" <temkin at sig.com> wrote:
> >
> > > Silly suggestion - run a GRE tunnel between the two to directly
> > > exchange EIGRP information?
> > >
> > >
> > >
> > > -----Original Message-----
> > > From: cisco-nsp-bounces at puck.nether.net
> > > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jim Brunetti
> > > Sent: Tuesday, January 06, 2004 12:44 PM
> > > To: cisco-nsp at puck.nether.net
> > > Subject: [nsp] Retaining EIGRP metrics when using BGP
> > >
> > >
> > > Is it possible to transport EIGRP metrics across a BGP backbone?
> > >
> > > D       128.103.1.0 [90/307200] via 128.104.1.1, 00:07:23, Ethernet0/0
> > >
> > > D       128.102.1.0 [90/412300] via 128.104.1.1, 00:07:23, Ethernet0/0
> > >
> > > These two routes are in Router 1.  Router 1 and Router 2 connect to
> > > each other using eBGP with many transit AS's in between.  Router 2
> > > redistributes BGP back into EIGRP.  Is there any way for router 2 to
> > > see the metric 307200 for network 128.103.1.0 when it is redistributed
> >
> > > from BGP into EIGRP and 412300 for network 128.102.1.0 when it is
> > > redistributed from BGP into EIGRP (basically making the entire BGP
> > > cloud look like a private line)?
> > >
> > >
> > >
> > >
> > >
> > > jim.brunetti at usa.net
> > >
> > >
> > >
> > > _______________________________________________
> > > 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/
> > >
> > > IMPORTANT: The information contained in this email and/or its
> > > attachments is
> > confidential. If you are not the intended recipient, please notify the
> > sender immediately by reply and immediately delete this message and all
> > its attachments.  Any review, use, reproduction, disclosure or
> > dissemination of this message or any attachment by an unintended
> > recipient is strictly prohibited.  Neither this message nor any
> > attachment is intended as or should be construed as an offer,
> > solicitation or recommendation to buy or sell any security or other
> > financial instrument.  Neither the sender, his or her employer nor any
> > of their respective affiliates makes any warranties as to the
> > completeness or accuracy of any of the information contained herein or
> > that this message or any of its attachments is free of viruses.
> > >
> > >
> >
> >
> >
> >
> >
> >
> > jim.brunetti at usa.net
> >
> >
> >
> > _______________________________________________
> > 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/
> >
> 






jim.brunetti at usa.net





More information about the cisco-nsp mailing list