HP-UX 11i Version 1 Installation and Update Guide, December 2003

Known Problems and Troubleshooting
Problems Configuring HP-UX 11i v1
Appendix B 197
system through the /usr/sbin/exportfs -au command. The file
systems will be re-exported if they have the entries in /etc/exports file
at the starting phase again, but not the file systems exported
interactively by the NFS packages.
How Do You Know
if This Affects
You?
You are affected if you enable AutoFS on an HA server.
What To Do Enabling AutoFS on the HA NFS server needs to be done with caution.
However, this kind of configuration is fully supported if one of these two
actions is taken before stopping the AutoFS daemon:
1. Manually move all NFS packages to the adoptive server node.
2. Halt all NFS packages.
The Auto FS daemon can be stopped either with the kill -9 command,
the nfs.client script, or the nfs.server script.
Once the AutoFS daemon is restarted, the NFS packages can be
restarted or manually moved back to the server node. AutoFS can be
restarted either with the /usr/sbin/automountd command or the
nfs.client script.
Hardware Information Not Captured on Systems With
Floppy Drive
On systems with a floppy-disk drive attached, hardware information will
not be captured in the System Configuration Repository (SCR) under 11i.
After updating a system with a floppy drive from 10.20 to 11i, you will
find a core file in /usr/dmi/bin, and hpuxci (HP-UX DMI Component
Instrumentation) will not be running.
How Do You Know
If This Affects
You?
This problem affects you if there is a floppy drive attached to (or installed
in) your system, and you use the System Configuration Repository (SCR)
to store hardware information. Since the hpuxci is not running,
hardware information will not be captured. The problem occurs if
/dev/floppy exists.
What To Do A fix for the problem will be made available in the earliest follow-up
patch release for 11i. In the meantime, if you depend on the SCR, you
should either not update to 11i, or remove the floppy drive.