Configuration requirements for Tru64 UNIX on HP AlphaServer hosts

You must configure the operating system before you can use Tru64 UNIX on HP AlphaServer hosts with the system.

Before you begin

Before you configure the host operating system, the following tasks must be completed:
  • Your system must be installed and operational.
  • You must install the appropriate host bus adapter (HBA) and driver on your host system.

About this task

After the prerequisite tasks are complete, use the following general steps to configure your Tru64 UNIX host system.

Procedure

  1. Zone the host to the system on the Fibre Channel SAN.
  2. Configure and map volumes to the host.
  3. For Tru64 UNIX 5.1 and later versions, you can discover the disks by using the hwmgr scan scsi command.

    The disks are discovered as IBM 2145 disks, and the number of discovered devices depends on the number of adapters and zoned paths to the system.

  4. Optionally, check the status and number of attached disks by using the following commands:
    • hwmgr view devices
    • hwmgr show scsi
    • hwmgr show components

Example

The following example shows output from the hwmgr view devices command:
# hwmgr v d
 HWID: Device Name          Mfg      Model            Location
 ------------------------------------------------------------------------------
    4: /dev/dmapi/dmapi
    5: /dev/scp_scsi
    6: /dev/kevm
  104: /dev/disk/dsk0c      COMPAQ   BD03685A24       bus-1-targ-0-lun-0
  105: /dev/disk/dsk1c      COMPAQ   BD036635C5       bus-1-targ-1-lun-0
  106: /dev/disk/cdrom0c    TEAC     CD-W216E         bus-2-targ-0-lun-0
  107: /dev/random
  108: /dev/urandom
  246: /dev/disk/dsk76c     IBM      2145             bus-0-targ-5-lun-0
  247: /dev/disk/dsk77c     IBM      2145             bus-0-targ-5-lun-1
  248: /dev/disk/dsk78c     IBM      2145             bus-0-targ-5-lun-2
  249: /dev/disk/dsk79c     IBM      2145             bus-0-targ-5-lun-3
  250: /dev/disk/dsk80c     IBM      2145             bus-4-targ-4-lun-4
The following example shows output from the hwmgr show scsi command:
# hwmgr sh s

        SCSI                DEVICE    DEVICE  DRIVER NUM  DEVICE FIRST
 HWID:  DEVICEID HOSTNAME   TYPE      SUBTYPE OWNER  PATH FILE   VALID PATH
-------------------------------------------------------------------------
  104:  0        es47       disk      none    2      1    dsk0   [1/0/0]
  105:  1        es47       disk      none    0      1    dsk1   [1/1/0]
  106:  2        es47       cdrom     none    0      1    cdrom0 [2/0/0]
  246:  77       es47       disk      none    2      8    dsk76  [0/6/0]
  247:  78       es47       disk      none    2      8    dsk77  [4/2/1]
  248:  79       es47       disk      none    2      8    dsk78  [0/6/2]
  249:  80       es47       disk      none    0      8    dsk79  [4/7/3]
  250:  3        es47       disk      none    0      8    dsk80  [4/7/4]
# hwmgr show scsi -full -id 250

        SCSI                DEVICE    DEVICE  DRIVER NUM  DEVICE FIRST
 HWID:  DEVICEID HOSTNAME   TYPE      SUBTYPE OWNER  PATH FILE   VALID PATH
-------------------------------------------------------------------------
  250:  3        es47       disk      none    0      4    dsk80  [4/7/4]

      WWID:01000010:6005-0768-0193-8100-5000-0000-0000-0014

      BUS   TARGET  LUN   PATH STATE
      ---------------------------------
      4     7       4     valid
      3     5       4     valid
      0     5       4     valid
      4     2       4     valid
#