- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: HPUX odd hostname+networking issue
Operating System - HP-UX
1752421
Members
6005
Online
108788
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
тАО11-12-2010 07:26 AM
тАО11-12-2010 07:26 AM
I've just done a clean HPUX 11.31 install on an RX2600 from DVD media.
The install went fine, big package set no problems.
the hostname of the machine is igniteux01 and is set in netconf, no issues.
[quote]
HOSTNAME=igniteux01
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1
[/quote]
when the machine boots and I run "hostname" it returns "igniteux01"
however if I run "uname -n" it returns "igniteux" rather than "igniteux01"
I have no idea whats causing uname to drop the 01. This is pretty much the first boot after install so nothings been set.
I'm also having some odd networking issues with the machine.
To debug this I've set nsswitch.conf to resolve from files only.
[quote]
hosts: files
[/quote]
if I ping localhost I a 5 minute delay, then it starts responding
[quote]
# ping localhost
PING localhost: 64 byte packets
64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms
[/quote]
but it really is approx 300 seconds before it starts to run, almost as if it's doing a lookup in the background and waiting for it to time out. if I ping 127.0.0.1 it responds straight away.
if I do an nslookup (remember it's working on files only) it responds straight away
# nslookup
Using /etc/hosts on: igniteux01
> localhost
Using /etc/hosts on: igniteux01
looking up FILES
Name: localhost
Address: 127.0.0.1
Aliases: loopback
I suspect this is all down to the igniteux01/igniteux naming issue, so I'd like to resolve/understand that and then move on.
The install went fine, big package set no problems.
the hostname of the machine is igniteux01 and is set in netconf, no issues.
[quote]
HOSTNAME=igniteux01
OPERATING_SYSTEM=HP-UX
LOOPBACK_ADDRESS=127.0.0.1
[/quote]
when the machine boots and I run "hostname" it returns "igniteux01"
however if I run "uname -n" it returns "igniteux" rather than "igniteux01"
I have no idea whats causing uname to drop the 01. This is pretty much the first boot after install so nothings been set.
I'm also having some odd networking issues with the machine.
To debug this I've set nsswitch.conf to resolve from files only.
[quote]
hosts: files
[/quote]
if I ping localhost I a 5 minute delay, then it starts responding
[quote]
# ping localhost
PING localhost: 64 byte packets
64 bytes from 127.0.0.1: icmp_seq=0. time=0. ms
[/quote]
but it really is approx 300 seconds before it starts to run, almost as if it's doing a lookup in the background and waiting for it to time out. if I ping 127.0.0.1 it responds straight away.
if I do an nslookup (remember it's working on files only) it responds straight away
# nslookup
Using /etc/hosts on: igniteux01
> localhost
Using /etc/hosts on: igniteux01
looking up FILES
Name: localhost
Address: 127.0.0.1
Aliases: loopback
I suspect this is all down to the igniteux01/igniteux naming issue, so I'd like to resolve/understand that and then move on.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2010 07:58 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2010 08:40 AM
тАО11-12-2010 08:40 AM
Re: HPUX odd hostname+networking issue
the hostname issue I knew about, but thought was an old legacy issue that had been resolved, changing it to ignite01 was simpler than the additional configuration requried.
I have no idea why ipodes wasn't in nsswitch.conf, I didn't notice it missing either, I've just added it and the box has pretty much come to life.
thanks,
I have no idea why ipodes wasn't in nsswitch.conf, I didn't notice it missing either, I've just added it and the box has pretty much come to life.
thanks,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2010 05:48 PM
тАО11-12-2010 05:48 PM
Re: HPUX odd hostname+networking issue
> I have no idea why ipodes wasn't in nsswitch.conf
nsswitch.conf is woefully lacking in documentation. The examples in /etc are not useful either. ipnodes is used for IPv6 compatibility and can be backported to 11.11 so all your systems have the same nsswitch.conf file. Here's a useful version with DNS as a fallback:
passwd: files
group: files
hosts: files [NOTFOUND=continue UNAVAIL=continue] dns
ipnodes: files
services: files
networks: files
protocols: files
rpc: files
publickey: files
netgroup: files
automount: files
aliases: files
I would not add dns to ipnodes unless you know that your DNS server understands IPv6 addresses (whether you use them or not). Otherwise, you may experience connection delays as the local resolver tries to identify an IP given a hostname. Use nsquery rather than nslookup for better information about hostname/IP lookups.
Bill Hassell, sysadmin
nsswitch.conf is woefully lacking in documentation. The examples in /etc are not useful either. ipnodes is used for IPv6 compatibility and can be backported to 11.11 so all your systems have the same nsswitch.conf file. Here's a useful version with DNS as a fallback:
passwd: files
group: files
hosts: files [NOTFOUND=continue UNAVAIL=continue] dns
ipnodes: files
services: files
networks: files
protocols: files
rpc: files
publickey: files
netgroup: files
automount: files
aliases: files
I would not add dns to ipnodes unless you know that your DNS server understands IPv6 addresses (whether you use them or not). Otherwise, you may experience connection delays as the local resolver tries to identify an IP given a hostname. Use nsquery rather than nslookup for better information about hostname/IP lookups.
Bill Hassell, sysadmin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP