Networking

Omnicube Virtual Controller - (Startup) Booting systems without Full Network configuration

 
330_IT
Occasional Contributor

Omnicube Virtual Controller - (Startup) Booting systems without Full Network configuration

Our organization has a vSphere environment with two ESXi hosts, with one OVC VM on each host.  ESXi host 1's OVC VM boots the system without the full network configuration; ESXi 2's OVC VM boots properly.  Subsequently, I'm unable to access the SimpliVity datastore VM's vmdk files to register VM's in ESXi admin portal (they don't show at all in the parent folder).

How can I get the full network configuration to load?  

3 REPLIES 3
gustenar
HPE Pro

Re: Omnicube Virtual Controller - (Startup) Booting systems without Full Network configuration

The OmniStack controllers have three networks, which one is not showing up if you look at the OVC configuration? Have you checked that all NIC cards are responding in the node? Let me know if you still have issues. 

I am an HPE employee
Accept or Kudo
330_IT
Occasional Contributor

Re: Omnicube Virtual Controller - (Startup) Booting systems without Full Network configura

So, the problematic OVC's eth2 (storage) is down:

eth2: <BROADCAST,MULTICAST> mtu 9000 qdisc mq state DOWN group default qlen 1000

I ran the ifup eth2 command, but I got the output below:

svtcli@omnicube-ip200-17:~$ ifup eth2

ifup: failed to open lockfile /run/network/ifstate.eth2: Permission denied

Any thoughts?

330_IT
Occasional Contributor

Re: Omnicube Virtual Controller - (Startup) Booting systems without Full Network configura

Here's the output from the problematic OVC:

tail -f $SVTLOG

2021-09-02T04:03:07.407Z WARN  0x7fe4de27f700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4ddc73700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4de687700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4ddef8700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4ddd75700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4df728700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4dfa2e700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.407Z WARN  0x7fe4de504700 [:] [storage.stgmgr.aiocommon] aioCommon.cpp:296 io_getevents returned 0 with 1 submitted with 10 sec 0 ns timeout

2021-09-02T04:03:07.831Z INFO  0x7fe511047700 [:] [storage.iocontext] ioContextList.cpp:86 Wrote nostart file to '/var/svtfs/0/nostart'.

2021-09-02T04:03:07.831Z FATAL 0x7fe511047700 [:] [abort] assert.cpp:26 /home/svtbuild/jenkins/workspace/svt-datapath/projects/storage/src/storage/cpp/stgmgr/ioContextList.cpp:96:failFast: Call to io_queue_release timed out after 60 seconds.