Nexus 9k doesn't start - ovs problem ?
Posted: Thu Mar 26, 2020 2:01 pm
Hi,
We are trying to run a Nexus 9k, but we can't. We tried a couple of images to check if the image was the problem, but no luck. The images that we tested are:
nxosv9k-7.0.3.I7.1
nxosv9k-7.0.3.I7.2
nxosv9k-7.0.3.I7.4
nxosv9k-9.2.4
I issued a tail -f /var/log/syslog when I tried to start the device and this is the error:
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_0
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_0
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_1
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_1
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_2
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_2
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_3
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_3
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_4
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_4
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_5
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_5
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_6
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_6
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_7
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_7
We also tried this in VMware and Xen as a host for the ova image,
Any help will be great !
Thank you in advance !
Esteban
We are trying to run a Nexus 9k, but we can't. We tried a couple of images to check if the image was the problem, but no luck. The images that we tested are:
nxosv9k-7.0.3.I7.1
nxosv9k-7.0.3.I7.2
nxosv9k-7.0.3.I7.4
nxosv9k-9.2.4
I issued a tail -f /var/log/syslog when I tried to start the device and this is the error:
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_0
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_0
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_1
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_1
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_2
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_2
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_3
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_3
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_4
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_4
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_5
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_5
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_6
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_6
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_7
Mar 26 15:54:24 nap-eve-ng ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_7
We also tried this in VMware and Xen as a host for the ova image,
Any help will be great !
Thank you in advance !
Esteban