Маршрутизаторы серии ME поддерживают различные способы построения сервисов L2VPN. Ниже приведен пример конфигурации L2VPN сервиса построенного на базе VPLS BGP Auto Discovery.
Для наглядности взят пример стыковки оборудования ME5200 и Juniper

Порядок конфигурации сервиса

interface tengigabitethernet 0/0/16.700
encapsulation outer-vid 700
exit
l2vpn
  bridge-group vp700
    bridge-domain vp700
      autodiscovery
        bgp
          ignore mtu-mismatch
          rd 65100:700
          route-target 65100:700
            export
            import
          exit
          signaling-protocol bgp
            ve-id 3
          exit
        exit
      exit
      interface tengigabitethernet 0/0/16.700
      exit
    exit
  exit
router bgp 65100
  neighbor 1.0.0.8 
    address-family l2vpn vpls 
    exit
    local-as 65100
    remote-as 65100
    send-community 
    send-community-ext 
    update-source 1.0.0.3
  exit
exit

Аналогичная конфигурация со стороны маршрутизатора Juniper:

root@vMX-8> show configuration protocols bgp       
traceoptions {
    file bgp;
    flag general;
}
local-address 1.0.0.8;
log-updown;
local-as 65100;
group inter {
    type internal;
    local-address 1.0.0.8;
    family inet {
        unicast;
    }
    family inet-vpn {
        unicast;
    }
    family l2vpn {
        signaling;
    }
    peer-as 65100;
    local-as 65100;
    neighbor 1.0.0.3;
}

root@vMX-8> show configuration routing-instances 
vp {
    instance-type vpls;
    interface ge-0/0/1.700;
    route-distinguisher 65100:700;
    vrf-target {
        import target:65100:700;
        export target:65100:700;
    }
    protocols {
        vpls {
            ignore-mtu-mismatch
            no-tunnel-services;
            site ce1 {
                site-identifier 8;
                interface ge-0/0/1.700;
            }
        }
    }
}
root@vMX-8> show configuration interfaces ge-0/0/1                     
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 700 {
    encapsulation vlan-vpls;
    vlan-id 700;
}

Аналогичным образом создается xconnect:

interface tengigabitethernet 0/0/16.2700
encapsulation outer-vid 2700
exit
l2vpn
  xconnect-group xc_l2vpn
    p2p 2700
      autodiscovery
        bgp
          rd 65100:2700
          route-target 65100:2700
            export
            import
          exit
          signaling-protocol bgp ve-id 2700
        exit
      exit
      interface tengigabitethernet 0/0/16.2700
    exit
  exit
exit
xc_l2vpn {
    instance-type l2vpn;
    protocols {
        l2vpn {
            site tor {
                interface ge-0/0/1.2700 {
                    remote-site-id 2700;
                }
                site-identifier 18;
            }
            encapsulation-type ethernet-vlan;
            no-control-word;
        }
    }
    interface ge-0/0/1.2700;
    route-distinguisher 65100:2700;
    vrf-target {
        import target:65100:2700;
        export target:65100:2700;
    }
}


0/ME5100:R2# show  l2vpn xconnect p2p 2700 
Mon Jan 22 10:33:40 2024
  MM  -- mtu mismatch            Up -- up              GUp -- going up
  CM  -- control-word mismatch   Dn -- down            GDn -- going down
  OL  -- no outgoing label       ST -- standby         Lld -- lower layer down
  BK  -- backup connection       Fl -- failed          Drm -- dormant
  SP  -- static pseudowire       SW -- switchover
  
  Group xc_l2vpn, XC 2700, mtu 1500, state Administrative active
      
      AC: Tengigabitethernet0/0/16.2700
        AC binding status: up, Interface oper state: up
  
    List of Autodiscovery PWs:
       
      PW: Neighbor 1.0.0.8, if-index 207, admin Up, oper Up
      Status codes: 
        PW type: ethernet-tagged, signaling: bgp, local group id: 0
        Encapsulation: MPLS, control word: control-word-not-present
        Vpn index: 3, type: ws
        Redundancy state active, MTU: 1500
        Attachment id: none local, none group, none remote
        Created: 2024-01-22 10:03:45, last state change: 00h29m55s ago
        
                                                Local                     Remote
        Label                                   41                        800014
        VE id                                   2700                      18                       
        BGP RD                                  65100:2700                65100:2700              
        Forwarding                              true                      true
        Customer-facing (ingress) recv fault    false                     false
        Customer-facing (egress) send fault     false                     false
        Local PSN-facing (ingress) recv fault   false                     false
        Local PSN-facing (egress) send fault    false                     false
        Switchover                              false                     false
        Remote capabilities:
          VC status can be signaled: false
          VCCV ID can be signaled  : false
            Remote Control Channel (CC) supported: none
            Remote Connectivity Verification (CV) supported: none
        Remote node capability:
          Manually set PW: true
          Protocol has not yet finished cap. determination: false
          Signaling the pseudowire: false
          Sending the pseudowire: false

Настройка MPLS транспорта в данном примере не рассматривается