Troubleshooting Fibre Channel Devices from the Solaris Operating System

Asset ID:	1-75-1009557.1
Update Date:	2012-09-11
Keywords:

Solution Type Troubleshooting Sure

Solution 1009557.1 : Troubleshooting Fibre Channel Devices from the Solaris Operating System

Applies to:

Sun Storage 6920 System - Version Not Applicable and later
Sun Storage 3510 FC Array - Version Not Applicable and later
Sun Storage 3511 SATA Array - Version Not Applicable and later
Sun Storage T3 Array - Version Not Applicable and later
Sun Storage T3+ Array - Version Not Applicable and later
All Platforms

Purpose

Description

This document assumes that there is a problem with a Fibre Channel device path from Solaris and will address the required troubleshooting steps. The information contained in this document does not address SCSI devices.

In order to provide you the most accurate fix, please validate that each statement under the symptoms below is true for your environment. These symptoms will hyperlink you into a relevant content that will:

1) tell you how to validate the listed symptom
2) tell you how to fix the symptom if it is true for your environment.

The listed symptoms are ordered in the most appropriate sequence to isolate the issue and be certain about the related fix. Please do not skip a step.

Symptoms:

- Device disappeared

- Device offline

-Can not see device in format

-Can not see device with luxadm commands

-Link errors

Troubleshooting Steps

Steps to Follow

Please validate that each troubleshooting step below is true for your environment. Each step will provide instructions via a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.

Step 1 - Identify the device or device path from format(1M) or /var/adm/messages.

Validate that the HBA in the path can be seen from the Operating System, and the devices connected to the HBA are visible.

For details on how to verify this refer to:

How to verify connectivity on Oracle/Sun Branded Host Bus Adaptors (HBAs) (Doc ID 1009556.1)

Example of device path:

     /devices/pci@1f,4000/SUNW,qlc@4/fp@0,0

Step 2 - Validate that the multipathing software is optimal.

Oracle/Sun supports two types of multipathing: Sun Storage Traffic Manager(STMS) and Veritas Dynamic Multi-Pathing(DMP).

Refer to:

DocID: 1002465.1 "Verifying STMS (mpxio) health" for STMS
DocID: 1011302.1"Verifying DMP Health" for VxDMP

Step 3 - Verify Sun Storage Array hardware and configuration is optimal.

Refer to the troubleshooting documents below to confirm the hardware and configuration settings are correct:

For T3 : DocID: 1012673.1 "Troubleshooting Sun StorEdge T3 Configuration"

For 351x : DocID: 1005313.1 "Troubleshooting Sun StorEdge 33x0/351x Configurations"

Step 4 - At this point, if you have validated that each troubleshooting step above is true for your environment, and the issue still exists, further troubleshooting is required.

Please gather a Solaris Explorer, and contact Oracle Support.

Refer to the Sun Explorer Product Information Center (Doc ID 1312847.1)

Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains.

NOTE: Storage: Fibre Channel (FC) Devices reporting sd or ssd " SCSI parity error messages may not be faulty themselves.

T3, T3+, luxadm, can't see device, mpxio, vxdmp, path offline, mapping, lun, Audited, normalized
Previously Published As
86520

Attachments

This solution has no attachment