Cann't present luns to hp-ux v11.31

[Alexander Ketshvili]

Hi gurus
I have a question about how to present a storage EVA 4000 lun to the hp-ux v 11.31.

I pluged in a HBA, configure san switch, and now i can see the following

# fcmsutil /dev/fcd0

Vendor ID is = 0x1077
Device ID is = 0x2432
PCI Sub-system Vendor ID is = 0x103C
PCI Sub-system ID is = 0x1705
PCI Mode = PCI Express x4
ISP Code version = 4.4.4
ISP Chip version = 2
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0x680a00
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x5001438000c0b219
N_Port Port World Wide Name = 0x5001438000c0b218
Switch Port World Wide Name = 0x2008000dec471f00
Switch Node World Wide Name = 0x2001000dec471f01
N_Port Symbolic Port Name = hpux2_fcd0
N_Port Symbolic Node Name = hpux2_HP-UX_B.11.31
Driver state = ONLINE
Hardware Path is = 0/3/0/0/0/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
Driver Version = @(#) fcd B.11.31.0903 Dec 14 2008

there is the following output for the ioscan

ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
disk 0 0/2/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3

The lun is created corretly on EVA and is presented. I was able to present this lun to the hp-ux B.11.23 May be there is a driver problem or other suggestions?

[Steven E. Protter]

Shalom,

Your fcmsutil output shows a perfectly good connection.

The fiber switch is fully visible.

So long as you are not using Oracle RAC try:

insf -e -C disk

That should detect properly presented LUNS.

SEP

[Bob_Vance]

Did you try just a

ioscan
then
ioscan -Cdisk
ioscan -fnCdisk
?

Is this the same system that was the 11.23 system and you upgraded it
or
a new system?


bv

[Bob_Vance]

ooops
I meant
ioscan
insf -Cdisk
ioscan -fnCdisk
.

bv

[Bob_Vance]

Gives the details of your presentation of the LUN to this host,
such as
LUN #
WWNs assigned to the host entry in EVA
.

bv

[Norman_21]

Are you using power path? if the following commands don't present the disk, then you either have a problem with zoning/masking or your FA settings needs to be configured for 11.31

ioscan
ioscan -d sdisk
powermt config
powermt save
powermt display
ioscan -m dsf

[Torsten.]

Powerpath?
This would not make sense ...
Check again if the vdisk is presented in hpux mode

[Norman_21]

I'm not suggesting that power path is the issue. In fact, you don't need power path with the luns in 11.31 unless it's a company policy. However, we had to set an additional flag for the luns in 11.31 at the FA port level. We have EMC storage though.

[Bob_Vance]

>I'm not suggesting that power path is the issue

I've never used Powerpath.
I wouldn't expect it prevent the legacy devices from showing up in ioscan -- but I'm just guessing.

bv

[Bob_Vance]

For me, there are too many unanswered questions about the origins of this box and its relation to the "11.23" box, the HBAs, the EVA host definition, etc.

I would like to know exactly what the presentation looks like on the EVA.

If the WWN
0x5001438000c0b218
is showing up in the EVA,
then it can't be a zoning issue.

If he has
correctly added this port
to the correct host entry
& presented the LUN to the correct host
well then ...

ioscan should see it
.



bv

[Alexander Ketshvili]

Thanks all for helping. We have one storage with 2 hp-ux blade boxes connected to it. One of them is B.11.23. The second one (problematic) is a fresh install B.11.31. I presented new lun and try ioscan on the 11.31 system.
# ioscan -Cdisk
H/W Path Class Description
===================================================
0/2/1/0.0.0.0.0 disk HP IR Volume
# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
disk 0 0/2/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3

than i try to check if zone maping is fine on eva and try to do it on the 11.23. There is an output of ioscan on that system
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
disk 1 0/2/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c1t0d0 /dev/dsk/c1t0d0s2 /dev/rdsk/c1t0d0 /dev/rdsk/c1t0d0s2
/dev/dsk/c1t0d0s1 /dev/dsk/c1t0d0s3 /dev/rdsk/c1t0d0s1 /dev/rdsk/c1t0d0s3
disk 2 0/3/0/0/0/0.104.2.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c2t0d1 /dev/rdsk/c2t0d1
disk 0 0/3/0/0/0/0.104.2.0.0.0.2 sdisk NO_HW DEVICE HP HSV200
/dev/dsk/c2t0d2 /dev/rdsk/c2t0d2
disk 3 0/3/0/0/0/0.104.3.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c4t0d1 /dev/rdsk/c4t0d1
disk 6 0/3/0/0/0/0.104.3.0.0.0.2 sdisk NO_HW DEVICE HP HSV200
/dev/dsk/c4t0d2 /dev/rdsk/c4t0d2
disk 4 0/3/0/0/0/1.179.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c6t0d1 /dev/rdsk/c6t0d1
disk 7 0/3/0/0/0/1.179.0.0.0.0.2 sdisk NO_HW DEVICE HP HSV200
/dev/dsk/c6t0d2 /dev/rdsk/c6t0d2
disk 5 0/3/0/0/0/1.179.3.0.0.0.1 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c8t0d1 /dev/rdsk/c8t0d1
disk 8 0/3/0/0/0/1.179.3.0.0.0.2 sdisk NO_HW DEVICE HP HSV200
/dev/dsk/c8t0d2 /dev/rdsk/c8t0d2

Type: NO_HW shows this new presented lun.

[Torsten.]

>> Type: NO_HW shows this new presented lun.


But it is no longer present.

Did you unpresent or delete the LUNs?

[Alexander Ketshvili]

Yes of course. Than I presented it again to the 11.31, but no results for ioscan.

[Bob_Vance]

You still haven't shown us the presentation info from the EVA.

the host's
ports
& presented LUNs
.
Does this LUN exist and does the LUN info on the EVA show that it is presented to the new host as LUN 2?

bv

[Alexander Ketshvili]

By the way, this disks is no longer available for B.11.23 but i can still see it in the ioscan output. Is it correct?

[Torsten.]

Yes, NO_HW means it was visible, but it no longer is.


The 11.31 may prevent access if you present/unpresent a LUN, because of different identifiers.

Any problem to reboot the host?

Otherwise you need to use scsimgr to ignore the security settings ...


I would first check again if the LUN is presented to the correct HBA, zoning should not be a problem if the WWN is visible on EVA.

[Alexander Ketshvili]

Just 10 minutes, I will reboot a host, and give eva details..

[Alexander Ketshvili]

There is an output from the EVA

Vdisk LUN
Hp-Ux2 1


FC Adapter port WWN
5001-4380-00c0-B218
5001-4380-00c0-B21A

[Bob_Vance]

> 5001-4380-00c0-B218

So there's definitely no FC zoning problem.


Are these WWNs/ports, for sure, defined in EVA host HpUx2 ?


When you presented the LUN, did you assigne LUN 1 or LUN 2.
It looks like you may have done LUN 1 for HpUx2 and LUN 2 for HpUx1 ( which is OK), I'm just trying to understand everything.
I surmise this from the fact that the ioscan NO_HW (which I presume was from HpUx1) showed it was LUN 2.

Did you assign a host type when you presented the LUN?

bv

[Steven E. Protter]

Shalom,

Try this:

rmsf -x
(This is an 11.31 only command.)


That should clean up previously pulled LUNS.

Follow that with:

insf -e -C disk

That should reveal the newly presented LUNS and all will be well.

SEP

[Michael Leu]

Check syslog for 'replace wwid' messages.

[chris huys_4]

> 2 hp-ux blade boxes
What sort of hp-ux blades ? If they are recent, like the bl870c i2, spock, http://h20272.www2.hp.com, says for connecting a eva4000, at least the march 2010 HWE patches needs to be installed. (or a march 2010 HP-UX 11iv3 core-os OE installed.. (swlist |grep -i OE) )

Greetz,
Chris

[Alexander Ketshvili]

Thanks all
Bob Vance - the lun 2 for old hp-ux means that there is already one active lun presented to it. There is only one lun presented to v11.31 thats why lun number is 1.
From Eva side I can see that operating system type is Hp-Ux
Both blades are HP BL860c. Eva is 4100
Version of the (problemtic) Hp-UX is B.11.31.0903

[chris huys_4]

> Both blades are HP BL860c. Eva is 4100
That would be strange, because BL860c is a proliant blade.

BL860c i2, could be it though, and then indeed march2010 HWE is the minimum in hardware enablement patchbundles installed, or update to the march2010 core-os OE or better still the current march2011 core-os OE..

Greetz,
Chris

[Torsten.]

>> That would be strange, because BL860c is a proliant blade.


No, BL860c is Itanium, BL680c is Proliant.