Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1999001.1
Update Date:2018-02-08
Keywords:

Solution Type  Problem Resolution Sure

Solution  1999001.1 :   LUN Status Failed From OPs Center  


Related Items
  • SPARC T5-4
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>HBA>SN-DK: FC HBA
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-10390785431>

Applies to:

SPARC T5-4 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

We have OPs Center running that shows the status of a LUN as failed.

The storage is from IBM

LUN GUID 00173800505816d5 size 64gb , all the others luns from the same storage have Status OK

The lun is visible at format 

We can see the physical paths and the storage ports Online using luxadm display or fcinfo lu -v

Application and Solaris have access to the lun

The only in-congruence is from mpathadm that the storage ports seems to be not available

Cause

The storage is IBM 2810XIV

LUN GUID 00173800505816d5 size 64gb , all the others luns from the same storage have Status OK

From Solaris :

** The lun is visible at format

From format

  14. c0t00173800505816D5d0
  /scsi_vhci/ssd@g00173800505816d5

** This is from the luxadm display , we can see the physical paths and the storage ports
** The path are ONLINE


DEVICE PROPERTIES for disk: 500xxxxxxxx0000
  Vendor: IBM
  Product ID: 2810XIV
  Revision: 0000
  Serial Num: 780505816D5
  Unformatted capacity: 65644.000 MBytes
  Read Cache: Enabled
  Minimum prefetch: 0x0
  Maximum prefetch: 0x0
  Device Type: Disk device
  Path(s):

  /dev/rdsk/c0t00173800505816D5d0s2
  /devices/scsi_vhci/ssd@g00173800505816d5:c,raw
  Controller /devices/pci@340/pci@1/pci@0/pci@6/SUNW,qlc@0,1/fp@0,0
  Device Address 500xxxxxxxxxx142,1
  Host controller port WWN 21000024ff56bf7d
  Class primary
  State ONLINE
  Controller /devices/pci@340/pci@1/pci@0/pci@6/SUNW,qlc@0,1/fp@0,0
  Device Address 500xxxxxxxxxx152,1
  Host controller port WWN 21000024ff56bf7d
  Class primary
  State ONLINE
  Controller /devices/pci@340/pci@1/pci@0/pci@6/SUNW,qlc@0/fp@0,0
  Device Address 500xxxxxxxxxx140,1
  Host controller port WWN 21000024ff56bf7c
  Class primary
  State ONLINE
  Controller /devices/pci@340/pci@1/pci@0/pci@6/SUNW,qlc@0/fp@0,0
  Device Address 500xxxxxxxxxx150,1
  Host controller port WWN 21000024ff56bf7c
  Class primary
  State ONLINE

*** From cfgadm the lun id 1 is connected configured

c15::500xxxxxxxxxx140,1 disk connected configured unknown
c15::500xxxxxxxxxx150,1 disk connected configured unknown
c16::500xxxxxxxxxx142,1 disk connected configured unknown
c16::500xxxxxxxxxx152,1 disk connected configured unknown


**** The only in-congruence is from mpathadm that the storage ports seems to be not available

mpathadm_list_LU.out: /dev/rdsk/c0t00173800505816D5d0s2
mpathadm_show_LU_c0t00173800505816D5d0s2.out: Name: 00173800505816d5

Logical Unit: /dev/rdsk/c0t00173800505816D5d0s2
  mpath-support: libmpscsi_vhci.so
  Vendor: IBM
  Product: 2810XIV
  Revision: 0000
  Name Type: unknown type
  Name: 00173800505816d5
  Asymmetric: yes
  Current Load Balance: round-robin
  Logical Unit Group ID: NA
  Auto Failback: on
  Auto Probing: NA

  Paths:
  Initiator Port Name: 21000024ff56bf7c
  Target Port Name: 500xxxxxxxxxx140
  Override Path: NA
  Path State: unknown
  Disabled: no

  Initiator Port Name: 21000024ff56bf7c
  Target Port Name: 500xxxxxxxxxx150
  Override Path: NA
  Path State: unknown
  Disabled: no

  Initiator Port Name: 21000024ff56bf7d
  Target Port Name: 500xxxxxxxxxx142
  Override Path: NA
  Path State: unknown
  Disabled: no

  Initiator Port Name: 21000024ff56bf7d
  Target Port Name: 500xxxxxxxxxx152
  Override Path: NA
  Path State: unknown
  Disabled: no

  Target Port Groups:
  ID: 0
  Explicit Failover: no
  Access State: unavailable <<<<<<<<<<
  Target Ports:
  Name: 500xxxxxxxxxx140
  Relative ID: 1024

  Name: 500xxxxxxxxxx150
  Relative ID: 1280

  Name: 500xxxxxxxxxx142
  Relative ID: 1026

  Name: 500xxxxxxxxxx152
  Relative ID: 1282

 

