How to Reimage and Reinstall BDA 4.1.0 and Higher when Network Information for BDA Servers is Changing

Asset ID:	1-71-2024209.1
Update Date:	2017-09-19
Keywords:

Solution Type Technical Instruction Sure

Solution 2024209.1 : How to Reimage and Reinstall BDA 4.1.0 and Higher when Network Information for BDA Servers is Changing

Applies to:

Big Data Appliance Integrated Software - Version 4.1.0 and later
Big Data Appliance X5-2 Hardware - Version All Versions to All Versions [Release All Releases]
Linux x86-64

Goal

Provide the steps needed to reimage and reinstall BDA V4.1.0 and higher when network information for BDA servers is changing.

The steps documented in this article return the BDA servers to factory settings so they can be used to change any server network information except private IB IPs. (The steps to change switch or PDU information are also not included). You can use this MOS note to change any of the following:

- client hostnames
- client domain
- client IP addresses
- client gateway or subnet
- admin hostnames
- admin IPs

All of these except the first two can also be done without a reimage using these MOS Notes.

How to RE-IP Oracle Big Data Appliance When Only Admin/ILOM IPs / Hostnames Are Changing Without Reimaging (Doc ID 1956650.1)
How to RE-IP Oracle Big Data Appliance When Admin IPs / Hostnames, ILOM IPs / Hostnames, Client IPs, Switches, and PDUs Are Changing Without Reimaging (Doc ID 1954238.1)

A frequently asked question is, why are the 2 notes listed above internal, in other words why is it not possible for customers to see them directly. The reasons for the 2 notes being internal is: 1) we do not want to give the instructions out directly as there is detailed work which can be done incorrectly 2) the exact steps depend on the version e.g. whether network.json is present or not and 3) the exact steps depend on exactly what information is changing. If the steps are required, file an SR to develop a set of steps that is customized for the specific situation being addressed.

This note can also be used to change private IB IPs if the new cluster configuration file generated by the Configuration Utility is used to deploy the new cluster.

An example of when the steps in this note would be used is if client network hostnames or client network domain names are being changed.

Solution

To reimage and reinstall BDA V4.1.0 and higher when network information for BDA servers is changing follow the steps below. The example here is based on BDA V4.2.0. Replace BDA V4.2.0 version details with the correct BDA V4.1 or higher version details as required.

Note: Ensure that DNS is updated with client hostname, admin hostname, etc. name changes being made.

client hostnames and admin hostnames were updated in DSN yet?

1.Use the correct BDA Version of the Configuration Utility to regenerate a new network.json file. And make sure to copy the required files off the BDA.

For example on BDA V4.2.0, use the BDA V4.2.0 Configuration Utility to regenerate a new network.json file.

a) Use the Configuration Utility to generate a new network.json file.

From the Oracle Big Data Appliance Patch Set Master Note (Doc ID 1485745.1) download the V4.2 Configuration Utility.

Use the configuration utility to regenerate a new rack_name-network.json file with the correct client/client domain names.

Note: Prior to reimage you will rename rack_name-network.json to network.json. The steps are documented fully in the subsequent referenced MOS documents.

Running the Configuration Utility will generate a new <cluster-name>-config.json in addition to new rack_name-network.json. You may not need to use this newly generated <cluster-name>-config.json as you may be able to continue using the existing file. This is because client names and domain name are not in <cluster-name>-config.son. Therefore the new one may be the same as the old one. However, if any configuration changes have been made you will need to use the newly generated files. For example if you decided to enable Kerberos or disable disk encryption, then you would need to use the newly generated <cluster-name>-config.json. Carefully compare the files. Use the new one if any changes. If no changes you can use the existing file after restoring the version copied off the BDA prior to reimage.

b) Make sure to copy the following files off the BDA for safe keeping. Reimaging will wipe out all the data on all servers(s).

i. Copy the existing network.json on the cluster (you can use it to compare to the new one).
ii. Copy the existing <cluster-name>-config.json
iii. Copy off anything else from the servers that you want to keep.

2. Re-image the BDA rack to factory settings via the steps below. Use the appropriate MOS note to perform the reimage. It will be listed in the Oracle Big Data Appliance Patch Set Master Note (Doc ID 1485745.1).

Note: You do not need the newly generate rack_name-network.json or <cluster>-config.json files at this point.

For example on BDA V4.2.0 follow the documented steps in: Oracle Big Data Appliance Base Image Version 4.1.0 for New Installations on OL6 (Doc ID 1962977.1)

An overview of the steps in 1962977.1 are below. They will be similar with correct version considerations for any BDA version.

a) Download the 4.1 BDA Base Image tarball from My Oracle Support.
The image patch is:
Patch 20369786: ORACLE BIG DATA APPLIANCE BASE IMAGE RELEASE V4.1.0 FOR ORACLE LINUX 6

b) Copy the BDA image tarball onto the first (bottom) server of the BDA to be reimaged.

c) As 'root' user unzip the base image.

d) To reimage the rack from existing customer network settings to the original factory network settings use the following:

# ./reimagerack --no-iloms deploy ship

The --no-iloms option to reimagerack avoids resetting the ILOMs. This gives you ILOM access to the nodes. If the ILOMs are reset then physical access to the nodes may be required.

3. Follow the standard network configuration process as described in sections 7.6.1, 7.6.2, 7.6.5, 7.6.6, 7.6.7 of the Oracle® Big Data Appliance Owner's Guide Release documentation, section 7.6 Configuring the Network.

Note: This is the section where networksetup-one and networksetup-two are run.

An overview of the sections is:

7.6.1 Copying the Configuration Files to Oracle Big Data Appliance.
Follow the steps to transfer the newly generated network.json to the BDA. You will be renaming the rack_name-network.json to network.json.

7.6.2 Starting the Network Configuration.
The section has 6 steps the last is running networksetup-one to start the network configuration. Follow all 6 steps.

7.6.5 Completing the Network Configuration.
Follow the 2 steps.

7.6.6 Checking the Virtual Interface Cards (VNICs) .

7.6.7 Verifying Access to the Network Services.

Note: At this point, 'hostname' will return a fully qualified domain name, but neither 'hostname -f' nor 'hostname --fqdn' will. This is expected. After the Mammoth install, both 'hostname -f' nor 'hostname --fqdn' return the FQDN.

Also note, the documentation states:

You can also check the NTP clients:
# ntpq -p

If 'ntpq -p' does not return successfully, try 'ntpq -p 127.0.0.1'. Although 'ntpq -p 127.0.0.1' and 'ntpq -p' should be the same, the former may be required in some environments.

# ntpq -p 127.0.0.1

In the case of ntpq problems, check the /etc/ntp.conf file and ntpq debug output with: 'ntpq -p -d'.

4. Install the correct BDA version using the Mammoth Software Deployment Bundle. Details per version can be found in the Oracle Big Data Appliance Patch Set Master Note (Doc ID 1485745.1).

For BDA V4.2 follow: Installing Oracle Big Data Appliance Mammoth (Software Deployment Bundle) Release V4.2 for New CDH Installations with OL6 Base Image (Doc ID 2011898.1).

For example for V4.2 from Doc ID 2011898.1:

a) Download Patch 21109091 and copy it over to Node 1 of the BDA. Patch 21109091 consists of 2 zip files:

p21109091_420_Linux-x86-64_1of2.zip
p21109091_420_Linux-x86-64_2of2.zip

b) Install BDA V4.2 using documented steps.

The above two steps will be similar with correct version considerations for any BDA version.

Attachments

This solution has no attachment