Big Data Appliance X3-2 Full Rack
 
Big Data Appliance X3-2 Hardware
 
Big Data Appliance X3-2 In-Rack Expansion
 
Big Data Appliance X4-2 Hardware
 
Big Data Appliance X4-2 Full Rack
 
Big Data Appliance X4-2 Starter Rack
 
Big Data Appliance X4-2 In-Rack Expansion
 
Big Data Appliance X3-2 Starter Rack
 

PLA-Support>Eng Systems>BDA>Big Data Appliance>DB: BDA_EST
 

In this Document

Symptoms

Cause

Solution

Applies to:

Symptoms

When configuring the hardware and network for a newly shipped BDA with a V4.1 image it is found that after configuring the network the BDA servers are not accessible on the admin network (but they are via the ILOMs).

In a little more detail the following general network configuration steps are completed:

- uploading the network.json configuration file to all servers on the BDA (after generating with the 4.1 configuration utility)
- running networksetup-one which configures admin and private networks
- connecting the BDA to the customer's networks
- running networksetup-two which configured the client network

After these steps it is found that BDA servers are not accessible on the admin network (but they are on the ILOMs).

Cause

This problem is caused by a bug in networksetup-one (actually in the underlying tool bdanetworktool) which incorrectly configures admin network routing so that the file /etc/sysconfig/network-scripts/route-eth0 contains incorrect information. 

The internal bug for this is: Bug 20381332 - networksetup-one misconfigures eth0 route

Solution

A workaround may be to manually update this file with the correct info and restart the eth0 interface.

This solution has no attachment