Ignite-UX Release Notes HP-UX 11iv1, HP-UX 11iv2 and HP-UX 11iv3 (762792-001, March 2014)

Three special variables: _hp_nfs_mount_opts, _hp_nfs_mount_retries and
_hp_tftp_cmds can be used where special networks (like WAN) require tuning of the NFS
and tftp services to increase performance or reliability. See instl_adm(4).
It is highly recommended that NFS over TCP be enabled on Ignite-UX servers. Problems have
been seen when only NFS over UDP is enabled (which is the default). To determine whether
NFS over TCP is enabled run the following command on your server:
# rpcinfo | grep nfs
100003 2 udp 0.0.0.0.8.1 nfs superuser
100003 3 udp 0.0.0.0.8.1 nfs superuser
100003 2 tcp 0.0.0.0.8.1 nfs superuser
100003 3 tcp 0.0.0.0.8.1 nfs superuser
If you see the last two lines, then NFS over TCP is enabled and nothing needs to be done. If
not, then it needs to be enabled. To enable it, "loopback" must be resolvable to the IP
address 127.0.0.1 and /etc/services must be accessible. In a standard installation of
HP-UX, there is an entry for "loopback" found in /etc/hosts which looks like:
127.0.0.1 localhost loopback
The default name service switch behavior for host name resolution does not look at /etc/
hosts. It first tries DNS, and if it cannot resolve the host name, it quits. In the default case,
when the nfs.server startup script is run, it will not enable NFS over TCP unless you are
using DNS and your DNS includes data for "loopback". If you do not use DNS, or if you
do and DNS does not include "loopback", then it is impossible to enable NFS over TCP
unless you provide and/or modify an /etc/nsswitch.conf file.
To enable NFS over TCP, you will either have to add "loopback" to your DNS database if
that is your only option, or to configure an /etc/nsswitch.conf file so that the host name
resolution via the name service switch will also search files (/etc/hosts). In addition, you
have to make sure the name service switch service behavior for services also searches files
(/etc/services). There are at least six name service switch template file provided in /etc.
If you have an /etc/nsswitch.conf file already, you will need to change it to include a
hosts and services file lookup. For example these lines might look like:
hosts: dns [NOTFOUND=continue] files [NOTFOUND=return]
services: nis [NOTFOUND=continue] files
These entries will tell the name service switch for host name resolution to first try DNS as before,
and if that fails, then continue on (instead of quitting) to look at /etc/hosts. Note that
[NOTFOUND=continue] is the default behavior with /etc/nsswitch.conf usage, so an
equivalent entry might just say "dns files". If resolving via files fails to find a name, then the
name service switch would return a failure.
The name service switch behavior for services would (using the line above) use NIS first and
fall back to files (/etc/services) if it cannot find the service name being searched for.
If there is no /etc/nsswitch.conf file, then the template /etc/nsswitch.hp_defaults
contains all the default name service switch behaviors of HP-UX. Assuming you want to preserve
all other networking behaviors, this would be a good starting point. You would copy that file
to /etc/nsswitch.conf, and then edit the hosts and services lines to look like the one
above.
Once the changes are made, you will have to stop and restart the NFS server on your Ignite-UX
server to enable NFS over TCP:
# /sbin/init.d/nfs.server stop
# /sbin/init.d/nfs.server start
Repeat running the rpcinfo command above. You should now see NFS over TCP enabled.
26 Known problems and workarounds