- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Omnicube Virtual Controller - (Startup) Booting sy...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-19-2021 10:25 AM - last edited on 09-10-2021 05:30 AM by support_s
08-19-2021 10:25 AM - last edited on 09-10-2021 05:30 AM by support_s
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-08-2021 05:00 AM
09-08-2021 05:00 AM
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 work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2021 09:31 AM
09-15-2021 09:31 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-15-2021 10:17 AM
09-15-2021 10:17 AM
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.