Operating System - HP-UX
1752518 Members
4850 Online
108788 Solutions
New Discussion юеВ

Re: After Applying patch PHKL_39747 - SAN disk are not available

 
ShebCnty
New Member

After Applying patch PHKL_39747 - SAN disk are not available

HP 11.31 - Applied patch PHKL_39747 as it was requested for Orcle Application Server, now I do not see my SAN disks.

# ioscan -funCdisk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 0 0/6/0/0/0/0/4/0/0/0.0.0 sdisk CLAIMED DEVICE HP LOGICAL 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
disk 2 255/1/0.0.0 sdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
#

Prior to Patch:
# ioscan -funCdisk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 8 0/3/0/0/0/0.97.9.19.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c8t0d0 /dev/rdsk/c8t0d0
disk 7 0/3/0/0/0/0.97.11.19.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c9t0d0 /dev/rdsk/c9t0d0
disk 0 0/6/0/0/0/0/4/0/0/0.0.0 sdisk CLAIMED DEVICE HP LOGICAL 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
disk 4 0/7/0/0/0/0.97.4.19.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c11t0d0 /dev/rdsk/c11t0d0
disk 5 0/7/0/0/0/0.97.5.19.0.0.0 sdisk CLAIMED DEVICE DGC CX500WDR10
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 2 255/1/0.0.0 sdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0


Both the HBA seems to be OK
# ioscan -funCfc
Class I H/W Path Driver S/W State H/W Type Description
====================================================================
fc 0 0/3/0/0/0/0 fclp CLAIMED INTERFACE HP AD299-60001 4Gb PCIe 1-port Fibre Channel Adapter
/dev/fclp0
fc 1 0/7/0/0/0/0 fclp CLAIMED INTERFACE HP AD299-60001 4Gb PCIe 1-port Fibre Channel Adapter
/dev/fclp1
#

Help Please!
11 REPLIES 11

Re: After Applying patch PHKL_39747 - SAN disk are not available

PHKL_39747 is not a storage subsystem patch, so I think its unlikely to be this particular patch that caused the problem... however did you install other patches at the same time?

Or maybe you turned off legacy DSFs?

What's the output of:

ioscan -funNC disk

This will show the agile DSFs...

What about:

insf -Lv

Does that show legacy mode enabled or disabled?

HTH

Duncan

I am an HPE Employee
Accept or Kudo
Steven E. Protter
Exalted Contributor

Re: After Applying patch PHKL_39747 - SAN disk are not available

Shalom,

I would swremove the patches recently installed and reboot.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
ShebCnty
New Member

Re: After Applying patch PHKL_39747 - SAN disk are not available

# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 1 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/disk/disk1 /dev/disk/disk1_p2 /dev/rdisk/disk1 /dev/rdisk/disk1_p2
/dev/disk/disk1_p1 /dev/disk/disk1_p3 /dev/rdisk/disk1_p1 /dev/rdisk/disk1_p3
disk 3 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk3 /dev/rdisk/disk3
#



# insf -Lv
insf: Legacy mode is enabled
#
ShebCnty
New Member

Re: After Applying patch PHKL_39747 - SAN disk are not available

yes dependent patched were also installed.

