PW redundancy in master/slave mode implements fault isolation for public and AC links.
When creating a PW on the local end, configure the PWs that are connected to the two remote PEs. The primary/secondary PW status is manually specified on a local PE and the remote master PE and is notified to the remote slave PE connected to the local PE. The combined usage of PW redundancy in master/slave mode and the bypass PW can prevent network-side faults from affecting the AC side and AC-side faults from affecting the network side.
This configuration is applicable only to the master/slave mode of PW redundancy. If only the independent PW redundancy mode is used, skip this configuration.
If multi-segment PWs need to be set up, you must configure a switching PW on each SPE. PW redundancy supports only dynamic switching PWs.
A CSG is enabled to receive packets on both primary and secondary PWs, preventing packet loss during a primary/secondary PW switchback.
Traffic is switched from the primary PW to the secondary PW.
In the scenario where PW redundancy in master/slave mode is configured, traffic is transmitted through the primary PW, and the secondary PW functions normally. To forcibly switch traffic from the primary PW to the secondary PW (for example, because of a device upgrade or service re-deployment), you can use the mpls l2vpn switchover command. To switch traffic back to the primary PW (for example, after the device is upgraded), you can run the undo mpls l2vpn switchover command to forcibly switch traffic from the secondary PW to the primary PW.
The configuration is committed.