About Networking in Oracle Compute Cloud Service

All the client-side networks provided by Oracle Public Cloud Machine are either Ethernet over InfiniBand (EoIB) or IP over InfiniBand (IPoIB). An EoIB network connection is required for external communication, and an IPoIB network connection is required for internal communication.

There are two types of cloud networks that you can use for the instances:

  • Tenant networks

    Networks that are assigned exclusively for a specific tenant. Only the instances in that tenant can use this network.

  • Service networks

    Networks that provide access to shared services across multiple tenants. The instances using this network have either the Service Consumer or Service Provider role.

The Oracle Cloud Administrator creates and manages all the network connections for external access. Whereas, you can create and manage all the IPoIB tenant network connections for internal communication. When you want to connect to the external systems outside the cloud, use EoIB networks for the instances. For communicating with the systems inside the cloud, use IPoIB networks for the instances. You need to assign at least one network connection to launch an instance using orchestration.

IPoIB Tenant Networks

You can create and manage only the IPoIB tenant networks. An IPoIB tenant network must be created for communication among instances in the same tenant. EoIB tenant networks, and EoIB and IPoIB service networks are all created and managed by the Oracle Cloud Administrator.

You can create IPoIB networks either by specifying the IP subnet from which the IP addresses will be used for the instances to be launched, or specifying the global IP pool and the subnet is derived from the pool.

A global IP pool allows IPoIB networks to be created without specifying the IP CIDR or ranges. The IP subnet is allocated from a common pool of IP addresses. You can define the network size while creating the vNet, and the smallest subnet is derived from the global IP pool. A unique CIDR is assigned to the vNet and includes all the IP addresses represented by that CIDR. The IP subnet network size is determined by the following method:

  1. Add 2 to the number of IP addresses requested while creating the IPoIB vNet.

  2. The result is rounded to the nearest power of 2.

For example, if you requested 5 IP address, adding 2 extra addresses to it makes 7 and rounding to the nearest power of 2 is 8. The IP subnet is created with 8 IP addresses. The first and last addresses of a subnet are not allocated to instances as unicast addresses, therefore the balance (6 addresses) is assigned to the vNet for allocation.