Support and News Forum

Greetings,

ESXi 6.5 / Supermicro hardware / eve-ng 2.0.3-92 / E5-2630L @2.00GHz

Spent many hours across a couple of sessions and 2 complete re-deployments of the OVA trying to figure this one out. Trying to add first router node. Node fails to start (red text) or sometimes says it starts but doesn't turn the icon to blue and telneting to assigned ip/port combo doesn't work. Tailing unl_wrapper.txt shows the Cisco IOL image appears to start and I also tested by launching an image manually from cmd line.

Tailing the syslog is a bit revealing as currently I'm getting:

Jul 25 08:32:07 eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_1_32
Jul 25 08:32:07 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_1_32
Jul 25 08:32:07 eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_1_48
Jul 25 08:32:07 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_1_48
Jul 25 08:32:08 eve-ng kernel: [ 698.802213] pnet0: port 2(vunl0_1_0) entered disabled state

I've verified nested virtualization is enabled and that promiscuous mode is enabled on the vswitch and port group.. Run the permissions fix many times, rebooted, etc.

Initially had some errors that may have been related regarding lack of ability to create persistent mac but don't see those now.

Don't think I missed anything in the docs but since everyone else seems to get this running on ESXi, maybe I did but I sure can't find it.

Thanks for pointing me in a productive direction as I'm completely stumped at this point.

Here's the output of the support script: (I do find it odd that my mac addr for pnet1 is all 0's??)

root@eve-ng:~# ./evenginfo.sh
***** EVE-NG INFORMATION TOOL - CREATED BY R! ******
Wed Jul 25 08:28:08 EEST 2018

***** EVE-NG VERSION INSTALLED *****
eve-ng 2.0.3-92

***** HOSTNAME INFORMATION *****
Static hostname: eve-ng
Virtualization: vmware
Operating System: Ubuntu 16.04.5 LTS
Kernel: Linux 4.9.40-eve-ng-ukms-2+
Architecture: x86-64

***** FILE SYSTEM DISK SPACE USAGE *****
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 799M 14M 785M 2% /run
/dev/mapper/eve--ng--vg-root 31G 2.9G 27G 10% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sda1 472M 83M 365M 19% /boot

***** CPU INFORMATION *****
model name : Intel(R) Xeon(R) CPU E5-2630L 0 @ 2.00GHz

***** FREE AND USED MEMORY *****
total used free shared buff/cache available
Mem: 7.8G 387M 7.1G 24M 282M 7.1G
Swap: 8.0G 0B 8.0G

***** INTERFACE INFORMATION *****
pnet0 8000.000c298efac8 no eth0
pnet1 8000.000000000000 no
pnet2 8000.000000000000 no
pnet3 8000.000000000000 no
pnet4 8000.000000000000 no
pnet5 8000.000000000000 no
pnet6 8000.000000000000 no
pnet7 8000.000000000000 no
pnet8 8000.000000000000 no
pnet9 8000.000000000000 no

***** KVM CHECK INFORMATION *****
INFO: /dev/kvm exists
KVM acceleration can be used

***** APACHE STATUS *****
* apache2.service - LSB: Apache2 web server
Active: active (running) since Wed 2018-07-25 08:20:51 EEST; 7min ago

***** CHECKING INERNET STATUS *****
PING www.google.com (216.58.192.196) 56(84) bytes of data.
64 bytes from ord30s25-in-f196.1e100.net (216.58.192.196): icmp_seq=1 ttl=50 time=19.5 ms

--- www.google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 19.538/19.538/19.538/0.000 ms

Following up on this.. My 'could not generate persistent MAC address for vun10_1_0, .._16 .._32 and .._48' error messages have returned. I had tried a fix by adding a 99-default.link to /etc/systemd/network to turn off and on persistent as well as the switch to tell systemd to evaluate virtual environment. None of those seemed to help so I removed them and back to the original could not generate persistent mac - no such file or directory errors.

Thanks.

Resolved.. After several re-deployments of the OVA and much log surfing, I finally tripped across the wrapper.tx in the temp folder indicating the absence of IOURC. It was in place in $HOME in both IOURC and .IOURC format as well as in the folder with the BINs.

Drove me nuts. The L3 15.x.2 that showed to be supported that I had would start in standalone mode outside of eve so I thought it was good. However, as a hail Mary, I grabbed the .1 variant and bang, right away I could deploy and start a node.

Extremely frustrating as the errors in the syslog that I reported here have zero indication of the true problem.. Around 10 hrs wasted so I truly hope someone else finds this and helps. Before you spend a bunch of time, simply try several different supported images, even if what you have seems to start ok standalone..