HPUX creates 16 paths per lun instead of 8 against EVA8000

[Bryan Rooney]

Installed software:

HPswsp A.3.0F.02F.00F HP StorageWorks Secure Path Device Driver and utilities for Active-Active Disk Arrays

O/S:
HPUX11i-OE-MC B.11.23.0603 HP-UX Mission Critical Operating Environment Component
HPUXBaseAux B.11.23.0603 HP-UX Base OS Auxiliary
HPUXBaseOS B.11.23 HP-UX Base OS

Server:
rx8620 nPartition

Instead of getting the usualy 8 paths I'm seeing 16 instead. There seems to be an additional set created for each lun with 255 in the hardware path:
disk 4 1/0/8/1/0.1.13.0.0.0.1 sdisk CLAIMED DEVICE HP HSV210
disk 10 1/0/8/1/0.1.13.0.0.0.2 sdisk CLAIMED DEVICE HP HSV210
disk 21 1/0/8/1/0.1.13.0.0.0.3 sdisk CLAIMED DEVICE HP HSV210
disk 33 1/0/8/1/0.1.13.0.0.0.4 sdisk CLAIMED DEVICE HP HSV210
disk 41 1/0/8/1/0.1.13.0.0.0.5 sdisk CLAIMED DEVICE HP HSV210
disk 47 1/0/8/1/0.1.13.0.0.0.6 sdisk CLAIMED DEVICE HP HSV210
disk 6 1/0/8/1/0.1.13.255.0.0.1 sdisk CLAIMED DEVICE HP HSV210
disk 13 1/0/8/1/0.1.13.255.0.0.2 sdisk CLAIMED DEVICE HP HSV210
disk 24 1/0/8/1/0.1.13.255.0.0.3 sdisk CLAIMED DEVICE HP HSV210
disk 36 1/0/8/1/0.1.13.255.0.0.4 sdisk CLAIMED DEVICE HP HSV210
disk 43 1/0/8/1/0.1.13.255.0.0.5 sdisk CLAIMED DEVICE HP HSV210
disk 50 1/0/8/1/0.1.13.255.0.0.6 sdisk CLAIMED DEVICE HP HSV210

Presenting containers from two different EVA8000s. HPUX ioscan creates 16 paths per lun for one eva and 6 paths per lun for the other EVA. I have an identical server being built at the same time without this issue. The ioscan command on that server creates only 8 paths per lun for each EVA as expected.

I've checked our other EVAs and verified we are not presenting from any other EVA except the two EVA8000s.

Anyone run into this before?

[Bryan Rooney]

Additional info about the fiber cards:
# fcmsutil /dev/td0

Vendor ID is = 0x00103c
Device ID is = 0x001029
XL2 Chip Revision No is = 2.3
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x00128c
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x010700
N_Port Node World Wide Name = 0x50060b00003002e7
N_Port Port World Wide Name = 0x50060b00003002e6
Driver state = ONLINE
Hardware Path is = 1/0/8/1/0
Number of Assisted IOs = 16758
Number of Active Login Sessions = 0
Dino Present on Card = NO
Maximum Frame Size = 2048
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon XL2 Driver B.11.23.0512 $Date: 2005/09/20 12:22:47 $Revision: r11.23/1

[V.Manoharan]

Hi Bryan Rooney,
probably you can check the fiberchannel patches are of latest and all the EVA recomended patches installed.

I had similar kind of issue with MSA multiple entries of one single lun where the latest FC patches resolved the issue.

regards
Mano

[avik]

I am not quite sure but check to see if you have multiple zones enabled for the same hba and controllers.

[Bill Costigan · Accepted solution]

From the ioscan it looks like each LUN is being addressed via two differnet address modes.

e.g.
1/0/8/1/0.1.13.0.0.0.1
1/0/8/1/0.1.13.255.0.0.1

are both the same LUN.

Besides patches, is it possible the the OS selection for the host in the EVA is not correct or perhaps it is correct now but wasn't earlier and the HPUX server is now using both addressing methods to located the LUNs.

Another possibility is that secure path is creating an extra entry for each LUN. I haven't used the active/active version of SP but I recall that the older one created its pseudo LUNs using the 255 H/W paths while the original LUNs were addressed through the non-255 H/W paths. (they were converted to HSX devices)

[Bryan Rooney]

Bill -

Thanks for directing me towards my error.
You said:
"Besides patches, is it possible the the OS selection for the host in the EVA is not correct or perhaps it is correct now but wasn't earlier and the HPUX server is now using both addressing methods to located the LUNs."
I checked the SMAD for the EVA in question and the host with the issue had Windows assigned as a host. Flipped it to HPUX and that resolved the issue.
Thank you again.
Bryan

[Bryan Rooney]

Host config within Command View was set to Windows instead of HPUX, causing the unusual creation of extra disks.