OPs Center  mostly uses:

   /opt/sun/n1gc/bin/xvmserver/xvmluinfo

This does look at path status. If the above command is showing that the paths are down, as it fetches it from the OS, then it's fully possible that the LUNs will show as degraded.

The faults should clear, as OC does periodic refresh of the xvmluinfo command, automatically once the path issue is resolved.

Looking at the source for xmvluinfo and it gets the details via libmpapi (see the manpage), which looks to be the same place that mpathadm gets its details from.

 

** The output of xmvluinfo reflect the status visible by mpathadm  

     Name            :  "00173800505816d5",

       NameType        :  "unknown type",

       DevPathName     :  "/dev/rdsk/c0t00173800505816D5d0s2",

       Capacity        :  67219456,

       OperationalPathCount   :  0,

       Vendor          :  "IBM     ",

       Product         :  "2810XIV         ",

       Revision        :  "0000",

       MultiPathConfig : {

               Asymmetric      :  "true",

               LoadBalanceType :  "roundrobin",

               LUGroupId       :  "NA",

               AutoFailbackEnabled     :  "on",

               AutoProbingEnabled      :  "NA",

       },

       LogicalUnitPaths : [

               {

               Weight          :  0,

               InitiatorPort   :  "21000024ff56bf7c",

               TargetPort      :  "500xxxxxxxxxx140",

               OverridePath    :  "NA",

               State   :  "unknown",

               Disabled        :  "false",

               },

               {

               Weight          :  0,

               InitiatorPort   :  "21000024ff56bf7c",

               TargetPort      :  "500xxxxxxxxxx150",

               OverridePath    :  "NA",

               State   :  "unknown",

               Disabled        :  "false",

               },

               {

               Weight          :  0,

               InitiatorPort   :  "21000024ff56bf7d",

               TargetPort      :  "500xxxxxxxxxx142",

               OverridePath    :  "NA",

               State   :  "unknown",

               Disabled        :  "false",

               Weight          :  0,

               InitiatorPort   :  "21000024ff56bf7d",

               TargetPort      :  "500xxxxxxxxxx152",

               OverridePath    :  "NA",

               State   :  "unknown",

               Disabled        :  "false",

               },

       ],

       TargetPortGroups :  [

               {

                       TPGId           :  0,

                       ExplicitFailover        :  "false",

                       AccessState     :  "unavailable",

               TargetPorts     : [

                       {

                       Name            :  "500xxxxxxxxxx140",

                       },

                       {

                       Name            :  "500xxxxxxxxxx150",

                       },

                       {

                       Name            :  "500xxxxxxxxxx142",

                       },

                       {

                       Name            :  "500xxxxxxxxxx152",

                       },

               ]

               },

       ],

 

       Status          :  FAILED   },

 

Solution

Until the mpathadm will not reflect the Path State OK , the OPs Center will return the status Degraded or Failed for the lun

The luxadm -e forcelip and the mpathadm failover have not changed the state of the path 

To restore the path state from mpathadm we have to run the luxadm -e offline  

# luxadm -e offline /devices/pci@340/pci@1/pci@0/pci@6/SUNW,qlc@0

# luxadm -e online /devices/pci@340/pci@1/pci@0/pci@6/SUNW,qlc@0

 The status of the LUN appears OK after executing the above luxadm -e offline/online 

References

<NOTE:1303745.1> - Troubleshooting Solaris[TM] 10 and Above (not for Solaris[TM] 8 & 9) SAN Fibre Channel (FC) HBA connectivity issues.
<NOTE:166650.1> - Working Effectively With Oracle Support - Best Practices
<NOTE:1339783.1> - Automated Diagnosis Requirements and Expectations for Disk Storage
<NOTE:1153444.1> - Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback