Discussion:
[j-nsp] EX4200/EX4550 VLAN translation
Mike Williams
2018-07-06 13:50:56 UTC
Permalink
Hey all,

So this is a new thing, to us at least.
We've got a need to transport some VLANs across a switch, without the
intermediary seeing them, and we're confused.
I was hoping someone could show us the light.

We have 3 EX VCs
VC1 2xEX4200
VC2 2xEX4200+2xEX4550
VC3 2xEX4550
where VC1 is connected to the EX4200s of VC2, and the EX4550s of VC2 are
connected to VC3.
VC2 to VC3 is already carrying tagged VLANs.
We need to get VLANs 128-137 from VC1 to VC3.
VC2 is already using VLANs in that range so we can't simply switch them
across.

I know about .1q tunnelling, what I don't know is how to remove the S-VLAN.
pop isn't an option in "vlans <blah> interface <foo> <int> mapping", and JUNOS
doesn't want to accept swap on a trunk interface (VC2 to VC3 is a trunk port).

Help?


Thanks
--
Mike Williams


_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Ross Halliday
2018-07-06 15:04:03 UTC
Permalink
I've never done VLAN rewriting on an EX but I can help with the tunnelling part.

SVLAN is configured like so:



ex4200 > show configuration groups TLS-L2PT
vlans {
<*> {
dot1q-tunneling {
customer-vlans [ native 1-4094 ];
layer2-protocol-tunneling {
all;
}
}
}
}

ex4200> show configuration vlans TLS-SomeplaceSomewhere
apply-groups TLS-L2PT;
vlan-id 2900;

ex4200> show configuration interfaces ge-2/0/45
mtu 9192;
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members 2900;
}
}
}



Even though the port is "access" it inhales everything that comes into it, not just untagged frames. Beyond that it is simply treated like any other tagged VLAN. This circuit passes through an MX and then some Ciena & Alcatel gear before getting to an EX3300 with nearly identical configuration as above.

Cheers
Ross




-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-***@puck.nether.net] On Behalf Of Mike Williams
Sent: Friday, July 06, 2018 9:51 AM
To: juniper-***@puck.nether.net
Subject: [j-nsp] EX4200/EX4550 VLAN translation

Hey all,

So this is a new thing, to us at least.
We've got a need to transport some VLANs across a switch, without the
intermediary seeing them, and we're confused.
I was hoping someone could show us the light.

We have 3 EX VCs
VC1 2xEX4200
VC2 2xEX4200+2xEX4550
VC3 2xEX4550
where VC1 is connected to the EX4200s of VC2, and the EX4550s of VC2 are
connected to VC3.
VC2 to VC3 is already carrying tagged VLANs.
We need to get VLANs 128-137 from VC1 to VC3.
VC2 is already using VLANs in that range so we can't simply switch them
across.

I know about .1q tunnelling, what I don't know is how to remove the S-VLAN.
pop isn't an option in "vlans <blah> interface <foo> <int> mapping", and JUNOS
doesn't want to accept swap on a trunk interface (VC2 to VC3 is a trunk port).

Help?


Thanks
--
Mike Williams


_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Jed Laundry
2018-07-09 23:36:58 UTC
Permalink
Hi Mike,

On an EX4550 running 14.1x53, I have a trunk interface with VLAN
translation as per below.

Three hints:

- you have to specify all the membership config under the vlan stanzas, you
can't have anything in the aeX.0 vlan members
- in 12.2, if you swapped a single VLAN on a trunk, you had to swap them
all. I never re-tested if this was resolved.
- I'm running 14.1 because I found a bug in 15.1 and later 12.3 releases
that prevented ARP replies on swapped VLANs from reaching an IRB interface
(PR1342432). This was resolved in 15.1R7, but I haven't had time to test
that release yet.

interfaces {
ae0 {
unit 0 {
family ethernet-switching;
}
}
}

vlans {
vlan-lan {
vlan-id 100;
interface {
ae0.0 {
mapping {
200 {
swap;
}
}
}
}
}
}

Thanks,
Jed.
Post by Mike Williams
Hey all,
So this is a new thing, to us at least.
We've got a need to transport some VLANs across a switch, without the
intermediary seeing them, and we're confused.
I was hoping someone could show us the light.
We have 3 EX VCs
VC1 2xEX4200
VC2 2xEX4200+2xEX4550
VC3 2xEX4550
where VC1 is connected to the EX4200s of VC2, and the EX4550s of VC2 are
connected to VC3.
VC2 to VC3 is already carrying tagged VLANs.
We need to get VLANs 128-137 from VC1 to VC3.
VC2 is already using VLANs in that range so we can't simply switch them
across.
I know about .1q tunnelling, what I don't know is how to remove the S-VLAN.
pop isn't an option in "vlans <blah> interface <foo> <int> mapping", and JUNOS
doesn't want to accept swap on a trunk interface (VC2 to VC3 is a trunk port).
Help?
Thanks
--
Mike Williams
_______________________________________________
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list juniper-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Loading...