3 Network Requirements
Oracle Private Cloud Appliance network architecture relies on physical high speed Ethernet connectivity.
The networking infrastructure in Oracle Private Cloud Appliance 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. However, Oracle Private Cloud Appliance can communicate with the Cisco ACI fabric in your datacenter using the L3Out functionality (static routes or eBGP) provided by Cisco ACI. For more information about this Cisco feature, see the Cisco ACI Fabric L3Out Guide.
Caution:
No changes to the networking switches in Oracle Private Cloud Appliance are supported unless directed to do so by a KM note or Oracle Support.
Network Connection Requirements
These sections describe the network connection requirements and data center network requirements to connect the Oracle Private Cloud Appliance to your existing network infrastructure.
Network Overview
For overview information regarding network infrastructure, see the following sections in the Hardware Overview chapter of the Oracle Private Cloud Appliance Concepts Guide.
Device Management Network
The device management network provides internal access to the management interfaces of all appliance components.
Data Network
The appliance data connectivity is built on redundant 100Gbit switches in two-layer design similar to a leaf-spine topology. An Oracle Private Cloud Appliance rack contains two leaf and two spine switches. The leaf switches interconnect the rack hardware components, while the spine switches form the backbone of the network and provide a path for external traffic.
Uplinks
Uplinks are the connections between the Oracle Private Cloud Appliance and the customer data center. For external connectivity, 5 ports are reserved on each spine switch. Four ports are available to establish the uplinks between the appliance and the data center network; one port is reserved to optionally segregate the administration network from the data traffic. Use this section to plan your network topology and logical connection options.
Administration Network
You can optionally segregate administrative appliance access from the data traffic.
Reserved Network Resources
Oracle Private Cloud Appliance requires a large number of IP addresses and several VLANs for internal operation. See "Reserved Network Resources" in the Hardware Overview section for the IP address ranges reserved for internal use by Oracle Private Cloud Appliance.
Network Configuration Requirements
On each spine switch, ports 1-4 can be used for uplinks to the data center network. For speeds of 10Gbps or 25Gbps, the spine switch port must be split using a 4-way splitter or breakout cable. For higher speeds of 40Gbps or 100Gbps each switch port uses a single direct cable connection. For detailed information about choosing the appropriate configuration, refer to "Uplinks" in the Network Infrastructure section of the Hardware Overview.
The uplinks are configured during system initialization, based on information you provide as part of the Initial Installation Checklist. Unused spine switch uplink ports, including unused breakout ports, are disabled for security reasons.
It is critical that both spine switches have the same connections to each to a pair of next-level data center switches. This configuration provides redundancy and load splitting at the level of the spine switches, the ports and the data center switches. This outbound cabling depends on the network topology you deploy. The cabling pattern plays a key role in the continuation of service during failover scenarios. For more information about the available topologies (Triangle, Square, and Mesh) refer to "Uplinks" in the Network Infrastructure section of the Hardware Overview.
-
Before installation, you must run network cables from your existing network infrastructure to the Oracle Private Cloud Appliance installation site. For instructions see Connect the Appliance to Your Network.
-
Plan to connect at least 1 high-speed Ethernet port on each spine switch to your data center public Ethernet network.
-
Configuring the optional Administration network requires 2 additional cable connections (one each from port 5 on the two spine switches) to a pair of next-level data center switches.
-
Uplink connectivity is based on layer 3 of the OSI model.
DNS Configuration for Oracle Private Cloud Appliance
To integrate the data of the Oracle Private Cloud Appliance's dedicated DNS zone into the data center DNS configuration, two options are supported: zone delegation or manual configuration. The preferred approach is to configure zone delegation, as described below.
However, if you select manual configuration, it is good practice to register network host names and IP addresses for the management network, client network, and additional public networks in the data center Domain Name System (DNS) prior to initial configuration. In particular, all public addresses, VIP addresses and infrastructure services endpoints should be registered in DNS prior to installation.
All addresses registered in DNS must be configured for forward resolution; reverse resolution is not supported in the Oracle Private Cloud Appliance services zone.
Zone Delegation (preferred)
For zone delegation to work, it is required that the data center's recursive caches are able to reach TCP/UDP port 53 on the virtual IP address shared by the appliance management nodes. It may be necessary to change your firewall configuration.
Configure the data center DNS server so that it operates as the parent zone of the appliance DNS zone. Thus, all DNS requests for the child zone are delegated to the appliance internal DNS server. In the data center DNS configuration, add a name server record for the child zone and an address record for the authoritative server of that zone.
In the example it is assumed that the data center DNS domain is
example.com, that the appliance is named
mypca, and that the management node cluster virtual IP
address is 192.0.2.102. The appliance internal DNS server host name is
ns1.
$ORIGIN example.com. [...] mypca IN NS ns1.mypca.example.com. ns1.mypca IN A 192.0.2.102
Manual Configuration
Manually add DNS records for all labels or host names required by the appliance.
In the examples it is assumed that the data center DNS domain is
example.com, that the appliance is named mypca, and that the
management node cluster virtual IP address is 192.0.2.102.
Note:
For object storage you must point the DNS label to the Object Storage Public IP. This is the public IP address you assign specifically for this purpose when setting up the data center public IP ranges during Initial Setup. Refer to the Public IPs step near the end of the section "Complete the Initial Setup".
| Appliance Infrastructure Service | Appliance DNS Label and Data Center DNS Records |
|---|---|
|
Admin service |
admin A 192.0.2.102
|
|
Networking, Compute, Block Storage, Work Requests services |
iaas A 192.0.2.102
|
|
Identity and Access Management service |
identity A 192.0.2.102
|
|
DNS service |
dns A 192.0.2.102
|
|
Object storage Note: Use the Object Storage Public IP from the Appliance Initial Setup. |
objectstorage A 198.51.100.33
|
|
File storage |
filestorage A 192.0.2.102
|
|
Alert manager |
alertmanager A 192.0.2.102
|
|
Container manager |
containermanager A 192.0.2.102
|
|
API |
api A 192.0.2.102
|
|
Grafana |
grafana A 192.0.2.102
|
|
Prometheus |
prometheus A 192.0.2.102
|
|
Prometheus-gw |
prometheus-gw A 192.0.2.102
|
|
Service Web UI |
adminconsole A 192.0.2.102
|
|
Compute Web UI |
console A 192.0.2.102
|
Data Center Switch Configuration Notes
When configuring the data center switches to accept incoming Oracle Private Cloud Appliance uplinks – the default uplinks as well as any custom uplinks you define – take these notes into account.
-
All uplinks, default and customer, are configured to use link aggregation (LACP). All switch ports included in an uplink configuration must belong to the same link aggregation group (LAG). The switch ports on the data center side of the uplinks must be configured accordingly.
-
The spine switches operate with the Virtual Port Channel (vPC) feature enabled in static routing configurations. For more information about configuration rules, see "Uplinks" in the Network Infrastructure section of the Hardware Overview.
-
Oracle Private Cloud Appliance supports layer 3 based uplink connectivity to the customer datacenter. Static routing and BGP4-based dynamic routing are supported in layer 3.
-
Auto-negotiation is not available for uplink ports. Transfer speed must be specified on the customer switches' end. For the supported uplink ports speeds, see "Uplinks" in the Network Infrastructure section of the Hardware Overview.
Default System IP Addresses
The management IP address represents a component's connection to the internal administration network.
Caution:
For hardware management, Oracle Private Cloud Appliance uses a network internal to the system. It is not recommended to connect the management ports or the internal administration network switches to the data center network infrastructure.
The table in this section lists the default management IP addresses assigned to servers and other hardware components in an Oracle Private Cloud Appliance base configuration rack.
| Rack Unit | Rack Component | Management IP Address Assigned During Manufacturing |
|---|---|---|
|
32 |
Spine Switch |
100.96.2.21 |
|
31 |
Spine Switch |
100.96.2.20 |
|
26 |
Management Switch |
100.96.2.1 100.96.0.1 |
|
25 |
Leaf/Data Switch |
100.96.2.23 |
|
24 |
Leaf/Data Switch |
100.96.2.22 |
|
Management Node VIP |
100.96.2.32 ILOM: 100.96.0.32 |
|
|
7 |
Management Node |
100.96.2.35 ILOM: 100.96.0.35 |
|
6 |
Management Node |
100.96.2.34 ILOM: 100.96.0.34 |
|
5 |
Management Node |
100.96.2.33 ILOM: 100.96.0.33 |
|
Storage VIPs |
Performance pool 100.96.2.5 Capacity pool 100.96.2.4 |
|
|
3-4 |
Oracle ZFS Storage Appliance ZS9-2 Controller Server (2 rack units) |
100.96.2.3 ILOM: 100.96.0.3 |
|
1-2 |
Oracle ZFS Storage Appliance ZS9-2 Controller Server (2 rack units) |
100.96.2.2 ILOM: 100.96.0.2 |
|
B |
PDU |
100.96.3.242 |
|
A |
PDU |
100.96.3.241 |
Compute nodes are assigned an IP address in the internal administration network during
the provisioning process. The system IP address is DHCP-based; the ILOM is assigned the
system IP, where the third octet is changed from 2 to 0. For example: if a compute node
receives IP 100.96.2.64 , then its ILOM has IP 100.96.0.64 . Once
assigned to a host, these IP addresses are stored and persisted in the DHCP database.