Database Reference
In-Depth Information
The process outlined in the setup poster seems simple enough. And it is, almost. Some of the colors are very close
to each other, so you have to pay attention to the shades. I've seen a few issues where data center people have made
some mistakes with the connections, and sometimes it is the coloring that has thrown them off. This is an area where
you can have someone on the team specialize in making these connections, rather than spreading this work around.
A more expanded set of documentation covering the connections between the server nodes and storage units is
included in both the ODA Getting Started Guide and the ODA Owner's Guide. The manuals include additional charts
that provide more details and can be easier to read than the setup poster.
To help validate the internal connections, Oracle recommends that you run
oakcli
to validate the cabling before
starting the configuration of the public networks. This step is documented in the Getting Started Guide in both the
“Deployment” and “Troubleshooting” chapters. The following is the command to validate the cabling:
# /opt/oracle/oak/bin/oakcli validate -c storagetopology
In addition to the cabling needed to connect the ODA components together, the external cabling needs to be
completed. The external cabling includes the connections between the ODA and the network in your data center,
as outlined in Table
5-2
. This includes the cabling for your public network, private network, and ILOM connections.
If the connections are bonded, each server node will have two public cable connections, two private network
connections, and one ILOM connection—for a total of ten network cables for the two ODA server nodes. Of course,
the connections can be reconfigured to not be bonded to deploy additional networks, if necessary. The procedures for
modifying the network interfaces are covered in several Oracle support MOS notes, including 1422563.1, 1436335.1,
and 1442113.1, as well as the Oracle Linux Administration manuals.
Apply the ILOM IP Addresses and Configure the ODA Public Network
There are a number of options for applying IP addresses to the ODA's network interfaces. These options are covered in
the Oracle deployment documentation starting with the setup poster, Getting Started Guide, MOS note 1373617.1 for
bare-metal deployments, or MOS note 1520579.1 for virtual deployments.
One area where the documentation could be a little clearer is the process for applying IP addresses to an ODA.
All of the documentation points to logging into each of the ODA nodes as
root
using the default password, and then
running the
firstnet
script on each server node to configure the public network for each host. There are also some
references in the manuals on setting up the ILOM first, but the information isn't very clear. Accordingly, we'll try to
clear things up.
First, setting up the ILOM to begin the process of adding IP addresses is the same on an ODA as it is on an Oracle
Solaris server or any other piece of Oracle Linux hardware. If you have an experienced sysadmin working with you to
deploy the ODA, he or she will already know what to. Starting the deployment of the ODA by applying the ILOM IPs
first is a very efficient way to start the deployment.
If you are on your own to deploy the ODA, don't worry—getting started by adding the IP addresses to the ILOMs
on each server is not hard. However, first you have to decide how you are going to connect to the ILOM device.
There are at least two options:
•
Connect to the ODA serial port using a laptop and a serial connection cable.
•
Connect to the ODA using a serial console device such as a data center KVM cart or a data
center KVM (keyboard, video, and mouse) appliance.
Connecting to the ODA ILOM through an ODA server serial port using your laptop with a serial cable is
documented by Oracle in MOS note 1395445.1. Again, if you have people used to deploying Oracle hardware, they
have already done this many times and know what to do. Regardless, the process is straightforward. Just follow the
procedure outlined in the MOS note.
