Configuring Bgp Community; Configuring Bgp - H3C S5600 Series Operation Manual

It is not required to specify an AS number for creating an IBGP peer group.
If there already exists a peer in a peer group, you can neither change the AS number of the peer
group, nor delete a specified AS number through the undo command.
In a hybrid EBGP peer group, you need to specify the AS number for all peers respectively.

Configuring BGP Community

Follow these steps to configure BGP community:
To do...
Enter system view
Enter BGP view
Configure the peers to
advertise COMMUNITY
attribute to each other
Specify routing policy for
the routes exported to
the peer group
When configuring BGP community, you must use a routing policy to define the specific
COMMUNITY attribute, and then apply the routing policy when a peer sends routing information.
For configuration of routing policy, refer to "IP Routing Policy Configuration".
Configuring BGP RR
Follow these steps to configure BGP RR:
To do...
Enter system view
Enter BGP view
Configure the RR and its client
Configure route reflection between
clients
Use the command...
system-view
bgp as-number
peer group-name
advertise-community
peer group-name route-policy
route-policy-name export
Use the command...
system-view
bgp as-number
peer group-name reflect-client
reflect between-clients
5-26
Remarks
—
—
Required
By default, no COMMUNITY attribute or
extended COMMUNITY attribute is
advertised to any peer group.
Required
By default, no routing policy is specified for
the routes exported to the peer group.
Remarks
—
—
Required
By default, no RR and its client is
configured.
Optional
By default, route reflection is
enabled between clients.