On BDA V4.7 the New Utility bdaibstatus Replaces bdacheckvnics

Asset ID:	1-71-2229626.1
Update Date:	2018-03-02
Keywords:

Solution Type Technical Instruction Sure

Solution 2229626.1 : On BDA V4.7 the New Utility bdaibstatus Replaces bdacheckvnics

Applies to:

Big Data Appliance Hardware - Version Not Applicable and later
Linux x86-64

Goal

The goal is to describe the new BDA V4.7 bdaibstatus utility and detail how to run it successfully on BDA V4.7 OL6 where it has some known issues.

Solution

Known Issues

1. On BDA V4.7 bdaibstatus throws an error when running the version that shipped with the 4.7 release. The utility fails with errors like below.

# bdaibstatus

bda0x ib0 cat: /sys/class/net/bondib0/slave_ib0/operstate: No such file or directory
yes yes NO
bda0x ib1 cat: /sys/class/net/bondib0/slave_ib1/operstate: No such file or directory

These errors cannot be ignored. This note delivers a version of bdaibstatus which fixes these errors in the 4.7 release.

Overview

On BDA V4.7 the new utility bdaibstatus replaces bdacheckvnics. bdaibstatus has similar functionality/usage as bdacheckvnics. bdaibstatus checks the status of both the client network bondeth0 and its slaves eth8 and eth9 as well as the private network bondib0 and its slaves ib0 and ib1 by pinging the gateway for each network.

However on BDA V4.7 OL6 the bdaibstatus utility has some issues which which can be resolved by using the bdaibstatus provided here. See the section: "BDA V4.7 OL6 specific bdaibstatus usage".

Make sure to review How to Install Patch 25492065 BACKPORT REQUEST FOR BUG 25404501 ON TOP OF BDA V4.7.0 FOR ORACLE LINUX 6 (Patch) (Doc ID 2230522.1). The recommendation is to apply the patch in that note rather than applying the patched bdaibstatus in this note.

General bdaibstatus usage:

bdaibstatus has these options:

# bdaibstatus -h

Usage: bdaibstatus [-bsgpch]

-b Brief. No heading.

-s Test the passive network interface also. Temporarily make each passive slave interface active, ping the gateway from that slave, and then return the slave to passive mode.

-g Bring down the primary interface if both of the following are true:

• The primary interface is bad (fails to ping the gateway).

• The non-primary interface is good (successfully pings the gateway).

This parameter includes an implicit -s.

-p Display results for private InfiniBand interfaces only.

-c Display results for client network interfaces only.

-h Display this help information.

Output looks like:

# bdaibstatus

host if status actv primary pkey

============== === ====== ==== ======== =======

bdanode01 ib0 up yes yes NO

bdanode01 ib1 up no no NO

host if status actv primary switch gw port ping gw vlan

============== === ====== ==== ======= ====================== ========= ======= ======

bdanode01 eth9 up yes yes bdasw-ib3 0A-ETH-1 yes N/A

BDA V4.7 OL6 specific bdaibstatus usage

On BDA V4.7 OL6 use the bdaibstatus attached. bdaibstatus will be found in bdaibstatus.zip.

To use this file perform the following steps as 'root' user on the node you want the script to run:

1. Copy the bdaibstatus.zip file to any temporary staging directory, for example /tmp, on the the node where it will be executed.

2. Uncompress bdaibstatus.zip:

# unzip bdaibstatus.zip

Archive: bdaibstatus.zip
inflating: bdaibstatus

Verify:

# ls -l bdaibstatus

-rw-r--r-- 1 root root 5162 Feb 2 17:38 bdaibstatus

# md5sum bdaibstatus

42330b17b37eb7a111899f87f20666da bdaibstatus

4. Copy the bdaibstatus from the staging directory to /opt/oracle/bda/bin/bdaibstatus2 and make sure the permissions are set to 0755:

# cp /tmp/bdaibstatus /opt/oracle/bda/bin/bdaibstatus2
# chmod 0755 /opt/oracle/bda/bin/bdaibstatus2

5. Then you can invoke bdaibstatus2.

6. Output looks as below.

# bdaibstatus2

host if status actv primary pkey
============== === ====== ==== ======== =======
bdanode01 ib0 up yes yes NO
bdanode01 ib1 up no no NO

host if status actv primary switch gw port ping gw vlan
============== === ====== ==== ======= ====================== ========= ======= ======
bdanode01 eth8 up no no bdasw-ib3 0A-ETH-1 --- N/A
bdanode01 eth9 up yes yes bdasw-ib2 0A-ETH-1 yes N/A

Attachments

This solution has no attachment