Networking - Practical Oracle Database Appliance - page 94

Configure the Remaining Networks
Once you have applied the ILOM and host public network IP addresses, you are ready to continue with the
deployment, which will apply the remaining IP addresses to your system. Run the ODA deployment process to
configure the remaining networks.
If you used the Oracle Appliance Manager Configurator offline to build your deployment configuration file, which
includes the IP addresses that have been assigned, you need to prepare the configuration file by running the oakcil
copy command. If you're not using a configuration file, you can run the Appliance Manager Configurator interactively.
Prepare the previously created ODA configuration file by running oakcli with the full path and file name, where
the file was copied to the ODA. The command syntax for this step is documented in the oakcli command reference in
the appendix of the ODA Getting Started Guide.

# ./oakcli copy -conf /path/file_name.param

Deploy the ODA using the previously prepared configuration file:

# ./oakcli deploy -conf /path/file_name.param

Alternatively, you can deploy the ODA interactively (without a previously prepared configuration file):

# ./oakcli deploy

If you plan on using the interactive approach, be sure to run the command using a GUI interface through the
ODA startx command or through the VNC Server that ships with ODAs.
Please be sure to read the complete set of documentation detailing all of the tasks required to deploy an ODA.
Since this chapter only concerns ODA networking, I have limited the deployment steps to those related to the
deployment of the ODA networks.

Post Deployment Options for Making Network Changes
There are a number of options for making network changes after the ODA has been deployed. One option is to start
all over again by “bare metaling” your machine and starting over with your deployment. The procedures for doing this
are outlined in MOS note 1373599.1. Depending on the status of your deployment, this may or may not be a practical
option.
If you have an experienced Oracle hardware and OS sysadmin working with you, he or she will already be ready
familiar with setting up the hardware and making network changes.
Oracle has published a number of MOS notes for making the following types of network changes:

• Implementing network bonding after the deployment has already been completed (MOS

1422563.1)

• Changing the ILOM Network IPs (MOS 1442113.1)

• Changing the DNS servers (MOS 1600317.1)

These notes are worth reading even if you don't need to change the IP addresses on any of your ODAs, because
they highlight one of the automation features of an ODA: the GridInst.pl script.
The GridInst.pl script is documented in MOS note 1409835.1 and can be found in the following directory:

/opt/oracle/oak/onecmd/GridInst.pl