From: Luis Rueda (luis.rueda@comsat.com.co)
Date: Mon Oct 10 2005 - 17:53:39 GMT-3
Bob,
I think what they are trying to achieve is that you create a peer-group
and add the send-community to the peer-group. Any other neighbor added
later to the peer group, not only will it receive the route but it would
also receive it with the community.
Hope this helps.
Luis Rueda
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Bob Jones
Sent: Monday, October 10, 2005 3:42 PM
To: ccielab@groupstudy.com
Subject: BGP No-Export community question
Hello group,
I'm working on a workbook scenario that looks like this:
BB1--R1--R3--R5--BB2
R1, R3 and R5 are in AS 50 and R3 is a route reflector. R1 is peered
to BB1 in AS 400 and R5 is peered to BB2 in AS 400. There is a network
130.1.1.0/24 being advertised on R3. The scenario asks to make sure
that 130.1.1.0/24 is not advertised outside of AS 50. Another
stipulation is that if another router is at some point added to AS 50,
it should also adhere to this policy. The first part I get, no-export
community set on R3 toward R1 and R5. No problem there. What I don't
get is the second part. How do you ensure that any new routers added to
the AS 50 in the future will also have the no-export community passed on
to them?
Thanks,
Bob
---------------------------------
Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:50 GMT-3