Configuring an AC Interface

In MPLS E-Line scenarios, a Layer 2 sub-interface can function as an AC interface, and traffic encapsulation can be configured on the AC interface to transmit different types of data packets.

Procedure

  1. Run system-view

    The system view is displayed.

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

    A Layer 2 sub-interface is created, and the sub-interface view is displayed.

    Before running this command, ensure that the Layer 2 main interface does not have the port link-type dot1q-tunnel command configuration. If the configuration has existed, run the undo port link-type command to delete it.

    In addition to using Layer 2 sub-interfaces as AC interfaces, AC interfaces can be Ethernet main interfaces, Layer 3 sub-interfaces, or Eth-Trunk interfaces.

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

    The flow encapsulation type is set to enable different interfaces to receive different data packets.

  4. Run evpl instance evpl-id

    An EVPL instance is bound to the Layer 2 sub-interface.

  5. (Optional) Run evpn-vpws ignore-ac-state

    The function to ignore the AC status on an interface is enabled.

    This step can be performed to ensure EVPN VPWS service continuity after the AC interface is configured with the CFM and interface association function in a primary/secondary link networking scenario. In this case, if a primary/secondary link switchover is triggered after the AC status of the interface is changed to down, the AC status of the interface is ignored, and the EVPN VPWS service does not need to be re-established during a primary/secondary link switchover.

  6. Run commit

    The configuration is committed.

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