Chapter 3 Network Requirements

New systems with factory-installed Controller Software Release 2.4.4 have an Ethernet-based network architecture.

Note

The networking infrastructure in Oracle Private Cloud Appliance and Oracle Private Cloud at Customer is integral to the appliance and shall not be altered. The networking does not integrate into any data center management or provisioning frameworks such as Cisco ACI, Network Director, or the like, with the exception of the ability to query the switches using SNMP in read-only mode. No changes to the networking switches in Oracle Private Cloud Appliance and Oracle Private Cloud at Customer are supported unless directed to do so by a KM note or Oracle Support.

3.1 Network Connection and IP Address Requirements

This section describes the network connection requirements and IP address requirements to connect the Oracle Private Cloud Appliance to your existing network infrastructure.

3.1.2 IP Address Requirements

The Oracle Private Cloud Appliance requires a large number of private IP addresses. These are reserved for the normal operation and future expansion of the system and cannot be reconfigured. While system-level subnets and IPs should be avoided, the customer is allowed to choose the network configuration for external and virtual machine traffic that suits their requirements.

For lists of default IP addresses that are preassigned to your Oracle Private Cloud Appliance, see Appendix A, Default IP Addresses.

To gain initial access to the Oracle Private Cloud Appliance Dashboard, you must connect a terminal or workstation with a web browser directly to the internal management network. Connect an Ethernet cable to the available port 48 in the Cisco Nexus 9348GC-FXP Switch, and statically configure the wired network connection of the workstation to use the IP address 192.168.4.254.

Caution

The IP address 192.168.4.254 and switch port 48 have been reserved specifically for the purpose of connecting a workstation during the first boot, initialization and provisioning of the appliance.

During the initial software configuration of the Oracle Private Cloud Appliance, you configure the network settings of the management nodes. For this purpose, you should reserve three IP addresses in the public (data center) network: one for each management node, and one to be used as virtual IP address shared by both management nodes. If the data center network traffic is tagged, make sure that the VLAN ID is also provided as part of the configuration. The virtual IP address provides access to the Dashboard once the software initialization is complete.

To avoid network interference and conflicts, you must ensure that the data center network does not overlap with any of the infrastructure networks of the Oracle Private Cloud Appliance internal configuration. These are the subnets and VLANs you should keep clear:

Subnets:

  • 192.168.4.0/24 – internal machine administration network: connects ILOMs and physical hosts

  • 192.168.32.0/21 – internal management network: traffic between management and compute nodes

  • 192.168.64.0/21 – underlay network for east/west traffic within the appliance environment

  • 192.168.72.0/21 – underlay network for north/south traffic, enabling external connectivity

  • 192.168.40.0/21 – storage network: traffic between the servers and the ZFS storage appliance

Note

Each /21 subnet comprises the IP ranges of eight /24 subnets or over 2000 IP addresses. For example: 192.168.32.0/21 corresponds with all IP addresses from 192.168.32.1 to 192.168.39.255.

VLANs:

  • 1 – the Cisco default VLAN

  • 3040 – the default service VLAN

  • 3041-3072 – a range of 31 VLANs reserved for customer VM and host networks

  • 3073-3099 – a range reserved for system-level connectivity

    Note

    VLANs 3090-3093 are already in use for tagged traffic over the /21 subnets listed above.

  • 3968-4095 – a range reserved for Cisco internal device allocation

3.2 General Network Configuration

Table 3.1 is a general network configuration worksheet to help you configure your Oracle Private Cloud Appliance. Oracle requests that you collect the information in preparation of the installation in your data center. The parameters entered in this worksheet are used as input during the initialization of the appliance.

Table 3.1 General Network Configuration Worksheet

Item

Your Configuration

Description and Example

Domain Name

Company network domain name.

Example: abc.example.com

Region

Name of the country in which Oracle Private Cloud Appliance is installed.

Time Zone

Valid time zone.

IP address of the Domain Name Server

IP address of one or more network name servers (up to three servers).

Example: 10.25.45.123, 10.25.45.125

NTP Server

IP address of a Network Time Protocol server.

Example: 10.12.13.14

Search Domains

A list of search domains for name lookup.

Example: example.com , example.org

Default Gateway

IP address of the default gateway in your organization.

Example: 10.203.72.2

IP address of Management node 1

IP address of the first management node in your company network.

Example: 10.203.72.101

Host name of Management node 1

Host name of the first management node in your company network.

Example: manager1

IP address of Management node 2

IP address of the second management node in your company network.

Example: 10.203.72.102

Host name of Management node 2

Host name of the second management node in your company network.

Example: manager2

Management virtual IP address

Virtual IP address of the management node cluster in your company network.

Example: 10.203.72.100

Management VLAN ID

Data center VLAN tag for the management network, if applicable.

Example: VLAN tag 20

vPC domain ID

vPC domain ID for spine switches must be unique in your environment, the default value is 1.

Example: vpc domain 1