Page 1 of 1

NXOS 9K v - unable to start node (logs attached)

Posted: Mon Nov 27, 2017 11:46 pm
by tilpheck
Hi there,

I'm running eve-ng on an ESXI host, all other nodes start fine but this NXOS9K I am trying to start will not..
Here is the tail of /var/log/syslog:


Nov 28 01:45:00 eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_1_7
Nov 28 01:45:00 eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_1_7
Nov 28 01:45:00 eve-ng systemd-udevd[8143]: Could not generate persistent MAC address for vunl0_1_7: No such file or directory
Nov 28 01:45:00 eve-ng kernel: [ 469.579439] IPv6: ADDRCONF(NETDEV_UP): vunl0_1_7: link is not ready
Nov 28 01:45:01 eve-ng kernel: [ 469.780734] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_0: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.780934] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_1: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.781112] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_2: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.781259] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_3: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.781414] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_4: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.781554] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_5: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.781697] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_6: link becomes ready
Nov 28 01:45:01 eve-ng kernel: [ 469.781841] IPv6: ADDRCONF(NETDEV_CHANGE): vunl0_1_7: link becomes ready


Any ideas?

Thanks!
Phil

Re: NXOS 9K v - unable to start node (logs attached)

Posted: Tue Nov 28, 2017 10:29 am
by Uldis (UD)
First Phil
Please send some info about your CPU model, how much CPU assigned for EVE VM as well RAM
CPU model is a must to know.
Next check if your Intel VT-x is enabled

give this command on cli:
kvm-ok

Nexus nodes are very heavy, need time to boot as well.

UD

Re: NXOS 9K v - unable to start node (logs attached)

Posted: Tue Nov 28, 2017 3:58 pm
by tilpheck
This one is on me; I didn't upgrade to the latest version (86) before attempting to run the recommended NXOSv image.
After upgrading to v86 it works perfectly.