Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX 11i Version 1.6 Installation and Configuration Guide: Itanium®-based Servers and Workstations > Appendix B Known Problems and Troubleshooting

Problems Configuring HP-UX 11i v1.6

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

Read these items before installing HP-UX 11i v1.6.

Enabling AutoFS on High Availability Servers Can Cause NFS Packages to be Dropped

Restarting NFS clients (with nfs.client stop/start) or NFS servers (with nfs.server stop/start) while NFS packages are running on the High Available (HA) server will cause the exported file systems that tie to NFS packages to be dropped.

This is because the SG-NFS exported file systems are handled interactively and they are not in the /etc/exports file. When stopping NFS clients or NFS servers, it will unexport all the file systems on the 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 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.

SCSI PCI HBA Documentation Correction

An error exists in the current manual for each of these SCSI PCI Host Bus Adapters (HBAs): A5150A, and A5159A

In the chapter about installing the adapter, under the heading "Setting the SCSI IDs," the first paragraph states that if you will be booting the system from a SCSI disk drive on the SCSI bus, you should give that drive the lowest SCSI ID on the bus. This is not correct.

The correct instruction is as follows:

  • If you plan to boot your system from a hard disk drive on the SCSI bus, you should assign that drive the highest priority available on the bus. A device's priority is determined by the device's SCSI ID. The order of the SCSI ID priorities (from highest to lowest) is 7, 6, 5, 4, 3, 2, 1, 0, 15, 14, 13, 12, 11, 10, 9, and 8. So, a device with SCSI ID 7 has the highest priority, and one with SCSI ID 8 has the lowest. Note that SCSI HBAs should always have the highest priority SCSI ID.

The following manuals are affected:

  • HP A4800A PCI FWD SCSI Host Bus Adapter Service and User Guide (A3725-96031, E0201), page 30

  • HP A5149A PCI Ultra2 SCSI Host Bus Adapter Service and User Guide (A5149-96003, E0201), page 31

  • HP A5150A PCI Dual Port Ultra2 SCSI Host Bus Adapter Service and User Guide (A5150-96002, E0201), page 35

  • HP A5159A PCI Dual Port FWD SCSI Host Bus Adapter Service and User Guide (A5159-96002), page 31

You can get a .pdf file of this notice through the HP-IT Resource Center (ITRC), at the following URL: http://itrc.hp.com

  1. Go to the area for knowledge trees

  2. Under "Hardware" select Networks

  3. Select mass storage connectivity

  4. Select scsi hba's

  5. Select technical support.

    This takes you to a page titled "scsi hba's." (You might want to bookmark this page, for future reference.)

  6. A link to the .pdf file is in the "technical notes" area at the top right of the page.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2002 Hewlett-Packard Development Company, L.P.