Configuring BGP community
By default, a router does not advertise the COMMUNITY or extended community attribute to its peers or peer groups. When the router receives a route carrying the COMMUNITY or extended community attribute, it removes the attribute before advertising the route to other peers or peer groups.
Perform this task to enable a router to advertise the COMMUNITY or extended community attribute to its peers for route filtering and control. You can also reference a routing policy to add or modify the COMMUNITY or extended community attribute for specific routes. For more information about routing policy, see "Configuring routing policies."
To configure BGP community (IPv4):
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP view or BGP-VPN instance view. |
| N/A |
3. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. | address-family ipv4 [ unicast ] | N/A |
4. Advertise the COMMUNITY or extended community attribute to a peer or peer group. |
| By default, the COMMUNITY or extended community attribute is not advertised. |
5. (Optional.) Apply a routing policy to routes advertised to a peer or peer group. | peer { group-name | ip-address } route-policy route-policy-name export | By default, no routing policy is applied. |
To configure BGP community (IPv6):
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP view. | bgp as-number | N/A |
3. Enter BGP IPv6 unicast address family view. | address-family ipv6 [ unicast ] | N/A |
4. Advertise the COMMUNITY or extended community attribute to a peer or peer group. |
| By default, the COMMUNITY or extended community attribute is not advertised. |
5. (Optional.) Apply a routing policy to routes advertised to a peer or peer group. | peer { group-name | ipv6-address } route-policy route-policy-name export | By default, no routing policy is applied. |