From: Rudy Phen@xxxxxxxx@DASG-KBT (Phen@xxxxxxxx@DASG-KBT)
Date: Fri Jun 25 1999 - 13:46:25 GMT-3
Local preference attribute is used between 2 IBGP router and not between BGP
router in different AS.
You can try set the local preference for particular route that pointed to
your IBGP peer router.
For Example..
router bgp 1
nei 172.16.1.1 remote-as 1 (your IBGP peer router)
nei 172.16.1.1 route-map 201-local out
route-map 201-local out
match ip add 10
set local-preference 300
If you want to influence routing decision inside the AS, you can try mine !
Best Regards,
Rudy Phen
STARtrac - Datacraft Asia Ltd
Phone : (65) 8436101
WWW.Datacraft-Asia.Com <http://www.Datacraft-Asia.Com>
Connecting People to Information
> -----Original Message-----
> From: Brian Van Benschoten [mailto:vader@inxpress.net]
> Sent: Thursday, June 24, 1999 7:33 PM
> To: Botten Russell; ccielab@groupstudy.com
> Subject: Re: BGP policy routing
>
>
> I believe that modifying outgoing updates is changing the
> MED. Which should
> "suggest" to your upstream AS which route to take back INTO your AS.
>
> I have the opposite. I want to influence MY AS to send a
> particular route
> out of a particular router. It may not be the closest exit
> point of my AS,
> but I want to force this behavior.
>
>
> ----- Original Message -----
> From: Botten Russell <russell.botten@siemens.com.au>
> To: 'Brian Van Benschoten' <vader@inxpress.net>; Botten Russell
> <russell.botten@siemens.com.au>; <ccielab@groupstudy.com>
> Sent: Wednesday, June 23, 1999 11:11 PM
> Subject: RE: BGP policy routing
>
>
> > As I understand it, you could put a route map on the
> outgoing updates and
> > modify the local preference there.
> >
> > This will still inform IBGP neighbours that this router is
> the preferred
> > exit for that route.
> >
> > It's only an idea ?
> >
> > Russell.
> >
> >
> > -----Original Message-----
> > From: Brian Van Benschoten [mailto:vader@inxpress.net]
> > Sent: Thursday, 24 June 1999 13:47
> > To: Botten Russell; ccielab@groupstudy.com
> > Subject: Re: BGP policy routing
> >
> >
> > I've been reading that book quite a bit....
> >
> > how do i accomplish the task i set out. to tag a single
> route (not all
> > routes from a AS or neighbor) with a higher preference.
> >
> > Thanks
> > ----- Original Message -----
> > From: Botten Russell <russell.botten@siemens.com.au>
> > To: 'Brian Van Benschoten' <vader@inxpress.net>;
> <ccielab@groupstudy.com>
> > Sent: Wednesday, June 23, 1999 10:35 PM
> > Subject: RE: BGP policy routing
> >
> >
> > > G'day Brian,
> > >
> > > Route maps associated with neighbour statements have no effect on
> incoming
> > > updates when matching based on IP addresses. See the BGP
> tutorial by
> > Bassam
> > > Halabi.
> > >
> > > Cheers,
> > > Russell.
> > >
> > > -----Original Message-----
> > > From: Brian Van Benschoten [mailto:vader@inxpress.net]
> > > Sent: Thursday, 24 June 1999 13:25
> > > To: ccielab@groupstudy.com
> > > Subject: BGP policy routing
> > >
> > >
> > > I'm getting the following error when applying a route
> map. I have a
> dual
> > > homed AS and want to set local preference for a single
> route coming in
> one
> > > of the ISP pipes.
> > >
> > > 2513(config-router)#neighbor 150.100.1.0 route-map 201-local in
> > > % "201-local" used as BGP inbound route-map, network
> match not supported
> > >
> > >
> > > router bgp 5
> > > no synchronization
> > > network 170.100.51.0 mask 255.255.255.0
> > > redistribute igrp 100
> > > neighbor 150.100.1.0 remote-as 254
> > > neighbor 150.100.1.0 route-map 201-local in <== here it
> is applied
> > > neighbor 170.100.2.3 remote-as 5
> > > neighbor 170.100.2.3 next-hop-self
> > > neighbor 170.100.200.2 remote-as 666
> > > no auto-summary
> > >
> > >
> > >
> > > route-map 201-local permit 10
> > > match ip address 10
> > > set local-preference 300
> > > !
> > > route-map 201-local permit 20
> > > match ip address 11
> > >
> > > access-list 10 permit 201.201.201.0 0.0.0.255 <== the
> route in question
> i
> > > want to apply local preference
> > > access-list 11 permit any
> > >
> > >
> > > CAUTION - This message may contain privileged and confidential
> information
> > > intended only for the use of the addressee named above.
> If you are not
> > the
> > > intended recipient of this message you are hereby
> notified that any use,
> > > distribution or reproduction of this message is
> prohibited. If you have
> > > received this message in error please notify Siemens
> Ltd., ACN 004 347
> > 880,
> > > or Siemens (NZ) Limited immediately.
> > >
> >
> >
> > CAUTION - This message may contain privileged and
> confidential information
> > intended only for the use of the addressee named above. If
> you are not
> the
> > intended recipient of this message you are hereby notified
> that any use,
> > distribution or reproduction of this message is prohibited.
> If you have
> > received this message in error please notify Siemens Ltd.,
> ACN 004 347
> 880,
> > or Siemens (NZ) Limited immediately.
> >
> >
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:39 GMT-3