Configuring Limited/Full Membership of Exalogic Guest vServers on the Default IPoIB Network
Last updated on MAY 23, 2018
Applies to:Oracle Exalogic Elastic Cloud Software - Version 18.104.22.168.0 and later
Exalogic Elastic Cloud X5-2 Hardware - Version X5 to X5 [Release X5]
Exalogic Elastic Cloud X6-2 Hardware - Version X6 to X6 [Release X6]
Oracle Virtual Sever (x86-64)
The procedure in this document is applicable to v2.0.6 and v2.0.4 Exalogic Guest vServers, running on EECS v22.214.171.124.0 or higher in a virtualized configuration.
When vServers are provisioned on the IPoIB default network, they are created, by default, with full membership on the network. When such vServers are created in different accounts within a vDC, due to their full membership, vServers provisioned in Account A can be reached from those provisioned in Account B. Currently, there is no support for changing the membership on the default IPoIB network during the process of vServer creation.
A set of scripts is provided with this document to enable the toggling of vServer membership on the default IPoIB network from full to limited. These scripts can be used to toggle the membership of Exalogic Guest vServers on the default partition if the vServers have an interface defined on that partition, and also provide support to verify whether the membership changes have been made successfully.
In one execution of the script, Guest vServers belonging to a single account can be modified. To change the membership of Guest vServers belonging to other accounts, the script needs to be executed once for each account.
The scripts may be used for the following operations as well:
- Changing the membership from limited to full
- Changing the membership of a subset of vServers in a given account
Important: Guest vServers are rebooted as part of script execution for the membership changes to take effect. It is recommended that this procedure be performed during a maintenance window.
- EECS version is a supported version, as listed in the “Applies To” section
- Guest vServers to be modified are at v2.0.4 or v2.0.6 or higher (v2.0.1 vServers are not supported)
- Root access to the Exalogic Control vServer (or ExalogicControlOVMM vServer in environments UPGRADED to 2.0.6)
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