Mapping a static Ethernet service instance to a VSI

An Ethernet service instance matches a list of VLANs on a site-facing interface. The VTEP assigns customer traffic from the VLANs to a VXLAN by mapping the Ethernet service instance to a VSI.

Configuration restrictions and guidelines

You can create static Ethernet service instances on both a Layer 2 aggregate interface and its member ports and map the Ethernet service instances to VSIs. However, the Ethernet service instances on the aggregation member ports are down. For the Ethernet service instances to come up, you must remove the aggregation member ports from the aggregation group.

If an Ethernet service instance is configured with the encapsulation untagged criterion on a Layer 2 Ethernet or aggregate interface, you cannot apply a QoS policy for VLAN tag nesting to that interface. For more information about VLAN tag nesting, see QoS configuration in ACL and QoS Configuration Guide.

When you configure Ethernet service instances, follow these feature compatibility restrictions and guidelines:

Ethernet service instances and QinQ cannot work together. Do not configure both features on an interface. For more information about QinQ, see Layer 2 —LAN Switching Configuration Guide.
To forward the multicast traffic from a VLAN on the interface, make sure an Ethernet service instance contains the VLAN ID. The interface cannot forward a multicast packet that does not match any Ethernet service instance.

When you configure Ethernet service instances, follow these access mode restrictions:

You must use Ethernet access mode if one of the following criteria is configured:
- encapsulation default
- encapsulation tagged
- encapsulation untagged
You can use Ethernet access mode or VLAN access mode if any other criterion is configured.

If you execute the encapsulation default command for an Ethernet service instance in Ethernet access mode on a Layer 2 Ethernet interface or Layer 2 aggregate interface, the interface can host multiple Ethernet service instances. Traffic that does not match any other Ethernet service instance matches the Ethernet service instance that uses the default criterion.

Configuration procedure

To map a static Ethernet service instance to a VSI:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	Enter Layer 2 Ethernet interface view. interface interface-type interface-number Enter Layer 2 aggregate interface view.interface bridge-aggregation interface-number	N/A
3. Create an Ethernet service instance and enter Ethernet service instance view.	service-instance instance-id	By default, no Ethernet service instances exist.
4. Configure a frame match criterion.	Match frames that do not match any other service instance on the interface: encapsulation default Match any 802.1Q tagged or untagged frames: encapsulation { tagged \| untagged } Match frames tagged with the specified outer and inner 802.1Q VLAN IDs: encapsulation s-vid vlan-id [ c-vid { vlan-id-list \| all } \| only-tagged ] encapsulation s-vid vlan-id-list [ c-vid vlan-id-list ]	By default, an Ethernet service instance does not contain a frame match criterion.
5. (Optional.) Configure the VLAN tag processing rule for incoming traffic.	rewrite inbound tag { remark 1-to-1 s-vid vlan-id \| strip s-vid }	By default, VLAN tags of incoming traffic are not processed.
6. (Optional.) Configure the VLAN tag processing rule for outgoing traffic.	rewrite outbound tag nest s-vid vlan-id	By default, VLAN tags of outgoing traffic are not processed.
7. (Optional.) Set the bandwidth limit for the Ethernet service instance.	bandwidth bandwidth	By default, no bandwidth limit is set for an Ethernet service instance.
8. Map the Ethernet service instance to a VSI.	xconnect vsi vsi-name [ access-mode { ethernet \| vlan } ] [ track track-entry-number&<1-3> ]	By default, an Ethernet service instance is not mapped to any VSI.

prev	up	next
Configuration restrictions and guidelines	home	Mapping dynamic Ethernet service instances to VSIs