Binding a VSI to an AC Interface

The view in which a VSI is bound to an Attachment Circuit (AC) interface depends on the type of link between the PE and CE.

Context

In VPLS applications, CEs are transparently connected to each other on the same network segment of a LAN by means of VSIs. Therefore, the IP addresses of the CEs must be different.

The interface directly connecting a PE to a CE cannot be configured with an IP address.

Procedure

  • Bind a VSI to an Ethernet interface.
    1. Run system-view

      The system view is displayed.

    2. Run interface interface-type interface-number

      The interface view is displayed.

    3. Run l2 binding vsi vsi-name [ access-port ]

      A VSI is bound to the Ethernet interface.

    4. Run commit

      The configuration is committed.

  • Bind a VSI to an Ethernet sub-interface.
    1. Run system-view

      The system view is displayed.

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

      The Ethernet sub-interface (AC interface) view is displayed.

    3. Run vlan-type dot1q vlan-id

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

    4. Run l2 binding vsi vsi-name

      A VSI is bound to the Ethernet sub-interface.

    5. Run commit

      The configuration is committed.

  • Bind a VSI to a VLANIF interface.
    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.

    4. Run commit

      The configuration is committed.

  • Bind a VSI to a L2VE interface.
    1. Run system-view

      The system view is displayed.

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

      The L2VE sub-interface view is displayed.

    3. Run vlan-type dot1q vlan-id

      The VLAN ID of the L2VE sub-interface is configured.

    4. Run l2 binding vsi vsi-name

      The L2VE interface is bound to a VSI.

    5. Run commit

      The configuration is committed.

  • Bind a VSI to an Eth-Trunk interface.
    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 to an Eth-Trunk interface, ensure that the interface is not configured with any Layer 3 attributes (such as IP addresses) or services.

      An Ethernet interface can join only one Eth-Trunk interface. To join another Eth-Trunk interface, the Ethernet interface must quit from the original one.

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

    9. Run commit

      The configuration is committed.

  • Bind a VSI to an Eth-Trunk sub-interface.
    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 to the Eth-Trunk interface is displayed.

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

      The member interfaces of a trunk interface cannot be Eth-Trunk interfaces.

    5. Run eth-trunk trunk-id

      The interface is added to the Eth-Trunk interface.

      Before adding an interface to an Eth-Trunk interface, ensure that the interface is not configured with any Layer 3 attributes (such as IP addresses) or any services.

      An Ethernet interface can join only one Eth-Trunk interface. To join another Eth-Trunk interface, the Ethernet interface must quit from the original one.

      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 interface-number

      The Eth-Trunk sub-interface view is displayed.

    8. Run vlan-type dot1q vlan-id

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

    9. Run l2 binding vsi vsi-name

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

    10. Run commit

      The configuration is committed.

  • Bind a VSI to a dot1q VLAN tag termination sub-interface.
    1. Run system-view

      The system view is displayed.

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

      The view of an Ethernet sub-interface (the AC interface) that connects a PE to a CE is displayed.

    3. Run encapsulation dot1q-termination [ rt-protocol ]

      The encapsulation type for a VLAN tag termination sub-interface is configured to be dot1q.

      Specify rt-protocol so that the dot1q VLAN tag termination sub-interface supports routing protocols.

    4. Run dot1q termination vid low-pe-vid [ to high-pe-vid ] [ vlan-group group-id ]

      The sub-interface is configured to terminate single-tagged packets.

      After you specify rt-protocol, the dot1q VLAN tag termination sub-interface terminates packets carrying a fixed-value VLAN tag.

    5. Run l2 binding vsi vsi-name

      A VSI is bound to the sub-interface for Dot1q VLAN tag termination.

    6. Run commit

      The configuration is committed.

  • Bind a VSI to a QinQ VLAN tag termination sub-interface.
    1. Run system-view

      The system view is displayed.

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

      The view of an Ethernet sub-interface (the AC interface) that connects a PE to a CE is displayed.

    3. Run encapsulation qinq-termination [ local-switch | rt-protocol ]

      The encapsulation type for a VLAN tag termination sub-interface is configured to be QinQ.

      In the preceding command:
      • Specify local-switch so that the QinQ VLAN tag termination sub-interface supports local switching.

      • Specify rt-protocol so that the QinQ VLAN tag termination sub-interface supports routing protocols.

    4. Run qinq termination pe-vid pe-vid [ to high-pe-vid ] ce-vid ce-vid [ to high-ce-vid ] [ vlan-group group-id ]

      The sub-interface is configured to terminate QinQ packets.

      After you specify rt-protocol, the sub-interface can terminate only double-tagged packets whose inner and outer tags are specific VLAN IDs.

    5. Run l2 binding vsi vsi-name

      A VSI is bound to the QinQ VLAN tag termination sub-interface.

    6. Run commit

      The configuration is committed.

  • Bind a VSI to a QinQ stacking sub-interface.
    1. Run system-view

      The system view is displayed.

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

      The view of an Ethernet sub-interface (the AC interface) that connects a PE to a CE is displayed.

    3. Run qinq stacking vid low-ce-vid [ to high-ce-vid ] [ vlan-group group-id ]

      The QinQ stacking sub-interface is configured.

      When you run the qinq stacking vid command on different sub-interfaces of a main interface, ensure that the values of ce-vid do not overlap.

      • If you have run the vlan-group command to configure a VLAN group on a sub-interface, you must specify vlan-group in the qinq stacking vid command.

      • If you do not run the vlan-group command to configure a VLAN group on a sub-interface, you cannot specify vlan-group in the qinq stacking vid command.

    4. Run l2 binding vsi vsi-name

      A VSI is bound to the QinQ stacking sub-interface.

    5. Run commit

      The configuration is committed.

Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >