From: W. Alan Robertson (warobertson@earthlink.net)
Date: Fri Oct 10 2003 - 10:30:38 GMT-3
It depends on your topology:
You can use a community to keep the route from being sent to AS 200, and
AS65000... Use the "local-as" community string.
If R3 is directly peered with R1, then unfortunately, that won't stop the
route from getting to R1. For that, your best bet would simply be to filter
it out...
If, on the other hand, R3 is peered with R2 only (And R2 is a route
reflector for R1 and R3), you can instead utilize the "no-advertize"
community in your R3-R2 setup, and that will keep R2 from sending the route
along to R1.
Can't give you a definitive answer without knowing all of the iBGP peering
specifics.
----- Original Message -----
From: "John Smith" <c00per_omers1@yahoo.com>
To: <ccielab@groupstudy.com>
Sent: Friday, October 10, 2003 1:15 AM
Subject: BGP - how to partially advertise in your own AS but not to others.
> R1 R2 and R3 are all in AS55,
> R1 connects to AS 65000, R3 connects to AS 65000
> R2 connects to AS 200
> You want to advertise lo1 5.5.5.5 on R3 to R2, but not R1( in your own
AS ), You don't want to advertise to AS 65000 or 200.
>
> Can this be done with communties?
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Mon Nov 24 2003 - 07:53:00 GMT-3