Configuring a large-scale BGP network
In a large network, the number of BGP connections is huge and BGP configuration and maintenance are
complicated. To simply BGP configuration, you can use the peer group, community, route reflector, and
confederation features as needed. For more information about configuring peer groups, see
"Configuring a BGP peer
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
To configure BGP community (IPv4):
Step
1.
Enter system view.
2.
Enter BGP view or BGP-VPN
instance view.
3.
Enter BGP IPv4 unicast
address family view or
BGP-VPN IPv4 unicast
address family view.
4.
Advertise the COMMUNITY
or extended community
attribute to a peer or peer
group.
5.
(Optional.) Apply a routing
policy to routes advertised to
a peer or peer group.
To configure BGP community (IPv6):
group."
policies."
Command
system-view
•
Enter BGP view:
bgp as-number
•
Enter BGP-VPN instance view:
a.
bgp as-number
b.
ip vpn-instance
vpn-instance-name
address-family ipv4 [ unicast ]
•
Advertise the COMMUNITY
attribute to a peer or peer
group:
peer { group-name |
ip-address }
advertise-community
•
Advertise the extended
community attribute to a peer
or peer group:
peer { group-name |
ip-address }
advertise-ext-community
peer { group-name | ip-address }
route-policy route-policy-name
export
243
Remarks
N/A
N/A
N/A
By default, the COMMUNITY or
extended community attribute is
not advertised.
By default, no routing policy is
applied.