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

CloudEngine 12800 and 12800E V200R005C10

This document describes the configurations of VPN, including GRE, BGP/MPLS IP VPN, BGP/MPLS IPv6 VPN, VLL, PWE3, and VPLS.
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).
Binding VSIs to AC Interfaces

Binding VSIs to AC Interfaces

Context

Based on the type of link between a PE and a CE, a VSI is bound to a VLANIF interface or a Layer 2 sub-interface when the PE and the CE are connected through the VLANIF interface or a Layer 2 sub-interface.

NOTE:
  • In the VPLS application, different CEs are transparently connected in the same LAN segment through VSIs, and the IP addresses of the CEs must be different. The IP address of the interface that connects the PE to the CE and the IP address of the CE must be in different network segments. Otherwise, the local CE may learn incorrect ARP entries. This leads to traffic loss between CEs in the same VSI.

  • Layer 2 protocol packets such as BPDUs cannot be transmitted over the VPLS network.

  • When a VLANIF interface is used as an AC-side interface, physical interfaces in the corresponding VLAN do not support port security or DHCP sticky MAC function.

Procedure

  • Bind a VSI to a VLANIF interface.

    Do as follows on the PEs at both ends of a PW:

    1. Run system-view

      The system view is displayed.

    2. Run interface vlanif vlan-id

      The VLANIF interface view is displayed.

    3. Run l2 binding vsi vsi-name

      The VLANIF interface is bound to the VSI.

      NOTE:
      • If a VLAN is configured with IGMP snooping, the VLANIF interface of the VLAN cannot be used as an AC interface. To bind the VLANIF interface to a VSI, delete the IGMP snooping configuration from the VLAN first.
      • If a VLAN has been specified as the TRILL CE VLAN, the corresponding interface cannot be configured as an AC-side interface.

      • If a VLAN has been specified as the MUX VLAN, the VLANIF interface of the VLAN cannot be configured as an AC-side interface.

      • If a VLAN is not mapped to MSTP instance 0, the VLANIF interface corresponding to the VLAN cannot be configured as an AC-side interface.

    4. Run commit

      The configuration is committed.

  • Bind a VSI to a Layer 2 sub-interface.

    Do as follows on the PEs at both ends of a PW:

    1. Run system-view

      The system view is displayed.

    2. Run bridge-domain bd-id

      Creating a bridge domain as a broadcast domain and displays the bridge domain view.

    3. Run l2 binding vsi vsi-name

      Binding a VSI to a BD.

      By default, a BD is not bound to any VSI.

    4. Run quit

      Return to the system view.

    5. Run interface interface-type interface-number.subnum mode l2

      Creating a Layer 2 sub-interface and displays the Layer 2 sub-interface view.

    6. Run encapsulation { dot1q [ vid low-vid [ to high-vid ] ] | default | untag | qinq [ vid pe-vid ce-vid ce-vid ] | qinq vid low-pe-vid [ to high-pe-vid ] ce-vid low-ce-vid [ to high-ce-vid ] }

      Configuring an encapsulation type on a Layer 2 sub-interface.

      By default, no encapsulation type is specified on a Layer 2 sub-interface.

      NOTE:

      If the encapsulation type of the VSI is VLAN, the type of the Layer 2 sub-interface added to the BD must be transparent transmission. If the encapsulation type of the VSI is Ethernet, the type of the Layer 2 sub-interface added to the BD must be termination.

      Transparent transmission Layer 2 sub-interfaces include:
      • Default
      • Dot1q (with the rewrite no-action command configured)
      • QinQ (without the rewrite pop double command configured)
      Termination Layer 2 sub-interfaces include:
      • Untag
      • Dot1q (without the rewrite no-action command configured)
      • QinQ (with the rewrite pop double command configured)

    7. Run bridge-domain bd-id

      Adding a Layer 2 sub-interface to a bridge domain.

      By default, no Layer 2 sub-interface is added to any BD.

    8. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-04-03

Document ID: EDOC1100075353

Views: 14475

Downloads: 25

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