Re: [j-nsp] l2circuit (martini) vlan-mismatch
On (2013-09-19 15:16 +0100), Alex Arseniev wrote: Hi Alex, Use explicit encapsulation-type ethernet under [protocols l2circuit interface ] and You won't be seeing this mismatch. On both sides of course. Whle this needs change in A-end also, it's very good tip, and I'll try that out. Just to be precise 'output-map swap' works just fine with different SVLAN in each ends, as long as there is SVLAN. If connection is without any SVLAN and we inject SVLAN, then for some reason JunOS will report VLAN-mismatch, even though it would not matter, as far end will swap it. -- ++ytti ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] l2circuit (martini) vlan-mismatch
On (2013-09-19 10:09 +0300), Saku Ytti wrote: Now consider in B-END if some of the SVLANs need to go to the L2VPN circuit and some SVLAN needs to be locally terminated. s/SVLAN/CVLAN/g sorry about that -- ++ytti ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] l2circuit (martini) vlan-mismatch
- Original Message - From: Saku Ytti s...@ytti.fi To: juniper-nsp@puck.nether.net Everything works just fine. Only I find it really strange B-END cannot push arbitrary S-VLAN, considering A-END is going to change it anyhow. If it's not 101, A-END vill be down with 'vlan-mismatch'. Use explicit encapsulation-type ethernet under [protocols l2circuit interface ] and You won't be seeing this mismatch. On both sides of course. HTH Thanks Alex ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
