From: Daniel Cisco Group Study (danielcgs@imc.net.au)
Date: Fri Jun 27 2003 - 23:24:51 GMT-3
I'm trying to nail down exactly what all the "named" communities do in BGP. All is OK, except for the "local-as" community.
The topic has come up occasionally through the archives, and the general consensus was that setting routes with the "local-as" comm att would allow the route to be propagated throughout all sub-as's of a confed.
In fact, I came across a Cisco URL which confirms this:
Quote:
local-as-Send this route to peers in other subautonomous systems within the local confederation. Do not advertise this route to an external system.
Pretty clear? Yes.
Try it...... I couldn't make this work.......What I saw was the routes being propagated only within the local sub AS in the confed !!!!!.
More research revealed the following URL:
Quote:
local-as -Do not advertise this route to peers outside the local autonomous system. This route will not be advertised to other autonomous systems or sub-autonomous systems when confederations are configured.
Now that's more like what I saw! What ? A contradiction?
Can anyone share their experiences with this feature?
Comments would be very much appreciated
Daniel
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:13 GMT-3