Specify Community Information
By default, no BGP community information is associated with generated routes. To associate community information with the routes, include the
communityoption:[edit routing-options generate (defaults | route)]community [community-ids];For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.
community-idsis one or more community identifiers for either communities or extended communities.The format for community identifiers is:
as-number:community-value
as-numberis the AS number and can be a value in the range 1 through 65534.community-valueis the community identifier and can be a number in the range 0 through 65535.You also can specify
community-idsfor communities as one of the following well-known community names, which are defined in RFC 1997:
no-advertise—Routes containing this community name are not advertised to other BGP peers.no-export—Routes containing this community name are not advertised outside a BGP confederation boundary.no-export-subconfed—Routes containing this community name are not advertised to external BGP peers, including peers in other members' ASs inside a BGP confederation.You can explicitly exclude BGP community information with a generated route using the
noneoption. Includenonewhen configuring an individual route in therouteportion of thegeneratestatement to override acommunityoption specified in thedefaultsportion of the statement.The format for extended community identifiers is:
type:administrator:assigned-number
typeis the type of extended community and can be either atarget,origin, ordomain-idcommunity. Thetargetcommunity identifies the destination to which the route is going. Theorigincommunity identifies where the route originated. Thedomain-idcommunity identifies the OSPF domain where the route originated.
administratoris the administrator. It is either an autonomous system (AS) number or an IPv4 address prefix, depending on the type of extended community.