Configuring HP-UX For Peripherals

Chapter 1 29
Getting Started
Viewing the System Configuration with ioscan
The card instance number is assigned by the operating system to the
interface card and reflects the order ioconfig binds that class of
interface card to its driver when it boots.
Instance is stored in two files — /etc/ioconfig and /stand/ioconfig.
Information in these files retain their information across reboots, unless
one is corrupted or missing, in which case, ioinit will rebuild the entire
/dev structure. (If this occurs, you would have to recreate any
customized permissions or files.)
An Example Showing Correlation Between Card Instance and
Device Files
The following example shows ioscan output taken from a Model 735.
This example shows how card instance number and hardware path
elements map directly into the device special file /dev/dsk/c1t5d0 as
card instance, target number, and device number.
Typically, the card instance maps as the digit after the letter c (or for
terminals, the number after tty). For this example, the digit is 1, as
shown in the second field of the first entry below.
Note, the card instance designated in the device special file refers to the
interface card, not to the instance number of the peripheral device
attached to the card. (Ignore those numbers. This is a departure from the
LU concept of previous HP-UX Series 800 releases. LU numbers were
similar to device instance numbers and are not used.)
The card instance number is unique only for the specific class (in this
case, ext_bus) of interface. Thus, for example, the tty class of interface
has its own sequence of card instance numbers, beginning with zero,
which appear in its device files.
/usr/sbin/ioscan -fn -H 2/0/7
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
ext_bus 1 2/0/7 c700 CLAIMED INTERFACE Built-in F/W SCSI
target 3 2/0/7.5 target CLAIMED DEVICE
disk 2 2/0/7.5.0 sdisk CLAIMED DEVICE HP C2247
/dev/dsk/c1t5d0 /dev/rdsk/c1t5d0
...