Getting errors on bdacheckib –s and on networksetup-two that the client and admin networks are on the same subnet.

Asset ID:	1-72-1917133.1
Update Date:	2018-01-23
Keywords:

Solution Type Problem Resolution Sure

Solution 1917133.1 : Getting errors on bdacheckib –s and on networksetup-two that the client and admin networks are on the same subnet.

Applies to:

Big Data Appliance X4-2 Hardware - Version All Versions and later
Linux x86-64

Symptoms

Getting errors on bdacheckib –s as follows:

[root@bda1node01 etc]# bdacheckib -s
bdacheckib: could not derive leaf1_name from ib fabric: setting to bdasw-ib2
bdacheckib: could not derive leaf2_name from ib fabric: setting to bdasw-ib3
bdacheckibx: entry for switch   bdasw-ib3 not found in iblinkinfo output
bdacheckibx: entry for switch    not found in iblinkinfo output

LINK bda1sw-ib1.0B   ... bda1sw-ib2.HCA-1.32FAIL
   Expected   0B to 8B on switch

LINK bda1sw-ib1.1B   ... bda1sw-ib3.HCA-1.32FAIL
   Expected   1B to 8B on switch bdasw-ib3

LINK bda1sw-ib1.1B   ... bdasw-ib3.8B    DOWN
bdacheckib: all servers of interest accessible

Additionally errors are received when running networksetup-two script that the client and administrator networks are on the same subnet.

Cause

The bdacheckib -s script with -s argument is for ship settings only, i.e. it should be run only before networksetup-one is executed.

After networksetup-one just use bdacheckib.

The client and admin checks can be ignored seen running networksetup-two. The error is harmless and the check for this will disappear in a future version of bdachecknet.

Solution

1. Run bdacheckib without any arguments:

# bdacheckib

2. Check on all nodes that the following files exist:

# dcli ls /root/BDA_*

/root/BDA_IMAGING_SUCCEEDED /root/BDA_REBOOT_SUCCEEDED

3. Run bdachecknet -v so it will do all its tests.

# bdachecknet -v

4. Proceed with installing mammoth.

a. If the networksetup0 was edited to bypass some errors, during mammoth -c the error may be seen:

ERROR: Required package bda is not valid : S.5....T. /opt/oracle/bda/bin/networksetup0

This may cause the bdachecksw checks in mammoth -c to get the following error:

BDA Appliance failed software validation

Additionally, the client and administrator network errors may still be seen. The error is harmless and can be ignored.

If /opt/oracle/bda/bin/networksetup0 was edited to bypass any errors then do the following to resolve this:
As root user copy /opt/oracle/bda/bin/networksetup0 with preserved timestamp from another node.

# scp -p <node2>:/opt/oracle/bda/bin/networksetup0 /opt/oracle/bda/bin/networksetup0

b. Re-run mammoth -c:

# ./opt/oracle/BDAMammoth/mammoth -c

Attachments

This solution has no attachment