Enabling a BGP4+ Device to Add the Community Attribute to Routes to Be Advertised
The community attribute is used to simplify route-policy management.
Context
The community attribute is transmitted between BGP4+ peers, and its transmission is not restricted within ASs. With the community attribute, a group of routes can share the same route-policy. Before sending a route with the community attribute to peers, BGP4+ can change the original community attribute carried by the route.
Procedure
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
- Run ipv6-family unicast
The IPv6 unicast address family view is displayed.
- Run peer { ipv4-address | ipv6-address | group-name } route-policy route-policy-name export
An export route-policy is applied to routes to be advertised to a specified peer or peer group.
When configuring a BGP4+ community, use a route-policy to define a specific community attribute. Then, apply the route-policy to the routes to be advertised.
For details about the route-policy configuration, see Routing Policy Configuration.
- Run either of the following commands to configure the device to advertise the community attribute to a peer or peer group:
To configure the device to advertise a standard community attribute to a specified peer or peer group, run the peer { ipv4-address | ipv6-address | group-name } advertise-community command.
To configure the device to advertise an extended community attribute to a specified peer or peer group, run the peer { ipv4-address | ipv6-address | group-name } advertise-ext-community command.
- Run commit
The configuration is committed.