Support and News Forum

Posted: **Sun Jun 07, 2020 2:51 pm**

Hi,
first, thank you for this great product eve-ng. And thank you for all the work you already invested into this. Great job!

I run some Cumulus VX instances, they work great, except that I can only boot up instances with maximum number of 28 Interfaces.
As soon as I change the number of interfaces to 29 or higher the cumulus VX instance will not boot anymore?

Do you by chance know if this is a limitation by cumulus or by eve-ng?
I tried already to look at the logs during bootup but I didn't found any helpful information.

Sorry if I'm wrong here with my question, just let me know if there is a better way, forum, board where I should go and ask.

Best regards,
Ulf

Posted: **Mon Jun 08, 2020 6:52 am**

no limit
Cumulus pic below has 36 ports

Posted: **Mon Jun 08, 2020 1:29 pm**

Hi Uldis,

thank you for your answer.
It looks like that I did something wrong, but I have no idea where to look a the moment?

Which version do you run? Cumulus VX version and EVE-NG Version? CE or PRO?
I'm running Cumulus Version 3.7.12 and EVE-NG CE Version 2.0.3-110 (QEMU version: 2.4.0), that's the OVA Image on VMware Workstation.

I took the ova Image booted it up with vmware workstation downloaded the cumulus VX image - moved it to the destination folder as it is described in the how-to (https://www.eve-ng.net/index.php/docume ... umulus-vx/) and booted it up, and as soon as I change to more then 28 interfaces I can click start but it takes around 1 second and cumulus is off again?

I will try to reproduce it.

Best regards,
Ulf

Posted: **Mon Jun 08, 2020 4:48 pm**

add node on topology, right click edit/set 28 interface and only the start.

Posted: **Tue Jun 09, 2020 12:03 pm**

Hi Uldis,

28 works fine, all higher than 28 stops working. It even didn't start anymore.

I debugged it and as far as I can say now as soon as I add a 29's interface to this call:

Code: Select all

TAG=T0D1- /opt/qemu-2.12.0/bin/qemu-system-x86_64 -nographic -device virtio-net-pci,netdev=net0,mac=50:00:00:01:00:00 -netdev tap,id=net0,ifname=vunl0_1_0,script=no -device virtio-net-pci,netdev=net1,mac=50:00:00:01:00:01 -netdev tap,id=net1,ifname=vunl0_1_1,script=no -device virtio-net-pci,netdev=net2,mac=50:00:00:01:00:02 -netdev tap,id=net2,ifname=vunl0_1_2,script=no -device virtio-net-pci,netdev=net3,mac=50:00:00:01:00:03 -netdev tap,id=net3,ifname=vunl0_1_3,script=no -device virtio-net-pci,netdev=net4,mac=50:00:00:01:00:04 -netdev tap,id=net4,ifname=vunl0_1_4,script=no -device virtio-net-pci,netdev=net5,mac=50:00:00:01:00:05 -netdev tap,id=net5,ifname=vunl0_1_5,script=no -device virtio-net-pci,netdev=net6,mac=50:00:00:01:00:06 -netdev tap,id=net6,ifname=vunl0_1_6,script=no -device virtio-net-pci,netdev=net7,mac=50:00:00:01:00:07 -netdev tap,id=net7,ifname=vunl0_1_7,script=no -device virtio-net-pci,netdev=net8,mac=50:00:00:01:00:08 -netdev tap,id=net8,ifname=vunl0_1_8,script=no -device virtio-net-pci,netdev=net9,mac=50:00:00:01:00:09 -netdev tap,id=net9,ifname=vunl0_1_9,script=no -device virtio-net-pci,netdev=net10,mac=50:00:00:01:00:0a -netdev tap,id=net10,ifname=vunl0_1_10,script=no -device virtio-net-pci,netdev=net11,mac=50:00:00:01:00:0b -netdev tap,id=net11,ifname=vunl0_1_11,script=no -device virtio-net-pci,netdev=net12,mac=50:00:00:01:00:0c -netdev tap,id=net12,ifname=vunl0_1_12,script=no -device virtio-net-pci,netdev=net13,mac=50:00:00:01:00:0d -netdev tap,id=net13,ifname=vunl0_1_13,script=no -device virtio-net-pci,netdev=net14,mac=50:00:00:01:00:0e -netdev tap,id=net14,ifname=vunl0_1_14,script=no -device virtio-net-pci,netdev=net15,mac=50:00:00:01:00:0f -netdev tap,id=net15,ifname=vunl0_1_15,script=no -device virtio-net-pci,netdev=net16,mac=50:00:00:01:00:10 -netdev tap,id=net16,ifname=vunl0_1_16,script=no -device virtio-net-pci,netdev=net17,mac=50:00:00:01:00:11 -netdev tap,id=net17,ifname=vunl0_1_17,script=no -device virtio-net-pci,netdev=net18,mac=50:00:00:01:00:12 -netdev tap,id=net18,ifname=vunl0_1_18,script=no -device virtio-net-pci,netdev=net19,mac=50:00:00:01:00:13 -netdev tap,id=net19,ifname=vunl0_1_19,script=no -device virtio-net-pci,netdev=net20,mac=50:00:00:01:00:14 -netdev tap,id=net20,ifname=vunl0_1_20,script=no -device virtio-net-pci,netdev=net21,mac=50:00:00:01:00:15 -netdev tap,id=net21,ifname=vunl0_1_21,script=no -device virtio-net-pci,netdev=net22,mac=50:00:00:01:00:16 -netdev tap,id=net22,ifname=vunl0_1_22,script=no -device virtio-net-pci,netdev=net23,mac=50:00:00:01:00:17 -netdev tap,id=net23,ifname=vunl0_1_23,script=no -device virtio-net-pci,netdev=net24,mac=50:00:00:01:00:18 -netdev tap,id=net24,ifname=vunl0_1_24,script=no -device virtio-net-pci,netdev=net25,mac=50:00:00:01:00:19 -netdev tap,id=net25,ifname=vunl0_1_25,script=no -device virtio-net-pci,netdev=net26,mac=50:00:00:01:00:1a -netdev tap,id=net26,ifname=vunl0_1_26,script=no -device virtio-net-pci,netdev=net27,mac=50:00:00:01:00:1b -netdev tap,id=net27,ifname=vunl0_1_27,script=no -device virtio-net-pci,netdev=net28,mac=50:00:00:01:00:1c -netdev tap,id=net28,ifname=vunl0_1_28,script=no -device virtio-net-pci,netdev=net29,mac=50:00:00:01:00:1d -netdev tap,id=net29,ifname=vunl0_1_29,script=no -device virtio-net-pci,netdev=net30,mac=50:00:00:01:00:1e -netdev tap,id=net30,ifname=vunl0_1_30,script=no -device virtio-net-pci,netdev=net31,mac=50:00:00:01:00:1f -netdev tap,id=net31,ifname=vunl0_1_31,script=no -smp 1 -m 1024 -name cumulus -uuid c4a65b90-88fe-4692-bdde-3f077942bfb8 -drive file=virtioa.qcow2,if=virtio,bus=0,unit=0,cache=none -machine type=pc,accel=kvm -nographic -rtc base=utc

I get the following error:

Code: Select all

qemu-system-x86_64: -device virtio-net-pci,netdev=net29,mac=50:00:00:01:00:1d: PCI: no slot/function available for virtio-net-pci, all in use or reserved

and I can reproduce this also with linux (debian/ubuntu) if I add more then 28 Interfaces in the WebGUI the node didn't start.
As I already wrote I used the OVA installaton with VMware Workstation.

Best regards,
Ulf

Posted: **Tue Jun 09, 2020 2:20 pm**

I did with 36 worked

Posted: **Tue Jun 09, 2020 4:17 pm**

Hi Uldis,

me too and it didn't work for me, That's why I ask for your versions what you use exactly to find out what's different.

I just did it, again. I downloaded the CE OVA from here (https://mega.nz/file/4pU2wIhQ#jmfEhGMNM ... m1uRxIjYEQ) the MEGA link on https://www.eve-ng.net/index.php/download/ which shows Version 2.0.3-110.
I extracted the zipfile I downloaded.
I go to VMware Workstation 15.5.5 click on File -> Open import the extracted ova file.
Start the VM. Create a new lab. Upload the cumulus-linux-3.7.12-vx-amd64-qemu.qcow2 file into the new created dir /opt/unetlab/addons/qemu/cumulus-3.7.12 as virtioa.qcow2. /opt/unetlab/wrappers/unl_wrapper -a fixpermissions after upload.

On the WebUI I click + Add an Object - Node -> Search for Cumulus VX - change the Interfaces from 8 to 32 - Save.
Start and what happens is: I get a notification Banner where says "cumulus stated" the icon gets blue for about one second and turns back to grey and nothing happens, it's not starting.

If I change back the Interfaces to 28, Save, Start, it's starting fine and everything works.

Do you also used EVE-NG CE 2.0.3-110? Do you also use the OVA file? Do you also use VMware Workstation?

Best regards,
Ulf

Posted: **Tue Jun 09, 2020 6:43 pm**

I am using EVE-Pro 2.0.6-52

Posted: **Tue Mar 01, 2022 11:35 pm**

Hello all,

Did you guys resolve the issue? I'm having the same issue tried on arista veos and mikrotik... the node will start only if u have less than 29 interfaces..
I got eve-ng 2.0.3-112 on vmware 15

Kind regards
K

Support and News Forum

Cumulus VX interface limit?

Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?

Re: Cumulus VX interface limit?