- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: hostname resolution not working with lan0 down...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-04-2015 11:57 PM
03-04-2015 11:57 PM
for a set of private IPs on same subnet on lan1, whenever the lan0 is down, host name resolution doesn't work and gets stuck.
# ifconfig lan0 down
# ping clientdp
<<no response, stuck>>
however when using ip for the same instead of hostname, it works
# ping 192.0.0.12
PING 192.0.0.12: 64 byte packets
64 bytes from 192.0.0.12: icmp_seq=0. time=0. ms
using hostname, no response
# ping serverdp
<<no response, stuck>>
when lan0 is up, it works fine
# ifconfig lan0 up
# ping clientdp
PING clientdp: 64 byte packets
64 bytes from 192.0.0.12: icmp_seq=0. time=0. ms
# ping serverdp
PING serverdp.ind.hp.com: 64 byte packets
64 bytes from 192.0.0.13: icmp_seq=0. time=1. ms
the objective is that Dataprotector uses the private IPs only, and not public IPs for taking backup, but due to lack of host name resolution with lan0 down, the backup doesnt even start. any other idea on forcing dp to use only the private ip for communication/backup process.
ps:/etc/hosts file has "192.0.0.12 clientdp" & "192.0.0.13 serverdp" as alias
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2015 03:21 AM