After Reboot "ifconfig -a" Reports that eth8/eth9 are Missing and BDA Nodes are Inaccessible via the Client Network
(Doc ID 2069212.1)
Last updated on JANUARY 02, 2020
Applies to:
Big Data Appliance Integrated Software - Version 4.2.0 and laterLinux x86-64
Symptoms
After reboot of one or more BDA cluster nodes, the BDA nodes are inaccessible via the client network. From the admin network running 'ifconfig -a' reports eth8/eth9 are missing on these nodes.
This can be observed after Step 3 of a BDA installation or upgrade, or on any reboot.
Additional symptoms look like:
1. The rdma configuration file, /etc/rdma/rdma.conf is observed to be modified on one or more cluster nodes.
You can verify if /etc/rdma/rdma.conf has been modified with: 'rpm -V rdma'. A single line should be returned if the file is not modified from the default.
a) Example output from 'rpm -V rdma' when /etc/rdma/rdma.conf is not modified on a single node:
Note: You may also see that BDA nodes are inaccessible via the client network after reboot with 'ifconfig -a' reporting eth8/eth9 missing from the adm network even if the above 3 symptoms are not observed. During reboot if the servers come online before the switches do, then the rdma service startup will not see the VNICs on the switches. In this case a reboot of the servers is a good thing to try first. But try just one node first to see if the issue is resolved and then reboot the others one at a time.
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! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |