[j-nsp] L2 VPNs configuration

Benny Sumitro benny.sumitro at gmail.com
Mon Nov 12 01:13:20 EST 2007


Hi Eugeniu,

I think you missed remote side identifier to connect this site to
which end site it is connected. L2VPN is point to point so you must
define the remote end id.

Try this on routing instance in pe2:

protocols {
    l2vpn {
        encapsulation-type ethernet;
        site to-pe1 {
            site-identifier 2;
            interface ge-0/0/1.0 {
                remote-site-id 1;
            }
        }
    }
}

and also of course vice versa from pe1.

Let me know if its working.

Regards,
Benny


On Nov 9, 2007 10:30 PM, Eugeniu Patrascu <eugeniu.patrascu at gmail.com> wrote:
>
>  From the documentation it seems it's not going to work:
>
> http://www.juniper.net/techpubs/software/junos/junos84/swconfig84-vpns/swconfig84-vpns.pdf
>
> says the following:
>
> NOTE: A Layer 2 VPN or Layer 2 circuit is not supported if the
> PE-router-to-P-router
> interface has VLAN-tagging enabled and uses a nonenhanced Flexible PIC
> Concentrator
> (FPC).
>
>
> the FPCs in the M7i routers are E-FPC, and I presume that E stands for
> enhanced.
>
> but the PE routers are J4350 and I'm using the onboard GE ports for
> connecting, and show chasis hardware reports them as FPC and I suspect
> that this might be the problem.
>
> Thanks.
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list