* Installing fileset "PHKL_38746.CORE2-KRN,r=1.0" (1 of 21).
* Installing fileset "PHKL_39747.C-INC,r=1.0" (2 of 21).
* Installing fileset "PHKL_39747.CORE2-KRN,r=1.0" (3 of 21).
NOTE: The requested changes could not be applied to the currently
running system, for the following reasons:
- Moving a module into or out of the 'static' state requires a
kernel rebuild.
* The system file '/stand/system' has been imported. The changes
will take effect at next boot.
* Installing fileset "PHKL_39747.ADMN-ENG-A-MAN,r=1.0" (4 of
21).
* Installing fileset "PHKL_39747.CORE-ENG-A-MAN,r=1.0" (5 of
21).
* Installing fileset "PHKL_39747.KERN-ENG-A-MAN,r=1.0" (6 of
21).
* Installing fileset "PHKL_39747.PAUX-ENG-A-MAN,r=1.0" (7 of
21).
* Installing fileset "PHSS_38527.CORE2-64SLIB,r=1.0" (8 of 21).
* Installing fileset "PHSS_38527.CORE2-SHLIBS,r=1.0" (9 of 21).
* File "/usr/lib/hpux32/aries32.so" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux32/pa_boot32.so" could not be removed. It
was renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* Installing fileset "PHSS_39094.C-KRN,r=1.0" (10 of 21).
* Installing fileset "PHSS_39094.C-MIN,r=1.0" (11 of 21).
* Installing fileset "PHSS_39094.C2-INC,r=1.0" (12 of 21).
* Installing fileset "PHSS_39094.CMDS2-AUX,r=1.0" (13 of 21).
* Installing fileset "PHSS_39094.CORE-64SLIB,r=1.0" (14 of 21).
* Installing fileset "PHSS_39094.CORE-SHLIBS,r=1.0" (15 of 21).
* File "/usr/lib/dld.sl" could not be removed. It was renamed
and added to the cleanup file "/var/adm/sw/cleanupfile".
* File "/usr/lib/libdld.2" could not be removed. It was renamed
and added to the cleanup file "/var/adm/sw/cleanupfile".
* Installing fileset "PHSS_39094.CORE2-64SLIB,r=1.0" (16 of 21).
* File "/usr/lib/hpux64/dld.so" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux64/libdl.so.1" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux64/libelf.so.1" could not be removed. It
was renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux64/uld.so" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* Installing fileset "PHSS_39094.CORE2-SHLIBS,r=1.0" (17 of 21).
* File "/usr/lib/hpux32/dld.so" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux32/libdl.so.1" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux32/libelf.so.1" could not be removed. It
was renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* File "/usr/lib/hpux32/uld.so" could not be removed. It was
renamed and added to the cleanup file
"/var/adm/sw/cleanupfile".
* Installing fileset "PHSS_39094.LANG-64ALIB,r=1.0" (18 of 21).
* Installing fileset "PHSS_39094.LANG-MIN,r=1.0" (19 of 21).
* Installing fileset "PHSS_39094.LINKER-HELP,r=1.0" (20 of 21).
* Installing fileset "PHSS_39094.LINKER-PAOBJ,r=1.0" (21 of 21).
* Building the software file "/var/adm/sw/needs_config" to be
used for post-reboot "swconfig" execution. The information in
this file will be used as input to "swconfig" after the system
reboots.

Patrick Wallek
Honored Contributor

Re: After Applying patch PHKL_39747 - SAN disk are not available

You did reboot the system after the patches were installed, right?
ShebCnty
New Member

Re: After Applying patch PHKL_39747 - SAN disk are not available

ioscan -P health
shows

fc 0 0/3/0/0/0/0 offline
fc 1 0/7/0/0/0/0 offline

Re: After Applying patch PHKL_39747 - SAN disk are not available

well that suggests a probvlem with your Clariion storage. Can you confirm that you are at least on FLARE26 and using failover mode 4 (ALUA) - these are both Clariion settings - to me this looks like you mkay be seeing only 2 ports on one Clariion controller whilst the LUN is "active" on the other controller...

HTH

Duncan

I am an HPE Employee
Accept or Kudo
Jozef_Novak
Respected Contributor

Re: After Applying patch PHKL_39747 - SAN disk are not available

Hello,

check which nport IDs are reachable with fcmsutil:

# fcmsutil dev/fclp0 get remote all

do it for both fclp cards.

J.
tkc
Esteemed Contributor

Re: After Applying patch PHKL_39747 - SAN disk are not available

do check out if the fclp driver needs update :

http://www.docs.hp.com/en/J4301-90016_e2/ar01s03.html