Troubleshooting Sun StorageTek[TM] 2500, Sun Storage [TM] 6000: Volume Not on Preferred Path

Asset ID:	1-75-1136186.1
Update Date:	2011-05-19
Keywords:

Solution Type Troubleshooting Sure

Solution 1136186.1 : Troubleshooting Sun StorageTek[TM] 2500, Sun Storage [TM] 6000: Volume Not on Preferred Path

Applies to:

Sun Storage 6130 Array - Version: Not Applicable and later   [Release: N/A and later ]
Sun Storage 2530 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 2510 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 6180 Array - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 6140 Array - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.

Purpose

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community - Storage Disk 6000 and 2000 Series RAID Arrays

This document is intended to provide a basic overview on how to troubleshoot events for volume not on preferred path.

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.

Symptoms:

SANtricity or Common Array Manager (CAM) report a major fault of One or More Volumes not on their Preferred Path (xx.66.1010).
The Service Action Required (SAR) LED on the array is ON.

Last Review Date

June 28, 2010

Instructions for the Reader

A Troubleshooting Guide is provided to assist in debugging a specific issue. When possible, diagnostic tools are included in the document to assist in troubleshooting.

Troubleshooting Details

1. Verify the Critical Faults on the array.

Reference <Document 1021057.1> Verify Sun StorageTek[TM] 2500 and Sun Storage[TM] 6000 Critical Faults via the User Interface.

If there is a Critical Fault for RPA Memory Error (xx.66.1041) or a Critical Fault for Controller is Offline (xx.66.1028), please reference <Document 1021113.1> Troubleshooting Sun Storage[TM] RAID Controller Failures.
If there is a Critical Fault of Host IO Card has Failed (xx.66.1150) or a Critical Fault of Host IO Card is Degraded (xx.66.1300), please reference <Document 1120725.1> Troubleshooting Sun Storage[TM] 6580/6780 Host Interface Card Faults.
If thre is a Critical Fault for Volume(s) Not Managed by the Preferred Controller (xx.66.1010), go to Step 2.

2. Get the affected volume name(s) from the alarm.

Collect a supportdata:

Reference <Document 1002514.1> Collecting Support Data for Arrays Using Sun StorageTek[TM] Common Array Manager.
Reference <Document 1014074.1> Collecting Support Data for Arrays Using un StorageTek[TM] SANtricity Storage Manager.
Extract the volume name(s) from the alarm file:
- If you use Sun StorageTek[TM] Common Array Manager:
  1. Extract and open the alarms.txt file from the supportdata.
  2. Get the volume name(s) from the alarm xx.66.1010.
    Example:
```
Alarm ID   : alarm54
Description: The following volume(s) is/are not managed by their preferred controller MyVol
Severity   : Major
Element    : 600A0B8000488066000009B44A9BD244
GridCode   : 57.66.1010
Date       : 2009-09-08 09:58:30
```
- If you use Sun StorageTek[TM] SANtricity Storage Manager:
  1. Extract and open the recoveryGuruProcedures.html file from the supportdata.
  2. Get the volume name(s) from the Failure Entry NON_PREFERRED_PATH.
    
    Example:Storage array: ST6540
    Preferred owner: Controller in slot A
    Current owner: Controller in slot B
    Affected volume group: 1
    Volume: MyVol1, MyVol2
    Affected volume group: 3
    Volume: MyVol3

3. Identify the Owning Controller, Preferred Controller and GUID/WWN.

Extract and open the storageArrayProfile.txt file from the supportdata.
Scroll past the SUMMARY section to DETAILS.
Search for the STANDARD VOLUMES section.
Locate your volume(s) which you got from Step 2.
Get the Volume Name, Volume ID/GUID, Preferred owner and Current owner from the details.

Example:

VOLUME NAME: MyVol 
      Volume status: Optimal 
      Capacity:                 600 GB (644,245,094,400 Bytes)                   
      Volume ID:                60:0a:0b:80:00:16:a4:9d:00:00:00:2a:46:4a:43:99  
      Subsystem ID (SSID):      26                                               
      Associated volume group:  11                                               
      RAID level:               5                                                
      Drive type:            Fibre Channel  
      Tray loss protection:  No             
      Preferred owner:  Controller in slot A  
      Current owner:    Controller in slot A  
      Segment size:           64 KB  
      Modification priority:  High   
      Read cache:                            Enabled   
      Write cache:                           Enabled   
         Write cache without batteries:      Disabled  
         Write cache with mirroring:         Enabled   
      Flush write cache after (in seconds):  10.00     
      Dynamic cache read prefetch:           Enabled   
      Enable background media scan:      Disabled  
      Media scan with redundancy check:  Disabled

If only one volume is affected by the alarm xx.66.1010 or if all the volumes affected by the alarm xx.66.1010 have the same controller for the Current owner, go to Step 4.
If there are multiple volumes affected by the alarm xx.66.1010 and these volumes have different controllers for the Current owner, go to Step 9.

4. Check the status of the host ports on the array.

Extract and open the storageArrayProfile.txt file from the supportdata.
Search for the Controllers section.
Look at the "Link status:" for the host ports on each controller:

Example:

   Tray.85.Controller.A
â¦
      Host interface: Fibre
         Port: ffffff
         NL-Port ID: 255
         Maximum data rate: 8 Gbit/s
         Current data rate: 2 Gbit/s
         Data rate control: Auto
         Link status: Down
         Topology: Unknown
         World-wide port name: 201A0080E517B6B6
         World-wide node name: 200A0080E517B6B6
         Part type: PM8032          

      Host interface: Fibre
         Port: ffffff
         NL-Port ID: 255
         Maximum data rate: 8 Gbit/s
         Current data rate: 8 Gbit/s
         Data rate control: Auto
         Link status: Up
         Topology: Unknown
         World-wide port name: 202A0080E517B6B6
         World-wide node name: 200A0080E517B6B6
         Part type: PM8032          

   Tray.85.Controller.B
â¦
      Host interface: Fibre
         Port: ffffff
         NL-Port ID: 255
         Maximum data rate: 8 Gbit/s
         Current data rate: 2 Gbit/s
         Data rate control: Auto
         Link status: Down
         Topology: Fabric
         World-wide port name: 201B0080E517B6B6
         World-wide node name: 200A0080E517B6B6
         Part type: PM8032          

      Host interface: Fibre
         Port: ffffff
         NL-Port ID: 255
         Maximum data rate: 8 Gbit/s
         Current data rate: 2 Gbit/s
         Data rate control: Auto
         Link status: Down
         Topology: Unknown
         World-wide port name: 202B0080E517B6B6
         World-wide node name: 200A0080E517B6B6
         Part type: PM8032

If all the host ports are down on one controller, go to Step 5.
If at least one host port is up on each controller, go to Step 9.

5. Check the cable connections to the controller with all down ports.

If at least one host port on each controller is cabled, go to Step 6.
If there is, by design, no cable to the preferred controller, go to Step 8.
If there is, by accident, no cable to the preferred controller, insert a cable.

6. Check the link lights on the array host ports.

If the link status LED is down, go to Step 7.
If the link status LED is up, go to Step 9.

7. Re-seat Host cable connection that shows DOWN.

Re-seat the appropriate cable.

If the LED status changed but the fault remains after 10 min, go to Step 9.
If the LED status changed and the fault disappears after 10 min, no further work is required, as you have successfully fixed the issue.
If the LED status did not change, go to Step 9.

8. Change the volume ownership.

You have indicated that by design, the array is being accessed by a host through only one controller. Keep in mind that this requires a network connection to both controllers, even if only one controller is being accessed. The controller needs to be able to "PULL" the volume ownership.

For Common Array Manager (CAM), please reference <Document 1006464.1> Changing a volume's "owning controller" and "preferred controller" in Sun StorageTek[TM] Common Array Manager.
For SANtricity, please proceed with the following steps:

Right-Click on the Volume in the Logical View.
Click the Change sub-menu.
Click the Ownership/Preferred Path.
Click on the controller that you want the preferred ownership to transition.

Note: The behavior in SANtricity will be the same as in the above document for CAM.

9. Open a Service Call with Oracle for further research.

Please provide a Support Data Collection:

Reference <Document 1002514.1> Collecting Support Data for Arrays Using Sun StorageTek[TM] Common Array Manager.
Reference <Document 1014074.1> Collecting Support Data for Arrays Using Sun StorageTek[TM] SANtricity Storage Manager.

Attachments

This solution has no attachment