[j-nsp] l2vpn tagged PE port to untagged PE port

[David Ball]

  For what it's worth, that may have eventually worked as well.  You'd need
to reverse your maps a bit by doing a 'push' on input and a 'pop' on output
(at the untagged side), and in that case both RI encapsulations would need
to be ethernet-vlan.  Accomplishes the same thing, but perhaps a little
less intuitive.

David

On 3 April 2012 11:27, Paul Stewart <paul at paulstewart.org> wrote:

> Thanks David… I went back and checked… ummm… had the VLAN maps on the
> opposite side (geesh!)****
>
> ** **
>
> Appreciate the second set of eyes…. ;)****
>
> ** **
>
> Paul****
>
> ** **
>
> ** **
>
> *From:* David Ball [mailto:davidtball at gmail.com]
> *Sent:* April-03-12 10:45 AM
> *To:* Paul Stewart
> *Cc:* juniper-nsp at puck.nether.net
> *Subject:* Re: [j-nsp] l2vpn tagged PE port to untagged PE port****
>
> ** **
>
>   Simply applying an 'input-vlan-map pop' and 'output-vlan-map push' on
> the trunked port (ge-1/3/9) didn't do the job ?  I used to have to do that
> all the time and don't recall encountering problems.  The routing-instance
> encapsulation will need to be 'ethernet' on both sides once you do that.**
> **
>
> ** **
>
> David****
>
> ** **
>
> On 3 April 2012 09:23, Paul Stewart <paul at paulstewart.org> wrote:****
>
> Hi folks.
>
>
>
> Have built an l2vpn session but ran into an issue.  One side of the session
> is handed off on a trunked port:
>
>
>
> [edit interfaces ge-1/3/9]
>
> flexible-vlan-tagging;
>
> speed 100m;
>
> encapsulation flexible-ethernet-services;
>
> }
>
> unit 444 {
>
>    description "OTA Testing";
>
>    encapsulation vlan-ccc;
>
>    vlan-id 444;
>
> }
>
>
>
> The routing instance looks like this:
>
>
>
> [edit routing-instances OTA-Testing]
>
> instance-type l2vpn;
>
> interface ge-1/3/9.444;
>
> route-distinguisher xx.xx.xxx.71:444;
>
> vrf-target target:11666:9444;
>
> protocols {
>
>    l2vpn {
>
>        encapsulation-type ethernet-vlan;
>
>        interface ge-1/3/9.444;
>
>        site dis1.millbrook1 {
>
>            site-identifier 71;
>
>            interface ge-1/3/9.444 {
>
>                remote-site-id 59;
>
>            }
>
>        }
>
>    }
>
> }
>
>
>
>
>
> The other end though has an untagged port (straight Ethernet).  I cannot
> figure out how to hand this off and keep getting an encapsulation mismatch
> on the l2vpn session?
>
>
>
> {master}[edit interfaces ge-2/1/3]
>
> speed 100m;
>
> link-mode full-duplex;
>
> encapsulation ethernet-ccc;
>
> unit 0;
>
>
>
> Routing instance:
>
>
>
> {master}[edit routing-instances OTA_Testing]
>
> instance-type l2vpn;
>
> interface ge-2/1/3.0;
>
> route-distinguisher xx.xx.xxx.xx:444;
>
> vrf-target target:11666:9444;
>
> protocols {
>
>    l2vpn {
>
>        encapsulation-type ethernet;
>
>        interface ge-2/1/3.0;
>
>        site core1.toronto1 {
>
>            site-identifier 59;
>
>            interface ge-2/1/3.0 {
>
>                remote-site-id 71;
>
>            }
>
>        }
>
>    }
>
> }
>
>
>
>
>
> I contacted JTAC and they suggested a VLAN map to pop and push. this didn't
> work . I previously had this labbed up and can't find my notes ;)
>
>
>
> Layer-2 VPN connections:
>
>
>
> Instance: OTA_Testing
>
>  Local site: core1.toronto1 (59)
>
>    connection-site           Type  St     Time last up          # Up trans
>
>    71                        rmt   EM
>
>
>
>
>
> Any thoughts on how I can fix this?
>
>
>
> Appreciate it,
>
> Paul
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp****
>
> ** **
>