My Oracle Support Banner

Running the networksetup-two Script for a New Installation on Oracle Big Data Appliance (BDA) X3-2 Fails with "networksetup-two: ping <gateway ip> (element# 2) failed" (Doc ID 1921433.1)

Last updated on NOVEMBER 13, 2019

Applies to:

Big Data Appliance X4-2 Hardware - Version All Versions and later
Big Data Appliance X3-2 Hardware - Version All Versions and later
Big Data Appliance X4-2 Full Rack - Version All Versions and later
Big Data Appliance X3-2 Full Rack - Version All Versions and later
Big Data Appliance X4-2 Starter Rack - Version All Versions and later
Linux x86-64

Symptoms

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.

  

The following symptoms exist while configuring the Oracle Big Data Appliance network.

 

1. The networksetup-two script fails when trying to ping the client data gateway as shown below:

...

networksetup-two: passed
networksetup-two: ssh into servers on client network by name
networksetup-two: passed
networksetup-two: test ntp servers
networksetup-two: passed
networksetup-two: ping client gateway
networksetup-two: ping <CLIENT_IP_ADDRESS> (element# 2) failed

 

2. The bdacheckvnics script also shows a "no" for pinging the gateway:

[root@node05 ~]# cd /opt/oracle/*/network
[root@node05 network]# ./bdacheckvnics

    host      if   status actv primary    switch                     gw port       ping gw
============== ===  ====== ==== === ====================== ========= ======
node05      ib0   up    yes  yes           ---                          ---              ---
node05      ib1   up    no   no             ---                          ---              ---
node05      eth8  up    no   no           <switch>-ib-sw1  0A-ETH-1         ---
node05      eth9  up    yes  yes         <switch>-ib-sw2  0A-ETH-1         no

 

3. The arp test shows output like:

[root@node05 network]# arp -a
node03-adm (<ADM_IP_HOST3>) at <HARDWARE_ADDRESS_HOST3> [ether] on eth0
? (<ADM_IP_HOSTx>) at <HARDWARE_ADDRESS_HOSTx> [ether] on bondeth0
? (<ADM_IP_HOSTy>) at <HARDWARE_ADDRESS_HOSTy> [ether] on bondeth0
? (<ADM_IP_HOSTz>) at <HARDWARE_ADDRESS_HOSTz> [ether] on bondeth0

 

4. The bdachecknet script fails with errors as follows:

...

bdachecknet: test admin name array matches ip array
<ADM_IP_HOST1>
bdachecknet: host name json element does not correspond to json element ip address: node01-adm (!=  index 0)
<ADM_IP_HOST2>
bdachecknet: host name json element does not correspond to json element ip address: node02-adm (!=  index 1)
<ADM_IP_HOST3>
bdachecknet: host name json element does not correspond to json element ip address: node03-adm (!=  index 2)
<ADM_IP_HOST4>
bdachecknet: host name json element does not correspond to json element ip address: node04-adm (!=  index 3)
...

 

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.