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 MAY 17, 2016

Applies to:

Oracle Exalogic Elastic Cloud Software - Version 2.0.6.2.4 and later
Linux x86-64
Oracle Virtual Server x86-64

Symptoms

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:

 

Changes

You may have recently stopped and restarted the Exalogic Control Stack (the software services running on the ExalogicControlExalogicControlOpsCenterPC1 and ExalogicControlOpsCenterPC1 vServers), which would indirectly trigger EM OpsCenter Control (EMOC) to re-discover rack assets and defined networks.
 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms