(Optional) Configuring the Features of Kompella VPLS

Context

During the Kompella VPLS configuration, if n PEs are located in a VPLS domain, n(n-1)/2 IBGP connections need to be established. When there are a large number of IBGP peers, network resources and CPU resources are greatly consumed. A route reflector (RR) can be used to solve the problem. One PE functions as an RR and other PEs function as clients. The clients establish IBGP connections with the RR.

When configuring route reflection for Kompella VPLS, configure the RR and reflection policy, and enable VPN-target filtering for received VPLS label blocks.

The BGP VPLS address family view is used to manage the VPLS label block.

Do as follows on the PEs at both ends of a PW:

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Run vpls-family
The BGP-VPLS address family view is displayed.
Run peer { group-name | ipv4-address } reflect-client
The RR and its client are configured.

After this command is run, the local device functions as the RR and a peer or a peer group functions as the client of the RR.
Run undo policy vpn-target
The filtering of VPLS label blocks based on VPN targets is disabled.

The RR deployed on a Kompella VPLS network does not save VPN routes or label blocks. You need to run this command to save all VPN routes or label blocks sent from PEs.

This command applies only to RRs and ASBRs.
Run rr-filter extcomm-filter-number
The reflection policy is configured.

By default, no reflection policy of the RR is created.

Only the IBGP route whose route-target extended community attribute meets the matching rules can be reflected. In this manner, load balancing is implemented.