At the moment I can't test it. Tomorrow I will let you know. Thanks to all for the suggestion of the "vlan-tags" solution.
2013/11/7 Per Granath <[email protected]> > Not clear what you want to do, although it looks like "family inet"..., > but would this work? > > # show interfaces ge-1/1/0 > flexible-vlan-tagging; > encapsulation flexible-ethernet-services; > unit 2 { > vlan-tags outer 3001 inner 2; > family inet { > address 1.1.1.1/31; > } > } > > > -----Original Message----- > From: juniper-nsp [mailto:[email protected]] On Behalf > Of Massimo Ravizza > Sent: Thursday, November 07, 2013 4:51 PM > To: [email protected] > Subject: [j-nsp] QinQ on MX5 > > Hi, > I need to connect an interface of an EX2200 with an MX5. On this interface > I do QinQ: > > set interfaces ge-0/1/1 unit 0 family ethernet-switching port-mode trunk > --> interface to MX > set interfaces vlan unit 2 family inet address X.X.X.X set vlans svlan1 > vlan-id 3001 set vlans svlan1 interface ge-0/1/1.0 set vlans svlan1 > dot1q-tunneling customer-vlans 2 set vlans svlan1 dot1q-tunneling > customer-vlans 10 set vlans svlan1 dot1q-tunneling customer-vlans 20 set > vlans vlan2 description Management set vlans vlan2 vlan-id 2 set vlans > vlan2 l3-interface vlan.2 > > On MX side, this kind of configuration is not possible. I tried to use > vlan-map, but MX doen't like it: > > > > [edit interfaces] > + ge-1/1/5 { > + vlan-tagging; > + mtu 9192; > + encapsulation flexible-ethernet-services; > + unit 2 { > + description MANAGEMENT; > + vlan-id 2; > + input-vlan-map pop; > + output-vlan-map { > + push; > + tag-protocol-id 0x8100; > + vlan-id 3001; > + } > + family inet { > + mtu 1500; > + address X.X.X.X; > + } > + } > + unit 401 { > + description "VLAN DATI"; > + vlan-id 401; > + input-vlan-map pop; > + output-vlan-map { > + push; > + tag-protocol-id 0x8100; > + vlan-id 3002; > + } > + family inet { > + mtu 1500; > + address X.X.X.X; > + } > + family mpls; > + } > + unit 402 { > + description "VLAN INTERNET"; > + vlan-id 402; > + input-vlan-map pop; > + output-vlan-map { > + push; > + tag-protocol-id 0x8100; > + vlan-id 3002; > + } > + family inet { > + mtu 1500; > + address X.X.X.X; > + } > + family mpls; > + } > + } > + vlan { > + unit 2 { > + family inet { > + address X.X.X.X; > + } > + } > + } > > [edit] > # commit check > [edit interfaces ge-1/1/5] > 'unit 2' > vlan map ge-1/1/5: input-vlan-map or output-vlan-map can only be > specified in vlan-ccc, extended-vlan-ccc, vlan-vpls or extended-vlan-vpls > encapsulations > error: configuration check-out failed > > Do you have some suggestion? > Thanks > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
