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 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Configuration Guide - VPN
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 a VSI to an AC Interface

Binding a VSI to an AC Interface

Based on the type of link between a PE and a CE, a VSI and an AC interface are bound in various views.

Context

Based on the type of link between a PE and a CE, a VSI is bound to an AC interface on the PE in one of the following modes:

  • Binding the VSI to the GE interface when the PE and the CE are connected through the Ethernet interface

  • Binding the VSI to the GE sub-interface when the PE and the CE are connected through the Ethernet sub-interface or GE sub-interface

  • Binding the VSI to the VLANIF interface when the PE and the CE are connected through the VLANIF interface

  • Binding the VSI to the VE interface when the PE and the CE are connected through the VE interface

  • Binding the VSI to the Eth-Trunk when the PE and the CE are connected through the Eth-Trunk interface

  • Binding the VSI to the Eth-Trunk sub-interface when the PE and the CE are connected through the Eth-Trunk sub-interface

  • Binding the VSI to a sub-interface for QinQ VLAN tag termination. For details, refer to the Configuration Guide - LAN Access & MAN Access.

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.

Procedure

  • Bind a VSI to an Ethernet interface.

    Perform the following steps on the endpoint PEs of a PW.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The Ethernet interface view is displayed.

    3. Run l2 binding vsi vsi-name

      The VSI is bound to the Ethernet interface.

  • Bind a VSI to an Ethernet sub-interface.

    Perform the following steps on the endpoint PEs of a PW.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The Ethernet sub-interface view is displayed.

    3. Run vlan-type dot1q vlan-id [ high-vid ]

      The VLAN type of the interface is configured.

    4. Run l2 binding vsi vsi-name

      The VSI is bound with the Ethernet sub-interface.

  • Bind a VSI to a VLANIF interface.

    Perform the following steps on the endpoint PEs 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.

  • Bind a VSI to an Eth-Trunk interface.

    Perform the following steps on the endpoint PEs of a PW.

    1. Run system-view

      The system view is displayed.

    2. Run interface eth-trunk trunk-id

      An Eth-Trunk interface is created.

    3. Run quit

      Return to the system view.

    4. Run interface interface-type interface-number

      The view of the interface to be added into the Eth-Trunk is displayed.

    5. Run eth-trunk trunk-id

      The interface is added into the Eth-Trunk.

      Before adding an interface into an Eth-Trunk, ensure the interface is not configured with any Layer 3 attributes such as IP address and any services.

      The types of the interfaces on both ends of an Eth-Trunk member link must be the same.

    6. Run quit

      Return to the system view.

    7. Run interface eth-trunk trunk-id

      The Eth-Trunk interface view is displayed.

    8. Run l2 binding vsi vsi-name

      The Eth-Trunk interface is bound with the VSI.

  • Bind a VSI to an Eth-Trunk sub-interface.

    Perform the following steps on the endpoint PEs of a PW.

    1. Run system-view

      The system view is displayed.

    2. Run interface eth-trunk trunk-id

      An Eth-Trunk interface is created.

    3. Run quit

      The system view is displayed.

    4. Run interface interface-type interface-number

      The view of the interface to be added into the Eth-Trunk is displayed.

      An Eth-Trunk member interface cannot be configured with a static MAC address.

      NOTE:

      Member interfaces of a trunk cannot be Eth-Trunk interfaces .

    5. Run eth-trunk trunk-id

      The interface is added into the Eth-Trunk.

      Before adding an interface into an Eth-Trunk, ensure the interface is not configured with any Layer 3 attributes such as IP address and any services.

      The types of the interfaces on both ends of an Eth-Trunk member link must be the same.

    6. Run quit

      Return to the system view.

    7. Run interface eth-trunk trunk-id .subnumber

      The Eth-Trunk sub-interface view is displayed.

    8. Run vlan-type dot1q vlan-id [ high-vid ]

      The VLAN encapsulation type is configured on the sub-interface.

    9. Run l2 binding vsi vsi-name

      The Eth-Trunk sub-interface is bound with the VSI.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 30268

Downloads: 55

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