Sun Storage 2500, 2500-M2 and 6000 Arrays: How to Map a Target Reset Request to a Host Bus Adapter (HBA)

Asset ID:	1-71-1949216.1
Update Date:	2016-06-30
Keywords:

Solution Type Technical Instruction Sure

Solution 1949216.1 : Sun Storage 2500, 2500-M2 and 6000 Arrays: How to Map a Target Reset Request to a Host Bus Adapter (HBA)

Applies to:

Sun Storage 6540 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 6140 Array - Version All Versions to All Versions [Release All Releases]
Sun Storage 2530-M2 Array - Version Not Applicable to Not Applicable [Release N/A]
Sun Storage 2510 Array - Version Not Applicable and later
Sun Storage 2530 Array - Version Not Applicable and later
Information in this document applies to any platform.

Goal

A target reset is the result of retryable errors on a host, and is issued by the host to reset its target nexus or LUN. This indicates that after a SCSI packet was sent, a reset occured on the bus that prevented the completion of the packet. This may be an indication of a faulty component on the fibre channel path. Identifying the host bus adapter (HBA) involved is one essential step in troubleshooting the problem.

This document describes how to identify the HBA which initiated the target reset.

Solution

Beginning with firmware 07.10.xx.xx, the Major Event Log (MEL) entry contains HBA information in the raw data of the MEL event.

Follow the steps below to identify the HBA details:

Collect a support data bundle for the disk array. See <Document 1002514.1> Collecting Sun Storage Common Array Manager Support Data for Arrays.
After unzipping the support data bundle, open majorEventLog.txt in a text editor.
In the text editor, search for event type 1202 - Fibre channel - TGT reset received.

Date/Time: Fri Nov 14 14:31:18 EST 2014
Sequence number: 21357
Event type: 1202
Event category: Error
Priority: Informational
Description: Fibre channel - TGT reset received
Event specific codes: 0/0/0
Component type: Controller
Component location: Tray.85.Controller.A
Logged by: Controller in slot A

Raw data:

4d 45 4c 48 03 00 00 00 6d 53 00 00 00 00 00 00
02 12 18 10 86 58 66 54 00 00 00 00 09 00 00 00
02 10 00 00 01 00 00 00 22 00 00 00 22 00 00 00
08 00 00 00 55 00 00 00 01 00 00 00 01 00 00 00
0a 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01 00 00 00 00 00 00 01 10 00 00 00 0c 00 13 07
00 00 00 10 e0 21 80 c9 00 17 02 00

The last line shows the WWPN of the HBA in byte swap format: 00 00 00 10 e0 21 80 c9
This converts to Actual WWPN: 10000000C98021E0.

Open storageArrayProfile.txt from the support data bundle in a text editor. Using the above 16 alphanumeric digit World Wide Port Name (WWPN), find the associated hostname of this HBA from the Mappings section.

For this example, search for 10000000C98021E0

Host: blade0-0                          ---> Host that has the HBA installed in it
         Host Port WWN: 10000000C9802150
            Alias: blade0-0
            Type: Solaris_MPxIO
         Host Port WWN: 10000000C98021E0       ---> The HBA that sent the "Fibre channel - TGT reset received" to the disk array controller
            Alias: blade0-0
            Type: Solaris_MPxIO

It is possible that the WWPN is not associated with any host and/or the WWPN as part of Default Storage domain. In such cases, the host(s) should be checked individually for the corresponding WWPN. In such cases where the WWPN sending the Target Reset to the disk array is not from one of the WWPN(s) under the "Mappings" section of the storageArrayProfile.txt, better Switch Zoning Administration is recommended. Best practice recommendation for switch zoning is to have one HBA and one disk array controller per single switch zone configured on the fibre channel switch.

Attachments

This solution has no attachment