Configuring bgp community, Configuring a bgp route reflector – H3C Technologies H3C SR8800 User Manual
Page 249
233
Configuring BGP community
A BGP community is a group of destinations with the same characteristics. It has no geographical
boundaries and is independent of ASs.
You can configure a routing policy to define which destinations belong to a BGP community and then
advertise the community attribute to a peer/peer group.
You can apply a routing policy to filter routes advertised to/received from a peer/peer group according
to the community attribute. This way helps simplify policy configuration and management.
For how to configure a routing policy, see the chapter “Configuring routing policies.”
To configure BGP community:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp as-number
N/A
3.
Advertise the community attribute to a
peer/peer group.
•
Advertise the community attribute
to a peer/peer group:
peer { group-name | ip-address }
advertise-community
•
Advertise the extended community
attribute to a peer/peer group:
peer { group-name | ip-address }
advertise-ext-community
Not configured by
default
4.
Apply a routing policy to routes advertised
to a peer/peer group.
peer { group-name | ip-address }
route-policy route-policy-name export
Not configured by
default
Configuring a BGP route reflector
If an AS has many BGP routers, you can configure them as a cluster and configure one of them as a route
reflector and others as clients to reduce IBGP connections.
To enhance network reliability and prevent single point of failure, specify multiple route reflectors for a
cluster. The route reflectors in the cluster must have the same cluster ID to avoid routing loops.
To configure a BGP route reflector:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp as-number
N/A