Preparing for Exadata - Oracle Exadata Recipes: A Problem-Solution Approach - page 143

After your installation is complete, you can run checkip.sh with the - m post_deploy112 argument to validate
your configuration.

How It Works
The checkip.sh script verifies network configuration for Exadata Database Machine pre-installation, during
installation, and post-installation. The following conditions are verified by checkip.sh :

• IP addresses that should be pingable are reachable.

• IP addresses that should not be pingable are not reachable.

• Hostnames that are expected to be registered in DNS are both forward and reverse resolvable

using the first name server in the dbm.dat file.
After running checkip.sh , any success or failure messages are logged to dbm.out . Prior to scheduling Oracle
ACS to perform your Exadata installation, you will need a clean run of checkip.sh . The reason this is so important is
because Exadata's onecommand process, discussed in Chapter 6, automates the installation of your Exadata Database
Machine and expects that your network's IP addresses and names match the configuration information provided
to Oracle and used during the installation. Failure to assign or resolve IP addresses and hostnames during the
installation will cause implementation delays and rework.

6-4. Customizing Your InfiniBand Network Configuration
Problem
You wish to change the default InfiniBand network configuration to support InfiniBand addressing flexibility across
multiple Exadata Database Machines. For example, if you wish to perform Exadata or Exalogic backups on your
InfiniBand network with IB-aware backup media servers, it may be important to have nonstandard and different
InfiniBand network configurations for multiple machines.

Solution
As each organization's nonstandard InfiniBand network configuration requirements may be different, it is important
to discuss your site's requirements with Oracle or your Oracle Partner prior to installing and configuring InfiniBand
networking on your Exadata Database Machine. By default, the InfiniBand network addresses on each Exadata
Database Machine will be configured the same; in other words, 192.168.10.1 will be the InfiniBand IP address on
your first database server, 192.168.10.2 will be configured on your second database server, and so forth. These are set
when /opt/oracle.SupportTools/firstconf/applyconfig.sh is run, which reads the /opt/oracle.SupportTools/
onecommand/preconf.csv file. To change these default InfiniBand IP addresses, you'll need to work with Oracle to
modify the standard templates ( preconf.csv ) used by Exadata's onecommand installation process so that the proper IP
addresses will be configured.

How It Works
Each Exadata Database Machine of each configuration (Quarter Rack, Half Rack, or Full Rack) will have identical
InfiniBand IP addresses unless you specifically change these when building your configuration. The applyconfig.sh
script, which is executed as part of your Exadata installation process, will set these IP addresses based on settings
established in a preconf.csv file. To deviate from these default settings, you need to ensure that your preconf.csv file
contains the desired information.