H3C Technologies H3C S12500 Series Switches - Manual (Page 253)

237
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.
In general, it is not required to make clients of a route reflector fully meshed. The route reflector forwards
routing information between clients. If clients are fully meshed, disable route reflection between clients to
reduce routing costs.
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 or BGP-VPN
instance view.
• Enter BGP view:
bgp as-number
• Enter BGP-VPN instance view:
a. bgp as-number
b. ipv4-family vpn-instance
vpn-instance-name
Use either method.
3. Configure the router as a route
reflector and specify a peer or
peer group as its client.
peer { group-name | ip-address }
reflect-client
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.)
4. Enable route reflection
between clients.
reflect between-clients
Optional.
Enabled by default.
5. 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.
Configuring a BGP confederation
Configuring a BGP confederation is another way for reducing IBGP connections in an AS.