Configuring Public-Network-and-Private-Network Decoupling for VPLS

When a VPLS recurses to a public network, to minimize the impact of VPLS service changes on the convergence of other services, configure the public-network-and-private-network decoupling function for VPLS.

Usage Scenario

When VPLS services recurse to a public network, public network flapping causes changes in the VPLS services. Consequently, a device updates entries, which adversely affects VPLS service convergence. To enable the VPLS private and public network decoupling function to prevent the impact on the VPLS services, run the mpls vpls convergence separate enable command.

Pre-configuration Tasks

Before configuring the public-network-and-private-network decoupling function for VPLS, configure basic VPLS functions.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls l2vpn

    MPLS L2VPN is enabled.

  3. Run commit

    The configuration is committed.

  4. Run quit

    Return to the system view.

  5. Run vsi vsi-name [ static ]

    A VSI is created, and the VSI view is displayed.

  6. Run mpls vpls convergence separate enable

    The public-network-and-private-network decoupling function for VPLS is enabled.

    After public-network-and-private-network decoupling for VPLS is enabled in the system view, this function takes effect in all VSIs. If this function is enabled in the VSI view, this function takes effect only in a specified VSI. The command run in the system view and that in the VSI view are mutually exclusive with each other.

  7. (Optional) Run reserve-interface fast-switch enable

    The reserve-interface fast switching function is enabled.

    To improve the switching performance of broadcast traffic if the master board fails, you can perform this step.

  8. Run commit

    The configuration is committed.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >