bdachecknet-cluster Fails to Resolve Client IP Addresses with "ip to name to ip resolve failed for ip address: <CLIENT_IP_HOSTx> (!= <PRIVATE_IP_HOSTx>)"
(Doc ID 2558311.1)
Last updated on JULY 20, 2024
Applies to:
Big Data Appliance Integrated Software - Version 4.11.0 and laterx86_64
Symptoms
Running bdachecknet-cluster fails with errors like:
...
bdachecknet-cluster: test client network (eoib) resolve and reverse resolve
bdachecknet-cluster: ip to name to ip resolve failed for ip address: <CLIENT_IP_HOSTx> (!= <PRIVATE_IP_HOSTx>)
...
bdachecknet-cluster: host name json element does not correspond to json element ip address: <HOSTNAMEx> (!= <PRIVATE_IP_HOSTx> index 0)
bdachecknet-cluster: test client network (eoib) resolve and reverse resolve
bdachecknet-cluster: ip to name to ip resolve failed for ip address: <CLIENT_IP_HOSTx> (!= <PRIVATE_IP_HOSTx>)
...
bdachecknet-cluster: host name json element does not correspond to json element ip address: <HOSTNAMEx> (!= <PRIVATE_IP_HOSTx> index 0)
The errors indicate bdachecknet-cluster expects the output to be <CLIENT_IP_HOSTx> but instead it is <PRIVATE_IP_HOSTx>, which indicates that the nameserver is returning the host's private IP address instead of the client IP address.
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 |