Lost SAN disks on HPUX 11.00

[Ken Penland_1]

I admittedly know very little about SAN allocations. All I know is that the SAN admin configured some disks, I saw it on my HP, and now I do not. He says everything is fine on his end, so it must be a problem with my HP..

Here is what I discovered so far. We have two systems that are practically identical, on the system that works, when I do an ioscan, I see the SAN disk configured to it as:
255 ba
255/0 ext_bus HSV110 (C)COMPAQ 0x50001FE150048540
255/1 ext_bus HSV110 (C)COMPAQ 0x50001FE150048540
255/1.0 target
255/1.0.1 disk HSV110 (C)COMPAQ


on the system that cannot see its disk, I see:

255 ba
255/0 ext_bus HSV110 (C)COMPAQ 0x50001FE150048540


the fact that I DO see it in ioscan leads me to believe that it is a problem with the HP. Any thoughts on what I should do to further troubleshoot or to fix this problem?

[RAC_1]

You are seeing just one disk. What is you do ioscan -fnCdisk? How many of disks it list and how many are from SAN??

Did you try insf -ev??

I am doubting that SANADMIN did change something. May be port assignments, zoning or something. What SAN is this??

[Ken Penland_1]

ioscan -funC disk on the good system I see the two internal disks, and the one SAN disk.

On the bad system, I see the two internal disks, but no SAN disk.

I have done insf -e, rebooted the box, nothing seems to bring it back.

[Ken Penland_1]

Good:
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
disk 0 0/0/1/1.15.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c1t15d0 /dev/rdsk/c1t15d0
disk 1 0/0/2/1.15.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c3t15d0 /dev/rdsk/c3t15d0
disk 2 255/1.0.1 sdisk CLAIMED DEVICE HSV110 (C)COMPAQ
/dev/dsk/c15t0d1 /dev/rdsk/c15t0d1


Broken:
# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
disk 0 0/0/1/1.15.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c1t15d0 /dev/rdsk/c1t15d0
disk 1 0/0/2/1.15.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c3t15d0 /dev/rdsk/c3t15d0

[RAC_1]

How SAN disks are connected on bad system?? Through FC cards?? IF yes, what does fcmsutil /dev/tdx say??

What does, ioscan fnCext_bus say??

Anil

[Ken Penland_1]

I dont think the is set up or something, I get an error message

fcmsutil /dev/dsk/c15t0d1
Error: FCP driver not loaded.
could not open device file.: No such device or address


but I got the ioscan for you, it is attached.

[RAC_1]

fcmsutil /dev/tdx

NOTICE "/dev/tdx" and not /dev/dsk stuff
Where x is number as you see in /dev/tdx device file.

[Ken Penland_1]

ah, I just noticed that as you posted, the bad and the good look pretty much identical..just a few number changes...the bad system is attached.

[Ken Penland_1]

Okay, now I have a new problem...the folks out where the HP actually resides (a UNIX guy and a SAN guy) fixed the problem, they are sending me the documentation on what they did...however, the disk is now seen as
c14t0d0 instead of c15t0d0 so I need to try and move the volume group information to point to the new disk...


All this on a late friday before a three day too.... *sigh*

[Ken Penland_1]

Oh, I didnt want that to mean I needed help with that...that was something I know about...I just had to blow away the lvmtab file and re-run vgscan -a

Thanks RAC for your patience...I still dont know what they did, he explained a bit over the phone, and it all sounded greek to me...I dont think I ever would have gotten it :P

[Ken Penland_1]

Thanks again RAC