After Planned Server Restart Exalytics OVM Failing With Errors: "bond1.340 on EXALOVS4 is locked, description: Start Virtual Machine"
(Doc ID 1961148.1)
Last updated on FEBRUARY 03, 2020
Applies to:Oracle Exalytics Software - Version 126.96.36.199.0 and later
Exalytics In-Memory Machine X3-4 - Version All Versions and later
Linux OS - Version Oracle Linux 5.5 and later
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
Exalytics machine with four Oracle Virtual Machines (OVM) was gracefully shut down as part of a planned outage. After restarting the machine, three of the VM's start successfully, but the fourth one fails to start.
It starts to load, but then fails with error like:
**** DISCLAIMER ****
Any IP addresses, Hostnames, Images, Sample outputs or other details used in this Knowledge Document are just the fictitious samples for better illustration of the problem type, goal, symptoms, and cause and solution steps.
Some of these example references can be found in following Oracle documentation links as well.
Exalytics In-Memory Machine Installation and Administration Guide for
Exalytics In-Memory Machine Owner's Guide:
Any Users ("admin", "root", "ilom-admin" etc.) listed in this knowledge document are the standard Product related users responsible for usage, management, administration tasks of Product and these users are common
in all the environments and not specific to any Customer. In the same way any Product tools/installation/logs directory structures (/opt, /usr, /root, /etc, /var/log/, /OVS/Repositories etc.) listed in this
knowledge document are standard Product directory structures which are common in all the environments.
** Any similarity to actual Customer deployments to any examples listed in the Knowledge Document is purely coincidental and not intended in any manner. **
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document