Additional Guest vServers Fail To Initialize Their Network Environment After 7 vServers Have Been Successfully Started On An Exalogic X5-2 Compute Node
(Doc ID 2010280.1)
Last updated on NOVEMBER 14, 2022
Applies to:
Enterprise Manager Ops Center - Version 12.1 to 12.1 [Release 12.0]Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.1 and later
Oracle VM - Version 3.2.8 to 3.2.8 [Release OVM32]
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64
Symptoms
You have an Exalogic system running Exalogic Elastic Cloud Software in a virtual deployment that contains one or more X5-2 compute nodes. After 7 Guest vServers have been started successfully and are actively running on a specific X5-2 node, you find that additional vServers created/started on that node cannot be accessed by any of the IPoIB or EoIB addresses that the vServer defines.
Within the /var/log/ovm_network.log log file of any Guest vServer newly created on the impacted compute node, the following errors are reported from the one time network configuration script that creates interface configuration files for the networks defined by the vServer:
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |