Configuring Ethernet service instances on BEBs

For a BEB to identify VLANs that must be extended across sites, you must configure Ethernet service instances on its customer network ports to map VLANs to SPB VSIs.

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


[NOTE: ]

NOTE:

The outer VLAN refers to the C-VLAN for a single-tagged frame and the S-VLAN for a double-tagged frame.


For more information about Ethernet service instance configuration commands, see VPLS commands in MPLS Command Reference.

To configure an Ethernet service instance on a customer network port:

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Enter Layer 2 Ethernet interface view or Layer 2 aggregate interface view.

interface interface-type interface-number

N/A

3. Configure the port link type.

port link-type { access | trunk | hybrid }

The default port link type is access.

4. Assign the port to VLANs.

  • Access link type:
    port
    access vlan vlan-id

  • Trunk link type:
    port trunk permit vlan
    { vlan-id-list | all }

  • Hybrid link type:
    p
    ort hybrid vlan vlan-id-list { tagged | untagged }

N/A

5. Create an Ethernet service instance and enter its view.

service-instance instance-id

By default, no Ethernet service instances exist.

6. Configure a frame match criterion.

  • encapsulation s-vid vlan-id [ only-tagged ]

  • encapsulation s-vid vlan-id-list

  • encapsulation { default | tagged | untagged }

Use one of the commands to configure a frame match criterion.

By default, an Ethernet service instance does not contain a frame match criterion.

7. Map the Ethernet service instance to the SPB VSI.

xconnect vsi vsi-name [ access-mode { ethernet | vlan } ] *

By default, an Ethernet service instance is not mapped to any SPB VSI.

VLAN access mode is not supported by Ethernet service instances that use the default, tagged, untagged, or s-vid vlan-id-list criterion.