Oracle Big Data Appliance V2.1.1 preinstall-checkip.sh Raises Errors Pinging Factory IP Addresses Existing on a Different Subnet
(Doc ID 1559399.1)
Last updated on MARCH 23, 2014
Applies to:Big Data Appliance Integrated Software - Version 2.1.1 and later
Running <rack_name>-preinstall-checkip.sh generated by the Oracle Big Data Appliance Configuration Utility to ensure the specified names and IP addresses for Oracle Big Data Appliance were added correctly to the name server, and they do not conflict with the existing network configuration raises errors pinging some of the Factory IP addresses existing on a different subset. Basically to perform the validation, <rack_name>-preinstall-checkip.sh, ensures that the new public IP addresses setup exist in DNS, but the private (Factory) IPs do not. Hence the script issues an ERROR if it can find/ping any of the private/Factory IP addresses. In the output below, some of the Factory IP addresses raise an ERROR as they can be pinged.
For example some of the Factory IPs can be pinged:
ERROR : 192.168.1.105 pings
SUCCESS : 192.168.1.106 does not ping
ERROR : 192.168.1.107 pings
SUCCESS : 192.168.1.108 does not ping
ERROR : 192.168.1.109 pings
ERROR : 192.168.1.110 pings
SUCCESS : 192.168.1.111 does not ping
SUCCESS : 192.168.1.112 does not ping
ERROR : 192.168.1.113 pings
ERROR : 192.168.1.114 pings
Can not ping some InfiniBand Bonded IP Addresses (bondib0)
ERROR : 192.168.10.1 pings
ERROR : 192.168.10.2 pings
ERROR : 192.168.10.3 pings
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