Getting errors on bdacheckib –s and on networksetup-two that the client and admin networks are on the same subnet. (Doc ID 1917133.1)

Last updated on JANUARY 23, 2018

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

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

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

Getting errors on bdacheckib –s and on networksetup-two that the client and admin networks are on the same subnet. (Doc ID 1917133.1)

Applies to:

Symptoms

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!