Vinod,
Applying local preference to a route learned from your provider effects your
outbound traffic. It determines the best route for packets leaving your AS.
To effect your incoming traffic and/or to prevent your provider from
propagating your route(s) to the internet, ask your provider if they
recognize RFC 1998 communities sent to them from you. Some providers have
route-maps which read communities that you send them and set attributes
within the provider AS such as no-export or local preference. If your
provider does not currently have a standard route-map that supports RFC 1998
communities, perhaps they would build one for you if you ask.
Thanks, Paul
-----Original Message-----
From: Vinod Anthony Joseph Cherunni [mailto:vac@dsqworld.com]
Sent: Monday, December 04, 2000 7:39 AM
To: cisco-nsp@puck.nether.net
Subject: [nsp] REG: BGP Attributes
Hi All,
A couple of questions on BGP attributes.
Assuming I have three upstream connections to two different service
providers on three different physical routers located in seperate geographic
locations in my network, which are interconnected through IBGP. Assuming
that I have a single connection to Provider A, & dual connections to Service
provider B. Now for a particular prefix, If I set a local preference of 200
for routes recieved on both links connected to Provider B, & a local
preference of 100 for all other routes recieved on all the three circuits,
How will the path selection happen for packets destined to the prefix which
has the local preference set to 200, Since two circuits have been configured
to set the local preference to 200 for a particular prefix.
If I am announcing both an aggregate & a specific route to an upstream ISP,
& If I need to restrict the ISP from further announcing the specific route
to any of his connected peers, because of reasons which would effect the
incoming traffic to my network, How do I achieved this.
Kindly advice,
With warm regards,
Vinod.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:22 EDT