From: ccie2be (ccie2be@nyc.rr.com)
Date: Sat Jul 24 2004 - 11:07:29 GMT-3
I'll lab this up later, but my initial thought is that for this work, you
would need the nei x.x.x.x update-source command.
For example,
R1 (using default route)
router bgp 100
nei <default route> remote-as 200
nei <default route> update source <int used with default route>
R2
router bgp 200
nei x.x.x.x remote-as 100 where x.x.x.x is addr of int using default
route.
As I say, I don't if this will work. I'll try to lab it later if I get a
chance.
HTH, Tim
----- Original Message -----
From: "Axel Foley" <kareem@synergyct.com>
To: "thunai" <thunai@cisco.com>; <ccielab@groupstudy.com>
Cc: <security@groupstudy.com>
Sent: Saturday, July 24, 2004 9:14 AM
Subject: Re: BGP Neighbor Specific Route
> Just let the other peer initiate the BGP session.
>
> > Dear Group ,
> >
> > Is there any way i can overcome the specfic route reqired for
> > BGP peering . Meaning when i am forming neighbor relationship with a
> > peer , unless i have a specfic route for that peer in my route-table the
> > peer relation ship is not comming ( i have default route ) . Its not
> > taking the default route for forming peer relationship.
> >
> >
> > Thanks in advance
> > Regds
> > Thunai
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:12:02 GMT-3