H3C Technologies H3C S10500 Series Switches - Manual (Page 243)

228
To do… Use the command… Remarks
or peer group
Advertise the extended
community attribute to a
peer or peer group
peer { group-name | ip-address }
advertise-ext-community
default.
Apply a routing policy to routes advertised to a
peer or peer group peer { group-name | ip-address }
route-policy route-policy-name export
Required
Not configured by
default.
Configuring a BGP route reflector
If an AS has many BGP routers, you can configure them as a cluster by configuring 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.
Follow these steps to configure a BGP route reflector:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Configure the router as a route
reflector and specify a peer or peer
group as its client
peer { group-name | ip-address }
reflect-client
Required
Not configured by default.
The peer reflect-client command
can be configured in both BGP
view and BGP-VPNv4 subaddress
family view. In BGP view, the
command enables the router to
reflect routes of the public network;
in BGP-VPNv4 subaddress family
view, the command enables the
router to reflect routes of the private
network. (You can enter
BGP-VPNv4 subaddress family
view by executing the ipv4-family
vpnv4 command in BGP view. For
more information about the
ipv4-family vpnv4 command, see
MPLS Command Reference.)
Enable route reflection between
clients
reflect between-clients
Optional
Enabled by default
Configure the cluster ID of the route
reflector
reflector cluster-id cluster-id
Optional
By default, a route reflector uses its
router ID as the cluster ID.