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
Important: Review theRead Before Installing or Updating to HP-UX 11i booklet accompanying the HP-UX 11i v1 OE Media before installing or updating to HP-UX 11i v1.: HP-UX 11i Version 1 Installation and Update Guide > Appendix B Known Problems and Troubleshooting

Problems Configuring HP-UX 11i v1

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

Read these items before installing or updating to 11i.

cdrecord Application Requires Patch

The cdrecord application delivered with the XCDROAST-RUN fileset in the TC-OpenSource product requires kernel patch PHKL_24283 or one of its successors (including PHKL_26410 and PHKL_27225)

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 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.

NOTE: If /dev/floppy exists, hpuxci sets default attributes for the device. The code that does this does not null-terminate the string passed to atoi() which results in a segfault (segmentation fault). The fix for this will terminate the string correctly.

Auto-Port Aggregation Will Not Work on rp7410 Systems

The igelan driver for core rp2710 cards does not support Auto-Port Aggregation (APA).

What To Do

To fix this problem install patch PHNE_25833 (or any patch that supersedes it).

EISA Cards Not Supported on 64-bit OS

EISA I/O drivers for TermIO, FDDI, 100BT and Token Ring cards are supported on HP-UX 32-bit OS, but not 64-bit OS. You will not see an error or warning message stating that these EISA products will not work after installing or updating to 64-bit OS.

100BT HSC-FX Cards Do Not Work on HP-UX 11i v1

The100BT HSC-FX cards, J3514A#002 and J3516A#002, do not work under 11i. The card is claimed, but the link does not come up.

This card is supported on K-Class, D-Class and A-180 systems. If you are not sure whether or not the card is installed in your system, use the appropriate command:

ioscan -kfClan | grep J3514A#002 (on K-Class)

ioscan -kfClan | grep J3516A#002 (on A-180 or D-Class)

If the card is installed, you will see the hardware path, interface number and other details displayed on the screen.

To fix the problem, either install patch PHNE_22727 or replace the HSC-FX card with an HSC-TX card, J3514A#001 (K-class) or J3516A#001 (A-180 and D-Class). If you replace the card, you will also need an FX-to-TX converter. The converter is not an HP product but has been qualified for use with HP cards; it is made by Transition Networks, part number C/E-100BTX-FX-04(SC).

SCSI PCI Restrictions for OLA/R

Online addition and replacement (OLA/R) of PCI HBAs is available in HP-UX 11i v1 on the HP 9000 L-Class, N-Class, and Superdome systems. This feature allows you to add or replace a failed HBA without having to reboot the system.

Some restrictions in the ability to perform online addition (OLA) and/or online replacement (OLR) apply with these SCSI HBAs:

  • A4800A

  • A5149A

  • A5150A

  • A5159A

  • A5838A

You can find more information about SCSI HBA OLA/R restrictions by going to 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. Select the ola/r support link in the list on the left side of the page; this takes you to the SCSI HBA OLA/R restrictions.

SCSI PCI HBA Documentation Correction

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

The content for the "Setting the SCSI IDs" section of the "Installing the Adapter" chapter is not correct. The correct content for the "Setting the SCSI IDs" section is as follows:

You must assign the SCSI host bus adapter and each SCSI device a separate SCSI ID (0 through 15 for a 16-bit SCSI bus). The device's priority on the SCSI bus is determined by the device's SCSI ID. The order of 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. A device with SCSI ID 7 has the highest priority, and one with SCSI ID 8 has the lowest.

When you are assigning SCSI IDs, we recommend you give the SCSI host bus adapter higher priority than the other SCSI devices on the bus. SCSI ID 7 is the preset SCSI ID for your HP SCSI host bus adapter (giving it the highest priority on the SCSI bus). Set each of the other SCSI devices on the bus to one of the remaining SCSI ID's.

For a multi-initiator (High Availability [HA]) configuration-where multiple SCSI host bus adapters are connected to the same SCSI bus-the SCSI host bus adapter that carries the most traffic should be assigned a SCSI ID of 7 (giving it the highest priority), then you must change the SCSI ID of each of the remaining SCSI host bus adapter's on the bus from the preset setting (7), to the next highest priority remaining SCSI IDs (e.g. 6, 5, 4... and so on).

If you plan to boot your system from a hard disk drive on the SCSI bus, you should assign that drive the next highest priority unassigned SCSI ID. If there is only one SCSI host bus adapter (SCSI ID = 7), the hard disk drive would be assigned a SCSI ID of 6. If there are multiple SCSI host bus adapters, the hard disk drive would be assigned the next highest priority SCSI ID available after all of the SCSI host bus adapters have been assigned higher priority SCSI IDs.

The peripheral device SCSI IDs are usually set with jumpers or a switch on the peripheral. Refer to the peripheral manufacturer's instructions to determine the ID of each device and how to change it.

You must have no duplication of SCSI IDs on a SCSI bus-the system will hang or crash if duplicate SCSI IDs are on the bus.

See the "Checking SCSI Bus Compatibility" section of the Service and User Guide for details on conforming and changing SCSI IDs.

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

HP-UX Apache-based Web Server Requires LD Patch to Start and Stop

IMPORTANT: Due to an ld defect, you may encounter problems starting and stopping HP-UX Apache-based Web Server (hpuxwsApache). At the time of this writing, HP is unable to include a patch. To fix this problem, follow the steps below:

To verify and install the required version of ld and libdld for the HP-UX Apache-based Web Server:

  1. Verify that you are using ld and libdld version B.11.32 or higher. To determine the version, enter the following command:

    ld -V

  2. If the version number is less than B.11.32, install Patch PHSS_26560. See “Installing Patches” for more information on how to install patches.

  3. As root, manually start HP Apache using the following command:

    /opt/hpws/apache/bin/apachectl1 start

Additional Documentation

For detailed configuration and installation instructions, see the following HP Apache documentation in the paths listed below (or at http://machinename/hp_docs/apache/document after the web server is started):

HP Apache Admin Guide: /opt/hpws/hp_docs/apache/apache.admin.guide

HP Apache Release Notes: /opt/hpws/hp_docs/apache/apache.release.notes

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