View - ADTRAN Support Community
View - ADTRAN Support Community
View - ADTRAN Support Community
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Additional BGP Configuration<br />
Specifies a privately defined community for routes serviced by this route map. This is a<br />
numeric value that can be an integer from 1 to 4294967295 or string in the form aa:nn, where aa is the<br />
AS number and nn is the community number. Multiple community number parameters can be present<br />
in the command.<br />
add Appends the listed community number to the end of the community attribute for routes serviced<br />
by this route map.<br />
internet Sets the community attribute to the reserved INTERNET community number for routes<br />
serviced by this route map.<br />
local-as Sets the community attribute to the reserved NO_EXPORT_SUBCONFED community<br />
number for routes serviced by this route map. Routes containing this attribute should not be advertised<br />
to eBGP peers.<br />
no-advertise Sets the community attribute to the reserved NO_ADVERTISE community number for<br />
routes serviced by this route map. Routes containing this attribute should not be advertised to any BGP<br />
peer.<br />
no-export Sets the community attribute to the reserved NO_EXPORT community number for routes<br />
serviced by this route map. Routes containing this attribute should not be advertised to BGP peers<br />
outside a confederation boundary.<br />
none Removes all communities from BGP routes serviced by this route map.<br />
See Table 1 on page 14 for a summary of the well-known communities (for example,<br />
INTERNET, NO_EXPORT_SUBCONFED, etc.) and the policy expected for these<br />
communities.<br />
Attributes, such as local preference and metric, can also be defined for the community string. A<br />
discussion of the set commands used to define these community attributes begin with Prepending<br />
Private AS Numbers for Load Balancing on page 28.<br />
Enabling an AOS Device to Send or Receive BGP Communities<br />
A BGP neighbor must be configured for BGP communities before it is able to send or receive a<br />
community attribute. Use the send-community standard command to enable this peer to accept a<br />
community attribute and add the community attribute to any advertisement sent by this peer. This<br />
command is issued from the BGP Neighbor Configuration mode:<br />
(config-bgp-neighbor)#send-community standard<br />
Deleting Communities from a Route<br />
BGP communities are not completely standardized. External neighbors can place routes in a<br />
community for which the local network does not define a policy or for which it defines a substantially<br />
different policy. A network administrator might not want to apply the policies that the external<br />
neighbor is requesting with the community attribute. As a result, the administrator might need to<br />
remove certain communities from inbound routes in order to enforce the organization’s policies.<br />
61200860L1-29.4E Copyright © 2012 <strong>ADTRAN</strong>, Inc. 15