Configuring Route Reflection for BGP IPv4 VPN Routes

Procedure

1. Run system-view

   The system view is displayed.

2. Run bgp { as-number-plain | as-number-dot }

   The BGP view is displayed.

3. Run ipv4-family vpnv4

   The BGP VPNv4 address family view is displayed.

4. Enable route reflection for BGP VPNv4 routes on the RR.

   • Run the peer group-name reflect-client command to enable route reflection if the RR establishes the MP IBGP connection with the peer group consisting of client PEs.

   • Run the peer ipv4-address reflect-client command repeatedly to enable route reflection if the RR establishes the MP IBGP connection with each PE rather than peer group.

5. Run undo policy vpn-target

   The filtering of VPNv4 routes based on the VPN target is disabled.

6. (Optional) Run rr-filter { extcomm-filter-number | extcomm-filter-name }

   The reflection policy is configured for the RR. Only the IBGP route of which route-target extended community attribute meets the matching rules can be reflected. This allows load balancing among RRs.

   In the command, the extended community filter specified by extcomm-filter-number or extcomm-filter-name must have been configured using the ip extcommunity-filter command.

7. (Optional) Run undo reflect between-clients

   Route reflection is disabled between clients.

   If the clients of an RR have established full-mesh connections with each other, the undo reflect between-clients command can be used to disable route reflection between clients in order to reduce the link cost. By default, route reflection is enabled between the clients of an RR.

   This command can only be configured on the RR.

8. (Optional) Run reflector cluster-id cluster-id

   The RR cluster ID is set.

   If a cluster has multiple RRs, you can use this command to set the same cluster ID for these RRs to prevent routing loops. By default, the cluster ID is the router ID.