HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

Problems HPUX 11.31 and Fujitsu CentricStor VTA 1500

 
Vito Robar
Occasional Visitor

Problems HPUX 11.31 and Fujitsu CentricStor VTA 1500

Hi Gurus!

Please advise me.

Problem is connecting HPUX 11.31 Itanium host to CentricStor VTA 1500. With all previous versions of HPUX 11.00, 11.11 v1, 11.23 went everything OK.

Problem is that CentricStor presents to HPUX 11.31 virtual drives as one. So we can use only one drive regardles of 8 CLAIMED device files, which representing 8 configured drives on one ICP port. I think that the catch is in configuration of CentricStor regarding HPUX 11.31 and/or changing and tunning the device on HPUX 11.31 on example disable native multipath, changing flags, strings etc. via scsimgr commands.

ioscan -fnC tape (legacy): (THIS IS OK)
tape 33 0/7/1/0.2.28.255.0.0.0 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/33m /dev/rmt/c10t0d0BEST
/dev/rmt/33mb /dev/rmt/c10t0d0BESTb
/dev/rmt/33mn /dev/rmt/c10t0d0BESTn
/dev/rmt/33mnb /dev/rmt/c10t0d0BESTnb
tape 34 0/7/1/0.2.28.255.0.0.1 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/34m /dev/rmt/c10t0d1BEST
/dev/rmt/34mb /dev/rmt/c10t0d1BESTb
/dev/rmt/34mn /dev/rmt/c10t0d1BESTn
/dev/rmt/34mnb /dev/rmt/c10t0d1BESTnb
tape 35 0/7/1/0.2.28.255.0.0.2 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/35m /dev/rmt/c10t0d2BEST
/dev/rmt/35mb /dev/rmt/c10t0d2BESTb
/dev/rmt/35mn /dev/rmt/c10t0d2BESTn
/dev/rmt/35mnb /dev/rmt/c10t0d2BESTnb
tape 36 0/7/1/0.2.28.255.0.0.3 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/36m /dev/rmt/c10t0d3BEST
/dev/rmt/36mb /dev/rmt/c10t0d3BESTb
/dev/rmt/36mn /dev/rmt/c10t0d3BESTn
/dev/rmt/36mnb /dev/rmt/c10t0d3BESTnb
tape 37 0/7/1/0.2.28.255.0.0.4 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/37m /dev/rmt/c10t0d4BEST
/dev/rmt/37mb /dev/rmt/c10t0d4BESTb
/dev/rmt/37mn /dev/rmt/c10t0d4BESTn
/dev/rmt/37mnb /dev/rmt/c10t0d4BESTnb
tape 38 0/7/1/0.2.28.255.0.0.5 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/38m /dev/rmt/c10t0d5BEST
/dev/rmt/38mb /dev/rmt/c10t0d5BESTb
/dev/rmt/38mn /dev/rmt/c10t0d5BESTn
/dev/rmt/38mnb /dev/rmt/c10t0d5BESTnb
tape 39 0/7/1/0.2.28.255.0.0.6 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/39m /dev/rmt/c10t0d6BEST
/dev/rmt/39mb /dev/rmt/c10t0d6BESTb
/dev/rmt/39mn /dev/rmt/c10t0d6BESTn
/dev/rmt/39mnb /dev/rmt/c10t0d6BESTnb
tape 40 0/7/1/0.2.28.255.0.0.7 stape CLAIMED DEVICE IBM 03590E1A
/dev/rmt/40m /dev/rmt/c10t0d7BEST
/dev/rmt/40mb /dev/rmt/c10t0d7BESTb
/dev/rmt/40mn /dev/rmt/c10t0d7BESTn
/dev/rmt/40mnb /dev/rmt/c10t0d7BESTnb



ioscan -fNC tape (THIS IS NOT OK, I WANT TO SEE 8 DRIVES)

kronos:root # ioscan -fNC tape
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
tape 8 64000/0xfa00/0x4 estape CLAIMED DEVICE IBM 03590E1A


ioscan -m hwpath (NOT OK, 1 DRIVE INCLUDES ALL 8 CONFIGURED DRIVES)

Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0x4
0/7/1/0.0x10000000c95f30c4.0x0 0/7/1/0.2.22.255.0.0.0
0/7/1/0.0x10000000c95f30c4.0x7000000000000 0/7/1/0.2.22.255.0.0.7
0/7/1/0.0x10000000c95f30c4.0x6000000000000 0/7/1/0.2.22.255.0.0.6
0/7/1/0.0x10000000c95f30c4.0x5000000000000 0/7/1/0.2.22.255.0.0.5
0/7/1/0.0x10000000c95f30c4.0x3000000000000 0/7/1/0.2.22.255.0.0.3
0/7/1/0.0x10000000c95f30c4.0x1000000000000 0/7/1/0.2.22.255.0.0.1
0/7/1/0.0x10000000c95f30c4.0x2000000000000 0/7/1/0.2.22.255.0.0.2
0/7/1/0.0x10000000c95f30c4.0x4000000000000 0/7/1/0.2.22.255.0.0.4

Best regards,

Helmut
1 REPLY
Vito Robar
Occasional Visitor

Re: Problems HPUX 11.31 and Fujitsu CentricStor VTA 1500

The issue is resolved.

The Host uses the HPUX11.31 specific Identifier for recognizing the drives.

Cause of the problem:

The 3590E virtual drive emulation generates a fixed Vendor
Specific Identifier (Bytes 48-55) for the Device Identification
Page (page code 0x83) of it's Inquiry command. That means, that
all configured 3590E are sending the same Identifier.
Some host applications using the Identifier for recognizing
the drives. Therefore the applications requesting unambiguous
Identifiers to differ the drives.



Please update CentricSotr to 3.1D SP04 P28.

Regards,

Helmut