L2circuit is down due to Vlan-id mismatch between MX-80 routers

I have configured L2circuit between MX-80 routers, the vc-id on both routers are same but the vlan-id is different. Duw to vlan-id mismatch the L2circuit is not coming up. Is there any options to rewrite the vlan-id??

Or another option is to try and swap the vlan-id on input and output on PE-2:

PE-2

unit 556 { encapsulation vlan-ccc; vlan-id 556;

input-vlan-map { swap; vlan-id 557; }

output-vlan-map { swap; vlan-id 556; }

One of those options should work. I have used a config like this on M320, but i have not tested on MX80, hopefully it will work.

When you have vlans configured with l2circuit the router will send a 'requested VLAN-ID' TLV in the LDP messaging. But when you configure an output map it will disable the vlan-id request, and if the router receives a vlan-id request from a another PE it will check ithe input vlan map to see if it matches.

The last resort is to use a hidden command to disable the vlan-id validation, but using that will most likely move the issue, with your l2circuit up but not able to forward traffic because the vlans are not correct.

Re: L2circuit is down due to Vlan-id mismatch between MX-80 routers

In JNCIE study guide by Harry Reynolds page 773. it is mentioned that The configuration and verification of translational cross connect (TCC), which is also known as “Layer 2.5 IP-Only Interworking,” was not demonstrated in the chapter body. TCC is supported in CCC, draft-Kompella, and draft-Martini based VPNs to allow for interworking between dissimilar access technologies (or differing VLAN IDs, which are normally required to be the same at both ends of a L2 VPN).

I didn't try before but it might solve your problem

note: interface in this case support either family inet or tcc it couldn't support both families.