After OL6 to OL7 Migration Reboot Step or After Re-imaging The Client Network is Not Created
(Doc ID 2792694.1)
Last updated on JULY 20, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.13.0 and laterx86_64
Symptoms
After Migrating Oracle Linux 6 (OL6) to Oracle Linux 7 (OL6) using the documentation "10.8.3 Oracle Linux 6 to Oracle Linux 7 Migration Steps", and successfully completing the ./bdareimagenode.sh and the subsequent reboot step, the client network on the reimaged host is found to be down. This can happen after re-imaging a server as well.
1. ssh to the affected host does not work. It is possible to ssh into the host admin network.
2. Logging into the host admin network with something like: ssh <HOSTNAME>-adm, and running ifconfig shows that the bondeth0 interface is not present.
3. Following General advice and a recommended flow for diagnosing client network issues on BDA (Doc ID 1984827.1), indicates no underlying problems on the client network itself.
4. However running /opt/oracle/bda/network/BdaUserConfigEoib to create the client network fails with:
:no ports found for leaf1
:input was
root@<IP_ADDRESS>'s password:
Permission denied, please try again.
root@<IP_ADDRESS>'s password:
:exit 1
*** <SWITCH> *** Out of branches near "fail <- generate json for gw ports" called from "parse ports from expect"
*** <SWITCH> *** Syntax error on line 3:
Permission denied, please try again.
root@<IP_ADDRESS>'s password:
bdanetworktool.main: generation of /opt/oracle/bda/network/leaf1gwp.json failed
Note: Check under /root/install_logs/ for logs containing further failure details.
6. Details on the failing script are in: BdaUserConfigEoib Fails with Password errors, "Permission denied, please try again." (Doc ID 2114968.1).
7. In the case here, the 'root' password on the two leaf switches, <RACK>sw-ib2 and <RACK>sw-ib3 are not the default which is required by BdaUserConfigEoib.
8. Checking the bdanetworktool logs at:
- /root/install_logs/bdanetworktool.err
- /root/install_logs/bdanetworktool.log
shows that the bdanetworktool can not log into the leaf switches and gather the information required to create the client network.
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 |