virtual exos 26.1.4 - Tagged traffic not working

[Calm_Horizons]

Hi all,

Has anybody successfully got the virtual exos 26.1.4 working with tagged traffic on ESXi? Spent ages thinking it was the VM environment but it does not appear to be.

Simple test scenario:

create vlan test
config vlan test ipaddress 10.1.2.10/24
config vlan test add ports 1 tagged

create vlan test
config vlan test ipaddress 10.1.2.11/24
config vlan test add ports 1 tagged

Try and ping between them, and absolutely nothing.

ESXI Portgroup promiscious mode with vlan 4095 (all VLANS) with the virtual adapters configured as E1000.

EXOS version 22.2.15 and 16.2.1.6 works absolutely fine. Will probably try 22.5 next.

So either looks like a bug, or I'm missing something new in the latest and greatest.

Oh ESXi version 6.7.

[jeronimo]

Better late than never:
You should use GNS3 instead of ESXi. ESXi is pain for bigger labs in that it requires a vSwitch for every interface etc.
You'll have some trouble to get EXOS going in GNS3 too, but if you follow this you'll be great:

• use the GNS3 VM (install it on ESXi) and only install the client on your PC in order to control the VM
• don't use the EXOS template shipped with GNS3 but those from extremenetworks github (same for the QCOW file (the "hard disk"))
• especially don't use an intel nic but a realtek (otherwise tagged traffic doesn't work)
• the first NIC shown in the hypervisor is the MGMT port of the switch, port 1 = NIC 2 and so on (just as in ESXi)
• pausing a link in GNS3 does not make the port actually down, although traffic will - of course - not pass

GNS3 has quirks. But you should try it.

[Calm_Horizons]

No unfortunately it does not survive reboot.

show port 1 information, looks identical before and end the disable/enable command.
Before (not working):
VCORE1-U> Em------e--fMB----- active - / - 1 0 4 0 9216 none

Disabled:
VCORE1-U> Dm------e--fMB----- ready - / - 1 0 4 0 9216 none

After enable (working):
VCORE1-U> Em------e--fMB----- active - / - 2 0 4 0 9216 none

I cannot see anything in the logs after a boot that reference port 1 other than the port up that would explain the behaviour.

Also worth noting port restart also corrects the issue until the next reboot.

[Zdeněk_Pala]

I was not able to make it working. Can you confirm the port down and port up is the cure? does it survive reboot = is it working after reboot?

Thank you.

Z.

[Calm_Horizons]

And the answer is a very simple:
disable port 1
enable port 1
and voila it works.

[Calm_Horizons]

As I cannot edit a post:
Power on the new switch:
configure vlan default delete ports all
create vlan test
configure vlan test tag 100
configure vlan test add ports 1 tagged
configure vlan test ipaddress 10.1.2.10/24

On Switch2:
configure vlan default delete ports all
create vlan test
configure vlan test tag 100
configure vlan test add ports 1 tagged
configure vlan test ipaddress 10.1.2.11/24

ping 10.1.2.10

Works in versions below 22.3, not working 22.4-6 using virtual exos images from github on esx 6.7.