AOS-CX Switch Simulator

Dear all,

with the above described setup I cannot get to work private VLANs as expected.

The most basic setup possible: one Primary PVLAN, one Secondary PVLAN depending on it, isolated type.

All comands regarding private VLANS apparently work, but then traffic between 3 test VPCs connected to the simulated switch do not work as expected.

Are PVLANs supported at all in that AOS-CX image?

Thank you in advance.

Regards

G

Hello,

thank you for your answer, but my setup must be much simpler, the simplest possible.

See following diagram:

Think of two hosts which must not see each other (VPC2 and VPC3) but both at the same time must see the router (VPC1).

I cannot figure out how to configure interface1/1/1 so that ping from VPC2 or VPC3 to VPC1 works.

VPC1 is configured as 192.168.1.1/24

VPC2 is configured as 192.168.1.2/24

VPC3 is configured as 192.168.1.3/24

What you see in the screenshot is the closest that I can do according to examples, other vendors' configurations, and Aruba documentation, but clearly is wrong.

Ping from VPC2 to VPC3 si correctly dropped since they are both on Isolate Private VLAN, and that's what I expect.

Thanks

G

Hi, I find connecting VPC's and other "clients" to the Aruba CX switches in EVE-NG to be unstable and unpredictable. I think I give up EVE-NG and convert to containerlabs.

Thank you Arne for your reply.

Did you manage to have the AOS-CX simulator PVLANS working in Containerlabs? If yes, on which AOS-CX simulator version?

Much better if anyone could come up with either one of the following statements:

1 - Yes, PVLANS are supported in AOS-CX simulator version 10.xx, so if they do not work it is you Lab system capabilities fault

2 - No, PVLANS are not supported in AOS-CX simulator version 10.xx, so give up trying because they will never work despite how good is your Lab system (EVE-NG community, EVE-NG pro, Containerlab, GNS3, whatever)

Thanks

G

Hi,

I have not tried Private VLAN in simulator in EVE-NG or in Containerlabs. Perhaps the feature need support from the hardware chip - so it can't work in the simulator.

My usage of the simulator is mostly related to testing my Ansible automation stuff, and EVPN-VXLAN dataplane does not work, STP does not work (does not discard TX on interfaces in blocking), ACL does not work, firmware does not work, reboot command does not point to image. It's a lot of things not working - but I love it for testing my code ;-)

The simulator running in Containerlabs will not be configured by Ansible over API for some reason. 

Making the functionality closer to the real thing would make things easier to test, when it comes to automation. The cost of lab equipment it not small when it comes to testing fabrics with active gateway IPv4 and IPv6 etc. Also do PoC with customers etc.

I don't have time to test private-vlan now, but I will keep both EVE-NG Pro and Containerlabs in addition to my physical lab. And do my dataplane testing mostly in the physical lab.