IDENTIFIER vs bus-target-lun in output from "hwmgr view device"

[Orjan Petersson]

We have 2 clustered ES-80 servers running 5.1b PK5, connected to an EVA5000.

For the vdisks on the EVA, the output from
# hvmgr view device
have two kinds of output lines:

736: /dev/disk/dsk34c COMPAQ HSV110 (C)COMPAQ bus-0-targ-1-lun-115

739: /dev/disk/dsk37c COMPAQ HSV110 (C)COMPAQ IDENTIFIER=118

where the number after IDENTIFIER= is the LUN assigned to the disk in the EVA.

Why do we get some disks showing bus-target-lun, and some showing IDENTIFIER? What is the difference, if any?
--
Orjan

[Vladimir Fabecic · Accepted solution]

It is simple. If OS ID is assigned, then you have identifier in output. If OS ID is NOT assigned, then you have bus-target-lun.
If you presented vdisk, without assigning OS ID and did hwmgr -scan scsi, you will have bus-target-lun, even if you assign OS ID later.
OS ID is not needed for TRU64, but can be usefull for locating in case of some trouble.

[Orjan Petersson]

Vladimir answered the question. Thanks!