4.1 Networks and Network Services

Oracle Private Cloud at Customer relies on different physical and logical networks to provide secure and reliable network connectivity for different application and management functions. This section outlines the minimum network requirements to install an Oracle Private Cloud at Customer system.

  • Infrastructure Management Network

    All infrastructure components inside the base rack are physically connected to this Gigabit Ethernet network, which uses the 192.168.4.0/24 subnet. A single uplink connects it to an Oracle-managed switch, which integrates the management interfaces of the external ZFS storage appliance and the Oracle Advanced Support Gateway. With a second network interface, the support gateway connects to the data center network, enabling Oracle to access the infrastructure management network remotely. No customer or external access to this network is permitted.

  • Virtual Machine Management Private Network

    A Private Virtual Interconnect (PVI), a virtual Ethernet network configured on top of the physical InfiniBand fabric, connects the management nodes and compute nodes in the 192.168.140.0/24 subnet. It is used for all network traffic inherent to Oracle VM Manager, Oracle VM Server and the Oracle VM Agents. No external access is provided.

  • Optical Storage Network

    Four 10GbE optical connections run between the base rack and internal 10GbE switches to provide resilient connectivity between the compute nodes and the external Oracle ZFS Storage Appliance ZS7-2. This dedicated 10GbE Ethernet internal network allows customer VMs to access shared storage on the external ZFS storage appliance. No external access is provided.

  • InfiniBand Storage Private Network

    For storage connectivity between the management nodes, compute nodes, and internal and external ZFS storage appliances, a high bandwidth IPoIB network is used. The components are assigned an IP address in the 192.168.40.0/24 subnet. This network also fulfills the heartbeat function for the clustered Oracle VM server pool. No external access is provided.

  • Virtual Machine Networks

    For network traffic to and from virtual machines (VMs), virtual Ethernet networks are configured on top op the physical InfiniBand fabric. Untagged traffic is supported by default; the customer can request the addition of VLANs to the network configuration, and subnets appropriate for IP address assignment at the virtual machine level. The default configuration includes one private VM network and one public VM network. Additional custom networks can be configured to increase network capacity. Contact Oracle for more information about expanding the network configuration.

    External VM connectivity is provided through public VM networks, which terminate on the I/O modules installed in the Fabric Interconnects and are routed externally across the 10GbE ports. The I/O ports must be cabled to redundant external 10GbE switches, which in turn must be configured to accept the tagged VLAN traffic to and from the VMs.

  • Client Network

    This information is currently not available in the documentation.

In addition, Oracle Private Cloud at Customer requires the following data center network services:

  • DNS Service

    As part of the deployment process, you work together with Oracle to determine the host names and IP addresses to be used when deploying Oracle Private Cloud at Customer. The fully qualified domain names (FQDN) and IP addresses of the management nodes must be registered in the data center Domain Name System (DNS).

  • NTP Service

    At least one reliable Network Time Protocol (NTP) server is required and should be accessible on the client network. The management nodes are configured to synchronize with the NTP server. All other Oracle Private Cloud at Customer components are configured to reference the active management node for clock synchronization.