Asset ID: |
1-72-1566168.1 |
Update Date: | 2017-01-05 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1566168.1
:
Connecting From BDA Node To IB Switch Using ssh Failed With Error "No route to host"
Related Items |
- Big Data Appliance X3-2 Full Rack
- Big Data Appliance X3-2 Hardware
- Big Data Appliance X3-2 In-Rack Expansion
- Big Data Appliance Hardware
- Big Data Appliance X3-2 Starter Rack
|
Related Categories |
- PLA-Support>Eng Systems>BDA>Big Data Appliance>DB: BDA_EST
|
In this Document
Created from <SR 3-7354103481>
Applies to:
Big Data Appliance Hardware - Version All Versions and later
Big Data Appliance X3-2 Hardware - Version All Versions and later
Big Data Appliance X3-2 Full Rack - Version All Versions and later
Big Data Appliance X3-2 Starter Rack - Version All Versions and later
Big Data Appliance X3-2 In-Rack Expansion - Version All Versions and later
Linux x86-64
Symptoms
Connecting from any of the BDA nodes to any of the IB switches using ssh failed with error: No route to host
[root@node01 ~]# ssh xxxxsw-ib1
ssh: connect to host xxxxsw-ib1 port 22: No route to host
Cause
The issue was due to all the switches (3 IB switches and 1 cisco switch) had IP addresses that are not on the admin network.
Oracle BDA requires all admin IPs to be on the same admin network. This includes the eth0 IPs of the servers, the ILOM IPs of the servers, the 3 IB switch IPs, the Cisco switch IP, and the PDU IPs.
Solution
Solution 1:
=======
Reassign the 4 switches (3 IB switches and 1 cisco switch) to fit inside the range and then perform the following steps to solve the issue:
1. Choose new IP addresses for the switches that are in the admin network IP ranges.
2. Update the installation worksheets.
3. Update the DNS servers so that the existing switch hostnames point to the new IP addresses.
4. Update the spreadsheets and generates a new BdaDeploy.json file.
5. Run through the EIS process to change the IPs on all 4 switches, rebooting the switches if needed.
6. Update the BdaDeploy.json file on all BDA servers. In other words, the newly generated BdaDeploy.json file (step 4) must be copied to all of the BDA servers in the rack, replacing the existing /opt/oracle/bda/BdaDeploy.json.
7. Update /etc/hosts on all BDA servers
8. Restart dnsmasq on all BDA servers
9. Confirm that BDA nodes can SSH to all switches. The ability to SSH into the Cisco switch is not necessarily needed, but SSH-ing into all 3 IB switches must work.
Solution 2:
=======
Reimage/Reinstall/Reconfigure the BDA rack to ensure that all admin IPs to be on the same admin network.
Attachments
This solution has no attachment