Versa / crosslink promiscuous mode

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
Richard70
Posts: 49
Joined: Sun Dec 23, 2018 9:53 am

Versa / crosslink promiscuous mode

Post by Richard70 » Mon May 31, 2021 3:44 pm

Hello,
I'have been labbing Versa Vos successfully for a few month but I have an issue with branch configured with 2 cpe in an active/active setup.
In order to get the setup work, I must configure the Xlinks on each cpe as "promiscuous" (and this is not required on real hardware cpe).
However, I suspect configuring the interfaces in promiscuous mode to introduce some weird behavior in other vos features.
Do you know how to configure EVE (or qemu ?) in order to get the crosslink work without the promiscuous mode ?
I'm using EVE Community 2.0.3.110 (and vos 20.2).
Thanks.
Rich

Richard70
Posts: 49
Joined: Sun Dec 23, 2018 9:53 am

Re: Versa / crosslink promiscuous mode

Post by Richard70 » Sat Jun 19, 2021 2:14 pm

Hi Eve team,

I think I found the culprit : the issue is due to the QEMU Nic type "virtio-net-pci" that is configured by default by the EVE template. It seems that it can't handle properly tagged frames.
When I use "vmxnet3" interface type (without changing QEMU version) that works, meaning that two crosslinked devices can ping eachothers with tagged frames.

Is there a reason to use this "virtio-net-pci" in the default template ?
Should I expect others issues if I use vmxnet3 instead ? Advice from Eve team would be highly appreciated :)
(I'm using bare metal EVE Community 2.0.3.110 / vos 20.2).
Thanks
Rich

Uldis (UD)
Posts: 3995
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Versa / crosslink promiscuous mode

Post by Uldis (UD) » Sat Jun 19, 2021 3:06 pm

First, not all versions of vendor images supporting tagged frames...
example Viptela for tagging interface need set to E1000 NIC type.
All what I can say I tested almost all Versa versions and it works,
not tested dot1q

You can change NIC type to E1000 and try

All tested on EVE PRO.
Ny Versa lab with book you can find here
https://www.eve-ng.net/index.php/lab-li ... sco-sdwan/
Uldis

Richard70
Posts: 49
Joined: Sun Dec 23, 2018 9:53 am

Re: Versa / crosslink promiscuous mode

Post by Richard70 » Sat Jun 19, 2021 3:38 pm

Hi Uldis,
all versa features I'm using are working fine, except dot1q.
I tested E1000 as you advised, and this type of interface is working fine too with dot1q (same as vmx3). But the default template's nic type "virtio" definitively does not work for dot1q.
So I understand that you advise to use E1000 (compared to vmx3) , right ?

Uldis (UD)
Posts: 3995
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Versa / crosslink promiscuous mode

Post by Uldis (UD) » Sun Jun 20, 2021 6:33 pm

Yes,
beause if image was originl KVM from Versa, t was advice to use virtio driver for NIC.
If versa is made from VMDK VM ware ten you can set it to e1000 or vmxnet3.

:) I am not Santa Claus predict such nuances :)
So you can simply bear im mind it...

Richard70
Posts: 49
Joined: Sun Dec 23, 2018 9:53 am

Re: Versa / crosslink promiscuous mode

Post by Richard70 » Mon Jun 21, 2021 4:01 pm

:lol:
Ok thank you !

Post Reply