Unable to run "bdacheckib BdaShip.json" while Verifying InfiniBand Topology in Oracle Big Data Appliance X4-2 Installation Steps

Asset ID:	1-72-1663316.1
Update Date:	2014-08-27
Keywords:

Solution Type Problem Resolution Sure

Solution 1663316.1 : Unable to run "bdacheckib BdaShip.json" while Verifying InfiniBand Topology in Oracle Big Data Appliance X4-2 Installation Steps

Applies to:

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

Symptoms

Running the following command for Oracle Big Data Appliance X4-2 per the documentation to verify the InfiniBand topology but getting information about usage instead as shown below:

[root@bda01 bda]# bdacheckib BdaShip.json

Usage: bdacheckib -s | -g | ( -m file )

[ -m file] # multi rack json file specifying the leaf and spine names in the cluster

# a rear view left to right concatenation of json files.

# Each json file must contain SPINE_NAME,

# LEAF1_NAME and LEAF2_NAME keys (see also -g )

# A rack can be an Exadata machine or Big Data Appliance.

[ -s ] # Bda is in "ship" configuration.

[ -g ] # Generate file "sample-multi-rack.json" (Use with -m).

# The json file lists racks in alphabetical order.

# Rack elements must be reordered in rack order.

Cause

The usage was changed and -s switch must be used instead of BdaShip.json.

Even running bdacheckib -s may see the following:

[root@bda01 bda]# bdacheckib -s
bdacheckibx: entry for switch bdasw-ib1 not found in iblinkinfo output
bdacheckibx: entry for switch bdasw-ib2 not found in iblinkinfo output
bdacheckibx: entry for switch bdasw-ib3 not found in iblinkinfo output
[root@bda01 bda]#

This error may occur if the switches have already been configured with their customer-specified hostnames.

Solution

Run with "bdacheckib -s" command instead:

[root@bda01 bda]# bdacheckib -s

Note: If an error is shown like:

It will be necessary to perform the following:

1. Rename hosts to factory-ship hostnames.

OR

2. If the switches have been configured back to factory-ship hostnames, a switch reboot may be necessary before the newly set switch hostname is visible on the InfiniBand fabric.

Attachments

This solution has no attachment