<div dir="auto">Hey Bryan,</div><div dir="auto"><br></div><div dir="auto">Have you already looked through the flexencap TOI?</div><div dir="auto"><br></div><div dir="auto"><div><a href="https://www.arista.com/en/support/toi/eos-4-24-2f/14551-flexible-interface-encapsulation-flexencap">https://www.arista.com/en/support/toi/eos-4-24-2f/14551-flexible-interface-encapsulation-flexencap</a></div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, May 10, 2024 at 09:19 Bryan Holloway via arista-nsp <<a href="mailto:arista-nsp@puck.nether.net">arista-nsp@puck.nether.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">So in Cisco (IOSXR)-land, it's trivial to terminate double-tagged <br>
traffic on an SVI like so:<br>
<br>
interface Bundle-Ether3.900<br>
ipv4 address 10.11.12.13 255.255.255.252<br>
encapsulation dot1q 900 second-dot1q 100<br>
<br>
... where 900 is the outer-tag, and 100 is the inner-tag.<br>
<br>
I've been trying to figure out a way to do this on Arista.<br>
<br>
Since there's no built-in way to do it on standard SVIs, I thought I'd <br>
take a look at their double-tag VLAN translation feature, which looks <br>
like it'll do the trick.<br>
<br>
So I created the following:<br>
<br>
interface Ethernet49/1<br>
switchport trunk allowed vlan 900<br>
switchport mode trunk<br>
switchport vlan translation 900 inner 100 200<br>
<br>
... which purports to dump double-tagged 900:100 traffic into the VLAN <br>
200 bridge domain.<br>
<br>
To wit:<br>
<br>
"On ingress, specified double-tagged packets are mapped to the bridging <br>
VLAN, and on egress packets with the ID of the bridging VLAN are double <br>
tagged as specified."<br>
<br>
So I created VLAN 200 and an SVI:<br>
<br>
interface Vlan200<br>
ip address <a href="http://10.11.12.14/30" rel="noreferrer" target="_blank">10.11.12.14/30</a><br>
<br>
But it doesn't work. Notably, the SVI doesn't even come up because there <br>
are no interfaces using VLAN 200.<br>
<br>
Fine ... so I added 200 to another unrelated trunk, which caused my <br>
VLAN200 interface to come up.<br>
<br>
But still no joy. I know this is a bit kludge-y, but shouldn't it work <br>
as advertised?<br>
<br>
Has anyone succeeded in something like this? I'm open to suggestions, <br>
thank you!<br>
<br>
- bryan<br>
<br>
P.S.: Running 4.25.4M on the Arista, which is admittedly a little long <br>
in the tooth.<br>
-- <br>
arista-nsp mailing list<br>
<a href="mailto:arista-nsp@puck.nether.net" target="_blank">arista-nsp@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/arista-nsp" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/arista-nsp</a><br>
</blockquote></div></div>