topic Re: SAM (Disk Devices) and ioscan does not match in Operating System - HP-UX

SAM (Disk Devices) and ioscan does not match

Alzhy — Mon, 16 Jun 2003 19:48:40 GMT

What could be wrong? Just finished installing Securepath to a Compaq Array. ioscan shows the two LUN's:
# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 0/0/1/0.4.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t4d0 /dev/rdsk/c0t4d0
disk 1 0/0/2/0.6.0 sdisk CLAIMED DEVICE HP 18.2GMAN3184MC
/dev/dsk/c1t6d0 /dev/rdsk/c1t6d0
disk 2 0/0/2/1.6.0 sdisk CLAIMED DEVICE HP 18.2GST318406LC
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
disk 5 255/0.0.0 sdisk CLAIMED DEVICE HSG80 LUN 0x60001FE1000C3B200009049038320007
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 6 255/0.0.1 sdisk CLAIMED DEVICE HSG80 LUN 0x60001FE1000C3B20000904903832000E
/dev/dsk/c12t0d1 /dev/rdsk/c12t0d1

But SAM sees only 1 LUN:
xqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqx
x Hardware Number Volume Total x
x Path of Paths Use Group Mbytes Description x
xlqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x
xx 0/0/1/0.4.0 1 Unused -- 32 HP DVD-ROM SCSI Dri ^ x
xx 0/0/2/0.6.0 1 LVM vg00 17366 HP 18.2GMAN3184MC x
xx 0/0/2/1.6.0 1 LVM vg00 17366 HP 18.2GST318406LC x
xx 255/0.0.0 2 Unused -- 86786 HSG80 LUN 0x60001FE x

Re: SAM (Disk Devices) and ioscan does not match

Alzhy — Mon, 16 Jun 2003 19:50:10 GMT

Btw, this is my SecurePath Status:

# spmgr display
Server: frfhpte3.sbcdo.com Report Created: Mon, Jun 16 13:49:37 2003
Command: spmgr display
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Storage: 5000-1FE1-000C-3B20
Load Balance: Off Auto-restore: Off
Path Verify: On Verify Interval: 30
HBAs: td0 td1
Controller: ZG04903832, Operational
ZG04706210, Operational
Devices: c12t0d0 c12t0d1

TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 0 c12t0d0 6000-1FE1-000C-3B20-0009-0490-3832-0007 4
255/0.0.0
Controller Path_Instance HBA Preferred? Path_Status
ZG04903832 no
c5t0d1 td0 no Standby
c9t0d1 td1 no Standby

Controller Path_Instance HBA Preferred? Path_Status
ZG04706210 no
c7t0d1 td0 no Active
c11t0d1 td1 no Available

TGT/LUN Device WWLUN_ID H/W_Path #_Paths
0/ 1 c12t0d1 6000-1FE1-000C-3B20-0009-0490-3832-000E 4
255/0.0.1
Controller Path_Instance HBA Preferred? Path_Status
ZG04903832 no
c5t0d2 td0 no Standby
c9t0d2 td1 no Standby

Controller Path_Instance HBA Preferred? Path_Status
ZG04706210 no
c7t0d2 td0 no Active
c11t0d2 td1 no Available

Re: SAM (Disk Devices) and ioscan does not match

Helen French — Mon, 16 Jun 2003 19:58:08 GMT

How many LUNs you actually have? First I would do is to install the latest patches, especially SAM cumulative patches and I/O related patches.

Re: SAM (Disk Devices) and ioscan does not match

Paul Sperry — Mon, 16 Jun 2003 19:59:56 GMT

In sam did you try
Diagnose missing disk
under actions?

Re: SAM (Disk Devices) and ioscan does not match

Alzhy — Mon, 16 Jun 2003 20:03:42 GMT

From spmgr and ioscan -- we've 2 LUN's from the Compaq array c12t0d0 (255/0.0.0) and c12t0d1 (255/0.0.1).

Yes I did try diagnose missing disk.. nothing changed..

Re: SAM (Disk Devices) and ioscan does not match

Elena Leontieva — Mon, 16 Jun 2003 20:05:16 GMT

You may want to check the Document id: DKKBRC00006641 entitled "Only first LUN of 3rd party disk array visible in SAM"

Re: SAM (Disk Devices) and ioscan does not match

Alzhy — Mon, 16 Jun 2003 20:07:36 GMT

May I know what is this document and where I can find DKKBRC00006641 ?

Re: SAM (Disk Devices) and ioscan does not match

Helen French — Mon, 16 Jun 2003 20:17:05 GMT

For the last question:

These are the Technical Knowledge Base documents. You need to get access to TKB from ITRC home page, then select "search by doc ID" and enter the document number there (DKKBRC00006641). This is the document you are looking for:

Only first LUN of 3rd party disk array visible in SAM DocId: DKKBRC00006641 Updated: 5/2/01 5:38:00 AM

PROBLEM
I attached a 3rd party disk array to my system. Although all configured LUNs
are visible with ioscan(1M) I only see the 1st LUN in SAM.CONFIGURATION
HP-UX 10.X, 11.X
SAMRESOLUTION
Typically devices that are unknown to SAM are unsupported by HP. Nevertheless
we may try our best to make SAM happy.

For unknown disk devices SAM uses the serial number to identify alternate PV
links. Some disk arrays (including Nikes and AutoRAIDs) show the same serial
number for all configured LUNs, so SAM needs a special handling in these cases.

A CRC checksum of the serial number can be found in the last 4 columns of the
12th field of ioscan -F:

e.g.:
# ioscan -FkCdisk | awk -F: '{print $18"\t"$12}'
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
STK OPENstorage 9176 0 0 2 2 0 0 0 0 57 145 86 53 249 250 207 23
^^^^^^^^^^^^^^
To make the disk array LUNs known to SAM we need to add an entry
to the file /usr/sam/lib/C/pd_devinfo.tx. Since Nike disk arrays also show
identical serial numbers we choose the type 'CLARIION' for this entry.

For the example STK disk array we could add (in one single line!):

DISK:::sdisk:::.*STK.*OPENstorage.*::::::::::::::
STK OPENstorage LUN:::::DISK_ARRAY,CLARIION

Now SAM should be able to show and configure all LUNs of the disk array.
However SAM is unable to distinguish the different LUNs since they show up with
the same serial number. The result may be the following warning message:

"SAM has detected unused disks with non-unique device identifications. These
disks may have multiple hardware paths. If this is the case, use the Disk
Devices Action "Mark Disk As Used" on the entries that correspond to additional
hardware paths to prevent possible data corruption."

Caveats:

Please note that the pd_devinfo.tx file may be overwritten by any SAM patch
installation. All changes need to be re-applied in such situations!

Please note that changing the pd_devinfo.tx file is unsupported by HP. It is
only a workaround to make SAM work with unsupported devices!

Re: SAM (Disk Devices) and ioscan does not match

Steven E. Protter — Mon, 16 Jun 2003 20:24:39 GMT

Good one Elena.

I was stumped.

SEP