Reg : Luns identify - HP-UX

[Mastan]

Hi,

I have created 10 new luns in Hitachi AMS 500 SAN and the SAN is connected hp-ux server through Brocade 8 Gbit/Sec SAN Switch.
I am able to see 8 new luns, but remaing two luns I am not abule to identify.
How to identify reaming two luns in HP-UX B.11.23 U ia64 unlimited-user license server.

Thanks in advance.

Regards,
Mastan.

Please guide me.

[Ricardo Pagán · Accepted solution]

whenever you create a path in the SAN must do a ioscan-fnC, often when using virtual machines to see what roads to use ioscan-tinienes fnNC and this option really all paths created.

[Steven E. Protter]

Shalom,

Please show output:

ioscan -fnCdisk

ioscan -m dsf

SEP

[Mastan]

Hi,

I have run ioscan -fnC disk command and please go through the below out put.

Inside the SAN total luns are 10 and here it is showing 8 luns only.


# ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s1 /dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s1 /dev/rdsk/c2t0d0s3
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s1 /dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s1 /dev/rdsk/c2t1d0s3
disk 3 0/3/1/0.1.2.255.0.0.0 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 4 0/3/1/0.1.2.255.0.0.1 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d1 /dev/rdsk/c6t0d1
disk 5 0/3/1/0.1.2.255.0.0.2 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d2 /dev/rdsk/c6t0d2
disk 6 0/3/1/0.1.2.255.0.0.3 sdisk NO_HW DEVICE HITACHI DF600F
/dev/dsk/c6t0d3 /dev/rdsk/c6t0d3
disk 7 0/3/1/0.1.2.255.0.0.4 sdisk NO_HW DEVICE HITACHI DF600F
/dev/dsk/c6t0d4 /dev/rdsk/c6t0d4
disk 8 0/3/1/0.1.2.255.0.0.5 sdisk NO_HW DEVICE HITACHI DF600F
/dev/dsk/c6t0d5 /dev/rdsk/c6t0d5
disk 9 0/3/1/0.1.2.255.0.0.6 sdisk NO_HW DEVICE HITACHI DF600F
/dev/dsk/c6t0d6 /dev/rdsk/c6t0d6
disk 10 0/3/1/0.1.2.255.0.0.7 sdisk NO_HW DEVICE HITACHI DF600F
/dev/dsk/c6t0d7 /dev/rdsk/c6t0d7

How to identify remaining 2 Luns..!

Regards,
Mastan.

[Ricardo Pagán]

ioscan -fnNC disk

[Mastan]

# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
/dev/dsk/c2t0d0s1 /dev/rdsk/c2t0d0s1
/dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s3
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 73.4GST373454LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
/dev/dsk/c2t1d0s1 /dev/rdsk/c2t1d0s1
/dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s3
disk 3 0/3/1/0.1.2.255.0.0.0 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d0 /dev/rdsk/c6t0d0
disk 4 0/3/1/0.1.2.255.0.0.1 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d1 /dev/rdsk/c6t0d1
disk 5 0/3/1/0.1.2.255.0.0.2 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d2 /dev/rdsk/c6t0d2
disk 6 0/3/1/0.1.2.255.0.0.3 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d3 /dev/rdsk/c6t0d3
disk 7 0/3/1/0.1.2.255.0.0.4 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d4 /dev/rdsk/c6t0d4
disk 8 0/3/1/0.1.2.255.0.0.5 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d5 /dev/rdsk/c6t0d5
disk 9 0/3/1/0.1.2.255.0.0.6 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d6 /dev/rdsk/c6t0d6
disk 10 0/3/1/0.1.2.255.0.0.7 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c6t0d7 /dev/rdsk/c6t0d7

[Ricardo Pagán]

Please show output

ioscan -fnNC disk

[Mastan]

luns - san ss

[chris huys_4]

Hi Mastan,

Looks to me that the storage guys didnt setup the array right.

The 255 in the 0/3/1/0.1.2.255.0.0.2 hwpath, looks to indicate that the ams500 diskarray controller is not configured with a fabric + pt to pt protocol.

So probably the diskarray is wrongly setup. Get the hitachi diskarray controllers properly setup and all should go well.

F.e. like in the following thread, were it looks like the same kind of diskarray but were the diskarray controller is setup in fabric mode + pt to pt protocol, and hence the 109 "figure" instead of the "255" figure.

https://forums13.itrc.hp.com/service/forums/questionanswer.do?threadId=1451981

disk 106 4/0/10/1/0.14.0.109.0.2.4 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c12t2d4 /dev/rdsk/c12t2d4
disk 107 4/0/10/1/0.14.0.109.0.2.5 sdisk CLAIMED DEVICE HITACHI DF600F
/dev/dsk/c12t2d5 /dev/rdsk/c12t2d5


Greetz,
Chris

[Mastan]

Hi Chris Huys, Ricardo Pagán, Steven E. Protter ,

Thanks for your suggestions.

We come to know that the HP server support only 8 LUNs per one port.

NOTE: Host Group parameter called "HP Connection Mode 2" that should be enabled in orderto have HP-UX reconigzing more than 8 LUNs in different targets.

Regards,
Mastan.