[j-nsp] MX: bridge-domains and l2circuit

[Chris Kawchuk]

You'll need to declare your xe- port with flexible-ethernet-services, so you can do per-unit encapsulations.

interfaces {
    xe-1/0/0 {
        vlan-tagging;
        encapsulation flexible-ethernet-services;
        unit 20 {
            encapsulation vlan-ccc;
            vlan-id 20;
        }
        unit 100 {
            encapsulation vlan-bridge;
            vlan-id 100;
        }
    }
}

neighbor xxx {
   interface xe-1/0/0.20 {
       virtual-circuit-id 20;
       ...
       ...
    }
}



On 2011-08-18, at 4:03 PM, Jonas Frey (Probe Networks) wrote:

> Hello all,
> 
> i am trying to build a l2circuit on a MX. The problem is that the vlan
> that needs to be included in the l2circuit comes via xe-1/0/0 which is
> configured in bridge mode:
> unit 0 {
>    family bridge {
>        interface-mode trunk;
>        vlan-id-list [ 20 30 40 ];
>    }
> 
> I need to build this l2circuit with vlan 20.
> 
> However when configuring the l2circuit i do not have a interface to use
> as the bridge doesnt create any subinterface for the vlan.
> 
> neighbor xxx {
>    interface ??? {
>        virtual-circuit-id 20;
> 
> 
> I cant configure any subinterface on xe-1/0/0 (like unit 1....) because
> bridge mode prohibits that. 
> 
> How can i get this to work?
> 
> Best regards,
> Jonas
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp