Creating a VPLS Connection

Procedure

1. Run system-view

   The system view is displayed.

2. Run mpls l2vpn

   MPLS L2VPN is enabled.

3. (Optional) Run bgp-vpn label-block-size size-value

   A BGP L2VPN label block size is configured.

4. Run vsi vsi-name

   A VSI is created.

5. Run pwsignal bgp multi-homing

   VPLS multi-homing is enabled.

6. Run route-distinguisher route-distinguisher

   An RD is configured for the VSI.

   The VPN target and site ID of a VSI can be configured only after the RD of the VSI is configured.

   Configuring different RDs for different PEs is recommended.

7. Run vpn-target vpn-target &<1-16> [ both | export-extcommunity | import-extcommunity ]

   A VPN target is configured for the VSI.

   Pay attention to the matching relationship between the local and remote VPN targets:

   • The local export-extcommunity must be the same as the remote import-extcommunity.

   • The local import-extcommunity must be the same as the remote export-extcommunity.

8. Run site-range site-range [ default-offset { 0 | 1 } ]

   A multi-homing site range is configured.

9. Configure VPLS multi-homing in different scenarios.
   • In VPLS multi-homing scenarios where a CE is single-homed to a PE, perform the following steps:
     1. Run site default

        The default VSI-BGP-SITE view is displayed.

        After the pwsignal bgp multi-homing command is run, the system automatically generates a default multi-homing site for the single-homed PE. After the default multi-homing site is generated, run the site default command to enter the default VSI-BGP-SITE view.

     2. Run site-id site-id

        A multi-homing site ID is configured.

     3. (Optional) Run preference preference

        A multi-homing site priority is configured.

   • In VPLS multi-homing scenarios where a CE is multi-homed to PEs, perform the following steps:
     1. Run site name site-name

        A multi-homing site is created, and the VSI-BGP-SITE view is displayed.

     2. Run site-id site-id

        A multi-homing site ID is configured.

     3. Run best-site

        The multi-homing site is configured as the optimal one.

        In VPLS multi-homing scenarios, the system selects a site for PW establishment based on the AC status (ACS), multi-homing site priority (PREF), and PE's router ID (PE-ID). However, the site selected may differ if the ACS, PREF, or PE-ID value changes, causing frequent PW changes. To prevent frequent PW changes, run the best-site command to specify an optimal multi-homing site so that the system will use the optimal site for PW establishment.

        This step is mutually exclusive with 9.e, and 9.f.

     4. (Optional) Run preference preference

        A multi-homing site priority is configured.

     5. (Optional) Run active delay-time delay-time

        A time period during which an AC interface remains in the blocked state is configured.

        This step is mutually exclusive with 9.c.

     6. (Optional) Run recover delay-time delay-time

        The delay after which an AC interface becomes active upon a device restart is configured.

        This step is mutually exclusive with 9.c.

10. (Optional) Run peer peer-address pw pw-name

    A PW is created, and the VSI-BGP-PW view is displayed.

11. (Optional) Run pw pw-name

    The VSI-BGP-PW view is displayed.

    After a PW is created in the preceding step, you can perform this step in the VSI-BGP-MH view to enter the VSI-BGP-PW view.

12. (Optional) Run one of the following commands to configure BUM traffic suppression for the BGP VPLS VSI:
    • To configure the maximum broadcast traffic rate that is allowed, run the broadcast-suppression cir cir-value [ cbs cbs-value ] command.
    • To configure the maximum multicast traffic rate that is allowed, run the multicast-suppression cir cir-value [ cbs cbs-value ] command.
    • To configure the maximum unknown unicast traffic rate that is allowed, run the unknown-unicast-suppression cir cir-value [ cbs cbs-value ] command.

    If the actual traffic rate reaches the configured maximum limit, the excess packets are discarded.

13. Run commit

    The configuration is committed.