bdacheckib on BDA V4.3-V4.5 Raises "iblinkinfo: invalid option -- 'R'"

Asset ID:	1-72-2190814.1
Update Date:	2016-11-04
Keywords:

Solution Type Problem Resolution Sure

Solution 2190814.1 : bdacheckib on BDA V4.3-V4.5 Raises "iblinkinfo: invalid option -- 'R'"

Applies to:

Big Data Appliance X4-2 Hardware - Version All Versions and later
Big Data Appliance Integrated Software - Version 4.3.0 to 4.5.0 [Release 4.3 to 4.5]
Linux x86-64

Symptoms

On BDA V4.3-BDA V4.5 running bdacheckib raises the following:

bdacheckib:

iblinkinfo: invalid option -- 'R'

Usage: iblinkinfo [options]

Options:
--node-name-map node name map file
--switch, -S <port_guid> start partial scan at the port specified by
<port_guid> (hex format)
--port-guid, -G <port_guid> (same as -S)
--Direct, -D <dr_path> start partial scan at the port specified by <dr_path>
--all, -a print all nodes found in a partial fabric scan
--hops, -n Number of hops to include away from specified node
--down, -d print only down links
--line, -l (line mode) print all information for each link
on a single line
--additional, -p print additional port settings (PktLifeTime,
HoqLife, VLStallCount)
--load-cache filename of ibnetdiscover cache to load
--diff filename of ibnetdiscover cache to diff
--diffcheck <key(s)> specify checks to execute for --diff
--filterdownports filename of ibnetdiscover cache to filter downports
--outstanding_smps, -o specify the number of outstanding SMP's
which should be issued during the scan
--switches-only Output only switches
--cas-only Output only CAs
--config, -z use config file, default: /etc/infiniband-diags/ibdiag.conf
--Ca, -C Ca name to use
--Port, -P Ca port number to use
--timeout, -t timeout in ms
--sm_port, -s SM port lid
--m_key, -y M_Key to use in request
--errors, -e show send and receive errors
--verbose, -v increase verbosity level
--help, -h help message
--version, -V show version

bdacheckib0: json ib link input < 3 els

Cause

This is Internal Bug 22123892 BDACHECKIB FAILED WITH "IBLINKINFO: INVALID OPTION -- 'R'".

This is due to a bug in bdacheckib.

Solution

This is fixed in BDA V4.6.0. To workaround the issue in lower releases follow these steps:

1. On Node1 as 'root' user copy /opt/oracle/bda/bin/bdacheckib to /opt/oracle/bda/bin/bdacheckib2.

# cp -p /opt/oracle/bda/bin/bdacheckib to /opt/oracle/bda/bin/bdacheckib2

2. Edit /opt/oracle/bda/bin/bdacheckib2 so that all lines which contain iblinkinfo do not contain -R (remove -R from those lines).

3. Run bdacheckib2 instead of bdacheckib.

# bdacheckib2

Sample output will be like:

LINK bda1sw-ib3.15A ... bda02.HCA-1.2 UP
LINK bda1sw-ib3.15B ... bda01.HCA-1.2 UP
LINK bda1sw-ib3.14A ... bda04.HCA-1.2 UP
LINK bda1sw-ib3.14B ... bda03.HCA-1.2 UP
LINK bda1sw-ib3.13A ... bda06.HCA-1.2 UP
LINK bda1sw-ib3.13B ... bda05.HCA-1.2 UP
LINK bda1sw-ib2.15A ... bda02.HCA-1.1 UP
LINK bda1sw-ib2.15B ... bda01.HCA-1.1 UP
LINK bda1sw-ib2.14A ... bda04.HCA-1.1 UP
LINK bda1sw-ib2.14B ... bda03.HCA-1.1 UP
LINK bda1sw-ib2.13A ... bda06.HCA-1.1 UP
LINK bda1sw-ib2.13B ... bda05.HCA-1.1 UP

Attachments

This solution has no attachment