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

S1720, S2700, S5700, and S6720 V200R010C00

This document describes the VPN configuration procedures and provides configuration examples.
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).
VSI Cannot Go Up in Kompella VPLS Mode

VSI Cannot Go Up in Kompella VPLS Mode

Fault Symptom

After Kompella VPLS is configured, the VSI cannot go Up.

Procedure

  1. Run the display vsi name vsi-name command to check whether the encapsulation types and MTUs on both ends are the same.

    • If the encapsulation types and MTUs on both ends are different, run the encapsulation { ethernet | vlan } command in the VSI view to change the encapsulation type on one end, or run the mtu mtu-value command to change the MTU on one end to ensure that the two ends use the same encapsulation type and MTU.

    • If the two ends use the same encapsulation type and MTU but the fault persists, go to step 2.

    NOTE:

    If the VSI needs to go Up, the encapsulation types and MTUs on both ends must be consistent.

  2. Check whether the site IDs on both ends are different in the VSI view.

    • If site IDs on both ends are the same, run the site site-id [ range site-range ] [ default-offset { 0 | 1 } ] command to change the site ID on one end to ensure that the two ends use different site IDs.

    • If site IDs on both ends are different, go to step 3.

    NOTE:

    If the VSI needs to go Up, site IDs on both ends cannot be the same.

  3. Run the display bgp vpls peer [ ipv4-address verbose | verbose ] [ | count ] [ | { begin | exclude | include } regular-expression ] command to check whether the BGP session between the two ends is in Established state.

    • If the BGP session is not in Established state, see "BGP Peer Relationship Fails to Be Established" to locate the fault and establish the BGP session.

    • If the BGP session between the two ends is in Established state, go to step 4.

  4. Run the display vsi name vsi-name verbose command to check whether the VSI selects a tunnel.

    • Check whether the Tunnel ID value is 0x0. If the Tunnel ID value is 0x0, the VSI does not select a tunnel.
    • Check the Tunnel Policy Name field. If this field is not displayed, the VSI uses an LDP LSP or no tunnel policy is configured for the VSI. To use an MPLS-TE tunnel, configure a tunnel policy. The value of the Tunnel Policy Name field indicates the tunnel policy of the VSI. You can run the display this command in the corresponding tunnel policy view to check the tunnel policy configuration.

    NOTE:

    If the tunnel binding destination dest-ip-address te { tunnel interface-number } command is configured in the tunnel policy view, run the mpls te reserved-for-binding command in the tunnel interface view.

    If the tunnel is not Up on both ends, see "LSP Goes Down" or " TE Tunnel Goes Down" to locate the fault and enable the tunnel to go Up. If the tunnel between the two ends is Up and the TE interface is correctly configured, go to step 5.

    NOTE:

    A VSI can be Up only when the tunnel between the two ends is Up.

  5. Check whether the site ID on the local end is smaller than the sum of range and default offset on the remote end.

    • If the site ID on the local end is equal to or greater than the sum of range and default offset on the remote end, modify either the site ID on the local end or the range on the remote end.

    • If the site ID on local end is smaller the sum of the range and default offset on the remote end, go to step 6.

  6. Run the display vsi name vsi-name verbose command to check whether the AC interfaces on both ends are Up.

    If the AC interfaces on the two ends are Down, see "Physical Interconnection&Interface Type" to make the AC interfaces go Up.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141944

Views: 73201

Downloads: 507

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