XtremIO – General AIX Connectivity Diagnostics

Article Number: 498083 Article Version: 4 Article Type: How To



XtremIO Family,XtremIO X1,XtremIO HW Gen1,XtremIO HW Gen2 400GB,XtremIO HW Gen2 400GB Encrypt Capbl,XtremIO HW Gen2 400GB Encrypt Disable,XtremIO HW Gen2 400GB Exp Encrypt Disable,XtremIO HW Gen2 400GB Expandable,XtremIO HW Gen2 800GB Encrypt Capbl

Before collaborating with the AIX host team, find the following information:

  • Agree with the customer on nature of the issue is
  • Get host grabs whenever possible
  • Obtain out array info: device/LUN numbers, SP, FA port, etc
  • Obtain out the Switch info: model, serial number, port number, etc
  • Ascertain whether third party products are involved: Oracle, DB2, Epic, etc

Once you have host grabs, perform initial analysis using the following methods:

  • Upload the grab to E-lab Advisor (https://elabadvisor.psapps.emc.com/app/upload/form) and generate a PDF report
  • See what other hardware the host is running with checking the following logs in the host grab /host/ directory:
    • /host/lslpp_-L___grep_EMC.txt (Shows which EMC products are used)
    • /host/errpt.txt (Small output of error report)
    • /host/errpt_-a.txt (Large output of error report)
    • /host/oslevel_-s (Find AIX version)

You can see the list of EMC products in use from /host/lslpp_-L___grep_EMC.txt:

#################################################### EMC Global Services Software Development (GSSD) ## This text has been added by EMCGrab ## Copyright (C) 2016 by Dell EMC Corporation ## All rights reserved. ##################################################### Operating System: AIX 6.1# Hostname: uxlawappprod# EMCGrab RunDate: Thu Mar 23 11:06:44 CDT 2017#################################################### Party Number: # Customer: # Contact Name: # Contact Phone: # Contact eMail: # Service Request Number: No Information Supplied#################################################### Command used to generate this file: lslpp -L | grep EMC# Output Filename: lslpp_-L___grep_EMC.txt################################################### AvamarClient-aix6-ppc 7.2.101.32 C F EMC Avamar client 7.2.101-32 AvamarDB2-aix6-ppc64 6.1.101.87 C F EMC Avamar client 6.1.101-87 EMC.CLARiiON.aix.rte 5.3.1.0 C F EMC CLARiiON AIX Support EMC.CLARiiON.fcp.rte 5.3.1.0 C F EMC CLARiiON FCP Support EMC.Symmetrix.aix.rte 5.3.0.5 C F EMC Symmetrix AIX Support EMC.Symmetrix.fcp.rte 5.3.0.5 C F EMC Symmetrix FCP Support EMC.XtremIO.aix.rte 5.3.1.0 C F EMC XtremIO AIX Support EMC.XtremIO.fcp.rte 5.3.1.0 C F EMC XtremIO FCP Support EMCpower.MgmtComponent 6.1.0.0 C F PowerPath Management EMCpower.base 6.1.0.0 C F PowerPath Base Driver and EMCpower.migration_enabler EMCpower.mpx 6.1.0.0 C F PowerPath Multi_Pathing 

Check /host/errpt.txt for a small output of error report:

IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTIONA924A5FC 0726083113 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATEDDCB47997 0721234813 T H hdisk231 DISK OPERATION ERRORDCB47997 0718233213 T H hdisk213 DISK OPERATION ERRORA924A5FC 0717184713 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED26623394 0708153613 T H fscsi2 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi2 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi2 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi2 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi2 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi2 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi0 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi0 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi0 COMMUNICATION PROTOCOL ERROR26623394 0708153613 T H fscsi0 COMMUNICATION PROTOCOL ERRORA924A5FC 0706201513 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATEDDCB47997 0705211013 T H hdisk39 DISK OPERATION ERRORA924A5FC 0704220513 P S SYSPROC SOFTWARE PROGRAM ABNORMALLY TERMINATED 

How do identify Disk Reservations issues from errpt_-a.txt

LABEL: SC_DISK_ERR2IDENTIFIER: B6267342.Type: PERM.Deleted..SENSE DATA0A00 2A00 0000 0064 0000 0804 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 002E E154 000A 3D00 0000 0000 0000 0000 0000 0000 0000 0083 0000 0000 003D 0017 

The PERM status of the error report indicates that the IO failed, a TEMP means that it was a retriable error and the IO succeeded, as follows:

LABEL: SC_DISK_ERR4.Type: TEMP.Deleted..SENSE DATA0A00 2A00 0000 0064 0000 0804 0000 0000 0000 0000 0000 0000 0118 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 002E E154 000A 3D00 0000 0000 0000 0000 0000 0000 0000 0083 0000 0000 003D 0017 

Device not ready errors can be reported in the following ways:

  1. The customer can set the device not ready on the array or with ECC
  2. A BCV is established to the source. An established BCV reports device not ready
  3. An I/O is sent down the passive path will usually report the device as not ready

To check for those alerts in errpt_-a.txt:

LABEL: SC_DISK_ERR2IDENTIFIER: B6267342.Type: PERMWPAR: GlobalResource Name: hdisk27Resource Class: diskResource Type: INVISTA_DISKPATH ID 0SENSE DATA0600 1B00 0000 0100 0000 0000 0000 0000 0000 0000 0000 0000 01020000 7000 0400 0000 000A 0000 0000 0403 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 5812 0005 40C0 0000 0000 0000 0000 0000 0000 0000 0083 0000 0000 0027 001A 

To see Command Time Out Disk Errors from /host/errpt_-a.txt for a command timeout on a read:

LABEL: SC_DISK_ERR4IDENTIFIER: DCB47997..Type: TEMPWPAR: GlobalResource Name: hdisk303Resource Class: diskResource Type: SYMM_VRAID..SENSE DATA0A00 2800 018A 6510 0000 1004 0000 0000 0000 0000 0000 0000 02000300 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0001 041C 000A B900 0000 0000 0000 0000 0000 0000 0000 0083 0000 0000 0035 001D 

To see Command Timeout Disk Error for No Device Response:

LABEL: SC_DISK_ERR3.Date/Time: Mon Aug 26 11:59:06 2013.Type: PERMWPAR: GlobalResource Name: hdisk19.DISK OPERATION ERROR.SENSE DATA0600 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 02000400 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0082 0000 0000 0034 001A 

Related:

  • No Related Posts

Leave a Reply