HP NetRAID-4M Configuration and Upgrade Guide (Release 5)

Chapter 9 Issues and Problem Resolution
70
Background: UnixWare 7.1.1 comes with a feature called MPIO (multi-processing
IO), a feature similar to clustering where two controllers can access the same hard
disk. MPIO is not installed by default but can be easily selected. MPIO seems to be
interfering with the boot process.
Workaround: Re-install UnixWare without MPIO.
66 Cannot distinguish PCI subsystem vendor ID
Problem: During UnixWare driver installation, by default, the wrong vendor ID is
assigned to the NetRAID-4M RAID controller.
Background: The first implementation of PCI provided vendor and device ID for
mapping device drivers to adapters. This is what UnixWare implemented and
continues to implement. Later in the evolution of PCI, generic PCI interface chips,
such as the one used in this adapter, became available. Multiple vendors started to
use these chips to implement different functionality. An extension to the original
PCI device driver mapping scheme was required so that device driver mismapping
did not occur between PCI options using the same generic interface chips and having
the same PCI vendor and device ID. The extension was a new set of fields on the
PCI option called the subvendor and subsystem ID fields. Since UnixWare only
implements matching of device drivers to PCI options using the vendor ID and
device ID, driver mismatching can occur. The UnixWare DCU (Device
Configuration Utility) can mismatch other vendor's drivers to the NetRAID-4M
controller and vice versa. Lack of any facility to map device drivers to PCI options
using PCI all of the vendor/device/subvendor/subsystem ids is a generic UnixWare
problem.
Workaround: In general, this problem can arise during boot container installations
and data container installations. In order to ensure that the problem does not occur,
use the UnixWare DCU to ensure that the hpnraid driver is assigned to the hpnraid
card. During driver installation, the mismatch must be manually corrected at the
DCU by removing the wrong ID and selecting a proper one from the list. Complete
the following steps to manually correct the ID:
1. Enter the DCU:
o During a boot container installation, enter the DCU when prompted.
o After a data container installation and before the CLI is run, run /sbin/d.
2. Use the Software Device Configuration to deselect all drivers for hardware that
are not present, or not being used on the system once in the DCU.