In this video, I'll show you how to complete the initial day 0 configuration of your Oracle
Private Cloud Appliance.
You first need to connect a laptop or workstation with a web browser directly to the management
network using an Ethernet cable connected to port 2 on the management switch.
Configure the wired network connection of the workstation to use the static IP address
100.96.3.254.
Here I'm showing the network settings on my laptop.
Using the web browser on the workstation, connect to the Oracle Private Cloud Appliance
First Boot interface on the active management node at
https://100.96.2.32:30099.
Here I'm showing the First Boot Wizard on the address and port number I mentioned.
I'll create the Administrative Account by providing a username and password, and confirm
the password.
I'll click Create Account & Login.
The Admin user was created successfully.
I'll click Continue to Login.
Now I'm prompted to sign in to the system with the credentials I just created.
Next I'm prompted to provide a System Name and Domain.
The Availability Domain is automatically provided.
As the Note says, "Once System Name and Domain are set, they CANNOT BE CHANGED."
"Please enter and check these details carefully."
I'll scroll down and I can optionally provide a Rack Name and Description.
I'll click Save Changes.
And now we're asked to wait while the Private Cloud Appliance initializes.
Initialization may take 15 minutes or longer.
But for this demonstration, I'll speed through this.
I'm now prompted to sign in again using the Administration credentials I created earlier
in this demo.
After signing in, I'm prompted to configure network parameters.
Beginning with Routing Type, I can select either Static or Dynamic.
I'll show the Dynamic routing parameters.
When dynamic routing is selected, BGP (Border Gateway Protocol) is used to establish a connection
between two Autonomous Systems: the appliance network and the data center network.
This configuration requires a registered Autonomous System Name (ASN) on each side of the connection.
For this demonstration, I'm going to select Static routing.
Static routing routes all external traffic through a gateway.
This default gateway must have an IP address in the same subnet as the external interfaces
of the spine switches.
Using a VLAN is supported, as long as its ID is within the permitted range (2-3899).
All gateways configured within a virtual cloud network will automatically have a route rule
to direct all traffic intended for external destination to the IP address of the default
gateway.
If you don't use VLAN or HSRP, you can just leave the defaults.
I'll click next to provide the network parameters for the management nodes.
Note that the Management Node VIP Hostname is different from the system name.
Here, I'm setting the network interface name.
And unlike, the system name and the domain name, this network information can be changed
later.
I'll speed through this and click Next.
Here I'm prompted to provide uplink information for my datacenter.
In this demonstration, the uplink port speed is 40 Gig but could be up to 100.
And uplink port count is 1 but customer datacenter could have more.
Here I'll set the netmask for the management network only.
I'll scroll down and click Next.
On this screen I'll provide my NTP servers.
I'll click Next.
On this screen, I can enable and configure Admin networking.
In an environment with elevated security requirements, you can optionally segregate administrative
appliance access from the data traffic.
Disable is the default but I'll select Enable and show the parameters needed.
Setting up the administration network requires additional Ethernet connections from the data
center Top of Rack switches to port 5 on each of the spine switches in the appliance.
Inside the administration network, the spine switches must each have one IP address and
a virtual IP shared between the two.
A default gateway is also required to route traffic.
A separate administration network can be used with both static and dynamic routing.
The use of a VLAN is supported, but when combined with static routing the VLAN ID must be different
from the one configured for the data network.
I'll change this back to Disable for this demonstration and click Next
On this screen I'll provide my DNS servers.
I'll click Next.
Here I'll enter the IP addresses for my datacenter that the Appliance can access.
Provide a comma-separated list of CIDRs.
These are the customer datacenter public IPs that the Appliance uses for OCI components
that require public IPs, for example OCI gateways and compute instances.
Note that they are not Public, but instead represent IP addresses that have access in
on premise networks.
And I can also provide Object Storage Public IP.
I'll click Save Changes.
Wait for the server to process our request.
I'll speed through this.
A message appears saying the Private Cloud Appliance is in a mode where networking configuration
may be tested before it is committed.
Once committed then certain parameters may not be changed including routing type and
public IPs.
I'll click Commit Changes.
Wait a bit while the Appliance initializes.
I'll speed through this.
The configuration process is complete.
I'll click Sign Out.
Now I'll sign in using the Admin credentials.
The first time you sign in after completing day 0 configuration, this screen appears providing
the opportunity to configure the phone home service to use Auto Service Request.
Day 0 configuration is complete but I'm just going to select Network Environment from the
hamburger menu and show the network information.
Here you can click each of the tabs to view the different networking parameters we entered
during Day 0 configuration.
This concludes this demonstration.
Thank you for watching.
Please check our additional information on Oracle Private Cloud Appliance in the Oracle
Private Cloud Appliance Documentation or in the Oracle Private Cloud Appliance Learning
Library.