Create an instance to be used in this environment. The creation process is the same for the bastion server (also used as a client), active nodes, and standby nodes, but some of the configuration values are different. Be careful to enter the appropriate values for the target instance.

  1. Select > Compute > Instances.
  1. Select sios20-c in the Compartment and click Create Instance.
  1. Enter the following values in the form that appears and click Create.
Item Value
Bastion Server Node1 Node2
Name sios20-bastion sios20-node1 sios20-node2
Create In
Availability domain AD 1 (*1)
Show advanced options
Capacity type Leave as default
Shielded instance Disabled
Image and shape
Image Windows Server 2022 Standard (*3)
Shape VM.Standard.E4.Flex (*4)
Primary network Select existing virtual cloud network
Subnet Select existing subnet
sios20-subnet1 sios20-subnet2
Public IPv4 address Assign a public IPv4 address Do not assign a public IPv4 address
Show advanced options (*Use default values except for [Private IPv4 address])
Private IPv4 address
Boot Volume
All the items Leave as default

*1 : An availability domain is one or more data centers located within a region. Since OCI still has many regions with a single availability domain, AD 1 is selected for both cluster nodes in this section. If multiple availability domains become available, specifying different availability domains for the active and standby nodes will increase availability.
*2 : A fault domain is a grouping of hardware and infrastructure, of which there are three within an availability domain. Instances can be distributed so that they do not reside on the same physical hardware within a single availability domain. To increase availability, specify different fault domains for active and standby systems.
*3 : Please select the OS version that your LifeKeeper deployment will support. For OS versions supported by LifeKeeper, please refer to each version’s support matrix (
*4 : Specify a Shape for which the OS specified in Image can use. Depending on your tenancy, you may need to increase your service limits.

Editing/Creating VNICs

Make the following changes and additions to the VNICs used in both sios20-node1 and sios20-node2 cluster nodes.

  • Change primary VNIC configuration
  • Create a new secondary VNIC

The procedure is described using sios20-node1 as an example. After completing the change/addition of VNIC to sios20-node1, the same process should be performed for sios20-node2.

Change primary VNIC configuration

  1. Select sios20-c under the Compartment and select sios20-node1 (or sios20-node2) in the list.
  1. On the sios20-node1 (or sios20-node2) details page, click [︙] on the right side of the record under Attached VNICs > vnicyyyyyyMMddHHmmss (Primary VNIC) and select Edit VNIC. (yyyyyyMMddHHmmss is probably the creation time of the VNIC.)
  1. Change and save the following configuration values. (Parameters for sios20-node2 are also listed)
Item Value
sios20-node1 sios20-node2
Name sios20-node1-vnic1 sios20-node2-vnic1
Skip source/destination check Enabled

Create a new secondary VNIC

  1. On the sios20-node1 (or sios20-node2) details page, click Attached VNICs > Create VNIC.
  1. Create two secondary VNICs, one for sios20-node1 and one for sios20-node2, by entering the following values in the form that appears.
Item Value
sios20-node1 sios20-node2
VNIC information
Name sios20-node1-vnic2 sios20-node2-vnic2
Select a virtual cloud network sios20-vcn
Network Normal setup: subnet
Select a subnet sios20-subnet3
Use network security groups to control traffic Disabled
Skip source/destination check Enabled
Primary IP information
Primary IP address
Assign a public IPv4 address Disabled (cannot be changed)
DNS record Do not assign a private DNS record (cannot be changed)


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment