The Network Settings tab is used to configure networking and service information for 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 by both management nodes. 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 subnets of the Oracle Private Cloud Appliance default 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
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
NoteVLANs 3090-3093 are already in use for tagged traffic over the
/21subnets listed above.3968-4095 – a range reserved for Cisco internal device allocation
In the Network Settings tab, the following fields are available for configuration:
Management Node 1:
IP Address: Specify an IP address within your datacenter network that can be used to directly access this management node.
Hostname: Specify the host name for the first management node system.
Management Node 2:
IP Address: Specify an IP address within your datacenter network that can be used to directly access this management node.
Hostname: Specify the host name for the second management node system.
Management Node Cluster:
Management Network VLAN:
No VLAN: By default this radio button is set. The default configuration does not assume that your management network exists on a VLAN.
VLAN Enabled: If you have configured a VLAN on your switch for the management network, you should set this radio button and then specify the VLAN ID for the VLAN that the management network must use in the provided field.
CautionWhen a VLAN is used for the management network, and VM traffic must be enabled over the same network, you must manually configure a VLAN interface on the vx13040 interfaces of the necessary compute nodes to connect them to the VLAN with the ID in question. For instructions to create a VLAN interface on a compute node, refer to the Create a VLAN section in the Oracle VM documentation.
Virtual IP: Specify the shared Virtual IP address that is used to always access the active management node. This IP address must be in the same subnet as the IP addresses that you have specified for each management node.
Domain Name: Specify the domain that each of the management node systems belong to.
Netmask: Specify the netmask for the network that the Virtual IP address and management node IP addresses belong to.
Default Gateway: Specify the default gateway for the network that the Virtual IP address and management node IP addresses belong to.
NTP: Specify the NTP server that the management nodes and other appliance components must use to synchronize their clocks to.
DNS: Specify at least one DNS server that the management nodes can use for domain name resolution.
PCA Admin Password: You must enter the current Oracle Private Cloud Appliance Admin account password to make changes to any of these settings.
Clicking the button at the bottom of the
page saves the settings that are currently displayed on the page
and updates the configuration on each of the management nodes. The
ovca services are restarted in the process, so
you are required to log back in to the Dashboard afterwards.
