Create Networks and Subnets
OCI interface types include those hidden from the internet and those that are not. In
addition, if you are deploying the OCSBC in HA mode, you must ensure that the cloud
can switch between media interfaces on HA instances during failover. This requires
secondary private and reserved public addressing. The table below lists configuration
requirements and considerations for interfaces, with respect to OCI interface types.
vNIC
Subnet
Public
or
Private
Required
for
Standalon
e
Required
for HA
Private
IP
Public IP -
Ephemeral
Seconda
ry
Private
IP
Reserved
Public IP
wancom0 Either
Required
Required
Require
d
Optional
N/A
Optional
wancom1 Private
N/A
Required
Require
d
N/A
N/A
N/A
wancom2 Private
N/A
Optional
Require
d
N/A
N/A
N/A
s0p0,
s1p0,
s0p1
(and all
other
Media
interfaces
)
Public
Between 1
and 8
interfaces
Between 1
and 8
interfaces
Require
d
Yes for
standalone
mode, if
traffic comes
through
Internet.
(N/A for HA)
Yes for
HA mode.
(Optional
for
standalon
e)
Yes for HA
mode, if
traffic
comes
through
Internet.
(Can be
used
instead of
ephemeral
public IP
for
standalone
.)
Oracle recommends creating regional subnets, which means the subnet can span
across availability domains within the region. With this primary and secondary OCSBC
instances can be deployed in two different Availability Domains thereby making use of
OCI infrastructure level high availability. Alternatively you could create non-Regional
subnets which means the subnet is limited to a single Availability Domain. In this case,
both primary and secondary OCSBC instances MUST be deployed within that
Availability Domain
Refer to OCI's Regional Subnets documentation for further information about using
these objects.
During the deployment procedure, ensure that OCI provides the IP address for the
wancom0 (primary management) interface via DHCP.
Create Dynamic Group and Policy Statements
High Availability (HA) instances require the ability to interact with the platform's API
during failover events. You create both Dynamic Groups and Policy Statements for this
purpose. Dynamic Groups include rules configuration, which you use to define the
instances that belong the group. Policy statements refer to dynamic group names,
followed by the action allowed for the group.
Chapter 7
Create and Deploy on OCI
7-24
