Filter
Top Products
Border Gateway Protocol IPv4 (BGPv4) | 247
Configure IP community lists
Within FTOS, you have multiple methods of manipulating routing attributes. One attribute you can
manipulate is the COMMUNITY attribute. This attribute is an optional attribute that is defined for a group
of destinations. In FTOS, you can assign a COMMUNITY attribute to BGP routers by using an IP
Community list. After you create an IP Community list, you can apply routing decisions to all routers
meeting the criteria in the IP Community list.
IETF RFC 1997 defines the COMMUNITY attribute and the pre-defined communities of INTERNET,
NO_EXPORT_SUBCONFED, NO_ADVERTISE, and NO_EXPORT. All BGP routes belong to the
INTERNET community. In the RFC, the other communities are defined as follows:
• All routes with the NO_EXPORT_SUBCONFED (0xFFFFFF03) community attribute are not sent to
CONFED-EBGP or EBGP peers, but are sent to IBGP peers within CONFED-SUB-AS.
• All routes with the NO_ADVERTISE (0xFFFFFF02) community attribute must not be advertised.
• All routes with the NO_EXPORT (0xFFFFFF01) community attribute must not be advertised outside a
BGP confederation boundary, but are sent to CONFED-EBGP and IBGP peers.
FTOS also supports BGP Extended Communities as described in RFC 4360—BGP Extended
Communities Attribute.
redistribute ospf process-id [match
external {1 | 2} | match internal]
[metric-type {external | internal}]
[route-map map-name]
ROUTER BGP or
CONF-ROUTER_BGPv6_
AF
Include specific OSPF routes in IS-IS.
Configure the following parameters:
•
process-id range: 1 to 65535
•
match external range: 1 or 2
• match internal
• metric-type: external or internal.
• map-name: name of a configured route
map.
Command Syntax Command Mode Purpose