Exalogic Virtual: OVM Network Setup Script Fails During Guest vServer Creation Due To Duplicate Exa-Admin-Fab Fabric Entries And Unexpected NetworkToFabric Associations
(Doc ID 2124170.1)
Last updated on JUNE 22, 2021
Applies to:Oracle Exalogic Elastic Cloud Software - Version 188.8.131.52.4 and later
Oracle Virtual Server x86-64
You have an Exalogic Rack configured as a Virtual deployment of Exalogic Elastic Cloud Software (EECS), where you have previously been able to create and access over the network guest vServers that are associated with one or more of the Infiniband networks defined by default (also referred to a Infrastructure Networks) and/or end user defined networks (often or referred to a Custom Networks).
However, following a restart of the Exalogic Control Stack (as could be needed after applying a patch-set or stopping and restarting Enterprise Manager OpsCenter (EMOC) related vServers around a backup taken by the ExaBR utility), the EMOC jobs for the new vServers you create complete successfully, and are still accessible via "xm console", however they are no longer accessible over the network for one or more of the network interfaces they define.
When you encounter this issue, the /var/log/ovm-netwok.log for the newly created vServers does not end with the following line:
We can see that:
- From the map of Networks defined in EMOC, the IP address 172.16.xx.xxx correlates to the IPoIB-virt-admin network which is an IPoIB rather than EoIB network
- The 172.16.xx.xxx address aligns with the ovm_network.log entry "com.oracle.linux.network.ipaddr.2 entry", which corresponds to the bond2 device for the guest vServer and correlates to the com.oracle.linux.network.slaveset.2 entry in the same log
- The com.oracle.linux.network.slaveset.2 entry is listed in the ovm_network.log file as an EoIB rather than an IPoIB network, which is unexpected
You may have recently stopped and restarted the Exalogic Control Stack (the software services running on the ExalogicControl, ExalogicControlOpsCenterPC1 and ExalogicControlOpsCenterPC1 vServers), which would indirectly trigger EM OpsCenter Control (EMOC) to re-discover rack assets and defined networks.
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