From: Scott Morris (smorris@ipexpert.com)
Date: Thu May 22 2008 - 15:32:51 ART
Both discuss the idea about NOT sending routes out to eBGP peers. But
"no-export" WILL still send to eBGP confederation peers (that line of
external is a little blurred).
The "local-as" will not send to ANY other AS, whether a confederation peer
or not.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M
#153, JNCIS-ER, CISSP, et al.
CCSI/JNCI-M/JNCI-ER
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of ccie
az
Sent: Thursday, May 22, 2008 1:41 PM
To: Cisco certification
Subject: BGP community
Hi All,
This may be an easy question, but whats the difference between the BGP
community Local-AS and No-export?
Rack1R6(config-route-map)#set community ?
<1-4294967295> community number
aa:nn community number in aa:nn format
additive Add to the existing community
internet Internet (well-known community)
local-AS Do not send outside local AS (well-known community)
no-advertise Do not advertise to any peer (well-known community)
no-export Do not export to next AS (well-known community)
From the description above it sounds like it will do the same thing. I have
3 routers in the same AS, but each router is also linked to another AS. The
goal was to stop all prefixes being advertised from one AS out to another. I
used local-AS, but the solution guide used no-export.
Az
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2008 - 06:59:18 ART