Configuring a VXLAN Service Access Point

On an IPv6 VXLAN, Layer 2 sub-interfaces are used for service access and can have different encapsulation types configured to transmit various types of data packets. After a Layer 2 sub-interface is associated with a bridge domain (BD), which is used as a broadcast domain on the IPv6 VXLAN, the sub-interface can transmit data packets through this BD.

Context

As described in Table 1, Layer 2 sub-interfaces can have different encapsulation types configured to transmit various types of data packets.

**Table 1** Traffic encapsulation types
Traffic Encapsulation Type	Description
dot1q	This type of sub-interface accepts only packets with a specified VLAN tag. The dot1q traffic encapsulation type has the following restrictions: The VLAN ID encapsulated by a Layer 2 sub-interface cannot be the same as that permitted by the Layer 2 interface where the sub-interface resides. The VLAN IDs encapsulated by a Layer 2 sub-interface and a Layer 3 sub-interface cannot be the same.
untag	This type of sub-interface accepts only packets that do not carry any VLAN tag. The untag traffic encapsulation type has the following restrictions: The physical interface where the involved sub-interface resides must have only default configurations. Only Layer 2 physical interfaces and Layer 2 Eth-Trunk interfaces can have untag Layer 2 sub-interfaces created. Only one untag Layer 2 sub-interface can be created on a main interface.
default	This type of sub-interface accepts all packets, regardless of whether they carry VLAN tags. The default traffic encapsulation type has the following restrictions: The main interface where the involved sub-interface resides cannot be added to any VLAN. Only Layer 2 physical interfaces and Layer 2 Eth-Trunk interfaces can have default Layer 2 sub-interfaces created. If a default Layer 2 sub-interface is created on a main interface, the main interface cannot have other types of Layer 2 sub-interfaces configured.
qinq	This type of sub-interface receives packets that carry two or more VLAN tags and determines whether to accept the packets based on the innermost two VLAN tags.

Configure a service access point on a Layer 2 gateway:

Procedure

Run system-view
The system view is displayed.
Run bridge-domain bd-id
A BD is created, and the BD view is displayed.
(Optional) Run description description
A BD description is configured.
Run quit
Return to the system view.
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 involved Layer 2 main interface does not have the port link-type dot1q-tunnel command configuration. If the configuration exists, run the undo port link-type command to delete it.
Run encapsulation { dot1q [ vid vid ] | default | untag | qinq [ vid pe-vid ce-vid { low-ce-vid [ to high-ce-vid ] } ] }
A traffic encapsulation type is configured for the Layer 2 sub-interface.
Run rewrite pop { single | double }
The Layer 2 sub-interface is enabled to remove single or double VLAN tags from received packets.

If the received packets each carry a single VLAN tag, specify single.

If the traffic encapsulation type has been specified as qinq using the encapsulation qinq vid pe-vid ce-vid { low-ce-vid [ to high-ce-vid ] | default } command in the preceding step, specify double.
Run bridge-domain bd-id
The Layer 2 sub-interface is added to the BD so that it can transmit data packets through this BD.

If a default Layer 2 sub-interface is added to a BD, no VBDIF interface can be created for the BD.
Run commit
The configuration is committed.