Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring EVPN VLAN-Aware Bundle Service

An Ethernet VPN (EVPN) VLAN-aware bundle service configured within an EVPN instance (EVI) provides a many-to-one mapping of VLAN IDs. The MAC-VRF instance corresponding to the EVI maintains a unique bridge table for each VLAN ID, and unique labels for each bridge domain.

Configure a Layer 2 interface with VLAN-aware bundle service support.

  1. Configure the interface with flexible-vlan-tagging.
  2. Configure the interface with flexible-ethernet-services encapsulation.
  3. Configure the interface to support the first VLAN.
  4. Configure the interface to support an additional VLAN.
  5. Configure a MAC-VRF routing-instance.
  6. Configure the EVPN protocol with MPLS encapsulation.
  7. Configure the vlan-aware service-type.
  8. Configure a route-distinguisher.
  9. Configure a vrf-target.
  10. Configure VLANs within the routing-instance.
    Note:

    You must configure set protocols evpn esi-resolution-per-bridge-domain on a Junos OS based device to interoperate with an ACX device running Junos OS Evolved, when both are configured with VLAN-aware bundle service. This statement is the default behavior on ACX devices.

    Note:

    Junos OS based devices support either the label-allocation-per-instance model, or the label-allocation-per-bridge-domain model. ACX devices only support label-allocation-per-bridge-domain. See label-allocation for more details on each model. label-allocation-per-bridge-domain is the default behavior on ACX devices and does not need explicit configuration.