Owner's Manual

479
the group as a whole and to give the group precedence. The grouped path can
itself include regular expression operators.
Pre-defined Community Names
You also can specify community-id as one of the following well-known community names, which
are defined in RFC 1997, BGP Communities Attribute:
-
no-advertise —Routes in this community name must not be advertised to other BGP peers.
-
no-export —Routes in this community must not be advertised outside a BGP confederation
boundary.
-
no-export-subconfed —Routes in this community must not be advertised to external BGP peers,
including peers in other members' ASs inside a BGP confederation.
Defining Community by Type
community-ids also identifies the type of extended community in the following format:
type:administrator:assigned-number
- type —The type of extended community. This can be either a bandwidth, target, origin , or
domain-id community. The bandwidth community sets up the bandwidth extended
community. The target community identifies the destination to which the route is going. The
origin community identifies where the route originated. The domain-id community identifies
the Open Shortest Path First (OSPF) domain from which the route originated.
administrator is the administrator. It is either an AS number or an IP version 4 (IPv4) address
prefix, depending on the type of extended community.
assigned-number identifies the local provider.
NOTE:
Regular expressions are not supported for extended communities
See Configuring the Extended Communities Attribute (Examples) for examples.
Click
Apply to accept your edits, or Cancel to abandon them. Clicking Configure sends these items
as configured to the selected equipment.
Refresh re-queries for field values on this screen.
Configuring the Extended Communities Attribute (Examples)
The following are JunOS representations of example extended community configurations. They
display the extended community expressions described above.
• A target community with an administrative field of 10458 and an assigned number of 20:
target:10458:20
• A target community with an administrative field of 1.1.1.1 and an assigned number of 20:
target:1.1.1.1:20
• An origin community with an administrative field of 1.1.1.1 and an assigned number of 20:
origin:1.1.1.1:20