Troubleshooting Guide for vServer Creation Issues In Exalogic Virtual Environments
(Doc ID 2104906.1)
Last updated on NOVEMBER 14, 2022
Applies to:
Oracle Exalogic Elastic Cloud Software - Version 2.0.4.0.0 and laterLinux x86-64
Oracle Virtual Server x86-64
Goal
This document describes how to troubleshoot vServer creation issues occurring in EMOC on Exalogic virtual environments.
It provides details on data that has to be collected when such issues are seen, as well and references to other MOS notes detailing the most common vServer creation problems.
Solution
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
Goal |
Solution |
Validate & Restart Control Stack and Enable vServer Placement EMOC Debug Flags |
Validate & Restart Control Stack |
Enable vServer Placement Debug Flags |
vServer failures due to lack of available resources on Dom0 Compute Nodes |
Validate free memory available on the Dom0 compute Nodes |
Validate free vCPU's available on the Dom0 Compute Nodes |
Validate if there are any discrepancies in available resources shown on Dom0 Compute Nodes & EMOC. |
Reference MOS Notes related to issue of unable to create vServer due to lack of available resources |
vServer Creation Issues Due to OVS services not running properly. |
xend service validation |
ovs-agent service validation |
o2cb service validation |
ocfs2 validation |
vServer Creation Failure Due to Compute Nodes Assets Status Shown as Unhealthy in EMOC and OVMM |
Reference MOS Notes related to issue of unable to create vServer due to problem of EMOC Domain model/OVM |
vServer creation failure due to template corruption or incorrect template usage |
Reference MOS Notes related to Template corruption or Incorrect template usage |
vServer creation failure due to specific network or issues on IB Switches |
Reference MOS Notes related to vServer creation issues due to specific networks/IB Switches |
Collect Full Exalogs |
References |