6.1 Verifying the Network Configuration Prior to Configuring the Rack

Use the checkip.sh script to ensure there are no IP address conflicts between the existing network and your new Oracle Exadata Rack.

The checkip.sh script performs a pre-installation check to verify that the IP addresses and host names that you specified in Oracle Exadata Deployment Assistant (OEDA) are defined in the DNS, that the NTP servers and gateways are available, and that private addresses are not pingable. Running this script before the hardware arrives help to avoid additional delays that would be caused by misconfigured network services, such as Domain Name System (DNS) and NTP.

The checkip.sh script is created in a format that matches the operating system of the client on which you ran OEDA. Because this script is run before the engineered system rack has arrived, you typically do not run this script on an engineered system server, but on a client. The client must have access to the same network where the engineered system will be deployed. The script is also available in the ZIP file generated by OEDA.

1. On the client where OEDA was run, copy the checkip.sh script generated by OEDA and the XML file CustomerName_hostname.xml to the same directory (one directory level up) as the OEDA config.sh script.
2. Run the checkip.sh script on the client machine or existing server.

   Use a command similar to the following, where configuration_file is the name of the configuration generated by the Oracle Exadata Deployment Assistant for the rack being installed.

   # ./checkip.sh -cf configuration_file

   If the command is run from a Microsoft Windows machine, then the command is checkip.cmd.

   If this engineered system rack is an addition for an existing installation, then run the checkip.sh script from an existing engineered system server. This enables the script to identify in-use IP addresses in the fabric. Not identifying existing IP addresses may cause IP collisions after installation of the new engineered system rack. To create a checkip.sh that can run on an existing server, you must run OEDA on a server or client that uses the same operating system as the existing engineered system server. OEDA supports IPv6 addresses.

   The output from the script is a file that contains status messages such as GOOD or ERROR.

If there are conflicts that you are unable to resolve, then work with your assigned Oracle representative to correct the problems.