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 an AC Interface to a VSI

Binding an AC Interface to a VSI

AC interfaces can be bound to VSIs based on access link types.

Context

The binding scenarios are classified as follows based on access link types:
  • Binding an Ethernet interface to a VSI: A PE uses GE interface to connect to a CE.
  • Binding an Ethernet sub-interface to a VSI: A PE uses GE sub-interface to connect to a CE.
  • Binding a VLANIF sub-interface to a VSI: A PE uses a VLANIF interface to connect to a CE
  • Binding an L2VE sub-interface to a VSI: A PE uses an L2VE sub-interface to connect to a CE.
  • Binding an Eth-Trunk interface to a VSI: A PE uses an Eth-Trunk interface to connect to a CE.
  • Binding an Eth-Trunk sub-interface to a VSI: A PE uses an Eth-Trunk sub-interface to connect to a CE.
  • Binding a dot1q VLAN tag termination sub-interface to a VSI: A PE uses a dot1q VLAN tag termination sub-interface to connect to a CE.
NOTE:

On a VPLS network, CEs transparently connect to each other on the same LAN segment and therefore must have different IP addresses. In addition, PE interfaces that connect to CEs must have different network segment addresses as connected CEs. Otherwise, local CEs may learn incorrect ARP entries, causing traffic loss.

Procedure

  • Bind an Ethernet interface to a VSI.

    Perform the following steps on the PEs at both ends 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 Ethernet interface is bound to a VSI.

    4. Run commit

      The configuration is committed.

  • Bind an Ethernet sub-interface to a VSI.

    Perform the following steps on the PEs at both ends of a PW.

    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number.subinterface-number

      The Ethernet sub-interface view is displayed.

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

      A VLAN encapsulation type is configured.

    4. Run l2 binding vsi vsi-name

      The Ethernet sub-interface is bound to a VSI.

    5. Run commit

      The configuration is committed.

  • Bind a VLANIF interface to a VSI.

    Perform the following steps 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 a VSI.

    4. Run commit

      The configuration is committed.

  • Bind an L2VE sub-interface to a VSI.

    Perform the following steps on the PEs at both ends of a PW.

    1. Run system-view

      The system view is displayed.

    2. Run interface virtual-ethernet interface-number.subinterface-number

      The VE sub-interface view is displayed.

    3. Run vlan-type dot1q vlan-id

      A VLAN ID is configured.

    4. Run l2 binding vsi vsi-name

      The L2VE sub-interface is bound to a VSI.

    5. Run commit

      The configuration is committed.

  • Bind an Eth-Trunk interface to a VSI.

    Perform the following steps on the PEs at both ends 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 interface view is displayed.

    5. Run eth-trunk trunk-id

      The interface is added to the Eth-Trunk interface.

      An interface to be added to an Eth-Trunk interface cannot have services or Layer 3 configurations.

      One Ethernet interface can be added only to one Eth-Trunk interface. Before adding an Ethernet interface to an Eth-Trunk interface, ensure that the Ethernet interface does not belong to any Eth-Trunk interface.

      The interfaces at the two ends of an Eth-Trunk member link must be of the same type.

    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 to a VSI.

    9. Run commit

      The configuration is committed.

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

    Perform the following steps on the PEs at both ends 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 interface view is displayed.

      Note that Eth-Trunk member interfaces cannot have statically configured MAC addresses.

    5. Run eth-trunk trunk-id

      The interface is added to the Eth-Trunk interface.

      An interface to be added to an Eth-Trunk interface cannot have services or Layer 3 configurations.

      One Ethernet interface can be added only to one Eth-Trunk interface. Before adding an Ethernet interface to an Eth-Trunk interface, ensure that the Ethernet interface does not belong to any Eth-Trunk interface.

      The interfaces at the two ends of an Eth-Trunk member link must be of the same type.

    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 ]

      A VLAN encapsulation type is configured.

    9. Run l2 binding vsi vsi-name

      The Eth-Trunk sub-interface is bound to a VSI.

    10. Run commit

      The configuration is committed.

Translation
Download
Updated: 2019-01-14

Document ID: EDOC1100058925

Views: 37153

Downloads: 61

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