No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - VPN

S7700 and S9700 V200R013C00

This document describes the configurations of VPN, including GRE, IPSec, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, VPLS, L2VPN Access to L3VPN.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
(Optional) Associating Spoke PW Status with Hub PW Status

(Optional) Associating Spoke PW Status with Hub PW Status

Context

Figure 7-29   VPLS PW redundancy networking

Under normal circumstances, if all hub PWs connected to SPE1 go Down but PW1 is Up, the upstream traffic still travels along the primary PW, PW1. As a result, traffic gets lost. To prevent the preceding problem, you can associate spoke PW status with hub PW status. Then, after all the hub PWs of the SPE where the primary spoke PW resides go Down, the SPE notifies the UPE of switching traffic to the secondary spoke PW for transmission.

Do as follows on the SPE devices:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run vsi vsi-name static

    The view of the created VSI is displayed.

  3. Run pwsignal ldp

    The VSI-LDP view is displayed.

  4. Run peer peer-address [ negotiation-vc-id vc-id ] pw pw-name

    The PW view is displayed.

  5. Run track hub-pw

    Spoke PW status is associated with hub PW status.

    By default, spoke PW status is not associated with hub PW status.

    This command can only be used to configure spoke PWs to track the status of hub PWs. The peer peer-address [ negotiation-vc-id vc-id ] [ tnl-policy policy-name ] upe must have been run to create a spoke PW.

    After the track hub-pw command is configured, the SPE notifies the UPE of switching traffic to the secondary spoke PW for transmission after detecting that all connected hub PWs go Down. The protect-group group-name and protect-mode pw-redundancy master commands must have been run to create a PW protection group with the master/slave PW redundancy mode, and the primary and secondary PWs have joined the group.

Translation
Download
Updated: 2019-04-08

Document ID: EDOC1100065751

Views: 38000

Downloads: 50

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next